Check for roaming prompts during mobility registration

Abstract

Systems and methods provide roaming guidance (SoR) information during a user equipment (UE) mobility registration process. In other systems and methods, as long as the UE's subscriber identity module (SIM) or universal SIM (USIM) indicates that the UE expects to receive SoR information due to initial registration in a visited public land mobile network (VPLMN), the UE performs initial registration until a valid SoR is received in the visited country or network, instead of triggering mobility registration and periodic registration.

Description

[Technical field]

[0001] This application relates generally to wireless communication systems, including steering of roaming (SoR) in a public land mobile network (PLMN). [Background technology]

[0002] Wireless mobile communication technologies use a variety of standards and protocols to transmit data between base stations and wireless mobile devices. Standards and protocols for wireless communication systems can include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G), the Institute of Electrical and Electronics, Engineers (IEEE) 802.16 standard, commonly known to industry groups as worldwide interoperability for microwave access (WiMAX), and the IEEE 802.11 standard for wireless local area networks (WLANs), commonly known to industry groups as Wi-Fi. In a 3GPP radio access network (RAN) of an LTE system, a base station may include a RAN node, such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as evolved Node B, enhanced Node B, eNodeB, or eNB) and / or an E-UTRAN Radio Network Controller (RNC), which communicates with wireless communication devices known as user equipment (UE). In a fifth generation (5G) wireless RAN, the RAN node may include a 5G node, an NR node (also referred to as next-generation Node B, or gNode B (gNB)).

[0003] The RAN communicates between the RAN nodes and the UEs using radio access technologies (RATs). The RANs may include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provide access to communication services via a core network. Each of the RANs operates according to a particular 3GPP RAT. For example, the GERAN implements the GSM and / or EDGE RATs, the UTRAN implements the universal mobile telecommunication system (UMTS) RAT or other 3GPP RATs, the E-UTRAN implements the LTE RAT, and the NG-RAN implements the 5G RAT. In certain deployments, the E-UTRAN may also implement the 5G RAT.

[0004] Navigation of a UE in a visited public land mobile network (VPLMN) is a procedure that allows a home public land mobile network (HPLMN) to update the list of preferred PLMN / access technology combinations in the UE via NAS (non-access stratum) signaling. A HPLMN is a PLMN whose PLMN identity's mobile country code (MCC) and mobile network code (MNC) match the MCC and MNC of the UE's international mobile subscriber identity (IMSI). The criteria for matching may be defined by 3GPP standards. A VPLMN is either a different PLMN than the HPLMN (if the equivalent HPLMN (EHPLMN) list does not exist or is empty) or a different PLMN than the EHPLMN (if the EHPLMN list exists). The HPLMN updates the list of preferred PLMN / access technology combinations depending on, for example, the PLMN in which the UE is registered or when required by HPLMN operator policy. Steering a UE in a VPLMN may also be known as roaming steering (SoR). SoR allows the HPLMN to steer a UE from one network to another. SoR is a technique whereby the HPLMN facilitates a roaming UE to roam to a preferred destination network.

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) of a reference number refers to the figure number in which that element is first introduced. [Brief description of the drawings]

[0006] [Figure 1] 4 is a flowchart of a method for a UE to communicate within a PLMN according to one embodiment. [Diagram 2]4 is a flowchart of a method for a UE according to one embodiment. [Diagram 3] 1 is a flowchart of a method for AMF in a wireless network according to one embodiment. [Figure 4] 1 is a flowchart of a method for a HPLMN, according to one embodiment. [Figure 5A] FIG. 13 is a data flow diagram of an example registration procedure according to one embodiment. [Figure 5B] FIG. 13 is a data flow diagram of an example registration procedure according to one embodiment. [Figure 6] 1 is a data flow diagram of an example method for directing a UE in a VPLM during registration, according to one embodiment. [Figure 7] FIG. 1 illustrates an example service-based architecture, according to certain embodiments. [Figure 8] FIG. 1 illustrates an infrastructure facility according to one embodiment. [Figure 9] FIG. 1 illustrates a platform according to one embodiment. [Figure 10] FIG. 2 illustrates components according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Both the subscriber and the subscriber's usual mobile operator (i.e., the UE's home network) may prefer that roaming take place via a local operator with acceptable pricing and network quality. As explained above, SoR allows the home network to redirect the UE to connect via a preferred roaming partner at a given location. The embodiments disclosed herein are generally aimed at facilitating SoR during the UE mobility registration process in a 5G NR access network. In other embodiments, instead of triggering mobility registration and periodic registration, the UE performs initial registration until a valid SoR is received in the visited country or network, as long as the UE's Subscriber Identity Module (SIM) or Universal SIM (USIM) indicates that the UE expects to receive SoR information due to initial registration in the VPLMN.

[0008] Registration to a PLMN includes the process of camping on a cell of a PLMN or a separate non-public network (SNPN) and performing any required location registrations (LR). The SoR information includes HPLMN protection information, which includes an indication of whether the Unified Data Management (UDM) requires an acknowledgment from the UE of successful reception of the roaming guidance information. The SoR information also includes one of the following: a list of preferred PLMN / access technology combinations and an indication that it is included, a secured packet and an indication that it is included, or an HPLMN indication that no modification of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is required and therefore no list of preferred PLMN / access technology combinations is provided. The secured packet includes the list of preferred PLMN / access technology combinations encapsulated by a security mechanism (see, for example, 3GPP TS 31.115).

[0009] Some aspects disclosed herein are directed to a 5G SoR methodology that is effective even when the visited (i.e., roaming) network cannot be trusted to relay guidance information received from the UE's home network. In general, the SoR methodology involves the home network sending SoR information to the UE via the visited (i.e., roaming) network as part of the UE registration, and the UE being configured by the HPLMN as part of the registration process to determine whether to initiate a roaming guidance procedure at the UE based on whether the SoR information is actually received. If the HPLMN does not configure the UE, the UE skips performing the SoR procedure. If the UE is configured to perform roaming guidance and the SoR information is not received (or if the integrity check of the SoR indicator fails), the UE may be configured, for example, to set the current visited (i.e., roaming) network to the lowest level of priority so that the UE knows to attempt to connect to an alternative roaming network if possible. However, if the SoR information is received (and the SoR information passes the integrity check), the UE may be configured to direct roaming according to guidance information obtained from the home network. The integrity check may be based at least in part on one or more keys shared between the HPLMN and the UE. If the home network concludes that the current visited (i.e., roaming) network is acceptable, the home network may convey that conclusion by sending an SoR indicator to the UE without additional guidance information. However, if the home network concludes that the current visited (i.e., roaming) network is not acceptable, such conclusion may be communicated by sending an SoR indicator to the UE with additional guidance information. The UE may then update the PLMN / RAT network selection information in the SIM or USIM, or in an internal memory, to direct roaming according to the guidance information received from the home network.

[0010] In some system implementations (see, for example, 3GPP TS 23.122), the HPLMN may configure the USIM to indicate that the UE is expecting to receive SoR information due to an initial registration in the VPLMN, so that the UE can detect if the VPLMN has changed the SoR information. If the UE detects that the VPLMN has changed or removed the SoR information, the UE may consider the current VPLMN as the lowest priority PLMN. However, currently, SoR updates are specified only for initial and emergency registrations. For example, the UE context information stored in the Access and Mobility Management Function (AMF) only includes an SoR update indicator for initial and emergency registrations. The SoR update indicator for initial registration indicates whether the UDM requests the AMF to retrieve SoR information when the UE performs registration with a non-access stratum (NAS) registration type "initial registration". The SoR update indicator for emergency registration indicates whether the UDM requests the AMF to retrieve SoR information when the UE performs registration with a NAS registration type "emergency registration".

[0011] In scenarios where the UE performs registration on 5G due to mobility from another RAT or due to a PLMN change, in conventional systems, SoR check during mobility registration is not mandatory, even when the UE's USIM indicates that the UE is expected to receive roaming guidance information. Thus, the AMF and the UE do not perform SoR-related operations. This may result in the UE remaining on a VPLMN with unacceptably low priority (e.g., having modified or removed the SoR information received from the HPLMN). Some non-limiting example scenarios of this problem are described below, but the problem is commonly seen in flows where mobility registration is triggered on a 5G roaming PLMN without prior receipt of an SoR container from the HPLMN.

[0012] In one example scenario, a UE's USIM indicates that the UE expects to receive SoR information due to initial registration in a VPLMN. The UE camps on and registers on VPLMN1 over LTE. The UE then reselects on 5G (different RAT) within the same VPLMN1 and performs mobility registration on 5G. The registration accept message on 5G VPLMN1 does not include the SoR transparent container information element (IE). The UE remains on VPLMN1 because the USIM is configured with an indication that the UE will receive and integrity check the SoR transparent container IE for the initial registration accept message only.

[0013] In another example scenario, a UE's USIM indicates that the UE expects to receive SoR information due to initial registration on a VPLMN. The UE camps on 5G VPLMN1 and successfully registers (authentication / SMC) but does not receive the SoR container. The UE transitions to REGISTERED-NORMAL-SERVICE. Per 3GPP TS 24.501, section 5.5.1.2.4, the UE locally detaches, lowers the priority of VPLMN1, and selects VPLMN2. The UE performs mobility registration on VPLMN2, but VPLMN2 does not provide a SoR container. The UE remains on VPLMN2 because the USIM is configured with an indication that the UE will receive and integrity check the SoR transparent container IE for the initial registration accept message only.

[0014] A control plane solution for SoR in 5GS is specified in 3GPP TS23.122. When a UE camps on a roaming network, the HPLMN may direct the UE to the most preferred network by sending an SoR container as part of the initial registration or downlink (DL) NAS transport message. There are scenarios where the UE is unable to successfully receive and store the SoR container, resulting in the current VPLMN being added to the "PLMNs where registration was aborted due to SoR" list. If the UE maintains this list, it may cause issues such as the UE losing normal service or getting stuck in a low priority PLMN. For example, when two VPLMNs are deployed / available in the current country, a UE registers with VPLMN1 and a registration accept message is received. The UE may have an operator controlled PLMN (OPLMN) list in the SIM. The conditions for adding the current PLMN to the "PLMNs with registration aborted due to SoR" list are met, VPLMN1 is added to the list and the connection is released. The UE attempts to search for a higher priority PLMN and finds VPLMN2, which may be a lower priority PLMN. Registration is attempted on VPLMN2 and a registration accept message is received. After registration is complete, the UE stays on VPLMN2 and adds VPLMN2 to the "PLMNs with registration aborted due to SoR" list. The UE then attempts to scan for higher priority PLMNs. Periodic HPLMN scanning continues. If the UE initiates mobility registration, no more SoR is expected to be received from the HPLMN and the UE is stalled on the non-preferred PLMN and no further PLMN selections are attempted until the HPLMN timer expires.

[0015] In one embodiment, the UE context information stored in the AMF (defined in 3GPP TS 23.502, Table 5.2.2.2.2-1 and described in detail below) is extended to maintain an indicator "SoR Update Indicator for Mobility Registration" to indicate that the UDM should request the AMF to receive an SoR container in a mobility registration request if no SoR container has been shared with the UE in a previous registration attempt. In some such embodiments, this indicator may be reset once the SoR container is successfully shared with the UE to avoid signaling overload between the UE, the AMF, and / or the UDM at every mobility registration.

[0016] For example, Table 1 shows the definition of the SoR Update Indicator for Mobility Registration, included in the UE context information stored in the AMF and used for the registration procedure by some embodiments, together with the SoR Update Indicator for Initial Registration and the SoR Update for Emergency Registration. [Table 1]

[0017] In some embodiments, the HPLMN may configure the SIM or USIM of the subscriber UE to indicate that the UE is expected to receive roaming guidance information due to initial registration or due to a mobility registration triggered before successful registration of the SoR container in the current power cycle registration in the VPLMN. At the same time, the HPLMN may note in the subscription information in the UDM that the UE is expected to receive roaming guidance information due to initial registration or due to a mobility registration triggered before successful registration of the SoR container in the current power cycle registration in the VPLMN. In this case, the HPLMN provides the UE with roaming guidance information during initial registration or during a mobility registration triggered before successful registration of the SoR container in the current power cycle registration in the VPLMN. Otherwise, if such a configuration is not provided in the SIM or USIM, it is optional for the HPLMN (e.g., based on operator policy) to provide the UE with roaming guidance information during initial registration or during a mobility registration triggered before successful reception of the SoR container in the current power cycle.

