Network function handling in the context of inter-management function mobility

A method for a target mobility management entity and a target mobility management entity for executing the method in a core network to communicate network function (NF) utilization information with a source mobility management entity during a change of mobility management entity are disclosed. The method comprises: receiving at least one old NF identifier (ID) from the source mobility management entity that corresponds to an old NF entity serving a user equipment (UE); determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF entity of a same NF type as the old NF entity; and communicating, to the source mobility management entity, information that indicates to the source mobility management entity whether the target mobility management entity uses the at least one old NF ID or uses the at least one new NF ID.

TECHNICAL FIELD

Embodiments presented herein relate to methods, nodes/functions entities, computer and computer program products for a target mobility management function in a core network to communicate network function (NF) utilization information with a source mobility management function during a change of mobility management function.

BACKGROUND

3GPP Technical Specification (TS) 23.502 v 15.1.0 has a mobility registration procedure with access and mobility management function (AMF) change, where the old (sometimes referred to herein as “source”) AMF may include some network function (NF) identifiers (IDs) (such as, by way of non-limiting example, PCF ID, SMSF ID, or the like) that are used by the user equipment (UE) and are provided to the new (sometimes referred to herein as “target”) AMF. The new/target AMF will check if the previously used NFs are still suitable for the UE and if not, new NF IDs may be selected.

FIG. 1illustrates the Registration procedure (TS 23.502 v 15.1.0, FIG. 4.2.2.2.2-1). Step 5 of the Registration procedure is the following:5. [Conditional] old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE Context in AMF (as per Table 5.2.2.2.2-1)).Old AMF responds to the new AMF for the Namf_Communication_UEContextTransfer invocation by including the UE's SUPI and MM Context.If old AMF holds information about established PDU Sessions, the old AMF includes Session Management Function (SMF) information DNN, S-NSSAI(s) and PDU Session ID.If old AMF holds information about active NGAP UE-TNLA bindings to N3IWF, the old AMF includes information about the NGAP UE-TNLA bindings.

Step 16 of the Registration procedure is the following:16. [Optional] new AMF performs a Policy Association Establishment as defined in clause 4.16.1.2. For an Emergency Registration, this step is skipped.If the new AMF contacts the Policy and Charging Function (PCF) identified by the (V−) PCF ID received during inter-AMF mobility in step 5, the new AMF shall include the (V−)PCF ID in the Npcf_AMPolicyControl Get operation. This indication is not included by the AMF during initial registration procedure.If the AMF notifies the Mobility Restrictions (e.g. UE location) to the PCF for adjustment, or if the PCF updates the Mobility Restrictions itself due to some conditions (e.g. application in use, time and date), the PCF shall provide the updated Mobility Restrictions to the AMF.

Step 21 of the Registration procedure is the following:21. [Conditional] old AMF to (V−)PCF: AMF-Initiated Policy Association Termination.If the old AMF previously initiated a Policy Association to the PCF, and the old AMF did not transfer the PCF ID to the new AMF (e.g. new AMF is in different PLMN), the old AMF performs an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2, to delete the association with the PCF.

The AMF establishes the connection/association with PCF (new PCF selected vs PCF re-used) in accordance with the following:

4.16.1 Policy Association Establishment

There are three cases considered for Policy Association Establishment:

1. UE initial registration with the network.

2. The AMF re-allocation without PCF change in handover procedure and registration procedure.

3. The AMF re-allocation with PCF change in handover procedure and registration procedure.

FIG. 2illustrates the AM Policy Association Establishment with new Selected PCF (TS 23.502 v 15.1.0, FIG. 4.16.1.2-1).

4.16.1.2 AM Policy Association Establishment with new Selected PCF. This procedure concerns the following scenarios:

1. UE initial registration with the network.

2. The AMF re-allocation with PCF change in handover procedure and registration procedure.

This procedure concerns both roaming and non-roaming scenarios.

FIG. 3illustrates the Policy Association Establishment with the old PCF (TS 23.502 v 15.1.0, FIG. 4.16.1.3-1).

AM Policy Association Establishment with the Old PCF

The procedure concerns the situation involving AMF relocation without PCF change in handover procedure and registration procedure.

This procedure concerns both roaming and non-roaming scenarios.

FIG. 4illustrates the Registration procedure supporting Short Message Service (SMS) over NAS (TS 23.502 v 15.1.0, FIG. 4.13.3.1-1).

Below is how the AMF manages the connection/association with the SMSF.

4.13.3.2 Deregistration Procedures for SMS over NAS

If the UE indicates to the AMF that the UE no longer wants to send and receive SMS over NAS (e.g., not including “SMS supported” indication in subsequent Registration Request message) or if the AMF considers that the UE is deregistered or the AMF receives a Deregistration Notification from the UDM indicating UE Initial Registration, Subscription Withdrawn or 5GS to EPS Mobility as specified in clause 5.2.3.2.2 of TS 23.502 v 15.1.0, the AMF invokes a Nsmsf_SMService_Deactivate service operation to trigger the release of the UE Context for SMS on SMSF based on local configurations. The AMF may delete or deactivate the stored SMSF address in its UE Context. The SMSF shall invoke a Nudm_UECM_Deregistration (SUPI, NF ID, Access Type) service operation from UDM to trigger the UDM to delete the SMSF address of the UE. The UDM may update the UE context in SMSF in UDR by Nudr_DM_Update (SUPI, Subscription Data, SMS Subscription data, SMSF address). The SMSF also removes the UE Context for SMS, including AMF address.

SUMMARY

There currently exist certain situations when moving from a source mobility management function (e.g., a source AMF) to a target mobility management function (e.g., a target AMF) where it is not defined whether the source AMF should terminate associations with NFs or not. In particular, when some NFs are selected by an AMF during initiation registration or initial PDU session establishment, a long-life connection/association will be created between the AMF and the NFs, such as, by way of non-limiting example, PCF and/or SMSF (SMF change will come in 3GPP rel-16).

