Terminal sharing subscription data changing method and device of double-guide equipment, and storage medium

Abstract

The invention provides a terminal sharing subscription data changing method and device of double-guide equipment and a storage medium, which are applied to a first network function entity, and the method comprises the following steps: detecting an association relationship between a first terminal and a second terminal; sending a first notification message to the second network function entity based on the association relationship under the condition that the shared subscription data of the first terminal is changed; wherein the first notification message is used for notifying that the shared subscription information of the first terminal is changed, and the first notification message comprises changed shared subscription data of the first terminal; or the first notification message is used for notifying the second terminal that the shared subscription information is changed, and the first notification message comprises the changed shared subscription data of the second terminal. According to the method and the device, under the condition that the shared subscription data of one terminal in the DualSteer equipment is changed, the shared subscription data of the other terminal in the DualSteer equipment is changed.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a method, device, and storage medium for changing shared contract data of a terminal of a dual-boot device. Background Art

[0002] Currently, two terminals (User Equipment, UE) in a DualSteer device can share some subscription data, such as access and mobility management (AM) subscription data, session management (SM) subscription data or policy data.

[0003] When the shared subscription data of the first UE is changed, the shared subscription data of the second UE will also change, which may affect the protocol data unit (PDU) session update of the UE and even require the UE to re-register.

[0004] However, the issue of changing the shared subscription data of the second UE has not yet been defined. Summary of the Invention

[0005] In response to the problems existing in the prior art, the embodiments of the present application provide a method, device and storage medium for changing the shared terminal subscription data of a dual-boot device, so as to solve the problem of changing the shared subscription data of a second UE when the shared subscription data of one UE in a DualSteer device changes.

[0006] In a first aspect, an embodiment of the present application provides a method for changing shared subscription data of a terminal of a dual-boot device, which is applied to a first network function entity, including:

[0007] detecting an association relationship between the first terminal and the second terminal;

[0008] When the shared subscription data of the first terminal changes, sending a first notification message to the second network function entity based on the association relationship;

[0009] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0010] In some embodiments, the association relationship includes at least one of the following:

[0011] The first terminal and the second terminal belong to the same dual-boot device;

[0012] The first terminal and the second terminal are registered on the same network element;

[0013] The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

[0014] In some embodiments, when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or

[0015] In a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or in a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or,

[0016] When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

[0017] In some embodiments, the shared subscription data includes at least one of the following:

[0018] AM contract data;

[0019] SM contract data;

[0020] Strategy data.

[0021] In a second aspect, an embodiment of the present application provides a method for changing shared subscription data of a terminal of a dual-boot device, which is applied to a second network function entity, including:

[0022] Receiving a first notification message sent by a first network function entity;

[0023] Based on the first notification message, change the shared subscription data of the second terminal;

[0024] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0025] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0026] When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

[0027] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0028] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0029] When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal;

[0030] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0031] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0032] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0033] If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal;

[0034] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0035] In some embodiments, the method further comprises:

[0036] In a case where the shared subscription data of the second terminal is changed and affects the existing PDU session of the second terminal, sending a PDU session release request or a PDU session update request to the third network function entity, or triggering a PDU session release request or a PDU session update request;

[0037] The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

[0038] In some embodiments, the method further comprises:

[0039] When the second terminal has no PDU session online, an AN release request is sent to the fourth network function entity; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

[0040] In some embodiments, the shared subscription data includes at least one of the following:

[0041] AM contract data;

[0042] SM contract data;

[0043] Strategy data.

[0044] In a third aspect, an embodiment of the present application further provides a first network function entity, including a memory, a transceiver, and a processor:

[0045] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0046] detecting an association relationship between the first terminal and the second terminal;

[0047] When the shared subscription data of the first terminal changes, sending a first notification message to the second network function entity based on the association relationship;

[0048] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0049] In some embodiments, the association relationship includes at least one of the following:

[0050] The first terminal and the second terminal belong to the same dual-boot device;

[0051] The first terminal and the second terminal are registered on the same network element;

[0052] The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

[0053] In some embodiments, when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or

[0054] In a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or in a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or,

[0055] When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

[0056] In some embodiments, the shared subscription data includes at least one of the following:

[0057] AM contract data;

[0058] SM contract data;

[0059] Strategy data.

[0060] In a fourth aspect, an embodiment of the present application further provides a second network function entity, including a memory, a transceiver, and a processor:

[0061] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0062] Receiving a first notification message sent by a first network function entity;

[0063] Based on the first notification message, change the shared subscription data of the second terminal;

[0064] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0065] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0066] When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

[0067] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0068] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0069] When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal;

[0070] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0071] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0072] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0073] If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal;

[0074] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0075] In some embodiments, the operations further include:

[0076] In a case where the shared subscription data of the second terminal is changed and affects the existing PDU session of the second terminal, sending a PDU session release request or a PDU session update request to the third network function entity, or triggering a PDU session release request or a PDU session update request;

[0077] The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

[0078] In some embodiments, the operations further include:

[0079] When the second terminal has no PDU session online, an AN release request is sent to the fourth network function entity; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

[0080] In some embodiments, the shared subscription data includes at least one of the following:

[0081] AM contract data;

[0082] SM contract data;

[0083] Strategy data.

[0084] In a fifth aspect, an embodiment of the present application further provides a device for changing shared subscription data of a terminal of a dual-boot device, comprising:

[0085] A detection module, configured to detect an association relationship between the first terminal and the second terminal;

[0086] a sending module, configured to send a first notification message to the second network function entity based on the association relationship when the shared subscription data of the first terminal changes;

[0087] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0088] In some embodiments, the association relationship includes at least one of the following:

[0089] The first terminal and the second terminal belong to the same dual-boot device;

[0090] The first terminal and the second terminal are registered on the same network element;

[0091] The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

[0092] In some embodiments, when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or

[0093] In a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or in a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or,

[0094] When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

[0095] In some embodiments, the shared subscription data includes at least one of the following:

[0096] AM contract data;

[0097] SM contract data;

[0098] Strategy data.

[0099] In a sixth aspect, an embodiment of the present application further provides a device for changing shared subscription data of a terminal of a dual-boot device, comprising:

[0100] A receiving module, configured to receive a first notification message sent by a first network function entity;

[0101] a changing module, configured to change the shared subscription data of the second terminal based on the first notification message;

[0102] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0103] In some embodiments, the change module is specifically configured to:

[0104] When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

[0105] In some embodiments, the change module is specifically configured to:

[0106] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0107] When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal;

[0108] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0109] In some embodiments, the change module is specifically configured to:

[0110] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0111] If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal;

[0112] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0113] In some embodiments, the apparatus further comprises:

[0114] A first processing module is configured to send a PDU session release request or a PDU session update request to a third network function entity, or trigger a PDU session release request or a PDU session update request, when the shared subscription data of the second terminal is changed and affects an existing PDU session of the second terminal;

[0115] The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

[0116] In some embodiments, the apparatus further comprises:

[0117] The second processing module is used to send an AN release request to the fourth network function entity when there is no PDU session online at the second terminal; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

[0118] In some embodiments, the shared subscription data includes at least one of the following:

[0119] AM contract data;

[0120] SM contract data;

[0121] Strategy data.

[0122] In the seventh aspect, an embodiment of the present application also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the terminal shared contract data change method of the dual-boot device described in the first aspect or the second aspect.

[0123] In an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the terminal shared contract data changing method of a dual-boot device as described in the first aspect or the second aspect.

[0124] In the ninth aspect, an embodiment of the present application further provides a communication device, in which a computer program is stored, and the computer program is used to enable the communication device to execute the terminal shared contract data change method of the dual-boot device described in the first aspect or the second aspect.

[0125] In the tenth aspect, an embodiment of the present application further provides a chip product, in which a computer program is stored, and the computer program is used to enable the chip product to execute the terminal shared contract data change method of the dual-boot device described in the first aspect or the second aspect.

[0126] The embodiments of the present application provide a method, device, and storage medium for changing shared terminal subscription data of a dual-boot device. By detecting the association relationship between a first terminal and a second terminal, when the shared subscription data of the first terminal changes, a first notification message is sent to a second network function entity based on the association relationship. The first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal. Alternatively, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal, so that the second network function entity changes the shared subscription data of the second terminal based on the first notification message, thereby achieving the change of the shared subscription data of another terminal in the DualSteer device when the shared subscription data of one terminal in the DualSteer device changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0127] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0128] Figure 1 This is a flow chart of UE configuration update triggered by AMF network element;

