Registration method and apparatus for dualsteer device, communication apparatus, and storage medium

Abstract

The present disclosure relates to a registration method and apparatus for a DualSteer device, a communication apparatus, and a storage medium. In an embodiment of the present disclosure, a first terminal of a DualSteer device sends a registration request, where the registration request comprises at least one of the following: an indication of the capability of the first terminal to support the DualSteer device, an identifier of the DualSteer device, and an association identifier between the first terminal and a second terminal in the DualSteer device, so that a network side completes the registration of the first terminal of the DualSteer device. Also, the network side feeds back policy information of the second terminal in the DualSteer device to the first terminal, and the first terminal sends the policy information of the second terminal to the second terminal, so that the second terminal completes registration under the guidance of the policy information of the second terminal. Thus, the embodiment of the present disclosure supports a DualSteer device accessing a 5G core network via two 3GPP access networks, thereby enabling the DualSteer device to simultaneously perform data transmission on two different 3GPP access networks.

Description

A registration method, device, communication device and storage medium for a dual-boot device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese patent application number 202410177900.7, filed with the China Patent Office on February 8, 2024, entitled “A registration method, device, communication device and storage medium for a dual-boot device,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0003] The present disclosure relates to the field of communication technology, and more particularly to a registration method, apparatus, communication device, and storage medium for a dual-boot device. Background Art

[0004] A DualSteer device supports traffic steering and user data exchange (for different services) across two 3GPP (3rd Generation Partnership Project) access networks. When transmitting data non-simultaneously on the two 3GPP access networks, the DualSteer device is a single user equipment (UE). When transmitting data simultaneously on the two 3GPP access networks, the DualSteer device is two UEs that share a single subscription profile but have different identities, such as different Subscription Permanent Identifiers (SUPIs).

[0005] When the dual-boot device is two UEs, the relevant technologies do not address issues such as what capabilities the two UEs need to carry when registering with the network, whether the network supports the new capabilities of the UE, and how to trigger the second UE to register with the core network. Summary of the Invention

[0006] At least one embodiment of the present disclosure provides a registration method, apparatus, communication device, and storage medium for a dual-boot device.

[0007] In a first aspect, an embodiment of the present disclosure provides a registration method for a dual-boot device, which is applied to a first terminal of the dual-boot device. The method includes:

[0008] The first terminal sends a registration request to the access mobility function (AMF) of the home public land mobile network (HPLMN). The registration request includes at least one of the following: an indication of the first terminal's capability to support dual-boot devices, an identifier of the dual-boot device, and an identifier for association between the first terminal and the second terminal in the dual-boot device.

[0009] The first terminal receives a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

[0010] In some embodiments, the registration request further includes a terminal policy container, and the registration method for a dual-boot device further includes:

[0011] The first terminal receives the policy information of the first terminal and the policy information of the second terminal of the dual-boot device sent by the AMF;

[0012] The first terminal sends the policy information of the second terminal to the second terminal.

[0013] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0014] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0015] In some embodiments, after the first terminal receives the registration success message sent by the AMF, the registration method for the dual-boot device further includes:

[0016] The first terminal sends a protocol data unit PDU session establishment request to the AMF, where the PDU session establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, the access type of the first terminal, the wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0017] In a second aspect, the present disclosure also provides a registration method for a dual-boot device, which is applied to a second terminal of the dual-boot device. The method includes:

[0018] The second terminal determines a target policy, where the target policy includes at least one of the following: an access type preference, a wireless access technology type preference, and a public land mobile network preference;

[0019] The second terminal sends a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0020] The second terminal receives a registration success message sent by the AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

[0021] In some embodiments, the second terminal determines the target strategy including:

[0022] If the second terminal receives a service initiation request, and the service initiation request includes a service type, the second terminal queries the policy information of the second terminal to obtain a target policy corresponding to the service type;

[0023] or,

[0024] If the second terminal does not receive the service initiation request, the second terminal queries the policy information to obtain the target policy corresponding to the terminal type and / or pre-configuration information of the second terminal.

[0025] In some embodiments, the second terminal receives the service initiation request, including:

[0026] The second terminal receives a service initiation request forwarded by the first terminal of the dual-boot device;

[0027] Alternatively, the second terminal detects a service initiation request.

[0028] In some embodiments, the registration request also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

[0029] In some embodiments, after the second terminal receives the registration success message sent by the AMF, the registration method for the dual-boot device further includes:

[0030] The second terminal sends a protocol data unit PDU session establishment request to the AMF, where the PDU session establishment request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an access type for the second terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0031] In a third aspect, an embodiment of the present disclosure further proposes a registration method for a dual-boot device, which is applied to access the mobile function AMF. The method includes:

[0032] The AMF receives a registration request sent by a first terminal or a second terminal of a dual-boot device, where the registration request includes at least one of the following: an indication of the first terminal or the second terminal's capability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal;

[0033] The AMF sends an authentication and subscription request to the unified data management (UDM) function. The authentication and subscription request includes at least one of the following: an indication of the first or second terminal's ability to support dual-boot devices and an identifier of the dual-boot device. The AMF receives the subscription information of the first terminal and the subscription information of the second terminal sent by the UDM function after successful authentication.

[0034] The AMF sends a registration success message to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

[0035] In some embodiments, after the AMF receives the contract information of the first terminal and the contract information of the second terminal sent after the UDM function authentication is passed, the registration method of the dual-boot device further includes:

[0036] The AMF determines whether the first terminal and the second terminal belong to the same dual-boot device;

[0037] If they belong to the same dual-boot device, execute AMF to send a registration success message to the first terminal or the second terminal;

[0038] The AMF associates and stores the registration context data of the first terminal and the second terminal.

[0039] In some embodiments, the registration request of the first terminal further includes a terminal policy container, and the registration method for the dual-boot device further includes:

[0040] The AMF sends a terminal policy establishment request to the policy control function PCF. The terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal;

[0041] The AMF receives the policy information of the first terminal and the policy information of the second terminal sent by the PCF;

[0042] The AMF sends the policy information of the first terminal and the policy information of the second terminal to the first terminal.

[0043] In some embodiments, the registration method for a dual-boot device further includes:

[0044] After the AMF receives the protocol data unit PDU session establishment request sent by the first terminal or the second terminal, it forwards the PDU session establishment request to the session management function SMF, wherein the PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, the access type of the first terminal, the wireless access technology type, and the association identifier of the first terminal and the second terminal, or includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and the association identifier of the first terminal and the second terminal.

[0045] In a fourth aspect, embodiments of the present disclosure further provide a subscription configuration method for a dual-boot device, which is applied to a unified data management function (UDM) and / or a unified data repository function (UDR) of a home public land mobile network (HPLMN). The method includes:

[0046] Receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to subscription configuration data of the first terminal or the second terminal in the dual-boot device:

[0047] Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

[0048] In some embodiments, the contract configuration method for a dual-boot device further includes:

[0049] Setting the first terminal identification or the second terminal identification of the dual-boot device in the terminal identification;

[0050] Set to true in dual boot device indication;

[0051] Setting the second terminal identification or the first terminal identification of the dual-boot device in the associated terminal identification;

[0052] When the dual boot device indication is true, the first terminal of the dual boot device is set to yes and the second terminal of the dual boot device is set to no in the master device.

[0053] In some embodiments, the contract configuration method for a dual-boot device further includes:

[0054] In the universal subscriber identity module USIM of the dual-boot device, corresponding configuration creation or update is performed according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

[0055] In a fifth aspect, the embodiments of the present disclosure further provide a registration method for a dual-boot device, which is applied to a policy control function (PCF) of a home public land mobile network (HPLMN). The method includes:

[0056] Receive a terminal policy establishment request sent by the access mobility function AMF, where the terminal policy establishment request includes at least one of the following: an indication of a capability of the first terminal of the dual-boot device to support dual-boot devices, an identifier of the first terminal, and an identifier of an association between the first terminal and the second terminal in the dual-boot device;

[0057] Send the policy information of the first terminal and the policy information of the second terminal to the AMF.

[0058] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0059] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0060] In a sixth aspect, an embodiment of the present disclosure further provides a registration apparatus for a dual-boot device, which is applied to a first terminal of the dual-boot device, and includes:

[0061] The first unit is configured to send a registration request to an access mobility function (AMF) of a home public land mobile network (HPLMN), where the registration request includes at least one of the following: a capability indication of the first terminal supporting dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0062] The second unit is used to receive a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

[0063] In a seventh aspect, an embodiment of the present disclosure further provides a registration apparatus for a dual-boot device, which is applied to a second terminal of the dual-boot device, and includes:

[0064] A first unit is configured to determine a target policy, the target policy comprising at least one of the following: an access type preference, a radio access technology type preference, and a public land mobile network preference;

[0065] The second unit is configured to send a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0066] The third unit is used to receive a registration success message sent by AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

[0067] In an eighth aspect, an embodiment of the present disclosure further provides a registration device for a dual-boot device, which is applied to access the mobile function AMF, and the device includes:

[0068] The first unit is configured to receive a registration request sent by a first terminal or a second terminal of a dual-boot device, where the registration request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal;

[0069] The second unit is configured to send an authentication and contract request to the unified data management (UDM) function, where the authentication and contract request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices and an identifier of the dual-boot device; and the AMF receives the contract information of the first terminal and the contract information of the second terminal sent by the UDM function after the authentication is passed;

[0070] The third unit is configured to send a registration success message to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

[0071] In a ninth aspect, embodiments of the present disclosure further provide a subscription configuration apparatus for a dual-boot device, which is applied to a unified data management function (UDM) and / or a unified data repository function (UDR) of a home public land mobile network (HPLMN). The apparatus includes:

