Procedure details
- Dina Bennett (Deactivated)
In the sequence diagram, you have the option to filter directly by specific protocol procedures, allowing you to focus on analysis. All procedures are defined using 3GPP definitions.
Below, you'll find the list and details of each procedure per protocol. These tables can be used as a reference to understand the procedures list included with the sequence diagram.
Diameter
Diameter is a signaling protocol used in telecommunications for authentication, authorization, and accounting (AAA) purposes. It is often used in communication between network elements, such as between a user's device and a Policy and Charging Rules Function (PCRF) in mobile networks.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
DIAMETER_Cx_ims | I/S-CSCF--HSS | DIAMETER + interface + pdn_class | This interface enables: Cx is a set of procedures that can be executed between the CSCF (interrogating and serving) and the HSS. Commands in this interface are used for the registration, location, and service profile access procedures on these interfaces. Messages |
DIAMETER_Gx | PGW--PCRF | DIAMETER + interface + pdn_class | Used by the PCRF to deliver commands for deploying and deleting charging policies to the PDN gateway (P-GW) and used by the P-GW to report bearer events to the PCRF. The Gx interface is located between the Policy and Charging Enforcement Function (PCEF) in PGW and the Policy and Charging Rules Function (PCRF) The Gx interface is used for provisioning and removal of PCC rules from the PCRF to the PCEF in PGW and the transmission of traffic plane events from the PCEF to the PCRF. The Gx interface can be used for charging control, policy control or both by applying AVPs relevant to the application. The Gx interface provides the following functions:
Messages |
DIAMETER_Gx_data | PGW--PCRF | DIAMETER + interface + pdn_class | Used by the PCRF to deliver commands for deploying and deleting charging policies to the PDN gateway (P-GW) and used by the P-GW to report bearer events to the PCRF, specific to data APN(pdn class). The Gx interface is located between the Policy and Charging Enforcement Function (PCEF) in PGW and the Policy and Charging Rules Function (PCRF) The Gx interface is used for provisioning and removal of PCC rules from the PCRF to the PCEF in PGW and the transmission of traffic plane events from the PCEF to the PCRF. The Gx interface can be used for charging control, policy control or both by applying AVPs relevant to the application. The Gx interface provides the following functions:
Messages |
DIAMETER_Gx_ims | PGW--PCRF | DIAMETER + interface + pdn_class | Used by the PCRF to deliver commands for deploying and deleting charging policies to the PDN gateway (P-GW) and used by the P-GW to report bearer events to the PCRF, specific to ims apn (pdn class). The Gx interface is located between the Policy and Charging Enforcement Function (PCEF) in PGW and the Policy and Charging Rules Function (PCRF) The Gx interface is used for provisioning and removal of PCC rules from the PCRF to the PCEF in PGW and the transmission of traffic plane events from the PCEF to the PCRF. The Gx interface can be used for charging control, policy control or both by applying AVPs relevant to the application. The Gx interface provides the following functions:
Messages |
DIAMETER_Gy_data | PGW--OCS | DIAMETER + interface + pdn_class | The Gy interface is used for online charging between the OCS and the PDN Gateway (PGW), this procedure is specific to data APN(pdn class). Messages |
DIAMETER_Gy_ims | PGW--OCS | DIAMETER + interface + pdn_class | The Gy interface is used for online charging between the OCS and the PDN Gateway (PGW), this procedure is specific to IMS APN(pdn class). Messages |
DIAMETER_Rf_ims | TAS--OFCS | DIAMETER + interface + pdn_class | The Rf reference point is located between the Charging Trigger Function (CTF) and the Offline Charging Data System (OFCS), and is used for the transport of charging events. The Rf interface is between the OCS and the IMS Call Session Control Function (CSCF) , this procedure is specific to IMSAPN(pdn class). Messages |
DIAMETER_Ro_ims | TAS--OCS | DIAMETER + interface + pdn_class | The Ro interface is between the OCS and the IMS Call Session Control Function (CSCF) , this procedure is specific to IMS APN (pdn class). Messages |
DIAMETER_Rx_ims | PCSCF--PCRF | DIAMETER + interface + pdn_class | The Rx reference point is between the Policy and Charging Rules Function (PCRF) and the Call Session Control Function (CSCF), and is used to exchange application level session information between the CSCF application functions. The application function information is part of the input used by the PCRF for the Policy and Charging Control (PCC) decisions, this procedure is specific to IMS APN (pdn class). Messages |
DIAMETER_S6a/S6d | MME--HSS | DIAMETER + interface + pdn_class | The S6a reference point is between the Home Subscriber Server (HSS) and the Mobility Management Entity (MME), and is used for location changes of the MME. The S6d interface is between the HSS and the Serving GPRS Service Node (SGSN), for location changes of the SGSN. The procedures, message parameters and protocol are similar between S6a and S6d. Messages |
DIAMETER_S6b_ims | PGW--AAA | DIAMETER + interface + pdn_class | The S6b reference point is between the PDN Gateway (PGW) and 3GPP AAA server/proxy for mobility related authentication if needed. This reference point may also be used to retrieve and request storage of mobility parameters, and may also be used to retrieve static QoS profile for a UE for non-3GPP access in case dynamic PCC is not supported, this procedure is specific to IMS APN (pdn class). Messages |
DIAMETER_Sh_ims | TAS--HSS | DIAMETER + interface + pdn_class | The Sh reference point resides between the Home Subscriber Server (HSS) and an Application Function (AF). The Sh interface implements a Diameter application that allows the download and update of transparent and not-transparent user data, and allows requests and notifications on changes to user data, this procedure is specific to IMS APN (pdn class). Messages |
DIAMETER_Sp_ims | PCRF--SPR | DIAMETER + interface + pdn_class | This interface allows the PCRF to request subscription information related to transport level policies from the SPR based on a subscriber ID, a PDN identifier and possible further IP CAN session attributes, as specified in 3GPP TS 23.203 v9.x. This interface allows the SPR to notify the PCRF when the subscription information has been changed if the PCRF has requested such notifications. The SPR shall stop sending the updated subscription information when a cancellation notification request has been received from the PCRF. PCRF queries the Subscriber Profile Repository(SPR) for dynamic information of subscriber over Sp interface. SPR sends all information about the subscriber policy/quota/rules to PCRF over Sp interface, this procedure is specific to IMS APN (pdn class). |
DIAMETER_SWx_ims | HSS--AAA | DIAMETER + interface + pdn_class | The SWx reference point are located between 3GPP AAA Server and HSS and is used for transport of authentication, subscription and PDN connection related data. The SWx interface is used for 3GPP LTE networks, this procedure is specific to IMS APN (pdn class). Messages |
DIAMETER_Sy | PCRF--OCS | DIAMETER + interface + pdn_class | The Sy reference point is located between the Policy and Charging Rules Function (PCRF) and the Online Charging System (OCS). The Sy reference point enables transfer of policy counter status information relating to subscriber spending from the OCS to the PCRF. Messages |
GTPv2
GTPv2 (GPRS Tunneling Protocol version 2) is a protocol used in mobile networks, particularly in the packet core network. It facilitates the communication between different network elements, such as between the Serving Gateway (SGW) and the PDN Gateway (PGW) in LTE (Long-Term Evolution) networks.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
GTPv2_Setup_data_apn | MME--SGW--PGW(S11/S5/S8) | GTPv2 + interface + pdn_class | Indicates GTPv2 procedures for data APN-based connections. The S11 reference point is between the MME and SGW and is used to support mobility and bearer management between the MME and S-GW. GTP-U (GPRS Tunnel Protocol User) tunnels are used between two entities of the EPS network. Such tunnels enable the traffic data to be compartmentalized. GTP-U traffic tunnels are constructed on the S1-U, S5 and X2 interfaces. The tunnel is identified by the TEID parameter, the IP addresses and the UDP port numbers. The entity receiving the traffic or signaling data determines the value of the TEID parameter which the sending entity has to use. The TEID parameter used for the signaling exchanged over the S5 interface is unique. The same parameter is used for all signaling messages relating to the activation of the various S5 bearers for the different mobiles. The TEID parameter used for the signaling exchanged over S11 interface is unique for each mobile. The same parameter is used for all signaling messages relating to the establishment of the various S1-U bearers for the same mobile. Bearer Management: The signaling bearer related to a mobile is created by the CREATE SESSION REQUEST message. It is reinforced by the use of a TEID parameter. The message is transmitted:
The SGW entity (or respectively PGW entity) responds to the MME entity (or respectively SGW entity) with the CREATE SESSION RESPONSE message. The MME entity may respond with the DOWNLINK DATA NOTIFICATION ACKNOWLEDGE message, indicating whether or not the request is accepted or with the DOWNLINK DATA NOTIFICATION FAILURE INDICATION message if the mobile does not respond to the paging or if the mobile service request is rejected. Mobility Management: Mobility management messages are exchanged between the source and target MME entities, when the handover of the mobile imposes a switch of MME entity. The new MME entity sends the CONTEXT REQUEST message to the former one in the procedure of TAI updating, to retrieve information about the context of the mobile. |
GTPv2_Setup_ims_apn | MME--SGW--PGW(S11/S5/S8) | GTPv2 + interface + pdn_class | Indicates GTPv2 procedures for IMS APN based connections. The S11 reference point is between the MME and SGW and is used to support mobility and bearer management between the MME and S-GW. GTP-U (GPRS Tunnel Protocol User) tunnels are used between two entities of the EPS network. Such tunnels enable the traffic data to be compartmentalized. GTP-U traffic tunnels are constructed on the S1-U, S5 and X2 interfaces. The tunnel is identified by the TEID parameter, the IP addresses and the UDP port numbers. The entity receiving the traffic or signaling data determines the value of the TEID parameter which the sending entity has to use. The TEID parameter used for the signaling exchanged over the S5 interface is unique. The same parameter is used for all signaling messages relating to the activation of the various S5 bearers for the different mobiles. The TEID parameter used for the signaling exchanged over S11 interface is unique for each mobile. The same parameter is used for all signaling messages relating to the establishment of the various S1-U bearers for the same mobile. Bearer Management: The signaling bearer related to a mobile is created by the CREATE SESSION REQUEST message. It is reinforced by the use of a TEID parameter. The message is transmitted:
The SGW entity (or respectively PGW entity) responds to the MME entity (or respectively SGW entity) with the CREATE SESSION RESPONSE message. The MME entity may respond with the DOWNLINK DATA NOTIFICATION ACKNOWLEDGE message, indicating whether or not the request is accepted or with the DOWNLINK DATA NOTIFICATION FAILURE INDICATION message if the mobile does not respond to the paging or if the mobile service request is rejected. Mobility Management: Mobility management messages are exchanged between the source and target MME entities, when the handover of the mobile imposes a switch of MME entity. The new MME entity sends the CONTEXT REQUEST message to the former one in the procedure of TAI updating, to retrieve information about the context of the mobile. |
GTPv2_Setup_sos_apn | MME--SGW--PGW(S11/S5/S8) | GTPv2 + interface + pdn_class | Indicates GTPv2 procedures for SOS APN based connections which are related with emergency calls. The S11 reference point is between the MME and SGW and is used to support mobility and bearer management between the MME and S-GW. GTP-U (GPRS Tunnel Protocol User) tunnels are used between two entities of the EPS network. Such tunnels enable the traffic data to be compartmentalized. GTP-U traffic tunnels are constructed on the S1-U, S5 and X2 interfaces. The tunnel is identified by the TEID parameter, the IP addresses and the UDP port numbers. The entity receiving the traffic or signaling data determines the value of the TEID parameter which the sending entity has to use. The TEID parameter used for the signaling exchanged over the S5 interface is unique. The same parameter is used for all signaling messages relating to the activation of the various S5 bearers for the different mobiles. The TEID parameter used for the signaling exchanged over S11 interface is unique for each mobile. The same parameter is used for all signaling messages relating to the establishment of the various S1-U bearers for the same mobile. Bearer Management: The signaling bearer related to a mobile is created by the CREATE SESSION REQUEST message. It is reinforced by the use of a TEID parameter. The message is transmitted:
The SGW entity (or respectively PGW entity) responds to the MME entity (or respectively SGW entity) with the CREATE SESSION RESPONSE message. The MME entity may respond with the DOWNLINK DATA NOTIFICATION ACKNOWLEDGE message, indicating whether or not the request is accepted or with the DOWNLINK DATA NOTIFICATION FAILURE INDICATION message if the mobile does not respond to the paging or if the mobile service request is rejected. Mobility Management: Mobility management messages are exchanged between the source and target MME entities, when the handover of the mobile imposes a switch of MME entity. The new MME entity sends the CONTEXT REQUEST message to the former one in the procedure of TAI updating, to retrieve information about the context of the mobile. |
GTPv2_Setup_UNKNOWN_apn | MME--SGW--PGW(S11/S5/S8) | GTPv2 + interface + pdn_class | Indicates GTPv2 procedures where there is no specific APN such as data/IMS/SOS found(unknown). The S11 reference point is between the MME and SGW and is used to support mobility and bearer management between the MME and S-GW. GTP-U (GPRS Tunnel Protocol User) tunnels are used between two entities of the EPS network. Such tunnels enable the traffic data to be compartmentalized. GTP-U traffic tunnels are constructed on the S1-U, S5 and X2 interfaces. The tunnel is identified by the TEID parameter, the IP addresses and the UDP port numbers. The entity receiving the traffic or signaling data determines the value of the TEID parameter which the sending entity has to use. The TEID parameter used for the signaling exchanged over the S5 interface is unique. The same parameter is used for all signaling messages relating to the activation of the various S5 bearers for the different mobiles. The TEID parameter used for the signaling exchanged over S11 interface is unique for each mobile. The same parameter is used for all signaling messages relating to the establishment of the various S1-U bearers for the same mobile. Bearer Management: The signaling bearer related to a mobile is created by the CREATE SESSION REQUEST message. It is reinforced by the use of a TEID parameter. The message is transmitted:
The SGW entity (or respectively PGW entity) responds to the MME entity (or respectively SGW entity) with the CREATE SESSION RESPONSE message. The MME entity may respond with the DOWNLINK DATA NOTIFICATION ACKNOWLEDGE message, indicating whether or not the request is accepted or with the DOWNLINK DATA NOTIFICATION FAILURE INDICATION message if the mobile does not respond to the paging or if the mobile service request is rejected. Mobility Management: Mobility management messages are exchanged between the source and target MME entities, when the handover of the mobile imposes a switch of MME entity. The new MME entity sends the CONTEXT REQUEST message to the former one in the procedure of TAI updating, to retrieve information about the context of the mobile. |
HTTP2
HTTP2 is the second major version of the Hypertext Transfer Protocol, used for communication on the World Wide Web. It is designed to improve efficiency and performance by introducing features such as multiplexing and header compression.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
HTTP2_namf | AMF | HTTP2 + interface + dnn | AMF Services and AMF Service Operations. Access and mobility management function (AMF) supports registration, connection, reachability, and mobility management. Provides a channel for exchanging session management messages between a UE and the SMF, and serves as the access point on the control plane of the core network for UEs and (R)AN. Reference : 3GPP TS 23.502 Namf_Communication
Namf_Communication
Namf_Communication
Namf_EventExposure
|
HTTP2_namf_data | AMF | HTTP2 + interface + dnn | AMF Services and AMF Service Operations with data DNN. Access and mobility management function (AMF) supports registration, connection, reachability, and mobility management. Provides a channel for exchanging session management messages between a UE and the SMF, and serves as the access point on the control plane of the core network for UEs and (R)AN. Reference : 3GPP TS 23.502 Namf_Communication
Namf_Communication
Namf_Communication
Namf_EventExposure
|
HTTP2_namf_ims | AMF | HTTP2 + interface + dnn | AMF Services and AMF Service Operations with IMS DNN. Access and mobility management function (AMF) supports registration, connection, reachability, and mobility management. Provides a channel for exchanging session management messages between a UE and the SMF, and serves as the access point on the control plane of the core network for UEs and (R)AN. Reference : 3GPP TS 23.502 Namf_Communication
Namf_Communication
Namf_Communication
Namf_EventExposure
|
HTTP2_nausf | AUSF | HTTP2 + interface + dnn | AUSF Services. Reference : 3GPP TS 23.502 Nausf_UEAuthentication |
HTTP2_nbsf | BSF | HTTP2 + interface + dnn | BSF Services and Service Operations. Reference : 3GPP TS 23.502 Binding Support Function (BSF) offers services to PCFs to register and deregister information about data sessions, and services to other applications to query the BSF which PCF that serves a specific data session. For voice services the Application Function (AF) is the IMS P-CSCF. The concept is not very complicated but is a very important function in order to connect the IMS and the 5GC domains when multiple Network Functions are deployed. The Nbsf provides the Nbsf_Management_Register, the Nbsf_Management_Deregister and the Nbsf_Management_Discovery services, the Nbsf_Management_Update, the Nbsf_Management_Subscribe, the Nbsf_Management_Unsubscribe and the Nbsf_Management_Notify operations. |
HTTP2_nbsf_data | BSF | HTTP2 + interface + dnn | BSF Services and Service Operations related with data DNN. Reference : 3GPP TS 23.502 Binding Support Function (BSF) offers services to PCFs to register and deregister information about data sessions, and services to other applications to query the BSF which PCF that serves a specific data session. For voice services the Application Function (AF) is the IMS P-CSCF. The concept is not very complicated but is a very important function in order to connect the IMS and the 5GC domains when multiple Network Functions are deployed. The Nbsf provides the Nbsf_Management_Register, the Nbsf_Management_Deregister and the Nbsf_Management_Discovery services, the Nbsf_Management_Update, the Nbsf_Management_Subscribe, the Nbsf_Management_Unsubscribe and the Nbsf_Management_Notify operations. |
HTTP2_nbsf_ims | BSF | HTTP2 + interface + dnn | BSF Services and Service Operations related with IMS DNN. Reference : 3GPP TS 23.502 Binding Support Function (BSF) offers services to PCFs to register and deregister information about data sessions, and services to other applications to query the BSF which PCF that serves a specific data session. For voice services the Application Function (AF) is the IMS P-CSCF. The concept is not very complicated but is a very important function in order to connect the IMS and the 5GC domains when multiple Network Functions are deployed. The Nbsf provides the Nbsf_Management_Register, the Nbsf_Management_Deregister and the Nbsf_Management_Discovery services, the Nbsf_Management_Update, the Nbsf_Management_Subscribe, the Nbsf_Management_Unsubscribe and the Nbsf_Management_Notify operations. |
HTTP2_nchf | CHF | HTTP2 + interface + dnn | CHF Services. Reference : 3GPP TS 23.502 Charging support in the 5GC architecture is provided through the Charging Function (CHF), which interacts with PCF and SMF to provide support for charging services. The CHF may authorize access to individual ser- vices or to a group of services by granting credits for authorized traffic. If a user is not authorized to access a certain service, then the CHF may deny credit requests and addi- tionally instruct the SMF to redirect the service request to a specified destination. The Nchf_SpendingLimitControl service exposed by CHF and consumed by the PCF is specified in 3GPP TS 23.502. Nchf_SpendingLimitControl_Subscribe : Subscribe to notification of changes in the status of the policy counters available at the CHF and retrieval Nchf_SpendingLimitControl_Unsubscribe : Cancel the subscription to status changes for all the policy counters available at the CHF. Nchf_SpendingLimitControl_Notify : Notify the change of the status of the subscribed policy counters available at the CHF. Alternatively, it can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Alternatively, it is also used by the CHF to notify the removal of a subscriber from the CHF system, so that the NF consumer can terminate the subscriptions of all the policy counters of the subscriber. |
HTTP2_nchf_data | CHF | HTTP2 + interface + dnn | CHF Services with data DNN class. Reference : 3GPP TS 23.502 Charging support in the 5GC architecture is provided through the Charging Function (CHF), which interacts with PCF and SMF to provide support for charging services. The CHF may authorize access to individual ser- vices or to a group of services by granting credits for authorized traffic. If a user is not authorized to access a certain service, then the CHF may deny credit requests and additionally instruct the SMF to redirect the service request to a specified destination. The Nchf_SpendingLimitControl service exposed by CHF and consumed by the PCF is specified in 3GPP TS 23.502. Nchf_SpendingLimitControl_Subscribe : Subscribe to notification of changes in the status of the policy counters available at the CHF and retrieval Nchf_SpendingLimitControl_Unsubscribe : Cancel the subscription to status changes for all the policy counters available at the CHF. Nchf_SpendingLimitControl_Notify : Notify the change of the status of the subscribed policy counters available at the CHF. Alternatively, it can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Alternatively, it is also used by the CHF to notify the removal of a subscriber from the CHF system, so that the NF consumer can terminate the subscriptions of all the policy counters of the subscriber. |
HTTP2_nchf_ims | CHF | HTTP2 + interface + dnn | CHF Services with IMS DNN class. Reference : 3GPP TS 23.502 Charging support in the 5GC architecture is provided through the Charging Function (CHF), which interacts with PCF and SMF to provide support for charging services. The CHF may authorize access to individual ser- vices or to a group of services by granting credits for authorized traffic. If a user is not authorized to access a certain service, then the CHF may deny credit requests and additionally instruct the SMF to redirect the service request to a specified destination. The Nchf_SpendingLimitControl service exposed by CHF and consumed by the PCF is specified in 3GPP TS 23.502. Nchf_SpendingLimitControl_Subscribe : Subscribe to notification of changes in the status of the policy counters available at the CHF and retrieval Nchf_SpendingLimitControl_Unsubscribe : Cancel the subscription to status changes for all the policy counters available at the CHF. Nchf_SpendingLimitControl_Notify : Notify the change of the status of the subscribed policy counters available at the CHF. Alternatively, it can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Alternatively, it is also used by the CHF to notify the removal of a subscriber from the CHF system, so that the NF consumer can terminate the subscriptions of all the policy counters of the subscriber. |
HTTP2_nnrf | NRF | HTTP2 + interface + dnn | NRF Services and Service Operations. Reference : 3GPP TS 23.502 Network repository function (NRF) Provides a new function for registration and discovery. It enables NFs to discover and communicate with each other through APIs. Nnrf_NFManagement service: This service enables one NF to manage its NF profile in NRF (i.e. register, update, deregister). This service also allows a consumer NF or SCP to subscribe in NRF to receive notifications regarding changes in the NF profile of other NFs. Nnrf_NFDiscovery service: This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF. Nnrf_AccessToken_service: This service provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501 [15]. Nnrf_Bootstrapping service: The Nnrf_Bootstrapping service lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set, by using a version- independent URI endpoint that does not need to be discovered by using a Discovery service |
HTTP2_nnrf_data | NRF | HTTP2 + interface + dnn | NRF Services and Service Operations with data DNN class. Reference : 3GPP TS 23.502 Nnrf_NFManagement service: This service enables one NF to manage its NF profile in NRF (i.e. register, update, deregister). This service also allows a consumer NF or SCP to subscribe in NRF to receive notifications regarding changes in the NF profile of other NFs. Nnrf_NFDiscovery service: This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF. Nnrf_AccessToken_service: This service provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501 [15]. Nnrf_Bootstrapping service: The Nnrf_Bootstrapping service lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set, by using a version- independent URI endpoint that does not need to be discovered by using a Discovery service |
HTTP2_nnrf_ims | NRF | HTTP2 + interface + dnn | NRF Services and Service Operations with ims dnn class. Reference : 3GPP TS 23.502 Nnrf_NFManagement service: This service enables one NF to manage its NF profile in NRF (i.e. register, update, deregister). This service also allows a consumer NF or SCP to subscribe in NRF to receive notifications regarding changes in the NF profile of other NFs. Nnrf_NFDiscovery service: This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF. Nnrf_AccessToken_service: This service provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501 [15]. Nnrf_Bootstrapping service: The Nnrf_Bootstrapping service lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set, by using a version- independent URI endpoint that does not need to be discovered by using a Discovery service |
HTTP2_npcf | PCF | HTTP2 + interface + dnn | PCF Services. Policy control function (PCF) Provides a unified policy framework and policy rules for control plane functions. Reference : 3GPP TS 23.502 Npcf_AMPolicyControl service: NF Service Consumer, e.g. AMF, can create and manage an AM Policy Association in the PCF through which the NF Service Consumer receives access and mobility related policy information for a UE identified by a SUPI. Npcf_SMPolicyControl service: NF Service Consumer, e.g. SMF, can create and manage a SM Policy Association in the PCF through which the NF Service Consumer receives policy information for a PDU Session.
Npcf_PolicyAuthorization Service: This service is to authorise an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. Additionally, this service allows an AF or TSCTSF to exchange port management information with DS-TT and NW-TT. This service allows the NF consumer to subscribe/unsubscribe the notification of events, which are defined in clause 6.1.3.18 of TS 23.503 [20]. Npcf_BDTPolicyControl Service: This service provides background data transfer policy, which includes the following functionalities:
Npcf_UEPolicyControl Service: NF Service Consumer, e.g. AMF, may create and manage a UE Policy Association in the PCF through which the NF Service Consumer receives Policy Control Request Trigger of UE Policy Association. Npcf_EventExposure service: This service enables an NF to subscribe and get notified about PCF events for a group of UE(s) or any UE accessing a combination of (DNN, S-NSSAI). Npcf_AMPolicyAuthorization Service: This service is to authorise an AF request and potentially create or change access and mobility management policies of a UE based on the request of the authorized AF or TSCTSF. This service allows the NF consumer to subscribe/unsubscribe the notification of events for related to a user (i.e. a SUPI) that has an AM or UE Policy Association established, or both, the list of events are defined in clause 6.1.3.18 of TS 23.503 [20]. |
HTTP2_npcf_data | PCF | HTTP2 + interface + dnn | PCF Services with data DNN. Policy control function (PCF) Provides a unified policy framework and policy rules for control plane functions. Reference : 3GPP TS 23.502 Npcf_AMPolicyControl service: NF Service Consumer, e.g. AMF, can create and manage an AM Policy Association in the PCF through which the NF Service Consumer receives access and mobility related policy information for a UE identified by a SUPI. Npcf_SMPolicyControl service: NF Service Consumer, e.g. SMF, can create and manage a SM Policy Association in the PCF through which the NF Service Consumer receives policy information for a PDU Session.
Npcf_PolicyAuthorization Service: This service is to authorize an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. Additionally, this service allows an AF or TSCTSF to exchange port management information with DS-TT and NW-TT. This service allows the NF consumer to subscribe/unsubscribe the notification of events, which are defined in clause 6.1.3.18 of TS 23.503 [20]. Npcf_BDTPolicyControl Service: This service provides background data transfer policy, which includes the following functionalities:
Npcf_UEPolicyControl Service: NF Service Consumer, e.g. AMF, may create and manage a UE Policy Association in the PCF through which the NF Service Consumer receives Policy Control Request Trigger of UE Policy Association. Npcf_EventExposure service: This service enables an NF to subscribe and get notified about PCF events for a group of UE(s) or any UE accessing a combination of (DNN, S-NSSAI). Npcf_AMPolicyAuthorization Service: This service is to authorize an AF request and potentially create or change access and mobility management policies of a UE based on the request of the authorized AF or TSCTSF. This service allows the NF consumer to subscribe/unsubscribe the notification of events for related to a user (i.e. a SUPI) that has an AM or UE Policy Association established, or both, the list of events are defined in clause 6.1.3.18 of TS 23.503 [20]. |
HTTP2_npcf_ims | PCF | HTTP2 + interface + dnn | PCF Services with IMS DNN. Policy control function (PCF) Provides a unified policy framework and policy rules for control plane functions. Reference : 3GPP TS 23.502 Npcf_AMPolicyControl service: NF Service Consumer, e.g. AMF, can create and manage an AM Policy Association in the PCF through which the NF Service Consumer receives access and mobility related policy information for a UE identified by a SUPI. Npcf_SMPolicyControl service: NF Service Consumer, e.g. SMF, can create and manage a SM Policy Association in the PCF through which the NF Service Consumer receives policy information for a PDU Session.
Npcf_PolicyAuthorization service: This service is to authorize an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. Additionally, this service allows an AF or TSCTSF to exchange port management information with DS-TT and NW-TT. This service allows the NF consumer to subscribe/unsubscribe the notification of events, which are defined in clause 6.1.3.18 of TS 23.503 [20]. Npcf_BDTPolicyControl service: This service provides background data transfer policy, which includes the following functionalities:
Npcf_UEPolicyControl service: NF Service Consumer, e.g. AMF, may create and manage a UE Policy Association in the PCF through which the NF Service Consumer receives Policy Control Request Trigger of UE Policy Association. Npcf_EventExposure service: This service enables an NF to subscribe and get notified about PCF events for a group of UE(s) or any UE accessing a combination of (DNN, S-NSSAI). Npcf_AMPolicyAuthorization service: This service is to authorize an AF request and potentially create or change access and mobility management policies of a UE based on the request of the authorized AF or TSCTSF. This service allows the NF consumer to subscribe/unsubscribe the notification of events for related to a user (i.e. a SUPI) that has an AM or UE Policy Association established, or both, the list of events are defined in clause 6.1.3.18 of TS 23.503 [20]. |
HTTP2_nsmf_data | SMF | HTTP2 + interface + dnn | SMF Services and SMF Service Operations with data DNN. Session management function (SMF) provides the session management, tunnel maintenance, IP address allocation and management, UP function selection, policy enforcement, QoS control, charging data collection, roaming, and other functions. Reference : 3GPP TS 23.502 Nsmf_PDUSession service: This service operates on the PDU Sessions. The following are the key functionalities of this NF service:
Nsmf_PDUSession_Create service operation: Create a new PDU Session in the H-SMF or SMF or create an association with an existing PDN Nsmf_PDUSession_Update service operation: Update the established PDU Session. Nsmf_PDUSession_Release service operation: It causes the immediate and unconditional deletion of the resources associated with the PDU Session. This service operation is used by V-SMF to request the H-SMF or used by I-SMF to request the SMF to release the resources related to a PDU Session for the serving network initiated PDU release case (e.g. implicit De-registration of UE in the serving network). Nsmf_PDUSession_CreateSMContext service operation: It creates an AMF-SMF association to support a PDU Session. Nsmf_PDUSession_UpdateSMContext service operation: It allows to update the AMF-SMF association to support a PDU Session and/or to provide SMF with N1/N2 SM information received from the UE or from the AN, or allows to establish forwarding tunnel between UPFs controlled by different SMFs (e.g. by UPF controlled by old I-SMF and UPF controlled by new I-SMF). Nsmf_PDUSession_ReleaseSMContext service operation: It allows to release the AMF-SMF association for a certain PDU Session because the PDU Session has been released. Nsmf_PDUSession_SMContextStatusNotify service operation: This service operation is used by the SMF to notify its consumers about the status of an SM context related to a PDU Session (e.g. PDU Session Release due to local reasons within the SMF, PDU Session handover to a different system or access type, SMF context transfer, triggering I-SMF selection for the PDU Session). The SMF may use this service operation to update the SMF derived CN assisted RAN parameters tuning in the AMF. The SMF may report the DDN Failure with NEF Correlation ID to the AMF. Nsmf_PDUSession_StatusNotify service operation: This service operation is used by the SMF to notify its consumers about the status of a PDU Session (e.g. PDU Session is released due to local reasons within the H-SMF, PDU Session handover to a different system or access type, triggering I-SMF reselection for the PDU Session). Nsmf_PDUSession_ContextPush service operation: This service operation is used by the SMF as Service Consumer to push one SM Context to a another SMF as NF Service Producer. It may be triggered by OAM. Nsmf_PDUSession_SendMOData service operation: When the AMF has received MO Small Data from the UE in NAS procedure, this service operation allows the AMF to send the MO Small Data to the SMF. Nsmf_PDUSession_TransferMOData service operation: When the V-SMF/I-SMF has received MO Small Data from AMF, this service operation allows the V-SMF/I-SMF to forward the MO Small Data to the (H-)SMF. Nsmf_PDUSession_TransferMTData service operation: When the (H-)SMF has received MT Small Data from the NEF, this service operation allows the (H- )SMF to send the MT Small Data to the V-SMF/I-SMF. Nsmf_EventExposure Service: This service provides events related to PDU Sessions towards consumer NF. The service operations exposed by this service allow other NFs to subscribe and get notified of events happening on PDU Sessions. The following are the key functionalities of this NF service.
Nsmf_EventExposure_Notify service operation: Report UE PDU Session related event(s) to the NF which has subscribed to the event report service. Nsmf_EventExposure_AppRelocationInfo service operation: Acknowledge the notification from the SMF regarding UE PDU Session related event(s). Nsmf_EventExposure_Subscribe service operation: This service operation is used by an NF to subscribe or modify a subscription for event notifications on a specified PDU Session or for all PDU Sessions of one UE, group of UE(s) or any UE. Nsmf_EventExposure_UnSubscribe service operation: This service operation is used by an NF to unsubscribe event notifications. Nsmf_PDUSession_ContextRequest service operation: This service operation is used by the NF Consumer to request for SM Context (e.g. during EPS IWK, HO, SM Context transfer indication), or during mobility procedure with I-SMF (or V-SMF) changes or may be triggered by OAM. |
HTTP2_nsmf_ims | SMF | HTTP2 + interface + dnn | SMF Services and SMF Service Operations with IMS DNN. Session management function (SMF) provides the session management, tunnel maintenance, IP address allocation and management, UP function selection, policy enforcement, QoS control, charging data collection, roaming, and other functions. Reference : 3GPP TS 23.502 Nsmf_PDUSession service: This service operates on the PDU Sessions. The following are the key functionalities of this NF service:
Nsmf_PDUSession_Create service operation: Create a new PDU Session in the H-SMF or SMF or create an association with an existing PDN Nsmf_PDUSession_Update service operation: Update the established PDU Session. Nsmf_PDUSession_Release service operation: It causes the immediate and unconditional deletion of the resources associated with the PDU Session. This service operation is used by V-SMF to request the H-SMF or used by I-SMF to request the SMF to release the resources related to a PDU Session for the serving network initiated PDU release case (e.g. implicit De-registration of UE in the serving network). Nsmf_PDUSession_CreateSMContext service operation: It creates an AMF-SMF association to support a PDU Session. Nsmf_PDUSession_UpdateSMContext service operation: It allows to update the AMF-SMF association to support a PDU Session and/or to provide SMF with N1/N2 SM information received from the UE or from the AN, or allows to establish forwarding tunnel between UPFs controlled by different SMFs (e.g. by UPF controlled by old I-SMF and UPF controlled by new I-SMF). Nsmf_PDUSession_ReleaseSMContext service operation: It allows to release the AMF-SMF association for a certain PDU Session because the PDU Session has been released. Nsmf_PDUSession_SMContextStatusNotify service operation: This service operation is used by the SMF to notify its consumers about the status of an SM context related to a PDU Session (e.g. PDU Session Release due to local reasons within the SMF, PDU Session handover to a different system or access type, SMF context transfer, triggering I-SMF selection for the PDU Session). The SMF may use this service operation to update the SMF derived CN assisted RAN parameters tuning in the AMF. The SMF may report the DDN Failure with NEF Correlation ID to the AMF. Nsmf_PDUSession_StatusNotify service operation: This service operation is used by the SMF to notify its consumers about the status of a PDU Session (e.g. PDU Session is released due to local reasons within the H-SMF, PDU Session handover to a different system or access type, triggering I-SMF reselection for the PDU Session). Nsmf_PDUSession_ContextPush service operation: This service operation is used by the SMF as Service Consumer to push one SM Context to a another SMF as NF Service Producer. It may be triggered by OAM. Nsmf_PDUSession_SendMOData service operation: When the AMF has received MO Small Data from the UE in NAS procedure, this service operation allows the AMF to send the MO Small Data to the SMF. Nsmf_PDUSession_TransferMOData service operation: When the V-SMF/I-SMF has received MO Small Data from AMF, this service operation allows the V-SMF/I-SMF to forward the MO Small Data to the (H-)SMF. Nsmf_PDUSession_TransferMTData service operation: When the (H-)SMF has received MT Small Data from the NEF, this service operation allows the (H- )SMF to send the MT Small Data to the V-SMF/I-SMF. Nsmf_EventExposure service: This service provides events related to PDU Sessions towards consumer NF. The service operations exposed by this service allow other NFs to subscribe and get notified of events happening on PDU Sessions. The following are the key functionalities of this NF service.
Nsmf_EventExposure_Notify service operation: Report UE PDU Session related event(s) to the NF which has subscribed to the event report service. Nsmf_EventExposure_AppRelocationInfo service operation: Acknowledge the notification from the SMF regarding UE PDU Session related event(s). Nsmf_EventExposure_Subscribe service operation: This service operation is used by an NF to subscribe or modify a subscription for event notifications on a specified PDU Session or for all PDU Sessions of one UE, group of UE(s) or any UE. Nsmf_EventExposure_UnSubscribe service operation: This service operation is used by an NF to unsubscribe event notifications. Nsmf_PDUSession_ContextRequest service operation: This service operation is used by the NF Consumer to request for SM Context (e.g. during EPS IWK, HO, SM Context transfer indication), or during mobility procedure with I-SMF (or V-SMF) changes or may be triggered by OAM. |
HTTP2_nsmsf | SMF | HTTP2 + interface + dnn | SMSF Services. The SMSF(Short Message Service Function) is an optional Network Function that is only deployed for enabling SMS over NAS services. Just as other Control Plane network functions in the 5G architecture, the SMSF exposes a service-based interface relying on HTTP communication, called Nsmsf. It connects with the AMF and the UDM Network Functions within the 5G Core architecture. The SMSF checks subscription data through interacting with the UDM, generates charging records and forwards SMS messages between the AMF and the SMS networks external to the 5G Core architecture. Reference : 3GPP TS 23.502 This service allows AMF to authorize SMS and activate SMS for the served user on SMSF. This service allows downlink SMS message transmit from consumer NF to SMSF. |
HTTP2_nudm | UDM | HTTP2 + interface + dnn | UDM Services and Service Operations. Unified data management (UDM) Provides unified data management, 3GPP AKA authentication, user identification, access authorization, registration, mobility, subscription, and SMS management. Reference : 3GPP TS 23.502 Nudm_SubscriberDataManagement (SDM) service: Subscription data types used in the Nudm_SubscriberDataManagement service are:
Nudm_UEAuthentication Service : This service is used by the requester NF to get authentication data and provide UDM with the result of the authentication procedure success. In the case of SNPN, this service may be used to instruct the AUSF to execute authentication towards AAA-S. Nudm_EventExposure service : The NF consumer subscribes to receive an event, deletes the subscription of an event if already defined in UDM, UDM reports the event to the consumer that has previously subscribed or The NF consumer requests to modify an existing subscription to event notifications. Nudm_ParameterProvision service : This service is for allowing NEF to provision of information which can be used for the UE in 5GS. Nudm_NIDDAuthorisation service : The consumer requests authorisation for NIDD Configuration or is used for the UDM to notify the NIDD Authorization Update to NF consumer. Nudm_ServiceSpecificAuthorisation service : This service is for authorisation of a specific service configuration. Nudm_ReportSMDeliveryStatus service : This service is to report the SM-Delivery Status to UDM. |
HTTP2_nudm_data | UDM | HTTP2 + interface + dnn | UDM Services and Service Operations with data DNN class. Unified data management (UDM) Provides unified data management, 3GPP AKA authentication, user identification, access authorization, registration, mobility, subscription, and SMS management. Reference : 3GPP TS 23.502 Nudm_SubscriberDataManagement (SDM) Service : Subscription data types used in the Nudm_SubscriberDataManagement Service are :
Nudm_UEAuthentication Service : This service is used by the requester NF to get authentication data and provide UDM with the result of the authentication procedure success. In the case of SNPN, this service may be used to instruct the AUSF to execute authentication towards AAA-S. Nudm_EventExposure service : The NF consumer subscribes to receive an event, deletes the subscription of an event if already defined in UDM, UDM reports the event to the consumer that has previously subscribed or The NF consumer requests to modify an existing subscription to event notifications. Nudm_ParameterProvision service : This service is for allowing NEF to provision of information which can be used for the UE in 5GS. Nudm_NIDDAuthorisation service : The consumer requests authorisation for NIDD Configuration or is used for the UDM to notify the NIDD Authorization Update to NF consumer. Nudm_ServiceSpecificAuthorisation service : This service is for authorisation of a specific service configuration. Nudm_ReportSMDeliveryStatus service : This service is to report the SM-Delivery Status to UDM. |
HTTP2_nudm_ims | UDM | HTTP2 + interface + dnn | UDM Services and Service Operations with IMS DNN class. Unified data management (UDM) Provides unified data management, 3GPP AKA authentication, user identification, access authorization, registration, mobility, subscription, and SMS management. Reference : 3GPP TS 23.502 Nudm_SubscriberDataManagement (SDM) Service : Subscription data types used in the Nudm_SubscriberDataManagement Service are:
Nudm_UEAuthentication service: This service is used by the requester NF to get authentication data and provide UDM with the result of the authentication procedure success. In the case of SNPN, this service may be used to instruct the AUSF to execute authentication towards AAA-S. Nudm_EventExposure service: The NF consumer subscribes to receive an event, deletes the subscription of an event if already defined in UDM, UDM reports the event to the consumer that has previously subscribed or The NF consumer requests to modify an existing subscription to event notifications. Nudm_ParameterProvision service : This service is for allowing NEF to provision of information which can be used for the UE in 5GS. Nudm_NIDDAuthorisation service: The consumer requests authorisation for NIDD Configuration or is used for the UDM to notify the NIDD Authorization Update to NF consumer. Nudm_ServiceSpecificAuthorisation service : This service is for authorisation of a specific service configuration. Nudm_ReportSMDeliveryStatus service: This service is to report the SM-Delivery Status to UDM. |
HTTP2_nudr | UDR | HTTP2 + interface + dnn | The Unified Data Repository (UDR) is the database where various types of data are stored. Important data is the subscription data and data defining various types of network or user policies. Usage of UDR to store and access data is offered as services to other network functions, specifically UDM, PCF and NEF. The operations defined for Nudr services are used when NF service consumers request a set of data from UDR, intends to insert a new data record into the UDR, e.g. a NF service consumer intends to insert a new application data record into the UDR, intends to delete user data stored in the UDR, e.g. a NF service consumer intends to delete an application data record, intends to update stored data in the UDR , NF service consumer performs the subscription to notification to data modified in the UDR or NF service consumer performs the un-subscription to notification to data modified in the UDR. Reference : 3GPP TS 23.502 |
HTTP2_nudr_data | UDR | HTTP2 + interface + dnn | The Unified Data Repository (UDR) is the database where various types of data is stored. Important data is of course the subscription data and data defining various types of network or user policies. Usage of UDR to store and access data is offered as services to other network functions, specifically UDM, PCF and NEF. The operations defined for Nudr services are used when NF service consumers request a set of data from UDR, intends to insert a new data record into the UDR, e.g. a NF service consumer intends to insert a new application data record into the UDR, intends to delete user data stored in the UDR, e.g. a NF service consumer intends to delete an application data record, intends to update stored data in the UDR , NF service consumer performs the subscription to notification to data modified in the UDR or NF service consumer performs the un-subscription to notification to data modified in the UDR. These procedures are specific to data DNN class Reference : 3GPP TS 23.502 |
HTTP2_nudr_ims | UDR | HTTP2 + interface + dnn | The Unified Data Repository (UDR) is the database where various types of data is stored. Important data is of course the subscription data and data defining various types of network or user policies. Usage of UDR to store and access data is offered as services to other network functions, specifically UDM, PCF and NEF. The operations defined for Nudr services are used when NF service consumers request a set of data from UDR, intends to insert a new data record into the UDR, e.g. a NF service consumer intends to insert a new application data record into the UDR, intends to delete user data stored in the UDR, e.g. a NF service consumer intends to delete an application data record, intends to update stored data in the UDR , NF service consumer performs the subscription to notification to data modified in the UDR or NF service consumer performs the un-subscription to notification to data modified in the UDR. These procedures are specific to IMS DNN class Reference : 3GPP TS 23.502 |
NAS
NAS (Non-Access Stratum) is a layer in the LTE protocol stack that handles signaling between the User Equipment (UE) and the Evolved NodeB (eNB) in mobile networks. It includes functions related to mobility, security, and session management.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
NAS-5GS_N1 | UE--AMF(N1) | NAS-5GS + interface + dnn | A single N1 NAS signaling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signaling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE. Initial Registration and Setup:
UE Context Release:
Reference : 3GPP TS 23.501 , TS 38.413, TS 38.401 and TS 38.410 |
NAS-5GS_N1_data | UE--AMF(N1) | NAS-5GS + interface + dnn | A single N1 NAS signaling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signaling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE. Initial Registration and Setup:
UE Context Release:
Reference : 3GPP TS 23.501 , TS 38.413, TS 38.401 and TS 38.410 |
NAS-5GS_N1_ims | UE--AMF(N1) | NAS-5GS + interface + dnn | A single N1 NAS signaling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signaling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE. Initial Registration and Setup:
UE Context Release:
Reference : 3GPP TS 23.501 , TS 38.413, TS 38.401 and TS 38.410 |
NAS-5GS_N1_sos | UE--AMF(N1) | NAS-5GS + interface + dnn | A single N1 NAS signaling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signaling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE. Initial Registration and Setup:
UE Context Release:
Reference : 3GPP TS 23.501 , TS 38.413, TS 38.401 and TS 38.410 |
NGAP
NGAP (Next Generation Application Part) is a protocol used in 5G networks for communication between various control plane elements. It plays a role similar to S1AP (used in LTE) and facilitates signaling between different nodes in the 5G architecture.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
NGAP_N2 | RAN--AMF(N2) | NGAP + interface + dnn | The following procedures are defined over N2:
> some information only on some access (such as Mobility Restriction List used only for 3GPP access).
N2 Interface (N2AP): Path Switching and Data Forwarding:
User Plane Function Setup and Release:
UE Radio Capability Information Transfer:
Reference : 3GPP TS 23.501 , TS 38.413, TS 38.401 and TS 38.410 |
NGAP_N2_data | RAN--AMF(N2) | NGAP + interface + dnn | The following procedures are defined over N2:
> some information only on some access (such as Mobility Restriction List used only for 3GPP access).
N2 Interface (N2AP): Path Switching and Data Forwarding:
User Plane Function Setup and Release:
UE Radio Capability Information Transfer:
|
NGAP_N2_ims | RAN--AMF(N2) | NGAP + interface + dnn | The following procedures are defined over N2:
> some information only on some access (such as Mobility Restriction List used only for 3GPP access).
N2 Interface (N2AP): Path Switching and Data Forwarding:
User Plane Function Setup and Release:
UE Radio Capability Information Transfer:
|
NGAP_N2_sos | RAN--AMF(N2) | NGAP + interface + dnn | The following procedures are defined over N2:
> some information only on some access (such as Mobility Restriction List used only for 3GPP access).
N2 Interface (N2AP): Path Switching and Data Forwarding:
User Plane Function Setup and Release:
UE Radio Capability Information Transfer:
|
PFCP
PFCP (Packet Forwarding Control Protocol) is a protocol used in the control plane of the User Plane Function (UPF) in 5G networks. It is responsible for the control of user plane traffic and policies in the 5G architecture.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
PFCP_N4 | SMF--UPF(N4) | PFCP + interface + dnn | In 5G, CUPS was applied from the outset, that is, in Release 15. The equivalent control plane and user plane nodes are Session Management Function (SMF) and User Plane Function (UPF). These are connected via the N4 interface. PFCP is used on this interface. PFCP Node Related Procedures
PFCP Session Related Procedures
Reference : 3GPP TS 29.244 |
PFCP_N4_data | SMF--UPF(N4) | PFCP + interface + dnn | In 5G, CUPS was applied from the outset, that is, in Release 15. The equivalent control plane and user plane nodes are Session Management Function (SMF) and User Plane Function (UPF). These are connected via the N4 interface. PFCP is used on this interface. PFCP Node Related Procedures
PFCP Session Related Procedures
Reference : 3GPP TS 29.244 |
PFCP_N4_ims | SMF--UPF(N4) | PFCP + interface + dnn | In 5G, CUPS was applied from the outset, that is, in Release 15. The equivalent control plane and user plane nodes are Session Management Function (SMF) and User Plane Function (UPF). These are connected via the N4 interface. PFCP is used on this interface. PFCP Node Related Procedures
PFCP Session Related Procedures
Reference : 3GPP TS 29.244 |
S1AP
S1AP (S1 Application Part) is a protocol used in LTE networks for communication between the eNB (Evolved NodeB) and the Mobility Management Entity (MME) during the establishment, maintenance, and release of connections.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
S1AP_EMM | S1-MME/S1-AP | S1AP + nas_eps_category + pdn_class | According to 3GPP TS 24.301 (NAS) There are two types of procedure which can be seen on the NAS layer. EMM (EPS Mobility Management) Procedure. EMM common procedures: An EMM common procedure can always be initiated whilst a NAS signaling connection exists. The procedures belonging to this type are:
Initiated by the NW:
EMM connection management procedures (S1 mode only):
Initiated by the UE/NW:
Initiated by the NW:
ESM (EPS Session Management) procedure : Two types of ESM procedures can be distinguished.
Transaction related procedures
Initiated by the NW:
|
S1AP_ESM | S1-MME/S1-AP | S1AP + nas_eps_category + pdn_class | According to 3GPP TS 24.301 (NAS) There are two types of procedure which can be seen on NAS layer. EMM (EPS Mobility Management) Procedure. EMM common procedures: An EMM common procedure can always be initiated whilst a NAS signalling connection exists.The procedures belonging to this type are:
Initiated by the NW:
EMM connection management procedures (S1 mode only):
Initiated by the UE/NW:
Initiated by the NW:
ESM (EPS Session Management) procedure : Two types of ESM procedures can be distinguished.
Transaction related procedures
Initiated by the NW:
|
S1AP_ESM_data | S1-MME/S1-AP | S1AP + nas_eps_category + pdn_class | According to 3GPP TS 24.301 (NAS) There are two types of procedure which can be seen on NAS layer. EMM (EPS Mobility Management) Procedure. EMM common procedures: An EMM common procedure can always be initiated whilst a NAS signalling connection exists.The procedures belonging to this type are:
Initiated by the NW:
EMM connection management procedures (S1 mode only):
Initiated by the UE/NW:
Initiated by the NW:
ESM (EPS Session Management) procedure : Two types of ESM procedures can be distinguished.
Transaction related procedures
Initiated by the NW:
|
S1AP_ESM_ims | S1-MME/S1-AP | S1AP + nas_eps_category + pdn_class | According to 3GPP TS 24.301 (NAS) There are two types of procedure which can be seen on NAS layer. EMM (EPS Mobility Management) Procedure. EMM common procedures: An EMM common procedure can always be initiated whilst a NAS signalling connection exists.The procedures belonging to this type are:
Initiated by the NW:
EMM connection management procedures (S1 mode only):
Initiated by the UE/NW:
Initiated by the NW:
ESM (EPS Session Management) procedure : Two types of ESM procedures can be distinguished.
Transaction related procedures
Initiated by the NW:
|
S1AP_ESM_sos | S1-MME/S1-AP | S1AP + nas_eps_category + pdn_class | According to 3GPP TS 24.301 (NAS) There are two types of procedure which can be seen on NAS layer. EMM (EPS Mobility Management) Procedure. EMM common procedures: An EMM common procedure can always be initiated whilst a NAS signaling connection exists. The procedures belonging to this type are:
Initiated by the NW:
EMM connection management procedures (S1 mode only):
Initiated by the UE/NW:
Initiated by the NW:
ESM (EPS Session Management) procedure : Two types of ESM procedures can be distinguished.
Transaction related procedures
Initiated by the NW:
|
SIP
SIP (Session Initiation Protocol) is a signaling protocol used for initiating, modifying, and terminating communication sessions, including voice and video calls over IP networks. It is commonly used in VoIP (Voice over Internet Protocol) and multimedia communication applications.
Procedure Name | Interface/NE Name | Structure | Description |
|---|---|---|---|
SIP_Call | UE--P/I/S-CSCF--TAS (Gm-Mw-ISC-Mx-Mr) | SIP + sip_subflow_type | The establishment of the VoLTE session (call) includes the following operations: The initial stages of setting up a VoLTE call are the processes of the initial attach, P-CSCF discovery and creating the default bearer for SIP signaling (by registering with the IMS network and subscribing to a registration event package). The first step in a VoLTE call setup is a SIP INVITE request initiated by the calling UE. Following this step, agreement is made on the media-specific parameters such as codecs (e.g. AMR or WB-AMR). After some RINGING, TRYING and OK messaging, the calling UE may respond with a Provisional ACK (PRACK) method as defined in RFC 3551. The PRACK method is used because ACK cannot safely traverse proxy servers that comply with RFC 3261. The PRACK is also forwarded to the called UE. When the called subscriber answers the call, the called UE will respond with a 200 OK before the RTP (media) messaging begins. Reference : 3GPP TS 24.229 |
SIP_De-Registration | UE--P/I/S-CSCF--HSS (Gm-Mw-Cx) | SIP + sip_subflow_type | The deregistration phase starts when the UA entity transmits a REGISTER message which parameter expires of the header Contact has a zero value.
Reference : 3GPP TS 24.229 |
SIP_Registration | UE--P/I/S-CSCF--HSS (Gm-Mw-Cx) | SIP + sip_subflow_type | After Authentication, Security and UE Capability requests, the network accepts the Attach request and activates the EPS bearer context. Once that has happened and the UE has also established a PDP context, a typical IMS SIP client registration (Figure 4) begins:
Reference : 3GPP TS 24.229 |