[0018] In an embodiment for directing a UE during registration in a VPLMN, as described in further detail below, the 5GS Registration Type IE in the received Registration Request message indicates "Initial Registration" or "Mobility Registration Update", and the "SoR Update Indicator for Initial Registration" field in the UE context is set to indicate that the UDM requests the AMF to retrieve SoR information when the UE performs a NAS registration type "Initial Registration" or "Mobility Registration Update" (e.g., as specified in Table 5.2.2.2.2-1 of 3GPP TS 23.502).

[0019] In addition, or in other embodiments, if the user subscription information indicates that roaming guidance information is to be sent because of an initial registration or because of a mobility registration triggered before a successful registration of an SoR container in a current power cycle registration in the VPLMN, the HPLMN UDM provides the roaming guidance information to the UE when the UE performs an initial registration or a mobility registration triggered before a successful registration of an SoR container in a current power cycle registration in the VPLMN. Otherwise, the HPLMN UDM may provide the roaming guidance information to the UE based on operator policy.

[0020] In an embodiment, for mobility registration and periodic registration updates accepted by the network (e.g., see 3GPP TS 24.501, section 5.5.1.3.4), if (a) an indication is configured in the UE's USIM that the UE will receive the SoR Transparent Container IE, the UE has not received the SoR container in the current power cycle, and the SoR Transparent Container IE is not included in the REGISTRATION ACCEPT message or the SoR Transparent Container IE does not pass the integrity check (see 3GPP TS 33.501), and (b) the UE attempts to acquire service on another PLMN as specified in 3GPP TS 23.122, annex C, the UE locally releases the established N1 NAS signaling connection after sending the REGISTRATION COMPLETE message.

[0021] Additionally, or in other embodiments of mobility registration and periodic registration updates accepted by the network (see, for example, 3GPP TS 24.501, section 5.5.1.3.4), if the REGISTRATION ACCEPT message includes a SOR Transparent Container IE and the SOR Transparent Container IE passes the integrity check (see 3GPP TS 33.501), (a) the UE proceeds with its behavior as specified in 3GPP TS 23.122, annex C, and (b) if the registration procedure is performed over 3GPP access and the UE attempts to obtain service on another PLMN as specified in 3GPP TS 23.122, annex C, the UE may locally release the established N1 NAS signaling connection after sending the REGISTRATION COMPLETE message. Otherwise, the UE sends a REGISTRATION COMPLETE message and does not locally release the current N1 NAS signaling connection. If an acknowledgement was requested in the SOR Transparent Container IE of the REGISTRATION ACCEPT message, the UE's acknowledgement is included in the SOR Transparent Container IE of the REGISTRATION COMPLETE message.

[0022] Additionally, or in other embodiments of mobility registration and periodic registration updates accepted by the network (see, for example, 3GPP TS 24.501, section 5.5.1.3.4), if the SOR Transparent Container IE passes the integrity check (see 3GPP TS 33.501) indicating that a list of preferred PLMN / access technology combinations is provided, and (a) if the list type indicates "PLMN identity and access technology list", the UE shall overwrite the highest priority entry in the "operator managed PLMN selector and access technology" list stored in the UE and proceed with the behavior as specified in 3GPP TS 23.122, annex C; or (b) if the list type indicates "secured packet", the UE shall behave as if a Short Message Service (SMS) was received with the protocol identifier set to SIM data download, the data encoding scheme set to class 2 message, and the SMS payload as the secured packet content of the SOR Transparent Container IE. The SMS payload is transferred to the Universal Integrated Circuit Card (UICC) as specified in 3GPP TS 23.040 and the UE proceeds to behave as specified in 3GPP TS 23.122, annex C.

[0023] In some embodiments, as long as the USIM indicates that the UE expects to receive roaming guidance information due to initial registration in the VPLMN, the UE performs initial registration until a valid SoR is received in the visited country instead of triggering mobility registration and periodic registration. In some such embodiments, the initial registration initiation procedure (e.g., see 3GPP TS 24.501, section 5.5.1.2.2) is modified to allow a UE in 5GMM-DEREGISTERED state to initiate a REGISTRATION initiation when: (a) the UE performs initial registration for 5GS services; (b) the UE performs initial registration for emergency services; (c) the UE performs initial registration for SMS via the NAS; (d) the UE moves from GERAN to NG-RAN coverage or the UE moves from UTRAN to NG-RAN coverage and the UE initiates a GPRS Attach or Routeing Area Update procedure while in A / Gb mode or Iu mode and thereafter the UE does not successfully complete an EPS Attach or Tracking Area Update procedure in S1 mode or a Registration procedure in N1 mode; and (e) the UE has not yet successfully received an SoR container in the VPLMN and the UE's USIM is configured to indicate that the UE is expected to receive roaming guidance information during the initial registration procedure. It specifies that the registration procedure for initial registration is initiated by sending a REQUEST message to the AMF.

[0024] Thus, according to one or more of the embodiments disclosed herein, the UE is able to detect if a VPLMN has changed or removed its SoR information and consider such VPLMN as the lowest priority PLMN. Furthermore, the disclosed embodiments benefit both the operator and the user, since the UE avoids remaining on a low priority PLMN and selects a high priority PLMN indicated by the HPLMN in the SoR container. Thus, the disclosed embodiments help to prevent a rogue network from tampering with the SoR container check by triggering an initial LTE camp-on and then redirecting the UE to a 5G network where the SoR check is circumvented in this case.

[0025] 1 is a flow chart of a method 100 for a UE to communicate in a PLMN, according to one embodiment. At block 102, the method 100 includes generating, by the UE, a registration request message to be sent to the VPLMN, the registration request message including a registration type parameter indicating a mobility registration update. At block 104, the method 100 includes processing, by the UE, a registration accept message from the VPLMN. At block 106, the method 100 includes determining, by the UE, whether the registration accept message includes valid SoR information from the HPLMN. At block 108, the method 100 includes selectively performing a PLMN selection procedure based on whether the registration accept message includes valid SoR information from the HPLMN, in response to the UE being configured to receive SoR information during a mobility registration procedure and the UE not having received SoR information during a current power cycle of the UE.

[0026] In some embodiments of the method 100, a Subscriber Identity Module (SIM) or Universal SIM (USIM) of the UE is configured with an indication that the UE will receive an SoR transparent container in a registration accept message, the SoR transparent container including the SoR information. Determining whether the registration accept message includes a secure copy of the SoR information from the HPLMN may include determining whether the SoR transparent container passes an integrity check.

[0027] In a particular embodiment of the method 100, the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing a PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes: determining whether the registration accept message does not include SoR information or the SoR information has been changed by the VPLMN; setting the VPLMN as the lowest priority PLMN in a local list stored in the UE; locally releasing a non-access stratum (NAS) signaling connection after sending a registration complete message to the VPLMN; and performing a PLMN selection procedure based on the local list to attempt registration to a different PLMN.

[0028] In some embodiments of method 100, the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing a PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes determining that the registration accept message includes the SoR information and that the SoR information passes an integrity check, and performing a PLMN selection procedure based on the prioritized list. In one such embodiment, the SoR information includes a list type indicator that indicates that the prioritized list is a PLMN identifier (ID) and access technology list, and method 100 further includes replacing one or more highest priority entries in a local list stored in the UE with entries from the prioritized list. In another such embodiment, the SoR information includes a list type indicator indicating that the prioritized list includes a secured packet that received a Short Message Service (SMS) message, and the method 100 further includes processing the SMS message as if it was received with a protocol identifier set to a Subscriber Identity Module (SIM) data download, a data encoding scheme set to a Class 2 message, and an SMS payload as secured packet content in an SoR transparent container information element (IE), and forwarding the SMS payload to a Universal Integrated Circuit Card (UICC).

[0029] 2 is a flow chart of a method 200 for a UE according to another embodiment. At block 202, the method 200 includes triggering a first initial registration procedure with a first VPLMN. At block 204, the method 200 includes determining that a registration accept message from the first VPLMN does not include valid SoR information. At block 206, the method 200 includes disconnecting from the first VPLMN. At block 208, the method 200 includes attempting a second initial registration procedure with the second VPLMN instead of triggering a mobility registration or periodic registration with the second VPLMN.

[0030] Some embodiments of method 200 further include refraining from triggering mobility registration or periodic registration in the first VPLMN, the second VPLMN, or another VPLMN until valid SoR information is received, as long as an indication is configured in the UE's SIM or USIM that the UE expects to receive valid SoR information due to its initial registration in the VPLMN.

[0031] In some embodiments of method 200, the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0032] 3 is a flow chart illustrating a method 300 for an AMF in a wireless network. At block 302, the method 300 includes receiving a registration request message from a UE at the AMF, the registration request message including a registration type parameter indicating a mobility registration update. At block 304, the method 300 includes performing a mobility registration procedure at the AMF for the UE in the VPLMN in response to the registration request message, the registration procedure including receiving and storing UE context information at the AMF. At block 306, the method 300 includes determining that the UE context information includes a roaming guidance (SoR) indicator for mobility registration indicating that a UDM of the HPLMN requests the VPLMN to retrieve SoR information in response to the registration type parameter indicating a mobility registration update when a SoR container has not been delivered to the UE in a previous registration. At block 308, the method 300 includes retrieving SoR information from the UDM in response to the SoR indicator for mobility registration and delivering the SoR information to the UE in a registration accept message.

[0033] In some embodiments of the method 300, retrieving the SoR information from the UDM includes invoking a Nudm_SDM_Get service operation message to the UDM to retrieve the SoR information.

[0034] In some embodiments of the method 300, delivering the SoR information to the UE includes delivering an SoR container to the UE.

[0035] In some embodiments of method 300, the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies. The SoR information may further include a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies, or secured packets.

[0036] 4 is a flow chart of a method 400 for a HPLMN. At block 402, the method 400 includes configuring the UE to operate in accordance with the SoR configuration, which includes configuring the UE to determine if SoR information is included in a registration accept message associated with a mobility registration with the VPLMN. At block 404, the method 400 includes setting the UE context information to include an SoR indicator for the mobility registration indicating that the VPLMN is requested to retrieve the SoR information in response to a registration type parameter indicating a mobility registration update when a SoR container was not delivered to the UE in a previous registration. At block 406, the method 400 includes providing the SoR information in the SoR container to the VPLMN for forwarding to the UE in response to a request from the VPLMN.

[0037] Some embodiments of the method 400 further include securing the SoR container using a key shared with the UE.

[0038] In some embodiments of method 400, the SoR configuration further includes configuring the UE to lower a priority of the VPLMN if the UE determines that the SoR container is not present in a registration accept message associated with mobility registration with the VPLMN or that the SoR container fails an integrity check.

[0039] In some embodiments of method 400, the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0040] In some embodiments of method 400, the SoR information further includes a list type indicator that indicates that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0041] 5A and 5B show a data flow diagram 500 of an example registration procedure according to one embodiment. The illustrated registration procedure is based on the registration call flow described in 3GPP TS 23.502 section 4.2.2.2.2, but modified according to some embodiments disclosed herein. The UE 502 registers with the network to be authorized to receive services, to enable mobility tracking, and to enable reachability. The UE 502 initiates the registration procedure using one of the following registration types: initial registration to 5GS; mobility registration update when changing to a new Tracking Area (TA) outside the UE's registration area in both CM-CONNECTED and CM-IDLE states, or when the UE needs to update its capabilities or protocol parameters negotiated in the registration procedure with or without changes to the new TA, due to a change in the UE's preferred network behavior that may create an incompatibility with the supported network behavior provided by the serving AMF, or when the UE intends to retrieve LADN information; periodic registration update (due to a predefined period of inactivity); or emergency registration.

[0042] As mentioned above, the UE context information stored in the AMF504 has been extended to include an indicator "SoR Update Indicator for Mobility Registration" to indicate whether the UDM506 requests the AMF504 to retrieve SoR information when the UE502 performs mobility registration with NAS registration type "Mobility Registration" when no SoR container was delivered to the UE in the previous registration.

