Using user equipment (UE) identifiers to register in fifth generation (5G) systems

Abstract

Methods, systems, and storage media for using a user equipment (UE) identifier for registration in a 5th Generation (5G) system are described. An apparatus of a user equipment includes processing circuitry to: retrieve a first 5G-GUTI from a memory; generating a registration request message comprising the first 5G-GUTI; encoding the registration request message for transmission to a fifth generation core (5GC) network of the second PLMN; receiving a registration acceptance message including a second 5G-GUTI; and using the second 5G-GUTI to access the second PLMN (Public Land Mobile Network).

Description

[0001] This application is a divisional application of a Chinese patent application filed on August 12, 2019, with application number 201980054014.2 and invention name “Using User Equipment (UE) Identifier to Register in a Fifth Generation (5G) System”.

[0002] Related Applications

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 718,263, filed on August 13, 2018, and entitled “USE OF UE IDENTIFIERS FOR REGISTRATION IN THE 5G SYSTEM,” the entire disclosure of which is incorporated by reference in its entirety. Background Art

[0004] As one of many aspects, embodiments of the present disclosure relate to using a user equipment (UE) identifier to register in a fifth generation (5G) system. Some embodiments may help enable a UE to simultaneously connect to a 5G system via a third generation partnership project (3GPP) and non-3GPP access. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The embodiment will be more easily understood by the following specific implementation in conjunction with the accompanying drawings. In order to facilitate this description, similar reference numerals represent similar structural elements. In each figure of the accompanying drawings, the embodiment is shown by way of example and not limitation.

[0006] Figure 1 and Figure 2 and Figure 3 An example of an operational flow / algorithm structure according to some embodiments is shown.

[0007] Figure 4A An example of a non-roaming architecture for a 5G core network with non-3GPP access according to some embodiments is shown.

[0008] Figure 4B An example of a home-routed roaming architecture for a 5G core network with a non-3GPP access having a non-3GPP interworking function (N3IWF) in the same visited public land mobile network (VPLMN) as the 3GPP access is shown according to some embodiments.

[0009] Figure 4C An example of a registration process according to some embodiments is shown.

[0010] Figure 5 Depicted is the architecture of a system of networks according to some embodiments.

[0011] Figure 6 Depicted are examples of components of an apparatus according to some embodiments.

[0012] Figure 7 Depicted are examples of interfaces for baseband circuitry according to some embodiments.

[0013] Figure 8 A block diagram of components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein is depicted according to some embodiments. DETAILED DESCRIPTION

[0014] Embodiments discussed herein may relate to the use of user equipment (UE) identifiers for registration in fifth generation (5G) systems. Other embodiments are also described and / or claimed.

[0015] The following detailed description refers to the accompanying drawings. The same figure numbers may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the various aspects protected by the claims. However, it will be apparent to those skilled in the art who benefit from this disclosure that the various aspects of the invention protected by the claims may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the invention due to unnecessary details.

[0016] The various aspects of the exemplary embodiments will be described using terms commonly used by those skilled in the art to convey the essence of their work to other persons skilled in the art. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced using only some of the described aspects. For purposes of explanation, many specific quantities, materials, and configurations are set forth in order to provide a thorough understanding of the exemplary embodiments. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced without these specific details. In other cases, well-known features may be omitted or simplified so as not to obscure the exemplary embodiments.

[0017] Furthermore, various operations will be described as multiple discrete operations in sequence in a manner that is most helpful for understanding the exemplary embodiments; however, the order of description should not be construed as implying that these operations are necessarily order-dependent. In particular, these operations do not necessarily have to be performed in the order presented.

[0018] The phrases "in various embodiments", "in some embodiments", etc. may refer to the same or different embodiments. Unless the context dictates otherwise, the terms "comprising", "having", and "including" are synonymous. The phrase "A and / or B" means (A), (B), or (A and B). The phrases "A / B" and "A or B" mean (A), (B), or (A and B), similar to the phrase "A and / or B". For the purposes of the present disclosure, the phrase "at least one of A and B" means (A), (B), or (A and B). The description may use the phrases "in one embodiment", "in an embodiment", "in some embodiments", and / or "in various embodiments", which may each refer to one or more of the same or different embodiments. In addition, the terms "comprising", "including", "having", etc. used with the embodiments of the present disclosure are synonymous.

[0019] Examples of embodiments may be described as processes, which are depicted as flow charts, flow diagrams, data flow diagrams, structure diagrams, or block diagrams. Although a flow chart may describe operations as sequential processes, multiple of these operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be rearranged. A process may terminate when its operations are completed, but may also have additional steps not included in the accompanying drawings. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function and / or the main function.

[0020] Examples of embodiments may be described in the general context of computer executable instructions (such as program codes, software modules, and / or functional processes) executed by one or more of the above-mentioned circuits. Program codes, software modules, and / or functional processes may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific data types. The program codes, software modules, and / or functional processes discussed herein may be implemented using existing hardware in existing communication networks. For example, the program codes, software modules, and / or functional processes discussed herein may be implemented using existing hardware at existing network elements or control nodes.

[0021] A User Equipment (UE) connected to a 5G system via both 3GPP and non-3GPP accesses simultaneously maintains two different Registration Management (RM) contexts, one for each access.

[0022] The architecture for a UE connecting to a 5G system via 3GPP and non-3GPP accesses may vary depending on whether the UE is roaming and whether the 3GPP and non-3GPP accesses reside in the same PLMN. Figure 4A and 4B Examples of the following two configurations are shown: Non-roaming architecture ( Figure 4A) and roaming architecture for 3GPP and non-3GPP accesses residing in the same VPLMN ( Figure 4B ).

[0023] According to the 5G system specification, UEs simultaneously connected to the 5G system via 3GPP and non-3GPP accesses belonging to the same PLMN or equivalent PLMN should use the same UE temporary identifier (5G-GUTI) in both accesses. The basic assumption is that the UE context is handled by a single AMF on the network side.

[0024] If the UE is already registered via one access in PLMN A (e.g. non-3GPP access) and attempts to register via another access in PLMN B (e.g. 3GPP access), the UE needs to follow specific logic on how to select the 5G-GUTI it provides in the Registration Request via the second access. The current basic assumption is that if the PLMN of the second access (PLMN B) is the same or equivalent to the PLMN of the first access (PLMN A), the UE needs to follow the registration procedure of clause 4.2.2.2 of 3GPP TS 23.502 v.15.2.0 dated 19 June 2018 to indicate the 5G-GUTI used in the first access (i.e. PLMN A) in the Registration Request, which states:

[0025] When the UE is performing an initial registration (i.e. the UE is in RM-DEREGISTERED state), the UE shall indicate its UE identity as follows:

[0026] - If the UE is in RM-Deregistered state, the UE shall include the native 5G-GUTI allocated by the same or equivalent PLMN (if available); otherwise, the UE shall include the native 5G-GUTI allocated by other PLMN (if available).

[0027] - If the UE is already in RM-Registered state by another access in the same or equivalent PLMN, it shall indicate the native 5G-GUTI assigned by the AMF during the previous registration procedure

[0028] (if available).

[0029] - If the UE is already registered with the same PLMN as the one the UE is trying to register with (e.g. PLMN B)

[0030] If another access in a non-equivalent PLMN (e.g. PLMN A) is in the RM-Registered state, the UE shall include a native 5G-GUTI (if available) allocated by the PLMN (e.g. PLMN C) that is different and non-equivalent to the PLMN in which the UE is already in the RM-Registered state (PLMN A).

[0031] - Otherwise, the UE shall include its SUCI in the Registration Request as defined in TS 33.501.

[0032] Behind this logic is the assumption that for two AMFs residing in equivalent PLMNs: 1) the new AMF will always be able to obtain the UE context from the old AMF, and 2) the old NG-RAN node (e.g. N3IWF) will have N2 connectivity to both AMFs.

[0033] The first assumption (i.e., inter-AMF acquisition) is likely realistic, especially since the 5G Core relies on a service-based architecture (HTTP-based) that facilitates communication between any pair of core network nodes.

[0034] The second assumption (i.e., a NG-RAN node with N2 connections to two AMFs) is unlikely. If no such connections exist, the current assumptions in this specification may lead to undesirable situations as described below:

[0035] Assume that the UE registers via the first access in PLMN A

[0036] The UE attempts to register with PLMN B which is equivalent to PLMN A. In the Registration Request, the UE provides the 5G-GUTI allocated by the PLMN.