[0129] Figure 2 This is a flow chart of UE policy update triggered by PCF network element;

[0130] Figure 3 This is one of the flow diagrams of the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application;

[0131] Figure 4 This is the second flow chart of the method for changing terminal shared contract data of a dual-boot device provided in an embodiment of the present application;

[0132] Figure 5 This is the third flow chart of the method for changing terminal shared contract data of a dual-boot device provided in an embodiment of the present application;

[0133] Figure 6 This is a fourth flow chart of a method for changing shared contract data of a terminal on a dual-boot device provided in an embodiment of the present application;

[0134] Figure 7 This is the fifth flow chart of the method for changing terminal shared contract data of a dual-boot device provided in an embodiment of the present application;

[0135] Figure 8 This is the sixth flow chart of the method for changing terminal shared contract data of a dual-boot device provided in an embodiment of the present application;

[0136] Figure 9 This is the seventh flow chart of the method for changing terminal shared contract data of a dual-boot device provided in an embodiment of the present application;

[0137] Figure 10 This is the eighth flow chart of the method for changing terminal shared contract data of a dual-boot device provided in an embodiment of the present application;

[0138] Figure 11 This is a ninth flow chart of a method for changing shared contract data of a terminal on a dual-boot device provided in an embodiment of the present application;

[0139] Figure 12 is a structural diagram of a first network function entity provided in an embodiment of the present application;

[0140] Figure 13 is a structural diagram of a second network function entity provided in an embodiment of the present application;

[0141] Figure 14 This is one of the structural diagrams of the terminal shared contract data changing device of the dual-boot device provided in the embodiment of the present application;

[0142] Figure 15 This is the second structural diagram of the terminal shared contract data changing device of the dual-boot device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0143] In order to facilitate a clearer understanding of the various embodiments of the present application, some relevant technical knowledge is first introduced as follows.

[0144] (1) DualSteer device definition

[0145] According to the latest TS22.261 definition, a DualSteer device is a device that supports traffic steering and user data exchange (for different services) across two 3rd Generation Partnership Project (3GPP) networks. It can be a single UE (when transmitting data non-simultaneously on the two networks) or two UEs (when transmitting data simultaneously on the two networks). Generally, a DualSteer device is a single UE. If it is two UEs, the two UEs share a subscription profile but have different identifiers (such as SUPI, etc.).

[0146] DualSteer devices can be smartphones, IoT terminals, drones, etc. Data contracting and policy control for DualSteer devices are all controlled by the home network.

[0147] The two 3GPP accesses may belong to the same home Public Land Mobile Network (PLMN), or to different PLMNs, or one may belong to a Public Network Integrated (PNI) PLMN and the other to a home PLMN.

[0148] The access type can be two fifth-generation mobile communication network (5G) New Radio (NR) accesses, or one terrestrial access, one satellite access, or one 5G NR access, one fourth-generation mobile communication network (4G) Long Term Evolution (LTE) access, or two different satellite types (low earth orbit (LEO), medium earth orbit (MEO), high earth orbit (GEO)) access, etc.

[0149] (2) DualSteer Device Traffic Steering and Traffic Switching Functional Definition: Traffic steering, or traffic steering, is the process of selecting an access network and routing traffic through it. This can apply to traffic for one or more services across two 3GPP access networks, including scenarios where all services use the same network connection (no data is transmitted simultaneously on both networks) or where different services are transmitted across different networks (data is transmitted simultaneously on both networks).

[0150] Traffic switching is the process of moving all services from one access network to another to minimize service interruption. This can apply to traffic for one or more services across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data transmission on both networks) or different services move to different networks (simultaneous data transmission on both networks).

[0151] (3) Terminal configuration update process

[0152] Currently, the terminal configuration update function supported by the 3GPP network mainly targets AM parameters and terminal policy (UEpolicy) parameters. The main update process is as follows:

[0153] Figure 1 This is a flow chart of UE configuration update triggered by Access and Mobility Management Function (AMF) network element, such as Figure 1 As shown, the UE configuration update process triggered by the AMF network element:

[0154] 0. The AMF network element decides to update the UE configuration or requires the UE to re-register;

[0155] 1. The AMF network element sends a configuration update command (UE Configuration Update Command) to the UE;

[0156] 2a. The UE sends a feedback message indicating that the configuration update is complete (UE Configuration Update Complete) to the AMF network element.

[0157] 2b. The AMF network element sends the Nudm_SDM_Info service message to the UDM network element;

[0158] 2c. The AMF network element updates the Radio Access Network (RAN).

[0159] 2d. UE informs lower layers;

[0160] 3a. The UE starts the registration procedure in the CM-CONNECTED state (as described in Section 4.2.2.2. Skipping steps 3b, 3c and 4).

[0161] 3b. The change will not affect the existing connections of the AMF network element;

[0162] 3c. Changes will affect existing connections of AMF network elements;

[0163] 4. Unless there is a PDU Session associated with emergency services, the AMF network element triggers the AN release procedure and the UE starts the registration procedure after entering the CM-IDLE state.

[0164] Figure 2 This is a flow chart of the UE policy update triggered by the Policy Control Function (PCF) network element, such as Figure 2 As shown in the figure, the UE policy update process triggered by the PCF network element:

[0165] 0. The PCF network element decides to update the UE policy;

[0166] 0a. The PCF network element subscribes to receive notifications of the UE policy container;

[0167] 1. The PCF network element sends the Namf_Communication_N1N2 message to the AMF network element for transmission;

[0168] 2. Network-triggered service requests;

[0169] 3. The AMF network element sends the UE policy delivery to the UE;

[0170] 4. The UE feeds back the UE policy delivery result to the AMF network element;

[0171] 5. The AMF network element sends a Namf_Communication_N1 message notification to the PCF network element.

[0172] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0173] Figure 3 This is one of the flow charts of the method for changing the shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 3 As shown, an embodiment of the present application provides a method for changing terminal shared subscription data of a dual-boot device, the execution subject of which may be a first network function entity, for example, a unified data management (UDM) network element or a PCF network element, and the method includes:

[0174] Step 310: Detect the association relationship between the first terminal and the second terminal.

[0175] Step 320: When the shared subscription data of the first terminal changes, a first notification message is sent to the second network function entity based on the association relationship;

[0176] Among them, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0177] Specifically, for a DualSteer device, when the shared subscription data of one terminal changes, the shared subscription data of the other terminal also needs to be changed.

[0178] The first network function entity detects an association relationship between the first terminal and the second terminal according to the subscription information of the first terminal and the subscription information of the second terminal.

[0179] If there is an association relationship between the first terminal and the second terminal, for example, the first terminal and the second terminal belong to the same DualSteer device, then after the shared subscription data of the first terminal changes, the first network function entity sends a first notification message to the second network function entity, and the first notification message is used to change the shared subscription data of the second terminal.

[0180] The first notification message is used to notify a first terminal of a change in shared subscription information, and the first notification message includes the changed shared subscription data of the first terminal. Alternatively, the first notification message is used to notify a second terminal of a change in shared subscription information, and the first notification message includes the changed shared subscription data of the second terminal. The first notification message is determined based on the association relationship between the first terminal and the second terminal. The notification content of the first notification message varies for different association relationships.

[0181] An embodiment of the present application provides a method for changing shared subscription data of terminals in a dual-boot device. The first network function entity detects the association relationship between the first terminal and the second terminal. When the shared subscription data of the first terminal changes, the first network function entity sends a first notification message to the second network function entity based on the association relationship. The first notification message is used to notify the first terminal that the shared subscription information has changed. The first notification message includes the changed shared subscription data of the first terminal. Alternatively, the first notification message is used to notify the second terminal that the shared subscription information has changed. The first notification message includes the changed shared subscription data of the second terminal, so that the second network function entity changes the shared subscription data of the second terminal based on the first notification message, thereby achieving the change of the shared subscription data of another terminal in the DualSteer device when the shared subscription data of one terminal in the DualSteer device changes.

[0182] In some embodiments, the shared subscription data includes at least one of: AM subscription data, SM subscription data, and policy data.