[0043] In step 508 of FIG. 5B, if the AMF 504 (or the old AMF) does not have the subscription data of the UE 502, the AMF 504 retrieves the access and mobility subscription data, the SMF selection subscription data, the UE context in the SMF data, and the LCS mobile origination using Nudm_SDM_Get. If the AMF 504 already has the subscription data of the UE but the SoR update indicator in the UE context requires the AMF to retrieve the SoR information depending on the NAS registration type ("initial registration" or "emergency registration" or "mobility registration") (see Annex C of TS 23.122), the AMF 504 retrieves the roaming guidance information using Nudm_SDM_Get. The UDM 506 may retrieve this information from the UDR by Nudr_DM_Query. After receiving a successful response, the AMF 504 may subscribe to be notified using Nudm_SDM_Subscribe when the requested data is modified, and the UDM 506 may subscribe to the UDR by Nudr_DM_Subscribe. If GPSI is available in the UE subscription data, the GPSI is provided to the AMF 504 in the access and mobility subscription data from the UDM 506. The UDM 506 may provide an indication that the subscription data for network slicing has been updated for the UE 502. If the UE 502 is subscribed to MPS in the serving PLMN, the access and mobility subscription data provided to the AMF 504 includes "MPS priority". If the UE 502 is subscribed to MCX in the serving PLMN, the access and mobility subscription data provided to the AMF 504 includes "MCX priority". The UDM 506 also provides an indication of IAB operation permission to the AMF 504 as part of the access and mobility subscription data. The AMF 504 triggers the setup of the UE context in the NG-RAN or the modification of the UE context in the NG-RAN, including an indication that the IAB node is authorized, if the initial setup is as per step 9c described in 3GPP TS 23.502 section 4.2.2.2.2.

[0044] FIG. 6 illustrates a data flow diagram 600 of an example method for steering a UE 602 in a VPLM during registration, according to one embodiment. The illustrated method is based on the control plane solution for roaming steering in 5GS described in 3GPP TS23.122 Annex C, but modified according to some embodiments described herein. The objective of this control plane solution for roaming steering in 5GS procedures is to enable the HPLMN to update the "operator managed PLMN selector and access technology" list in the UE 602 by providing a protected list of preferred PLMN / access technology combinations to the HPLMN via NAS signaling. If the selected PLMN is a VPLMN, the HPLMN can provide roaming steering information to the UE 602 using control plane mechanisms during and after registration. If the selected PLMN is a HPLMN, the HPLMN can provide roaming steering information to the UE 602 using control plane mechanisms only after registration. The HPLMN updates the "operator managed PLMN selector and access technology" based on operator policy, which can be based on the registered VPLMN, the location of the UE 602, etc.

[0045] The HPLMN may configure the USIM of the subscriber UE to indicate that the UE 602 is expected to receive roaming guidance information due to initial registration or due to a mobility registration triggered before the successful registration of the SoR container in the current power cycle registration in the VPLMN. At the same time, the HPLMN notes in the subscription information in the UDM 606 that the UE 602 is expected to receive roaming guidance information due to initial registration or due to a mobility registration triggered before the successful registration of the SoR container in the current power cycle registration in the VPLMN. In this case, the HPLMN is obliged to provide the roaming guidance information to the UE 602 during the initial registration or during a mobility registration triggered before the successful registration of the SoR container in the current power cycle registration in the VPLMN. Otherwise, if such a configuration is not provided in the USIM, it is optional (based on the operator policy) for the HPLMN to provide the roaming guidance information to the UE 602 during the initial registration or during a mobility registration triggered before the successful reception of the SoR container in the current power cycle. In this example, the User Data Repository (UDR) is considered part of the UDM 606 .

[0046] Since the HPLMN needs to take into account certain criteria, including the number of customers distributed across multiple VPLMNs within the same country or region, the list of preferred PLMN / access technology combinations may not always be the same for all users. The list of preferred PLMN / access technology combinations needs to be dynamically generated, e.g., on demand, by a dedicated roaming guidance application function (SOR-AF608) providing operator specific data analysis solutions.

[0047] To support various deployment scenarios, the UDM 606 supports using a PLMN / access technology preferred combination list or secured packets that is or becomes available to the UDM 606, obtaining the PLMN / access technology preferred combination list or secured packets from the SOR-AF 608, or both. HPLMN policies for SOR-AF 608 invocations can exist in the UDM 606 only if the UDM 606 supports obtaining the PLMN / access technology preferred combination list or secured packets from the SOR-AF 608.

[0048] If the UE's USIM is configured to indicate that the UE 602 is expected to receive roaming guidance information during the initial registration procedure but does not receive such information or the security check on the roaming guidance information fails and the currently selected VPLMN is not included in the "PLMNs Aborted Registration Due to SoR" list and the currently selected VPLMN is not part of the "User Controlled PLMN Selector with Access Technology" list and the UE 602 is not in manual operation mode, then the UE 602 performs PLMN selection considering the current VPLMN as the lowest priority.

[0049] Both while UE 602 is attempting to register with the VPLMN and after UE 602 has registered with the VPLMN, the VPLMN transparently forwards the roaming guidance information received from the HPLMN to UE 602 and transparently forwards the acknowledgement of successful reception of the roaming guidance information received from UE 602 to the HPLMN. If the last received roaming guidance information contains a "list of preferred PLMN / access technology combinations", the ME does not delete the "operator managed PLMN selector and access technology" list when UE 602 is powered off. The ME deletes the "operator managed PLMN selector and access technology" list stored in the ME when a new USIM is inserted.

[0050] 6, the selected PLMN is a VPLMN and the AMF 604 is located within the selected VPLMN. For the illustrated steps described below, security protection may be described in 3GPP TS 33.501.

[0051] In step 1 (UE 602 to VPLMN AMF 604), the UE initiates an initial registration, emergency registration, or mobility registration update procedure to the VPLMN AMF by sending a REGISTRATION REQUEST message with a 5GS registration type IE indicating "initial registration", "emergency registration", or "mobility registration update".

[0052] In step 2, upon receiving the REGISTRATION REQUEST message, the VPLMN AMF 604 performs the registration procedure as defined in section 4.2.2.2.2 of 3GPP TS 23.502. As part of the registration procedure, (a) if the VPLMN AMF does not have the subscription data of the UE 602, the VPLMN AMF invokes a Nudm_SDM_Get service operation to the HPLMN UDM 606 to obtain, among other information, the access and mobility subscription data of that UE (see step 14b of section 4.2.2.2.2 of 3 GPP TS 23.502). or (b) the VPLMN AMF already has the subscription data of the UE, and i) the 5GS Registration Type IE in the received Registration Request message indicates “Initial Registration” or “Mobility Registration Update” and the “SoR Update Indicator for Initial Registration” field in the UE context is set to “The UDM requests the AMF to retrieve SoR information when the UE performs a NAS registration type “Initial Registration” or “Mobility Registration Update” as specified in Table 5.2.2.2.2-1 of 3GPP TS 23.502”, or ii) the 5GS Registration Type IE in the received Registration Request message indicates “Emergency Registration” and the “SoR Update Indicator for Emergency Registration” field in the UE context is set to “The UE performs a NAS registration type “Initial Registration” or “Mobility Registration Update” as specified in Table 5.2.2.2.2-1 of 3GPP TS 23.502”, If "UDM requests AMF to retrieve SoR information when performing NAS registration type "emergency registration" as specified in Table 5.2.2.2.2-1 of TS 23.502" is configured, the VPLMN AMF invokes a Nudm_SDM_Get service operation message to the HPLMN UDM to retrieve roaming guidance information (see step 14b of clause 4.2.2.2.2 of 3GPP TS 23.502). Otherwise, the VPLMN AMF sends a registration accept message to the UE without roaming guidance information and steps 3a, 3b, 3c, 3d, 4, 5, 5a, 6 are skipped.

[0053] In step 3a, if the user subscription information indicates to send roaming guidance information due to initial registration or due to mobility registration triggered before successful registration of the SoR container in the current power cycle registration in the VPLMN, the HPLMN UDM 606 provides the roaming guidance information to the UE 602 when the UE 602 performs initial registration or mobility registration triggered before successful registration of the SoR container in the current power cycle registration in the VPLMN. In other cases, the HPLMN UDM may provide the roaming guidance information to the UE based on the operator policy.

[0054] If the HPLMN UDM is to provide roaming guidance information to the UE when the UE performs registration in the VPLMN and there is no HPLMN policy for SOR-AF608 invocation, steps 3b and 3c are not performed.

[0055] If the HPLMN UDM is to provide roaming guidance information to the UE when the UE performs registration in the VPLMN and if there is an HPLMN policy for SOR-AF paging, the HPLMN UDM obtains a list of preferred PLMN / access technology combinations or secured packets from the SOR-AF using steps 3b and 3c.

[0056] In step 3b (HPLMN UDM 606 to SOR-AF 608), Nsoraf_SoR_Obtain request (VPLMN ID, SUPI of UE 602, Access Type (see 3GPP TS 29.571)). The VPLMN ID and Access Type parameters, which indicate where the UE is trying to register, are stored in the HPLMN UDM.

[0057] In step 3c (SOR-AF 608 to HPLMN UDM 606), Nsoraf_SoR_Obtain response (PLMN / access technology preferred combination list, or secured packets, or neither). Based on the information received in step 3b and operator specific criteria, if any, the SOR-AF may include a PLMN / access technology preferred combination list or secured packets in the Nsoraf_SoR_Obtain response, or may provide an Nsoraf_SoR_Obtain response without a PLMN / access technology preferred combination list or secured packets. In some implementations, when the access type with which the UE 602 is registering indicates 3GPP access, the UE is registering via an NG-RAN access technology. Based on the operator's deployment and policies, if the UDM receives a list of preferred PLMN / access technology combinations in the Nsoraf_SoR_Obtain response from the SOR-AF and the UDM supports communication with the SP-AF, the UDM may send this list to the SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544. Even if the same VPLMN ID, UE SUPI and access type are provided to the SOR-AF, the SOR-AF may include a different list of preferred PLMN and access technology combinations or a different secured packet for each Nsoraf_SoR_Obtain request. The SOR-AF may subscribe to the HPLMN UDM to be informed of changes in the roaming status of the UE identified by the SUPI.

[0058] In step 3d), the HPLMN UDM 606 forms roaming guidance information as specified in 3GPP TS 33.501 from the PLMN / access technology preferred combination list or secured packet obtained in step 3a or the PLMN / access technology preferred combination list or secured packet obtained in step 3c. If in step 3a or 3c no list of preferred PLMN and access technology combinations or secured packets are obtained or if the SOR-AF 608 does not send a Nsoraf_SoR_Obtain response to the HPLMN-UDM within the operator defined time after the HPLMN-UDM sent a Nsoraf_SoR_Obtain request to the SOR-AF (step 3b) (step 3c) and the UE 602 has performed initial registration in a VPLMN and the user subscription information indicates to send roaming guidance information resulting from the initial registration in the VPLMN, then the HPLMN UDM forms the roaming guidance information as specified in 3GPP TS 33.501 from the HPLMN indication that "no modification of the 'operator managed PLMN selector and access technology' list stored in the UE is required and therefore no list of preferred PLMN / access technology combinations is provided".

[0059] In step 4 (HPLMN UDM 606 to VPLMN AMF 604), the HPLMN UDM sends a response to the Nudm_SDM_Get service operation to the VPLMN AMF, which includes the roaming guidance information in the Access and Mobility Subscription Data. The Access and Mobility Subscription data type is defined in clause 5.2.3.3.1 of 3GPP TS 23.502. The HPLMN may also request the UE 602 to return a positive acknowledgement of the success of the security check of the received roaming guidance information by providing an indication thereof as part of the roaming guidance information in the Nudm_SDM_Get response service operation.

[0060] In step 5 (VPLMN AMF 604 to HPLMN UDM 606), as part of the registration procedure, the VPLMN AMF also invokes the Nudm_SDM_Subscribe service operation to the HPLMN UDM to subscribe to notifications of changes to the subscription data received in step 4), including notifications of updates to the roaming guidance information contained in the access and mobility subscription data (see step 14c of section 4.2.2.2.2 of 3GPP TS 23.502).

[0061] In step 6 (VPLMN AMF 604 to UE 602), the VPLMN AMF transparently transmits the received roaming guidance information to the UE in a REGISTRATION ACCEPT message.

