Two registrations of a linked dual-boot device

Abstract

An Access and Mobility Management (AMF) function for a communication network is provided. The AMF is configured to receive, via a first 3GPP access path, a first registration request from a dual-booting device for registering the dual-booting device with the AMF. The first registration request includes a first identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device. The AMF is also configured to: obtain, from a Unified Data Management Entity (UDI), first subscription information associated with the first UEI, the first subscription information including a first linked subscription identifier; and send, to the dual-booting device, a first registration acceptance message including a first Globally Unique Temporary Identifier (GUTI) assigned to the first registration of the dual-booting device. The AMF is further configured to receive, via a second 3GPP access path, a second registration request from the dual-booting device for registering the dual-booting device with the AMF. The second registration request includes a second identifier associated with a second UEI of the dual-booting device. AMF is also configured to: obtain second subscription information associated with a second user equipment identifier from a unified data management entity, the second subscription information including a second linked subscription identifier; determine that the first subscription information and the second subscription information are linked based on the first linked subscription identifier and the second linked subscription identifier; and send a second registration acceptance message to the dual-boot device, the second registration acceptance message including a link identifier and a second GUTI assigned to the second registration of the dual-boot device, wherein the link identifier indicates that AMF has linked the first registration and the second registration.

Description

[0001] Related applications This application claims the priority benefit of U.S. Provisional Patent Application No. 63 / 624,595, filed January 24, 2025, which is incorporated herein by reference as if reproduced in its entirety. Technical Field

[0002] This application generally relates to apparatus and methods for processing multiple registrations made by dual-booting devices to a 5G communication network, which supports (e.g., is configured to) switch, split, and bootstrap user plane traffic to different access paths for multi-access data sessions. Background Technology

[0003] Fifth-generation (5G) mobile communication networks (e.g., cellular networks) offer increased bandwidth compared to earlier generations of mobile communication networks (e.g., fourth-generation mobile communication networks) and provide robust low-latency connectivity and massive machine-to-machine connections for the Internet of Things (IoT). 5G communication networks (e.g., cellular networks, referred to as "5G networks") allow communication devices (such as user equipment (UEs) or mobile communication devices) to access the communication network via different types of access networks, including 3GPP access networks and non-3GPP access networks. 3GPP access networks can include terrestrial networks or non-terrestrial networks (e.g., New Radio (NR) or satellite).

[0004] 5G communication networks can support access traffic switching, splitting, and redirection (e.g., ATSSS rules can be configured to specify which access network each traffic flow should use). Improvements in ATSSS-enabled communication networks are expected. Summary of the Invention

[0005] The following description of the invention is intended to introduce various aspects of the specific implementation methods to the reader, and is not intended to limit or define any invention.

[0006] In a first aspect, an apparatus for a communication network is provided. The apparatus includes an Access and Mobility Management (AMF) function. The AMF is configured to: receive, via a first 3GPP access path, a first registration request from a dual-steer device for registering the dual-steer device with the AMF, the first registration request including a first hidden identifier associated with a first UE identifier of the dual-steer device; obtain, from a unified data management entity, first subscription information associated with the first UE identifier, the first subscription information including a first linked subscription identifier; send, to the dual-steer device, a first registration acceptance message including a first globally unique temporary identifier (GUTI) assigned to the dual-steer device for the first registration; receive, via a second 3GPP access path, a second registration request from the dual-steer device for registering the dual-steer device with the AMF, the second registration request including a second hidden identifier associated with a second UE identifier of the dual-steer device; obtain, from a unified data management entity, second subscription information associated with the second UE identifier, the second subscription information including a second linked subscription identifier; determine, based on the first linked subscription identifier and the second linked subscription identifier, that the first subscription information and the second subscription information are linked; and send, to the dual-steer device, a second registration acceptance message including a link identifier and a second GUTI assigned to the dual-steer device for the second registration.

[0007] In a second aspect, a method performed by an Access and Mobility Management Function (AMF) is provided. The method includes receiving, via a first 3GPP access path, a dual-booting device for registering the dual-booting device with the AMF, the first registration request including a first hidden identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device; obtaining, from a Unified Data Management Entity (UDI), first subscription information associated with the first UEI, the first subscription information including a first linked subscription identifier; sending, to the dual-booting device, a first registration acceptance message including a first Globally Unique Temporary Identifier (GUTI) assigned to the first registration of the dual-booting device; receiving, via a second 3GPP access path, a second registration request for registering the dual-booting device with the AMF, the second registration request including a second hidden identifier associated with a second UEI of the dual-booting device; obtaining, from the UDI, second subscription information associated with the second UEI, the second subscription information including a second linked subscription identifier; determining, based on the first linked subscription identifier and the second linked subscription identifier, that the first subscription information and the second subscription information are linked; and sending, to the dual-booting device, a second registration acceptance message including a link identifier and a second GUTI assigned to the second registration of the dual-booting device.

[0008] In a third aspect, an apparatus for a communication network is provided. The apparatus includes at least one processor and at least one memory storing instructions for the Access and Mobility Management Function (AMF), wherein the instructions are executed by the at least one processor causing the apparatus to at least: receive, via a first 3GPP access path, a dual-booting device for registering the dual-booting device with the AMF, the first registration request including a first hidden identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device; obtain, from a Unified Data Management Entity (UDI), first subscription information associated with the first UEI, the first subscription information including a first linked subscription identifier; send, to the dual-booting device, a first registration acceptance message including a first Globally Unique Temporary Identifier (GUTI) assigned to the first registration of the dual-booting device; receive, via a second 3GPP access path, a dual-booting device for registering the dual-booting device with the AMF, the second registration request including a second hidden identifier associated with a second UEI of the dual-booting device; obtain, from the UDI, second subscription information associated with the second UEI, the second subscription information including a second linked subscription identifier; determine, based on the first linked subscription identifier and the second linked subscription identifier, that the first subscription information and the second subscription information are linked; and send, to the dual-booting device, a second registration acceptance message including a link identifier and a second GUTI assigned to the second registration of the dual-booting device.

[0009] In a fourth aspect, an apparatus for a communication network is provided, the apparatus comprising: an Access and Mobility Management Function (AMF). The AMF is configured to: receive, via a first 3GPP access path, a dual-booting device for registering the dual-booting device with the AMF, the first registration request including a first identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device; obtain, from a Unified Data Management Entity (UDI), first subscription information associated with the first UEI; send, to the dual-booting device, a first registration acceptance message including a first Globally Unique Temporary Identifier (GUTI) assigned to the first registration of the dual-booting device; receive, via a second 3GPP access path, a second registration request for registering the dual-booting device with the AMF, the second registration request including a second identifier associated with a second UEI of the dual-booting device and a GUTI assigned to the first registration of the dual-booting device; obtain, from the UMI, second subscription information associated with the second UEI, and determine that the first and second subscription information are linked based on the GUTI included in the second registration request; and send, to the dual-booting device, a second registration acceptance message including a second GUTI assigned to the second registration of the dual-booting device.

[0010] In a fifth aspect, a method is provided performed by an Access and Mobility Management Function (AMF) of a communication network. The method includes: receiving, via a first 3GPP access path, a dual-booting device for registering the dual-booting device with the AMF, the first registration request including a first identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device; obtaining, from a Unified Data Management Entity (UDI), first subscription information associated with the first UEI; sending, to the dual-booting device, a first registration acceptance message including a first Globally Unique Temporary Identifier (GUTI) assigned to the first registration of the dual-booting device; receiving, via a second 3GPP access path, a second registration request for registering the dual-booting device with the AMF, the second registration request including a second identifier associated with a second UEI of the dual-booting device and a GUTI assigned to the first registration of the dual-booting device; obtaining, from the UMI, second subscription information associated with the second UEI, and determining that the first and second subscription information are linked based on the GUTI included in the second registration request; and sending, to the dual-booting device, a second registration acceptance message including a second GUTI assigned to the second registration of the dual-booting device.

[0011] In a sixth aspect, an apparatus for a communication network is provided, the apparatus comprising: at least one processor and at least one memory storing instructions for access and mobility management functions, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: receiving, via a first 3GPP access path, a dual-booting device for registering the dual-booting device with an AMF, the first registration request including a first identifier associated with a first user equipment identifier of the dual-booting device; obtaining, from a unified data management entity, first subscription information associated with the first user equipment identifier; sending, to the dual-booting device, a first registration acceptance message including a first globally unique temporary identifier (GUTI) assigned to the first registration of the dual-booting device; receiving, via a second 3GPP access path, a dual-booting device for registering the dual-booting device with an AMF, the second registration request including a second identifier associated with a second user equipment identifier of the dual-booting device and a GUTI assigned to the first registration of the dual-booting device; obtaining, from the unified data management entity, second subscription information associated with the second user equipment identifier, and determining that the first subscription information and the second subscription information are linked based on the GUTI included in the second registration request; and sending, to the dual-booting device, a second registration acceptance message including a second GUTI assigned to the second registration of the dual-booting device.

[0012] In some examples of any of the first, second, third, fourth, fifth, and sixth aspects, the first link subscription identifier includes the second user device identifier, and the second link subscription identifier includes the first user device identifier.

[0013] In some examples of any of the first, second, third, fourth, fifth, and sixth aspects, the link identifier includes the first GUTI.