[0037] The AMF in PLMN B is able to retrieve the UE context in PLMN A, but cannot move the N2 connection from the NG-RAN node in PLMN A to the AMF in PLMN B.

[0038] Considering the fixed logic in the current specification, the UE starts using the 5G-GUTI allocated by PLMN B for both accesses. This will obviously create an error situation on the old access.

[0039] The present disclosure provides an implementation for fixing this error situation. The implementation herein provides a simplified UE logic for indicating the 5G-GUTI in a registration request message. The implementation herein provides an explicit indication in a registration accept message, wherein the network indicates to the UE whether the 5G-GUTI allocated via the second access should also be used by the first access. By using explicit indications from the network side, operators have the flexibility to support concurrent 3GPP and non-3GPP accesses without having to implement full connectivity between the NG-RAN node and the AMF residing in its own PLMN or an equivalent PLMN. The implementation herein can be implemented in the registration process example shown below.

[0040] 4.2.2.2.2 General Registration

[0041] Figure 4CExamples of registration processes according to various embodiments are shown. Figure 4C The process can be done as follows:

[0042] 1.UE to (R)AN: AN message (AN parameters, Registration request (Registration type, SUCI or 5G-GUTI or PEI, Last visited TAI (if available), Security parameters, Requested NSSAI, [Mapping of requested NSSAI], UE Radio Capability Update, UE MM Core Network Capabilities, PDU Session Status, List of PDU Sessions to be activated, Follow-up request, MICO mode preference, Requested DRX parameters) and UE Policy Container (List of PSI).

[0043] For NG-RAN, the AN parameters include, for example, SUCI or 5G-GUTI, the selected PLMN ID and the requested NSSAI, and the establishment cause. The establishment cause provides the reason for requesting to establish an RRC connection.

[0044] The Registration Type indicates whether the UE wants to perform an Initial Registration (i.e. the UE is in RM-DEREGISTERED state), a Mobility Registration Update (i.e. the UE is in RM-REGISTERED state and the registration procedure is initiated due to mobility or because the UE needs to update its capabilities or protocol parameters, or requests a change in the set of network slices it is allowed to use), a Periodic Registration Update (i.e. the UE is in RM-REGISTERED state and the registration procedure is initiated due to expiration of the Periodic Registration Update timer, see clause 4.2.2.2.1) or an Emergency Registration (i.e. the UE is in Limited Service state).

[0045] When the UE is performing an initial registration (i.e. the UE is in RM-DEREGISTERED state), the UE shall indicate its UE identity as follows:

[0046] - If the UE is in RM-Deregistered state, the UE shall include the native 5G-GUTI allocated by the same or equivalent PLMN (if available); otherwise, the UE shall include the native 5G-GUTI allocated by other PLMN (if available).

[0047] - If the UE is already in RM-REGISTERED state by another access in the same or equivalent PLMN, it shall indicate the native 5G-GUTI allocated by the AMF during the previous registration procedure (if available).

[0048] - If the UE is already in the RM-Registered state by another access in a PLMN (e.g. PLMN A) that is not equivalent to the PLMN with which the UE is attempting to register (e.g. PLMN B), the UE shall include a native 5G-GUTI (if available) allocated by the PLMN (e.g. PLMN C) that is different and not equivalent to the PLMN with which the UE is already in the RM-Registered state (PLMN A).

[0049] - Otherwise, the UE shall include its SUCI in the Registration Request.

[0050] Additionally or alternatively, when the UE is performing an initial registration to a serving PLMN, the UE shall indicate its UE identity in the following order:

[0051] -Native 5G-GUTI assigned by the serving PLMN (if available).

[0052] - Otherwise, the native 5G-GUTI assigned by the PLMN equivalent to the serving PLMN

[0053] (if available).

[0054] - Otherwise, the native 5G-GUTI assigned by any PLMN if available.

[0055] - Otherwise, the UE shall include its SUCI in the Registration Request.

[0056] When the UE is performing an initial registration using its native 5G-GUTI (i.e. the UE is in RM-DEREGISTERED state), the UE shall indicate the relevant GUAMI information in the AN parameters. When the UE is performing an initial registration using its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.

[0057] If the UE previously received a UE Configuration Update Command indicating that the UE needs to re-register and that a 5G-GUTI should not be provided in the access stratum signaling when performing the registration procedure, the UE performs a mobility registration and should not include any GUAMI information in the AN parameters. For emergency registration, if the UE does not have a valid 5G-GUTI available, a SUCI should be included; when the UE does not have a SUPI and does not have a valid 5G-GUTI, a PEI should be included. In other cases, the 5G-GUTI is included and indicates the last serving AMF.

[0058] The UE may provide the UE's usage settings based on its configuration. In the case of an initial registration or a mobility registration update, the UE includes a mapping of the requested NSSAI (if available) of each S-NSSAI in the requested NSSAI to the S-NSSAI of the configured NSSAI of the HPLMN to ensure that the network can verify whether the S-NSSAI in the requested NSSAI is allowed based on the subscribed S-NSSAI.

[0059] In the case of a mobility registration update, the UE includes the PDU sessions for which there is pending uplink data in the "list of PDU sessions to be activated". In some cases, the UE may include PDU sessions in the "list of PDU sessions to be activated" even if there is no pending uplink data for those PDU sessions.

[0060] UE MM Core Network Capabilities are provided by the UE and processed by the AMF. The UE includes in the UE MM Core Network Capabilities an indication of whether the request type flag "handover" for the PDN connection request is supported during the attach procedure.

[0061] If available, the last visited TAI shall be included in order to help the AMF generate a registration area for the UE.

[0062] Security parameters are used for authentication and integrity protection. The requested NSSAI indicates network slice selection assistance information. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status indicates an established PDU session of the current PLMN in the UE. A list of PDU sessions to be activated is included to indicate the PDU sessions for which the UE intends to activate a UP connection. When the UE is outside the availability area of ​​the LADN, the PDU session corresponding to the LADN should not be included in the list of PDU sessions to be activated. A subsequent request is included when the UE has pending uplink signaling and the UE does not include a list of PDU sessions to be activated or the registration type indicates that the UE wants to perform an emergency registration. In the initial registration and mobility registration update, the UE provides the DRX parameters requested by the UE.

[0063] The UE provides a UE radio capability update indication.

[0064] UE access selection and PDU session selection identifies the UE access selection list and the PDU session selection policy information stored in the UE. The PCF uses this information to determine whether the UE must be updated with a new PSI, or whether some of the stored PSIs are no longer applicable and must be removed.

[0065] 2. If the 5G-GUTI is not included or the 5G-GUTI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI (if available).

[0066] (R)AN selects AMF. If the UE is in CM-Connected state, then (R)

[0067] The AN may forward the registration request message to the AMF based on the UE's N2 connection.

[0068] If the (R)AN cannot select an appropriate AMF, it forwards the Registration Request to the AMF that has been configured in the (R)AN to perform AMF selection.

[0069] 3. (R)AN to new AMF: N2 message (N2 parameters, Registration Request (as described in step 1) and UE Access Selection and PDU Session Selection information, UE Context Request).

[0070] When NG-RAN is used, the N2 parameters include the selected PLMN ID, location information and cell identity related to the cell on which the UE is camped.

[0071] When NG-RAN is used, the N2 parameters also include the establishment cause.

[0072] The mapping for the requested NSSAI is provided only if available.

[0073] If the registration type indicated by the UE is periodic registration update, steps 4 to 20 may be omitted.

[0074] 4. [Conditions] New AMF to old AMF: NAMF_COMMUNICATION_UE CONTEXT TRANSFER (FULL REGISTRATION REQUEST) or New AMF to UDSF: NUDSF_UNSTRUCTURED DATA MANAGEMENT_CHALLENGE().

[0075] (With UDSF deployment): If the UE's 5G-GUTI is included in the Registration Request and the serving AMF has changed since the last registration procedure, the new AMF and the old AMF are in the same AMF Set, and UDSF is deployed, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using the Nudsf_UnstructuredDataManagement_Challenge service operation, or if UDSF is not deployed, they may share the stored UE context via an implementation specific manner. This also includes event subscription information for each NF consumer for a given UE. In this case, the new AMF performs and verifies integrity protection using the integrity protected full Registration Request NAS message.

[0076] (without UDSF deployment): If the UE’s 5G-GUTI was included in the Registration Request and the serving AMF has changed since the last registration procedure, the new AMF may invoke a call to the old AMF including a complete Registration Request NAS message which may be integrity protected.

[0077] The old AMF invokes the Namf_Communication_UE Context Transfer service operation to request the SUPI and UE context of the UE. For details on this service operation, see clause 5.2.2.2.2. In this case, the old AMF uses the 5G-GUTI and the integrity protected complete Registration Request NAS message, or the indication that the SUPI and UE are verified according to the new AMF, to verify the integrity protection in the case where the Context Transfer service operation call corresponds to the requested UE. The old AMF also transfers the event subscription information of each NF consumer for the UE to the new AMF.

[0078] NOTE 1: If the new AMF has performed a successful UE authentication after a previous integrity check failure in the old AMF, the new AMF sets an indication that the UE was authenticated according to step 9A.

[0079] NOTE 2: After the UE successfully registers with the new AMF, the NF consumer does not need to subscribe to events using the new AMF again.

[0080] If the new AMF has received the UE context from the old AMF during the handover procedure,

[0081] Then skip steps 4, 5 and 10.

[0082] For Emergency Registration, if the UE identifies itself with a 5G-GUTI that is unknown to the AMF, steps 4 and 5 are skipped and the AMF immediately requests a SUPI from the UE. If the UE identifies itself with a PEI, the SUPI request shall be skipped. Allowing Emergency Registration without User Identity depends on local regulations.

[0083] 5. [Conditions] Old AMF to new AMF: Response to Namf_Communication_UE Context Transfer (SUPI, UE Context in AMF (as per Table 5.2.2.2.2-1)) or UDSF to new AMF: Nudsf_UnstructuredDataManagement_Query(). If the UDSF was queried in step 4, the UDSF responds to the new AMF for the Nudsf_UnstructuredDataManagement_Query call with the relevant context including the established PDU session, the old AMF includes the SMF information DNN, S-NSSAI and PDU Session ID, the active NGAP UE-TNLA binding to the N3IWF, and the old AMF includes information about the NGAP UE-TNLA binding. If the old AMF was queried in step 4, the old AMF responds to the new AMF for the Namf_Communication_UE Context Transfer call by including the UE's SUPI and UE context.

[0084] If the old AMF holds information about the established PDU session, the old AMF includes SMF information, DNN, S-NSSAI and PDU session ID.

[0085] If the old AMF holds information about an active NGAP UE-TNLA binding to the N3IWF, the old AMF includes information about the NGAP UE-TNLA binding.

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

[0087] If the old AMF holds information about AM policy association, the old AMF includes information about AM policy association including policy control request trigger and PCF ID. In the case of roaming, it includes V-PCF ID and H-PCF ID.

[0088] NOTE 3: When the new AMF uses UDSF for context retrieval, the interaction between the old AMF, new AMF and UDSF due to simultaneous UE signalling on the old AMF is an implementation specific issue.

[0089] 6. [Conditions] New AMF to UE: Identity Request ().

[0090] If the SUCI is neither provided by the UE nor retrieved from the old AMF, the Identity Request procedure is initiated by the AMF sending an Identity Request message to the UE requesting the SUCI.

[0091] 7. [Conditions] UE to new AMF: Identity Response ().

[0092] The UE responds with an Identity Response message including the SUCI. The UE derives the SUCI by using the public key provided by the HPLMN.

[0093] 8.AMF may decide to initiate UE authentication by invoking AUSF. In this case, AMF selects AUSF based on SUPI or SUCI.

[0094] If the AMF is configured to support Emergency Registration for Unauthenticated SUPI and the UE indicates Registration Type of Emergency Registration, the AMF skips authentication or the AMF accepts that authentication may have failed and continues with the registration procedure.

[0095] 9a.According to the request from AMF, AUSF shall perform authentication of UE. AUSF selects UDM and obtains authentication data from UDM.

[0096] Once the UE has been authenticated, the AUSF provides the relevant security related information to the AMF. In case the AMF provides the SUCI to the AUSF, the AUSF shall return the SUPI to the AMF only after successful authentication.

[0097] After successful authentication in the new AMF triggered by the integrity check failure in the old AMF at step 5, the new AMF again invokes step 4 above and indicates that the UE is authenticated (i.e. via the Cause parameter).

[0098] The AMF decides whether the Registration Request needs to be re-routed as described in clause 4.2.2.2.3,

[0099] The initial AMF refers to AMF.

[0100] 9b Perform NAS security initiation.

[0101] 9c. When completing the NAS security function setup, if the 5G-AN has requested the UE context or

[0102] If AMF is required to provide UE context, AMF initiates the NGAP process to provide security context to 5G-AN.

[0103] 9d.5G-AN stores the security context and confirms AMF. 5G-AN uses the security context

[0104] To protect the messages exchanged with the UE.

[0105] 10.[Condition] New AMF to old AMF: NAMF_COMMUNICATION_REGISTRATION COMPLETE NOTIFICATION().

[0106] If the AMF has changed, the new AMF notifies the old AMF that the UE's registration is complete in the new AMF by invoking the Namf_Communication_RegistrationCompleteNotification service operation.

[0107] If the authentication / security process fails, the registration should be rejected and the new AMF should be the old AMF

[0108] Invoke the NAMF_COMMUNICATION_REGISTRATIONCOMPLETENotification service operation with a reject indication cause code. The old AMF continues as if the UE CONTEXT TRANSFER service operation had never been received.

[0109] If one or more of the S-NSSAIs used in the old registration area

[0110] If the old AMF cannot be served in the target registration area, the new AMF determines which PDU session cannot be supported in the new registration area. The new AMF calls a Namf_SendReturn for the old AMF, including the rejected PDU session ID and the rejection reason (e.g., S-NSSAI is no longer available).

[0111] Communication_Registration Complete Notification Service Operation. Then, the new AMF modifies the PDU accordingly

[0112] Session status. The old AMF notifies the corresponding SMF to locally release the UE's SM context by calling the Nsmf_PDU Session_ReleaseSMContext service operation.

[0113] For details on the operation of the Namf_communication_registration completion notification service, see clause 5.2.2.2.3.

[0114] 11. [Conditions] New AMF to UE: Identity Request / Response (PEI).

[0115] If the PEI is neither provided by the UE nor retrieved from the old AMF, then it is sent via the AMF

[0116] The Identity Request procedure is initiated by sending an Identity Request message to the UE to retrieve the PEI. The PEI shall be transport encrypted unless the UE is performing an emergency registration and cannot be authenticated. For emergency registration, the UE may have included the PEI in the Registration Request. If so, the PEI retrieval is skipped.

[0117] 12. Optionally, the new AMF initiates the ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation (see clause 5.2.4.2.2).

[0118] PEI inspection is performed as described in clause 4.7.

[0119] For emergency registration, if PEI is blocked, operator policy determines whether the emergency registration process continues or stops.

[0120] 13. If step 14 is to be performed, the new AMF selects the UDM based on the SUPI, and the UDM can then select the UDR instance.

[0121] AMF selects UDM.

[0122] If the AMF has changed since the last registration procedure, or if the UE provides a

[0123] and the SUPI of the valid context in the AMF, or if the UE is registered to the same AMF, the UE is already registered to a non-3GPP access (i.e. the UE registered over a non-3GPP access and initiated this registration procedure to add a 3GPP access), the new AMF registers with the UDM using Nudm_UECM_REGISTER and subscribes to be notified when the UDM deregisters the AMF. The UDM stores the AMF identity associated with the access type, and

[0124] The AMF identity associated with another access type is not removed. The UDM may store the information provided by Nudr_UDM_Update when registering in the UDR.

[0125] The AMF uses Nudm_SDM_Get to retrieve access and mobility subscription data, SMF selection subscription data and UE context in SMF data. This requires UDM

[0126] This information can be retrieved from the UDR via Nudr_UDM_Challenge. After receiving a successful response, the AMF uses Nudm_SDM_

[0127] Subscribe to get notifications. UDM can send notifications to UDR through Nudr_UDM_Subscribe

[0128] Subscription. If GPSI is available in the UE subscription data, then the GPSI is provided to the AMF in the access and mobility subscription data from the UDM. The UDM may provide an indication to the UE to update the subscription data for the network slice. If the UE is subscribed to MPS in the serving PLMN, then the “MPS priority” is included in the information provided to the AMF.

[0129] access and mobility subscription data.

[0130] The new AMF provides the access type serving the UE to the UDM, and the access type is set to "3GPP access". The UDM stores the associated access type together with the serving AMF in the UDR through Nudr_UDM_Update.

[0131] After obtaining the access and mobility subscription data from the UDM, the new AMF creates a UE context for the UE.

[0132] For emergency registrations where the UE is not successfully authenticated, the AMF shall not register with the UDM.

[0133] For emergency registration, the AMF shall not check access restrictions, regional restrictions or subscription restrictions. For emergency registration, the AMF shall ignore any unsuccessful registration response from the UDM and continue with the registration process.

[0134] l4d. When the UDM associates the access type (e.g., 3GPP) with the

[0135] When stored together with the serving AMF, this will cause the UDM to initiate a Nudm_UECM_Deregistration notification (see clause 5.2.3.2.2) to the old AMF corresponding to the same (e.g. 3GPP) access, if any. The old AMF removes the UE context for the UE. If the serving NF removal reason indicated by the UDM is initial registration, the old AMF invokes the Nsmf_PDU Session_Release SM Context (SUPI, PDU Session ID) service operation for all associated SMFs of the UE as described in clause 4.2.2.3.2 to notify that the UE has been deregistered from the old AMF. The SMF shall release the PDU Session upon obtaining this notification.

[0136] 14e. The old AMF uses Nudm_SDM_Unsubscribe to unsubscribe the subscription data to UDM. 15. If the AMF decides to initiate PCF communication, for example, the AMF has not yet obtained the access and mobility policy for the UE, or if the access and mobility policy in the AMF is no longer valid, the AMF performs the following operations.

[0137] If the new AMF receives the PCF ID included in the UE context from the old AMF in step 5, the AMF contacts the (V-)PCF identified by the (V-)PCF ID.

[0138] If the (V-)PCF identified by the (V-)PCF ID cannot be used in step 5 (e.g., no response from the (V-)PCF) or the PCF ID is not received from the old AMF, the AMF selects the (V)-PCF based on the V-NRF to H-NRF interaction and may select the H-PCF (for roaming scenarios).

[0139] 16. [Optional] The new AMF performs AM policy association establishment. For emergency registration, this step is skipped.

[0140] If the new AMF contacts the PCF identified by the (V-)PCF ID received during inter-AMF mobility in step 5, the new AMF shall include the PCF ID in the Npcf_AM Policy Control Create operation. This indication is not included by the AMF during the initial registration procedure.

[0141] If the AMF informs the PCF of the mobility restrictions (e.g. UE location) for adjustment, or if the PCF updates the mobility restrictions itself due to some conditions (e.g. applications in use, time and date), the PCF shall provide the updated mobility restrictions to the AMF.

[0142] 17.[Condition]AMF to SMF: Nsmf_PDU Session_Update SM Context().

[0143] For emergency registered UEs, this step applies when the registration type is mobility registration update.

[0144] AMF calls Nsmf_PDU Session_Update SM Context in the following scenarios (see

[0145] See clause 5.2.8.2.6):

[0146] - If the "List of PDU Sessions to be activated" is included in the Registration Request in step 1, the AMF sends an Nsmf_PDU_Update_SM Context Request to the SMF associated with the PDU Sessions in order to activate the User Plane Connection for these PDU Sessions. The steps from step 5 onwards as described in clause 4.2.3.2 are performed to complete the User Plane Connection Activation without sending an MM NAS Service Accept from the AMF to the (R)AN as described in step 12 of clause 4.2.3.2.

[0147] When the serving AMF has changed, the new serving AMF informs the SMF that has taken over the responsibility of the signalling path to the UE for each PDU Session: the new serving AMF invokes the Nsmf_PDU Session_Update SM Context service operation using the SMF information received from the old AMF at step 5. The new serving AMF also indicates whether the PDU Session is to be reactivated.

[0148] Perform the steps described in clause 4.2.3.2 from step 5. In the case of an intermediate UPF insertion, removal or change for a PDU session not included in the "PDU Sessions to be reactivated", the process is performed without N11 and N2 interaction to update the N3 user plane between the (R)AN and 5GC.

[0149] AMF calls Nsmf_PDU_session_release_SM_up and down for SMF in the following scenarios

[0150] Text service operation:

[0151] - If any PDU Session status indicates that it is released at the UE, the AMF invokes the Nsmf_PDU Session_Release SM Context service operation for the SMF in order to release any network resources associated with the PDU Session.

[0152] If the serving AMF changes, the new AMF shall wait until step 18 (where all SMFs are associated with the UE) is completed. Otherwise, steps 19 to 22 may continue in parallel with this step.

[0153] 18. New AMF to N3IWF: N2 AMF mobility request ().

[0154] If the AMF has changed and the old AMF has indicated an existing NGAP UE association with the N3IWF, And if the new AMF has There is N2 connection to N3IWF , the new AMF creates a NGAP UE association with the N3IWF to which the UE is connected. This automatically releases the existing NGAP UE association between the old AMF and the N3IWF

[0155] 19.N3IWF to new AMF: N2 AMF mobility response ().

[0156] 20. [Conditions] Old AMF to (V-)PCF: AMF-initiated Policy Association Termination. If the old AMF previously initiated a Policy Association to the PCF and the old AMF did not transfer the PCF ID to the new AMF (e.g. the new AMF is in a different PLMN), the old AMF performs the AMF-initiated Policy Association Termination procedure as defined in clause 4.16.3.2 to delete the association with the PCF.

[0157] 21. New AMF to UE: Registration Accept (5G-GUTI, registration area, mobility restrictions, PDU session status, allowed NSSAI, [mapping of allowed NSSAI],

[0158] [Configured NSSAI for serving PLMN], [Mapping of configured NSSAI], periodic registration update timer, LADN information and accepted MICO mode, IMS voice session support indication over PS, emergency service support indicator, accepted DRX parameters, network support without N26 interworking), network slice subscription change indication. The allowed NSSAI for the UE's access type is included in the N2 message carrying the Registration Accept message.

[0159] The AMF sends a Registration Accept message to the UE, indicating that the Registration Request has been accepted. If the AMF allocates a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in the RM-Registered state by another access in the same or equivalent PLMN, and If the AMF has successfully established an N2 connection with the NG-(R)AN node for another access, the AMF shall includeThe UE shall use the 5G-GUTI received in the Registration Accept for indication of both registrations. If the 5G-GUTI is not included in the Registration Accept, the UE shall allocate the 5G-GUTI used for the existing registration also for the new registration. If the AMF allocates a new registration area, it shall send the registration area to the UE via the Registration Accept message. If the registration area is not included in the Registration Accept message, the UE shall regard the old registration area as valid. Mobility restrictions are included in case mobility restrictions apply to the UE and the registration type is not an emergency registration. The AMF indicates the established PDU session to the UE in the PDU Session Status. The UE locally removes any internal resources related to the PDU session that are not marked as established in the received PDU Session Status. If the AMF calls the Nsmf_PDU Session_Update SM Context procedure for UP activation of the PDU session in step 18 and receives a rejection from the SMF, the AMF indicates the PDU Session ID to the UE and the reason why the user plane resources are not activated. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes any internal resources related to the PDU session of the current PLMN that are not marked as established in the received PDU session status. If the PDU session status information is in the registration request, the AMF shall indicate the PDU session status to the UE. The mapping of allowed NSSAIs is the mapping of each S-NSSAI in the allowed NSSAIs to the S-NSSAI of the configured NSSAI of the HPLMN. The mapping of configured NSSAIs is the mapping of each S-NSSAI in the configured NSSAI of the serving PLMN to the S-NSSAI of the configured NSSAI of the HPLMN. The AMF shall include in the registration accept message the LADN information of the LADNs defined in clause 5.6.5 of TS 23.501 [2] that are available within the registration area determined by the AMF for the UE. If the UE includes MICO mode in the request, the AMF responds whether MICO mode should be used.

[0160] In case of registration over 3GPP access, the AMF sets the IMS Voice Session Support Indication over PS. In order to set the IMS Voice Session Support Indication over PS, the AMF may need to perform the UE / RAN Radio Information and Compatibility Request procedure in clause 4.2.8a to check the compatibility of the UE and NG-RAN radio capabilities related to IMS Voice over PS. If the AMF does not receive the Voice Support Match Indicator from the NG-RAN in time, based on the specific implementation, the AMF may set the IMS Voice Session Support Indication over PS and update it at a later stage.

[0161] In case of registration over non-3GPP access, the AMF sets the IMS Voice Session Support Indication over PS.

[0162] The emergency service support indicator informs the UE that emergency services are supported, i.e. the UE is allowed to request a PDU session for emergency services. If the AMF receives the "MPS Priority" as part of the access and mobility subscription data from the UDM, then based on the operator policy, the "MPS Priority" is included in the Registration Accept message to the UE to inform the UE whether the configuration of Access Identity 1 is valid in the selected PLMN.

[0163] AMF sets interworking without N26 parameters.

[0164] In this step, RRC Inactive Assistance Information may be provided to the NG-RAN.

[0165] If the UDM intends to indicate to the UE that the subscription has changed, a network slice subscription change indication is included. If the AMF includes a network slice subscription change indication, the UE shall locally erase all network slice configurations for all PLMNs and, if applicable, update the configuration of the current PLMN based on any received information.

[0166] 22. [Condition] UE to new AMF: Registration completed ().

[0167] In step 22, when the AMF has successfully updated itself after receiving the network slice subscription change indication, the UE sends a registration completion message to the AMF.

[0168] The UE sends a Registration Complete message to the AMF to confirm whether a new 5G-GUTI is allocated.

[0169] When the Registration Request does not include a "List of PDU Sessions" to be activated, the AMF releases the signalling connection with the UE according to clause 4.2.6.

[0170] When a Subsequent Request is included in the Registration Request, the AMF shall not release the signalling connection after the registration procedure is completed.

[0171] If the AMF knows that some signalling is pending in the AMF or between the UE and 5GC, the AMF shall not release the signalling connection immediately after the registration procedure is completed.

[0172] 23. [Condition]: If the access and mobility subscription data provided by UDM to AMF in l4b includes roaming steering information with an indication that UDM requests confirmation of receipt of this information from the UE, the AMF provides UE confirmation to UDM using Nudm_SDM_Info.

[0173] For the case described in clause 4.15.4, a mobility related event notification to the NF consumer is triggered at the end of this procedure.

[0174] The embodiments of this document may be reflected in the registration process at operation 1 (registration request), operation 18 (N2 AMF mobility request), and operation 21 (registration acceptance).

[0175] At operation 1, when the UE is performing an initial registration to a serving PLMN, the UE shall indicate its UE identity in the following order: the native 5G-GUTI assigned by the serving PLMN (if available); otherwise, the native 5G-GUTI assigned by a PLMN equivalent to the serving PLMN (if available); otherwise, the native 5G-GUTI assigned by any PLMN (if available); otherwise, the UE shall include its SUCI in the registration request;

[0176] At operation 18 (New AMF to N3IWF: N2 AMF Mobility Request()), if the AMF has changed and the old AMF has indicated an existing NGAP UE association with the N3IWF, and if the new AMF has an N2 connection to the N3IWF, the new AMF creates an NGAP UE association with the N3IWF to which the UE is connected. This automatically releases the existing NGAP UE association between the old AMF and the N3IWF

[0177] At operation 21, new AMF to UE: registration acceptance (5G-GUTI, registration area, mobility restrictions, PDU session status, allowed NSSAI, [mapping of allowed NSSAI], [configured NSSAI for serving PLMN], [mapping of configured NSSAI], periodic registration update timer, LADN information and accepted MICO mode, IMS voice session support indication over PS, emergency service support indicator, accepted DRX parameters, network support without N26 interworking), network slice subscription change indication.

[0178] The AMF sends a Registration Accept message to the UE, indicating that the Registration Request has been accepted. If the AMF allocates a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in RM-REGISTERED state by another access in the same or equivalent PLMN, and if the AMF has successfully established an N2 connection with the NG-(R)AN node for the other access, the AMF shall include an indication that the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If the 5G-GUTI is not included in the Registration Accept, the UE shall use the 5G-GUTI allocated for the existing registration also for the new registration.

[0179] Note that the indication in the Registration Accept message may also have different semantics. For example, instead of indicating to the UE whether the 5G-GUTI allocated via the second access should also be used via the first access, it may indicate that the registration "is accepted for 3GPP access and non-3GPP access". The meaning is the same for both cases, i.e. the UE registers to the same AMF over 3GPP access and non-3GPP access, and in this case the UE shall use the same 5G-GUTI over both accesses.

[0180] 5.3.2.4 Support for UEs registered via 3GPP and non-3GPP access

[0181] For a given serving PLMN, for example when a UE is served continuously or simultaneously by a 3GPP access and a non-3GPP access (via N3IWF) of the same PLMN, there is one RM context for the UE for each access. The UDM manages separate / independent UE registration procedures for each access.

[0182] When served by the same PLMN for both 3GPP and non-3GPP accesses, the UE is served by the same AMF, except for temporary cases (e.g. after mobility from EPS while the UE has a PDU Session associated with the non-3GPP access).

[0183] The AMF associates multiple access-specific RM contexts of the UE with:

[0184] -5G-GUTI common to both 3GPP and non-3GPP accesses. The 5G-GUTI is globally unique.

[0185] -Registration status for each access type (3GPP / non-3GPP)

[0186] - Registration area for each access type: one registration area for 3GPP access and another registration area for non-3GPP access. The registration areas for 3GPP access and non-3GPP access are independent.

[0187] -Timers for 3GPP access:

[0188] - Periodic registration timer; and

[0189] - Mobile reachability timer and implicit logout timer.

[0190] -Timers for non-3GPP access:

[0191] -UE non-3GPP remote timer; and

[0192] - Network non-3GPP implicit deregistration timer.

[0193] The AMF does not provide a periodic registration timer for the UE via non-3GPP access. Therefore, the UE does not need to perform a periodic registration update procedure via non-3GPP access. Instead, during the initial registration procedure and re-registration, the network provides the UE with a UE non-3GPP deregistration timer, which starts when the UE enters the non-3GPP CM-IDLE state.

[0194] When a 3GPP access and a non-3GPP access for the same UE are served by the same PLMN or equivalent PLMN, the AMF allocates the same 5G-GUTI for use in both accesses (assuming that there is a control and user plane connection between the nodes of the registered PLMN and its equivalent PLMN). This 5G-GUTI may be allocated or reallocated in either of the 3GPP and non-3GPP accesses. The 5G-GUTI is allocated when the UE successfully registers and is valid in both 3GPP and non-3GPP accesses of the same PLMN or equivalent PLMN for the UE. When performing initial access through a non-3GPP access or through a 3GPP access when the UE is already registered with the 5G system through another access of the same PLMN or equivalent PLMN, the UE provides a native 5G-GUTI for the other access. This enables the AN to select an AMF that maintains the UE context created during the previous registration process via the GUAMI derived from the 5G-GUTI, and enables the AMF to associate the UE request with the existing UE context via the 5G-GUTI.

[0195] If the UE is performing a registration through one access and intends to perform a registration through another access in the same PLMN or an equivalent PLMN (e.g., the 3GPP access and the selected N3IWF are in the same PLMN), the UE shall not initiate a registration through the other access until the registration procedure through the first access is completed. The access that the UE uses first to perform the registration depends on the UE specific implementation.

[0196] When the UE successfully registers to an access (3GPP access or non-3GPP access respectively) and the UE registers via other accesses:

[0197] - If the second access is in the same PLMN or an equivalent PLMN (e.g. the UE registers via a 3GPP access and selects an N3IWF located in the same PLMN), the UE shall use the 5G-GUTI that was provided to the UE during a previous registration or UE configuration update of the first access in the same PLMN or an equivalent PLMN for registration to the PLMN associated with the new access. Upon successful completion of registration to the second access, if the network includes a 5G-GUTI in the Registration Accept, the UE shall include the 5G-GUTI received in the Registration Accept.

[0198] The GUTI is used for both registrations. If a 5G-GUTI is not included in the Registration Accept, the UE shall use the same 5G-GUTI allocated for the existing registration for the new registration.

[0199] - If the second access is located in a different PLMN than the registered PLMN of the first access (i.e. not the registered PLMN or an equivalent PLMN of the registered PLMN) (e.g. the UE is registered to a 3GPP access and selects an N3IWF located in a different PLMN than the PLMN of the 3GPP access, or the UE is registered via a non-3GPP access and is registered to a 3GPP access in a different PLMN than the PLMN of the N3IWF), then the UE shall be able to access the N3IWF only if the UE has previously obtained a PLMN from (not the same as and not equivalent to) the PLMN with which the UE has registered.

[0200] The UE shall use the 5G-GUTI for registration to the PLMN associated with the new access only if the UE does not include the 5G-GUTI, then the SUCI shall be used for the new registration. Upon successful completion of the registration to the second access, the UE shall have two 5G-

[0201] GUTI (one for each PLMN).

[0202] When the UE 5G-GUTI allocated during the registration process performed over 3GPP (e.g., the UE first registers over 3GPP access) is location-dependent, the same UE 5G-GUTI may be reused in non-3GPP access when the selected N3IWF function is in the same PLMN as the 3GPP access. When the UE 5G-GUTI is allocated during the registration process performed over non-3GPP access (e.g., the UE first registers over non-3GPP access), the UE 5G-GUTI may not be location-dependent, so that the UE 5G-GUTI may not be valid for NAS procedures performed over 3GPP access, and in this case, a new AMF is allocated during the registration process performed over 3GPP access.

[0203] When the UE first registers via 3GPP access, if the UE registers to the same PLMN via non-3GPP access, the UE shall send the GUAMI obtained via 3GPP access to the N3IWF, and the N3IWF shall use the received GUAMI to select the same AMF as the 3GPP access.

[0204] The deregistration request message indicates whether it applies to 3GPP access or non-3GPP access or both.

[0205] If the UE is registered on both 3GPP and non-3GPP access and it is in CM-IDLE over the non-3GPP access, the UE or AMF may initiate a deregistration procedure over the 3GPP access to deregister the UE only on the non-3GPP access, in which case all PDU sessions associated with the non-3GPP access shall be released.

[0206] If the UE is registered on both 3GPP and non-3GPP accesses and it is in CM-IDLE over the 3GPP access and in CM-CONNECTED over the non-3GPP access, the UE may initiate a deregistration procedure over the non-3GPP access to deregister the UE on the 3GPP access only, in which case all PDU sessions associated with the 3GPP access shall be released.

[0207] Figure 5 The architecture of a system 500 of a network according to some embodiments is shown. System 500 is shown to include user equipment (UE) 501 and UE 502. UE 501 and UE 502 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but these UEs may also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld terminals, or any computing device that includes a wireless communication interface.

[0208] In some embodiments, any of UEs 501 and 502 may include an Internet of Things (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 technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs that may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0209] UE 501 and 502 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 510, which may be, for example, an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NGRAN), or some other type of RAN. UE 501 and UE 502 utilize connection 503 and connection 504, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 503 and connection 504 are shown as air interfaces to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, etc.