[0062] In step 7, if roaming guidance information is received and the security check is successful, perform (a) and (b): (a) If the roaming guidance information includes a secured packet (see 3GPP TS 31.115), if UDM 606 has not requested an acknowledgement from UE 602, UE 602 sends a REGISTRATION COMPLETE message without a SOR transparent container and the ME uploads the secured packet to the USIM using the procedures in 3GPP TS 31.111. If UDM has not requested an acknowledgement from the UE and the ME has received a USAT REFRESH command modifier (3GPP TS 31.111) of type "Steering of Roaming", UDM performs items a), b) and c) of the procedure for roaming guidance in subclause 4.4.6. Then, if the UE has a list of available and acceptable PLMNs in the area, and the UE determines based on this list that there is a PLMN of higher priority than the selected VPLMN, and the UE is in automatic network selection mode, the UE either does i) or ii): i) locally release the current N1 NAS signaling connection and then attempts to obtain service on the higher priority PLMN by acting as if timer T controlling periodic attempts had expired, as specified in subclause 4.4.3.3. In this case, steps 8 to 11 are skipped. If the UE has an established emergency PDU session (see 3GPP TS 24.501), the reception of the roaming guidance information does not trigger the release of the N1 NAS signaling connection. The UE locally releases the current N1 NAS signaling connection subsequently after the emergency PDU session is released. ii) does not locally release the current N1 NAS signaling connection and skips steps 8 to 10. (b) If the roaming guidance information includes a list of preferred PLMN / access technology combinations, the ME shall replace the highest priority entry in the "operator managed PLMN selector and access technology" list stored in the ME with the received list of preferred PLMN / access technology combinations.Furthermore, if the UDM does not require an acknowledgement from the UE, the UE has a list of available and acceptable PLMNs in the area, the UE determines based on this list that there is a PLMN of higher priority than the selected VPLMN, and the UE is in automatic network selection mode, the UE sends a REGISTRATION COMPLETE message to the serving AMF 604 without the SOR transparent container and does either i) or ii): i) locally release the current N1 NAS signaling connection and then attempt to obtain service on the higher priority PLMN by acting as if the timer T controlling the periodic attempts had expired, as specified in subclause 4.4.3.3. In this case, steps 8 to 11 are skipped. If the UE has an established emergency PDU session (see 3GPP TS 24.501), the reception of the roaming guidance information does not trigger the release of the N1 NAS signaling connection. The UE locally releases the current N1 NAS signaling connection subsequently after the emergency PDU session is released. ii) Do not locally release the current N1 NAS signaling connection and skip steps 8 and 10.

[0063] In step 8, if (a) an indication is set in the UE's USIM that the UE 602 will receive roaming guidance information due to initial registration in the VPLMN, but no list of preferred PLMN / access technology combinations, no secured packets, and no HPLMN indication "no change to the 'operator managed PLMN selector and access technology' list stored in the UE is required and therefore no list of preferred PLMN / access technology combinations is provided" has been received in the REGISTRATION ACCEPT message and the UE performs initial registration in the VPLMN, or the roaming guidance information is received but the security check is not successful, and (b) the currently selected VPLMN is not included in the "PLMNs for which registration has been aborted due to SoR" list and is not part of the "User managed PLMN selector and access technology" list and the UE is not in manual operation mode, the UE sends a REGISTRATION COMPLETE message to the serving AMF 604 without the SoR transparent container and updates the current N1 Release the NAS signaling connection locally, store the PLMN identity in the "PLMNs with registration aborted due to SoR" list, and attempt to obtain service on a higher priority PLMN by acting as if the timer T controlling the periodic attempts had expired as specified in subclause 4.4.3.3, with the exception that the current PLMN is considered as the lowest priority, skipping steps 9 to 12. If the UE has an established emergency PDU session (see 3GPP TS 24.501), the UE locally releases the current N1 NAS signaling connection after release of the emergency PDU session. When the UE is in manual operation mode or the currently selected VPLMN is part of the "User Managed PLMN Selector and Access Technology" list, the UE stays on that VPLMN.

[0064] In step 9 (UE 602 to VPLMN AMF 604), if the UDM 606 requested an acknowledgement from the UE, the UE has verified that the roaming guidance information was provided by the HPLMN in step 7, and the UE sends a REGISTRATION COMPLETE message to the serving AMF along with a SOR transparent container containing the UE acknowledgement, and if the roaming guidance information contains a secured packet and the security check is successful, the UE performs items a), b) and c) of the roaming guidance procedure in subclause 4.4.6 upon receiving a USAT REFRESH command modifier of type "Steering of Roaming".

[0065] In step 10 (VPLMN AMF 604 to HPLMN UDM 606), if the SOR Transparent Container is received in the REGISTRATION COMPLETE message, the AMF provides the received SOR Transparent Container to the UDM using the Nudm_SDM_Info service operation. If the HPLMN determined in step 4 that the UE 602 is to acknowledge the success of the security check of the received roaming guidance information, the UDM verifies that an acknowledgment was provided by the UE as specified in 3GPP TS 33.501.

[0066] Step 10a (HPLMN UDM 606 to SOR-AF 608), Nsoraf_SoR_Info (SUPI of UE 602, delivery successful). If HPLMN policy exists for SOR-AF invocation and the HPLMN UDM received and verified the UE acknowledgment in step 10, the HPLMN UDM informs the SOR-AF of the list of preferred combinations of PLMN and access technology or the successful delivery of the secured packet to the UE.

[0067] In step 11, if the UE 602 has a list of available PLMNs in the area and based on this list the UE determines that there is a PLMN of higher priority than the selected VPLMN and the UE is in automatic network selection mode, the UE attempts to obtain service on the higher priority PLMN after release of the N1 NAS signaling connection by acting as if timer T controlling periodic attempts had expired, as specified in subclause 4.4.3.3. If the N1 NAS signaling connection is not released after an implementation-dependent time, the UE may locally release the N1 signaling connection, except when the UE has an established emergency PDU session (see 3 GPP TS 24.501).

[0068] In step 12, the UE 602 deletes the "PLMNs Aborted Due to SoR" list.

[0069] When the UE is powered off or the USIM is removed, the "PLMNs for which registration has been discontinued due to SoR" list is deleted.

[0070] System architecture example

[0071] In some embodiments, the 5G system architecture supports data connectivity and services that enable deployment to use technologies such as network function virtualization and software defined networks. The 5G system architecture can leverage service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows for independent scalability, evolution, and flexible deployment (e.g., centralized or distributed (remote) deployment). Modularized function design allows for reuse of functions, enabling flexible and efficient network slicing. A network function and its network function services can directly or indirectly interact with another NF and its network function services via a service communication proxy. Another intermediate function can assist in routing of control plane messages. The architecture minimizes dependencies between the AN and the CN. The architecture can include a converged core network with a common AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture also supports a unified authentication framework, stateless NFs where computational resources are separated from storage resources, functionality exposure, simultaneous access to local and centralized services (to support low latency services and access to local data networks, user plane functions may be deployed in close proximity to the AN), and / or roaming for both home routed traffic and local breakout traffic within visited PLMNs.

[0072] The 5G architecture may be defined as service-based, and interactions between network functions may include service-based representations, where network functions in the control plane (e.g., AMF) allow other authorized network functions to access their services. The service-based representations may also include point-to-point reference points. Reference point representations may also be used to indicate interactions between NF services in network functions described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0073] FIG. 7 illustrates a service-based architecture 700 in 5GS according to one embodiment. As described in 3GPP TS23.501, the service-based architecture 700 includes NFs such as NSSF708, NEF710, NRF714, PCF712, UDM726, AUSF718, AMF720, SMF722, etc., for communicating with UE716, (R)AN706, UPF702, and DN704. NFs and NF services can communicate directly, referred to as direct communication, or indirectly via SCP724, referred to as indirect communication. FIG. 7 also illustrates corresponding service-based interfaces, including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf, and Nausf, and reference points N1, N2, N3, N4, and N6. Some example functions provided by the NFs illustrated in FIG. 7 are described below.

[0074] The NSSF708 supports functions such as selecting a set of network slice instances to serve the UE, determining the allowed NSSAI and mapping it to a subscribed S-NSSAI, if necessary, determining the configured NSSAI and mapping it to a subscribed S-NSSAI, if necessary, and / or determining the AMF set that will be used to serve the UE or determining a list of candidate AMF(s) based on the configuration, possibly by querying the NRF.

[0075] The NEF 710 supports the publication of functions and events. NF functions and events can be securely published by the NEF 710 (e.g., for third parties, application functions, and / or edge computing). The NEF 710 can store / retrieve information as structured data using a standardized interface (Nudr) to the UDR. The NEF 710 can also secure the provision of information from external applications to the 3GPP network and provide application functions to securely provide information (e.g., expected UE behavior, 5G LAN group information, and service specific information) to the 3GPP network, where the NEF 710 can authenticate, authorize, and assist in the coordination of application functions. The NEF 710 can provide internal-external information translation by translating between information exchanged with the AF and information exchanged with internal network functions. For example, the NEF 710 translates between AF service identifiers and internal 5G core information such as DNN and S-NSSAI. The NEF 710 can handle the masking of network and user sensitive information to the external AF according to network policies. The NEF 710 can receive information from other network functions (based on their exposed capabilities) and store the received information in the UDR using standardized interfaces. The stored information can then be accessed by the NEF 710 and re-exposed to other network and application functions and used for other purposes such as analytics. For external exposure of services related to a particular UE(s), the NEF 710 can be in the HPLMN. Depending on the operator's agreement, the NEF 710 in the HPLMN can have interface(s) with NF(s) in the VPLMN. If the UE is capable of switching between EPC and 5GC, the SCEF+NEF can be used for service exposure.

[0076] The NRF 714 supports service discovery functionality by receiving NF discovery requests from NF instances or SCPs and providing information of discovered NF instances to the NF instances or SCPs. The NRF 714 also supports P-CSCF discovery (a special case of AF discovery by the SMF), maintains NF profiles of available NF instances and their supported services, and / or can notify subscribed NF service consumers or SCPs about newly registered / updated / deregistered NF instances along with their NF services. In the context of network slicing, based on the network implementation, multiple NRFs may be deployed at various levels, such as at the PLMN level (the NRF is configured with information about the entire PLMN), at the shared slice level (the NRF is configured with information belonging to a set of network slices), and / or at a slice-specific level (the NRF is configured with information belonging to the S-NSSAI). In the context of roaming, multiple NRFs may be deployed in different networks, where an NRF(s) in a visited PLMN (known as a vNRF) is configured with information about the visited PLMN, and an NRF(s) in a home PLMN (known as a hNRF) is configured with information about the home PLMN referenced by the vNRF via the N27 interface.

[0077] The PCF 712 supports a unified policy framework to manage network behavior. The PCF 712 provides policy rules to the control plane function(s) and enforces them. The PCF 712 accesses subscription information relevant to policy decisions in a unified data repository (UDR). The PCF 712 can access a UDR located in the same PLMN as the PCF.

[0078] The UDM 726 supports generation of 3GPP AKA authentication credentials, user identification handling (e.g., storage and management of per-subscriber SUPI in 5G systems), deciphering of privacy-preserving subscription identifiers (SUCI), access authorization based on subscription data (e.g., roaming restrictions), serving NF registration management for the UE (e.g., storing the serving AMF for the UE, storing the serving SMF for the UE's PDU sessions), service / session continuity (e.g., by maintaining SMF / DNN assignments for ongoing sessions), MT-SMS delivery, lawful interception functionality (especially in the case of outbound roaming where the UDM is the only point of contact for the LI), subscription management, SMS management, 5G LAN group management handling, and / or external parameter provisioning (expected UE behavior parameters or network configuration parameters). To provide such functionality, the UDM 726 uses subscription data (including authentication data) that may be stored in the UDR, in which case the UDM implements the application logic and may not require internal user data storage, and several different UDMs may serve the same user in different transactions. The UDM 726 may be located in the HPLMN of the subscribers it serves and may have access to information of UDRs located in the same PLMN.

[0079] The AF 728 interacts with the core network to provide services supporting, for example, application influence on traffic routing, access to the NEF 710, interaction with the policy framework for policy control, and / or IMS interaction with the 5GC. Based on an operator's deployment, application functions that are deemed trusted by the operator may interact directly with the associated network functions. Application functions that do not have direct access to network functions by the operator may interact with the associated network functions using an external exposure framework via the NEF 710.

[0080] AUSF718 supports authentication for 3GPP access and untrusted non-3GPP access. AUSF718 can also provide network slice-specific authentication and authorization support.

[0081] The AMF 720 supports termination of the RAN CP interface (N2), termination of the NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interface to the LI system), transport of SM messages between the UE and the SMF, transparent proxy for routing SM messages, access authentication, access authorization, transport of SMS messages between the UE and the SMSF, the SEAF, location service management for barring services, transport of location service messages between the UE and the LMF and between the RAN and the LMF, EPS bearer ID allocation for interworking with the EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, provisioning of external parameters (expected UE behavior parameters or network configuration parameters), and / or network slice specific authentication and authorization. Some or all of the AMF functions may be supported within a single instance of the AMF 720. Regardless of the number of network functions, in a particular embodiment, there is only one NAS interface instance per access network between the UE and the CN, terminating in one of the network functions that implements at least NAS security and mobility management. The AMF 720 may also include policy-related functions.