[0072] The first unit is configured to receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to the subscription configuration data of the first terminal or the subscription configuration data of the second terminal in the dual-boot device:

[0073] Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

[0074] In a tenth aspect, the embodiments of the present disclosure further provide a registration apparatus for a dual-boot device, which is applied to a policy control function (PCF) of a home public land mobile network (HPLMN). The apparatus includes:

[0075] The first unit is configured to receive a terminal policy establishment request sent by an access mobility function (AMF), where the terminal policy establishment request includes at least one of the following: an indication of a capability of a first terminal of a dual-boot device to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0076] The second unit is used to send the policy information of the first terminal and the policy information of the second terminal to the AMF.

[0077] In an eleventh aspect, an embodiment of the present disclosure further provides a communication device, which includes a memory, a transceiver, and a processor;

[0078] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0079] Send a registration request to the access mobility function (AMF) of the home public land mobile network (HPLMN), where the registration request includes at least one of the following: an indication of the first terminal's capability to support dual-boot devices, an identifier of the dual-boot device, and an identifier associated with the first terminal and the second terminal in the dual-boot device;

[0080] Receive a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

[0081] In some embodiments, the registration request also includes a terminal policy container, and the processor is further configured to:

[0082] Receive the policy information of the first terminal and the policy information of the second terminal of the dual-boot device sent by the AMF;

[0083] The policy information of the second terminal is sent to the second terminal.

[0084] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0085] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0086] In some embodiments, after the first terminal receives the registration success message sent by the AMF, the processor is further configured to:

[0087] A protocol data unit (PDU) session establishment request is sent to the AMF. The PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, an access type of the first terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0088] In a twelfth aspect, an embodiment of the present disclosure further provides a communication device, which includes a memory, a transceiver, and a processor;

[0089] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0090] determining a target strategy, the target strategy comprising at least one of: an access type preference, a wireless access technology type preference, and a public land mobile network preference;

[0091] Sending a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0092] Receive a registration success message from the AMF, which includes an indication of whether the network supports dual-boot devices.

[0093] In some embodiments, determining the target strategy includes:

[0094] If a service initiation request is received, and the service initiation request includes a service type, querying the policy information of the second terminal to obtain a target policy corresponding to the service type;

[0095] or,

[0096] If no service initiation request is received, the policy information is queried to obtain the target policy corresponding to the terminal type and / or pre-configured information of the second terminal.

[0097] In some embodiments, receiving a service initiation request includes:

[0098] Receiving a service initiation request forwarded by a first terminal of the dual-boot device;

[0099] Alternatively, a service initiation request is detected.

[0100] In some embodiments, the registration request also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

[0101] In some embodiments, after receiving the registration success message sent by the AMF, the processor is further configured to:

[0102] A protocol data unit (PDU) session establishment request is sent to the AMF. The PDU session establishment request includes at least one of the following: an indication of the ability of the second terminal to support dual-boot devices, an access type of the second terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0103] In a thirteenth aspect, an embodiment of the present disclosure further provides a communication device, which includes a memory, a transceiver, and a processor;

[0104] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0105] Receiving a registration request sent by a first terminal or a second terminal of a dual-boot device, the registration request including at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal;

[0106] Sending an authentication and contract signing request to the unified data management (UDM) function, the authentication and contract signing request including at least one of the following: an indication of the first terminal or the second terminal's ability to support dual-boot devices and an identifier of the dual-boot device; and receiving contract signing information of the first terminal and contract signing information of the second terminal sent by the UDM function after successful authentication;

[0107] A registration success message is sent to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

[0108] In some embodiments, after receiving the contract information of the first terminal and the contract information of the second terminal sent after the UDM function authentication is passed, the processor is further configured to:

[0109] determining whether the first terminal and the second terminal belong to the same dual-boot device;

[0110] If they belong to the same dual-boot device, sending a registration success message to the first terminal or the second terminal;

[0111] The registration context data of the first terminal and the second terminal are associated and stored.

[0112] In some embodiments, the registration request of the first terminal also includes a terminal policy container, and the processor is further configured to:

[0113] Sending a terminal policy establishment request to the policy control function PCF, where the terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an identifier associated with the first terminal and the second terminal;

[0114] Receiving policy information of the first terminal and policy information of the second terminal sent by the PCF;

[0115] The policy information of the first terminal and the policy information of the second terminal are sent to the first terminal.

[0116] In some embodiments, the processor is further configured to:

[0117] After receiving the protocol data unit PDU session establishment request sent by the first terminal or the second terminal, the PDU session establishment request is forwarded to the session management function SMF, wherein the PDU session establishment request includes at least one of the following: the capability indication of the first terminal to support dual-boot devices, the access type of the first terminal access, the wireless access technology type, and the association identifier of the first terminal and the second terminal, or includes at least one of the following: the capability indication of the second terminal to support dual-boot devices, the access type of the second terminal access, the wireless access technology type, and the association identifier of the first terminal and the second terminal.

[0118] In a fourteenth aspect, an embodiment of the present disclosure further provides a communication device, which includes a memory, a transceiver, and a processor;

[0119] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0120] Receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to subscription configuration data of the first terminal or the second terminal in the dual-boot device:

[0121] Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

[0122] In some embodiments, the processor is further configured to:

[0123] Setting the first terminal identification or the second terminal identification of the dual-boot device in the terminal identification;

[0124] Set to true in dual boot device indication;

[0125] Setting the second terminal identification or the first terminal identification of the dual-boot device in the associated terminal identification;

[0126] When the dual boot device indication is true, the first terminal of the dual boot device is set to yes and the second terminal of the dual boot device is set to no in the master device.

[0127] In some embodiments, the processor is further configured to:

[0128] In the universal subscriber identity module USIM of the dual-boot device, corresponding configuration creation or update is performed according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

[0129] In a fifteenth aspect, an embodiment of the present disclosure further provides a communication device, which includes a memory, a transceiver, and a processor;

[0130] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer programs in the memory and executing:

[0131] Receive a terminal policy establishment request sent by the access mobility function AMF, where the terminal policy establishment request includes at least one of the following: an indication of a capability of the first terminal of the dual-boot device to support dual-boot devices, an identifier of the first terminal, and an identifier of an association between the first terminal and the second terminal in the dual-boot device;

[0132] Send the policy information of the first terminal and the policy information of the second terminal to the AMF.

[0133] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0134] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0135] In the sixteenth aspect, the embodiments of the present disclosure further propose a processor-readable storage medium, wherein the processor-readable storage medium stores a program, and the program is used to enable the processor to execute the registration method for a dual-boot device of any embodiment of the first aspect, or execute the registration method for a dual-boot device of any embodiment of the second aspect, or execute the registration method for a dual-boot device of any embodiment of the third aspect, or execute the contract configuration method for a dual-boot device of any embodiment of the fourth aspect, or execute the registration method for a dual-boot device of any embodiment of the fifth aspect.

[0136] In at least one embodiment of the present disclosure, a registration request is sent by the first terminal of a dual-boot device, and the registration request carries an indication of the first terminal's ability to support dual-boot devices and / or an identifier of the dual-boot device and / or an associated identifier of the first terminal and the second terminal in the dual-boot device, so that the network side completes the registration of the first terminal of the dual-boot device. In addition, the network side feeds back the policy information of the second terminal in the dual-boot device to the first terminal, and the first terminal sends the policy information of the second terminal to the second terminal, so that the second terminal completes the registration under the guidance of the policy information of the second terminal. Therefore, the embodiment of the present disclosure supports a dual-boot device to access the 5G core network through two 3GPP access networks, and further supports a dual-boot device to simultaneously transmit data on two different 3GPP access networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0137] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0138] FIG1 is a schematic diagram of a process for registering a dual-boot device according to an embodiment of the present disclosure;

[0139] FIG2 is a flow chart of a registration method for a dual-boot device provided by an embodiment of the present disclosure;

[0140] FIG3 is a flow chart of a registration method for a dual-boot device provided by an embodiment of the present disclosure;

[0141] FIG4 is a flow chart of a signing configuration method for a dual-boot device provided by an embodiment of the present disclosure;

[0142] FIG5 is a flow chart of a registration method for a dual-boot device provided by an embodiment of the present disclosure;

[0143] FIG6 is a schematic diagram of a process for a first terminal (UE1) of a dual-boot device to register in a home public land mobile network HPLMN (e.g., 5G New Radio NR) according to an embodiment of the present disclosure;

[0144] FIG7 is a schematic diagram of a process of registering a second terminal (UE2) of a dual-boot device in PLMN1 (eg, a low-orbit satellite / LEO) according to an embodiment of the present disclosure;

[0145] FIG8 is a schematic diagram of a process for registering a second terminal (UE2) of a dual-boot device in PLMN1 (eg, Satellite / GEO) according to an embodiment of the present disclosure;

[0146] FIG9 is a schematic diagram of a process for registering a second terminal (UE2) of a dual-boot device in PLMN2 (e.g., 5G New Radio NR) according to an embodiment of the present disclosure;

[0147] FIG10 is a schematic diagram of a communication device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0148] In order to more clearly understand the above-mentioned purposes, features and advantages of the present disclosure, the present disclosure is further described in detail below with reference to the accompanying drawings and examples. It will be understood that the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. The specific embodiments described herein are merely used to explain the present disclosure, rather than to limit the present disclosure. Based on the described embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art are within the scope of protection of the present disclosure.

[0149] It should be noted that, in this document, relational terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.