[0210] In this embodiment, UE 501 and UE 502 may also directly exchange communication data via ProSe interface 505. ProSe interface 505 may alternatively be referred to as a sidelink interface including 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).

[0211] UE 502 is shown configured to access access point (AP) 506 via connection 507. Connection 507 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 506 would include wireless fidelity. In this example, AP 506 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below).

[0212] The RAN 510 may include one or more access nodes that enable connection 503 and connection 504. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 510 may include one or more RAN nodes (e.g., macro RAN nodes 511) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes 512) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0213] Either of the RAN nodes 511 and 512 may terminate the air interface protocol and may be the first point of contact for the UE 501 and UE 502. In some embodiments, either of the RAN nodes 511 and 512 may fulfill various logical functions of the RAN 510, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0214] According to some embodiments, UEs 501 and 502 may be configured to communicate with each other or with any of RAN nodes 511 and 512 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0215] In some embodiments, a downlink resource grid may be used for downlink transmissions from any one of RAN node 511 and RAN node 512 to UE 501 and UE 502, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements. In the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0216] The physical downlink shared channel (PDSCH) may deliver user data and higher layer signaling to UE 501 and UE 502. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel, among other things. It may also inform UE 501 and UE 502 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 502 within a cell) may be performed at either RAN node 511 or RAN node 512 based on channel quality information fed back from either UE 501 or UE 502. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 501 and UE 502.