[0183] Specifically, the AM subscription data may be a network slice (Single Network Slice Selection Assistance Information, S-NSSAI) and a service area (service area), etc. When the shared subscription data is AM subscription data, the first network function entity may be a UDM network element, and the second network function entity may be an AMF network element.

[0184] The SM subscription data may include a data network name (DNN) and quality of service (QoS), etc. When the shared subscription data is SM subscription data, the first network function entity may be a UDM network element, and the second network function entity may be a session management function (SMF) network element.

[0185] In the case where the shared subscription data is policy data, the first network function entity may be a PCF network element, and the second network function entity may be an AMF network element.

[0186] In some embodiments, the association relationship includes at least one of the following:

[0187] The first terminal and the second terminal belong to the same dual-boot device;

[0188] The first terminal and the second terminal are registered on the same network element;

[0189] The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

[0190] In some embodiments, the association relationship includes at least one of the following:

[0191] The first terminal and the second terminal belong to the same dual-boot device, or the first terminal and the second terminal do not belong to the same dual-boot device;

[0192] The first terminal and the second terminal are registered on the same network element, or the first terminal and the second terminal are not registered on the same network element;

[0193] The PDU sessions of the first terminal and the second terminal are anchored on the same network element, or the PDU sessions of the first terminal and the second terminal are not anchored on the same network element (ie, anchored on different network elements).

[0194] Specifically, the first network function entity first needs to detect whether the first terminal and the second terminal belong to the same DualSteer device. If the shared subscription data is AM subscription data or policy data, the first network function entity also needs to detect whether the first terminal and the second terminal are registered on the same AMF network element; if the shared subscription data is SM subscription data, the first network function entity also needs to detect whether the PDU sessions of the first terminal and the second terminal are anchored on the same SMF network element.

[0195] In some embodiments, when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or,

[0196] In a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or in a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or

[0197] When the association relationship between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

[0198] Specifically, if it is detected that the first terminal and the second terminal belong to the same DualSteer device, then when the shared subscription data of the first terminal is changed, the shared subscription data of the second terminal needs to be changed.

[0199] In the case where the first terminal and the second terminal belong to the same DualSteer device, regardless of whether the first terminal and the second terminal are registered on the same AMF network element and whether the PDU session of the first terminal and the second terminal is anchored on the same SMF network element, after the shared subscription data of the first terminal changes, the first network function entity can simultaneously trigger the subscription information change process for the first terminal and the second terminal, that is, the first network function entity sends a notification message of the change of the shared subscription information of the first terminal to the second network function entity to which the first terminal belongs, and sends a notification message of the change of the shared subscription information of the second terminal to the second network function entity to which the second terminal belongs, and then the second network function entity to which the first terminal belongs sends a request message for changing the shared subscription data to the first terminal to change the shared subscription data of the first terminal, and the second network function entity to which the second terminal belongs sends a request message for changing the shared subscription data to the second terminal to change the shared subscription data of the second terminal.

[0200] When the first terminal and the second terminal belong to the same DualSteer device, when the shared subscription data is AM subscription data or policy data, if it is also detected that the first terminal and the second terminal are registered on the same AMF network element; or when the shared subscription data is SM subscription data, if it is also detected that the PDU sessions of the first terminal and the second terminal are anchored on the same SMF network element, in order to save signaling resources, the first network function entity may only send a notification message of a change in the shared subscription information of the first terminal to the second network function entity, and then the second network function entity sends a request message for changing the shared subscription data to the first terminal and the second terminal respectively, so as to change the shared subscription data of the first terminal and the shared subscription data of the second terminal.

[0201] If the first network function entity cannot detect the association relationship between the first terminal and the second terminal, that is, it does not know whether the first terminal and the second terminal belong to the same DualSteer device, or the first network function entity does not support the DualSteer function, after the shared subscription data of the first terminal changes, the first network function entity can only send a notification message of the change of the shared subscription information of the first terminal to the second network function entity to which the first terminal belongs, and the second network function entity also only sends a request message for changing the shared subscription data to the first terminal.

[0202] Since the first terminal and the second terminal belong to the same DualSteer device, the first terminal and the second terminal can communicate directly. After receiving the request message for changing the shared subscription data sent by the second network function entity, the first terminal can send a notification message of the shared subscription data change to the second terminal to notify the second terminal to change the shared subscription data.

[0203] Figure 4 This is a second flow chart of a method for changing shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 4 As shown, the present application provides a method for changing terminal shared subscription data of a dual-boot device, the execution subject of which may be a second network function entity, such as an AMF network element / SMF network element, and the method includes:

[0204] Step 410, receiving a first notification message sent by the first network function entity; the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0205] Step 420: Based on the first notification message, change the shared subscription data of the second terminal.

[0206] Specifically, for a DualSteer device, when the shared subscription data of one terminal changes, the shared subscription data of the other terminal also needs to be changed.

[0207] The second network function entity receives a first notification message sent by the first network function entity. The first notification message is used to notify the first terminal of a change in shared subscription information, and the first notification message includes the changed shared subscription data of the first terminal. Alternatively, the first notification message is used to notify the second terminal of a change in shared subscription information, and the first notification message includes the changed shared subscription data of the second terminal. The first notification message is determined based on the association relationship between the first terminal and the second terminal. For different association relationships, the notification content of the first notification message sent by the first network function entity is also different.

[0208] If the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, the second network function entity can directly send a request message for changing the shared subscription data to the second terminal to change the shared subscription data of the second terminal; if the first notification message is used to notify the first terminal that the shared subscription information of the first terminal has changed, and the first notification message includes the changed shared subscription data of the first terminal, the second network function entity can change the shared subscription data of the second terminal through the premise that the first terminal and the second terminal belong to the same DualSteer device, or through the first terminal.

[0209] In a method for changing shared subscription data of terminals in a dual-boot device provided in an embodiment of the present application, a second network function entity receives a first notification message sent by a first network function entity; the first notification message is used to notify the first terminal that the shared subscription information has changed, and includes the changed shared subscription data of the first terminal, or the first notification message is used to notify the second terminal that the shared subscription information has changed, and includes the changed shared subscription data of the second terminal. Based on the first notification message, the shared subscription data of the second terminal is changed, so that when the shared subscription data of one terminal in the DualSteer device is changed, the shared subscription data of another terminal in the DualSteer device is changed.

[0210] In some embodiments, the shared subscription data includes at least one of: AM subscription data, SM subscription data, and policy data.

[0211] Specifically, the AM subscription data may be a network slice (Single Network Slice Selection Assistance Information, S-NSSAI) and a service area (service area), etc. When the shared subscription data is AM subscription data, the first network function entity may be a unified data management (UDM) network element, and the second network function entity may be an AMF network element.

[0212] The SM subscription data may include a data network name (DNN) and quality of service (QoS), etc. When the shared subscription data is SM subscription data, the first network function entity may be a UDM network element, and the second network function entity may be a session management function (SMF) network element.

[0213] In the case where the shared subscription data is policy data, the first network function entity may be a PCF network element, and the second network function entity may be an AMF network element.

[0214] In some embodiments, based on the first notification message, changing the shared subscription data of the second terminal includes:

[0215] When the first notification message is used to notify the second terminal that the shared contract information has changed, and the first notification message includes the changed shared contract data of the second terminal, a first request message for requesting to change the shared contract information is sent to the second terminal, and the first request message includes the changed shared contract data of the second terminal.

[0216] Specifically, the first request message may be a configuration update (UE configuration update command) request message, an N1 SM message, or a request message for changing policy subscription information.

[0217] For example, the AMF network element to which UE2 belongs is AMF2. If the shared contract data is AM contract data, when AMF2 receives a notification message sent by the UDM network element to notify UE2 that the AM contract information has changed, and the notification message contains the changed AM contract data of UE2, the AMF2 network element sends a configuration update request message to UE2. The configuration update request message contains the contract information that UE2 needs to change, that is, it contains the changed AM contract data of UE2.

[0218] For example, the SMF network element to which UE2 belongs is SMF2. If the shared contract data is SM contract data, when SMF2 receives a notification message sent by the UDM network element to notify UE2 that the SM contract information has changed, and the notification message contains the changed SM contract data of UE2, SMF2 sends an N1 SM message to UE2. The N1 SM message contains the contract information that needs to be changed for UE2, that is, it contains the changed SM contract data of UE2.