[0150] Currently, the 5G system supports the same terminal accessing the 5G core network through both a 3GPP access network and a non-3GPP access network. It also establishes a Multi-Access (MA) Protocol Data Unit (PDU) session and two N3 links for simultaneous user plane data transmission. The two N3 links include one N3 link established between the terminal and the User Plane Function (UPF) via the 3GPP access network, and another N3 link established between the terminal and the UPF via the non-3GPP access network. Both the terminal and the UPF must support MultiPath TCP (MPTCP), MultiPath QUIC (MPQUIC), or Access Traffic Steering, Switching, Splitting-LowLayer (ATSSS-LL) to implement multipath transmission of user plane data flows.

[0151] However, the current 5G system does not support a single terminal accessing the 5G core network through two 3GPP access networks simultaneously, nor does it support a single terminal transmitting data simultaneously on two different 3GPP access networks. Therefore, 3GPP has designed dual-boot devices. When data transmission is required on two 3GPP access networks simultaneously, the dual-boot device becomes two UEs that access two 3GPP access networks and transmit data simultaneously on both 3GPP access networks.

[0152] Dual-boot devices can be smartphones, IoT terminals, drones, etc. Data contracting and policy control of dual-boot devices are all controlled by the home network. The two 3GPP access networks accessed by dual-boot devices can belong to the same Public Land Mobile Network (PLMN), or different PLMNs, or a PLMN and a PLMN of a Public Network Integrated (PNI), etc. The access type can be two 5G NR accesses, or one terrestrial access and one satellite access, or one 5G NR access and one 4G LTE access, or two accesses of different satellite types (low orbit LEO, medium orbit MEO, high orbit GEO), etc.

[0153] Dual-boot devices feature traffic steering, which selects an access network and directs traffic through it. Traffic steering is applicable to traffic steering scenarios where one or more services are connected across two 3GPP access networks. This includes scenarios where all services use the same access network connection (no data is transmitted simultaneously on the two 3GPP access networks) or scenarios where different services are transmitted across different access networks (data is transmitted simultaneously on the two 3GPP access networks).

[0154] Dual-boot devices feature traffic switching, which transfers all services from one access network to another to minimize service interruption. Traffic switching is applicable to switching one or more services across two 3GPP access networks, including scenarios where all services use the same access network connection (no data is transmitted simultaneously on the two 3GPP access networks) or scenarios where different services are switched to different access networks (data is transmitted simultaneously on the two 3GPP access networks).

[0155] When the dual-boot device is two UEs, the relevant technologies do not address issues such as what capabilities the two UEs need to carry when registering with the network, whether the network supports the new capabilities of the UE, and how to trigger the second UE to register with the core network.

[0156] At least one embodiment of the present disclosure provides a registration method, device, communication device or storage medium for a dual-boot device, wherein a registration request is sent through the first terminal of the dual-boot device, and the registration request carries an indication of the first terminal's ability to support dual-boot devices and / or an identifier of the dual-boot device and / or an associated identifier of the first terminal and the second terminal in the dual-boot device, so that the network side completes the registration of the first terminal of the dual-boot device. In addition, the network side feeds back the policy information of the second terminal in the dual-boot device to the first terminal, and the first terminal sends the policy information of the second terminal to the second terminal, so that the second terminal completes the registration under the guidance of the policy information of the second terminal. Therefore, the embodiment of the present disclosure supports a dual-boot device to access the 5G core network through two 3GPP access networks, and further supports a dual-boot device to simultaneously transmit data on two different 3GPP access networks.

[0157] For the second terminal UE2 of a dual-boot device, static settings can be directly set in the subscription through the unified data management (UDM) to trigger the second terminal's registration and select the access type. Alternatively, the policy control function (PCF) can send corresponding UE2 policy information for routing guidance (as shown in the relevant embodiments of Figures 1 to 9).

[0158] The PCF is set in the contract as follows:

[0159] The terminal's policy information is divided into different categories, such as business class, high-reliability communication class, power saving class, and asynchronous registration class.

[0160] Enhanced Mobile Broadband (eMBB) service class: When a service of a certain type (identified by APP ID / OSI ID) is triggered, UE2 selects the corresponding PLMN or RAT type for registration according to the policy issued by the network;

[0161] According to the high-reliability communication category: When a high-reliability service (such as uRLLC service) is triggered, UE2 must immediately initiate registration, and the registered PLMN and RAT type must be consistent with UE1;

[0162] By power-saving type: When the terminal is an energy-saving terminal or the service is power-saving, UE2 needs to register to the power-saving network (such as LTE), and the other UE1 also needs to enter a deep power-saving state (such as DRX) to reduce energy consumption;

[0163] Asynchronous registration type: When the network requires two terminals to register asynchronously, after UE1 registers, UE2 must register to a different PLMN or RAT type than UE1.

[0164] Table 1 shows the static setting information of different types of policies.

[0165] Table 1 Static setting information of different types of strategies

[0166] Among them, Access Type preference is the access type preference, RAT Type preference is the radio access technology type preference, and PLMN preference is the public land mobile network preference.

[0167] The disclosed embodiments provide a method for a UDM to perform subscription settings on a first terminal UE1 and a second terminal UE2 of a dual-boot device, thereby enabling selection of an access type for UE2. In this embodiment, the subscription settings of the dual-boot device in a home UDM (hUDM) and a Universal Subscriber Identity Module (USIM) are based on the original subscription data, and two SUPI settings of the dual-boot device are added to the hUDM and the USIM of the dual-boot device. In addition, an indication of whether the two SUPIs are dual-boot devices and a designated access type are added, as shown in Table 2 or Table 3.

[0168] Table 2. Contract setup information for dual-boot devices

[0169] Table 3. Contract setup information for dual-boot devices

[0170] In Table 2 and Table 3, the dual-boot device indicator (DualSteer device indicator) is used to indicate whether the terminal is a dual-boot device, and if so, select True; otherwise, select False.

[0171] The associated identifier (Associated SUPI / IMSI or PEI / IMEI) indicates:

[0172] The association identifiers of UE1 and UE2 are, for example: the Subscription Concealed Identifier (SUCI) of UE1 is associated with the SUCI of UE2; or, the International Mobile Subscriber Identity (IMSI) of UE1 is associated with the IMSI of UE2; or, the Permanent Equipment Identity (PEI) of UE1 is associated with the PEI of UE2; or, the International Mobile Equipment Identity (IMEI) of UE1 is associated with the IMEI of UE2.

[0173] Primary Device or Leading Device: This option determines whether the terminal is the primary device, i.e., the device with priority in the HPLMN, only when the terminal is a dual-boot device. Select Yes if it is, or No if it is not.

[0174] The DualSteer Device applies for Emergency service indicator determines whether emergency services are applicable to dual-boot devices. Select Yes if yes, or No if no.

[0175] RAT restriction is an existing parameter that indicates which radio access technology (RAT) types a terminal cannot access. For UE2, you can directly specify the types it requires access to and restrict the types it does not require access to. For example, in Table 2 or Table 3, UE2 cannot access via 4G and can only access via non-4G access types (such as 5G New Radio).

[0176] The following embodiments, Figures 1 to 9, describe how, after UE1 completes registration with its home public land mobile network (HPLMN), it obtains the home network's triggering policy for UE2 registration (i.e., UE2's policy information) and forwards it to UE2 (via internal forwarding). Under the guidance of different policies, UE2 triggers registration with the core network (as shown in the embodiments of Figures 7 to 9). The embodiments of Figures 7 to 9 primarily provide routing guidance based on eMBB service class.

[0177] FIG1 is a flow chart of a dual-boot device registration method provided by an embodiment of the present disclosure, wherein the dual-boot device registration method is applied to a first terminal of the dual-boot device. As shown in FIG1 , the dual-boot device registration method may include but is not limited to steps 101 and 102:

[0178] In step 101, a first terminal sends a registration request to an access mobility function (AMF) of a home public land mobile network (HPLMN). The registration request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device.

[0179] In this embodiment, the DualSteer device may have two terminals: a first terminal (UE1) and a second terminal (UE2). The first terminal (UE1) is the terminal that plays a leading role and is denoted as the primary device or the leading device. The first terminal sends a registration request to the Access and Mobility Management Function (AMF) of the Home Public Land Mobile Network (HPLMN).

[0180] In this embodiment, the terminal mobility management core network capability parameter (User Equipment Mobility Management Core Network Capability, UE MM Core Network Capability) in the registration request carries the capability indication of the first terminal supporting dual-boot devices and / or the identifier of the dual-boot device (for example, a permanent equipment identifier (PEI)) and / or the association identifier of the first terminal (UE1) and the second terminal (UE2) in the dual-boot device.

[0181] In this embodiment, the association identifiers of UE1 and UE2 are, for example: the SUCI (Subscription Concealed Identifier) ​​of UE1 is associated with the SUCI of UE2; or the International Mobile Subscriber Identity (IMSI) of UE1 is associated with the IMSI of UE2; or the Permanent Equipment Identity (PEI) of UE1 is associated with the PEI of UE2; or the International Mobile Equipment Identity (IMEI) of UE1 is associated with the IMEI of UE2.

[0182] In step 102, the first terminal receives a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

[0183] In this embodiment, the registration success message includes at least one of the following items: an identifier of the first terminal (for example, UE1's 5G global unique temporary identifier (5G Global Unique Temporary Identifier, 5G-GUTI)), an indication of whether the network supports dual-boot devices, and an identifier of the second terminal (for example, UE2's 5G-GUTI).