[0217] PDCCH can use control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, called resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0218] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to four sets of nine physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0219] RAN 510 is shown as being communicatively coupled to a core network (CN) 520 via an S1 interface 513. In an embodiment, CN 520 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 513 is divided into two parts: S1-U interface 514, which carries traffic data between RAN nodes 511 and 512 and a serving gateway (S-GW) 522; and S1-mobility management entity (MME) interface 515, which is a signaling interface between RAN nodes 511 and 512 and MME 521.

[0220] In this embodiment, CN 520 includes MME 521, S-GW 522, Packet Data Network (PDN) Gateway (P-GW) 523 and Home Subscriber Server (HSS) 524. MME 521 may be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 521 may manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 524 may include a database for network users, which includes subscription-related information for supporting network entities to handle communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN 520 may include one or more HSS 524. For example, HSS 524 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, positioning dependencies, etc.

[0221] The S-GW 522 may terminate the S1 interface 513 towards the RAN 510 and route data packets between the RAN 510 and the CN 520. In addition, the S-GW 522 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies.

[0222] The P-GW 523 may terminate the SGi interface toward the PDN. The P-GW 523 may route data packets between the EPC network and an external network such as a network including an application server 530 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 525. Generally, the application server 530 may be an element that provides an application program that uses IP bearer resources with the core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 523 is shown as being communicatively coupled to the application server 530 via an IP communication interface 525. The application server 530 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 501 and UE 502 via the CN 520.