[0219] For example, the AMF network element to which UE2 belongs is AMF2. If the shared subscription data is policy data, when AMF2 receives a notification message sent by the PCF network element to notify UE2 that the policy subscription information has changed, and the notification message contains the changed policy data of UE2, the AMF2 network element sends a request message for changing the policy subscription information to UE2. The request message for changing the policy subscription information contains the policy subscription information that UE2 needs to change, that is, it contains the changed policy data of UE2.

[0220] In the method for changing the shared contract data of terminals of a dual-boot device provided in an embodiment of the present application, when a first notification message is used to notify a second terminal that the shared contract information has changed, and the first notification message includes the changed shared contract data of the second terminal, a first request message for requesting a change in the shared contract information is sent to the second terminal, and the first request message includes the changed shared contract data of the second terminal, thereby realizing a change in the shared contract data of the second terminal.

[0221] In some embodiments, based on the first notification message, changing the shared subscription data of the second terminal includes:

[0222] When the first notification message is used to notify the first terminal that the shared subscription information of the first terminal has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0223] When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal;

[0224] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0225] Specifically, when the first notification message is used to notify the first terminal of a change in the shared subscription information of the first terminal, and the first notification message includes the changed shared subscription data of the first terminal, the second network function entity detects whether the first terminal and the second terminal belong to the same DualSteer device based on the shared subscription data of the first terminal and the second terminal. The shared subscription data of the first terminal and the second terminal is obtained by the second network function entity from the first network function entity.

[0226] When it is detected that the first terminal and the second terminal belong to the same DualSteer device, the second network function entity confirms that the shared subscription data of the second terminal also needs to be changed, and sends request messages for changing the shared subscription data to the first terminal and the second terminal respectively to change the shared subscription data of the first terminal and the shared subscription data of the second terminal, that is, the second network function entity sends a first request message for requesting a change of shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal, and sends a second request message for requesting a change of shared subscription information to the first terminal, the second request message including the changed shared subscription data of the first terminal.

[0227] The changed shared subscription data of the second terminal is determined by the second network function entity based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0228] For example, if the shared subscription data is AM subscription data, when the AMF network element receives a notification message sent by the UDM network element to notify UE1 that the AM subscription information has changed, and the notification message contains the changed AM subscription data of UE1, the AMF network element detects that UE1 and UE2 belong to the same DualSteer device, then the AMF network element sends configuration update request messages to UE1 and UE2 respectively.

[0229] For example, if the shared subscription data is SM subscription data, when the SMF network element receives the notification message sent by the UDM network element to notify UE1 that the SM subscription information has changed, and the notification message contains the changed SM subscription data of UE1, the SMF network element detects that UE1 and UE2 belong to the same DualSteer device, then the SMF network element sends N1SM messages to UE1 and UE2 respectively.

[0230] For example, if the shared subscription data is policy data, when the AMF network element receives a notification message sent by the PCF network element to notify UE1 that the policy subscription information has changed, and the notification message contains the changed policy data of UE1, the AMF network element detects that UE1 and UE2 belong to the same DualSteer device, then the AMF network element sends a request message for changing the policy subscription information to UE1 and UE2 respectively.

[0231] In a method for changing shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application, a first notification message is used to notify a first terminal of a change in shared contract information. When it is detected that the first terminal and the second terminal belong to the same dual-boot device, a first request message for requesting a change in shared contract information is sent to the second terminal. The first request message includes the changed shared contract data of the second terminal, thereby realizing a change in the shared contract data of the second terminal.

[0232] In some embodiments, based on the first notification message, changing the shared subscription data of the second terminal includes:

[0233] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0234] If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in the shared subscription information, the second request message including the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, the second notification message is used to notify the second terminal of the change in the shared subscription information, and the second notification message includes the changed shared subscription data of the second terminal;

[0235] The shared subscription data of the second terminal after the change is determined based on the shared subscription data of the first terminal and the second terminal, and the shared subscription data of the first terminal after the change.

[0236] Specifically, when the first notification message is used to notify the first terminal of a change in the shared subscription information of the first terminal, and the first notification message includes the changed shared subscription data of the first terminal, the second network function entity detects whether the first terminal and the second terminal belong to the same DualSteer device based on the shared subscription data of the first terminal and the second terminal. The shared subscription data of the first terminal and the second terminal is obtained by the second network function entity from the first network function entity.

[0237] When it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the DualSteer function, the second network function entity can only send a second request message to the first terminal to request a change in the shared subscription information based on the notification content of the first notification message. The second request message includes the changed shared subscription data of the first terminal.

[0238] Because the first terminal and the second terminal belong to the same DualSteer device, they can communicate directly. After receiving the second request message, the first terminal triggers the first terminal to send a second notification message to the second terminal. The second notification message is used to notify the second terminal of the change in shared subscription information. The second notification message contains the changed shared subscription data of the second terminal. The second terminal can change the shared subscription data based on the second notification message.

[0239] The changed shared subscription data of the second terminal is determined by the first terminal based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0240] For example, if the shared subscription data is AM subscription data, when the AMF network element receives a notification message sent by the UDM network element to notify UE1 that the AM subscription information has changed, and the notification message contains the changed AM subscription data of UE1, the AMF network element cannot detect whether UE1 and UE2 belong to the same DualSteer device or do not support the DualSteer function. Then the AMF network element sends a configuration update request message to UE1, and the configuration update request message triggers UE1 to send a notification message to UE2, and the notification message contains the subscription information that UE2 needs to change.

[0241] For example, if the shared subscription data is SM subscription data, when the SMF network element receives a notification message sent by the UDM network element to notify UE1 that the SM subscription information has changed, and the notification message contains the changed SM subscription data of UE1, the SMF network element cannot detect whether UE1 and UE2 belong to the same DualSteer device or do not support the DualSteer function. Then the SMF network element sends an N1 SM message to UE1, and the N1 SM message triggers UE1 to send a notification message to UE2, and the notification message contains the subscription information that needs to be changed for UE2.

[0242] For example, if the shared subscription data is policy data, when the AMF network element receives a notification message sent by the PCF network element to notify UE1 that the policy subscription information has changed, and the notification message contains the changed policy data of UE1, the AMF network element cannot detect whether UE1 and UE2 belong to the same DualSteer device or do not support the DualSteer function. The AMF network element sends a request message to UE1 to change the policy subscription information. The request message to change the policy subscription information triggers UE1 to send a notification message to UE2, and the notification message contains the subscription information that UE2 needs to change.

[0243] In a method for changing shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application, a first notification message is used to notify the first terminal that the shared contract information has changed. When it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, a second request message for requesting a change in the shared contract information is sent to the first terminal. The second request message includes the changed shared contract data of the first terminal. The second request message is used to trigger the first terminal to send a second notification message to the second terminal. The second notification message is used to notify the second terminal that the shared contract information has changed. The second notification message includes the changed shared contract data of the second terminal, thereby realizing the change of the shared contract data of the second terminal.

[0244] In some embodiments, the method for changing shared subscription data of a terminal of a dual-boot device provided in an embodiment of the present application further includes:

[0245] When the shared subscription data of the second terminal is changed and affects the existing PDU session of the second terminal, send a PDU session release request or a PDU session update request to the third network function entity, or trigger a PDU session release request or a PDU session update request;

[0246] Among them, the PDU session release request is used to request deletion of the session related to the shared subscription data of the second terminal; the PDU session update request is used to request update of the PDU session of the second terminal.

[0247] Specifically, for example, if the shared subscription data is AM subscription data, when the change of AM subscription data affects the existing PDU session of UE2, the AMF network element sends a PDU session release request to the SMF network element to request deletion of the session related to UE2's AM subscription data; or the AMF network element sends a PDU session update request to the SMF network element to avoid the change of AM subscription data affecting the PDU session of UE2.

[0248] For example, if the shared subscription data is SM subscription data, when the change of SM subscription data affects the existing PDU session of UE2, the SMF network element triggers a PDU session release request to request deletion of the session related to UE2's SM subscription data; or the SMF network element triggers a PDU session update request to avoid the change of SM subscription data affecting the PDU session of UE2.