During UE mobility and when a new/target AMF is selected, if the old/source AMF does not provide information related to the selected/old NFs, i.e. the PCF ID or SMSF ID to the new/target AMF, then it is clear, at least for the PCF case (SMSF change is not named currently in the TS), that the old/source AMF is responsible for connection/association release.

However, in the situation where the old/source AMF provides information related to the selected NFs, such as providing the PCF ID and/or SMSF ID, for example, the new/target AMF may decide to either 1) re-use the NFs selected by the old/source AMF, or 2) select new NFs to serve the UE and PDU sessions. However, the long-life connection/association handling between the old/source AMF and the NFs is not clearly specified, regardless of whether the NFs are re-used or new NFs are selected.

Certain aspects of the present disclosure and their embodiments provide solutions to the aforementioned or other challenges.

The solution proposes:

1. A mechanism between the new/target AMF and the old/source AMF, during an inter-AMF mobility procedure, to allow the new/target AMF to inform the old/source AMF if the NF (e.g., SMSF, PCF, SMF), which were selected for the UE and PDU session(s) by the old/source AMF, will be re-used or not. The target AMF may make a separate indication for each NF, such that the target AMF may indicate that some NFs are reused, and others are not.

2. If not reused, the old/source AMF is responsible for initiating the release of connection/association of the NFs after being informed by the new/target AMF.

There are, proposed herein, various embodiments that address one or more of the issues disclosed herein.

In one embodiment, a method for a target mobility management function in a core network to communicate network function (NF) utilization information with a source mobility management function during a change of mobility management function is provided. The method includes receiving, by the target mobility management function, at least one old NF identifier (ID) from the source mobility management function that corresponds to an old network function (NF) serving a user equipment (UE). The method further includes determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF of a same NF type as the old NF. The method further includes communicating, by the target mobility management function to the source mobility management function, information that indicates to the source mobility management function whether the target mobility management function uses the at least one old NF ID or uses the at least one new NF ID.

In another embodiment, a target mobility management function node for communicating network function (NF) utilization information with a source mobility management function node during a change of mobility management function is provided. The target mobility management function node includes one or more processors and includes memory storing instructions executable by the one or more processors. The target mobility management function node is operable to perform the method of receiving, by the target mobility management function node, at least one old NF identifier (ID) from the source mobility management function node that corresponds to an old network function (NF) serving a user equipment (UE), determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF of a same NF type as the old NF, and communicating, by the target mobility management function node to the source mobility management function node, information that indicates to the source mobility management function node whether the target mobility management function node uses the at least one old NF ID or uses the at least one new NF ID.

In another embodiment, a method for a source mobility management function in a core network to receive network function (NF) utilization information from a target mobility management function during a change of mobility management function is provided. The method includes sending, by the source mobility management function to the target mobility management function, at least one old NF identifier (ID) that corresponds to an old network function (NF) serving a user equipment (UE). The method further includes receiving, by the source mobility management function from the target mobility management function, information that indicates whether the target mobility management function uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF serving the UE.

In another embodiment, a source mobility management function node for receiving network function (NF) utilization information from a target mobility management function node during a change of mobility management function is provided. The source mobility management function node includes one or more processors and includes memory storing instructions executable by the one or more processors, whereby the source mobility management function node is operable to perform the method of sending, by the source mobility management function node to the target mobility management function node, at least one old NF identifier (ID) that corresponds to an old network function (NF) serving a user equipment (UE), and receiving, by the source mobility management function node from the target mobility management function node, information that indicates whether the target mobility management function node uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF serving the UE.

Certain embodiments may provide one or more of the following technical advantage(s).

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Radio Node: As used herein, a “radio node” is either a radio access node or a wireless device.

Radio Access Node: As used herein, a “radio access node” or “radio network node” is any node in a radio access network of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

Wireless Device: As used herein, a “wireless device” is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.

Network Node: As used herein, a “network node” is any node that is either part of the radio access network or the core network of a cellular communications network/system.

FIG. 5illustrates one example of a cellular communications network500according to some embodiments of the present disclosure. In the embodiments described herein, the cellular communications network500is a 5G NR network. In this example, the cellular communications network500includes base stations502-1and502-2, which in LTE are referred to as eNBs and in 5G NR are referred to as gNBs, controlling corresponding macro cells504-1and504-2. The base stations502-1and502-2are generally referred to herein collectively as base stations502and individually as base station502. Likewise, the macro cells504-1and504-2are generally referred to herein collectively as macro cells504and individually as macro cell504. The cellular communications network500may also include a number of low power nodes506-1through506-4controlling corresponding small cells508-1through508-4. The low power nodes506-1through506-4can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells508-1through508-4may alternatively be provided by the base stations502. The low power nodes506-1through506-4are generally referred to herein collectively as low power nodes506and individually as low power node506. Likewise, the small cells508-1through508-4are generally referred to herein collectively as small cells508and individually as small cell508. The base stations502(and optionally the low power nodes506) are connected to a core network510.

The base stations502and the low power nodes506provide service to wireless devices512-1through512-5in the corresponding cells504and508. The wireless devices512-1through512-5are generally referred to herein collectively as wireless devices512and individually as wireless device512. The wireless devices512are also sometimes referred to herein as UEs.

FIG. 6illustrates an exemplifying wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface.FIG. 6can be viewed as one particular implementation of the cellular communications network500ofFIG. 5.