[0223] The P-GW 523 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 526 is a policy and charging control element of the CN 520. In a non-roaming scenario, there may be a single PCRF in the domestic public land mobile network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the UE's IP-CAN session: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in the visited public land mobile network (VPLMN). The PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523. The application server 530 may signal the PCRF 526 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 526 may configure the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Communication Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by application server 530 .

[0224] Figure 6Exemplary components of a device 600 according to some embodiments are shown. In some embodiments, the device 600 may include an application circuit 602, a baseband circuit 604, a radio frequency (RF) circuit 606, a front-end module (FEM) circuit 608, one or more antennas 610, and a power management circuit (PMC) 612 (at least coupled together as shown). The components of the illustrated device 600 may be included in a UE or a RAN node. In some embodiments, the device 600 may include fewer elements (e.g., the RAN node may not utilize the application circuit 602, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 600 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be separately included in more than one device for a specific implementation of a cloud-RAN (C-RAN)).

[0225] The application circuit 602 may include one or more application processors. For example, the application circuit 602 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices, and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 600. In some embodiments, the processor of the application circuit 602 may process IP data packets received from the EPC.

[0226] The baseband circuit 604 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 604 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 606 and generate baseband signals for the transmit signal path of the RF circuit 606. The baseband processing circuit 604 may interact with the application circuit 602 to generate and process baseband signals and control the operation of the RF circuit 606. For example, in some embodiments, the baseband circuit 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G base) band processor 604C, or one or more other baseband processors 604D of other existing generations, generations under development or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 604 (e.g., one or more of the baseband processors 604A-604D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuit 606. In other embodiments, some or all of the functions of the baseband processors 604A-D may be included in a module stored in the memory 604G and executed via the central processing unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 604 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 604 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0227] In some embodiments, the baseband circuit 604 may include one or more audio digital signal processors (DSPs) 604F. The audio DSP 604F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 604 and the application circuit 602 may be implemented together, such as on a system on a chip (SOC).