[0249] For example, if the shared contract data is policy data, and the change in policy data affects UE2's existing PDU session, the AMF network element sends a PDU session release request to the SMF network element. The PDU session release request is used to request deletion of the session related to UE2's policy data; or the AMF network element sends a PDU session update request to the SMF network element to avoid the change in policy data affecting UE2's PDU session.

[0250] In some embodiments, the method for changing shared subscription data of a terminal of a dual-boot device provided in an embodiment of the present application further includes:

[0251] When the second terminal has no PDU session online, an AN release request is sent to the fourth network function entity; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

[0252] Specifically, for example, when UE2 does not have any PDU session online, the AMF network element to which UE2 belongs sends an AN release request to the RAN network element to request deletion of the connection between the RAN network element and UE2, and / or trigger UE2 to re-register.

[0253] The following is a further description of the method for changing terminal shared subscription data of a dual-boot device provided by this application with several specific embodiments.

[0254] Example 1: Shared AM subscription data changes, UDM network element triggers two UE configuration updates

[0255] The prerequisites for this embodiment are: UE1 and UE2 both belong to a DualSteer device, and their subscription data is defined in UDM1 of the HPLMN. UE1 and UE2 share some AM subscription data, such as S-NSSAI and service area. RAN1, RAN2, AMF1, AMF2, SMF1, UPF1, and UDM1 all belong to the HPLMN. Assuming UE1 and UE2 are registered in the HPLMN and have established PDU sessions, UE1 is registered with AMF1 through RAN1, and UE2 is registered with AMF2 through RAN2. Both UE sessions are anchored to SMF1 / UPF1.

[0256] This embodiment assumes that UE1 and UE2 share subscription data (such as S-NSSAI). When only the S-NSSAI data of UE1 is changed, UDM1 triggers subscription information change requests for UE1 and UE2 respectively.

[0257] Figure 5 This is a flow chart of the third method for changing the shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 5 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0258] Step 1: Based on the subscription information, UDM1 determines that UE1 and UE2 belong to the same DualSteer device and are registered with different AMFs. When UE1's AM subscription data is changed, UDM1 triggers the UE1 subscription change process. Specifically, UDM1 sends a UE1 subscription change notification message (including the changed AM subscription data, such as S-NSSAI) to AMF1, to which UE1 belongs.

[0259] Step 2: AMF1 sends a UE configuration update command request message to UE1. The request message contains the subscription information that needs to be updated, whether the UE needs to reply with a confirmation message, and whether the UE needs to re-register immediately.

[0260] Step 3: UE1 sends a UE configuration update complete message to AMF1 to confirm the updated subscription information.

[0261] Step 4: If the changed S-NSSAI affects UE1's existing PDU session, AMF1 sends a PDU session release request to SMF1, requesting SMF1 to delete the session related to UE1's S-NSSAI.

[0262] Step 5: If UE1 does not have any PDU session online, AMF1 sends an AN release request to RAN1 to delete the connection between RAN1 and UE1. UE1 re-initiates registration according to the instructions of AMF1 in step 2.

[0263] Step 6: When UE1's AM subscription data changes, UDM1 also triggers UE2's subscription information change process, that is, UDM1 sends a UE2 subscription information change notification (including the changed AM subscription data, such as S-NSSAI) to AMF2 to which UE2 belongs.

[0264] Step 7: AMF2 sends a UE configuration update command request message to UE2. The request message contains the subscription information that needs to be updated, whether the UE needs to reply with a confirmation message, and whether the UE needs to re-register immediately.

[0265] Step 8: UE2 sends a UE configuration update complete message to AMF2 to confirm the updated subscription information.

[0266] Step 9: If the changed S-NSSAI affects UE2's existing PDU session, AMF2 sends a PDU session release request to SMF1, requesting SMF1 to delete the session related to UE2 S-NSSAI.

[0267] Step 10: If UE2 does not have any PDU session online, AMF2 sends an AN release request to RAN2 to delete the connection between RAN2 and UE2. UE2 re-initiates registration according to the instructions of AMF2 in step 7.

[0268] Example 2: Shared AM subscription data change, AMF triggers two UE configuration updates

[0269] The prerequisites of this embodiment are the same as those of implementation 1, except that in this implementation, UE1 and UE2 are both registered with the same AMF1.

[0270] This embodiment assumes that UE1 and UE2 share subscription data (such as S-NSSAI). When only the S-NSSAI data of UE1 is changed, UDM only triggers the information change request of UE1, but AMF1 triggers the information change process of UE1 and UE2 at the same time.

[0271] Figure 6 This is a fourth flow chart of a method for changing shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 6 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0272] Step 1: UDM1 determines that UE1 and UE2 belong to the same DualSteer device based on their subscription information, and that both UE1 and UE2 are registered with the same AMF. When UE1's AM subscription data is changed, UDM1 triggers the UE1 subscription information change process. Specifically, UDM1 sends a UE1 subscription information change notification message (including the changed AM subscription data, such as S-NSSAI) to the AMF1 to which UE1 belongs.

[0273] Step 2a: AMF1 sends a UE configuration update command request message to UE1. The request message contains the subscription information that needs to be updated, whether the UE needs to reply with a confirmation message, and whether the UE needs to re-register immediately.

[0274] Step 2b: AMF1 sends a UE configuration update command request message to UE2. The request message contains the subscription information that needs to be updated, whether the UE needs to reply with a confirmation message, and whether the UE needs to re-register immediately.

[0275] Step 3a: UE1 sends a UE configuration update complete message to AMF1 to confirm the updated subscription information.

[0276] Step 3b: UE2 sends a UE configuration update complete message to AMF1 to confirm the updated subscription information.

[0277] Step 4: If the changed S-NSSAI affects the existing PDU sessions of UE1 and UE2, AMF1 sends PDU session release requests for UE1 and UE2 to SMF1 respectively, requesting SMF1 to delete the sessions related to UE1 and UE2 S-NSSAI.

[0278] Step 5a: If UE1 does not have any PDU session online, AMF1 sends an AN release request to RAN1 to delete the connection between RAN1 and UE1. UE1 re-initiates registration according to the instructions in step 2a.

[0279] Step 5b: If UE2 does not have any PDU session online, AMF1 sends an AN release request to RAN2 to delete the connection between RAN2 and UE2. UE2 re-initiates registration according to the instructions in step 2b.

[0280] Example 3: Shared AM subscription data changes, UE triggers another UE configuration update

[0281] The prerequisites of this embodiment are the same as those of the second embodiment.

[0282] This embodiment assumes that UE1 and UE2 share AM subscription data (such as S-NSSAI). The difference is that when only the S-NSSAI data of UE1 is changed, UDM will only trigger an information change request for UE1, and AMF1 will only trigger an information change request for UE1. UE1 forwards the shared AM subscription data changes to UE2 through internal implementation.

[0283] Figure 7 This is a flowchart of the fifth method for changing the shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 7 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0284] Step 1: If UDM1 or AMF1 cannot determine whether UE1 and UE2 belong to the same DualSteer device based on the subscription information, or does not support the DualSteer function, when UE1's AM subscription data is changed, UDM1 triggers UE1's subscription information change process, that is, UDM1 sends a notification message of UE1's subscription information change (including the changed AM subscription data, such as S-NSSAI) to AMF1 to which UE1 belongs.

[0285] Step 2: AMF1 sends a UE configuration update command request message to UE1. The request message contains the subscription information that needs to be updated, whether the UE needs to reply with a confirmation message, and whether the UE needs to re-register immediately.

[0286] Step 3: UE1 sends a UE configuration update complete message to confirm the updated subscription information.

[0287] Step 4: If the changed S-NSSAI affects UE1's existing PDU session, AMF1 sends PDU session release requests for UE1 and UE2 to SMF1 respectively, requesting SMF1 to delete the sessions related to UE1 S-NSSAI and UE2 S-NSSAI.

[0288] Step 5: UE1 notifies UE2 of the change in shared subscription data through internal implementation.

[0289] Step 6: If UE1 does not have any PDU session online, AMF1 sends AN release to RAN1 to delete the connection between RAN1 and UE1. UE1 re-initiates registration according to the instructions in step 2.

[0290] Step 7: If UE2 believes that the changed AM subscription data needs to trigger re-registration, it initiates a mobility registration update request, carrying the changed subscription data; the registration trigger time and conditions depend on the UE implementation.

