Full configuration method and apparatus for mr-dc, computer device and readable medium

Abstract

The present disclosure provides a full-quantity configuration method of MR-DC, the method is applied to a target MN-CU, and the method comprises the following steps: in response to determining that a target MN-DU completes full-quantity configuration, sending an indication message to a target SN, wherein the indication message is used to instruct the target SN to perform full-quantity configuration. After the target MN-DU completes full-quantity configuration, the target MN-CU instructs the target SN-CU to perform full-quantity configuration by using the indication message, so that the target SN-CU can instruct the target SN-DU to perform full-quantity configuration, and full-quantity configuration of the target SN can be realized. The present embodiment can make up for the deficiency of the standard protocol, support full-quantity configuration of the UE, the MN and the SN when the MR-DC network performs mobility switching, reduce the probability of packet loss or UE release in the service process, and improve the continuity of the service of the dual-connection user. The present disclosure further provides a full-quantity configuration device of MR-DC, a computer device and a readable medium.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and specifically to a full configuration method, apparatus, computer device, and readable medium for an MR-DC. Background Technology

[0002] In SA (Standalone) mobility scenarios, both gNB-CU (gNB Central Unit) and gNB-DU (gNB Distributed Unit) can trigger full configuration. If gNB-CU decides to trigger full configuration, it will notify gNB-DU via F1 interface; if gNB-CU does not decide to trigger full configuration, gNB-DU can also decide to trigger full configuration and notify gNB-CU via F1 interface, so that both UE (User Terminal) and gNB-CU can be notified to perform full configuration.

[0003] In MR-DC (Multi-Radio Dual Connectivity) mobility scenarios with SN handover, when the target MN (Master Node) -CU has not decided to perform full configuration, but the target MN-DU needs to perform full configuration, the target MN-DU informs the target MN-CU via the F1 interface that it needs to notify the UE, target MN-CU, and target SN to perform full configuration. However, there is currently no means to notify the target SN to perform full configuration. In this situation, if the mobility handover continues, the PDCP (Packet Data Convergence Protocol) sequence numbers of the UE and the target SN will be inconsistent, causing a sudden drop in traffic and affecting user traffic services. If the mobility handover fails, it will affect key indicators such as handover success rate, SN addition success rate, and UE call drop rate. Summary of the Invention

[0004] This disclosure provides a method, apparatus, computer device, and readable medium for full configuration of an MR-DC.

[0005] In a first aspect, embodiments of this disclosure provide a full configuration method for an MR-DC, the method being applied to a target master node central unit MN-CU, comprising:

[0006] In response to determining that the target master node distribution unit MN-DU has completed full configuration, an indication message is sent to the target auxiliary node central unit SN-CU, the indication message being used to instruct the target SN-CU to perform full configuration.

[0007] In some embodiments, sending an indication message to the target secondary node SN-CU includes: sending an indication message to the target SN-CU via the Xn interface.

[0008] In some embodiments, the indication message is a user-side Xn interface address indication message.

[0009] In a first aspect, embodiments of this disclosure also provide a method for full configuration of an MR-DC, the method being applied to a target secondary node central unit SN-CU, comprising:

[0010] Receive an indication message sent by the target master node central unit MN-CU, the indication message being used to instruct the target SN-CU to perform full configuration;

[0011] Perform full configuration.

[0012] In some embodiments, after performing a full configuration, the following is also included:

[0013] Send a user context modification request message to the target secondary node distribution unit (SN-DU), the user context modification request message being used to instruct the target SN-DU to perform full configuration;

[0014] Receive the user context modification response message sent by the target SN-DU, which is sent by the target SN-DU after completing full configuration.

[0015] In some embodiments, receiving the indication message sent by the target master node central unit MN-CU includes:

[0016] Receive the instruction message sent by the target MN-CU through the Xn interface.

[0017] In some embodiments, the indication message is a user-side Xn interface address indication message.

[0018] In another aspect, this disclosure also provides a full configuration device for MR-DC, the device being a target master node central unit MN-CU, including a determination module and a full configuration indication module, the determination module being used to determine whether the target master node distribution unit MN-DU has completed full configuration;

[0019] The full configuration instruction module is used to send an instruction message to the target auxiliary node central unit SN-CU in response to the determination module determining that the target master node distribution unit MN-DU has completed full configuration. The instruction message is used to instruct the target SN-CU to perform full configuration.

[0020] In another aspect, this disclosure also provides a full configuration device for MR-DC, the device being an auxiliary node central unit SN-CU, including a first receiving module and a full configuration module, the first receiving module being used to receive an indication message sent by a target master node central unit MN-CU, the indication message being used to instruct the target SN-CU to perform full configuration;

[0021] The full configuration module is used to perform full configuration.

[0022] In another aspect, embodiments of this disclosure also provide a computer device, including: one or more processors; a storage device having one or more programs stored thereon; and when the one or more programs are executed by the one or more processors, causing the one or more processors to implement the full configuration method of MR-DC as described above.

[0023] In another aspect, embodiments of this disclosure also provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed, it implements the full configuration method of MR-DC as described above.

[0024] The full configuration apparatus and method for MR-DC provided in this disclosure, applied to a target MN-CU, includes: in response to determining that the target MN-DU has completed full configuration, sending an indication message to a target SN, the indication message instructing the target SN to perform full configuration. In this disclosure, after the target MN-DU completes full configuration, the target MN-CU uses the indication message to instruct the target SN-CU to perform full configuration, so that the target SN-CU can instruct the target SN-DU to perform full configuration, thus achieving full configuration of the target SN. This disclosure supplements the deficiencies of standard protocols, supporting full configuration of the UE, MN, and SN during mobility handover in MR-DC networking, reducing the probability of packet loss or UE release during service operations, and improving the continuity of dual-connectivity user services. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of the MR-DC networking architecture;

[0026] Figure 2 This is a schematic diagram of the full configuration process of MR-DC with MN-CU as the execution subject provided in the embodiments of this disclosure;