[0184] In some embodiments, the registration request in step 101 may further include a UE policy container. After the first terminal sends the registration request to the AMF, it also receives policy information of the first terminal and policy information of the second terminal of the dual-boot device from the AMF. After receiving the policy information of the second terminal, the first terminal sends the policy information of the second terminal to the second terminal.

[0185] The policy information of the second terminal is used for registration guidance information that the second terminal needs to access when initiating a service and establishing a protocol data unit (PDU) session. The policy information of the second terminal includes at least one of the following:

[0186] Service type and identification, terminal type and identification, dual-steer device indicator, operator settings, network configuration, access type preference, radio access technology type preference, and public land mobile network preference. The terminal type and identification refers to the terminal type and identification of the second terminal.

[0187] In some embodiments, after the first terminal receives the registration success message sent by the AMF in step 102, the first terminal sends a protocol data unit PDU session establishment request to the AMF, wherein the PDU session establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an access type (Access Type) of the first terminal, a radio access technology type (RAT Type), and an association identifier between the first terminal and the second terminal.

[0188] FIG2 is a flow chart of a registration method for a dual-boot device provided by an embodiment of the present disclosure, wherein the registration method for a dual-boot device is applied to a second terminal of the dual-boot device. As shown in FIG2 , the registration method for a dual-boot device may include but is not limited to steps 201 to 203:

[0189] In step 201, the second terminal determines a target policy, where the target policy includes at least one of the following: an access type preference, a radio access technology type preference, and a public land mobile network preference.

[0190] In this embodiment, before sending a registration request, the second terminal of a dual-boot device needs to determine a target policy so as to determine, based on the target policy, which AMF to send the registration request to. The second terminal determines the target policy based on its policy information, which is sent by the first terminal of the dual-boot device to the second terminal.

[0191] In some embodiments, the second terminal may determine the target strategy using the following method 1 or method 2:

[0192] Method 1: If the second terminal receives a service initiation request that includes a service type, the second terminal queries its policy information to obtain the target policy corresponding to the service type. The second terminal may receive the service initiation request by proactively detecting the service initiation request or by forwarding the service initiation request from the first terminal of the dual-boot device.

[0193] Method 2: If the second terminal does not receive the service initiation request, the second terminal queries the policy information to obtain the target policy corresponding to the terminal type and / or pre-configured information of the second terminal, where the pre-configured information is manually pre-configured for the second terminal.

[0194] In step 202, the second terminal sends a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference. The registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device.

[0195] In step 203, the second terminal receives a registration success message sent by the AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

[0196] In some embodiments, the registration request in step 202 also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

[0197] In some embodiments, after the second terminal receives the registration success message sent by the AMF in step 203, the second terminal sends a protocol data unit PDU session establishment request to the AMF, wherein the PDU session establishment request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an access type (Access Type) of the second terminal, a radio access technology type (RAT Type), and an association identifier between the first terminal and the second terminal.

[0198] FIG3 is a flow chart of a registration method for a dual-boot device provided by an embodiment of the present disclosure, which is applied to accessing the mobile function AMF. As shown in FIG3 , the registration method for a dual-boot device may include but is not limited to steps 301 to 303:

[0199] In step 301, the AMF receives a registration request sent by the first terminal or the second terminal of a dual-boot device. The registration request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal.

[0200] For example, the AMF receives a registration request sent by the first terminal of a dual-boot device, where the registration request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal.

[0201] For another example, the AMF receives a registration request sent by the second terminal of a dual-boot device, where the registration request includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal.

[0202] In step 302, the AMF sends an authentication and contract request to the unified data management (UDM) function. The authentication and contract request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, and an identifier of the dual-boot device; and the AMF receives the contract information of the first terminal and the contract information of the second terminal sent after the UDM function is authenticated.

[0203] In this embodiment, the AMF sends an authentication and contract request to the Unified Data Management (UDM) function. After authentication, the UDM function sends the contract information of the first terminal and the contract information of the second terminal to the AMF.

[0204] In step 303, the AMF sends a registration success message to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

[0205] In some embodiments, in step 302, after the AMF receives the subscription information of the first terminal and the subscription information of the second terminal sent after the UDM function authentication is passed, the AMF determines whether the first terminal and the second terminal belong to the same dual-boot device. If they belong to the same dual-boot device, the AMF sends a registration success message to the first terminal or the second terminal. The AMF associates and stores the registration context data of the first terminal and the second terminal.

[0206] In some embodiments, in step 301, the registration request sent by the first terminal also includes a terminal policy container (UE policy container). After receiving the registration request, the AMF will also send a terminal policy establishment request to the Policy Control Function (PCF), wherein the terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal. After receiving the policy establishment request, the PCF determines the policy information of the first terminal and the policy information of the second terminal, and sends the policy information of the first terminal and the policy information of the second terminal to the AMF. The AMF sends the policy information of the first terminal and the policy information of the second terminal to the first terminal.

[0207] In some embodiments, after the AMF receives a protocol data unit PDU session establishment request sent by the first terminal or the second terminal, it forwards the PDU session establishment request to the session management function (SMF), wherein the PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, the access type of the first terminal, the wireless access technology type, and the association identifier of the first terminal and the second terminal, or includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and the association identifier of the first terminal and the second terminal.

[0208] FIG4 is a flow chart illustrating a method for configuring a subscription for a dual-boot device according to an embodiment of the present disclosure. The method is applied to the HPLMN unified data management (UDM) function and / or the unified data repository (UDR) function. As shown in FIG4 , the method for configuring a subscription for a dual-boot device may include, but is not limited to, steps 401 and 402:

[0209] In step 401, a subscription request from a first terminal or a second terminal in a dual-boot device is received, and at least one of the following fields is added to the subscription configuration data of the first terminal or the subscription configuration data of the second terminal in the dual-boot device:

[0210] Terminal identification, dual-steer device indicator, associated terminal identification, primary device indicator (Primary Device indicator or Leading Device indicator), dual-steer device for emergency services indication.

[0211] In step 402, the first terminal identifier or the second terminal identifier of the dual-boot device is set in the terminal identifier; the dual-boot device indication is set to true; the second terminal identifier or the first terminal identifier of the dual-boot device is set in the associated terminal identifier; when the dual-boot device indication is true, the first terminal of the dual-boot device is set to yes in the master device, and the second terminal of the dual-boot device is set to no.

[0212] In some embodiments, in a Universal Subscriber Identity Module (USIM) of a dual-boot device, corresponding configuration creation or update is performed according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

[0213] FIG5 is a flow chart of a registration method for a dual-boot device according to an embodiment of the present disclosure. The registration method for a dual-boot device is applied to a policy control function (PCF) of a home public land mobile network (HPLMN). As shown in FIG5 , the registration method for a dual-boot device may include, but is not limited to, steps 501 and 502:

[0214] In step 501, a terminal policy establishment request sent by the access mobility function AMF is received, and the terminal policy establishment request includes at least one of the following: an indication of the capability of the first terminal of the dual-boot device to support dual-boot devices, an identifier of the first terminal, and an association identifier of the first terminal and the second terminal in the dual-boot device.

[0215] In step 502, the policy information of the first terminal and the policy information of the second terminal are sent to the AMF.

[0216] The policy information of the second terminal includes at least one of the following:

[0217] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0218] Figure 6 is a schematic diagram of a process for registering a first terminal (UE1) of a dual-boot device in a home public land mobile network (HPLMN) (e.g., 5G New Radio NR) according to an embodiment of the present disclosure. In this embodiment, the first terminal (UE1) and the second terminal (UE2) belong to the same dual-boot device, and the subscription information and policy information (UE policy) of UE1 and UE2 are defined in the UDM1 / UDR and PCF1 of PLMN1 (i.e., HPLMN), respectively. RAN1, AMF1, UMD1 / UDR, PCF1, and UPF1 all belong to PLMN1 (i.e., HPLMN), where RAN1 belongs to the 3GPP access network.

[0219] As shown in Figure 6, the process of UE1 registering in the HPLMN (5G New Radio NR) includes the following steps 1 to 9:

[0220] 1. UE1 sends a registration request to AMF1 in the HPLMN. The UE MM Core Network Capability parameter of the registration request carries an indication of UE1's ability to support dual-boot devices, a UE policy container parameter, and an identifier of the dual-boot device (e.g., Permanent Equipment Identifier (PEI)).

[0221] 2. AMF1 sends an authentication and contract request to UDM1. The authentication and contract request includes at least one of the following: UE1's capability indication for supporting dual-boot devices and the dual-boot device identifier PEI. After successful authentication, UDM1 sends UE1's contract information and UE2's contract information to AMF1. In specific implementations, UDM1 can send terminal contract information to AMF1, which includes UE1's contract information and UE2's contract information. UDM1 can also send UE1's contract information to AMF1, which includes UE2's contract information.

[0222] 3. If AMF1 supports dual-boot devices, AMF1 sends a registration success message to UE1, which includes at least one of the following: an identifier of UE1 (e.g., 5G-GUTI), an indication of whether the network supports dual-boot devices, and an identifier of UE2 (e.g., 5G-GUTI).

[0223] 4. Since UE1's registration request includes a terminal policy container (UE policy container), AMF1 sends a terminal policy establishment request to PCF1, and the terminal policy establishment request includes at least one of the following: UE1's capability indication of supporting dual-boot devices, UE1's identifier (5G-GUTI), and the association identifier of UE1 and UE2.