[0291] Example 4: Shared SM subscription data changes, UDM triggers two UE configuration updates

[0292] The prerequisites of this embodiment are the same as those of implementation one, except that the two UE PDU sessions are anchored on different SMFs.

[0293] In this embodiment, UE1 and UE2 share some SM subscription data, such as DNN, QoS, etc. When only the DNN data of UE1 is changed, the UDM will trigger subscription information change requests for UE1 and UE2 respectively.

[0294] Figure 8 This is a flowchart of the sixth method for changing shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 8 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0295] Step 0: UE1's SM subscription information (such as DNN, QoS) changes on UDM1.

[0296] In steps 1a-1b, UDM1 determines that UE1 and UE2 belong to the same DualSteer device based on their subscription information and discovers that their PDU sessions are anchored on different SMFs. When UE1's SM subscription data is changed, UDM1 triggers the subscription information change process for both UE1 and UE2. Specifically, UDM1 sends a subscription information change notification message (including the changed SM subscription data, such as DNN and QoS) to SMF1 and SMF2, respectively.

[0297] Step 2a: SMF1 sends an N1 SM message to UE1, which includes the SM subscription information that needs to be updated and whether the UE needs to reply with a confirmation message.

[0298] Step 2b: SMF2 sends an N1 SM message to UE2, which contains the SM subscription information that needs to be updated and whether the UE needs to reply with a confirmation message;

[0299] Step 3a: UE1 sends an N1 SM response message to SMF1 to confirm the updated subscription information.

[0300] Step 3b: UE2 sends an N1 SM response message to SMF2 to confirm the updated subscription information.

[0301] Step 4: If the changed DNN / QoS affects the existing PDU sessions of UE1 and UE2, SMF1 and SMF2 trigger a release request or a PDU session update request for UE1 and UE2 respectively.

[0302] Step 5a: SMF1 notifies AMF1 of the result of UE1 PDU session release / update.

[0303] Step 5b: SMF2 notifies AMF2 of the result of UE2 PDU session release / update.

[0304] Step 6a: If UE1 does not have any PDU session online, AMF1 sends an AN release request to RAN1 to delete the connection between RAN1 and UE1. UE1 re-initiates registration according to the instructions in step 2a.

[0305] Step 6b: If UE2 does not have any PDU session online, AMF2 sends an AN release request to RAN2 to delete the connection between RAN2 and UE2. UE2 re-initiates registration according to the instructions in step 2b.

[0306] Example 5: Shared SM subscription data change, SMF triggers two UE configuration updates

[0307] The prerequisites in this embodiment are the same as those in embodiment 1. The difference from embodiment 4 is that the PDU sessions of UE1 and UE2 are both anchored in the same SMF.

[0308] In this embodiment, UE1 and UE2 share some SM subscription data, such as DNN and QoS. When only UE1's DNN data is changed, the UDM triggers only the information change request for UE1. The SMF triggers the subscription change notification process for both UE1 and UE2.

[0309] Figure 9 This is a flowchart of the seventh method for changing the shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 9 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0310] Step 0: UE1's session subscription information (such as DNN, QoS) changes on UDM1.

[0311] Step 1: Based on the subscription information, UDM1 determines that UE1 and UE2 belong to the same DualSteer device and that the PDU sessions of both UEs are anchored to the same SMF. When UE1's SM subscription data is changed, UDM1 only triggers the subscription change process for UE1. That is, UDM1 only sends a notification message about UE1's subscription change (including the changed SM subscription data, such as DNN and QoS) to SMF1.

[0312] Step 2a: SMF1 sends an N1 SM message to UE1, which includes the SM subscription information that needs to be updated and whether the UE needs to reply with a confirmation message.

[0313] Step 2b: SMF1 sends an N1 SM message to UE2, which includes the SM subscription information that needs to be updated and whether the UE needs to reply with a confirmation message.

[0314] Step 3a: UE1 sends an N1 SM response message to SMF1 to confirm the updated subscription information.

[0315] Step 3b: UE2 sends an N1 SM response message to SMF1 to confirm the updated subscription information.

[0316] Step 4: If the changed DNN / QoS affects the existing PDU sessions of UE1 and UE2, SMF1 triggers a release request or an update of the PDU sessions for UE1 and UE2 respectively.

[0317] Step 5a: SMF1 notifies AMF1 of the result of UE1 PDU session release / update.

[0318] Step 5b: SMF1 notifies AMF2 of the result of UE2 PDU session release / update.

[0319] Step 6a: If UE1 does not have any PDU session online, AMF1 sends an AN release request to RAN1 to delete the connection between RAN1 and UE1. UE1 re-initiates registration according to the instructions in step 2a.

[0320] Step 6b: If UE2 does not have any PDU session online, AMF2 sends an AN release request to RAN2 to delete the connection between RAN2 and UE2. UE2 re-initiates registration according to the instructions in step 2b.

[0321] Example 6: Shared SM subscription data changes, UE triggers another UE configuration update

[0322] This is similar to Example 3. The difference is that this implementation changes the SM data. When only UE1's SM subscription data (such as DNN, QoS) is changed, UDM will only trigger an information change request for UE1, and SMF1 will also only trigger an information change request for UE1. UE1 will forward the shared SM subscription data changes to UE2 through internal implementation.

[0323] Figure 10 This is a flowchart of the eighth method for changing the shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 10 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0324] Step 1: If UDM1 or SMF1 cannot determine whether UE1 and UE2 belong to the same DualSteer device based on the subscription information or does not support the DualSteer function, when UE1's SM subscription data (such as DNN) is changed, UDM1 triggers UE1's subscription information change process. That is, UDM1 only sends UE1's subscription information change notification (including the changed SM subscription data, such as DNN) to SMF1.

[0325] Step 2: SMF1 sends an N1 SM message to UE1, which includes the SM subscription information that needs to be updated and whether the UE needs to reply with a confirmation message.

[0326] Step 3: UE1 sends an N1 SM response message to confirm the updated subscription information.

[0327] Step 4: UE1 notifies UE2 of the change in shared SM subscription data through internal implementation.

[0328] Step 5: If the changed DNN affects the existing PDU sessions of UE1 and UE2, SMF1 triggers a release request or an update request for the PDU sessions of UE1 and UE2 respectively.

[0329] Step 6a: SMF1 notifies AMF1 of the result of UE1 PDU session release or update.

[0330] Step 6b: SMF1 notifies AMF2 of the result of UE2 PDU session release or update.

[0331] Step 7a: If UE1 does not have any PDU session online, AMF1 sends an AN release request to RAN1 to delete the connection between RAN1 and UE1. UE1 re-initiates registration according to the instructions in step 2.

[0332] Step 7b: If UE2 does not have any PDU sessions online, AMF1 sends an AN release request to RAN2, deleting the connection between RAN2 and UE2. If UE2 believes that the changed SM subscription data requires re-registration, it initiates a mobility registration update request with the changed subscription data; the registration triggering time and conditions are specific to the UE implementation.

[0333] Step 8: UE2 may initiate a corresponding PDU session request based on the latest SM subscription data (such as DNN).

[0334] Example 7: Shared UE policy data changes, PCF triggers two UE configuration updates

[0335] In this embodiment, it is assumed that when the policy data shared by the two UEs in the DualSteer device is changed, if only the policy data of UE1 is changed, the PCF will synchronously trigger the policy data change process of UE2.

[0336] UE1 and UE2 have registered with AMF1 and AMF2 through RAN1 and RAN2 respectively. The policy subscription data of UE1 and UE2 are stored in PCF1 of HPLMN.

[0337] Figure 11 This is a ninth flow chart of a method for changing shared contract data of a terminal of a dual-boot device provided in an embodiment of the present application. Figure 11 As shown, the method for changing terminal shared subscription data of a dual-boot device provided in an embodiment of the present application includes the following steps:

[0338] Step 0: The UE1 policy data stored in PCF1 changes. PCF determines that UE1 and UE2 share some policy subscription data and are registered with different AMFs. When the shared policy data changes, PCF1 triggers a notification message to the AMF for both UE1 and UE2 about the information change.

[0339] Step 1a: PCF1 sends a notification message of UE1's policy subscription information change (including the changed policy subscription data) to AMF1 to which UE1 belongs.