[0228] In some embodiments, the baseband circuit 604 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 604 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0229] RF circuit 606 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 606 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 606 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 608 and providing baseband signals to baseband circuit 604. RF circuit 606 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 604 and providing RF output signals for transmission to FEM circuit 608.

[0230] In some embodiments, the receive signal path of the RF circuit 606 may include a mixer circuit 606a, an amplifier circuit 606b, and a filter circuit 606c. In some embodiments, the transmit signal path of the RF circuit 606 may include a filter circuit 606c and a mixer circuit 606a. The RF circuit 606 may also include a synthesizer circuit 606d for synthesizing the frequency used by the mixer circuit 606a for the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 606a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 608 based on the synthesized frequency provided by the synthesizer circuit 606d. The amplifier circuit 606b may be configured to amplify the down-converted signal, and the filter circuit 606c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 604 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 606a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0231] In some embodiments, mixer circuit 606a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 606d to generate an RF output signal for FEM circuit 608. The baseband signal can be provided by baseband circuit 604 and can be filtered by filter circuit 606c.

[0232] In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be configured for superheterodyne operation.

[0233] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 606 may include an analog-to-digital converter (ADC) circuit and a digital-to-analog converter (DAC) circuit, and the baseband circuit 604 may include a digital baseband interface to communicate with the RF circuit 606.