[0224] 5. After receiving the policy establishment request, PCF1 determines the policy information of UE1 and UE2 based on the pre-configured policy information, and sends the policy information of UE1 and UE2 to AMF1 through the message (Namf_Communication_N1N2Message Transfer). In the specific implementation method, PCF1 can send terminal policy information to AMF1 (as shown in Table 3 below), and the terminal policy information includes the policy information of UE1 and UE2. PCF1 can also send UE1's policy information to AMF1, and include UE2's policy information in UE1's policy information. Among them, UE2's policy information is used for the registration guidance information that UE2 needs to access when initiating services and establishing PDU sessions.

[0225] The policy information of UE2 includes at least one of the following:

[0226] Service type and identification, terminal type and identification, dual-steer device indicator, operator settings, network configuration, access type preference, radio access technology type preference, and public land mobile network preference. The terminal type and identification refers to the terminal type and identification of the second terminal.

[0227] Table 3 Terminal policy information

[0228] Based on Table 3, if UE2 needs to initiate a service with OSId / OSAppId 2, the PDU session established by UE2 needs to be accessed through the 3GPP under PLMN1, and the access type is Satellite (LEO). If UE2 needs to initiate a service with DNN catt, the PDU session established by UE2 needs to be accessed through the 3GPP under PLMN1, and the access type is Satellite (GRO). If UE2 needs to initiate a service with a destination IP address of 172.168.1.1, the PDU session established by UE2 needs to be accessed through the 3GPP under PLMN2, and the access type is 5G NR.

[0229] Note that in Table 3, the Access Type preference, RAT Type preference, and PLMN preference have different priorities and correspond to each other. Services such as OSId / OSAppId 1, OSId / OSAppId 2, DNN: catt, and IP address: 172.168.1.1 represent different service types.

[0230] 6a. If UE1 is in idle state, AMF1 triggers a service request to UE1, and when UE1 becomes connected, AMF1 sends the policy information of UE1 and UE2 obtained in step 5 to UE1.

[0231] 6b. If UE1 is in a connected state, AMF1 directly sends the policy information of UE1 and UE2 obtained in step 5 to UE1.

[0232] 7. If UE1 accepts UE1's policy information and UE2's policy information, UE1 responds to AMF1.

[0233] 8. AMF1 sends a notification message (Namf_Communication_N1MessageNotify) to PCF1, informing PCF1 that UE1 has accepted UE1’s policy information and UE2’s policy information.

[0234] 9. UE1 sends the policy information of UE2 issued by PCF1 to UE2 through internal implementation based on the identifier of UE2 received in step 3. In this embodiment, UE1 can also forward the identifier of UE1 (5G-GUTI) received in step 3 to UE2.

[0235] Based on Figure 6, Figure 7 is a flowchart of a second terminal (UE2) of a dual-boot device provided by an embodiment of the present disclosure registering in PLMN1 (e.g., Satellite / LEO). Referring to Table 3, when UE1 detects the service initiation of OSId / OSAppId 2, that is, when UE1 receives the service initiation request, UE1 forwards the service initiation request to UE2. If UE2 has not yet registered in the network, UE2 determines the target policy based on the policy information of UE2 sent by UE1, and the target policy includes at least one of the following: the access type preference (Access Type preference) is 3GPP access, (RAT Type preference) is Satellite (LEO), and the public land mobile network preference (PLMN preference) is PLMN1. UE2 selects Satellite (LEO) access based on the target policy and sends a registration request to AMF1 in PLMN1. After UE2 receives the registration success message sent by AMF1, UE2 sends a protocol data unit PDU session establishment request to AMF1, and AMF1 forwards the PDU session establishment request to the session management function SMF1.

[0236] As shown in FIG7 , the process of UE2 registering in PLMN1 (e.g., satellite low-orbit / LEO) includes but is not limited to the following steps 0 to 8:

[0237] 0. When UE1 detects a service initiation for OSId / OSAppId 2, UE1 forwards the service initiation request to UE2. Alternatively, UE2 directly detects the service initiation for OSId / OSAppId 2, and UE2 is not yet registered with PLMN1. It should be noted that the specific implementation of service detection within the UE depends on the UE's internal implementation and is not the focus of this article.

[0238] 1. Based on the UE2 policy information sent by UE1, UE2 selects satellite (low earth orbit) Satellite (LEO) access and initiates a registration request to AMF1 through RAN2. The registration request includes at least one of the following: UE2's capability indication for supporting dual-boot devices, the dual-boot device identifier PEI, and the association identifiers of the first and second terminals in the dual-boot device. In some embodiments, the registration request may also carry UE1's identifier (5G-GUTI). UE1's identifier is used by RAN2 to select the same AMF as UE1 (i.e., AMF1) to send the registration request.

[0239] 2. AMF1 receives UE2's registration request and initiates an authentication and contract request to UDM1. After UDM1 authenticates, if AMF1 has already saved UE2's contract information (as shown in step 2 of Figure 6), there is no need to obtain it from UDM1 again. Otherwise, AMF1 needs to obtain UE2's contract information from UDM1.

[0240] 3. AMF1 sends a registration success message to UE2, which includes at least one of the following: an identifier of UE2 (e.g., 5G-GUTI) and an indication of whether the network supports dual-boot devices.

[0241] 4. UE2 initiates a PDU session establishment request to AMF1.

[0242] 5. AMF1 tries to select the same SMF1 as UE1 session (if any), and forwards UE2's PDU session establishment request to SMF1, while carrying UE2's capability indication of supporting dual-boot devices and access type (satellite low orbit), etc.

[0243] 6. If SMF1 has already obtained UE2's contract information by querying UE1 earlier, there is no need to obtain UE2's contract information from UDM1 again. Otherwise, SMF1 needs to obtain UE2's contract information from UDM1.

[0244] 7. SMF1 creates N4 session with UPF1.

[0245] 8. SMF1 sends a message to UE2 through AMF1 indicating that the PDU session has been successfully established.

[0246] Based on Figure 6, Figure 8 is a flowchart of the registration of the second terminal (UE2) of a dual-boot device in PLMN1 (for example, Satellite (High Orbit) Satellite / GEO) provided by an embodiment of the present disclosure. Referring to Table 3, when UE1 detects the initiation of the DNN:catt service, UE1 forwards the service initiation request to UE2. If UE2 has been registered in PLMN1 (such as accessed through 5GNR), UE2 reselects the satellite (high orbit) (Satellite / GEO) registration access based on the policy information of UE2 sent by UE1, and sends a registration request to AMF2 in PLMN1. After the registration is completed, UE2 initiates a PDU session establishment request to SMF1 through AMF2.

[0247] As shown in FIG8 , the process of UE2 registering in PLMN1 (e.g., Satellite / GEO) includes but is not limited to the following steps 0 to 8:

[0248] 0. When UE1 detects the initiation of the DNN:catt service, UE1 forwards the service initiation request to UE2; or UE2 directly detects the initiation of the DNN:catt service and UE2 has been registered in PLMN1 through 5G NR.

[0249] 1. Based on the UE2 policy information sent by UE1, UE2 selects the satellite high orbit (Satellite / GEO) to re-initiate the registration request. UE2 initiates a mobility registration update request to AMF2 through RAN3. The mobility registration update request includes at least one of the following: UE2's original identifier (5G-GUTI), UE2's ability to support dual-boot devices, and the dual-boot device identifier PEI, etc.

[0250] 2. AMF2 receives UE2's mobility registration update request and locates the original AMF1 using UE2's original identifier. AMF2 interacts with AMF1 to obtain UE2's authentication data, subscription information, and UE2's session data (e.g., the identifier / address of SMF1 used to establish the session), DNN, S-NSSAI, and other information. AMF2 authenticates UE2 based on the information obtained from the interaction. If AMF1 does not retain the corresponding authentication data, AMF2 initiates an authentication request for UE2 to UDM1.

[0251] 3. After AMF2 authentication is successful, it sends a registration success message to UE2. The registration success message includes at least one of the following: UE2's new identifier (5G-GUTI) and an indication of whether the network supports dual-boot devices.

[0252] 4. After receiving the registration success message, UE2 sends a PDU session establishment or update request to AMF2.

[0253] 5. AMF2 selects the same SMF1 as UE2’s previous session (if any), and forwards UE2’s PDU session establishment or update request to SMF1, while carrying UE2’s capability indication of supporting dual-boot devices and access type (satellite high orbit), etc.

[0254] 6-8 are similar to steps 6 to 8 in FIG. 7 , except that an update request is added.

[0255] Based on Figure 6, Figure 9 is a schematic diagram of the process of registering the second terminal (UE2) of a dual-boot device in PLMN2 (for example, 5G new radio NR) provided by an embodiment of the present disclosure. Referring to Table 3, when UE1 detects the initiation of a service at IP address: 172.168.1.1, UE1 forwards the service initiation request to UE2. If UE2 has not yet registered in PLMN1, UE2 selects PLMN2 for access and initiates registration through 5G NR based on the policy information of UE2 sent by UE1. After the registration is completed, the corresponding PDU session establishment request is initiated to SMF3 through AMF3 in PLMN2.

[0256] In FIG9 , the process of UE2 registering in PLMN2 (e.g., 5G NR) includes but is not limited to the following steps 0 to 8:

[0257] 0. When UE1 detects that the service with the destination IP address 172.168.1.1 is initiated, UE1 forwards the service initiation request to UE2; or UE2 directly detects that the service with the IP address 172.168.1.1 is initiated, and UE2 has not yet registered in PLMN1.

[0258] 1. Based on the UE2 policy information sent by UE1, UE2 selects PLMN2 for registration and selects 5G NR access. It initiates a registration request to AMF3 in PLMN2 through RAN4. The registration request includes at least one of the following: UE2's capability indication of supporting dual-boot devices and the dual-boot device identifier PEI, etc.