[0027] Figure 3 A schematic diagram of the full configuration process of MR-DC with SN-CU as the execution subject provided in this embodiment of the disclosure. Figure 1 ;

[0028] Figure 4A schematic diagram of the full configuration process of MR-DC with SN-CU as the execution subject provided in this embodiment of the disclosure. Figure 2 ;

[0029] Figures 5-14 A schematic diagram of the full configuration process of MR-DC for 10 specific examples provided in the embodiments of this disclosure;

[0030] Figure 15 A schematic diagram of the structure of the MR-DC full configuration device (MN-CU) provided in the embodiments of this disclosure;

[0031] Figure 16 Schematic diagram of the MR-DC full configuration device (SN-CU) provided in the embodiments of this disclosure Figure 1 ;

[0032] Figure 17 Schematic diagram of the MR-DC full configuration device (SN-CU) provided in the embodiments of this disclosure Figure 2 . Detailed Implementation

[0033] Exemplary embodiments will be described more fully below with reference to the accompanying drawings; however, these exemplary embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will enable those skilled in the art to fully understand the scope of this disclosure.

[0034] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0035] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. As used herein, the singular forms “a” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the said feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded.

[0036] The embodiments described herein can be described with reference to plan views and / or cross-sectional views using the ideal schematic diagrams of this disclosure. Therefore, the example illustrations can be modified according to manufacturing techniques and / or tolerances. Therefore, the embodiments are not limited to those shown in the drawings, but include modifications to configurations formed based on manufacturing processes. Therefore, the areas illustrated in the drawings are schematic in nature, and the shapes of the areas shown in the figures illustrate specific shapes of areas of an element, but are not intended to be limiting.

[0037] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined herein.

[0038] like Figure 1 As shown, in the MR-DC dual-connectivity networking scenario, dual-connectivity technology fully utilizes the radio air interface resources of different stations (same standard, different standards) to improve user experience speed. A 5G UE can simultaneously connect to two base stations, MN and SN, to increase the throughput of a single user. MN and SN can be two NR base stations or two ng-eNB / NR base stations.

[0039] The MR-DC of the 5G core network includes the following three types: NE-DC (NR-E-UTRA Dual Connectivity, dual connectivity of 5G NR and 4G radio access network), NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity, dual connectivity of 4G radio access network and 5G NR under 5G core network), and NR-DC (NR-NR Dual Connectivity, dual connectivity of 5G NR and 5G NR). The embodiments disclosed herein can be applied to the above three MR-DC scenarios.

[0040] This disclosure provides a full configuration method for MR-DC, which is applied to mobility handover scenarios under MR-DC networking. The mobility handover scenarios described in this disclosure are all MN handover with SN handover scenarios, meaning that not only MN handover but also SN handover is required. In this disclosure, the source MN (including source MN-CU and source MN-DU) and source SN (including source SN-CU and source SN-DU) refer to the MN and SN before handover, and the target MN (including target MN-CU and target MN-DU) and target SN (including target SN-CU and target SN-DU) refer to the MN and SN after handover.

[0041] The MR-DC mobility handover in this disclosure embodiment can include the following types: MR-DC mobility Xn handover, MR-DC mobility Ng handover, MR-DC mobility intra-DU handover, MR-DC mobility inter-DU handover, MR-DC mobility inter-site conditional handover, and MR-DC mobility intra-site conditional handover. It should be noted that all six types of MR-DC mobility handover include cases where the source SN and target SN are the same or different. Specifically, MR-DC mobility Xn handover is an MN handover initiated by the source MN based on the Xn interface; MR-DC mobility Ng handover is an MN handover initiated by the source MN based on the Ng interface; MR-DC mobility intra-DU handover is an MN handover initiated by the MN-CU within the DU; MR-DC mobility inter-DU handover is an MN handover initiated by the MN-CU between DUs; MR-DC mobility inter-site conditional handover is an MN handover initiated by the source MN to multiple target base stations; and MR-DC mobility intra-site conditional handover is an intra-site handover initiated by the MN to multiple intra-site cells.

[0042] like Figure 2 As shown, the full configuration method of MR-DC provided in this embodiment of the present disclosure is applied to the target MN-CU, and includes the following steps:

[0043] Step 11: In response to determining that the target MN-DU has completed full configuration, an indication message is sent to the target SN-CU. The indication message is used to instruct the target SN-CU to perform full configuration.

[0044] In this step, after determining that the target MN-DU has completed full configuration, the target MN-CU sends an instruction message to the target SN-CU. Upon receiving this instruction message, the target SN-CU is able to perform full configuration. It should be noted that after completing full configuration, the target SN-CU also instructs the target SN-DU to perform full configuration.

[0045] Existing standard protocols do not define a method for the target MN-CU to instruct the target SN-CU to perform a full configuration, leading to a sudden drop in service traffic, affecting user traffic services or causing mobility handover failures. In this embodiment, after the target MN-DU completes its full configuration, the target MN-CU uses an instruction message to instruct the target SN-CU to perform a full configuration. This allows the target SN-CU to instruct the target SN-DU to perform a full configuration, enabling full configuration of the target SN. This addresses the shortcomings of standard protocols and supports full configuration for the UE, MN, and SN during mobility handover in MR-DC networking. This reduces the probability of packet loss or UE release during service operations and improves the continuity of dual-connectivity user services.

[0046] It should be noted that in MR-DC mobility scenarios, the UE also needs to perform a full configuration. Therefore, after the target SN completes its full configuration, the source MN sends RRC (Radio Resource Control Reconfiguration) information to the UE. This RRC reconfiguration information consists of the full configuration information of the target SN and the target MN, instructing the UE to perform a full configuration based on the full configuration information of the target SN and the target MN.

[0047] In some embodiments, sending an indication message to the target SN-CU includes the following steps: sending the indication message to the target SN-CU via the Xn interface, that is, in this step, the target MN-CU and the target SN-CU transmit the indication message through the Xn interface.