Seen from the access side, the 5G network architecture shown inFIG. 6comprises a plurality of User Equipment (UEs) connected to either a Radio Access Network (RAN) or an Access Network (AN) as well as an Access and Mobility Management Function (AMF). Typically, the R(AN) comprises base stations, e.g. such as evolved Node Bs (eNBs) or 5G base stations (gNBs) or similar. Seen from the core network side, the 5G core NFs shown inFIG. 6include a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), a Unified Data Management (UDM), an AMF, a Session Management Function (SMF), a Policy Control Function (PCF), and an Application Function (AF).

Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE and the AMF. The reference points for connecting between the AN and the AMF and between the AN and the UPF are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF and the SMF, which implies that the SMF is at least partly controlled by the AMF. N4 is used by the SMF and the UPF so that the UPF can be set using the control signal generated by the SMF, and the UPF can report its state to the SMF. N9is the reference point for the connection between different UPFs, and N14 is the reference point connecting between different AMFs, respectively. N15 and N7 are defined since the PCF applies policy to the AMF and the SMP, respectively. N12 is required for the AMF to perform authentication of the UE. N8 and N10 are defined because the subscription data of the UE is required for the AMF and the SMF.

The 5G core network aims at separating user plane and control plane. The user plane carries user traffic while the control plane carries signaling in the network. InFIG. 6, the UPF is in the user plane and all other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in the control plane. Separating the user plane and the control plane guarantees that each plane resource will be scaled independently. It also allows UPFs to be deployed separately from control plane functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data networks for some applications requiring low latency.

The core 5G network architecture is composed of modularized functions. For example, the AMF and SMF are independent functions in the control plane. Separated AMF and SMF allow independent evolution and scaling. Other control plane functions like the PCF and the AUSF can be separated as shown inFIG. 6. Modularized function design enables the 5G core network to support various services flexibly.

Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the control plane, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

FIG. 7illustrates a 5G network architecture using service-based interfaces between the NFs in the control plane, instead of the point-to-point reference points/interfaces used in the 5G network architecture ofFIG. 6. However, the NFs described above with reference toFIG. 6correspond to the NFs shown inFIG. 7. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. InFIG. 7, the service-based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service-based interface of the AMF and Nsmf for the service-based interface of the SMF, etc. The Network Exposure Function (NEF) and the Network Repository Function (NRF) inFIG. 7are not shown inFIG. 6discussed above. However, it should be clarified that all NFs depicted inFIG. 6can interact with the NEF and the NRF ofFIG. 7as necessary, though not explicitly indicated inFIG. 6.

Some properties of the NFs shown inFIGS. 6 and 7may be described in the following manner. The AMF provides UE-based authentication, authorization, mobility management, etc. A UE even using multiple access technologies is basically connected to a single AMF because the AMF is independent of the access technologies. The SMF is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF for user plane data transfer. If a UE has multiple sessions, different SMFs may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF provides information on the packet flow to the PCF responsible for policy control in order to support Quality of Service (QoS). Based on the information, the PCF determines policies about mobility and session management to make the AMF and SMF operate properly. The AUSF supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM stores subscription data of the UE. The Data Network (DN), not part of the 5G core network, provides Internet access or operator services and similar.

An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure. The NFs UPF, AMF, SMF, PCF, AF, AUSF, and UDM are specific examples of a User Plane (UP) entity, a Mobility Management (MM) entity, a Session Management (SM) entity, a Policy and Charging (PC) entity, an Application entity, an Authentication Server entity and a Unified Data Management entity respectively.

The embodiments enhance communication between a source mobility management function, such as, by way of non-limiting example, a source access and mobility management function (AMF), and a target mobility management function, such as by way of non-limiting example, a target AMF, during a change from the source mobility management function to the target mobility management function. The change, for example, may be a handover. The target mobility management function informs the source mobility management function whether old network functions that were used by the source mobility management function will be used by the target mobility management function, or whether new network functions will be used. If new network functions are being used the target mobility management function, the source mobility management function may perform one or more acts to dissociate from the previous network functions.

The embodiments have applicability in a wide range of applications, including, by way of non-limiting example, the standards TS 23.501 and TS 23.502.

In one embodiment, during a CM-IDLE/CM-CONNECTED mode mobility with AMF change, a new/target AMF shall indicate to an old/source AMF if any old NF has been re-used or wherein new NFs have been selected for the UE in the following AMF services, in case the old AMF has provided information that identifies old NFs for the UE.

In one embodiment, the Namf_Communication_RegistrationCompleteNotify service operation may be modified in the following manner to support communications between the target AMF and the source AMF regarding whether a new NF has been selected or old NFs are being utilized.

Service operation name: Namf_Communication_RegistrationCompleteNotifyDescription: This service operation is used by the consumer NF to inform the AMF that a prior UE context transfer has resulted in the UE successfully registering with it. The UE context is marked inactive in the AMF.NOTE 1: This notification corresponds to an implicit subscription.Input, Required: 5G-GUTI, Reason.Input, Optional: PDU Session ID(s) (indicates the PDU Session(s) to be released), [IN ONE EMBODIMENT, THIS INFORMATION MAY BE EXPANDED TO INCLUDE: NF change related indications (such as, by way of non-limiting example, that a new PCF/SMSF has been selected or that the old PCF/SMSF is being re-used).]Output, Required: None.Output, Optional: None.See clause 4.2.2.2.2 step 10 for example usage of this service operation. When the consumer NF (AMF) receives this notification, it marks the UE context information as inactive since the UE context has been successfully transferred to the peer NF and the UE has successfully registered there. The AMF sends a Namf_Communication_TransferComplete ack to the consumer NF.

In one embodiment, the Namf_Communication_N2InfoNotify service operation may be modified in the following manner to support communications between the target (new) AMF and the source (old) AMF regarding whether a new NF has been selected or old NFs are being utilized.