[0082] In addition to the above-mentioned functions, the AMF 720 may include the following functions to support non-3GPP access networks: support of an N2 interface with the N3IWF / TNGF, where some information (e.g., 3GPP cell identification) and procedures (e.g., handover related) defined on 3GPP access may not apply and non-3GPP access specific information that does not apply to 3GPP access may apply, support of NAS signaling with the UE on the N3IWF / TNGF, where some procedures supported by NAS signaling on 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access, support of authentication of UE connected via the N3IWF / TNGF, management of mobility, authentication, and separate security context state(s) of UE connected via non-3GPP access or connected simultaneously via 3GPP access and non-3GPP access; support of coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support of a CM management context dedicated to the UE for connection via non-3GPP access. It may not be necessary for all of the above functions to be supported within an instance of a network slice.

[0083] The SMF 722 supports session management (e.g., session establishment, modification, teardown, including tunnel maintenance between the UPF and AN nodes), UE IP address allocation and management (including optional authorization), where the UE IP address may be received from the UPF or from an external data network, DHCPv4 (server and client) and DHCPv6 (server and client) functions, functions that respond to Address Resolution Protocol requests and / or IPv6 Neighbor Solicitation requests based on local cache information for Ethernet PDUs (e.g., the SMF responds to ARP and / or IPv6 Neighbor Solicitation requests by providing a MAC address corresponding to the IP address sent in the request), selection and control of user plane functions, including controlling the UPF to proxy ARP or IPv6 Neighbor Discovery or forwarding all ARP / IPv6 Neighbor Solicitation traffic to the SMF for Ethernet PDU sessions, traffic steering configuration in the UPF to route traffic to the appropriate destination, 5G VN group management (e.g., maintaining the topology of the associated PSA UPFs, PSA Establishment and teardown of N19 tunnels between UPFs, configuration of traffic forwarding in the UPF to apply local switching and / or N6 based forwarding or N19 based forwarding), termination of interface to policy control function, Lawful Interception (for SM events and interface to LI system), collection of charging data and support of charging interface, control and coordination of charging data collection in the UPF, termination of SM part of NAS message, downlink data notification, initiation of AN specific SM information sent from N2 to AN via AMF, determination of SSC mode of session, control plane CIoT 5GS optimization, header compression, functioning as I-SMF in deployments where I-SMF can be inserted / removed / relocated, provisioning of external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery of IMS services, roaming functionality (e.g. handling local enforcement and QoSThis includes enforcing SLAs (VPLMN), charging data collection and charging interface (VPLMN), and / or lawful intercept (for interface to VPLMN and LI systems for SM events), interacting with external DNs for forwarding signaling for PDU session authentication / authorization by the external DN, and / or instructing the UPF and NG-RAN to perform redundant transmission on the N3 / N9 interface. Some or all of the SMF functions may be supported within a single instance of the SMF. However, in certain embodiments, it is not necessary that all of the functions be supported within an instance of a network slice. In addition to this function, the SMF 722 may include policy-related functions.

[0084] The SCP 724 includes any one or more of the following: indirect communication, delegation discovery, message forwarding and routing to destination NF / NF service, communication security (e.g., authorization of NF service consumers to access NF service producers' APIs), load balancing, monitoring, overload control, etc., and / or optionally interacting with UDRs to resolve UDM Group ID / UDR Group ID / AUSF Group ID / PCF Group ID / CHF Group ID / HSS Group ID based on UE ID (SUPI or IMPI / IMPU, etc.). Some or all of the SCP functions may be supported within a single instance of an SCP. In certain embodiments, the SCP 724 may be deployed in a distributed manner and / or more than one SCP may be in the communication path between NF services. SCPs may be deployed at the PLMN level, the shared slice level, and the slice-specific level. It may be up to the operator to ensure that the SCP communicates with the associated NRF.

[0085] The UE 716 may include devices having wireless communication capabilities. For example, the UE 716 may include a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more cellular networks). The UE 716 may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or any computing device that includes a wireless communication interface. A UE may also be referred to as a client, a mobile, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio device, a reconfigurable radio device, or a reconfigurable mobile device. The UE 716 may comprise an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize a technology (e.g., M2M technology, MTC technology, or mMTC technology) for exchanging data with other UEs over the PLMN, an MTC server or device, ProSe or D2D communication, a sensor network, or an IoT network. M2M data exchange or MTC data exchange may be an exchange of machine initiated data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0086] The UE 716 may be configured to connect or communicatively couple with the (R)AN 706 via a radio interface 730, which may be a physical communication interface or layer configured to operate with a cellular communication protocol, such as a GSM protocol, a CDMAP network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, or the like. For example, the UE 716 and the (R)AN 706 may exchange control plane data via a protocol stack including a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer using a Uu interface (e.g., an LTE-Uu interface). DL transmissions may be from the (R)AN 706 to the UE 716, and UL transmissions may be from the UE 716 to the (R)AN 706. The UE 716 may further use a sidelink to directly communicate with another UE (not shown) for D2D, P2P, and / or ProSe communications. For example, the ProSe interface may alternatively be referred to as a sidelink interface and comprises one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0087] The (R)AN 706 includes one or more access nodes, which may be referred to as a base station (BS), Node B, evolved Node B (eNB), next generation Node B (gNB), RAN node, controller, transmit / receive point (TRP), etc., and may comprise a ground station (e.g., terrestrial access point) or satellite station that provides coverage within a geographic area (e.g., a cell). The (R)AN 706 may include one or more RAN nodes for providing a macrocell, a picocell, a femtocell, or other type of cell. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs with an association with the femtocell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, etc.).

[0088] Although not shown, multiple RAN nodes (such as (R)AN 706) may be used, where an Xn interface is defined between two or more nodes. In some implementations, the Xn interface may include an Xn User Plane (Xn-U) interface and an Xn Control Plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide mobility support for the UE 716 in connected mode (e.g., CM connected), including management and error handling functions, functions to manage the Xn-C interface, and functions to manage UE mobility in connected mode between one or more (R)AN nodes. Mobility support may include context transfer from an old (source) serving (R)AN node to a new (target) serving (R)AN node, and control of user plane tunnels between the old (source) serving (R)AN node and the new (target) serving (R)AN node.

[0089] The UPF 702 can function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnecting to the DN 704, and a branching point to support multi-homed PDU sessions. The UPF 702 can also perform packet routing and packet forwarding, packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection); traffic usage reporting, perform QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement) for the user plane, perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffer and downlink data notification triggers. The UPF 702 can include uplink classifiers to support routing traffic flows to the data network. The DN 704 can represent various network operator services, Internet access, or third party services. The DN 704 may include, for example, an application server.

[0090] 8 illustrates an example of infrastructure equipment 800 according to various embodiments. The infrastructure equipment 800 may be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any other element / device described herein. In other examples, the infrastructure equipment 800 may be implemented within or by a UE.

[0091] The infrastructure equipment 800 includes application circuitry 802, baseband circuitry 804, one or more radio front-end modules (RFEM) 806, memory circuitry 808, power management integrated circuit (shown as PMIC 810), power T circuitry 812, network controller circuitry 814, network interface connector 820, satellite positioning circuitry 816, and user interface circuitry 818. In some embodiments, the device infrastructure equipment 800 may include additional elements, such as, for example, memory / storage, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in two or more devices. For example, the circuits may be included separately in two or more devices for CRAN, vBBU, or other similar implementations. The application circuitry 802 may include, but is not limited to, one or more processors (or processor cores), cache memory, as well as low dropout regulators (LDOs), interrupt controllers, SPI, I / O, and other similar implementations. 2The application circuitry 802 may include one or more of the following circuits: a serial interface such as a universal programmable serial interface module (UPLC), a real-time clock (RTC), timer counters including interval and watchdog timers, a general purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC), a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. A processor (or core) of the application circuitry 802 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage elements to enable various applications or operating systems to run on the infrastructure facility 800. In some implementations, the memory / storage elements may be on-chip memory circuits, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology as described herein.

[0092] The processor(s) of application circuitry 802 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuitry 802 may include or be a special purpose processor / controller that operates in accordance with various embodiments herein. As examples, the processor(s) of application circuitry 802 may include one or more Intel Pentium®, Core®, or Xeon® processor(s), Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Unit (APU), or Epyc® processor, ARM-based processor(s) licensed from ARM Holdings Ltd., such as the ARM Cortex-A family processors, and processors of MIPS-based designs offered by MIPS Technologies, Inc., such as ThunderX2® offered by Cavium™, Inc., MIPS Warrior P-class processors, etc. In some embodiments, infrastructure facility 800 may not utilize application circuitry 802, and instead may include a dedicated processor / controller for processing IP data received from, for example, an EPC or 5GC.

[0093] In some implementations, the application circuitry 802 may include one or more hardware accelerators, which may be a microprocessor, a programmable processing device, or the like. The one or more hardware accelerators may include, for example, a computer vision (CV) and / or a deep learning (DL) accelerator. As examples, the programmable processing device may be one or more of a field programmable device (FPD) such as a field programmable gate array (FPGA), a programmable logic device (PLD) such as a complex PLD (CPLD), a high capacity PLD (HCPLD), an ASIC such as a structured ASIC, a programmable SoC (PSoC), or the like. In such implementations, the circuitry of the application circuitry 802 may include logic blocks or logic fabrics and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions of various implementations described herein. In such an embodiment, the circuitry of the application circuitry 802 may include memory cells (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc., in look-up tables (LUTs), etc. The baseband circuitry 804 may be implemented, for example, as a soldered board containing one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0094] The user interface circuitry 818 may include one or more user interfaces designed to enable user interaction with the infrastructure facility 800, or peripheral component interfaces designed to enable peripheral component interaction with the infrastructure facility 800. The user interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio light emitting device, a microphone, a printer, a scanner, a headset, a display screen or device, etc. The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0095] The wireless front-end module 806 may include a millimeter-wave (mm-wave) radio front-end module (RFEM) and one or more sub-mm-wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mm-wave RFICs may be physically separate from the mm-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both mm-wave and sub-mm-wave wireless functions may be implemented within the same physical wireless front-end module 806 that incorporates both mm-wave and sub-mm-wave antennas.

[0096] The memory circuitry 808 may include one or more of volatile memory including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), and the like, and may incorporate Intel® and Micron® three-dimensional (3D) cross point (XPOINT) memory. The memory circuitry 808 may be implemented as one or more of a solder packaged integrated circuit, a socketed memory module, and a plug-in memory card.

[0097] The PMIC 810 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or a capacitor. The power alarm detection circuit may detect one or more of brownout (under-voltage) and surge (over-voltage) conditions. The power T-circuit 812 may supply power drawn from a network cable that provides both power and data connectivity to the infrastructure equipment 800 using a single cable.

[0098] The network controller circuitry 814 can provide connectivity to the network using a standard network interface protocol, such as Ethernet, Ethernet over GRE tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. The network connection may be provided using a physical connection to or from the infrastructure equipment 800 via the network interface connectors 820, which may be electrical (commonly referred to as "copper wiring"), optical, or wireless. The network controller circuitry 814 can include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 814 can include multiple controllers for providing connections to other networks using the same or different protocols.