[0259] 2. AMF3 receives the registration request sent by UE2, initiates authentication and contract request to UDM1 in PLMN1, and obtains UE2's contract information from UDM1.

[0260] 3. After UDM1 authentication is successful, AMF3 sends a registration success message to UE2. The registration success message includes at least one of the following: UE2's identifier (5G-GUTI) and an indication of whether the network supports dual-boot devices.

[0261] 4-8 are similar to steps 4 to 8 in FIG. 7 , except that both SMF3 and UPF3 belong to PLMN2.

[0262] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art will understand that the embodiments of the present disclosure are not limited by the order of the actions described, because according to the embodiments of the present disclosure, certain steps can be performed in other orders or simultaneously. In addition, those skilled in the art will understand that the embodiments described in the specification are all optional embodiments.

[0263] An embodiment of the present disclosure provides a registration device for a dual-boot device, which is applied to a first terminal of the dual-boot device. The registration device for the dual-boot device includes but is not limited to: a first unit and a second unit.

[0264] The first unit is configured to send a registration request to an access mobility function (AMF) of a home public land mobile network (HPLMN), where the registration request includes at least one of the following: a capability indication of the first terminal supporting dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0265] The second unit is used to receive a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

[0266] In some embodiments, the registration request further includes a terminal policy container, and the registration apparatus for the dual-boot device further includes:

[0267] The third unit is used to receive the policy information of the first terminal and the policy information of the second terminal of the dual-boot device sent by the AMF;

[0268] The fourth unit is configured to send the policy information of the second terminal to the second terminal.

[0269] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0270] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0271] In some embodiments, the registration apparatus for the dual-boot device further comprises:

[0272] The fifth unit is used to send a protocol data unit PDU session establishment request to the AMF after the second unit receives the registration success message sent by the AMF, where the PDU session establishment request includes at least one of the following: an indication of the ability of the first terminal to support dual-boot devices, the access type of the first terminal, the wireless access technology type, and the association identifier of the first terminal and the second terminal.

[0273] For details of the above embodiments of the registration apparatus for a dual-boot device, reference may be made to the embodiments of the registration method for a dual-boot device shown in FIG1 , and will not be described again to avoid repetition.

[0274] The present disclosure provides a registration device for a dual-boot device. The registration device for a dual-boot device is applied to a second terminal of the dual-boot device. The registration device for a dual-boot device includes but is not limited to: a first unit, a second unit, and a third unit, which are described in detail as follows:

[0275] A first unit is configured to determine a target policy, the target policy comprising at least one of the following: an access type preference, a radio access technology type preference, and a public land mobile network preference;

[0276] The second unit is configured to send a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0277] The third unit is used to receive a registration success message sent by AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

[0278] In some embodiments, the first unit is configured to:

[0279] If a service initiation request is received, and the service initiation request includes a service type, the second terminal queries the policy information of the second terminal to obtain a target policy corresponding to the service type;

[0280] or,

[0281] If no service initiation request is received, the second terminal queries the policy information to obtain the target policy corresponding to the terminal type and / or pre-configuration information of the second terminal.

[0282] In some embodiments, the first unit receives a service initiation request, including:

[0283] Receiving a service initiation request forwarded by a first terminal of the dual-boot device;

[0284] Alternatively, a service initiation request is detected.

[0285] In some embodiments, the registration request also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

[0286] In some embodiments, the registration apparatus for the dual-boot device further comprises:

[0287] The fourth unit is used to send a protocol data unit PDU session establishment request to the AMF after the third unit receives the registration success message sent by the AMF, where the PDU session establishment request includes at least one of the following: an indication of the ability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0288] For details of the above embodiments of the registration apparatus for a dual-boot device, reference may be made to the embodiments of the registration method for a dual-boot device shown in FIG2 , and will not be described again to avoid repetition.

[0289] The present disclosure provides a registration device for a dual-boot device, which is used to access an AMF (Advanced Mobile Function). The registration device for the dual-boot device includes but is not limited to: a first unit, a second unit, and a third unit, which are described in detail as follows:

[0290] The first unit is configured to receive a registration request sent by a first terminal or a second terminal of a dual-boot device, where the registration request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal;

[0291] The second unit is configured to send an authentication and contract signing request to the unified data management (UDM) function, wherein the authentication and contract signing request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices and an identifier of the dual-boot device; and receive contract signing information of the first terminal and contract signing information of the second terminal sent by the UDM function after authentication is passed;

[0292] The third unit is configured to send a registration success message to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

[0293] In some embodiments, the registration apparatus for the dual-boot device further comprises:

[0294] The fourth unit is configured to determine whether the first terminal and the second terminal belong to the same dual-boot device after the second unit receives the contract information of the first terminal and the contract information of the second terminal sent after the UDM function authentication is passed;

[0295] Correspondingly, the third unit determines in the fourth unit that the first terminal and the second terminal belong to the same dual-boot device, and then sends a registration success message to the first terminal or the second terminal; and associates and stores the registration context data of the first terminal and the second terminal.

[0296] In some embodiments, the registration request sent by the first terminal also includes a terminal policy container, and the registration apparatus of the dual-boot device further includes:

[0297] The fifth unit is used to send a terminal policy establishment request to the policy control function PCF, where the terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an associated identifier of the first terminal and the second terminal; receive the policy information of the first terminal and the policy information of the second terminal sent by the PCF; and send the policy information of the first terminal and the policy information of the second terminal to the first terminal.

[0298] In some embodiments, the registration apparatus for the dual-boot device further comprises:

[0299] The sixth unit is used to forward the protocol data unit PDU session establishment request to the session management function SMF after receiving the protocol data unit PDU session establishment request sent by the first terminal or the second terminal, wherein the PDU session establishment request includes at least one of the following: the capability indication of the first terminal to support dual-boot devices, the access type of the first terminal access, the wireless access technology type, and the association identifier of the first terminal and the second terminal, or includes at least one of the following: the capability indication of the second terminal to support dual-boot devices, the access type of the second terminal access, the wireless access technology type, and the association identifier of the first terminal and the second terminal.

[0300] For details of the above embodiments of the registration apparatus for a dual-boot device, reference may be made to the embodiments of the registration method for a dual-boot device shown in FIG3 , and will not be described again to avoid repetition.

[0301] The present disclosure provides a subscription configuration device for a dual-boot device, which is applied to a unified data management (UDM) function and / or a unified data repository (UDR) function of a home public land mobile network (HPLMN). The subscription configuration device includes:

[0302] The first unit is configured to receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to the subscription configuration data of the first terminal or the subscription configuration data of the second terminal in the dual-boot device:

[0303] Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

[0304] In some embodiments, the subscription configuration device further includes:

[0305] The second unit is used to set the first terminal identification or the second terminal identification of the dual-boot device in the terminal identification; set it to true in the dual-boot device indication; set the second terminal identification or the first terminal identification of the dual-boot device in the associated terminal identification; when the dual-boot device indication is true, set the first terminal of the dual-boot device to yes and the second terminal of the dual-boot device to no in the master device.

[0306] In some embodiments, the subscription configuration device further includes:

[0307] The third unit is configured to create or update corresponding configuration in a universal subscriber identity module (USIM) of the dual-boot device according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

[0308] For details of the above embodiments of the contract configuration apparatus for a dual-boot device, reference may be made to the embodiments of the contract configuration method for a dual-boot device shown in FIG4 , and will not be described again to avoid repetition.

[0309] The present disclosure provides a registration device for a dual-boot device, which is applied to a policy control function (PCF) of a home public land mobile network (HPLMN). The registration device for a dual-boot device includes:

[0310] The first unit is configured to receive a terminal policy establishment request sent by an access mobility function (AMF), where the terminal policy establishment request includes at least one of the following: an indication of a capability of a first terminal of a dual-boot device to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0311] The second unit is used to send the policy information of the first terminal and the policy information of the second terminal to the AMF.

[0312] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0313] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0314] For details of the above embodiments of the registration apparatus for a dual-boot device, reference may be made to the embodiments of the registration method for a dual-boot device shown in FIG5 , and will not be described again to avoid repetition.

[0315] The present disclosure also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a program, wherein the program is used to cause the processor to execute the steps of each embodiment of the registration method for a dual-boot device or the contract configuration method for a dual-boot device. The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as a floppy disk, hard disk, tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0316] FIG10 is a schematic diagram of a communication device provided in an embodiment of the present disclosure. As shown in FIG10 , the communication device provided in an embodiment of the present disclosure includes a memory 1001, a transceiver 1002, and a processor 1003.

[0317] The memory 1001 is used to store computer programs; the transceiver 1002 is used to send and receive data under the control of the processor 1003; the processor 1003 is used to read the computer program in the memory 1001 and execute any one of the processes 1 to 5:

[0318] Process 1:

[0319] Send a registration request to the access mobility function (AMF) of the home public land mobile network (HPLMN), where the registration request includes at least one of the following: an indication of the first terminal's capability to support dual-boot devices, an identifier of the dual-boot device, and an identifier associated with the first terminal and the second terminal in the dual-boot device;

[0320] Receive a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

[0321] In some embodiments, the registration request also includes a terminal policy container, and the processor 1003 is further configured to:

[0322] Receive the policy information of the first terminal and the policy information of the second terminal of the dual-boot device sent by the AMF;

[0323] The policy information of the second terminal is sent to the second terminal.

[0324] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0325] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0326] In some embodiments, after the first terminal receives the registration success message sent by the AMF, the processor 1003 is further configured to:

[0327] A protocol data unit (PDU) session establishment request is sent to the AMF. The PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, an access type of the first terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0328] Process 2:

[0329] determining a target strategy, the target strategy comprising at least one of: an access type preference, a wireless access technology type preference, and a public land mobile network preference;

[0330] Sending a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device;

[0331] Receive a registration success message from the AMF, which includes an indication of whether the network supports dual-boot devices.

[0332] In some embodiments, determining the target strategy includes:

[0333] If a service initiation request is received, and the service initiation request includes a service type, querying the policy information of the second terminal to obtain a target policy corresponding to the service type;

[0334] or,

[0335] If no service initiation request is received, the policy information is queried to obtain the target policy corresponding to the terminal type and / or pre-configured information of the second terminal.

[0336] In some embodiments, receiving a service initiation request includes:

[0337] Receiving a service initiation request forwarded by a first terminal of the dual-boot device;

[0338] Alternatively, a service initiation request is detected.

[0339] In some embodiments, the registration request also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

[0340] In some embodiments, after receiving the registration success message sent by the AMF, the processor 1003 is further configured to:

[0341] A protocol data unit (PDU) session establishment request is sent to the AMF. The PDU session establishment request includes at least one of the following: an indication of the ability of the second terminal to support dual-boot devices, an access type of the second terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

[0342] Process three:

[0343] Receiving a registration request sent by a first terminal or a second terminal of a dual-boot device, the registration request including at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal;

[0344] Sending an authentication and contract signing request to the unified data management (UDM) function, the authentication and contract signing request including at least one of the following: an indication of the first terminal or the second terminal's ability to support dual-boot devices and an identifier of the dual-boot device; and receiving contract signing information of the first terminal and contract signing information of the second terminal sent by the UDM function after successful authentication;

[0345] A registration success message is sent to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

[0346] In some embodiments, after receiving the contract information of the first terminal and the contract information of the second terminal sent after the UDM function authentication is passed, the processor 1003 is further configured to:

[0347] determining whether the first terminal and the second terminal belong to the same dual-boot device;

[0348] If they belong to the same dual-boot device, sending a registration success message to the first terminal or the second terminal;

[0349] The registration context data of the first terminal and the second terminal are associated and stored.

[0350] In some embodiments, the registration request of the first terminal also includes a terminal policy container, and the processor 1003 is further configured to:

[0351] Sending a terminal policy establishment request to the policy control function PCF, where the terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an identifier associated with the first terminal and the second terminal;

[0352] Receiving policy information of the first terminal and policy information of the second terminal sent by the PCF;

[0353] The policy information of the first terminal and the policy information of the second terminal are sent to the first terminal.

[0354] In some embodiments, the processor 1003 is further configured to:

[0355] After receiving the protocol data unit PDU session establishment request sent by the first terminal or the second terminal, the PDU session establishment request is forwarded to the session management function SMF, wherein the PDU session establishment request includes at least one of the following: the capability indication of the first terminal to support dual-boot devices, the access type of the first terminal access, the wireless access technology type, and the association identifier of the first terminal and the second terminal, or includes at least one of the following: the capability indication of the second terminal to support dual-boot devices, the access type of the second terminal access, the wireless access technology type, and the association identifier of the first terminal and the second terminal.

[0356] Process 4:

[0357] Receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to subscription configuration data of the first terminal or the second terminal in the dual-boot device:

[0358] Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

[0359] In some embodiments, the processor 1003 is further configured to:

[0360] Setting the first terminal identification or the second terminal identification of the dual-boot device in the terminal identification;

[0361] Set to true in dual boot device indication;

[0362] Setting the second terminal identification or the first terminal identification of the dual-boot device in the associated terminal identification;

[0363] When the dual boot device indication is true, the first terminal of the dual boot device is set to yes and the second terminal of the dual boot device is set to no in the master device.

[0364] In some embodiments, the processor 1003 is further configured to:

[0365] In the universal subscriber identity module USIM of the dual-boot device, corresponding configuration creation or update is performed according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

[0366] Process 5:

[0367] Receive a terminal policy establishment request sent by the access mobility function AMF, where the terminal policy establishment request includes at least one of the following: an indication of a capability of the first terminal of the dual-boot device to support dual-boot devices, an identifier of the first terminal, and an identifier of an association between the first terminal and the second terminal in the dual-boot device;

[0368] Send the policy information of the first terminal and the policy information of the second terminal to the AMF.

[0369] In some embodiments, the policy information of the second terminal includes at least one of the following:

[0370] Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

[0371] In Figure 10, transceiver 1002 is used to receive and transmit data under the control of processor 1003. The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits such as one or more processors represented by processor 1003 and memory represented by memory 1001. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be further described herein. The bus interface provides an interface. Transceiver 1002 can be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or other transmission medium. Processor 1003 is responsible for managing the bus architecture and general processing, and memory 1001 can store data used by processor 1003 when performing operations.

[0372] In FIG10 , the processor 1003 may be an integrated circuit chip having signal processing capabilities. During implementation, each step of the above method may be performed by hardware integrated logic circuits in the processor 1003 or by software instructions. The processor 1003 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor may be a microprocessor or any conventional processor.

[0373] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0374] Those skilled in the art will appreciate that although some embodiments described herein include certain features and not others included in other embodiments, the combination of features from different embodiments is intended to be within the scope of this disclosure and to form different embodiments.

[0375] Those skilled in the art will understand that the description of each embodiment has its own focus, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0376] Although the embodiments of the present disclosure have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A registration method for a dual-boot device, applied to a first terminal of the dual-boot device, the method comprising: The first terminal sends a registration request to an access mobility function (AMF) of a home public land mobile network (HPLMN), where the registration request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device; The first terminal receives a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

2. The method according to claim 1, wherein The registration request also includes a terminal policy container, and the method further includes: The first terminal receives the policy information of the first terminal and the policy information of the second terminal of the dual-boot device sent by the AMF; The first terminal sends the policy information of the second terminal to the second terminal.

3. The method according to claim 2, wherein: The policy information of the second terminal includes at least one of the following: Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

4. The method according to claim 1, wherein After the first terminal receives the registration success message sent by the AMF, the method further includes: The first terminal sends a protocol data unit PDU session establishment request to the AMF, where the PDU session establishment request includes at least one of the following: an indication of the ability of the first terminal to support dual-boot devices, an access type of the first terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

5. A registration method for a dual-boot device, applied to a second terminal of the dual-boot device, the method comprising: The second terminal determines a target policy, the target policy comprising at least one of: an access type preference, a radio access technology type preference, and a public land mobile network preference; The second terminal sends a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the second terminal's ability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device; The second terminal receives a registration success message sent by the AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

6. The method according to claim 5, wherein: The second terminal determines the target strategy including: If the second terminal receives a service initiation request, and the service initiation request includes a service type, the second terminal queries the policy information of the second terminal to obtain a target policy corresponding to the service type; or, If the second terminal does not receive the service initiation request, the second terminal queries the policy information to obtain the target policy corresponding to the terminal type and / or pre-configuration information of the second terminal.

7. The method according to claim 6, wherein: The second terminal receives the service initiation request, including: The second terminal receives a service initiation request forwarded by the first terminal of the dual-boot device; Alternatively, the second terminal detects a service initiation request.

8. The method according to claim 5, wherein The registration request also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

9. The method according to claim 5, wherein: After the second terminal receives the registration success message sent by the AMF, the method further includes: The second terminal sends a protocol data unit PDU session establishment request to the AMF, and the PDU session establishment request includes at least one of the following: an indication of the ability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and an association identifier between the second terminal and the first terminal.

10. A registration method for a dual-boot device, applied to accessing an AMF, the method comprising: The AMF receives a registration request sent by a first terminal or a second terminal of a dual-boot device, where the registration request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal; The AMF sends an authentication and contract request to the unified data management (UDM) function, where the authentication and contract request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices and an identifier of the dual-boot device; and the AMF receives the contract information of the first terminal and the contract information of the second terminal sent by the UDM function after authentication is passed; The AMF sends a registration success message to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

11. The method according to claim 10, wherein: After the AMF receives the subscription information of the first terminal and the subscription information of the second terminal sent after the UDM function authentication is passed, the method further includes: If the first terminal and the second terminal belong to the same dual-boot device, executing the AMF to send a registration success message to the first terminal or the second terminal; The AMF associates and stores the registration context data of the first terminal and the second terminal.

12. The method according to claim 10, wherein: The registration request sent by the first terminal also includes a terminal policy container, and the method further includes: The AMF sends a terminal policy establishment request to the policy control function PCF, where the terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal; The AMF receives the policy information of the first terminal and the policy information of the second terminal sent by the PCF; The AMF sends the policy information of the first terminal and the policy information of the second terminal to the first terminal.

13. The method according to claim 10, further comprising: After the AMF receives the protocol data unit PDU session establishment request sent by the first terminal or the second terminal, it forwards the PDU session establishment request to the session management function SMF, wherein the PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, the access type of the first terminal, the wireless access technology type, and the association identifier of the first terminal and the second terminal, or includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and the association identifier of the second terminal and the first terminal.

14. A method for configuring a subscription for a dual-boot device, applied to a Home Public Land Mobile Network (HPLMN) unified data management (UDM) function and / or unified data repository (UDR) function, the method comprising: Receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to subscription configuration data of the first terminal or the second terminal in the dual-boot device: Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

15. The method according to claim 14, wherein The method further comprises: Setting the first terminal identification or the second terminal identification of the dual-boot device in the terminal identification; set to true in said dual boot device indication; Setting the second terminal identification or the first terminal identification of the dual-boot device in the associated terminal identification; When the dual boot device indication is true, the first terminal of the dual boot device is set to yes and the second terminal of the dual boot device is set to no in the master device.