Service operation name: Namf_Communication_N2InfoNotify.Description: The AMF uses this service operation to notify a particular N2 message information towards the NFs that have subscribed (implicitly or explicitly) for the specific information.Input, Required: AMF ID (GUAMI), N2 information.Input, Optional: [IN ONE EMBODIMENT, THIS INFORMATION MAY BE EXPANDED TO INCLUDE: NF change-related indications (such as, by way of non-limiting example, that a new PCF/SMSF has been selected or that the old PCF/SMSF is being re-used).] Session ID (e.g. PDU Session ID) if the N2 information notified is related to a session (e.g. PDU Session).Output, Required: None.Output, Optional: None.

In one embodiment, the Namf_Communication_CreateUEContext service operation may be modified in the following manner to support communications between the target (new) AMF and the source (old) AMF regarding whether a new NF has been selected or old NFs are being utilized.

Service operation name: Namf_Communication_CreateUEContextDescription: This service operation is used by an old AMF to create the UE context in a new AMF during handover procedures.Input, Required: 5G-GUTI, UE context of the identified UE. As described in Table 5.2.2.2.2-1, the UE context may include the SUPI, DRX parameters, AM policy information, PCF ID, UE network capability, used N1 security context information, event subscriptions by other consumer NF, and the list of SM PDU Session IDs along with the SMF handling the PDU Session, N2 information including source to target RAN transparent container, Endpoint information of S-AMF to receive N2 information notification about handover complete.Input, Optional: allocated EBI information, PCF ID.Output, Required: Cause, N2 information including Target to Source transparent container, N2 SM information (PDU Sessions failed to be setup list, and the N3 DL forwarding information), handle for the UE context created, [IN ONE EMBODIMENT, THIS INFORMATION MAY BE EXPANDED TO INCLUDE: NF change-related indications (i.e. a new SMF has been selected or an old SMF is re-used).]Output, Optional: None.Note: in case of HO, New changes can either be made in 5.2.2.2.10 (more suitable if the NF is PCF or SMSF) or in 5.2.2.2.11 (more suitable if the NF is SMF)

The above service operations may be used in various procedures, including, for example, the preparation phase and the execution phase of the hand over procedure, for CM-CONNECTED mode mobility.

FIG. 8illustrates the 4.9.1.3.2 Preparation Phase. In support of the embodiments, Step 12 of the Preparation Phase may be updated to including the following:

12. [Conditional] T-AMF to S-AMF:Namf_Communication_CreateUEContext Response (N2 information necessary for S-AMF to send Handover Command to S-RAN including Target to Source transparent container, PDU Sessions failed to be setup list, N2 SM information (N3 DL forwarding Information)).AMF supervises the Nsmf_PDUSession_UpdateSMContext Response message from the involved SMFs. At expiry of the maximum wait time or when all Nsmf_PDUSession_UpdateSMContext Response messages are received, T-AMF sends the Namf_Communication_CreateUEContext Response to the S-AMF.[IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: If the S-AMF (source AMF) has identified old NF IDs (e.g. SMF IDs) in step 3, the T-AMF (target AMF) shall indicate back whether the old NF IDs (e.g. SMF IDs) are being re-used by the target AMF or whether new NF IDs are selected by the target AMF.]The Target to Source transport container is received from the T-RAN. The N2 SM Information is received from the SMF in step 11f.

FIG. 9illustrates the 4.9.1.3.3 Execution Phase. In support of the embodiments, Step 6a of the Preparation Phase may be updated to include the following:6a. [Conditional] T-AMF to S-AMF: Namf_Communication_N2InfoNotify.The T-AMF notifies to the S-AMF about the N2 handover notify received from the T-RAN by invoking the Namf_Communication_N2InfoNotify.[IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: If the S-AMF has provided selected NF IDs (e.g. PCF ID, SMSF IDs, and the like) in preparation phase step 3, the new AMF shall indicate back if the NF IDs are re-used by the new AMF or new NF IDs are selected/used by the new AMF.]

A timer in S-AMF is started to supervise when resources in S-RAN shall be release.

Step 14a may also be updated in the following manner:14a. AMF to S-RAN: UE Context Release Command ( ).After the timer in step 6a expires, the AMF sends UE Context Release Command.[IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: The S-AMF also invokes the Nsmf_PDUSession_ReleaseSMContext service operation to release the resource in SMF, in case an SMF change is indicated in step 12 of the preparation phase.]14b. S-RAN to AMF: UE Context Release Complete ( ).The source NG-RAN releases its resources related to the UE and responds with a UE Context Release Complete ( ) message.

FIG. 10illustrates 5.1.1.1.1 and 4.2.2.2.2 General Registration procedure, either for CM-IDLE mode mobility or CM-CONNECTED mode mobility.

Step 5. [Conditional] old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE Context in AMF (as per Table 5.2.2.2.2-1)) or UDSF to new AMF: Nudsf_Unstructured Data Management_Query( ).

If the UDSF was queried in step 4, the UDSF responds to the new AMF for the Nudsf_Unstructured Data Management_Query invocation with the related contexts including established PDU Sessions, the old AMF includes SMF information DNN, S-NSSAI(s) and PDU Session ID, active NGAP UE-TNLA bindings to N3IWF, the old AMF includes information about the NGAP UE-TNLA bindings. If the Old AMF was queried in step 4, Old AMF responds to the new AMF for the Namf_Communication_UEContextTransfer invocation by including the UE's SUPI and UE Context.

If old AMF holds information about established PDU Session(s), the old AMF includes SMF information, DNN(s), S-NSSAI(s) and PDU Session ID(s).

If old AMF holds information about active NGAP UE-TNLA bindings to N3IWF, the old AMF includes information about the NGAP UE-TNLA bindings.

If old AMF fails the integrity check of the Registration Request NAS message, the old AMF shall indicate the integrity check failure.