[0014] In some examples of any of the first to sixth aspects, the first user equipment identifier is a first subscription permanent identifier (SUPI), and the first identifier associated with the first user equipment identifier is a first subscription hidden identifier (SUCI) generated based on the first SUPI; the second user equipment identifier associated with the second user equipment identifier is a second SUPI, and the second identifier is a second SUCI generated based on the second SUPI.

[0015] In some examples of any of the first to sixth aspects, the first user equipment identifier is a first subscription permanence identifier (SUPI) and the first identifier is a first GUTI; the second user equipment identifier is a second subscription permanence identifier (SUPI) and the first identifier is a second GUTI.

[0016] In some examples of any of the first to sixth aspects, the dual-boot device includes two user equipments, wherein a first registration request is received from a first user equipment (UE) of the two user equipments, and a second registration request is received from a second user equipment (UE) of the two user equipments.

[0017] In some examples of any of the first to sixth aspects, the dual-boot device includes two subscriber identity modules, wherein a first user equipment identifier includes a first subscription permanent identifier associated with the first subscriber identity module of the two subscriber identity modules, and a second user equipment identifier includes a second subscription permanent identifier associated with the second subscriber identity module of the two subscriber identity modules.

[0018] In some examples of any of the first to sixth aspects, it is determined that: based on the first link subscription information and the second link subscription information, the first subscription information and the second subscription information are linked to the subscription profile of the dual-boot device.

[0019] In some examples of any of the first to sixth aspects, the first user equipment identifier includes a first subscription permanent identifier of the first user equipment, and the second user equipment identifier includes a second subscription permanent identifier of the second user equipment.

[0020] In some examples of any of the first to sixth aspects, the first 3GPP access path includes a first RRC connection between the dual-booting device and the radio access network node and a first signaling connection between the RAN node and the AMF, and the second 3GPP access path includes a second RRC connection between the dual-booting device and the RAN node and a second signaling connection between the RAN node and the AMF.

[0021] In some examples of any of the first to sixth aspects, the AMF is also configured to perform and / or the method further includes: after obtaining first subscription information, sending a first request to the RAN node for establishing a first user equipment context for the first user equipment; and after obtaining second subscription information, sending a second request to the RAN node for establishing a second user equipment context for a second user equipment associated with the first user equipment context of the first user equipment.

[0022] In some examples of any of the first to sixth aspects, the first request includes a first initial context establishment request message, which includes a first user equipment context identifier for association with a first user equipment context; the second request includes a second initial context establishment request message, which includes a second user equipment context identifier for association with a second user equipment context and link information indicating to the RAN node that the first user equipment context will be associated with the second user equipment context.

[0023] In some examples of any of the first to sixth aspects, the first user equipment context identifier includes a first next-generation application protocol (NGAP) user equipment identifier, and the second user equipment context identifier includes a second NGAP UE ID.

[0024] In some examples of any of the first to sixth aspects, the linking information includes a first user equipment context identifier.

[0025] In a seventh aspect, a dual-booting device is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the dual-booting device to perform at least the following operations: transmitting a first registration request for registering the dual-booting device with a communication network via a first 3GPP access path, the first registration request including a first identifier associated with a first user equipment identifier of the dual-booting device; receiving a first registration acceptance message via the first 3GPP access path, the first registration acceptance message including a first globally unique temporary identifier (GUTI) of a first registration assigned to the dual-booting device by the communication network; transmitting a second registration request for registering the dual-booting device with the communication network via a second 3GPP access path, the second registration request including a second identifier associated with a second user equipment identifier of the dual-booting device and the first GUTI; and receiving a second registration acceptance message via the second 3GPP access path, the second registration acceptance message including a link identifier and a second GUTI of a second registration assigned to the dual-booting device by the communication network, wherein the link identifier indicates that the communication network has linked the first registration and the second registration.

[0026] In an eighth aspect, a method performed by a dual-booting device is provided. The method includes: sending a first registration request for registering the dual-booting device with a communication network via a first 3GPP access path, the first registration request including a first identifier associated with a first user equipment identifier of the dual-booting device; receiving a first registration acceptance message via the first 3GPP access path, the first registration acceptance message including a first globally unique temporary identifier (GUTI) of a first registration assigned to the dual-booting device by the communication network; sending a second registration request for registering the dual-booting device with the communication network via a second 3GPP access path, the second registration request including a second identifier associated with a second user equipment identifier of the dual-booting device and the first GUTI; and receiving a second registration acceptance message via the second 3GPP access path, the second registration acceptance message including a link identifier and a second GUTI of a second registration assigned to the dual-booting device by the communication network, wherein the link identifier indicates that the communication network has linked the first registration and the second registration.

[0027] In a ninth aspect, a dual-booting device is provided, comprising: components for transmitting a first registration request to a communication network to register the dual-booting device via a first 3GPP access path, the first registration request including a first identifier associated with a first user equipment identifier of the dual-booting device; components for receiving a first registration acceptance message via the first 3GPP access path, the first registration acceptance message including a first globally unique temporary identifier (GUTI) of a first registration assigned to the dual-booting device by the communication network; components for transmitting a second registration request to the communication network to register the dual-booting device via a second 3GPP access path, the second registration request including a second identifier associated with a second user equipment identifier of the dual-booting device and the first GUTI; and components for receiving a second registration acceptance message via the second 3GPP access path, the second registration acceptance message including a link identifier and a second GUTI of a second registration assigned to the dual-booting device by the communication network, wherein the link identifier indicates that the communication network has linked the first registration and the second registration.

[0028] In some examples of any of the seventh, eighth, and ninth aspects, the link identifier includes the first GUTI.

[0029] According to some aspects, this disclosure provides a non-transitory computer-readable medium storing computer-executable instructions. When executed, these computer-executable instructions configure a processor to perform any of the methods described herein. Attached Figure Description

[0030] The accompanying drawings are used to illustrate various examples of the articles, methods, and systems described herein and are not intended to limit the scope of the teachings in any way. In the drawings: Figure 1 This is a schematic block diagram of a dual-booting device communicating via a communication network and a data network according to some embodiments; Figure 2 This is a block diagram of an example dual-boot device according to at least some embodiments; Figure 3 An example registration process for registering a dual-boot device to a communication network, according to at least some embodiments, is shown; Figure 4 Example context information for a dual-boot device according to some embodiments is shown; Figure 5 Another example initial registration process for initially registering a dual-boot device to a communication network, according to at least some embodiments, is shown; Figure 6 Another example process for initially registering a dual-boot device to a communication network, according to at least some embodiments, is shown; Figure 7An example process for registering a dual-booting device to a communication network and establishing a PDU session for the dual-booting device, according to at least some embodiments, is shown; Figure 8 Example methods performed by the access and mobility management functions of a communication network according to some embodiments are shown; Figure 9 Another example method performed by the access and mobility management function of a communication network according to some embodiments is shown; Figure 10 An example method performed by a dual-boot device according to some embodiments is shown. Detailed Implementation

[0031] Various aspects of this disclosure generally relate to methods and apparatus for processing multiple registrations made by a dual-boot device to a communication network that supports (e.g., is configured for) ATSSS.

[0032] Now for reference Figure 1 The diagram illustrates schematic block diagrams according to at least some embodiments of the present disclosure, wherein a dual-boot device 170 communicates with a data network 110 via a communication network 100. The communication network 100 includes a radio access network (RAN) 130 and a core network 120.

[0033] Radio access network (RAN) 130 may include a terrestrial network (TN) and / or a non-terrestrial network (NTN). The NTN may include a satellite network and ground stations connected to the core network 130, the satellite network comprising multiple satellites located in one or more different orbits, such as geostationary orbit (GEO), medium Earth orbit (MEO), and low Earth orbit (LEO). The TN may include one or more radio access nodes. For example, the TN may be NG-RAN, and one or more RAN nodes may be gNBs. A gNB may include a centralized unit (e.g., gNB-CU) and one or more distributed units (e.g., one or more gNB-DUs) linked to the centralized unit (e.g., gNB-CU) via an F1 interface.

[0034] Core network 120 may include a 5G core network (e.g., a core network operating according to 3GPP standards for NR). Core network 108 has a service-based architecture and includes multiple network functions, including an Access and Mobility Management Function (AMF) configured to perform registration management, reachability management, and connection management, and to handle Next Generation Application Protocol Signaling (NGAP) transmitted between the AMF and the 5G RAN nodes of RAN 130. Core network 120 also includes Policy Control Functions (PCFs) (including AM PCFs and / or SM PCFs, which are described in further detail below), session management functions, and a Unified Data Repository (UDM) configured to store subscription profiles of subscribers of communication network 100. Core network 120 may include other network functions, including, for example, Application Functions (AF), Authentication Server Functions (AUSF), Network Open Functions (NEF), Network Repository Functions (NRF), Network Slice Selection Functions (NSSF), and User Plane Functions (UPF). For ease of illustration, other network functions of core network 108, such as Binding Support Functions (BSF) and Charging Functions (CHF), are not shown. The functions of these other network functions of the core network are well known to those skilled in the art, and therefore will not be described in detail.

[0035] The dual-booting device 170 may include: (a) two Universal Subscriber Identity Modules (USIMs), or (b) two different user equipments, each of which has a USIM. The dual-booting device 170 may establish two different 3GPP access paths for communicating with the core network 120 (e.g., sending and receiving control plane signaling to and from the core network 120). For example, in scenario (a), the dual-booting device establishes a 3GPP access path associated with each subscriber USIM. This 3GPP access path is a signaling connection between the dual-booting device 170 and the core network 120 (e.g., the AMF of the core network 120), and includes an RRC connection between the dual-booting device 170 and the RAN node of the RAN 130, and a signaling connection between the RAN node of the RAN 130 and the core network 120 (e.g., the AMF of the core network 120).