[0048] In some embodiments, the indication message is a user-side Xn interface address indication message. In this step, the target MN-CU sends an Xn-U ADDRESS INDICATION message to the target SN-CU to instruct the target SN-CU to perform a full configuration. The user-side Xn interface address indication message (Xn-U ADDRESS INDICATION) is a message defined by existing standard protocols. In this embodiment of the disclosure, a field can be added to the user-side Xn interface address indication message (Xn-U ADDRESS INDICATION) to instruct the target SN-CU to perform a full configuration, thereby enabling the message to have the function of instructing the target SN-CU to perform a full configuration.

[0049] This disclosure also provides a method for full configuration of an MR-DC, which is applied to a target SN-CU, such as... Figure 3 As shown, the method includes the following steps:

[0050] Step 21: Receive the indication message sent by the target MN-CU. The indication message is used to instruct the target SN-CU to perform full configuration.

[0051] In this step, the target SN-CU receives the indication message sent by the target MN-CU.

[0052] Step 22: Perform full configuration.

[0053] In this step, the target SN-CU performs a full configuration locally based on the instruction message.

[0054] After the target SN-CU has completed full configuration, a full configuration also needs to be performed on the target SN-DU. Therefore, in some embodiments, such as Figure 4As shown, after performing a full configuration (i.e., step 22), the full configuration method of the MR-DC further includes the following steps:

[0055] Step 31: Send a User Context Modification Request message to the target SN-DU. The User Context Modification Request message is used to instruct the target SN-DU to perform a full configuration.

[0056] In this step, after the target SN-CU completes the full configuration locally, it sends a UE CONTEXT MODIFICATION REQUEST message to the target SN-DU through the F1 interface to instruct the target SN-DU to perform the full configuration.

[0057] Step 32: Receive the user context modification response message sent by the target SN-DU. The user context modification response message is sent by the target SN-DU after completing the full configuration.

[0058] In this step, after the target SN-DU performs full configuration locally based on the UE CONTEXT MODIFICATION REQUEST message, it returns a UE CONTEXT MODIFICATION RESPONSE message to the target SN-CU through the F1 interface to notify the target SN-CU that the target SN-DU has completed full configuration.

[0059] After the target SN-CU and target SN-DU perform full configuration respectively, the full configuration of the target SN is completed.

[0060] In some embodiments, receiving the indication message sent by the target MN-CU (i.e., step 21) includes the following steps: receiving the indication message sent by the target MN-CU through the Xn interface. That is, in this step, the target MN-CU and the target SN-CU transmit the indication message through the Xn interface.

[0061] In some embodiments, the indication message is a user-side Xn interface address indication message. The target SN-CU receives the Xn-U ADDRESS INDICATION message sent by the target MN-CU so that the target SN-CU can perform a full configuration locally. The user-side Xn interface address indication message (Xn-U ADDRESS INDICATION) is a message defined by an existing standard protocol. In this embodiment of the disclosure, a field can be added to the user-side Xn interface address indication message (Xn-U ADDRESS INDICATION) to instruct the target SN-CU to perform a full configuration, thereby enabling the message to have the function of instructing the target SN-CU to perform a full configuration.

[0062] To clearly illustrate the solutions of the embodiments of this disclosure, the following descriptions are in conjunction with... Figure 5-14 This paper describes 10 MR-DC mobility handover scenarios.

[0063] Example 1: MR-DC Mobility Xn Handover (SN Change) Scenario

[0064] In this example, the UE accesses the network from the source MN, which switches to the target MN via the Xn interface. The target MN selects a different target SN than the source SN. Taking adding an SN to the target MN as an example, the process of the target MN, target SN, and UE performing a full configuration is illustrated. Figure 5 As shown, the specific implementation steps are as follows:

[0065] Step 1: In response to the UE accessing the source MN and having added the source SN, the source MN sends a handover request message (HANDOVER REQUEST) to the target MN-CU through the Xn interface to initiate MR-DC mobility Xn handover.

[0066] Step 2: The target MN-CU sends an SN addition request message (S-NODE ADDITIONREQUEST) to the target SN-CU, thereby initiating the SN addition process.

[0067] Step 3: The target SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITIONREQUEST ACKNOWLEDGE) to the target MN-CU.

[0068] Step 4: The target MN-CU sends a User Context Establishment Request message (UECONTEXT SETUP REQUEST) to the target MN-DU through the F1 interface to initiate the context establishment process.

[0069] Step 5: The target MN-DU performs full configuration and sends a UE CONTEXT SETUP RESPONSE message to the target MN-CU to notify the target MN-CU that the target MN-DU has completed full configuration.

[0070] Step 6: The target MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the target SN-CU to instruct the target SN-CU to perform full configuration.

[0071] Step 7: The target SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the target SN-DU to perform full configuration.

[0072] Step 8: The target SN-DU performs full configuration and replies with a UE CONTEXT MODIFICATION RESPONSE message to the target SN-CU via the F1 interface.

[0073] Step 9: The target SN-CU sends a notification message (NOTIFICATION) to the target MN-CU, which carries the first RRC reconfiguration information (RRCReconfiguration 1). The first RRC reconfiguration information is the full configuration information of the target SN.

[0074] Step 10: The target MN-CU sends a handover request confirmation message to the source MN.

[0075] Step 11: The source MN sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the target SN and the full configuration information of the target MN.

[0076] In the MR-DC mobility Xn handover (SN change) scenario, the source SN and the target SN are different. After the target MN-DU performs full configuration, the target MN-CU instructs the target SN-CU to perform full configuration through the Xn interface, and the target SN-CU instructs the target SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the target SN all perform full configuration, thereby improving the user experience.

[0077] Example 2, MR-DC Mobility Xn Handover Scenario (SN unchanged)

[0078] In this example, the UE accesses the network from the source MN, which switches to the target MN via the Xn interface, and the target SN selected by the target MN is the same as the source SN. Taking adding an SN to the target MN as an example, the process of the target MN, target SN, and UE performing a full configuration is illustrated below. Figure 6 As shown, the specific implementation steps are as follows:

[0079] Step 1: In response to the UE accessing the source MN and having added the SN, the source MN sends a handover request message (HANDOVER REQUEST) to the target MN-CU through the Xn interface to initiate MR-DC mobility Xn handover.

[0080] Step 2: The target MN-CU sends an SN addition request message (S-NODE ADDITION REQUEST) to the SN-CU, thereby initiating the SN addition process. In this example, the target MN selects the same target SN as the source SN, therefore the target SN-CU is the same as the source SN-CU (represented as SN-CU), and the target SN-DU is the same as the source SN-DU (represented as SN-DU).

[0081] Step 3: SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITION REQUESTACKNOWLEDGE) to the target MN-CU.

[0082] Step 4: The target MN-CU sends a User Context Establishment Request message (UECONTEXT SETUP REQUEST) to the target MN-DU through the F1 interface to initiate the context establishment process.

[0083] Step 5: The target MN-DU performs full configuration and sends a UE CONTEXT SETUP RESPONSE message to the target MN-CU to notify the target MN-CU that the target MN-DU has completed full configuration.

[0084] Step 6: The target MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the SN-CU to instruct the SN-CU to perform full configuration.

[0085] Step 7: The SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the SN-DU to perform full configuration.

[0086] Step 8: The SN-DU performs full configuration and replies with a User Context Modification Response (UE CONTEXT MODIFICATION RESPONSE) to the target SN-CU via the F1 interface.

[0087] Step 9: The SN-CU sends a notification message (NOTIFICATION) to the target MN-CU, which carries the first RRC reconfiguration information (RRC Reconfiguration1). The first RRC reconfiguration information is the full configuration information of the SN.

[0088] Step 10: The target MN-CU sends a handover request confirmation message to the source MN.

[0089] Step 11: The source MN sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the SN and the full configuration information of the target MN.

[0090] In the MR-DC mobility Xn handover (SN unchanged) scenario, the source SN and the target SN are the same. After the target MN-DU performs full configuration, the target MN-CU instructs the SN-CU to perform full configuration through the Xn interface, and the SN-CU instructs the SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the SN all perform full configuration, thereby improving the user experience.

[0091] Example 3: MR-DC Mobility Ng Handover (SN unchanged)

[0092] In this example, the UE accesses the network from the source MN, which switches to the target MN via the Ng interface, and the target SN selected by the target MN is the same as the source SN. Taking adding an SN to the target MN as an example, the process of the target MN, target SN, and UE performing a full configuration is illustrated. Figure 7 As shown, the specific implementation steps are as follows:

[0093] Step 1: In response to the UE accessing the source MN and having added the SN, the source MN sends a handover request message (HANDOVER REQUEST) to the AMF (Authentication Management Function) through the Ng interface to initiate MR-DC mobility Ng handover.

[0094] Step 2: The AMF forwards a handover request message to the target MN-CU.

[0095] Step 3: The target MN-CU sends an SN addition request message (S-NODE ADDITION REQUEST) to the SN-CU, thereby initiating the SN addition process. In this example, the target MN selects the same target SN as the source SN, therefore the target SN-CU is the same as the source SN-CU (represented as SN-CU), and the target SN-DU is the same as the source SN-DU (represented as SN-DU).

[0096] Step 4: The target SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITIONREQUEST ACKNOWLEDGE) to the target MN-CU.

[0097] Step 5: The target MN-CU sends a User Context Establishment Request message (UECONTEXT SETUP REQUEST) to the target MN-DU through the F1 interface to initiate the context establishment process.

[0098] Step 6: The target MN-DU performs full configuration and sends a User Context Setup Response Message (UE CONTEXT SETUP RESPONSE) to the target MN-CU to notify the target MN-CU that the target MN-DU has completed full configuration.

[0099] Step 7: The target MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the SN-CU to instruct the SN-CU to perform full configuration.

[0100] Step 8: The SN-CU performs full configuration and sends a UE context modification request message to the SN-DU through the F1 interface to instruct the SN-DU to perform full configuration.

[0101] Step 9: SN-DU performs full configuration and replies to SN-CU with a User Context Modification Response (UE CONTEXT MODIFICATION RESPONSE) via the F1 interface.

[0102] Step 10: The SN-CU sends a notification message (NOTIFICATION) to the target MN-CU, which carries the first RRC reconfiguration information (RRC Reconfiguration1). The first RRC reconfiguration information is the full configuration information of the SN.

[0103] Step 11: The target MN-CU replies to the AMF with a handover request confirmation message (HANDOVER REQUESTACKNOWLEDGE).

[0104] Step 12: AMF sends a handover command (HANDOVER COMMAND) to the source MN.

[0105] Step 13: The source MN sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the SN and the full configuration information of the target MN.

[0106] In the MR-DC mobility Ng handover (SN unchanged) scenario, the source SN and the target SN are the same. After the target MN-DU performs full configuration, the target MN-CU instructs the SN-CU to perform full configuration through the Xn interface, and the SN-CU instructs the SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the SN all perform full configuration, thereby improving the user experience.

[0107] Example 4, MR-DC Mobility Ng Handover (SN Change)

[0108] In this example, the UE accesses the network from the source MN, which switches to the target MN via the Ng interface. The target SN selected by the target MN is different from the source SN. Taking adding an SN to the target MN as an example, the process of the target MN, target SN, and UE performing a full configuration is illustrated. Figure 8 As shown, the specific implementation steps are as follows:

[0109] Step 1: In response to the UE accessing the source MN and having added the source SN, the source MN sends a handover request message (HANDOVER REQUEST) to the AMF (Authentication Management Function) through the Ng interface to initiate MR-DC mobility Ng handover.

[0110] Step 2: The AMF forwards a handover request message to the target MN-CU.

[0111] Step 3: The target MN-CU sends an SN addition request message (S-NODE ADDITIONREQUEST) to the target SN-CU, thereby initiating the SN addition process.

[0112] Step 4: The target SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITIONREQUEST ACKNOWLEDGE) to the target MN-CU.

[0113] Step 5: The target MN-CU sends a User Context Establishment Request message (UECONTEXT SETUP REQUEST) to the target MN-DU through the F1 interface to initiate the context establishment process.