16. The method according to claim 14, wherein The method further comprises: In the universal subscriber identity module (USIM) of the dual-boot device, corresponding configuration creation or updating is performed according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

17. A registration method for a dual-boot device, applied to a policy control function (PCF) of a home public land mobile network (HPLMN), the method comprising: receiving a terminal policy establishment request sent by an access mobility function (AMF), the terminal policy establishment request including at least one of the following: an indication of a capability of a first terminal of a dual-boot device to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal in the dual-boot device; Send the policy information of the first terminal and the policy information of the second terminal to the AMF.

18. The method according to claim 17, wherein The policy information of the second terminal includes at least one of the following: Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

19. A registration device for a dual-boot device, applied to a first terminal of the dual-boot device, the device comprising: a first unit configured to send a registration request to an access mobility function (AMF) of a home public land mobile network (HPLMN), the registration request including at least one of the following: an indication of the first terminal's capability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device; The second unit is used to receive a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

20. A registration device for a dual-boot device, applied to a second terminal of the dual-boot device, the device comprising: A first unit is configured to determine a target policy, wherein the target policy includes at least one of the following: an access type preference, a radio access technology type preference, and a public land mobile network preference; a second unit, configured to send a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, wherein the registration request includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device; The third unit is used to receive a registration success message sent by the AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

21. A registration device for a dual-boot device, used for accessing an AMF (Active Mobile Function), comprising: A first unit is configured to receive a registration request sent by a first terminal or a second terminal of a dual-boot device, wherein the registration request includes at least one of the following: an indication of a capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal; The second unit is configured to send an authentication and contract request to the unified data management (UDM) function, where the authentication and contract request includes at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices and an identifier of the dual-boot device; and the AMF receives the contract information of the first terminal and the contract information of the second terminal sent by the UDM function after the authentication is passed; The third unit is configured to send a registration success message to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

22. A subscription configuration device for a dual-boot device, applied to a Home Public Land Mobile Network (HPLMN) unified data management function (UDM) and / or unified data repository function (UDR), the device comprising: The first unit is configured to receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to the subscription configuration data of the first terminal or the subscription configuration data of the second terminal in the dual-boot device: Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

23. A registration device for a dual-boot device, applied to a policy control function (PCF) of a home public land mobile network (HPLMN), the device comprising: The first unit is configured to receive a terminal policy establishment request sent by an access mobility function (AMF), where the terminal policy establishment request includes at least one of the following: an indication of a capability of a first terminal of a dual-boot device to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal in the dual-boot device; The second unit is used to send the policy information of the first terminal and the policy information of the second terminal to the AMF.

24. A communication device, wherein: Including memory, transceiver, processor; The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory and execute: Sending a registration request to an access mobility function (AMF) of a home public land mobile network (HPLMN), the registration request including at least one of the following: an indication of the first terminal's capability to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device; Receive a registration success message sent by the AMF, where the registration success message includes at least one of the following: an identifier of the first terminal, an indication of whether the network supports dual-boot devices, and an identifier of the second terminal.

25. The communication device according to claim 24, wherein The registration request sent by the first terminal also includes a terminal policy container, and the processor is further configured to: receiving the policy information of the first terminal and the policy information of the second terminal of the dual-boot device sent by the AMF; The policy information of the second terminal is sent to the second terminal.

26. The communication device according to claim 25, wherein The policy information of the second terminal includes at least one of the following: Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

27. The communication device according to claim 24, wherein After the first terminal receives the registration success message sent by the AMF, the processor is further configured to: A protocol data unit (PDU) session establishment request is sent to the AMF, where the PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, an access type of the first terminal, a wireless access technology type, and an association identifier between the first terminal and the second terminal.

28. A communication device, wherein: Including memory, transceiver, processor; The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory and execute: determining a target policy, the target policy comprising at least one of: an access type preference, a wireless access technology type preference, and a public land mobile network preference; Sending a registration request to the AMF corresponding to the public land mobile network preference through the radio access network corresponding to the access type preference and the radio access technology type preference, where the registration request includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal in the dual-boot device; Receive a registration success message sent by the AMF, where the registration success message includes an indication of whether the network supports dual-boot devices.

29. The communication device according to claim 28, wherein The target determination strategy includes: If a service initiation request is received, and the service initiation request includes a service type, querying the policy information of the second terminal to obtain a target policy corresponding to the service type; or, If no service initiation request is received, the policy information is queried to obtain the target policy corresponding to the terminal type and / or pre-configured information of the second terminal.

30. The communication device according to claim 29, wherein The receiving of the service initiation request includes: receiving a service initiation request forwarded by a first terminal of the dual-boot device; Alternatively, a service initiation request is detected.

31. The communication device according to claim 28, wherein The registration request also includes an identifier of the first terminal of the dual-boot device, and the identifier of the first terminal is used to select the same AMF as the first terminal to send the registration request.

32. The communication device according to claim 28, wherein After receiving the registration success message sent by the AMF, the processor is further configured to: A protocol data unit (PDU) session establishment request is sent to the AMF, where the PDU session establishment request includes at least one of the following: an indication of the ability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and an association identifier between the second terminal and the first terminal.

33. A communication device, wherein: Including memory, transceiver, processor; The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory and execute: Receiving a registration request sent by a first terminal or a second terminal of a dual-boot device, the registration request including at least one of the following: an indication of a capability of the first terminal or the second terminal to support dual-boot devices, an identifier of the dual-boot device, and an association identifier between the first terminal and the second terminal; Sending an authentication and contract signing request to a unified data management (UDM) function, the authentication and contract signing request including at least one of the following: an indication of the capability of the first terminal or the second terminal to support dual-boot devices and an identifier of the dual-boot device; and receiving contract signing information of the first terminal and the second terminal sent by the UDM function after authentication is passed; A registration success message is sent to the first terminal or the second terminal, where the registration success message includes at least one of the following: an identifier of the first terminal and / or the second terminal, and an indication of whether the network supports dual-boot devices.

34. The communication device according to claim 33, wherein After receiving the contract information of the first terminal and the contract information of the second terminal sent after the UDM function authentication is passed, the processor is further configured to: If the first terminal and the second terminal belong to the same dual-boot device, executing the step of sending a registration success message to the first terminal or the second terminal; The registration context data of the first terminal and the second terminal are associated and stored.

35. The communication device according to claim 33, wherein The registration request of the first terminal also includes a terminal policy container, and the processor is further configured to: Sending a terminal policy establishment request to a policy control function (PCF), where the terminal policy establishment request includes at least one of the following: an indication of the first terminal's ability to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal; receiving the policy information of the first terminal and the policy information of the second terminal sent by the PCF; The policy information of the first terminal and the policy information of the second terminal are sent to the first terminal.

36. The communication device according to claim 33, wherein the processor is further configured to: After receiving the protocol data unit PDU session establishment request sent by the first terminal or the second terminal, forwarding the PDU session establishment request to the session management function SMF, wherein, The PDU session establishment request includes at least one of the following: an indication of the capability of the first terminal to support dual-boot devices, the access type of the first terminal, the wireless access technology type, and an association identifier between the first terminal and the second terminal, or includes at least one of the following: an indication of the capability of the second terminal to support dual-boot devices, the access type of the second terminal, the wireless access technology type, and an association identifier between the second terminal and the first terminal.

37. A communication device, wherein: Including memory, transceiver, processor; The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory and execute: Receive a subscription request from a first terminal or a second terminal in a dual-boot device, and add at least one of the following fields to subscription configuration data of the first terminal or the second terminal in the dual-boot device: Terminal identification, dual-boot device indication, associated terminal identification, primary device indication, dual-boot device for emergency services indication.

38. The communication device according to claim 37, wherein: The processor is further configured to: Setting the first terminal identification or the second terminal identification of the dual-boot device in the terminal identification; set to true in said dual boot device indication; Setting the second terminal identification or the first terminal identification of the dual-boot device in the associated terminal identification; When the dual boot device indication is true, the first terminal of the dual boot device is set to yes and the second terminal of the dual boot device is set to no in the master device.

39. The communication device according to claim 37, wherein The processor is further configured to: In the universal subscriber identity module (USIM) of the dual-boot device, corresponding configuration creation or updating is performed according to the subscription configuration data of the first terminal and / or the subscription configuration data of the second terminal in the dual-boot device.

40. A communication device, wherein: Including memory, transceiver, processor; The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; and the processor is used to read the computer program in the memory and execute: receiving a terminal policy establishment request sent by an access mobility function (AMF), the terminal policy establishment request including at least one of the following: an indication of a capability of a first terminal of a dual-boot device to support dual-boot devices, an identifier of the first terminal, and an association identifier between the first terminal and the second terminal in the dual-boot device; Send the policy information of the first terminal and the policy information of the second terminal to the AMF.

41. The communication device according to claim 40, wherein: The policy information of the second terminal includes at least one of the following: Service type and identification, terminal type and identification, dual-boot device indication, operator settings, network configuration, access type preference, radio access technology type RAT type preference, and public land mobile network PLMN preference.

42. A processor-readable storage medium, wherein: The processor-readable storage medium stores a program, and the program is used to enable the processor to execute the registration method for a dual-boot device as described in any one of claims 1 to 4, or execute the registration method for a dual-boot device as described in any one of claims 5 to 9, or execute the registration method for a dual-boot device as described in any one of claims 10 to 13, or execute the contract configuration method for a dual-boot device as described in any one of claims 14 to 16, or execute the registration method for a dual-boot device as described in claim 17 or 18.

Images