[0036] although Figure 1 Only one communication network is shown, but it should be understood that the dual-boot device 170 can communicate with two different communication networks, and each communication network may include a RAN and a core network. For example, the two communication networks may include two public land mobile networks, one public land mobile network and a separate non-public network, or two separate non-public networks.

[0037] Now for reference Figure 2A simplified block diagram of an apparatus according to at least some embodiments is shown. Apparatus 200 implements or includes one or more networking functions, including AMF. Apparatus 200 may be a computer or computing system, such as a standalone computer, a distributed computer, or a cloud computing system; in the case of virtualization, apparatus 200 may be an underlying physical computer providing a virtual machine or container that provides AMF. Apparatus 200 typically has at least one processor 202 operatively coupled to at least one memory 204 and at least one input / output device 206.

[0038] At least one memory 204 includes volatile memory storing instructions for one or more network functions, including instructions for an AMF (e.g., AMF 3xx) executable by at least one processor 202, and input and output data used or generated during the execution of the instructions. Execution of the AMF instructions causes the AMF to perform or... Figure 8 and Figure 9 The method is shown in the figure and described in detail below. At least one memory 204 may also include non-volatile memory for storing input and / or output data and program code containing executable instructions.

[0039] The processor 202 can transmit or receive data via I / O device 206 (such as a network communication interface (not shown)), or as appropriate via any additional input / output device 206.

[0040] As described above, the dual-booting device 170 can register with the core network 120 (e.g., the AMF) via multiple (e.g., two different) 3GPP access paths by sending a registration request to the core network 120 of the communication network 100 via each corresponding access path. However, the core network 120 (e.g., the AMF of the core network 120) is unaware that the multiple registration requests received via multiple 3GPP access paths are associated with the same device (e.g., originating from the dual-booting device 170), and therefore the AMF will treat these multiple registrations as registrations from different devices.

[0041] In one example aspect of this disclosure, the core network (e.g., AMF) of the communication network is configured to handle multiple registrations received from a dual-booting device via multiple 3GPP access paths. Since the dual-booting device has two different subscriptions to the core network and registers with the core network using these two different subscriptions via two different 3GPP access paths, the core network needs to associate the two registrations made by the dual-booting device to the core network so that the core network can handle policies and rules related to how to switch, bootstrap, or split traffic between two data connections (e.g., PDU sessions) established between the dual-booting device and the core network (e.g., the core network's UPF). The core network (e.g., AMF) uses information received from the dual-booting device 170, or subscription information received from the unified data management entity (e.g., the dual-booting device's subscription profile), to associate the two registrations of the dual-booting device.

[0042] The core network (e.g., AMF) receives registration requests from the dual-booting device 120 via each of the multiple 3GPP access paths, assigns a network identifier (e.g., a globally unique temporary identifier) ​​to each corresponding registration, and determines whether the registration requested via the multiple 3GPP access paths originates from the dual-booting device (e.g., from the same device). Advantageously, this method has almost no impact on RAN 230.

[0043] Now for reference Figure 3 The document illustrates an initial registration process for registering a dual-boot device (e.g., dual-boot device 170) to a communication network (e.g., communication network 100) according to an example embodiment.