[0099] The positioning circuitry 816 includes circuitry for receiving and decoding signals transmitted / broadcast by a Global Navigation Satellite System (GNSS) positioning network. Examples of navigation satellite constellations (or GNSS) include the United States Global Positioning System (GPS), the Russian Global Navigation System (GLONASS), the European Union's Galileo system, the Chinese BeiDou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., Navigation by Indian Constellation (NAVIC), the Japanese Quasi-Zenith Satellite System (QZSS), the French Doppler Orbitography and Radio positioning Integrated by Satellite (DORIS), etc.). The positioning circuitry 816 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communications) for communicating with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 816 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC for performing position tracking / estimation without GNSS assistance using a master timing clock. The positioning circuitry 816 may also be part of or interact with the baseband circuitry 804 and / or the wireless front-end module 806 to communicate with nodes and components of a positioning network. The positioning circuitry 816 may also provide position and / or time data to the application circuitry 802, which may use the data to synchronize operations with various infrastructures, etc. The components shown in FIG. 8 may communicate with each other using interface circuitry, which may include a number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Enhanced ISA (EISA), Peripheral Component Interconnect (PCI), Enhanced Peripheral Component Interconnect (PCix), PCI Express (PCie), or a number of other technologies. The bus / IX may be a proprietary bus, for example, used in SoC-based systems.Other bus / IX systems, notably I. 2 C interface, SPI interface, point-to-point interface, and power bus may also be included.

[0100] FIG. 9 illustrates an example platform 900 according to various embodiments. In an embodiment, the computer platform 900 may be suitable for use as a UE, an application server, and / or any other element / device discussed herein. The platform 900 may include any combination of components shown in the examples. The components of the platform 900 may be implemented as an integrated circuit (IC), a portion thereof, a separate electronic device, or other module, logic, hardware, software, firmware, or a combination thereof adapted to the computer platform 900, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 9 is intended to show an overhead view of the components of the computer platform 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0101] The application circuit 902 may include, but is not limited to, one or more processors (or processor cores), cache memory, and one or more LDOs, interrupt controllers, SPIs, I 2The application circuitry 902 may include circuits such as a serial interface such as a SPI, SPI-C, or universal programmable serial interface module, timer counters including RTC, interval and watchdog timers, general purpose IO, memory card controllers such as SD MMC, USB interface, MIPI interface, and JTAG test access port. The processor (or core) of the application circuitry 902 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage elements to enable various applications or operating systems to run on the platform 900. In some implementations, the memory / storage elements may be on-chip memory circuits, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and / or any other type of memory device technology as described herein.

[0102] The processor(s) of application circuitry 902 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, application circuitry 902 may include or be a special purpose processor / controller that operates in accordance with various embodiments herein.

[0103] By way of example, the processor of the application circuit 902 may include an Intel® Architecture Core® based processor, such as a Quark®, Atom®, i3, i5, i7, or MCU class processor, or another such processor available from Intel® Corporation. The processor of the application circuit 902 may also be one or more of an Advanced Micro Devices (AMD) Ryzen® processor or accelerated processing unit (APU); AS-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors, ARM-based designs licensed from ARM Holdings, Ltd, such as the ARM Cortex-A, Cortex-R, and Cortex-M families of processors, and the like. In some implementations, the application circuit 902 may be part of a system-on-chip (SoC) in which the application circuit 902 and other components are formed on a single integrated circuit or in a single package, such as an Edison™ or Galileo™ SoC board manufactured by Intel® Corporation.

[0104] Additionally or alternatively, application circuitry 902 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, programmable logic devices (PLDs) such as composite PLDs (CPLDs) and high capacity PLDs (HCPLDs), ASICs such as structured ASICs, programmable SoCs (PSoCs), etc. In such embodiments, the circuitry of application circuitry 902 may include logic blocks or logic fabrics and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, and functions of various embodiments described herein. In such embodiments, the circuitry of application circuitry 902 may include memory cells (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.) used to store logic blocks, logic fabric, data, etc., in look-up tables (LUTs), etc.

[0105] The baseband circuitry 904 may be implemented, for example, as a soldered board containing one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0106] The wireless front-end module 906 may include a millimeter-wave (mm-wave) radio front-end module (RFEM) and one or more sub-mm-wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mm-wave RFICs may be physically separate from the mm-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both mm-wave and sub-mm-wave wireless functions may be implemented within the same physical wireless front-end module 906 that incorporates both mm-wave and sub-mm-wave antennas.

[0107] The memory circuitry 908 may include any number and type of memory devices used to provide a given amount of system memory. By way of example, the memory circuitry 908 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (RAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 908 may be developed according to the Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR) based designs, such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuitry 908 may be implemented as one or more of a solder package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered onto a motherboard via a ball grid array (BGA). In a low power implementation, the memory circuitry 908 may be an on-die memory or register associated with the application circuitry 902. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuitry 908 may include one or more mass storage devices, which may include a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive memory, a phase change memory, a holographic memory, or a chemical memory, among others. For example, the computer platform 900 may incorporate a three-dimensional (3D) cross point (XPOINT) memory from Intel® and Micron®.

[0108] Removable memory circuitry 926 may include devices, circuits, enclosures, ports or receptacles, etc. used to couple portable data storage devices with platform 900. These portable data storage devices may be used for mass storage purposes and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD image cards, etc.), USB flash drives, optical disks, external HDDs, etc.

[0109] Platform 900 may also include interface circuitry (not shown) used to connect external devices with platform 900. External devices connected to platform 900 via the interface circuitry include sensors 922 and electromechanical components (shown as EMC 924), as well as a removable memory device coupled to a removable memory circuit 926.

[0110] The sensors 922 may include devices, modules, or subsystems intended to detect events or changes in the environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers, Microelectromechanical Systems (MEMS) or Nanoelectromechanical Systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, and / or magnetometers, level sensors, flow sensors, temperature sensors (e.g., thermistors), pressure sensors, barometric pressure sensors, gravimeters, altimeters, image capture devices (e.g., cameras or lensless apertures), Light Detection and Ranging (LiDAR) sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones or other similar audio capture devices, etc.

[0111] EMC 924 includes devices, modules, or subsystems whose purpose is to enable platform 900 to change its state, position, and / or orientation, or to move or control a mechanism or (sub)system. Additionally, EMC 924 may be configured to generate and send messages / signaling to other components of platform 900 to indicate a current state of EMC 924. Examples of EMC 924 include one or more power switches, relays including electromechanical relays (EMRs) and / or solid-state relays (SSRs), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In an embodiment, platform 900 is configured to operate one or more EMCs 924 based on one or more captured events and / or commands or control signals received from service providers and / or various clients. In some implementations, the interface circuitry may connect the platform 900 with a positioning circuitry 916. The positioning circuitry 916 includes circuitry for receiving and decoding signals transmitted / broadcast by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuitry 916 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communications) for communicating with components of the positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 916 may include a Micro-PNT IC for performing position tracking / estimation without GNSS assistance using a master timing clock.The positioning circuitry 916 may also be part of or interact with the baseband circuitry 904 and / or the wireless front-end module 906 to communicate with nodes and components of a positioning network. The positioning circuitry 916 may also provide position and / or time data to the application circuitry 902, which may use the data to synchronize operation with various infrastructures (e.g., wireless base stations), such as for turn-by-turn navigation applications.

[0112] In some implementations, the interface circuit may connect the platform 900 with a near-field communication circuit (shown as NFC circuit 912). The NFC circuit 912 is configured to provide contactless short-range communication based on the Radio Frequency Identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuit 912 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 900. The NFC circuit 912 comprises an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides the NFC circuit 912 with NFC functionality by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit a near-field RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 912, or may initiate data transfer between the NFC circuitry 912 and another active NFC device (e.g., a smartphone or NFC-enabled POS terminal) in proximity to the platform 900.

[0113] The driver circuitry 918 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the platform 900. The driver circuitry 918 may include individual drivers that enable other components of the platform 900 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 900. For example, the driver circuitry 918 may include a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to a touchscreen interface of the platform 900, a sensor driver for obtaining sensor readings of the sensor 922 and controlling and allowing access to the sensor 922, an EMC driver for obtaining actuator positions of the EMC 924 and / or controlling and allowing access to the EMC 924, a camera driver for controlling and allowing access to an embedded capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0114] A power management integrated circuit (denoted as PMIC 910) (also referred to as a "power management circuit") may manage the power supplied to various components of the platform 900. Specifically, with respect to the baseband circuitry 904, the PMIC 910 may control power source selection, voltage scaling, battery charging, or DC-DC conversion. The PMIC 910 may often be included when the platform 900 can be powered by a battery 914, for example, when this device is included in a UE.

[0115] In some embodiments, the PMIC 910 may control or otherwise be part of various power saving mechanisms of the platform 900. For example, if the platform 900 is in an RRC connected state and is still connected to a RAN node because it expects to receive traffic shortly, after some period of inactivity the platform may enter a state known as discontinuous reception mode (DRX). During this state the platform 900 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 900 may transition to an RRC_Idle state, where the platform disconnects from the network and does not perform operations such as channel quality feedback, handovers, etc. The platform 900 goes into a very low power state, performs paging, where it periodically wakes up again, listens to the network, and powers down again. The platform 900 cannot receive data in this state, and must transition to the RRC connected state to receive data. In further power saving modes, the device may be allowed to be unavailable from the network for longer than the paging interval (which can range from a few seconds to a few hours). During this time the device may not be able to reach the network at all and may be completely powered down. Any data sent during this time will be significantly delayed, but the delay is deemed acceptable.

[0116] A battery 914 may power the platform 900, although in some examples the platform 900 may be deployed and mounted at a fixed location and may have a power source coupled to a power grid. The battery 914 may be a lithium ion battery, a metal air battery such as a zinc air battery, an aluminum air battery, a lithium air battery, etc. In some implementations, such as for V2X applications, the battery 914 may be a typical lead acid automobile battery.

[0117] In some implementations, the battery 914 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or battery monitoring integrated circuit. The BMS may be included in the platform 900 to track the state of charge (SoCh) of the battery 914. The BMS may be used to monitor other parameters of the battery 914 to provide fault predictions, such as the state of health (SoH) and state of function (SoF) of the battery 914. The BMS may communicate information about the battery 914 to the application circuit 902 or other components of the platform 900. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 902 to directly monitor the voltage of the battery 914 or the current from the battery 914. The battery parameters may be used to determine operations that the platform 900 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0118] A power block, or other power source coupled to the electric grid, may be coupled to the BMS to charge the battery 914. In some examples, the power block may be replaced with a wireless power receiver to obtain power wirelessly, for example, via a loop antenna in the computer platform 900. In these examples, wireless battery charging circuitry may be included in the BMS. The particular charging circuitry selected may depend on the size of the battery 914 and thus the current required. Charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

[0119] User interface circuitry 920 includes various input / output (I / O) devices present in or connected to platform 900 and may include one or more user interfaces designed to enable user interaction with platform 900 and / or peripheral component interfaces designed to enable peripheral component interaction with platform 900. User interface circuitry 920 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as a sensor reading, an actuator position(s), or other similar information. The output device circuitry may include any number and / or combination of audio or visual displays, among others, one or more simple visual outputs / indicators such as binary status indicators (e.g., light emitting diodes (LEDs)), and multi-character visual outputs or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), and may output characters, graphics, multimedia objects, etc., generated or created from operation of the platform 900. The output device circuitry may also include speakers or other audio emission devices, printer(s), and / or the like. In some embodiments, the sensor 922 may be used as an input device circuitry (e.g., image capture devices, motion capture devices, etc.), and one or more EMCs may be used as output device circuitry (e.g., actuators for providing tactile feedback, etc.). In another example, an NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read an electronic tag and / or connect with another NFC-enabled device.Peripheral component interfaces include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, and the like.

[0120] Although not shown, the components of platform 900 can communicate with each other using any suitable bus or interconnect (IX) technology, which may include any number of technologies including ISA, EISA, PCI, PCIx, PCIe, Time Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be, for example, a proprietary bus / IX used in SoC-based systems. In particular, the I 2 Other bus / IX systems may be included such as a C interface, an SPI interface, a point-to-point interface, and a power bus.