If old AMF holds information about AM Policy Association, the old AMF includes the information about the AM Policy Association including the policy control request trigger and PCF ID. In the roaming case, V-PCF ID and H-PCF ID are included.

In support of the embodiments, Step 10 may be updated to including the following:10. [Conditional] new AMF to old AMF: Namf_Communication_RegistrationCompleteNotify ( ).If the AMF has changed the new AMF notifies the old AMF that the registration of the UE in the new AMF is completed by invoking the Namf_Communication_RegistrationCompleteNotify service operation.If the authentication/security procedure fails, then the Registration shall be rejected, and the new AMF invokes the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code towards the old AMF. The old AMF continues as if the UE context transfer service operation was never received.If one or more of the S-NSSAls used in the old Registration Area cannot be served in the target Registration Area, the new AMF determines which PDU Session cannot be supported in the new Registration Area. The new AMF invokes the Namf_Communication_RegistrationCompleteNotify service operation including the rejected PDU Session ID and a reject cause (e.g. the S-NSSAI becomes no longer available) towards the old AMF. Then the new AMF modifies the PDU Session Status correspondingly. The old AMF informs the corresponding SMF(s) to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation.[IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: If the old AMF has provided selected/old NF IDs (e.g. PCF ID, SMSF IDs, . . . ), the new AMF shall indicate if these NF IDs are re-used by the new AMF or new NF IDs are selected by the new AMF.]See clause 5.2.2.2.3 for details of Namf_Communication_RegistrationCompleteNotify service operation.

In support of the embodiments, Step 21 may be updated to include the following:21. [Conditional] old AMF to (V−)PCF: AMF-Initiated Policy Association Termination.If the old AMF previously initiated a Policy Association to the PCF, and the old AMF did not transfer the [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: selected/old NF IDs, e.g. PCF ID] to the new AMF (e.g. new AMF is in different PLMN), the old AMF performs an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2, to delete the association with the PCF [IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: and release the resource in PCF.][IN ONE EMBODIMENT, THE INFORMATION MAY BE UPDATED TO INCLUDE: If the source AMF transferred the selected/old NF IDs to the target AMF, and the target AMF has indicated back in step 10 (or step 6a in the execution phase of the N2 HO procedure) if the selected/old NF IDs are re-used or if new NF IDs are selected by the target AMF, the source AMF either performs local release of the PCF or an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2, to delete the association with the PCF.

FIG. 11illustrates the 4.16.1.3-1: Policy Association Establishment with the old PCF procedure. In support of the embodiments, Steps 6a and 6b may be added in the following manner.

AM Policy Association Establishment with the Old PCF

The procedure relates to the situation of AMF relocation without PCF change in handover procedure and registration procedure.[IN ONE EMBODIMENT, THE FOLLOWING STEPS MAY BE ADDED: Steps 6a, 6b, Based on provided NF (e.g. PCF) re-use or NF change information from the new/target AMF (as specified in Registration procedure or HO procedure), the old AMF may initiate Policy Association Termination procedure, as defined in clause 4.16.3.2, to delete the association with the PCF or may only perform a local PCF release.]

FIG. 12is a schematic block diagram of a network function node suitable for implementing a source mobility management function or target mobility management function according to some embodiments of the present disclosure. The network function node1200, for example, may be a computing device or other processing device. As illustrated, the network function node1200includes a control system1202that includes one or more processors1204(e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory1206, and a network interface1208. The one or more processors1204are also referred to herein as processing circuitry. In addition, the network function node1200may, in some embodiments, include one or more radio units1210that each include one or more transmitters1212and one or more receivers1214coupled to one or more antennas1216. The radio units1210may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s)1210is external to the control system1202and connected to the control system1202via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s)1210and potentially the antenna(s)1216are integrated together with the control system1202. The one or more processors1204operate to provide one or more functions of the network function node1200as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory1206and executed by the one or more processors1204.

FIG. 13is a schematic block diagram that illustrates a virtualized embodiment of the network function node1200according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures.

As used herein, a “virtualized” radio access node is an implementation of the network function node1200in which at least a portion of the functionality of the network function node1200is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network function node1200includes the control system1202that includes the one or more processors1204(e.g., CPUs, ASICs, FPGAs, and/or the like), the memory1206, the network interface1208, the one or more radio units1210that each include the one or more transmitters1212, and the one or more receivers1214coupled to the one or more antennas1216, as described above. The control system1202is connected to the radio unit(s)1210via, for example, an optical cable or the like. The control system1202is connected to one or more processing nodes1300coupled to or included as part of a network(s)1302via the network interface1208. Each processing node1300includes one or more processors1304(e.g., CPUs, ASICs, FPGAs, and/or the like), memory1306, and a network interface1308.

In this example, functions1310of the network function node1200described herein are implemented at the one or more processing nodes1300or distributed across the control system1202and the one or more processing nodes1300in any desired manner. In some particular embodiments, some or all of the functions1310of the network function node1200described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s)1300. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s)1300and the control system1202is used in order to carry out at least some of the desired functions1310. Notably, in some embodiments, the control system1202may not be included, in which case the radio unit(s)1210communicates directly with the processing node(s)1300via an appropriate network interface(s).

FIG. 14is a schematic block diagram of the network function node1200according to some other embodiments of the present disclosure. The network function node1200includes one or more modules1402, each of which is implemented in software. The module(s)1402provide the functionality of the network function node1200described herein, such as that attributed to a target AMF or a source AMF.