[0114] Step 6: The target MN-DU performs full configuration and sends a User Context Setup Response Message (UE CONTEXT SETUP RESPONSE) to the target MN-CU to notify the target MN-CU that the target MN-DU has completed full configuration.

[0115] Step 7: The target MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the target SN-CU to instruct the target SN-CU to perform full configuration.

[0116] Step 8: The target SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the target SN-DU to perform full configuration.

[0117] Step 9: The target SN-DU performs full configuration and replies with a UE CONTEXT MODIFICATION RESPONSE message to the target SN-CU via the F1 interface.

[0118] Step 10: The target SN-CU sends a notification message (NOTIFICATION) to the target MN-CU, which carries the first RRC reconfiguration information (RRCReconfiguration 1). The first RRC reconfiguration information is the full configuration information of the target SN.

[0119] Step 11: The target MN-CU replies to the AMF with a handover request confirmation message (HANDOVER REQUESTACKNOWLEDGE).

[0120] Step 12: AMF sends a handover command (HANDOVER COMMAND) to the source MN.

[0121] Step 13: The source MN sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the target SN and the full configuration information of the target MN.

[0122] In the MR-DC mobility Ng handover (SN change) scenario, the source SN and the target SN are different. After the target MN-DU performs full configuration, the target MN-CU instructs the target SN-CU to perform full configuration through the Xn interface, and the target SN-CU instructs the target SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the target SN all perform full configuration, thereby improving the user experience.

[0123] Example 5: Intra-DU handover in MR-DC mobility (SN unchanged)

[0124] In this example, the UE accesses the network from the MN, and a handover occurs within the DU from the MN. The target SN selected by the target MN is the same as the source SN. Taking the addition of an SN in the target cell as an example, this illustrates the process of full configuration for the MN, SN, and UE. It should be noted that MR-DC mobility DU handover includes intra-cell (CU) handover and inter-cell (CU) handover; this example uses intra-cell (CU) handover as an example. Figure 9 As shown, the specific implementation steps are as follows:

[0125] Step 1: In response to the UE accessing the MN and having already added an SN, if the MN-CU determines to initiate an intra-DU handover, the MN-CU sends an SN modification request message (S-NODE MODIFICATION REQUEST) to the SN-CU, thereby initiating the SN modification procedure. In this example, the target SN selected by the target MN is the same as the source SN; therefore, the target SN-CU is the same as the source SN-CU (denoted as SN-CU), and the target SN-DU is the same as the source SN-DU (denoted as SN-DU).

[0126] Step 2: SN-CU returns an SN Modification Request acknowledgment message (S-NODE MODIFICATION REQUESTACKNOWLEDGE) to MN-CU.

[0127] Step 3: The MN-CU sends a User Context Modification Request message (UE CONTEXTMODIFICATION REQUEST) to the MN-DU through the F1 interface to initiate the context modification process.

[0128] Step 4: The MN-DU performs a full configuration and sends a User Context Modification Response (UECONTEXT MODIFICATION RESPONSE) message to the MN-CU to notify the MN-CU that the MN-DU has completed the full configuration.

[0129] Step 5: The MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the SN-CU to instruct the SN-CU to perform full configuration.

[0130] Step 6: The SN-CU performs full configuration and sends a UE context modification request message to the SN-DU through the F1 interface to instruct the SN-DU to perform full configuration.

[0131] Step 7: The SN-DU performs full configuration and replies to the SN-CU with a User Context Modification Response (UE CONTEXT MODIFICATION RESPONSE) via the F1 interface.

[0132] Step 8: SN-CU sends a notification message (NOTIFICATION) to MN-CU carrying the first RRC reconfiguration information (RRC Reconfiguration 1). The first RRC reconfiguration information is the full configuration information of SN.

[0133] Step 9: The MN-CU sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the SN and the full configuration information of the target MN.

[0134] In the MR-DC intra-DU handover scenario (SN unchanged), the source SN and the target SN are the same. After the MN-DU performs full configuration, the MN-CU instructs the SN-CU to perform full configuration through the Xn interface, and the SN-CU instructs the SN-DU to perform full configuration, so as to ensure that the UE, MN and SN all perform full configuration and improve the user experience.

[0135] Example 6: Intra-DU handover in MR-DC mobility (SN change)

[0136] In this example, the UE accesses the network from the MN, and a handover occurs within the DU from the MN. The target SN selected by the target MN is different from the source SN. Taking the addition of an SN in the target cell as an example, the process of full configuration for the MN, SN, and UE is explained. It should be noted that MR-DC mobility DU handover includes intra-cell (CU) handover within the site and inter-cell (CU) handover. This example uses intra-cell (CU) handover within the site as an example. Figure 10 As shown, the specific implementation steps are as follows:

[0137] Step 1: In response to the UE accessing the MN and having already added the source SN, if the MN-CU decides to initiate an intra-DU handover, the MN-CU sends an SN addition request message (S-NODE ADDITION REQUEST) to the target SN-CU, thereby initiating the SN addition process.

[0138] Step 2: The target SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITION REQUESTACKNOWLEDGE) to the MN-CU.

[0139] Step 3: The MN-CU sends a User Context Modification Request message (UE CONTEXTMODIFICATION REQUEST) to the MN-DU through the F1 interface to initiate the context modification process.

[0140] Step 4: The MN-DU performs a full configuration and sends a User Context Modification Response (UECONTEXT MODIFICATION RESPONSE) message to the MN-CU to notify the MN-CU that the MN-DU has completed the full configuration.

[0141] Step 5: The MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the target SN-CU to instruct the target SN-CU to perform full configuration.

[0142] Step 6: The target SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the SN-DU to perform full configuration.

[0143] Step 7: The target SN-DU performs full configuration and replies to the SN-CU with a User Context Modification Response (UE CONTEXT MODIFICATION RESPONSE) via the F1 interface.