[0121] 10 is a block diagram illustrating a component 1000 that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some example embodiments. Specifically, FIG. 10 illustrates a diagrammatic representation of hardware resources 1002, including one or more processors 1006 (or processor cores), one or more memory / storage devices 1014, and one or more communication resources 1024, each of which may be communicatively coupled via a bus 1016. In embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1022 may be executed to provide an execution environment for one or more network slices / sub-slices that utilize the hardware resources 1002.

[0122] Processor 1006 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1008 and processor 1010.

[0123] The memory / storage 1014 may include main memory, disk storage, or any suitable combination thereof. The memory / storage 1014 may include any type of volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0124] Communications resources 1024 may include interconnect or network interface components or other suitable devices for communicating with one or more peripherals 1004 or one or more databases 1020 over network 1018. For example, communications resources 1024 may include wired communications components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communications components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communications components.

[0125] The instructions 1012 may include software, programs, applications, applets, apps, or other executable code to cause at least one of the processors 1006 to perform any one or more of the methodologies discussed herein. The instructions 1012 may reside, completely or partially, in at least one of the processors 1006 (e.g., in a cache memory of the processor), the memory / storage 1014, or any suitable combination thereof. Additionally, any portion of the instructions 1012 may be transferred to the hardware resources 1002 from any combination of the peripherals 1004 or the database 1020. Thus, the memory of the processor 1006, the memory / storage 1014, the peripherals 1004, and the database 1020 are examples of computer-readable and machine-readable media.

[0126] In one or more embodiments, at least one of the components depicted in one or more of the preceding figures may be configured to perform one or more of the operations, techniques, processes, and / or methods as described in the Examples section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the Examples section.

[0127] Example Section

[0128] The following examples relate to further embodiments.

[0129] Example 1 is a method for a UE communicating in a public land mobile network (PLMN), the method including: generating, by the UE, a registration request message to send to a visited PLMN (VPLMN), the registration request message including a registration type parameter indicating a mobility registration update; processing, at the UE, a registration accept message from the VPLMN; determining, by the UE, whether the registration accept message includes valid roaming guidance (SoR) information from a home PLMN (HPLMN); and, in response to the UE being configured to receive SoR information during a mobility registration procedure and the UE not receiving SoR information during a current power cycle of the UE, selectively performing a PLMN selection procedure based on whether the registration accept message includes valid SoR information from the HPLMN.

[0130] Example 2 includes the method of example 1, wherein an indication is set in a subscriber identity module (SIM) or universal SIM (USIM) of the UE that the UE will receive an SoR transparent container in the registration accept message, and the SoR transparent container includes SoR information.

[0131] Example 3 includes the method of example 2, in which determining whether the registration acceptance message includes a secure copy of the SoR information from the HPLMN includes determining whether the SoR transparent container passes an integrity check.

[0132] Example 4 includes the method of example 1, wherein the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing a PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes: determining whether the registration accept message does not include SoR information or the SoR information has been changed by the VPLMN; setting the VPLMN as the lowest priority PLMN in a local list stored in the UE; locally releasing a Non-Access Stratum (NAS) signaling connection after sending a registration complete message to the VPLMN; and performing a PLMN selection procedure based on the local list to attempt registration to a different PLMN.

[0133] Example 5 includes the method of example 1, wherein the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing the PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes determining that the registration accept message includes the SoR information and that the SoR information passes an integrity check, and performing the PLMN selection procedure based on the prioritized list.

[0134] Example 6 includes the method of example 5, wherein the SoR information includes a list type indicator indicating that the prioritized list is a PLMN Identifier (ID) and access technology list, and the method further includes replacing one or more highest priority entries in a local list stored in the UE with entries from the prioritized list.

[0135] Example 7 includes the method of example 5, wherein the SoR information includes a list type indicator indicating that the prioritized list includes a secured packet of received Short Message Service (SMS) messages, the method further includes processing the SMS message as if it was received with a protocol identifier set to a Subscriber Identity Module (SIM) data download, a data encoding scheme set to a class 2 message, and an SMS payload as secured packet content of an SoR transparent container information element (IE), and forwarding the SMS payload to a Universal Integrated Circuit Card (UICC).

[0136] Example 8 is a method for a UE, the method including triggering a first initial registration procedure with a first Visited Public Land Mobile Network (VPLMN), determining that a registration accept message from the first VPLMN does not include valid SoR information, disconnecting from the first VPLMN, and instead of triggering mobility registration or periodic registration with the second VPLMN, attempting a second initial registration procedure with the second VPLMN.

[0137] Example 9 includes the method of Example 8, and further includes refraining from triggering mobility registration or periodic registration in the first VPLMN, the second VPLMN, or another VPLMN until valid SoR information is received, as long as an indication is set in the UE's Subscriber Identity Module (SIM) or Universal SIM (USIM) that the UE expects to receive valid SoR information due to initial registration in the VPLMN.

[0138] Example 10 includes the method of example 8, in which the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0139] Example 11 is a method for an access and mobility management function (AMF) in a wireless network, the method including: receiving, in the AMF, a registration request message from a user equipment (UE), the registration request message including a registration type parameter indicating a mobility registration update; performing, in the AMF, in response to the registration request message, a mobility registration procedure for the UE in a visited public land mobile network (VPLMN), the mobility registration procedure including receiving and storing UE context information in the AMF; determining, in response to the registration type parameter indicating a mobility registration update when a SoR container has not been delivered to the UE in a previous registration, that the UE context information includes a roaming guidance (SoR) indicator for the mobility registration indicating that a unified data management (UDM) of a home public land mobile network (HPLMN) requests the visited public mobile network (VPLMN) to retrieve SoR information; and, in response to the SoR indicator for the mobility registration, retrieving the SoR information from the UDM and delivering the SoR information to the UE in a registration accept message.

[0140] Example 12 includes the method of example 11, in which retrieving the SoR information from the UDM includes invoking a Nudm_SDM_Get service operation message to the UDM to retrieve the SoR information.

[0141] Example 13 includes the method of example 11, in which delivering the SoR information to the UE includes delivering an SoR container to the UE.

[0142] Example 14 includes the method of example 11, in which the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0143] Example 15 includes the method of example 14, wherein the SoR information further includes a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0144] Example 16 is a method for a home public land mobile network (HPLMN) that includes configuring a user equipment (UE) to operate in accordance with a visited public land mobile network (VPLMN) roaming guidance (SoR) configuration that includes configuring the UE to determine whether a registration accept message associated with a mobility registration at a VPLMN includes SoR information, configuring UE context information to include an SoR indicator for the mobility registration indicating that the VPLMN is requested to retrieve SoR information in response to a registration type parameter indicating a mobility registration update when a SoR container has not been delivered to the UE in a previous registration, and providing the SoR information in the SoR container to the VPLMN for forwarding to the UE in response to a request from the VPLMN.

[0145] Example 17 includes the method of example 16, further including securing the SoR container using a key shared with the UE.

[0146] Example 18 includes the method of example 16, wherein the SoR configuration further includes configuring the UE to lower the priority of the VPLMN if the UE determines that the SoR container is not present in a registration accept message associated with the mobility registration with the VPLMN or the SoR container fails an integrity check.

[0147] Example 19 includes the method of example 16, in which the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0148] Example 20 includes the method of example 16, wherein the SoR information further includes a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0149] Example 21 is a UE having a processor and a memory, the memory storing instructions that, when executed by the processor, configure the UE to generate a registration request message for transmission by the UE to a Visited PLMN (VPLMN), the registration request message including a registration type parameter indicating a mobility registration update, process a registration accept message from the VPLMN at the UE, determine by the UE whether the registration accept message includes valid roaming guidance (SoR) information from a Home PLMN (HPLMN), the UE being configured to receive SoR information during a mobility registration procedure, and in response to the UE not receiving SoR information during a current power cycle of the UE, selectively perform a PLMN selection procedure based on whether the registration accept message includes valid SoR information from the HPLMN.

[0150] Example 22 includes the UE of Example 21, wherein an indication is set in a subscriber identity module (SIM) or universal SIM (USIM) of the UE that the UE will receive an SoR transparent container in a registration accept message, and the SoR transparent container includes SoR information.

[0151] Example 23 includes the UE of example 22, in which determining whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes determining whether the SoR transparent container passes an integrity check.

[0152] Example 24 includes the UE of Example 21, wherein the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing a PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes: determining whether the registration accept message does not include SoR information or the SoR information has been changed by the VPLMN; setting the VPLMN as the lowest priority PLMN in a local list stored in the UE; locally releasing a non-access stratum (NAS) signaling connection after sending a registration complete message to the VPLMN; and performing a PLMN selection procedure based on the local list to attempt registration to a different PLMN.

[0153] Example 25 includes the UE of Example 21, wherein the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing the PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes determining that the registration accept message includes the SoR information and that the SoR information passes an integrity check, and performing the PLMN selection procedure based on the prioritized list.

[0154] Example 26 includes the UE of Example 25, wherein the SoR information includes a list type indicator indicating that the prioritized list is a PLMN Identifier (ID) and access technology list, and the method further includes replacing one or more highest priority entries in a local list stored in the UE with an entry from the prioritized list.

[0155] Example 27 includes the UE of Example 25, wherein the SoR information includes a list type indicator indicating that the prioritized list includes a secured packet that received a Short Message Service (SMS) message, and the method further includes processing the SMS message as if it was received with a protocol identifier set to a Subscriber Identity Module (SIM) data download, a data encoding scheme set to a class 2 message, and an SMS payload as secured packet content of an SoR transparent container information element (IE), and forwarding the SMS payload to the Universal Integrated Circuit Card (UICC).

[0156] Example 28 is a non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that, when executed by a computer, cause the computer to generate, by the UE, a registration request message to be sent to a Visited PLMN (VPLMN), the registration request message including a registration type parameter indicating a mobility registration update, process, at the UE, a registration accept message from the VPLMN, determine, by the UE, whether the registration accept message includes valid roaming guidance (SoR) information from a Home PLMN (HPLMN), and, in response to the UE being configured to receive SoR information during a mobility registration procedure and the UE not receiving SoR information during a current power cycle of the UE, selectively perform a PLMN selection procedure based on whether the registration accept message includes valid SoR information from the HPLMN.

[0157] Example 29 includes the computer-readable storage medium of Example 28, wherein an indication is set in a subscriber identity module (SIM) or universal SIM (USIM) of the UE that the UE will receive an SoR transparent container in the registration accept message, and the SoR transparent container includes the SoR information.

[0158] Example 30 includes the computer-readable storage medium of example 29, wherein determining whether the registration acceptance message includes a secure copy of the SoR information from the HPLMN includes determining whether the SoR transparent container passes an integrity check.

[0159] Example 31 includes the computer-readable storage medium of Example 28, wherein the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing a PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes determining whether the registration accept message does not include SoR information or the SoR information has been modified by the VPLMN, setting the VPLMN as a lowest priority PLMN in a local list stored in the UE, locally releasing a non-access stratum (NAS) signaling connection after sending a registration complete message to the VPLMN, and performing a PLMN selection procedure based on the local list to attempt registration to a different PLMN.

[0160] Example 32 includes the computer-readable storage medium of Example 28, wherein the SoR information further includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing the PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN includes determining that the registration accept message includes the SoR information and the SoR information passes an integrity check, and performing the PLMN selection procedure based on the prioritized list.

[0161] Example 33 includes the computer-readable storage medium of Example 32, wherein the SoR information includes a list type indicator indicating that the prioritized list is a PLMN identifier (ID) and access technology list, and the method further includes replacing one or more highest priority entries in a local list stored in the UE with an entry from the prioritized list.

[0162] Example 34 includes the computer-readable storage medium of example 32, wherein the SoR information includes a list type indicator indicating that the prioritized list includes a secured packet that received a short message service (SMS) message, and the method further includes processing the SMS message as if it was received with a protocol identifier set to a subscriber identity module (SIM) data download, a data encoding scheme set to a class 2 message, and an SMS payload as secured packet content of an SoR transparent container information element (IE), and forwarding the SMS payload to a universal integrated circuit card (UICC).