FIG. 15is a flowchart illustrating a method for a target mobility management function, such as a target AMF, in a core network to communicate NF utilization information with a source mobility management function, such as a source AMF, during a change of mobility management function according to one embodiment. The target mobility management function receives at least one old NF identifier (ID) from the source mobility management function that corresponds to an old network function (NF) serving a user equipment (UE) (block1500). The old NF may comprise, for example, an old SMF, an old SMSF, an old PCF, or any other NF. The target mobility management function determines to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF of a same NF type as the old NF (block1502). The new NF may comprise, for example, a new SMF, a new SMSF, a new PCF, or any other NF. The target mobility management function communicates, to the source mobility management function, information that indicates to the source mobility management function whether the target mobility management function uses the at least one old NF ID or uses the at least one new NF ID (block1504).

FIG. 16is a flowchart illustrating a method implemented in a source mobility management function, such as a source AMF, in accordance with one embodiment. The source mobility management function sends, to the target mobility management function, such as a target AMF, at least one old NF identifier (ID) that corresponds to an old network function (NF) serving a user equipment (UE) (block1600). The old NF may comprise, for example, an old SMF, an old SMSF, an old PCF, or any other NF. The source mobility management function receives, from the target mobility management function, information that indicates whether the target mobility management function uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF serving the UE (block1602). The new NF may comprise, for example, a new SMF, a new SMSF, a new PCF, or any other NF.

Some Embodiments

Some of the embodiments described above may be summarized in the following itemized manner:Item 1. A method for a target mobility management function entity in a core network to communicate network function (NF) utilization information with a source mobility management function entity during a change of mobility management function entity, comprising:

receiving, by the target mobility management function entity, at least one old NF identifier (ID) from the source mobility management function entity that corresponds to an old NF entity serving a user equipment (UE);

determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF entity of a same NF type as the old NF entity; and

communicating, by the target mobility management function entity to the source mobility management function entity, information that indicates to the source mobility management function entity whether the target mobility management function entity uses the at least one old NF ID or uses the at least one new NF ID.Item 2. The method of item 1 wherein the NF entities comprise one or more of a short message service function (SMSF) entity, a policy control function (PCF) entity, and a session management function (SMF) entity.Item 3. The method of item 1 wherein the target mobility management function entity comprises a target access and mobility management function (AMF) entity, and wherein the source mobility management function entity comprises a source AMF entity.Item 4. The method of item 3 wherein communicating the information that indicates to the source mobility management function entity whether the target mobility management function entity uses the at least one old NF ID or uses the at least one new NF ID comprises:

sending, by the target AMF entity to the source AMF ewntity, a Namf_Communication_CreateUEContext response that indicates to the source AMF entity whether the target AMF entity uses the at least one old NF ID or uses the at least one new NF ID.Item 5. The method of item 4 further comprising generating the Namf_Communication_CreateUEContext response while invoking a Namf_Communication_CreateUEContext service operation.Item 6. The method of item 3 wherein communicating the information that indicates to the source AMF entity whether the target AMF entity uses the at least one old NF ID or uses the at least one new NF ID comprises:

receiving, by the target AMF entity, a handover notify from a radio access node (RAN); and

invoking, by the target AMF entity in response to the handover notify, a Namf_Communication_N2InfoNotify service operation that indicates to the source AMF entity whether the target AMF entity uses the at least one old NF ID or uses the at least one new NF ID.Item 7. The method of item 3 wherein communicating the information that indicates to the source AMF entity whether the target AMF entity uses the at least one old NF ID or uses the at least one new NF ID comprises:

invoking, by the target AMF entity, a Namf_Communication_RegistrationCompleteNotify service operation that indicates to the source AMF entity whether the target AMF entity uses the at least one old NF ID or uses the at least one new NF ID.Item 8. The method of item 1 wherein determining to either use the at least one old NF ID or to use the at least one new NF ID that corresponds the new NF entity of the same NF type as the old NF entity comprises performing a NF service discover function to determine to either use the at least one old NF ID or to use the at least one new NF ID that corresponds to the new NF entity of the same NF type as the old NF entity.Item 9. A method for a source mobility management function entity in a core network to receive network function (NF) utilization information from a target mobility management function entity during a change of mobility management function entity, comprising:

sending, by the source mobility management function entity to the target mobility management function entity, at least one old NF identifier (ID) that corresponds to an old NF entity serving a user equipment (UE); and

receiving, by the source mobility management function entity from the target mobility management function entity, information that indicates whether the target mobility management function entity uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF entity serving the UE.Item 10. The method of item 9 wherein the NF entities comprise one or more of a short message service function (SMSF) entity, a policy control function (PCF) entity, and a session management function (SMF) entity.Item 11. The method of item 9 wherein the target mobility management function entity comprises a target access and mobility management function (AMF) entity, and wherein the source mobility management function entity comprises a source AMF entity.Item 12. The method of item 11 wherein the information indicates that the target AMF entity is using a new session management function (SMF) ID, and further comprising:

invoking a Nsmf_PDUSession_ReleaseSMContext service operation, by the source AMF entity toward an old SMF entity, to release an existing session management (SM) context in the old SMF entity.Item 13. The method of item 11 wherein the information indicates that the target AMF entity is using an old SMF ID, and further comprising:

deleting, by the source AMF entity locally, to release an existing session management (SM) context in the source AMF entity.Item 14. The method of item 11 wherein the information indicates that the target AMF entity is using an old policy control function (PCF) ID, and further comprising:

performing, by the source AMF entity, a local release of an old PCF that corresponds to the old PCF ID.Item 15. The method of item 14 wherein the information indicates that the target AMF entity is utilizing a new PCF ID, and further comprising:

sending, by the source AMF entity to a PCF entity, a Npcf_AMPolicyControl_Delete service operation.Item 16. The method of item 11 wherein the information indicates that the target AMF entity is using an old SMSF ID and further comprising:

performing, by the source AMF entity, a local release of an association context of an old SMSF entity that corresponds to the old SMSF ID.Item 17. The method of item 11 wherein the information indicates that the target AMF entity is utilizing a new SMSF ID and further comprising:

sending, by the source AMF entity to an old SMSF entity, a Nsmsf_SMService_Deactivate service operation to trigger a release of UE Context for SMS on the old SMSF entity.Item 18. A target mobility management function entity for communicating network function (NF) utilization information with a source mobility management function entity during a change of mobility management function entity, the target mobility management function entity comprising:

one or more processors; and

memory storing instructions executable by the one or more processors, whereby the target mobility management function entity is operable to perform the method of:receiving, by the target mobility management function entity, at least one old NF identifier (ID) from the source mobility management function entity that corresponds to an old NF entity serving a user equipment (UE);determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF entity of a same NF type as the old NF entity; andcommunicating, by the target mobility management function entity to the source mobility management function entity, information that indicates to the source mobility management function entity whether the target mobility management function entity uses the at least one old NF ID or uses the at least one new NF ID.Item 19. A source mobility management function entity for receiving network function (NF) utilization information from a target mobility management function entity during a change of mobility management function entity, the source mobility management function entity comprising:

one or more processors; and

memory storing instructions executable by the one or more processors, whereby the source mobility management function entity is operable to perform the method of:sending, by the source mobility management function entity to the target mobility management function entity, at least one old NF identifier (ID) that corresponds to an old NF entity serving a user equipment (UE); andreceiving, by the source mobility management function entity from the target mobility management function entity, information that indicates whether the target mobility management function entity uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF entity serving the UE.Item 20. A non-transitory computer readable medium storing software instructions that, when executed by one or more processors of a network entity for performing a method for a source mobility management function entity for receiving network function (NF) utilization information from a target mobility management function entity during a change of mobility management function entity, cause the network entity to perform the method of:

sending, by the source mobility management function entity to the target mobility management function entity, at least one old NF identifier (ID) that corresponds to an old NF entity serving a user equipment (UE); and

receiving, by the source mobility management function entity from the target mobility management function entity, information that indicates whether the target mobility management function entity uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF entity serving the UE.Item 21. A computer program comprising instructions which, when executed by at least one processor of a network entity, cause the at least one processor to perform the method of:

sending, by a source mobility management function entity to a target mobility management function entity, at least one old network function (NF) identifier (ID) that corresponds to an old NF entity serving a user equipment (UE); and

receiving, by the source mobility management function entity from the target mobility management function entity, information that indicates whether the target mobility management function entity uses the at least one old NF ID or uses at least one new NF ID that corresponds to a new NF entity serving the UE.Item 22. A carrier comprising the computer program of item 21, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.Item 23. A non-transitory computer readable medium storing software instructions that, when executed by one or more processors of a network entity for performing a method for communicating network function (NF) utilization information with a source mobility management function entity during a change of mobility management function entity, cause the network entity to perform the method of:

receiving at least one old NF identifier (ID) from the source mobility management function entity that corresponds to an old NF serving a user equipment (UE);

determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF entity of a same NF entity type as the old NF entity; and

communicating, to the source mobility management function entity, information that indicates to the source mobility management function entity whether the target mobility management function entity uses the at least one old NF ID or uses the at least one new NF ID.Item 24. A computer program comprising instructions which, when executed by at least one processor of a network entity, cause the at least one processor to perform the method of:

receiving, by a target mobility management function entity, at least one old network function (NF) identifier (ID) from a source mobility management function entity that corresponds to an old NF entity serving a user equipment (UE);

determining to either use the at least one old NF ID or to use at least one new NF ID that corresponds to a new NF entity of a same NF entity type as the old NF entity; and

communicating, by the target mobility management function entity to the source mobility management function entity, information that indicates to the source mobility management function entity whether the target mobility management function entity uses the at least one old NF ID or uses the at least one new NF ID.Item 25. A carrier comprising the computer program of item 24, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.
Abbreviations

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