[0144] Step 8: The target SN-CU sends a notification message (NOTIFICATION) to the MN-CU carrying the first RRC reconfiguration information (RRC Reconfiguration1). The first RRC reconfiguration information is the full configuration information of the target SN.

[0145] Step 9: The MN-CU sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the target SN and the full configuration information of the target MN.

[0146] In the MR-DC intra-DU handover (SN change) scenario, the source SN and the target SN are different. After the MN-DU performs full configuration, the MN-CU instructs the target SN-CU to perform full configuration through the Xn interface, and the target SN-CU instructs the target SN-DU to perform full configuration, so as to ensure that the UE, MN and target SN all perform full configuration, thereby improving the user experience.

[0147] Example 7: MR-DC inter-mobility DU handover (SN unchanged)

[0148] In this example, the UE accesses the network from the MN, an inter-DU handover occurs within the MN, and the target SN selected for the target cell is the same as the source SN. Taking the addition of an SN in the target cell as an example, this section illustrates the process of full configuration for the MN, SN, and UE. It should be noted that MR-DC mobility DU handover includes intra-CU handover within the site and inter-CU handover; this example uses intra-CU handover within the site as an example. Figure 11 As shown, the specific implementation steps are as follows:

[0149] Step 1: In response to the UE accessing the MN and having already added an SN, if the MN-CU determines to initiate a handover between DUs within the site, the MN-CU sends an SN modification request message (S-NODE MODIFICATION REQUEST) to the SN-CU, thereby initiating the SN modification process. In this example, the target SN selected by the target MN is the same as the source SN; therefore, the target SN-CU is the same as the source SN-CU (denoted as SN-CU), and the target SN-DU is the same as the source SN-DU (denoted as SN-DU).

[0150] Step 2: SN-CU returns an SN Modification Request acknowledgment message (S-NODE MODIFICATION REQUESTACKNOWLEDGE) to MN-CU.

[0151] Step 3: The MN-CU sends a User Context Setup Request message (UECONTEXT SETUP REQUEST) to the target MN-DU within the station via the F1 interface to initiate the context modification process.

[0152] Step 4: The target MN-DU (i.e., MN-target DU) within the site performs full configuration and sends a UE CONTEXT SETUP RESPONSE message to the MN-CU to notify the MN-CU that the target MN-DU within the site has completed full configuration.

[0153] Step 5: The MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the SN-CU to instruct the SN-CU to perform full configuration.

[0154] Step 6: The SN-CU performs full configuration and sends a UE context modification request message to the SN-DU through the F1 interface to instruct the SN-DU to perform full configuration.

[0155] Step 7: The SN-DU performs full configuration and replies to the SN-CU with a User Context Modification Response (UE CONTEXT MODIFICATION RESPONSE) via the F1 interface.

[0156] Step 8: SN-CU sends a notification message (NOTIFICATION) to MN-CU carrying the first RRC reconfiguration information (RRC Reconfiguration 1). The first RRC reconfiguration information is the full configuration information of SN.

[0157] Step 9: The MN-CU sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the SN and the full configuration information of the target MN.

[0158] In the MR-DC inter-mobility DU handover scenario (SN unchanged), the source SN and the target SN are the same. After the target MN-DU in the station performs full configuration, the MN-CU instructs the SN-CU to perform full configuration through the Xn interface, and the SN-CU instructs the SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the SN all perform full configuration, thereby improving the user experience.

[0159] Example 8: MR-DC Mobility DU Inter-handover (SN Change)

[0160] In this example, the UE accesses the network from the MN, an inter-DU handover occurs within the MN, and the target SN selected for the target cell is different from the source SN. Taking the addition of an SN in the target cell as an example, this section illustrates the process of full configuration for the MN, SN, and UE. It should be noted that MR-DC mobility DU handover includes intra-CU handover within the site and inter-CU handover; this example uses intra-CU handover within the site as an example. Figure 12 As shown, the specific implementation steps are as follows:

[0161] Step 1: In response to the UE accessing the MN and having already added the source SN, if the MN-CU determines to initiate a handover between DUs within the site, the MN-CU sends an SN addition request message (S-NODE ADDITION REQUEST) to the target SN-CU, thereby initiating the SN addition process.

[0162] Step 2: The target SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITION REQUESTACKNOWLEDGE) to the MN-CU.

[0163] Step 3: The MN-CU sends a User Context Setup Request message (UECONTEXT SETUP REQUEST) to the target MN-DU within the station via the F1 interface to initiate the context modification process.

[0164] Step 4: The target MN-DU (i.e., MN-target DU) within the site performs full configuration and sends a UE CONTEXT SETUP RESPONSE message to the MN-CU to notify the MN-CU that the target MN-DU within the site has completed full configuration.

[0165] Step 5: The MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the target SN-CU to instruct the target SN-CU to perform full configuration.

[0166] Step 6: The target SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the target SN-DU to perform full configuration.

[0167] Step 7: The target SN-DU performs full configuration and replies with a UE CONTEXT MODIFICATION RESPONSE message to the target SN-CU via the F1 interface.

[0168] Step 8: The target SN-CU sends a notification message (NOTIFICATION) to the MN-CU carrying the first RRC reconfiguration information (RRC Reconfiguration1). The first RRC reconfiguration information is the full configuration information of the target SN.

[0169] Step 9: The MN-CU sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the target SN and the full configuration information of the target MN.

[0170] In the MR-DC inter-mobility DU handover (SN change) scenario, the source SN and the target SN are different. After the target MN-DU in the station performs full configuration, the MN-CU instructs the target SN-CU to perform full configuration through the Xn interface, and the target SN-CU instructs the target SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the target SN all perform full configuration, thereby improving the user experience.

[0171] Example 9: MR-DC inter-station conditional handover (SN unchanged)

[0172] In this example, the UE accesses the network from the source MN, the source MN determines the handover conditions, and hands over to the target MN based on the Xn interface. The source MN sends handover requests to the MNs of multiple target cells, one of which selects the same target SN as the source SN. It should be noted that MR-DC inter-site mobility conditional handover includes all intra-site and inter-site conditional handover scenarios; this example uses Xn handover as an example. The process of adding an SN to the target MN, and the UE performing full configuration, is illustrated using the example of adding an SN to the target MN. Figure 13 As shown, the specific implementation steps are as follows:

[0173] Step 1: In response to the UE accessing the source MN and having added the SN, if the source MN decides to perform a conditional handover, the source MN sends a handover request message (HANDOVER REQUEST) to multiple target MN-CUs through the Xn interface to initiate MR-DC mobility Xn handover.

[0174] Step 2: One of the target MN-CUs sends an SN addition request message (S-NODE ADDITIONREQUEST) to the SN-CU, thereby initiating the SN addition process. In this example, the target SN selected by the target cell is the same as the source SN, therefore the target SN-CU is the same as the source SN-CU (represented as SN-CU), and the target SN-DU is the same as the source SN-DU (represented as SN-DU).

[0175] Step 3: SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITION REQUESTACKNOWLEDGE) to the target MN-CU.

[0176] Step 4: The target MN-CU sends a User Context Establishment Request message (UECONTEXT SETUP REQUEST) to the target MN-DU through the F1 interface to initiate the context establishment process.

[0177] Step 5: The target MN-DU performs full configuration and sends a UE CONTEXT SETUP RESPONSE message to the target MN-CU to notify the target MN-CU that the target MN-DU has completed full configuration.

[0178] Step 6: The target MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the SN-CU to instruct the SN-CU to perform full configuration.

[0179] Step 7: The SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the SN-DU to perform full configuration.

[0180] Step 8: The SN-DU performs full configuration and replies to the SN-CU with a User Context Modification Response (UE CONTEXT MODIFICATION RESPONSE) via the F1 interface.

[0181] Step 9: The SN-CU sends a notification message (NOTIFICATION) to the target MN-CU, which carries the first RRC reconfiguration information (RRC Reconfiguration1). The first RRC reconfiguration information is the full configuration information of the SN.

[0182] Step 10: The target MN-CU sends a handover request confirmation message to the source MN.

[0183] Step 11: The source MN sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the SN and the full configuration information of the target MN.

[0184] MR-DC inter-site handover conditions (SN unchanged): The source SN and the target SN are the same. After the target MN-DU performs full configuration, the target MN-CU instructs the SN-CU to perform full configuration through the Xn interface, and the SN-CU instructs the SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the SN all perform full configuration, thereby improving the user experience.

[0185] Example 10: MR-DC inter-station conditional handover (SN change)

[0186] In this example, the UE accesses the network from the source MN, the source MN determines the handover conditions, and hands over to the target MN based on the Xn interface. The source MN sends handover requests to the MNs of multiple target cells, one of which selects a different target SN than the source SN. It should be noted that MR-DC inter-site mobility conditional handover includes all intra-site and inter-site conditional handover scenarios; this example uses Xn handover as an example. The process of adding an SN to the target MN, and the UE performing full configuration, is illustrated using the example of adding an SN to the target MN. Figure 14 As shown, the specific implementation steps are as follows:

[0187] Step 1: In response to the UE accessing the source MN and having added the source SN, if the source MN decides to perform a conditional handover, the source MN sends a handover request message (HANDOVER REQUEST) to multiple target MN-CUs through the Xn interface to initiate MR-DC mobility Xn handover.

[0188] Step 2: One of the target MN-CUs sends an SN addition request message (S-NODE ADDITIONREQUEST) to the target SN-CU, thereby initiating the SN addition process. In this example, the target SN selected by the MN of the target cell is the same as the source SN, therefore the target SN-CU is the same as the source SN-CU (denoted as SN-CU), and the target SN-DU is the same as the source SN-DU (denoted as SN-DU).

[0189] Step 3: The target SN-CU returns an SN Addition Request acknowledgment message (S-NODE ADDITIONREQUEST ACKNOWLEDGE) to the target MN-CU.

[0190] Step 4: The target MN-CU sends a User Context Establishment Request message (UECONTEXT SETUP REQUEST) to the target MN-DU through the F1 interface to initiate the context establishment process.

[0191] Step 5: The target MN-DU performs full configuration and sends a UE CONTEXT SETUP RESPONSE message to the target MN-CU to notify the target MN-CU that the target MN-DU has completed full configuration.

[0192] Step 6: The target MN-CU sends a user-side Xn interface address indication message (Xn-U ADDRESSINDICATION) to the target SN-CU to instruct the target SN-CU to perform full configuration.

[0193] Step 7: The target SN-CU performs full configuration and sends a UE context modification request message to the target SN-DU through the F1 interface to instruct the target SN-DU to perform full configuration.

[0194] Step 8: The target SN-DU performs full configuration and replies with a UE CONTEXT MODIFICATION RESPONSE message to the target SN-CU via the F1 interface.

[0195] Step 9: The target SN-CU sends a notification message (NOTIFICATION) to the target MN-CU, which carries the first RRC reconfiguration information (RRCReconfiguration 1). The first RRC reconfiguration information is the full configuration information of the target SN.

[0196] Step 10: The target MN-CU sends a handover request confirmation message to the source MN.

[0197] Step 11: The source MN sends the second RRC reconfiguration information (RRC Reconfiguration 2) to the UE to instruct the UE to perform full configuration. The second RRC reconfiguration information is the full configuration information of the target SN and the full configuration information of the target MN.

[0198] In MR-DC inter-site conditional handover (SN change), the source SN and the target SN are different. After the target MN-DU performs full configuration, the target MN-CU instructs the target SN-CU to perform full configuration through the Xn interface, and the target SN-CU instructs the target SN-DU to perform full configuration, so as to ensure that the UE, the target MN, and the target SN all perform full configuration, thereby improving the user experience.

[0199] This disclosure embodiment is aimed at MR-DC mobility scenarios. When MN-DU triggers full configuration, the SN can be instructed to perform full configuration through the Xn interface field. This avoids packet loss and flow interruption caused by MN and UE performing full configuration but SN not performing full configuration.