[0044] The process begins in step 1. In step 1, the dual-boot device 170 directs traffic to the RAN node of RAN 130 (in... Figure 3 In step 1, the NG-RAN node 310 sends an RRC establishment request message (e.g., an RRC connection request message) to establish an RRC connection between the dual-booting device 170 and the NG-RAN node 310. In step 2, the NG-RAN node 310 sends an RRC establishment response message (e.g., an RRC connection establishment message) to the dual-booting device 170 to establish an RRC connection (e.g., a first RRC connection) between the dual-booting device 170 and the NG-RAN node 310. In step 3, the dual-booting device 170 sends an RRC establishment completion message (e.g., an RRC connection completion message) to the NG-RAN node 310, indicating to the NG-RAN node 310 that an RRC connection (e.g., a first RRC connection) has been established between the dual-booting device 170 and the NG-RAN node 310. The RRC establishment completion message includes a first NAS registration request sent by the dual-booting device 170 for registering itself with the AMF 320. The first NAS registration request includes a first registration identifier (in... Figure 3 (Shown as RegID1). The first registration identifier indicates that the first NAS registration request is for the first registration of dual-booting device 170 to AMF 320. In step 4, NG-RAN node 310 uses the N2 interface to set up and establish a first signaling connection for dual-booting device 170 between NG-RAN node 310 and AMF 320. Therefore, in step 4, a first 3GPP access path for the first registration of dual-booting device 170 is established between dual-booting device 170 and AMF 320, which includes a first RRC connection and a first signaling connection. Also in step 4, NG-RAN node 310 extracts the first NAS registration request from the RRC completion setup message and sends a Next Generation Access Protocol (NGAP) message to AMF 320, which includes the first NAS registration request to AMF 320. At step 5, AMF 320 assigns a first NGAP identifier, which uniquely identifies dual-booting device 170 on the NG interface (in Figure 3 The first UE context for dual-booting device 170 is established at NG-RAN node 310 by sending an initial context establishment message (e.g., NGAP-UE-ID-1) to NG-RAN node 310. The initial context establishment message includes a first NGAP identifier (e.g., NGAP-UE-ID-1). Upon receiving the initial context establishment message, NG-RAN node 310 establishes the first UE context for dual-booting device 170 and associates the first NGAP identifier (e.g., NGAP-UE-ID-1) with the first UE context for dual-booting device 170. In step 6, AMF 320 assigns a first network identifier to dual-booting device 170 and sends a NAS registration acceptance message to dual-booting device 170. The first network identifier assigned to dual-booting device 170 is an identifier that uniquely identifies dual-booting device 170 within the communication network 100 (e.g., within RAN 130 and core network 120). In some cases, the first network identifier is a globally unique temporary identifier (GUTI) or a 5G-GUTI (e.g., NGAP-UE-ID-1). Figure 3 (As shown in 5G-GUTI-1). In some cases, the NAS registration acceptance message includes a first registration identifier (RegID1) and a first network identifier (e.g., Figure 3 (5G-GUTI-1 shown). The first registration identifier (Reg1) is stored by the dual boot device 170 as UE context information associated with the first network identifier (e.g., 5G-GUTI-1) of the dual boot device 170.

[0045] In step 7, dual-booting device 170 sends a second RRC establishment request (e.g., a second RRC connection request message) to NG-RAN node 310. In step 8, NG-RAN node 310 sends a second RRC establishment response message (e.g., a second RRC connection establishment message) to dual-booting device 170 to establish another RRC connection (e.g., a second RRC connection) between dual-booting device 170 and NG-RAN node 130. In step 9, dual-booting device 170 sends a second RRC establishment completion message (e.g., a second RRC connection completion message) to NG-RAN node 310, indicating to NG-RAN node 310 that a second RRC connection has been established between dual-booting device 170 and NG-RAN node 310. The second RRC establishment completion message includes a second NAS registration request sent by dual-booting device 170 for registering itself with AMF 320. A second registration identifier indicates that the second NAS registration request is for a second registration by dual-booting device 170 with AMF 320. In step 10, NG-RAN node 310 uses the N2 interface to set up and establish a second signaling connection between NG-RAN node 310 and AMF 320 for dual-booting device 170. Therefore, in step 10, a second 3GPP access path for the second registration of dual-booting device 170 is established between dual-booting device 170 and AMF 320, which includes a second RRC connection and a second signaling connection. At step 11, AMF 320 assigns a second NGAP identifier, which uniquely identifies dual-booting device 170 on the NG interface (in...). Figure 3The first NGAP identifier (e.g., NGAP-UE-ID-2) is shown in the diagram, and a second initial context establishment message is sent to the NG-RAN node 310 to establish a second UE context for the dual-booting device 170 at the NG-RAN node 310. The second initial context establishment message includes a second NGAP identifier (e.g., NGAP-UE-ID-2) and linking information indicating that the first NGAP identifier and the second NGAP identifier are used for the dual-booting device 170 (e.g., the first UE context and the second UE context are used for the same device). Upon receiving the second initial context establishment message, the NG-RAN node 310 establishes a second UE context for the dual-booting device 170 and associates the second NGAP identifier (e.g., NGAP-UE-ID-1) with the second UE context for the dual-booting device 170. In some cases, the linking information is a linked UE-ID, and the linked UE-ID is set to the first NGAP identifier (e.g., NGAP-UE-ID-1). In step 12, the AMF 320 sends a second NAS registration acceptance message to the dual-booting device 170. In some cases, the second NAS registration acceptance message includes a second registration identifier (Reg2) and a second network identifier for the dual-boot device (e.g., 5G-GUTI-2).

[0046] After step 12, the dual-booting device 170 enters RRC idle mode and releases the first and second RRC connections. In step 13, the dual-booting device 170, in RRC idle mode, performs RRC connection establishment. The dual-booting device 170 determines that an RRC connection needs to be established for the first registration of the dual-booting device 170. Subsequently, the dual-booting device 170 selects a first network identifier (e.g., 5G-GUTI-1), obtains 5G-S-TMSI-1 from the first network identifier (e.g., 5G-GUTI-1), and sends an RRC establishment request (e.g., an RRC connection request) including 5G-S-TMSI-1 to the NG-RAN node 310. In step 14, the NG-RAN node 310 sends an RRC establishment response (e.g., an RRC connection response) to the dual-booting device 170 to establish an RRC connection (e.g., a first RRC connection) between the dual-booting device 170 and the NG-RAN node 130. In step 15, the dual-booting device 170 sends an RRC establishment completion message to the NG-RAN node 310. The RRC establishment completion message includes a NAS registration request for updating the first registration made by the dual-booting device 170 to the AMF 320, and 5G-S-TMSI-1. The NAS registration request includes a first registration identifier (Reg ID1) and a first network identifier of the dual-booting device 170 (e.g., 5G-GUTI-1).

[0047] In other example embodiments, in step 13, the dual-booting device 170 determines that an RRC connection needs to be established for the second registration of the dual-booting device 170, selects a second network identifier (e.g., 5G-GUTI-2), obtains 5G-S-TMSI-2 from the second network identifier (e.g., 5G-GUTI-2), and sends an RRC establishment request (e.g., an RRC connection request) including 5G-S-TMSI-2 to the NG-RAN node 310. In step 14, the NG-RAN node 310 sends an RRC establishment response (e.g., an RRC connection response) to the dual-booting device 170 to establish an RRC connection (e.g., a second RRC connection) between the dual-booting device 170 and the NG-RAN node 130. In step 15, the dual-booting device 170 sends an RRC establishment completion message to the NG-RAN node 310, the RRC establishment completion message including a NAS registration request for updating the first registration of the dual-booting device 170 with the AMF 320 and 5G-S-TMSI-1. The NAS registration request includes a first registration identifier (Reg ID1) and a first network identifier (e.g., 5G-GUTI-1) for the dual-boot device 170.

[0048] In relation to Figure 3 During the description, the AMF 320 assigns a different 5G Globally Unique Temporary Identifier (5G-GUTI) to each registration made by the dual-booting device 170 to the AMF 320 via the 3GPP access path. Assigning a different 5G-GUTI to each registration of the dual-booting device 170 enables differentiation of the 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI) sent via RRC, thereby differentiating the respective RRC connections between the dual-booting device 170 and the NG-RAN node 310, as well as the Next Generation Application Protocol (NGAP) associations for different registrations of the same device 170. This allows the NG-RAN node (e.g., NG-RAN node 130) to associate N2 and N3 connections for different registrations. Each NGAP association can be associated with the tuple {5G-S-TMSI, UE NGAP ID}. The AMF 320 can associate the two registrations if they are registered with the same Subscription Permanent Identifier (SUPI), or if they are registered with different Subscription Permanent Identifiers (SUPI) and the AMF receives an indication from the device or UDM that the two registrations need to be associated.

[0049] In some cases, the dual-booting device 170 maintains the UE context for each 5G-GUTI / S-TMSI, including the Registration Management (RM) state, CM state, RRC state, and Enterprise Mobility Management (EMM) security context. When establishing an RRC connection, the dual-booting device 170 selects the 5G-S-TMSI (derived from the 5G-GUTI) that has been assigned for the corresponding registration.

[0050] Two dual-booting devices 170 registered with AMF 320 are treated as two different UEs (with different 5G S-TMSI and NGAP-UE IDs) by NG-RAN node 310. In some cases, when establishing a UE context for dual-booting device 170 in NG-RAN node 310, AMF 320 provides linking information to NG-RAN node 310, which NG-RAN node 310 uses to determine if a UE context is associated with the same device (e.g., dual-booting device 170). AMF 320 provides the linking information by sending an NGAP Initial Context Establishment Request message, which includes a public identifier (not required to be SUPI for security reasons) or any other identifier that allows NG-RAN node 310 to associate multiple UE contexts received from AMF 320 with dual-booting device 170. Figure 3 In the example shown, this can be achieved by AMF 320 including the UE NGAP ID 1, which is included in the first NGAP initial UE context establishment request sent during the first N2 connection establishment, again in the NGAP initial UE context establishment request message sent to NG-RAN node 310 during the second N2 connection establishment.

[0051] In some cases, enabling NG-RAN node 310 to be aware that different UE contexts correspond to dual-booting device 170 (e.g., belonging to the same device) allows NG-RAN node 310 to allocate radio resources to dual-booting device 170 in a manner that avoids interference between radio signals exchanged between dual-booting device 170 and NG-RAN node 310 related to two registrations made by dual-booting device 170 to the AMF. When paging dual-booting device 170, AMF 320 selects and includes the 5G-S-TMSI of dual-booting device 170 corresponding to the registration for which UE 170 needs to initiate a service request.

[0052] refer to Figure 4An example of context information associated with the device identifier of the dual-boot device 170 is shown. In some example embodiments, the context information is stored in the memory of the dual-boot device as one or more context tables 400 corresponding to each SUPI, PLMN ID, or independent NPN ID; these context tables 400 may also correspond to a registration identifier (registration ID) in the PLMN ID, and each context table stores the corresponding 5G-GUTI. Specifically, given a context table 402 (e.g., based on a given SUPI, PLMN ID, or independent NPN ID, and the registration ID in the PLMN ID) in Figure 4 As shown, and including the following data components:

[0053] When the dual-boot device 170 operates in RRC idle mode, it determines which of the two registrations it made with the AMF320 requires an RRC connection reconfiguration. Therefore, the dual-boot device 170 selects one of the first and second network identifiers mapped to a given registration (e.g., 5G-GUTI (e.g., 5G-GUTI-1 for registration 1)), establishes the RRC connection using the derived corresponding 5G-S-TMSI, and performs the registration update using the 5G-GUTI. The UE170 may store the security context generated from successful authentication based on each SUPI.

[0054] In some cases, Figure 3 The process described herein facilitates the reuse of the combination of 5G-S-TMSI and UE NGAP ID for NG-RAN node 310 to identify the individual registration of dual-boot devices in any RRC state at any time.

[0055] Figure 5 Another example initial registration process for initially registering a dual-booting device 170 to a communication network 100 is illustrated. The dual-booting device 170 includes two UEs (shown as UE-1 and UE-2), and the first UE (UE-1) has a first identifier (generally referred to herein as the first UE identifier) ​​identifying the first UE (UE-1), and the second UE (UE-2) has a second identifier (generally referred to herein as the first UE identifier) ​​identifying the second UE (UE-2). The UDM stores subscription information for the first UE (UE-1) and the second UE (UE-2). The first UE identifier may be a first subscription permanent identifier (SUPI) representing the permanent identity of the first UE in the communication network 100. The second UE identifier may be a second subscription permanent identifier (SUPI) representing the permanent identity of the second UE in the communication network 100.

[0056] The process begins at point 1. At point 1, the first UE (UE-1) of the dual-booting device 170 generates a first hidden identifier (e.g., SUCI-1 generated from SUPI-1) from the first UE identifier and sends a NAS registration request to the AMF 420 of the communication network (e.g., communication network 100) via a first 3GPP access path, which includes an RRC connection between the first UE (UE-1) of the dual-booting device 170 and the NG-RAN node 410, and a first signaling connection (e.g., an NG connection) between the NG-RAN node 410 and the AMF 420. The NAS registration request includes the first hidden identifier (e.g., SUCI-1) of the first UE identifier. At point 2, upon receiving the first NAS registration request from the first UE (UE-1), the AMF 420 generates a first UE identifier from the first hidden identifier and retrieves subscription information associated with the first UE identifier (e.g., SUCI-1) from the UDM 430. The AMF420 uses the Nudum_Get service operation and a first UE identifier (e.g., SUPI-1) to retrieve subscription information associated with the first UE identifier (e.g., SUPI-1). The subscription information associated with the first UE identifier (e.g., SUPI-1) includes the first UE identifier (e.g., SUPI-1) and a linked subscription identifier. Figure 5 In the example shown, the link subscription identifier is set to the second UE identifier (e.g., SUPI-2), which instructs the AMF 420 that the subscription information associated with the first UE identifier is linked to the subscription information associated with the second UE identifier.

[0057] At three locations, AMF 420 assigns a first NGAP identifier, which uniquely identifies the first UE (UE-1) of the dual-boot device 170 on the NG interface between NG-RAN node 410 and AMF420 (e.g., ...). Figure 5As shown in NGAP-UE-ID-1, the NG-RAN node 410 sends an initial context establishment message to the NG-RAN node 410 to establish a first UE context for the first UE (UE-1) at the NG-RAN node 410. At point 4, after establishing the first UE context for the first UE (UE-1) and associating the first UE context with the first NGAP identifier (NGAP-UE-ID-1), the NG-RAN node 410 sends an initial context establishment response message to the AMF 420 to indicate that the first UE context for the first UE (UE-1) has been established at the NG-RAN node 410. At point 5, the AMF 420 registers the first UE (UE-1) with the AMF 420 (e.g., stores the registration of the first UE-1), assigns a first GUTI (shown as GUTI-1) to the registration of the first UE (UE-1), and sends a NAS registration acceptance message including the first GUTI (e.g., GUTI-1) to the first UE (UE-1).

[0058] At point 6, the second UE (UE-2) of the dual-booting device 170 generates a second hidden identifier (e.g., SUCI-2 generated from SUPI-2) based on the second UE identifier, and sends a NAS registration request via a second 3GPP access path. This second 3GPP access path includes an RRC connection between the second UE (UE-2) of the dual-booting device 170 and the NG-RAN node 410, and a second signaling connection (e.g., a second NG connection) between the NG-RAN node 410 and the AMF 420. The NAS registration request includes the second hidden identifier. At point 7, upon receiving the NAS registration request from the second UE (UE-2), the AMF 420 generates a second UE identifier (e.g., SUPI-2) from the second hidden identifier (e.g., SUCI-2), and retrieves subscription information associated with the second UE identifier (e.g., SUCI-2) from the UDM 430. The AMF 420 uses the Nudum_Get service operation and the second UE identifier (e.g., SUPI-2) to retrieve the subscription information associated with the second UE identifier (e.g., SUPI-2). The subscription information associated with the second UE identifier (e.g., SUCI-2) includes the second UE identifier (e.g., SUPI-2) and the linked subscription identifier. Figure 5 In the example shown, the link subscription identifier is set to the second UE identifier (e.g., SUPI-2), which instructs the AMF 420 that the subscription information associated with the first UE identifier is linked to the subscription information associated with the second UE identifier.

[0059] At point 8, AMF 420 assigns a second NGAP identifier, which uniquely identifies the second UE (UE-2) of dual-boot device 170 on the NG interface between NG-RAN node 410 and AMF420 (e.g., Figure 7 As shown in NGAP-UE-ID-2, a second initial context establishment message is sent to NG-RAN node 410 to establish a second UE context for the second UE (UE-2) associated with the second NGAP identifier (NGAP-UE-ID-2). At point 9, NG-RAN node 410 sends a second initial context establishment response message to AMF 420 to indicate that the second UE context for the second UE (UE-2) has been established at NG-RAN node 410 and linked to the first UE context for the first UE (UE-1) used for dual boot device 170.

[0060] At point 10, AMF 420 registers a second UE (UE-2) with AMF 420 (e.g., stores the registration of the second UE (UE-2), assigns a second GUTI (shown as GUTI-1) to the registration of the second UE (UE-2), and sends a NAS registration acceptance message to the second UE (UE-2) including a link identifier and the second GUTI (e.g., GUTI-2). The link identifier indicates to the second UE (UE-2) that the registration of the first UE-1 and the registration of the second UE-2 are linked to each other. In some example embodiments, the link identifier may be GUTI-1 assigned by AMF 430 for registering the first UE-1 with AMF 420.

[0061] At position 11, AMF 420 directs to SMF (e.g., Figure 5 The SMF (Simplified Chinese version of SMF / PCF 440) sends requests to establish and / or modify PDU sessions, and / or to the PCF (e.g., Figure 5 The PCF (PCF) of the SMF / PCF 440 shown sends a request to establish and / or modify the policy association for the dual-boot device 170. In response to the request to establish and / or modify the policy association for the dual-boot device 170, the PCF (e.g., Figure 5 The PCF of the SMF / PCF 440 shown provides a coordinated URSP policy for the first UE (UE-1) and the second UE (UE-2) of the dual boot device 170.

[0062] although Figure 5A dual boot device 170 including two UEs is shown; however, it should be understood that in other embodiments, the dual boot device 170 may include two USIMs instead of two UEs. In an embodiment, the dual boot device 170 includes two USIMs, a first USIM associated with a first UE identifier, and a second USIM associated with a second UE identifier (e.g., SUPI-2). Figure 5 The process shown operates in the same manner as described above, except that the first and second NAS registration requests are sent by the dual boot device 170 instead of the first and second UEs (e.g., UE-1, UE-2), and the first and second NAS registration acceptance messages are received by the dual boot device 170 instead of the first and second UEs.

[0063] Figure 6 Another example initial registration process for initially registering a dual-booting device 170 to a communication network 100 is illustrated. The dual-booting device 170 includes two UEs (shown as UE-1 and UE-2), and the first UE (UE-1) has a first identifier identifying the first UE (UE-1) (generally referred to herein as the first UE identifier), while the second UE (UE-2) has a second identifier identifying the second UE (UE-2) (generally referred to herein as the first UE identifier). The UDM stores subscription information for the first UE (UE-1) and subscription information for the second UE (UE-2). The first UE identifier may be a first subscription permanent identifier (SUPI) representing the permanent identity of the first UE in the communication network 100. The second UE identifier may be a second subscription permanent identifier (SUPI) representing the permanent identity of the second UE in the communication network 100.

[0064] The process begins at point 1. At point 1, the first UE (UE-1) of the dual-booting device 170 generates a first hidden identifier (e.g., SUCI-1 generated from SUPI-1) from the first UE identifier and sends a NAS registration request to the AMF 520 of the communication network (e.g., communication network 100) via a first 3GPP access path, which includes an RRC connection between the first UE (UE-1) of the dual-booting device 170 and the NG-RAN node 510, and a first signaling connection (e.g., an NG connection) between the NG-RAN node 510 and the AMF 520. The NAS registration request includes the first hidden identifier (e.g., SUCI-1) of the first UE identifier. At point 2, upon receiving the first NAS registration request from the first UE (UE-1), the AMF 520 generates a first UE identifier from the first hidden identifier and retrieves subscription information associated with the first UE identifier (e.g., SUCI-1) from the UDM 530. The AMF520 uses the Nudum_Get service operation and a first UE identifier (e.g., SUPI-1) to retrieve subscription information associated with the first UE identifier (e.g., SUPI-1).

[0065] At three locations, AMF 520 assigns a first NGAP identifier, which uniquely identifies the first UE (UE-1) of dual-boot device 170 on the NG interface between NG-RAN node 510 and AMF520 (e.g., ...). Figure 6 As shown in NGAP-UE-ID-1, the NG-RAN node 510 sends an initial context establishment message to the NG-RAN node 510 to establish a first UE context for the first UE (UE-1). At point 4, after establishing the first UE context for the first UE (UE-1) and associating the first UE context with the first NGAP identifier (NGAP-UE-ID-1), the NG-RAN node 510 sends an initial context establishment response message to the AMF 520 to indicate that the first UE context for the first UE (UE-1) has been established at the NG-RAN node 510. At point 5, the AMF 520 registers the first UE (UE-1) with the AMF 520 (e.g., stores the registration of the first UE-1), assigns a first GUTI (shown as GUTI-1) to the registration of the first UE (UE-1), and sends a NAS registration acceptance message including the first GUTI (e.g., GUTI-1) to the first UE (UE-1).

[0066] At point 6, the second UE (UE-2) of the dual-booting device 170 generates a second hidden identifier (e.g., SUCI-2 generated from SUPI-2) based on the second UE identifier, and sends a NAS registration request via a second 3GPP access path. This second 3GPP access path includes an RRC connection between the second UE (UE-2) of the dual-booting device 170 and the NG-RAN node 510, and a second signaling connection (e.g., a second NG connection) between the NG-RAN node 410 and the AMF 520. The NAS registration request includes the second hidden identifier and a first GUTI (e.g., GUTI-1). At point 7, when the AMF 420 receives the NAS registration request from the second UE (UE-2), it generates a second UE identifier (e.g., SUPI-2) based on the second hidden identifier (e.g., SUCI-2), and determines, based on the presence of the first GUTI (e.g., GUTI-1), that the registration of the second UE-2 at the AMF 520 will be linked to the registration of the first UE-1 at the AMF 520. The AMF 520 also retrieves subscription information associated with a second UE identifier (e.g., SUCI-2) from the UDM 430. The AMF 520 uses the Nudum_Get service operation and the second UE identifier (e.g., SUPI-2) to retrieve the subscription information associated with the second UE identifier (e.g., SUPI-2).

[0067] At point 8, AMF 520 assigns a second NGAP identifier, which uniquely identifies the second UE (UE-2) of dual-boot device 170 on the NG interface between NG-RAN node 510 and AMF520 (e.g., Figure 7 As shown in NGAP-UE-ID-2, a second initial context establishment message is sent to NG-RAN node 410 to establish a second UE context for the second UE (UE-2) associated with the second NGAP identifier (NGAP-UE-ID-2). At 9, NG-RAN node 510 sends a second initial context establishment response message to AMF 520 to indicate that a second UE context for the second UE (UE-2) has been established at NG-RAN node 510.

[0068] At point 10, AMF 520 registers the second UE (UE-2) with AMF 520 (e.g., stores the registration of the second UE (UE-2), assigns a second GUTI (shown as GUTI-1) to the registration of the second UE (UE-2), and sends a NAS registration acceptance message including the second GUTI (e.g., GUTI-2) to the second UE (UE-2). At point 11, AMF 520 sends a NAS registration acceptance message to SMF (e.g., stores the registration of the second UE (UE-2)). Figure 6The SMF (Simplified Chinese Components) of the SMF / PCF540 shown sends requests to establish and / or modify PDU sessions, and / or sends requests to the PCF (e.g., ...). Figure 6 The PCF (PCF) of the SMF / PCF 540 shown sends a request to establish and / or modify the policy association for the dual-boot device 170. In response to the request to establish and / or modify the policy association for the dual-boot device 170, the PCF (e.g., Figure 6 The PCF of the SMF / PCF 540 shown provides a coordinated URSP policy for the first UE (UE-1) and the second UE (UE-2) of the dual boot device 170.

[0069] although Figure 6 A dual boot device 170 including two UEs is shown; however, it should be understood that in other embodiments, the dual boot device 170 may include two USIMs instead of two UEs. In an embodiment, the dual boot device 170 includes two USIMs, a first USIM associated with a first UE identifier, and a second USIM associated with a second UE identifier (e.g., SUPI-2). Figure 6 The process shown operates in the same manner as described above, except that the first and second NAS registration requests are sent by the dual boot device 170 instead of the first and second UEs (e.g., UE-1, UE-2), and the first and second NAS registration acceptance messages are received by the dual boot device 170 instead of the first and second UEs.

[0070] Figure 7 Another example process is shown for registering a dual-boot device to a communication network and establishing a PDU session for the dual-boot device.

[0071] Figure 7 The process shown involves dual boot device 170, AMF 620, AMF policy control function PCF (shown as AMPCF 630), UE PCF (shown as UE PCF 635), SMF PCF (shown as SM PCF 650) and SMF 640.

[0072] like Figure 7 As shown, the dual-booting device 170 includes two UEs, a first UE 170-1 and a second UE 170-2. As described above, the first UE has a first UE identifier (e.g., SUPI-1_), and the second UE 170-2 has a second UE identifier (e.g., SUPI-2). It should be understood that when the dual-booting device 170 includes a single UE with two USIMs, and the first USIM of the two USIMs is associated with the first UE identifier (e.g., SUPI-1) and the second USIM of the two USIMs is associated with the second UE identifier (e.g., SUPI-2), Figure 7 The process shown will work in the same way.

[0073] The process begins at 10. At 10, the first UE 170-1 of the dual-booting device 170 registers with the AMF 620 by sending a first registration request to the AMF 620. The first registration request may include a first NAS registration request. The first registration request includes a hidden identifier (e.g., SUCI-1) of the first UE identifier generated by the dual-booting device 170 based on the first UE identifier (e.g., SUPI-1), or includes a first GUTI (Globally Unique Temporary Identifier) ​​assigned to the first UE 170-1 during the first UE 170-1's previous registration with the AMF 620.

[0074] In step 12, as part of processing a registration request sent by the first UE 170-1 of the dual-booting device 170, the AMF 620 can establish a UE policy association with the UE PCF 635 by sending an Npcf_UEPolicyControl creation request message to the UE PCF 635. The Npcf_UEPolicyControl creation request message includes the first UE identifier (e.g., SUPI-1). Also in step 12, as part of the registration process, the AMF 620 can establish an AM policy association with the AM PCF 630 by sending an Npcf_AMPolicyControl creation request message to the AM PCF 630. The Npcf_AMPolicyControl creation request message includes the first UE identifier (e.g., SUPI-1) of the first UE 170-1 of the dual-booting device.

[0075] In step 14, AMF 620 accepts the first registration of the first UE 170-1 from dual-boot device 170 and sends a first registration acceptance message to the first UE 170-1. The first registration acceptance message may include a NAS registration acceptance message, which includes the first GUTI (Globally Unique Temporary Identifier) ​​assigned by AMF 620 to the first UE 170-1 for registration with AMF 620. Figure 7 In the diagram, the first GUTI is shown as GUTI-1.

[0076] In step 20, the second UE 170-2 of the dual-boot device 170 registers with the network (e.g., AMF 620) by sending a second registration request to AMF 620. The second registration request may include a second NAS registration request. The second registration request may include a second hidden identifier (e.g., a second SUCI (Subscription Hidden Identifier)) generated by the second UE 170-2 based on the second UE identifier (e.g., SUPI-2) or a GUTI (Globally Unique Temporary Identifier) ​​previously registered by the second UE 170-2 with AMF 620 assigned by AMF 520, and may also include a link identifier (i.e., the GUTI received for the first UE 170-1 at step 14). After the second UE 170-2 establishes a radio connection (e.g., an RRC connection) with the NG-RAN node (not shown), the second UE 170-2 provides the NG-RAN node with the GUAMI received in step 14 for the GUTI of the first UE 170-1 to ensure that the NG-RAN node selects the same AMF (e.g., AMF 620) used in the first registration (steps 10 to 14).

[0077] In step 22, as part of the registration process, AMF 620 can establish a UE policy association with UE PCF 635 by sending an Npcf_UEPolicyControl creation request message to UE PCF 635. The Npcf_UEPolicyControl creation request message includes the SUPI of the second UE 170-2 (e.g., SUPI-2) and the SUPI of the first UE 170-1 (e.g., SUPI-1) as linked SUPIs. Also in step 22, as part of the registration process, AMF 620 can establish an AM policy association with AM PCF 630 by sending an Npcf_AMPolicyControl creation request message to AM PCF 630. The Npcf_AMPolicyControl creation request message includes the SUPI of the second UE 170-2 (e.g., SUPI-2) and the SUPI of the first UE 170-1 (e.g., SUPI-1) as linked SUPIs.

[0078] The UE PCF 635 or AM PCF 630 that receives the linking information that links two policy control sessions together can determine to provide consistent UE policies related to the policy control sessions established in steps 12 and 22. For example, the UE PCF 635 can provide consistent UE routing policy (URSP) rules on the UE policy associations that are associated with each other (here, the policy association of the first UE 170-1 and the policy association of the second UE 170-2).

[0079] In step 25, AMF 320 accepts the registration of the second UE 170-2 from device 170 to the network and sends a NAS registration acceptance message to the second UE 170-2. The registration acceptance message may include a second network identifier (e.g., a GUTI (Globally Unique Temporary Identifier)) assigned to the second UE 170-2 for the registration, and also includes an indication that AMF 320 has accepted the link registration, which is given by, for example, by sending back the link GUTI of the first UE 170-1 received in step 20.

[0080] In step 30, the dual-booting device 170, for example, a UE 170-1 in the dual-booting device, requests the establishment of a PDU session for DNN and S-NSSAI. This request may include a NAS PDU session establishment request. The PDU session establishment request message may include DNN and S-NSSAI, as well as other parameters for the PDU session. At step 31, the AMF 620 propagates the PDU session establishment request to its selected SMF 640 via an Nsmf_PDUSession_UpdateSMContext request, which includes the SUPI of the first UE 170-1, but may also carry link information in the form of a link SUPI for the second UE 170-2.

[0081] At step 32, as part of the PDU session establishment request process, SMF 640 can establish an SM policy association with SMPCF 650 by sending an Npcf_SMPolicyControl creation request message to SMPCF 650. The Npcf_SMPolicyControl creation request includes the SUPI (e.g., SUPI-1) of the first UE 170-1 involved, and may also include link information in the form of a link SUPI of the second UE 170-2.

[0082] In step 35, SMF 640 accepts PDU session establishment by sending a Namf_Communication_N1N2MessageTransfer message, which includes a NAS PDU session establishment acceptance message. In step 36, SMF transmits the NAS PDU session establishment acceptance message to the first UE 170-1.

[0083] In step 40, the dual boot device 170 (e.g., the second UE 170-2 in the dual boot device 170) requests the establishment of a PDU session for DNN and S-NSSAI. This request may include a NAS PDU session establishment request. The PDU session establishment request may include DNN and S-NSSAI, as well as other parameters for the PDU session. At step 41, AMF 620 propagates the PDU establishment request to SMF 640 via an Nsmf_PDUSession_UpdateSMContext request message, which includes the SUPI of the second UE 170-2 (e.g., SUPI-2) and may also include link information in the form of a SUPI (e.g., SUPI-1 of the first UE 170-1).

[0084] At step 42, as part of the PDU session establishment request process, SMF 640 can establish an SM policy association with SM PCF 650 by sending an Npcf_SMPolicyControl creation request message. The Npcf_SMPolicyControl creation request message includes the SUPI (e.g., SUPI-2) of the second UE 170-2 involved, and may also include link information in the form of a link SUPI of the first UE 170-1.

[0085] In step 45, SMF 640 accepts PDU session establishment by sending a Namf_Communication_N1N2MessageTransfer message, which includes NAS PDU session establishment acceptance. In step 46, AMF 620 transmits the NAS PDU session establishment acceptance to the second UE 170-2.

[0086] In step 48, the SM PCF 650, having received the linking information that links the two SM policy control sessions established in steps 32 and 42 together, can determine to provide a consistent QoS policy related to the two SM policy control sessions.

[0087] Now for reference Figure 8A flowchart illustrating an example method 800 executed by an AMF (Advanced Feature Function) of a communication network (e.g., communication network 100) is shown. In some embodiments, one or more memories of the apparatus may store instructions for the AMF, and execution of the instructions for the AMF by one or more processors of the apparatus causes the apparatus to perform or conduct method 800. In some embodiments, a non-transitory computer-readable medium may store instructions for the AMF, and execution of the instructions for the AMF by one or more processors of the apparatus causes the apparatus to perform or conduct method 800.

[0088] Method 800 begins at 802. At 802, the AMF receives a first registration request from the dual-booting device via a first 3GPP access path for registering the dual-booting device with the AMF. The first registration request includes a first identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device. In some embodiments, the first identifier may be a first hidden identifier generated based on the first UEI. The first hidden identifier may be a SUPI (e.g., SUPI-1 described herein). In some embodiments, the first identifier is a GUTI provided to the dual-booting device 170 in a previous registration with the AMF. At 804, the AMF obtains first subscription information associated with the first UEI from the Unified Data Management Entity. The first subscription information includes a first linked subscription identifier. At 806, the AMF sends a first registration acceptance message to the dual-booting device. The first registration acceptance message includes a first Globally Unique Temporary Identifier (GUTI) assigned to the first registration of the dual-booting device. In some embodiments, the AMF sends the first registration acceptance message via the first 3GPP access path. At 808, the AMF receives a second registration request from the dual-booting device via a second 3GPP access path for registering the dual-booting device with the AMF. The second registration request includes a second identifier associated with the second User Equipment Identifier (UEI) of the dual-booting device. In some embodiments, the second identifier may be a second hidden identifier generated based on the UEI. The second hidden identifier may be a SUPI (e.g., SUPI-2 as described herein). At 810, the AMF obtains second subscription information associated with the UEI from the Unified Data Management Entity. The second subscription information includes a second linked subscription identifier. At 812, the AMF determines that the first subscription information and the second subscription information are linked based on the first linked subscription identifier and the second linked subscription identifier. At 814, the AMF sends a second registration acceptance message to the dual-booting device. The second registration acceptance message includes a linked identifier and a second GUTI assigned to the second registration of the dual-booting device. The linked identifier indicates that the AMF has linked the first registration and the second registration. In some embodiments, the AMF sends the second registration acceptance message via a second 3GPP access path. In some embodiments, the AMF associates the first GUTI and the first linked subscription identifier with the first registration and / or associates the second GUTI and the second linked subscription identifier with the second registration.

[0089] Now for reference Figure 9A flowchart of another example method 900 executed by an AMF (Advanced Feature Function) of a communication network (e.g., communication network 100) is shown. In some embodiments, one or more memories of the apparatus may store instructions for the AMF, and execution of the instructions for the AMF by one or more processors of the apparatus causes the apparatus to perform or conduct method 900. In some embodiments, a non-transitory computer-readable medium may store instructions for the AMF, and execution of the instructions for the AMF by one or more processors of the apparatus causes the apparatus to perform or conduct method 900.

[0090] Method 900 begins at 902. At 902, the AMF receives a first registration request from the dual-booting device via a first 3GPP access path for registering the dual-booting device with the AMF. The first registration request includes a first identifier associated with a first User Equipment Identifier (UEI) of the dual-booting device. In some embodiments, the first identifier may be a first hidden identifier generated based on the first UEI. The first hidden identifier may be a SUPI (e.g., SUPI-1 described herein). At 904, the AMF sends a first registration acceptance message to the dual-booting device. The first registration acceptance message includes a first Globally Unique Temporary Identifier (GUTI) assigned to the dual-booting device for the first registration. In some embodiments, the AMF sends the first registration acceptance message via the first 3GPP access path. At 906, the AMF receives a second registration request from the dual-booting device via a second 3GPP access path for registering the dual-booting device with the AMF. The second registration request includes a second identifier associated with a second UEI of the dual-booting device and the first GUTI. In some embodiments, the second identifier may be a second hidden identifier generated based on the second UEI. The second hidden identifier may be a SUPI (e.g., SUPI-2 described herein). At 908, the AMF determines, based on a second registration request including a first GUTI, to link a first subscription information associated with a first user equipment identifier and a second subscription information associated with a second user equipment identifier. At 910, the AMF sends a second registration acceptance message to the dual-booting device, the second registration acceptance message including a second GUTI assigned to the second registration of the dual-booting device. In some embodiments, the AMF sends the second registration acceptance message via a first 3GPP access path. In some embodiments, the AMF sends the second registration acceptance message via a second 3GPP access path. In some embodiments, the AMF associates the first GUTI and the first linked subscription identifier with the first registration and / or associates the second GUTI and the second linked subscription identifier with the second registration.

[0091] Now for reference Figure 10The diagram illustrates a flowchart of an example method 1000 executed by a dual-boot device 170. In some embodiments, one or more memories of the dual-boot device 170 store instructions, and execution of the instructions causes the device to perform or carry out method 1000.

[0092] The method begins at 1002. At 1002, the dual-booting device sends a first registration request via a first 3GPP access path to register the dual-booting device with a communication network (e.g., the AMF of the communication network). The first registration request includes a first identifier associated with a first user equipment identifier of the dual-booting device. The first identifier may include a first hidden identifier generated based on the first user equipment identifier. The first hidden identifier may be a SUPI (e.g., SUPI-1 as described herein).

[0093] At 1004, the dual-booting device receives a first registration acceptance message via a first 3GPP access path. The first registration acceptance message includes a first GUTI for the first registration assigned to the dual-booting device by the communication network.

[0094] At point 1006, the dual-booting device sends a second registration request via a second 3GPP access path to register the dual-booting device with the communication network. The second registration request includes a second identifier associated with the second user equipment identifier of the dual-booting device and a first GUTI. The second identifier may include a second hidden identifier generated based on the second user equipment identifier. The second hidden identifier may include a SUPI (e.g., SUPI-2 as described herein).

[0095] At point 1008, the dual-booting device receives a second registration acceptance message via a second 3GPP access path. This second registration acceptance message includes a link identifier and a second GUTI of the second registration assigned to the dual-booting device by the communication network. The link identifier indicates that the communication network has linked the first and second registrations.

[0096] Various systems or processes have been described to provide embodiments of the claimed subject matter. Any such example embodiments described are not intended to limit any claim, and any claim may cover a process or system different from the described process or system. The claims are not limited to systems or processes having all the features of any of the foregoing systems or processes, nor are they limited to systems or processes having features common to multiple or all of the foregoing systems or processes. The foregoing systems or processes may not be embodiments of any proprietary right granted by the grant of this patent application.

[0097] For the sake of simplicity and clarity, reference numerals may be repeated in the accompanying drawings to indicate corresponding or similar elements. Furthermore, numerous specific details are set forth to provide a thorough understanding of the subject matter described herein. However, those skilled in the art will understand that the subject matter described herein can be practiced without these specific details. In other instances, well-known methods, processes, and components have not been described in detail so as not to obscure the subject matter described herein.

[0098] As used herein, an element or feature introduced in the singular and preceded by the word "a" or "an" should be understood to not necessarily exclude multiple elements or features. Furthermore, references to "an example" or "an embodiment" are not intended to exclude other examples or embodiments that also include the described elements or features. A reference to "example" herein means that one or more features, structures, elements, components, characteristics, and / or operating steps described in connection with that example are included in at least one embodiment and / or implementation of the subject matter of this disclosure. Therefore, the phrases "an example," "another example," and similar terms throughout this disclosure may, but do not necessarily, refer to the same example. Furthermore, the subject matter characterizing any example may, but does not necessarily include the subject matter characterizing any other example.

[0099] Unless expressly stated to the contrary, examples or embodiments of "comprising," "having," or "including" elements or features having a particular property may include additional elements or features that do not have that property. Furthermore, it should be understood that the terms "comprising," "having," and "including" mean "including but not limited to," and that the terms "comprising," "having," and "including" have equivalent meanings.

[0100] As used herein, the term “and / or” can include any and all combinations of one or more of the associated listed elements or features.

[0101] The term “coupled / coupling” as used herein can have several different meanings depending on the context in which it is used. For example, the term “coupled” can have mechanical, electrical, or communication meanings. For instance, as used herein, depending on the specific context, the term “coupled” or “coupling” can indicate that two elements or devices are directly connected to each other or connected to each other via electrical elements, electrical signals, or mechanical elements through one or more intermediate elements or devices. Furthermore, the term “operably coupled” can be used to indicate that an element or device can transmit data to and receive data from another element or device electrically, optically, or wirelessly.

[0102] The phrase “configured as” in this article refers to an actual configuration state that fundamentally links the element or feature preceding the phrase “configured as” to the physical characteristics of that element or feature.

[0103] Unless otherwise stated, the terms “first,” “second,” etc., are used merely as labels in this document and are not intended to impose any order, position, or hierarchy requirements on the items referred to by these terms. Furthermore, references to “second” items do not require or exclude the presence of lower-numbered items (e.g., “first” items) and / or higher-numbered items (e.g., “third” items).

[0104] As used herein, the terms “approximately” and “about” refer to a quantity that still performs the desired function or achieves the desired result close to that quantity. For example, the terms “approximately” and “about” can refer to a quantity within engineering tolerances that will be readily understood by those skilled in the art.

[0105] As described above, the embodiments described herein can be implemented as a combination of hardware or software. Furthermore, in some examples, one or more systems and methods described herein can be implemented or implemented as part of a distributed or cloud-based computing system having multiple computing components distributed across a computing network.

[0106] Some aspects of the embodiments described herein can be implemented via software written in a high-level procedural language such as an object-oriented programming language. Therefore, the program code can be written in any suitable programming language, such as Java, Python, or Rust. Alternatively or otherwise, some of these elements implemented via software can be written in assembly language, machine language, or firmware as needed. In any case, the language can be a compiled or interpreted language.

[0107] At least some of these software programs may be stored on a storage medium (e.g., a computer-readable medium, such as, but not limited to, a read-only memory, a disk, or an optical disk) or on a device readable by a general-purpose or special-purpose programmable device. When read by a programmable device, the software program code configures the programmable device to operate in a new, specific, and predefined manner to perform at least one of the methods described herein.

[0108] Furthermore, at least some programs associated with the systems and methods described herein can be distributed as computer program products, including computer-readable media carrying computer-usable instructions for one or more processors. Such media can be provided in various forms, including non-transitory forms, such as, but not limited to, one or more disks, optical disks, magnetic tapes, chips, and magnetic and electronic storage devices.

[0109] Although embodiments have been described above with reference to the accompanying drawings, those skilled in the art will understand that changes and modifications can be made without departing from the scope defined by the appended claims.

Claims

1. An apparatus for a communication network, the apparatus comprising: Access and Mobility Management (AMF) functions are configured to: Receives a first registration request from the dual-booting device via a first 3GPP access path for registering the dual-booting device with the AMF, the first registration request including a first identifier associated with a first user equipment identifier of the dual-booting device; Obtain first subscription information associated with the first user equipment identifier from the unified data management entity; the first subscription information includes a first link subscription identifier. Send a first registration acceptance message to the dual-booting device, the first registration acceptance message including a first globally unique temporary identifier (GUTI) for the first registration assigned to the dual-booting device. Receive a second registration request from the dual-booting device via a second 3GPP access path for registering the dual-booting device with the AMF, the second registration request including a second identifier associated with a second user equipment identifier of the dual-booting device; Obtain second subscription information associated with the second user equipment identifier from the unified data management entity; the second subscription information includes a second link subscription identifier. The first subscription information and the second subscription information are linked based on the first link subscription identifier and the second link subscription identifier; as well as A second registration acceptance message is sent to the dual-boot device. The second registration acceptance message includes a link identifier and a second GUTI assigned to the second registration of the dual-boot device, wherein the link identifier indicates that the AMF has linked the first registration and the second registration.

2. The apparatus of claim 1, wherein the first link subscription identifier includes the second user equipment identifier, and the second link subscription identifier includes the first user equipment identifier.

3. The apparatus of claim 1 or 2, wherein the link identifier includes the first GUTI.

4. The apparatus according to any one of claims 1 to 3, wherein the first user equipment identifier is a first subscription permanent identifier (SUPI), and the first identifier associated with the first user equipment identifier is a first subscription hidden identifier (SUCI) generated based on the first SUPI, and wherein the second user equipment identifier associated with the second user equipment identifier is a second SUPI, and the second identifier is a second SUCI generated based on the second SUPI.

5. The apparatus according to any one of claims 1 to 3, wherein the first user equipment identifier is a first subscription permanence identifier (SUPI) and the first identifier is the first GUTI, and wherein the second user equipment identifier is a second subscription permanence identifier (SUPI) and the first identifier is the second GUTI.

6. The apparatus according to any one of claims 1 to 5, wherein the dual-booting device comprises two user equipments, and wherein the first registration request is received from a first user equipment (UE) of the two user equipments, and the second registration request is received from a second user equipment (UE) of the two user equipments.

7. The apparatus according to any one of claims 1 to 6, wherein the dual-booting device comprises two subscriber identity modules, wherein the first user equipment identifier comprises a first subscription permanent identifier associated with the first subscriber identity module of the two subscriber identity modules, and wherein the second user equipment identifier comprises a second subscription permanent identifier associated with the second subscriber identity module of the two subscriber identity modules.

8. The apparatus according to any one of claims 1 to 7, wherein the determination includes determining, based on first link subscription information and second link subscription information, a subscription profile of the first subscription information and the second subscription information linked to the dual-boot device.

9. The apparatus according to any one of claims 1 to 8, wherein the first user equipment identifier includes a first subscription permanent identifier of the first user equipment, and the second user equipment identifier includes a second subscription permanent identifier of the second user equipment.

10. The apparatus according to any one of claims 1 to 9, wherein the first 3GPP access path includes a first RRC connection between the dual-booting device and the radio access network node and a first signaling connection between the RAN node and the AMF, and the second 3GPP access path includes a second RRC connection between the dual-booting device and the RAN node and a second signaling connection between the RAN node and the AMF.

11. The apparatus of claim 10, wherein the AMF is further configured to perform: After obtaining the first subscription information, a first request for establishing a first user equipment context for the first user equipment is sent to the RAN node; and After obtaining the second subscription information, a second request is sent to the RAN node to establish a second user equipment context for the second user equipment, wherein the second user equipment context for the second user equipment is associated with the first user equipment context of the first user equipment.

12. The apparatus of claim 11, wherein the first request includes a first initial context establishment request message, the first initial context establishment request message including a first user equipment context identifier for associating with the first user equipment context, and wherein the second request includes a second initial context establishment request message, the second initial context establishment request message including a second user equipment context identifier for associating with the second user equipment context and the link information indicating to the RAN node that the first user equipment context will be associated with the second user equipment context.

13. The apparatus of claim 12, wherein the first user equipment context identifier includes a first Next Generation Application Protocol (NGAP) user equipment identifier, and wherein the second user equipment context identifier includes a second NGAP UE ID.

14. The apparatus of claim 12 or 13, wherein the linking information includes the first user equipment context identifier.

15. An apparatus for a communication network, the apparatus comprising: Access and Mobility Management (AMF) functions are configured to: Receives a first registration request from the dual-booting device via a first 3GPP access path for registering the dual-booting device with the AMF, the first registration request including a first identifier associated with a first user equipment identifier of the dual-booting device; Obtain first subscription information associated with the first user equipment identifier from the unified data management entity; Send a first registration acceptance message to the dual-booting device, the first registration acceptance message including a first globally unique temporary identifier (GUTI) for the first registration assigned to the dual-booting device. Receive a second registration request from the dual-booting device via a second 3GPP access path for registering the dual-booting device with the AMF, the second registration request including a second identifier associated with a second user equipment identifier of the dual-booting device and the GUTI of the first registration assigned to the dual-booting device; Obtain second subscription information associated with the second user equipment identifier from the unified data management entity, and The link between the first subscription information and the second subscription information is determined based on the GUTI included in the second registration request; as well as A second registration acceptance message is sent to the dual-boot device, the second registration acceptance message including a second GUTI assigned to the second registration of the dual-boot device.

16. The apparatus of claim 15, wherein the first link subscription identifier includes the second user equipment identifier, and the second link subscription identifier includes the first user equipment identifier.

17. The apparatus of claim 15 or 16, wherein the link identifier includes the first GUTI.

18. The apparatus of any one of claims 15 to 17, wherein the first user equipment identifier is a first subscription permanent identifier (SUPI), and the first identifier associated with the first user equipment identifier is a first subscription hidden identifier (SUCI) generated based on the first SUPI, and wherein the second user equipment identifier associated with the second user equipment identifier is a second SUPI, and the second identifier is a second SUCI generated based on the second SUPI.

19. The apparatus according to any one of claims 15 to 18, wherein the first user equipment identifier is a first subscription permanence identifier (SUPI) and the first identifier is a first GUTI, and wherein the second user equipment identifier is a second subscription permanence identifier (SUPI) and the first identifier is a second GUTI.

20. The apparatus of any one of claims 15 to 19, wherein the dual-booting device comprises two user equipments, and wherein the first registration request is received from a first user equipment (UE) of the two user equipments, and the second registration request is received from a second user equipment (UE) of the two user equipments.

21. The apparatus of any one of claims 15 to 20, wherein the dual-boot device comprises two subscriber identity modules, and wherein the first user equipment identifier comprises a first subscription permanent identifier associated with the first subscriber identity module of the two subscriber identity modules, and wherein the second user equipment identifier comprises a second subscription permanent identifier associated with the second subscriber identity module of the two subscriber identity modules.

22. The apparatus according to any one of claims 15 to 21, wherein the determination comprises: The subscription profile of the dual-boot device is determined based on the first link subscription information and the second link subscription information.

23. The apparatus of any one of claims 15 to 22, wherein the first user equipment identifier includes a first subscription permanent identifier of the first user equipment, and the second user equipment identifier includes a second subscription permanent identifier of the second user equipment.

24. The apparatus of any one of claims 15 to 23, wherein the first 3GPP access path includes a first RRC connection between the dual-booting device and the radio access network node and a first signaling connection between the RAN node and the AMF, and the second 3GPP access path includes a second RRC connection between the dual-booting device and the RAN node and a second signaling connection between the RAN node and the AMF.

25. The apparatus of claim 24, wherein the AMF is further configured to perform: After obtaining the first subscription information, a first request for establishing a first user equipment context for the first user equipment is sent to the RAN node; and After obtaining the second subscription information, a second request is sent to the RAN node to establish a second user equipment context for the second user equipment, wherein the second user equipment context for the second user equipment is associated with the first user equipment context of the first user equipment.

26. The apparatus of claim 25, wherein the first request includes a first initial context establishment request message, the first initial context establishment request message including a first user equipment context identifier for associating with the first user equipment context, and wherein the second request includes a second initial context establishment request message, the second initial context establishment request message including a second user equipment context identifier for associating with the second user equipment context and the link information indicating to the RAN node that the first user equipment context will be associated with the second user equipment context.

27. The apparatus of claim 26, wherein the first user equipment context identifier includes a first Next Generation Application Protocol (NGAP) user equipment identifier, and wherein the second user equipment context identifier includes a second NGAP UE ID.

28. The apparatus of claim 26 or 27, wherein the linking information includes the first user equipment context identifier.

29. A dual-guidance device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the dual-boot device to perform at least the following operations: A first registration request for registering the dual-booting device with the communication network is sent via a first 3GPP access path. The first registration request includes a first identifier associated with a first user equipment identifier of the dual-booting device. A first registration acceptance message is received via the first 3GPP access path, the first registration acceptance message including a first globally unique temporary identifier (GUTI) for the first registration assigned to the dual-boot device by the communication network. A second registration request for registering the dual-booting device with the communication network is sent via a second 3GPP access path. The second registration request includes a second identifier associated with the second user equipment identifier of the dual-booting device and the first GUTI. as well as A second registration acceptance message is received via the second 3GPP access path. The second registration acceptance message includes a second GUTI and a link identifier for the second registration assigned to the dual-boot device by the communication network, wherein the link identifier indicates that the communication network has linked the first registration and the second registration.

30. The dual-boot device of claim 29, wherein the link identifier includes the first GUTI.

Images