[0234] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0235] In some embodiments, synthesizer circuit 606d may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0236] Synthesizer circuit 606d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 606a of RF circuit 606. In some embodiments, synthesizer circuit 606d may be a fractional-N / N+1 synthesizer.

[0237] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 604 or the application processor 602 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 602.

[0238] The synthesizer circuit 606d of the RF circuit 606 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0239] In some embodiments, the synthesizer circuit 606d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 606 can include an IQ / polarity converter.

[0240] The FEM circuitry 608 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 606 for further processing. The FEM circuitry 608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 606 for transmission through one or more of the one or more antennas 610. In various embodiments, amplification by either the transmit signal path or the receive signal path may be accomplished only in the RF circuitry 606, only in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[0241] In some embodiments, the FEM circuit 608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 608 may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to the RF circuit 606). The transmit signal path of the FEM circuit 608 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 606); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 610).

[0242] In some embodiments, PMC 612 can manage the power provided to baseband circuit 604. Specifically, PMC 612 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 600 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 612 can generally be included. PMC 612 can improve power conversion efficiency while providing the desired specific implementation size and heat dissipation characteristics.

[0243] Figure 6 PMC 612 is shown coupled only to baseband circuit 604. However, in other embodiments, PMC 612 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuit 602, RF circuit 606, or FEM 608) and perform similar power management operations.

[0244] In some embodiments, the PMC 612 may control or otherwise be part of various power saving mechanisms of the device 600. For example, if the device 600 is in the RRC_CONNECTED state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 600 may be powered off for short time intervals, thereby saving power.

[0245] If there is no data traffic activity for an extended period of time, the device 600 may transition to the RRC Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 600 may not be able to receive data in this state, and in order to receive data, it must transition back to the RRC Connected state.

[0246] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0247] The processor of the application circuit 602 and the processor of the baseband circuit 604 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 604 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 602 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0248] Figure 7 An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 6 The baseband circuit 604 may include processors 604A-604E and a memory 604G used by the processors. Each of the processors 604A-604E may include a memory interface 704A-704E for sending / receiving data to / from the memory 604G, respectively.

[0249] The baseband circuit 604 may also include: one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 712 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 604); an application circuit interface 714 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 604); Figure 6 RF circuit interface 716 (for example, for sending / receiving data to / from the application circuit 602); Figure 6 an interface for sending / receiving data to / from a RF circuit 606); a wireless hardware connection interface 718 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 720 (eg, an interface for sending / receiving power or control signals to / from PMC 612).

[0250] Figure 8 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 8 A schematic diagram of hardware resources 800 is shown, including one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which can be communicatively coupled via a bus 840. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 800.

[0251] Processor 810 (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 812 and processor 814.

[0252] The memory / storage device 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 820 may include, but is not limited to, any type of volatile or non-volatile memory, such as 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.

[0253] The communication resources 830 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 804 or one or more databases 806 via the network 808. For example, the communication resources 830 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g. Low power consumption), components and other communication components.

[0254] The instructions 850 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 810 to perform any one or more of the methods discussed herein. The instructions 850 may reside completely or partially in at least one of the processors 810 (e.g., in a cache memory of the processor), the memory / storage device 820, or any suitable combination thereof. In addition, any portion of the instructions 850 may be transmitted to the hardware resources 800 from any combination of the peripheral device 804 or the database 806. Therefore, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable media and machine-readable media.

[0255] In various embodiments, Figures 5 to 8 Equipment / components, especially Figure 7 The baseband circuit can be used to practice all or part of Figures 1 to 3 Any of the depicted operational flows / algorithm structures.

[0256] Figure 1 An example of an operation flow / algorithm structure that may be performed by a user equipment (UE) according to some embodiments is depicted in . In this example, the operation flow / algorithm structure 100 may include retrieving a first fifth generation globally unique temporary identifier (5G-GUTI) allocated by a public land mobile network (PLMN) to the UE from a memory at 105. The operation flow / algorithm structure 100 may also include generating a registration request message including the first 5G-GUTI at 110. The operation flow / algorithm structure 100 may also include encoding the registration request message for transmission to a fifth generation core (5GC) network of a second PLMN at 115. The operation flow / algorithm structure 100 may also include receiving a registration acceptance message including a second 5G-GUTI at 120. The operation flow / algorithm structure 100 may also include accessing the second PLMN using the second 5G-GUTI at 125.

[0257] Figure 2 Another example of an operational flow / algorithm structure that may be performed by a next generation Node B (gNB) according to some embodiments is depicted in . In this example, the operational flow / algorithm structure 200 may include receiving a registration request message from a user equipment (UE) at 205, the registration request message including a first fifth generation globally unique temporary identifier (5G-GUTI) for the UE. The operational flow / algorithm structure 200 may also include allocating a second 5G-GUTI that the UE will use to access a public land mobile network (PLMN) at 210. The operational flow / algorithm structure 200 may also include encoding a registration accept message for transmission to the UE at 215, the registration accept message including the second 5G-GUTI.

[0258] Figure 3 Another example of an operational flow / algorithm structure that may be performed by a UE according to some embodiments is depicted in . In this example, the operational flow / algorithm structure 300 may include generating a first message at 305, the first message including a first fifth generation globally unique temporary identifier (5G-GUTI) allocated by a first public land mobile network (PLMN) to the UE. The operational flow / algorithm structure 300 may also include encoding the first message for transmission to a fifth generation core (5GC) network of a second PLMN at 310. The operational flow / algorithm structure 300 may also include receiving a second message including a second 5G-GUTI at 315. The operational flow / algorithm structure 300 may also include accessing the second PLMN using the second 5G-GUTI at 320.

[0259] Example

[0260] Some non-limiting examples are provided below.

[0261] Embodiment 1 includes a device of a user equipment (UE), the device comprising: a memory, the memory being used to store a first fifth generation globally unique temporary identifier (5G-GUTI) allocated to the UE by a public land mobile network (PLMN); and a processing circuit, the processing circuit being coupled to the memory to: retrieve the first 5G-GUTI from the memory; generate a registration request message including the first 5G-GUTI; encode the registration request message for transmission to a fifth generation core (5GC) network of a second PLMN; receive a registration acceptance message including a second 5G-GUTI; and access the second PLMN using the second 5G-GUTI.

[0262] Embodiment 2 includes an apparatus according to embodiment 1 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by the second PLMN.

[0263] Embodiment 3 includes an apparatus according to embodiment 1 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by a PLMN equivalent to the second PLMN.

[0264] Embodiment 4 includes an apparatus according to embodiment 1 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by a PLMN that is not the second PLMN and is not equivalent to the second PLMN.

[0265] Embodiment 5 includes the apparatus of embodiment 1 or some other embodiments herein, wherein the registration request message is used to register to access the second PLMN while connected to the first PLMN.

[0266] Embodiment 6 includes an apparatus according to embodiment 5 or some other embodiments herein, wherein the processing circuit is used to access the second PLMN using the second 5G-GUTI and access the first PLMN using the first 5G-GUTI.

[0267] Embodiment 6a includes an apparatus according to embodiment 5 or some other embodiments herein, wherein the first PLMN is accessed via a first access type, and the second PLMN is accessed via a second access type, and the second PLMN is the same as or equivalent to the first PLMN.

[0268] Embodiment 6b includes the apparatus of embodiment 6a or some other embodiments herein, wherein the first access type is a non-3GPP access and the second access type is a 3GPP access, or vice versa.

[0269] Embodiment 7 includes the apparatus of embodiment 1 or some other embodiments herein, wherein the registration accept message includes an indication that the UE successfully registered for both 3rd Generation Partnership Project (3GPP) access and non-3GPP access.

[0270] Embodiment 7a comprises the apparatus described in accordance with embodiment 7 or some other embodiments herein, wherein the registration acceptance message comprises an indication that the second 5G-GUTI should also be used in the first access.

[0271] Embodiment 7b includes an apparatus according to embodiment 7 or some other embodiments herein, wherein, in the absence of an indication, the UE maintains the first 5G-GUTI for use in the first access.

[0272] Embodiment 8 comprises one or more computer-readable media storing instructions that, when executed by one or more processors, cause a fifth generation core (5GC) network to: receive a registration request message from a user equipment (UE), the registration request message comprising a first fifth generation globally unique temporary identifier (5G-GUTI) for the UE; allocate a second 5G-GUTI to be used by the UE to access a second public land mobile network (PLMN); and encode a registration acceptance message for transmission to the UE, the registration acceptance message comprising the second 5G-GUTI.