[0200] The full configuration method for MR-DC in this disclosure is applied to MR-DC mobility scenarios. By adding a field to the protocol to instruct the target SN to perform full configuration, the problem of sudden drop in traffic or handover failure can be solved.

[0201] Based on the same technical concept, this disclosure also provides an MR-DC full configuration device, wherein the device is a target MN-CU, such as Figure 15 As shown, the MN-CU includes a determination module 101 and an indication full configuration module 102. The determination module 101 is used to determine whether the target master node distribution unit MN-DU has completed full configuration.

[0202] The full configuration instruction module 102 is used to send an instruction message to the target auxiliary node central unit SN-CU in response to the determination module determining that the target master node distribution unit MN-DU has completed full configuration. The instruction message is used to instruct the target SN-CU to perform full configuration.

[0203] In some embodiments, the instruction full configuration module 102 is used to send an instruction message to the target SN-CU via the Xn interface.

[0204] In some embodiments, the indication message is a user-side Xn interface address indication message.

[0205] Based on the same technical concept, this disclosure also provides an MR-DC full configuration device, wherein the device is an SN-CU, such as... Figure 16 As shown, the SN-CU includes a first receiving module 201 and a full configuration module 202. The first receiving module 201 is used to receive an indication message sent by the target master node central unit MN-CU, and the indication message is used to instruct the target SN-CU to perform full configuration.

[0206] The full configuration module 202 is used to perform full configuration.

[0207] In some embodiments, such as Figure 17 As shown, the SN-CU further includes a sending module 203 and a second receiving module 204. The sending module 203 is used to send a user context modification request message to the target auxiliary node distribution unit SN-DU after the full configuration module 202 performs full configuration. The user context modification request message is used to instruct the target SN-DU to perform full configuration.

[0208] The second receiving module 204 is used to receive a user context modification response message sent by the target SN-DU, the user context modification response message being sent by the target SN-DU after completing full configuration.

[0209] In some embodiments, the first receiving module 201 is configured to receive an indication message sent by the target MN-CU via the Xn interface.

[0210] In some embodiments, the indication message is a user-side Xn interface address indication message.

[0211] This disclosure also provides a computer device, which includes one or more processors and a storage device; wherein the storage device stores one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the full configuration method of MR-DC as described above.

[0212] This disclosure also provides a computer-readable medium having a computer program stored thereon, wherein the computer program, when executed, implements the full configuration method of MR-DC as described above.

[0213] It will be understood by those skilled in the art that all or some of the steps in the methods disclosed above, and the functional modules / units in the apparatus, can be implemented as software, firmware, hardware, and suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0214] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A method for full configuration of an MR-DC, characterized in that, The method is applied to the target master node central unit MN-CU, including: In a multi-wireless dual-connectivity MR-DC mobility MN handover scenario with SN, in response to determining that the target primary node distribution unit MN-DU has triggered and completed full configuration while the target MN-CU has not decided on full configuration, an indication message is sent to the target secondary node central unit SN-CU. The indication message is a user-side Xn interface address indication message, used to instruct the target SN-CU to perform full configuration.

2. The method as described in claim 1, characterized in that, Sending the indication message to the target auxiliary node SN-CU includes: sending the indication message to the target SN-CU through the Xn interface.

3. A method for full configuration of an MR-DC, characterized in that, The method is applied to the target auxiliary node central unit SN-CU, including: In a multi-wireless dual-connection MR-DC mobility MN handover with SN scenario, an indication message is received from the target master node central unit MN-CU. The indication message is sent by the target MN-CU when it is determined that the target master node distribution unit MN-DU has triggered and completed full configuration, but the target MN-CU has not decided on full configuration. It is used to instruct the target SN-CU to perform full configuration. Perform full configuration; A user context modification request message is sent to the target secondary node distribution unit (SN-DU) via the F1 interface. The user context modification request message is used to instruct the target SN-DU to perform full configuration. Receive the user context modification response message sent by the target SN-DU, which is sent by the target SN-DU after completing full configuration.

4. The method as described in claim 3, characterized in that, The receipt of the indication message sent by the target master node central unit MN-CU includes: Receive the instruction message sent by the target MN-CU through the Xn interface.

5. The method as described in claim 3, characterized in that, The indication message is the user-side Xn interface address indication message.

6. A full-scale MR-DC configuration device, characterized in that, The device is a target master node central unit MN-CU, which includes a determination module and an indication full configuration module. The determination module is used to determine whether the target master node distribution unit MN-DU has completed full configuration. The full configuration instruction module is used to, in a multi-wireless dual-connectivity MR-DC mobility MN handover with SN scenario, in response to the determination module determining that the target primary node distribution unit MN-DU has triggered and completed full configuration while the target MN-CU has not decided on full configuration, send an instruction message to the target secondary node central unit SN-CU. The instruction message is a user-side Xn interface address instruction message, used to instruct the target SN-CU to perform full configuration.

7. A full-scale MR-DC configuration device, characterized in that, The device is an auxiliary node central unit (SN-CU), comprising a first receiving module, a full configuration module, a sending module, and a second receiving module. The first receiving module is used to receive an indication message sent by the target master node central unit (MN-CU) in a multi-wireless dual-connectivity (MR-DC) mobility MN handover SN scenario. The indication message is sent by the target MN-CU when it determines that the target master node distribution unit (MN-DU) has triggered and completed full configuration, but the target MN-CU has not decided on full configuration. The indication message is used to instruct the target SN-CU to perform full configuration. The full configuration module is used to perform full configuration; The sending module is used to send a user context modification request message to the target secondary node distribution unit (SN-DU) through the F1 interface after the full configuration module performs full configuration. The user context modification request message is used to instruct the target SN-DU to perform full configuration. The second receiving module is used to receive a user context modification response message sent by the target SN-DU, the user context modification response message being sent by the target SN-DU after completing full configuration.

8. A computer device, comprising: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the full configuration method of MR-DC as described in any one of claims 1-5.

9. A computer-readable medium having a computer program stored thereon, wherein, When the program is executed, it implements the full configuration method of MR-DC as described in any one of claims 1-5.

Images