[0340] Step 1b: PCF1 sends a notification message of UE2 policy subscription information change (including the changed policy subscription data) to AMF2 to which UE2 belongs.

[0341] Step 2a: AMF1 forwards the received changed policy subscription data of UE1 to UE1.

[0342] Step 2b: AMF2 forwards the received changed UE2 policy subscription data to UE2.

[0343] Step 3a: If UE1 accepts the change in subscription data, it responds to AMF1.

[0344] Step 3b: If UE2 accepts the change in subscription data, it responds to AMF2.

[0345] Step 4a: If the changed UE policy data requires UE1 to re-initiate registration or create a new PDU session, UE1 re-initiates registration or creates a new PDU session;

[0346] Step 4b: If the changed UE policy data requires UE2 to re-initiate registration or create a new PDU session, UE2 re-initiates registration or creates a new PDU session.

[0347] In fact, the network can also update the policy data of UE2 through AMF and UE itself respectively, which is similar to Embodiment 2 and Embodiment 3 and will not be repeated in this application.

[0348] Figure 12 This is a schematic diagram of the structure of the first network function entity provided in an embodiment of the present application. Figure 12 As shown, the first network function entity includes a memory 1220, a transceiver 1200, and a processor 1210, wherein:

[0349] The memory 1220 is used to store computer programs; the transceiver 1200 is used to send and receive data under the control of the processor 1210; the processor 1210 is used to read the computer program in the memory 1220 and perform the following operations:

[0350] detecting an association relationship between the first terminal and the second terminal;

[0351] When the shared subscription data of the first terminal changes, sending a first notification message to the second network function entity based on the association relationship;

[0352] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0353] Specifically, the transceiver 1200 is configured to receive and send data under the control of the processor 1210 .

[0354] Among them, Figure 12In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1210 and memory represented by memory 1220. The bus architecture may also link together 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 described further herein. The bus interface provides an interface. The transceiver 1200 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 when performing operations.

[0355] The processor 1210 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0356] In some embodiments, the association relationship includes at least one of the following:

[0357] The first terminal and the second terminal belong to the same dual-boot device;

[0358] The first terminal and the second terminal are registered on the same network element;

[0359] The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

[0360] In some embodiments, when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or

[0361] In a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or in a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or,

[0362] When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

[0363] In some embodiments, the shared subscription data includes at least one of the following:

[0364] AM contract data;

[0365] SM contract data;

[0366] Strategy data.

[0367] It should be noted that the first network function entity provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment in which the execution subject is the first network function entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0368] Figure 13 is a structural diagram of the second network function entity provided in an embodiment of the present application, such as Figure 13 As shown, the first network function entity includes a memory 1320, a transceiver 1300, and a processor 1310, wherein:

[0369] The memory 1320 is used to store computer programs; the transceiver 1300 is used to send and receive data under the control of the processor 1310; the processor 1310 is used to read the computer program in the memory 1320 and perform the following operations:

[0370] Receiving a first notification message sent by a first network function entity;

[0371] Based on the first notification message, change the shared subscription data of the second terminal;

[0372] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0373] Specifically, the transceiver 1300 is configured to receive and send data under the control of the processor 1310 .

[0374] Among them, Figure 13 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linked together by one or more processors represented by processor 1310 and memory represented by memory 1320. The bus architecture may also link together 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 described further herein. The bus interface provides an interface. The transceiver 1300 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 1310 is responsible for managing the bus architecture and general processing, and the memory 1320 may store data used by the processor 1310 when performing operations.

[0375] The processor 1310 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0376] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0377] When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

[0378] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0379] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0380] When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal;

[0381] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0382] In some embodiments, the changing the shared subscription data of the second terminal based on the first notification message includes:

[0383] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0384] If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal;

[0385] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0386] In some embodiments, the operations further include:

[0387] In a case where the shared subscription data of the second terminal is changed and affects the existing PDU session of the second terminal, sending a PDU session release request or a PDU session update request to the third network function entity, or triggering a PDU session release request or a PDU session update request;

[0388] The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

[0389] In some embodiments, the operations further include:

[0390] When the second terminal has no PDU session online, an AN release request is sent to the fourth network function entity; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

[0391] In some embodiments, the shared subscription data includes at least one of the following:

[0392] AM contract data;

[0393] SM contract data;

[0394] Strategy data.

[0395] It should be noted that the above-mentioned second network function entity provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment in which the execution subject is the second network function entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0396] Figure 14 This is one of the structural diagrams of the terminal shared contract data changing device of the dual-boot device provided in the embodiment of the present application, such as Figure 14 As shown, the embodiment of the present application also provides a terminal shared subscription data changing device for a dual-boot device, including a detection module 1410 and a sending module 1420; wherein:

[0397] A detection module 1410 is configured to detect an association relationship between a first terminal and a second terminal;

[0398] A sending module 1420 is configured to send a first notification message to a second network function entity based on the association relationship when the shared subscription data of the first terminal changes;

[0399] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0400] In some embodiments, the association relationship includes at least one of the following:

[0401] The first terminal and the second terminal belong to the same dual-boot device;

[0402] The first terminal and the second terminal are registered on the same network element;

[0403] The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

[0404] In some embodiments, when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or

[0405] In a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or in a case where the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or,

[0406] When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

[0407] In some embodiments, the shared subscription data includes at least one of the following:

[0408] AM contract data;

[0409] SM contract data;

[0410] Strategy data.

[0411] It should be noted here that the terminal shared contract data changing device of the dual-boot device provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiment in which the execution subject is the first network function entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0412] Figure 15 This is a second structural diagram of the terminal shared contract data changing device of the dual-boot device provided in the embodiment of the present application, such as Figure 15As shown, the embodiment of the present application also provides a terminal shared subscription data changing device for a dual-boot device, including a receiving module 1510 and a changing module 1520; wherein:

[0413] The receiving module 1510 is configured to receive a first notification message sent by a first network function entity;

[0414] A changing module 1520, configured to change the shared subscription data of the second terminal based on the first notification message;

[0415] In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

[0416] In some embodiments, the changing module 1520 is specifically configured to:

[0417] When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

[0418] In some embodiments, the changing module 1520 is specifically configured to:

[0419] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0420] When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal;

[0421] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0422] In some embodiments, the changing module 1520 is specifically configured to:

[0423] When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device;

[0424] If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal;

[0425] The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

[0426] In some embodiments, the apparatus further comprises:

[0427] A first processing module is configured to send a PDU session release request or a PDU session update request to a third network function entity, or trigger a PDU session release request or a PDU session update request, when the shared subscription data of the second terminal is changed and affects an existing PDU session of the second terminal;

[0428] The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

[0429] In some embodiments, the apparatus further comprises:

[0430] The second processing module is used to send an AN release request to the fourth network function entity when there is no PDU session online at the second terminal; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

[0431] In some embodiments, the shared subscription data includes at least one of the following:

[0432] AM contract data;

[0433] SM contract data;

[0434] Strategy data.

[0435] It should be noted here that the terminal shared contract data changing device of the dual-boot device provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment in which the above-mentioned execution subject is the second network function entity, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.

[0436] It should be noted that the division of units / modules in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0437] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0438] In some embodiments, a non-transitory readable storage medium is also provided, which stores a computer program, and the computer program is used to enable a processor to execute the terminal shared contract data change method of a dual-boot device provided by the above-mentioned method embodiments.

[0439] Specifically, the above-mentioned non-transitory readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0440] It should be noted that the non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.

[0441] In some embodiments, a processor-readable storage medium is also provided, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the terminal shared contract data changing method of the dual-boot device provided by the above-mentioned method embodiments.

[0442] Specifically, the processor-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiments in this embodiment will not be described in detail here.

[0443] In some embodiments, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the terminal shared contract data changing method of a dual-boot device provided by the above-mentioned method embodiments.

[0444] Specifically, the above-mentioned computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0445] In some embodiments, a communication device is further provided, in which a computer program is stored. The computer program is used to enable the communication device to execute the terminal shared subscription data changing method of the dual-boot device provided by the above-mentioned method embodiments.

[0446] Specifically, the above-mentioned communication equipment provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0447] In some embodiments, a chip product is further provided, in which a computer program is stored. The computer program is used to enable the chip product to execute the terminal shared subscription data changing method of the dual-boot device provided by the above-mentioned method embodiments.