[0273] Embodiment 9 includes one or more computer-readable media according to embodiment 8 or some other embodiments herein, wherein the instructions are also used to identify a change between a first access mobility function (AMF) associated with the UE to a second AMF associated with the UE.

[0274] Embodiment 10 includes one or more computer-readable media according to embodiment 9 or some other embodiments herein, wherein the instructions are further used to: identify an indication of an existing next generation application protocol (NGAP) association of the UE with a non-3GPP interworking function (N3IWF) from the first AMF; identify an N2 connection to the N3IWF for the second AMF; and create an NGAP UE association with the N3IWF for the second AMF.

[0275] Embodiment 11 includes one or more computer-readable media according to embodiment 8 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by the second PLMN or a PLMN equivalent to the second PLMN.

[0276] Embodiment 12 includes one or more computer-readable media according to embodiment 8 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by a PLMN that is not the second PLMN and is not equivalent to the second PLMN.

[0277] Embodiment 13 includes one or more computer-readable media according to embodiment 8 or some other embodiments herein, wherein the registration accept message includes an indication that the UE successfully registered for both third generation partnership project (3GPP) access and non-3GPP access.

[0278] Embodiment 14 comprises one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to perform the following operations: generate a first message comprising a first fifth generation globally unique temporary identifier (5G-GUTI) allocated to the UE by a public land mobile network (PLMN); and encode the first message for transmission to a fifth generation core (5GC) network of a second PLMN; receive a second message comprising a second 5G-GUTI; and access the second public land mobile network (PLMN) using the second 5G-GUTI.

[0279] Embodiment 15 includes one or more computer-readable media as described in embodiment 14 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by the second PLMN.

[0280] Embodiment 16 includes one or more computer-readable media according to embodiment 14 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by a PLMN equivalent to the second PLMN.

[0281] Embodiment 17 includes one or more computer-readable media according to embodiment 14 or some other embodiments herein, wherein the first 5G-GUTI is a native 5G-GUTI allocated by a PLMN that is not the second PLMN and is not equivalent to the second PLMN.

[0282] Embodiment 18 includes one or more computer-readable media as described in embodiment 14 or some other embodiments herein, wherein the first message is used to register to access the second PLMN while connected to the first PLMN.

[0283] Embodiment 19 includes one or more computer-readable media according to embodiment 18 or some other embodiments herein, wherein the instructions are used to access the second PLMN using the second 5G-GUTI and access the first PLMN using the first 5G-GUTI.

[0284] Embodiment 20 includes one or more computer-readable media as described in embodiment 14 or some other embodiments herein, wherein the second message includes an indication that the UE successfully registered for both third generation partnership project (3GPP) access and non-3GPP access.

[0285] Example 21 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1-20, or any other method or process described herein.

[0286] Embodiment 22 may include one or more non-transitory computer-readable media, which include 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 Embodiments 1-20 or any other method or process described herein.

[0287] Embodiment 23 may include a device comprising logic components, modules and / or circuits for performing one or more elements of the method described in or related to any of Embodiments 1-20 or any other method or process described herein.

[0288] Example 24 may include methods, techniques, or processes as described or related to any of Examples 1-20, or portions or components thereof.

[0289] Embodiment 25 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, as described or related to any one of Embodiments 1-20.

[0290] Embodiment 26 may include a method of communicating in a wireless network as shown and described herein.

[0291] Embodiment 27 may include a system for providing wireless communications as shown and described herein.

[0292] Embodiment 28 may include an apparatus for providing wireless communications as shown and described herein.

[0293] The description of the specific implementations shown herein, including the specific implementations described in the Abstract, is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Although specific implementations and examples are described herein for illustrative purposes, various alternative or equivalent embodiments or implementations calculated to achieve the same purpose can be made based on the above detailed description without departing from the scope of the present disclosure.

Claims

1. A user equipment UE, comprising: a memory storing a first fifth generation globally unique temporary identifier 5G-GUTI allocated by a first public land mobile network PLMN to the UE; as well as A processing circuit, the processing circuit is coupled to the memory, and the processing circuit is configured to: retrieving the first 5G-GUTI from the memory; generating a registration request message including the first 5G-GUTI; Encoding the registration request message for transmission to a fifth generation core 5GC network of a second PLMN; In response to the UE being registered in the first PLMN and a connection with an access node of the first PLMN being established, receiving a registration accept message including a second 5G-GUTI, wherein the registration accept message indicates that the second 5G-GUTI is to be used to access the first PLMN and the second PLMN; as well as Use the second 5G-GUTI to access the first PLMN or the second PLMN.

2. The UE of claim 1, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by the second PLMN.

3. The UE of claim 1, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by a third PLMN equivalent to the second PLMN.

4. The UE of claim 1, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by a third PLMN that is not the second PLMN and is not equivalent to the second PLMN.

5. The UE of claim 1, wherein the registration request message is configured to register for accessing the second PLMN while connected to the first PLMN. 6 . The UE of claim 1 , wherein the registration accept message includes an indication that the UE is successfully registered for 3rd Generation Partnership Project (3GPP) access and non-3GPP access.

7. The UE according to claim 1, wherein the registration acceptance message includes an explicit indication for indicating that the second 5G-GUTI is to be used to access the first PLMN and the second PLMN.

8. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the fifth generation core 5GC network to perform the following operations: receiving a registration request message from a user equipment UE, the registration request message including a first fifth generation globally unique temporary identifier 5G-GUTI for the UE; allocating a second 5G-GUTI to be used by the UE to access a first public land mobile network PLMN; as well as In response to the UE being registered to the first PLMN and a connection with an access node of the first PLMN being established, a registration accept message is encoded for transmission to the UE, the registration accept message including the second 5G-GUTI, wherein the registration accept message indicates that the second 5G-GUTI is to be used to access the first PLMN and the second PLMN.

9. One or more non-transitory computer-readable media according to claim 8, wherein the instructions further cause the 5GC network to identify a change between a first access mobility function AMF associated with the UE and a second AMF associated with the UE.

10. The one or more non-transitory computer-readable media of claim 9, wherein the instructions further cause the 5GC network to: identifying an indication from the first AMF of an existing Next Generation Application Protocol NGAP association of the UE to a non-3GPP interworking function N3IWF; identifying an N2 connection to the N3IWF for the second AMF; and Create an NGAP UE association to the N3IWF for the second AMF.

11. The one or more non-transitory computer-readable media of claim 8, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by the first PLMN or a second PLMN equivalent to the first PLMN.

12. The one or more non-transitory computer-readable media of claim 8, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by a second PLMN that is not the first PLMN and is not equivalent to the first PLMN.

13. One or more non-transitory computer-readable media according to claim 8, wherein the registration accept message includes an explicit indication that the second 5G-GUTI is to be used to access the first PLMN and the second PLMN.

14. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the user equipment UE to perform the following operations: Generate a first message, the first message comprising a first fifth generation globally unique temporary identifier 5G-GUTI allocated by a first public land mobile network PLMN to the UE; as well as Encoding the first message for transmission to a fifth generation core 5GC network of a second PLMN; In response to the UE being registered with the first PLMN and a connection with an access node of the first PLMN being established, receiving a second message including a second 5G-GUTI, wherein the second message indicates that the first PLMN and the second PLMN are to be accessed using the second 5G-GUTI; as well as Use the second 5G-GUTI to access the first PLMN or the second PLMN.

15. The one or more non-transitory computer-readable media of claim 14, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by the second PLMN.

16. The one or more non-transitory computer-readable media of claim 14, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by a third PLMN equivalent to the second PLMN.

17. The one or more non-transitory computer-readable media of claim 14, wherein the first 5G-GUTI comprises a native 5G-GUTI allocated by a third PLMN that is not the second PLMN and is not equivalent to the second PLMN.

18. The one or more non-transitory computer-readable media of claim 14, wherein the first message is configured to register for access to the second PLMN while connected to the first PLMN.

19. The one or more non-transitory computer-readable media of claim 14, wherein the indication comprises an indication that the UE successfully registered for Third Generation Partnership Project (3GPP) access and non-3GPP access.

20. The one or more non-transitory computer-readable media of claim 14, wherein the second message includes an explicit indication that the second 5G-GUTI is to be used to access the first PLMN and the second PLMN.

Images