[0163] Example 35 is an apparatus for an AMF, comprising: a processor and a memory storing instructions, which, when executed by the processor, configure the apparatus to: receive, in the AMF, a registration request message from a user equipment (UE), the registration request message including a registration type parameter indicating a mobility registration update; in response to the registration request message, perform, in the AMF, a mobility registration procedure for the UE in a visited public land mobile network (VPLMN), the mobility registration procedure including receiving and storing UE context information in the AMF; determine, in response to the registration type parameter indicating a mobility registration update when a SoR container has not been delivered to the UE in a previous registration, that the UE context information includes a roaming guidance (SoR) indicator for the mobility registration indicating that a unified data management (UDM) of a home public land mobile network (HPLMN) requests the visited public mobile network (VPLMN) to retrieve SoR information; and, in response to the SoR indicator for the mobility registration, retrieve the SoR information from the UDM and deliver the SoR information to the UE in a registration accept message.

[0164] Example 36 includes the computing device of example 35, in which retrieving the SoR information from the UDM includes invoking a Nudm_SDM_Get service operation message to the UDM to retrieve the SoR information.

[0165] Example 37 includes the computing device of example 35, in which delivering the SoR information to the UE includes delivering an SoR container to the UE.

[0166] Example 38 includes the computing device of example 35, wherein the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0167] Example 39 includes the computing device of Example 38, wherein the SoR information further includes a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0168] Example 40 is a non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that, when executed by a processor of an AMF computer, cause the computer to: receive, in the AMF, a registration request message from a user equipment (UE), the registration request message including a registration type parameter indicating a mobility registration update; and, in response to the registration request message, perform, in the AMF, a mobility registration procedure for a UE in a visited public land mobile network (VPLMN), the mobility registration procedure including receiving and storing UE context information in the AMF. determining that the UE context information includes a roaming guidance (SoR) indicator for mobility registration indicating that a Unified Data Management (UDM) of a Home Public Land Mobile Network (HPLMN) requests a Visited Public Mobile Network (VPLMN) to retrieve SoR information in response to a registration type parameter indicating a mobility registration update when an SoR container has not been delivered to the UE in a previous registration; and retrieving the SoR information from the UDM and delivering the SoR information to the UE in a registration accept message in response to the SoR indicator for mobility registration.

[0169] Example 41 includes the computer-readable storage medium of example 40, in which retrieving the SoR information from the UDM includes invoking a Nudm_SDM_Get service operation message to the UDM to retrieve the SoR information.

[0170] Example 42 includes the computer-readable storage medium of example 40, in which delivering the SoR information to the UE includes delivering an SoR container to the UE.

[0171] Example 43 includes the computer-readable storage medium of example 40, wherein the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0172] Example 44 includes the computer-readable storage medium of Example 43, wherein the SoR information further includes a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0173] Example 45 is a computing device comprising a processor and a memory storing instructions, which when executed by the processor, cause the device to configure a user equipment (UE) to operate in accordance with a SoR configuration including configuring the UE to determine whether SoR information is included in a registration accept message associated with a mobility registration in a visited public land mobile network (VPLMN), configure UE context information to include an SoR indicator for mobility registration indicating that the VPLMN is requested to retrieve SoR information in response to a registration type parameter indicating a mobility registration update when an SoR container has not been delivered to the UE in a previous registration, and provide to the VPLMN, upon request from the VPLMN, to forward the SoR information in the SoR container to the UE.

[0174] Example 46 includes the computing device of example 45, wherein the instructions further configure the device to secure the SoR container with a key shared with the UE.

[0175] Example 47 includes the computing device of example 45, wherein the SoR configuration further includes configuring the UE to lower the priority of the VPLMN if the UE determines that an SoR container is not present in a registration accept message associated with mobility registration with the VPLMN or the SoR container fails an integrity check.

[0176] Example 48 includes the computing device of example 45, wherein the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0177] Example 49 includes the computing device of example 45, wherein the SoR information further includes a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0178] Example 50 is a non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that, when executed by a computer, cause the computer to configure a user equipment (UE) to operate in accordance with a SoR configuration including configuring the UE to determine whether SoR information is included in a registration accept message associated with a mobility registration in a visited public land mobile network (VPLMN), configure UE context information to include an SoR indicator for mobility registration indicating that the VPLMN has been requested to retrieve SoR information in response to a registration type parameter indicating a mobility registration update when an SoR container has not been delivered to the UE in a previous registration, and provide to the VPLMN, upon request from the VPLMN, to forward the SoR information in the SoR container to the UE.

[0179] Example 51 includes the computer-readable storage medium of example 50, wherein the instructions further configure the computer to secure the SoR container using a key shared with the UE.

[0180] Example 52 includes the computer-readable storage medium of Example 50, and the SoR configuration further includes configuring the UE to lower the priority of the VPLMN if the UE determines that an SoR container is not present in a registration accept message associated with mobility registration with the VPLMN or the SoR container fails an integrity check.

[0181] Example 53 includes the computer-readable storage medium of example 50, wherein the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

[0182] Example 54 includes the computer-readable storage medium of Example 50, wherein the SoR information further includes a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

[0183] Example 55 may include an apparatus including means for performing one or more elements of a method described or related to any of the above examples, or any other method or process described herein.

[0184] Example 56 may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above examples or any other method or process described herein.

[0185] Example 57 may include a device including logic, modules, or circuitry that performs one or more elements of a method described in or related to any of the above examples or any other method or process described herein.

[0186] Example 58 may include any method, technique, or process described or related to any of the above examples or any portion or part thereof.

[0187] Example 59 may include an apparatus including one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of the above examples or portions thereof.

[0188] The embodiment 60 may include a signal as described or related to any of the above embodiments or portions or parts thereof.

[0189] Example 61 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of the above examples or any portion or part thereof, or as described in the present disclosure.

[0190] Example 62 may include a signal encoded with data as described or related to any of the above examples or portions or parts thereof or as described in this disclosure.

[0191] Example 63 may include a signal encoded using a datagram, packet, frame, segment, PDU, or message described or associated with any of the above examples or any portion or part thereof, or described in the present disclosure.

[0192] Example 64 may include an electromagnetic signal carrying computer-readable instructions that, upon execution of the computer-readable instructions by one or more processors, cause the one or more processors to perform a method, technique, or process described in or related to any of the above examples or portions thereof.

[0193] Example 65 may include a computer program having instructions that, when executed by a processing element, cause the processing element to perform a method, technique, or process described in or related to any of the above examples or portions thereof.

[0194] Example 66 may include signals in a wireless network as shown and described herein.

[0195] Example 67 may include a method of communicating in a wireless network as shown and described herein.

[0196] Example 68 may include a system for providing wireless communication as shown and described herein.

[0197] Example 69 can include a device for providing wireless communication as shown and described herein.

[0198] Any of the above-described examples can be combined with any other example (or combination of examples) unless otherwise stated. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0199] The embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that contain specific logic for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0200] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, split into multiple systems, or otherwise split or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. It is appreciated that parameters, attributes, aspects, etc. are described in one or more embodiments for clarity only, and that parameters, attributes, aspects, etc. may be combined or substituted with parameters, attributes, etc. of another embodiment, unless specifically disclaimed herein.

[0201] It is well understood that use of personal information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personal information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized uses should be clearly indicated to users.

[0202] Although the foregoing has been described in some detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. Thus, the present embodiments should be considered as illustrative and not restrictive, and the description should not be limited to the details given herein, but may be modified within the scope of the appended claims and their equivalents.

Claims

1. 1. A method for a user equipment (UE) communicating in a public land mobile network (PLMN), comprising: generating, by the UE, a registration request message for sending to a Visited PLMN (VPLMN), the registration request message including a registration type parameter indicating a mobility registration update; processing, at the UE, a registration accept message from the VPLMN; determining, by the UE, whether the registration accept message includes valid SoR information from a Home PLMN (HPLMN); selectively performing a PLMN selection procedure based on whether the Registration Accept message includes the valid SoR information from the HPLMN, when the UE is configured to receive the SoR information during the mobility registration procedure and the UE has not received the SoR information during a current power cycle of the UE; A method comprising:

2. 2. The method of claim 1, wherein an indication is configured in the UE's Subscriber Identity Module (SIM) or Universal SIM (USIM) that the UE will receive an SoR Transparent Container in the registration accept message, the SoR Transparent Container including the SoR information.

3. The method of claim 2 , wherein determining whether the Registration Accept message includes a secure copy of the SoR information from the HPLMN comprises determining whether the SoR Transparent Container passes an integrity check.

4. the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and selectively performing the PLMN selection procedure based on whether the registration accept message includes a secure copy of the SoR information from the HPLMN. determining whether the Registration Accept message does not include the SoR information or whether the SoR information has been modified by the VPLMN; Setting the VPLMN as the lowest priority PLMN in a local list stored in the UE; locally releasing a non-access stratum (NAS) signaling connection after sending a registration complete message to the VPLMN; performing the PLMN selection procedure based on the local list to attempt registration in a different PLMN; The method of claim 1 , comprising:

5. selectively performing the PLMN selection procedure based on whether the SoR information includes a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies, and whether the registration accept message includes a secure copy of the SoR information from the HPLMN; determining that the Registration Accept message includes the SoR information and that the SoR information passes an integrity check; performing the PLMN selection procedure based on the prioritized list; and The method of claim 1 , comprising:

6. 6. The method of claim 5, wherein the SoR information includes a list type indicator indicating that the prioritized list is a PLMN Identifier (ID) and Access Technology list, the method further comprising replacing one or more highest priority entries in a local list stored in the UE with entries from the prioritized list.

7. The SoR information includes a list type indicator indicating that the prioritized list includes secured packets that received Short Message Service (SMS) messages, and the method further comprises: processing the SMS message as if it had been received with a protocol identifier set to Subscriber Identity Module (SIM) Data Download, a data encoding scheme set to Class 2 message, and an SMS payload as secured packet content of a SoR Transparent Container information element (IE); transferring the SMS payload to a Universal Integrated Circuit Card (UICC); The method of claim 5 further comprising:

8. A method for Access and Mobility Management Function (AMF) in a wireless network, comprising: Receiving, in the AMF, a registration request message from a user equipment (UE), the registration request message including a registration type parameter indicating a mobility registration update; performing, in the AMF, a mobility registration procedure for the UE in a visited public land mobile network (VPLMN) in response to the registration request message, the mobility registration procedure including receiving and storing UE context information in the AMF; determining that the UE context information includes a Roaming Guidance (SoR) indicator for mobility registration, the SoR indicator indicating that a Unified Data Management (UDM) of a Home Public Land Mobile Network (HPLMN) requests the VPLMN to retrieve SoR information in response to the registration type parameter indicating a mobility registration update when a SoR container has not been delivered to the UE in a previous registration; retrieving the SoR information from the UDM in response to an SoR indicator for the mobility registration and delivering the SoR information to the UE in a registration accept message; A method comprising:

9. 9. The method of claim 8, wherein retrieving the SoR information from the UDM comprises invoking a Nudm_SDM_Get service operation message to the UDM to retrieve the SoR information.

10. The method of claim 8 , wherein delivering the SoR information to the UE comprises delivering the SoR container to the UE.

11. The method of claim 8 , wherein the SoR information comprises a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

12. 12. The method of claim 11, wherein the SoR information further comprises a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

13. 1. A method for a Home Public Land Mobile Network (HPLMN), comprising: configuring a user equipment (UE) to operate in accordance with a Roaming Guidance (SoR) configuration, the SoR configuration including configuring the UE to determine whether SoR information is included in a registration accept message associated with a mobility registration in a visited public land mobile network (VPLMN); configuring UE context information to include an SoR indicator for mobility registration indicating that the VPLMN is requested to retrieve the SoR information in response to a registration type parameter indicating a mobility registration update when a SoR container has not been delivered to the UE in a previous registration; upon request from the VPLMN, providing the SoR information to the VPLMN in the SoR container for forwarding to the UE; A method comprising:

14. The method of claim 13, further comprising: securing the SoR container using a key shared with the UE.

15. 14. The method of claim 13, wherein the SoR configuration further comprises configuring the UE to lower a priority of the VPLMN if the UE determines that the SoR Container is not present in the Registration Accept message associated with mobility registration with the VPLMN or the SoR Container fails an integrity check.

16. The method of claim 13 , wherein the SoR information comprises a prioritized list of preferred PLMNs or preferred combinations of PLMNs and access technologies.

17. 17. The method of claim 16, wherein the SoR information further comprises a list type indicator indicating that the prioritized list is one of a list of PLMN identifiers (IDs) and access technologies or secured packets.

Images