[0448] It should also be noted that the terms "first," "second," and the like in the embodiments of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein. Furthermore, the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects. For example, the first object can be one or more.

[0449] In the embodiments of this application, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0450] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0451] In this application, "determine B based on A" means that factor A must be considered when determining B. This is not limited to "determine B based solely on A" and should also include: "determine B based on A and C", "determine B based on A, C, and E", "determine C based on A, and further determine B based on C", etc. It can also include using A as a condition for determining B, for example, "when A meets the first condition, use the first method to determine B"; another example, "when A meets the second condition, determine B"; another example, "when A meets the third condition, determine B based on the first parameter", etc. Of course, it can also be a condition that uses A as a factor in determining B, for example, "when A meets the first condition, use the first method to determine C, and further determine B based on C", etc.

[0452] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0453] The terminal device involved in the embodiments of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, or a user device, but is not limited in the embodiments of the present application.

[0454] The network device involved in the embodiments of the present application may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be named otherwise. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (eNB or e-NodeB) in the Long Term Evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., and is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0455] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO. It can also use diversity transmission, precoding transmission, or beamforming transmission.

[0456] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[0457] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0458] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce an article of manufacture comprising an instruction device that implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0459] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0460] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for changing shared contract data of a terminal of a dual-boot device, characterized in that: Applied to the first network function entity, including: detecting an association relationship between the first terminal and the second terminal; When the shared subscription data of the first terminal changes, sending a first notification message to the second network function entity based on the association relationship; In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

2. The method for changing shared contract data of a terminal of a dual-boot device according to claim 1, characterized in that: The association relationship includes at least one of the following: The first terminal and the second terminal belong to the same dual-boot device; the first terminal and the second terminal are registered on the same network element; The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

3. The method for changing shared contract data of a dual-boot device according to claim 2, wherein: When the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or, When the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or, When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

4. The method for changing terminal shared subscription data of a dual-boot device according to any one of claims 1 to 3, characterized in that: The shared subscription data includes at least one of the following: AM contract data; SM contract data; Strategy data.

5. A method for changing shared contract data of a terminal of a dual-boot device, characterized in that: Applicable to the second network function entity, including: Receiving a first notification message sent by a first network function entity; Based on the first notification message, change the shared subscription data of the second terminal; In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

6. The method for changing shared contract data of a terminal of a dual-boot device according to claim 5, characterized in that: The changing the shared subscription data of the second terminal based on the first notification message includes: When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

7. The method for changing shared contract data of a terminal of a dual-boot device according to claim 5, characterized in that: The changing the shared subscription data of the second terminal based on the first notification message includes: When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device; When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal; The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

8. The method for changing shared contract data of a terminal of a dual-boot device according to claim 5, wherein: The changing the shared subscription data of the second terminal based on the first notification message includes: When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device; If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal; The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

9. The method for changing terminal shared contract data of a dual-boot device according to any one of claims 5 to 8, characterized in that: The method further comprises: In a case where the shared subscription data of the second terminal is changed and affects the existing PDU session of the second terminal, sending a PDU session release request or a PDU session update request to the third network function entity, or triggering a PDU session release request or a PDU session update request; The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

10. The method for changing terminal shared subscription data of a dual-boot device according to any one of claims 5 to 8, characterized in that: The method further comprises: When the second terminal has no PDU session online, an AN release request is sent to the fourth network function entity; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

11. The method for changing terminal shared subscription data of a dual-boot device according to any one of claims 5 to 8, characterized in that: The shared subscription data includes at least one of the following: AM contract data; SM contract data; Strategy data.

12. A first network function entity, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: detecting an association relationship between the first terminal and the second terminal; When the shared subscription data of the first terminal changes, sending a first notification message to the second network function entity based on the association relationship; In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

13. The first network function entity according to claim 12, characterized in that: The association relationship includes at least one of the following: The first terminal and the second terminal belong to the same dual-boot device; The first terminal and the second terminal are registered on the same network element; The PDU sessions of the first terminal and the second terminal are anchored on the same network element.

14. The first network function entity according to claim 13, characterized in that: When the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, the first notification message is used to notify the second terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the second terminal; or, When the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the first terminal and the second terminal are registered on the same network element, or when the association relationship is that the first terminal and the second terminal belong to the same dual-boot device, and the PDU sessions of the first terminal and the second terminal are anchored on the same network element, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal; or, When the association between the first terminal and the second terminal cannot be detected, or the dual-boot function is not supported, the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal.

15. The first network function entity according to any one of claims 12 to 14, characterized in that: The shared subscription data includes at least one of the following: AM contract data; SM contract data; Strategy data.

16. A second network function entity, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving a first notification message sent by a first network function entity; Based on the first notification message, change the shared subscription data of the second terminal; In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

17. The second network function entity according to claim 16, characterized in that: The changing the shared subscription data of the second terminal based on the first notification message includes: When the first notification message is used to notify the second terminal that the shared subscription information of the second terminal has changed, and the first notification message includes the changed shared subscription data of the second terminal, a first request message for requesting to change the shared subscription information is sent to the second terminal, and the first request message includes the changed shared subscription data of the second terminal.

18. The second network function entity according to claim 16, characterized in that: The changing the shared subscription data of the second terminal based on the first notification message includes: When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device; When detecting that the first terminal and the second terminal belong to the same dual-boot device, sending a first request message for requesting a change in shared subscription information to the second terminal, the first request message including the changed shared subscription data of the second terminal; The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

19. The second network function entity according to claim 16, characterized in that: The changing the shared subscription data of the second terminal based on the first notification message includes: When the first notification message is used to notify the first terminal that the shared subscription information has changed, and the first notification message includes the changed shared subscription data of the first terminal, detecting whether the first terminal and the second terminal belong to the same dual-boot device; If it is impossible to detect whether the first terminal and the second terminal belong to the same dual-boot device or do not support the dual-boot function, sending a second request message to the first terminal for requesting a change in shared subscription information, where the second request message includes the changed shared subscription data of the first terminal; the second request message is used to trigger the first terminal to send a second notification message to the second terminal, where the second notification message is used to notify the second terminal of the change in shared subscription information, where the second notification message includes the changed shared subscription data of the second terminal; The changed shared subscription data of the second terminal is determined based on the shared subscription data of the first terminal and the second terminal, and the changed shared subscription data of the first terminal.

20. The second network function entity according to any one of claims 16 to 19, characterized in that: The operations further include: In a case where the shared subscription data of the second terminal is changed and affects the existing PDU session of the second terminal, sending a PDU session release request or a PDU session update request to the third network function entity, or triggering a PDU session release request or a PDU session update request; The PDU session release request is used to request deletion of a session related to the shared subscription data of the second terminal; and the PDU session update request is used to request update of the PDU session of the second terminal.

21. The second network function entity according to any one of claims 16 to 19, characterized in that: The operations further include: When the second terminal has no PDU session online, an AN release request is sent to the fourth network function entity; the AN release request is used to delete the connection between the fourth network function entity and the second terminal, and / or trigger the second terminal to re-register.

22. The second network function entity according to any one of claims 16 to 19, characterized in that: The shared subscription data includes at least one of the following: AM contract data; SM contract data; Strategy data.

23. A terminal shared contract data changing device for a dual-boot device, characterized in that: include: A detection module, configured to detect an association relationship between the first terminal and the second terminal; a sending module, configured to send a first notification message to the second network function entity based on the association relationship when the shared subscription data of the first terminal changes; In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

24. A terminal shared contract data changing device for a dual-boot device, characterized in that: include: A receiving module, configured to receive a first notification message sent by a first network function entity; a changing module, configured to change the shared subscription data of the second terminal based on the first notification message; In which, the first notification message is used to notify the first terminal that the shared contract information of the first terminal has changed, and the first notification message includes the changed shared contract data of the first terminal; or, the first notification message is used to notify the second terminal that the shared contract information of the second terminal has changed, and the first notification message includes the changed shared contract data of the second terminal.

25. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, which is used to enable the processor to execute the terminal shared contract data change method of a dual-boot device as described in any one of claims 1 to 4, or execute the terminal shared contract data change method of a dual-boot device as described in any one of claims 5 to 11.

Images