1 × RTT CDMA20001 × Radio Transmission Technology2GSecond Generation3GThird Generation3GPPThird Generation Partnership Project4GFourth Generation5GFifth GenerationABSAlmost Blank SubframeACAlternating CurrentAFApplication FunctionAMFAccess and Mobility Management FunctionANAccess NetworkAPAccess PointARQAutomatic Repeat RequestASICApplication Specific Integrated CircuitATMAsynchronous Transfer ModeAUSFAuthentication Server FunctionAWGNAdditive White Gaussian NoiseBCCHBroadcast Control ChannelBCHBroadcast ChannelBSBase StationBSCBase Station ControllerBTSBase Transceiver StationBWBandwidthBWPBandwidth PartCACarrier AggregationCCComponent CarrierCCCHCommon Control ChannelCDCompact DiskCDMACode Division Multiple AccessCGICell Global IdentifierCIRChannel Impulse ResponseCOTSCommercial Off-the-ShelfCPCyclic PrefixCPECustomer Premise EquipmentCPICHCommon Pilot ChannelCPICH Ec/NoCommon Pilot Channel received energy per chip dividedby the power density in the bandCPUCentral Processing UnitCQIChannel Quality InformationC-RNTICell Radio Network Temporary IdentifierCSIChannel State InformationCSI-RSChannel State Information Reference SignalD2DDevice-to-DeviceDASDistributed Antenna SystemDCDirect CurrentDCCHDedicated Control ChannelDIMMDual In-Line Memory ModuleDLDownlinkDMDemodulationDMRSDemodulation Reference SignalDNData NetworkDRXDiscontinuous ReceptionDSPDigital Signal ProcessorDTXDiscontinuous TransmissionDTCHDedicated Traffic ChannelDUTDevice Under TestDVDDigital Video DiskE-CIDEnhanced Cell Identifier (positioning method)EEPROMElectrically Erasable Programmable Read Only MemoryECGIEvolved Cell Global IdentifiereMTCEnhanced Machine-Type CommunicationeNBEnhanced or Evolved Node BePDCCHEnhanced Physical Downlink Control ChannelEPROMErasable Programmable Read Only MemoryE-SMLCEvolved Serving Mobile Location CenterE-UTRAEvolved Universal Terrestrial Radio AccessE-UTRANEvolved Universal Terrestrial Radio Access NetworkFDDFrequency Division DuplexingFFSFor Further StudyFPGAField Programmable Gate ArrayGERANGlobal System for Mobile (GSM) Communications Enhanced DataRates for GSM Evolution Radio Access NetworkGHzGigahertzgNBNew Radio Base StationGNSSGlobal Navigation Satellite SystemGPSGlobal Positioning SystemGSMGlobal System for Mobile CommunicationsHARQHybrid Automatic Repeat RequestHDDSHolographic Digital Data StorageHD-DVDHigh-Density Digital Versatile DiscHOHandoverHRPDHigh Rate Packet DataHSPAHigh Speed Packet AccessI/OInput and OutputIoTInternet of ThingsIPInternet ProtocolLANLocal Area NetworkLEELaptop Embedded EquipmentLMELaptop Mounted EquipmentLOSLine of SightLPPLong Term Evolution Positioning ProtocolLTELong Term EvolutionM2MMachine-to-MachineMACMedium Access ControlMANOManagement and OrchestrationMBMSMultimedia Broadcast Multicast ServicesMBSFNMultimedia Broadcast Multicast Service Single FrequencyNetworkMCEMulti-Cell/Multicast Coordination EntityMDTMinimization of Drive TestsMIBMaster Information BlockMIMOMultiple Input Multiple OutputMMEMobility Management EntityMSCMobile Switching CenterMSRMulti-Standard RadioMTCMachine Type CommunicationNB-IoTNarrowband Internet of ThingsNEFNetwork Exposure FunctionNFNetwork FunctionNFVNetwork Function VirtualizationNICNetwork Interface ControllerNPDCCHNarrowband Physical Downlink Control ChannelNRNew RadioNRFNetwork Repository FunctionNSSFNetwork Slice Selection FunctionO&MOperation and MaintenanceOCNGOrthogonal Frequency Division Multiple Access Channel NoiseGeneratorOFDMOrthogonal Frequency Division MultiplexingOFDMAOrthogonal Frequency Division Multiple AccessOSSOperations Support SystemOTDOAObserved Time Difference of ArrivalOTTOver-the-TopPBCHPhysical Broadcast ChannelP-CCPCHPrimary Common Control Physical ChannelPCellPrimary CellPCFPolicy Control FunctionPCFICHPhysical Control Format Indicator ChannelPDAPersonal Digital AssistantPDCCHPhysical Downlink Control ChannelPDPProfile Delay ProfilePDSCHPhysical Downlink Shared ChannelP-GWPacket Data Network GatewayPHICHPhysical Hybrid Automatic Repeat Request Indicator ChannelPLMNPublic Land Mobile NetworkPMIPrecoder Matrix IndicatorPRACHPhysical Random Access ChannelPRBPhysical Resource BlockPROMProgrammable Read Only MemoryPRSPositioning Reference SignalPSSPrimary Synchronization SignalPSTNPublic Switched Telephone NetworksPUCCHPhysical Uplink Control ChannelPUSCHPhysical Uplink Shared ChannelQoSQuality of ServiceRACHRandom Access ChannelRAIDRedundant Array of Independent DisksRAMRandom Access MemoryRANRadio Access NetworkRATRadio Access TechnologyREResource ElementRFRadio FrequencyRLMRadio Link ManagementRNCRadio Network ControllerRNTIRadio Network Temporary IdentifierROMRead Only MemoryRRCRadio Resource ControlRRHRemote Radio HeadRRMRadio Resource ManagementRRURemote Radio UnitRSReference SignalRSCPReceived Signal Code PowerRSRPReference Symbol Received Power/Reference Signal ReceivedPowerRSRQReference Symbol Received Quality/Reference Signal ReceivedQualityRSSIReceived Signal Strength IndicatorRSTDReference Signal Time DifferenceRTTRound Trip TimeRUIMRemovable User IdentitySCEFService Capability Exposure FunctionSCellSecondary CellSCHSynchronization ChannelSDRAMSynchronous Dynamic Random Access MemorySDUService Data UnitSFNSystem Frame NumberS-GWServing GatewaySISystem InformationSIBSystem Information BlockSIMSubscriber Identity ModuleSMFSession Management FunctionSMSFShort Message Service FunctionSNRSignal to Noise RatioSOCSystem on a ChipSONSelf-Organizing NetworkSONETSynchronous Optical NetworkingSRSSounding Reference SignalSSSynchronization SignalSSSSecondary Synchronization SignalTCPTransmission Control ProtocolTDDTime Division DuplexingTDOATime Difference of ArrivalTOATime of ArrivalTPMITransmit Precoding Matrix IndicatorTRPTransmission/Reception PointTSSTertiary Synchronization SignalTTITransmission Time IntervalUDMUnified Data ManagementUEUser EquipmentULUplinkUMTSUniversal Mobile Telecommunications SystemUSBUniversal Serial BusUSIMUniversal Subscriber Identity ModuleUTDOAUplink Time Difference of ArrivalUTRAUniversal Terrestrial Radio AccessUTRANUniversal Terrestrial Radio Access NetworkV2IVehicle-to-InfrastructureV2VVehicle-to-VehicleV2XVehicle-to-EverythingVMMVirtual Machine MonitorVNEVirtual Network ElementVNFVirtual Network FunctionVoIPVoice over Internet ProtocolWANWide Area NetworkWCDMAWideband Code Division Multiple AccessWDWireless DeviceWiMaxWorldwide Interoperability for Microwave AccessWLANWireless Local Area Network