Method, apparatus and related device for configuring multiple secondary cell groups

Abstract

The application discloses a multi-secondary cell group configuration method and device and related equipment, and belongs to the technical field of communication. The method comprises the following steps: a terminal receives target configuration information, wherein the target configuration information is used for configuring multiple secondary cell groups for the terminal; and the terminal performs a target configuration operation according to the target configuration information, so that the terminal is configured with multiple SCGs.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a multi-auxiliary cell group configuration method, apparatus and related equipment. Background Technology

[0002] Dual Connectivity (DC) provides a terminal with resources from two network nodes (access network elements). One network node is called the Master Node (MN), and the other is called the Secondary Node (SN). Each network node can also use carrier aggregation technology, which configures a series of serving cells, also known as cell groups, controlled by that node. The cell group controlled by the MN is called the Master Cell Group (MCG), and the one controlled by the SN is called the Secondary Cell Group (SCG).

[0003] Currently, network nodes have limited SCG resources configured for terminals, resulting in poor communication performance of the terminals. Summary of the Invention

[0004] This application provides a multi-auxiliary cell group configuration method, apparatus, and related equipment, which can solve the problem that the limited SCG resources configured by network nodes for terminals lead to poor communication performance of terminals.

[0005] Firstly, a method for configuring multiple secondary cell groups is provided, including:

[0006] The terminal receives target configuration information, which is used to configure at least one secondary cell group (SCG) for the terminal.

[0007] The terminal performs a target configuration operation based on the target configuration information, so that the terminal can configure multiple SCGs.

[0008] Secondly, a method for configuring multiple secondary cell groups is provided, including:

[0009] The master node (MN) sends target configuration information to the terminal, which is used to configure at least one secondary cell group (SCG) for the terminal.

[0010] Thirdly, a multi-auxiliary cell group configuration device is provided, including:

[0011] The secondary node (SN) sends target configuration information to the terminal, which is used to configure at least one secondary cell group (SCG) for the terminal.

[0012] Fourthly, a multi-auxiliary cell group configuration device is provided, comprising:

[0013] The receiving module is used to receive target configuration information, which is used to configure at least one secondary cell group (SCG) for the terminal.

[0014] The execution module is used to perform target configuration operations based on the target configuration information, so that the terminal can be configured with multiple SCGs.

[0015] Fifthly, a multi-auxiliary cell group configuration device is provided, comprising:

[0016] The first sending module is used to send target configuration information to the terminal, the target configuration information being used to configure at least one secondary cell group (SCG) for the terminal.

[0017] Sixthly, a multi-auxiliary cell group configuration device is provided, comprising:

[0018] The second sending module is used to send target configuration information to the terminal, wherein the target configuration information is used to configure at least one secondary cell group (SCG) for the terminal.

[0019] In a seventh aspect, a terminal is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the multi-auxiliary cell group configuration method as described in the first aspect.

[0020] Eighthly, a network node is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the multi-secondary cell group configuration method as described in the second or third aspect.

[0021] A ninth aspect provides a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the multi-auxiliary cell group configuration method as described in the first, second, or third aspect.

[0022] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run network-side device programs or instructions to implement the steps of the multi-auxiliary cell group configuration method as described in the first, second, or third aspect.

[0023] In this embodiment, the terminal receives target configuration information, which is used to configure multiple secondary cell groups (SCGs) for the terminal. The terminal performs a target configuration operation based on the target configuration information to configure multiple SCGs. The terminal can configure multiple SCGs based on the target configuration information sent by the network node, thus improving the terminal's communication performance. Attached Figure Description

[0024] Figure 1 This is a structural diagram of a network system provided in an embodiment of this application;

[0025] Figure 2 This is a flowchart of a multi-auxiliary cell group configuration method provided in an embodiment of this application;

[0026] Figure 3 This is another flowchart of the multi-auxiliary cell group configuration method provided in the embodiments of this application;

[0027] Figure 4 This is another flowchart of the multi-auxiliary cell group configuration method provided in the embodiments of this application;

[0028] Figure 5 This is a structural diagram of the first multi-auxiliary cell group configuration device provided in the embodiments of this application;

[0029] Figure 6 This is a structural diagram of the second multi-auxiliary cell group configuration device provided in the embodiments of this application;

[0030] Figure 7 This is a structural diagram of the third multi-auxiliary cell group configuration device provided in the embodiments of this application;

[0031] Figure 8 This is a structural diagram of the communication device provided in the embodiments of this application;

[0032] Figure 9 This is a structural diagram of the terminal provided in the embodiments of this application;

[0033] Figure 10 This is a structural diagram of a network node provided in an embodiment of this application. Detailed Implementation

[0034] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0035] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship. In this application, "transmission" refers to the transmission of a signal, not signal sending in the narrow sense.

[0036] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, although these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0037] Figure 1This diagram illustrates a structural diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), central unit (CU), distributed unit (DU), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station, CU, and DU in the NR system are used as examples, but the specific type of base station is not limited.

[0038] The multi-auxiliary cell group configuration method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0039] Please see Figure 2 , Figure 2 This is a flowchart of a multi-auxiliary cell group configuration method provided in an embodiment of this application. The multi-auxiliary cell group configuration method includes:

[0040] Step 201: The terminal receives target configuration information, which is used to configure multiple secondary cell groups (SCGs) for the terminal.

[0041] Understandably, for normal communication, the network needs to configure the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer for the terminal. For Data Radio Bearer (DRB), the network also needs to configure the Service Data Adaptation Protocol (SDAP) layer. To meet the needs of different services, the network needs to configure different configuration parameters for the terminal for different Protocol Data Unit (PDU) sessions and Quality of Service (QoS). In other words, the network needs to configure multiple sets of SDAP / PDCP / RLC / MAC / PHY layer configurations for the terminal. Each configuration can be simply understood as a specific radio bearer, represented by a radio bearer identifier ID. A gNB can configure multiple sets of SDAP / PDCP / RLC / MAC / PHY layer configurations for the terminal, that is, configure multiple complete radio bearers. In a CU-DU separation scenario, the SDAP / PDCP layer is located in the CU, and the RLC / MAC / PHY layer is located in the DU. Therefore, a complete radio bearer requires joint configuration by the CU and DU; that is, the CU configures the SDAP / PDCP portion of the radio bearer, and the DU configures the RLC / MAC / PHY portion. In current protocols, radio bearer configuration sometimes refers generally to the configuration of multiple SDAP / PDCP / RLC / MAC / PHY layers for the terminal, and sometimes specifically to the SDAP / PDCP configuration of multiple radio bearers (e.g., the SDAP / PDCP configurations of multiple DRBs and multiple SRBs are collectively referred to as RadioBearerConfig). The meaning depends on the specific context. SCG configuration generally refers primarily to the configuration of the RLC / MAC / PHY layer (sometimes also called RLC radio bearer configuration).

[0042] In this application, multiple SCGs can correspond to one base station or multiple base stations. For example, one gNB may configure multiple SCGs for a terminal. Or, one gNB may configure one SCG for a terminal, and another gNB may configure another SCG for the terminal. Multiple SCGs can also correspond to multiple DUs, and the multiple DUs are associated with one or more CUs. For example, each SCG corresponds to the resources of one DU, or each SCG is a radio resource configured for the UE by one DU. These SCGs or these DUs can be associated with their respective corresponding CUs, or partially associated with the same CU. This means that the PDCP entities associated with multiple SCGs may be located at multiple base stations, or at the same base station, or at the same CU.

[0043] In this application, SCG includes cell groups other than the primary cell group (MCG) configured by the network for the terminal; the name of these groups is not limited herein. For example, the network can configure multiple SCGs for the terminal, each associated with an SCG ID. Alternatively, the network can configure a primary SCG and a secondary SCG for the terminal. Or, the network can configure one SCG for the terminal, and then configure an additional SCG list (i.e., AdditionalSCGList) or an additional SCG (i.e., AdditionalSCG).

[0044] Multiple SCGs can use the same Radio Access Technologies (RAT) or different RATs.

[0045] Before receiving the target configuration information, the terminal can also indicate to the network-side device whether it supports receiving the target configuration information. For example, this can be done through capability information reporting.

[0046] The target configuration information is sent to the terminal by the network node (i.e., the network-side device). The network node can be either the SN or the master node (MN).

[0047] Step 202: The terminal performs a target configuration operation based on the target configuration information, so that the terminal configures multiple SCGs. For example, the terminal performs at least one of the following operations based on the target configuration information:

[0048] SCG creation operation;

[0049] Adding an SCG;

[0050] SCG modification operations;

[0051] SCG release operation;

[0052] SCG activation operation;

[0053] Deactivation of SCG;

[0054] SCG's sleep operation;

[0055] SCG switching operation.

[0056] The establishment or addition of an SCG also includes configuring the terminal to operate in a dual-connection DC or multi-connection MC mode.

[0057] Based on the target configuration information, the terminal can also perform SCG configuration recovery operations. For example, if the terminal retains the configuration of multiple SCGs when it is released to the RRC inactive state by the network, the RRC resume message can indicate to the terminal which SCG configurations need to be recovered and which SCG configurations need to be released during the RRC connection recovery process.

[0058] The SCG switching operation includes: switching between multiple configured SCGs (e.g., SCG Switch) and replacing a configured SCG with a new SCG (e.g., SN change, SCG change).

[0059] The terminal can configure multiple SCGs or only one SCG based on the target configuration information.

[0060] In this embodiment, the terminal receives target configuration information, which is used to configure multiple secondary cell groups for the terminal. The terminal performs a target configuration operation based on the target configuration information to configure multiple SCGs. The terminal can configure multiple SCGs based on the target configuration information sent by the network node, thus improving the terminal's communication performance.

[0061] In the above, the target configuration information is used to indicate at least one of the following:

[0062] Should the terminal be configured in multi-connection mode?

[0063] Should the terminal be configured as a multi-SCG mode?

[0064] Whether to configure the current secondary node (SN) of the terminal as the primary SN;

[0065] The number of SCGs;

[0066] The addition of at least one SCG;

[0067] Release of at least one SCG;

[0068] At least one SCG modification;

[0069] At least one SCG wireless access type;

[0070] Configuration information for at least one SCG;

[0071] The identifier of the SCG being activated for the first time;

[0072] The default SCG identifier;

[0073] The identifier for a dormant SCG.

[0074] Whether to configure the current secondary node SN of the terminal as the primary SN also includes at least one of the following:

[0075] Should the currently configured SCG of the terminal be set as the primary SCG?

[0076] Whether to configure the currently configured SN PDCP entity of the terminal as the primary SN PDCP entity;

[0077] Whether to configure the currently configured SCG-related radio bearer of the terminal as the primary SCG radio bearer.

[0078] The configuration information corresponding to SCG includes the Radio Link Control (RLC) bearer configuration. Specifically, this may include configuration parameters for the RLC layer, Media Access Control (MAC) layer, physical layer, and so on.

[0079] Furthermore, the terminal activates the SCG corresponding to FirstActiveSCGId (the identifier of the first activated SCG) if at least one of the following conditions is met:

[0080] When the terminal receives an RRC Resume message;

[0081] When the terminal initiates an RRC resume;

[0082] When the terminal completes the RRC resume process;

[0083] When the terminal receives the MN handover command;

[0084] When the terminal handover is complete;

[0085] When the terminal execution condition changes;

[0086] When the SCG currently being used by the terminal fails. These failure conditions include Radio Link Failure (RLF), Synchronization Reconfiguration Failure, etc.

[0087] When the network reconfigures the FirstActiveSCGId parameter;

[0088] Receive the first information container and configure multiple SCG configurations;

[0089] Once the terminal is configured for multi-connection or multi-SCG mode.

[0090] In this application, "when XX" can be understood as "under the condition of XX". For example, as mentioned above, "when the terminal receives the RRC Resume message" can be understood as "under the condition that the terminal receives the RRC Resume message".

[0091] Furthermore, the UE switches to the default SCG if at least one of the following conditions is met:

[0092] If the UE does not receive downlink scheduling and / or does not transmit uplink data on the current SCG for a certain period of time, the UE switches to the default SCG. Optionally, the length of this period is determined by the protocol or by a timer based on network configuration.

[0093] In the above, the configuration information corresponding to at least one SCG includes the configuration of at least one RLC radio bearer, and the configuration of the RLC radio bearer is used to indicate at least one of the following:

[0094] Logical channel identifier; for example, values ​​such as 5, 32, 40, etc.

[0095] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0096] The first radio bearer associated with the RLC radio bearer;

[0097] The PDCP entity or the first radio bearer is associated with a first serving network element, which provides additional resources on top of dual connectivity. The first radio bearer associated with the RLC radio bearer includes at least one DRB and / or at least one SRB associated with the RLC radio bearer. DRBs and SRBs can be identified using corresponding IDs; for example, the first radio bearers associated with the RLC radio bearer could be DRB 1, DRB 32, DRB 35, DRB 40, SRB 1, SRB 2, or SRB 4.

[0098] Optionally, the configuration information corresponding to SCG may also include at least one of the following: RLC reconstruction identifier, RLC layer configuration, and MAC layer configuration.

[0099] The first serving network element is the serving network element of the terminal other than MN and SN. That is, the network node is a new SCG configured for the terminal, which can be associated with the radio bearer configured by MN or SN, or it can be associated with the radio bearer configured by the first network element.

[0100] Optionally, the above method can be used to associate the configuration of the MCG with the radio bearer of the first serving network element. That is, the configuration information corresponding to the MCG can also include the configuration of at least one RLC radio bearer, and the configuration of the RLC radio bearer is used to indicate at least one of the following:

[0101] Logical channel identifier;

[0102] The PDCP entity associated with the RLC radio bearer;

[0103] The first radio bearer associated with the RLC radio bearer;

[0104] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0105] In one embodiment of this application, the target configuration information is used to configure a second radio bearer, the second radio bearer being a radio bearer associated with a first serving network element, the first serving network element being used to provide additional resources on the basis of dual connectivity.

[0106] The configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal. This can be understood as follows: although the third information container is introduced into the protocol for configuring the first radio bearer, it can also be used by the MN or SN to configure the radio bearer configuration / PDCP configuration of the MN or SN.

[0107] For example, a third information container can be defined as RadioBearerConfigExt to distinguish it from RadioBearerConfig and RadioBearerConfig2 in related technologies. The third information container indicates at least one of the following:

[0108] 1) The security configuration of the UE includes at least one of the following:

[0109] Security algorithms;

[0110] Key information; where the key information indicates which network node's security key corresponds to the wireless bearer configured in the current third information container. For example:

[0111] In one configuration: KeyToUse = ENUMERATED{master, secondary}, KeyToUseSCG = INTEGAR(1..N), where N is the number of configured SNs. If KeyToUse indicates master, the radio bearer configured in the current third information container uses the key of MN. If KeyToUse indicates secondary, and the KeyToUseSCG field is absent or its value is 1, it indicates that the radio bearer configured in the current third information container uses the key of the first SN (or primary SN). If KeyToUse indicates secondary, and the KeyToUseSCG field value is 2, it indicates that the radio bearer configured in the current third information container uses the key of the second SN (or secondary SN).

[0112] In another approach: KeyToUseExt = INTEGAR(0..N), where 0 represents the master, 1 to N represent several configured SNs, and N is the number of configured SNs.

[0113] 2) DRB configuration between the additional SN and the UE (the additional SN being a newly introduced SN in addition to the SN in the dual-connectivity DC), wherein at least one of the following is indicated:

[0114] DRB ID, where the DRB ID is a newly defined ID;

[0115] SDAP configuration;

[0116] PDCP configuration. The PDCP configuration can include at least one of the following: the number of associated MAC entities, the number of associated RLC entities, priority information among multiple paths, and PDCP duplication. For example, the PDCP configuration might indicate that the radio bearer or PDCP configured in the current third information container is associated with two SCGs and MCGs, with one of the MCGs set as the primary path and one of the SCGs set as a secondary path. Setting such priorities allows terminals to preferentially select higher-priority paths for sending and receiving information in specific scenarios, saving network resources on other paths.

[0117] 3) Additional SN and UE SRB configuration, wherein at least one of the following is indicated:

[0118] PDCP configuration;

[0119] SRB ID, wherein the SRB ID is a newly defined ID (e.g., SRB4); further, it also includes a new SRB release instruction (e.g., srb4-ToRelease);

[0120] Instruct the user to configure the SRB as either primary SRB3 or secondary SRB3;

[0121] This indicates whether the SRB3 is configured to be active or deactivated.

[0122] It can be stipulated that only one SRB3 of a UE is in an active or available state at any given time; if the SCG corresponding to SRB3 is in an active state, then SRB3 is in an active or available state, otherwise SRB3 is in an inactive or unavailable state; for example, if two SCGs belong to the same gNB, the network side may activate the SRB3 corresponding to one of the SCGs and deactivate the SRB3 corresponding to the other SCG.

[0123] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0124] The terminal receives the target configuration information in at least one of the following ways:

[0125] The target configuration information is received via MCG, for example, in the case of initially adding multiple SCGs;

[0126] The target configuration information is received through the configured first SCG. The target configuration information is used to configure a second SCG other than the first SCG for the terminal. For example, in the case of dual connection mode, the first SCG is the SCG configured in dual connection mode.

[0127] The target configuration information is received through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

[0128] Target configuration information can be sent via Radio Resource Control (RRC) messages, MACCE, and Downlink Control Information (DCI), or it can be forwarded or transmitted at inter-network interfaces. RRC messages include, for example, RRC establishment messages, RRC reconfiguration messages, and RRC recovery messages.

[0129] In one embodiment of this application, the target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single-connection mode, or when the terminal's dual-connection mode is released or canceled. When the UE is configured with the first information container, the UE believes that it has been configured with multiple connections, multiple SCGs, or multiple SNs.

[0130] Furthermore, the terminal performs a target configuration operation based on the target configuration information, so that the terminal configures multiple SCGs, including:

[0131] The terminal performs at least one of the following operations based on the first information container:

[0132] Configure the terminal to a multi-connection mode or a multi-SCG mode;

[0133] Perform at least one configuration operation for an SCG.

[0134] In one embodiment of this application, the target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connectivity mode. This is used to configure several additional SCGs or SNs for the UE based on the existing SCG / SN configuration. Optionally, when the UE is configured with the second information container, the UE believes it has been configured with multiple connections or multiple SCGs. For example, MR-DC with multiple SCGs.

[0135] Furthermore, the terminal performs a target configuration operation based on the target configuration information, so that the terminal configures multiple SCGs, including:

[0136] The terminal performs at least one of the following operations based on the second information container:

[0137] Configure the terminal to a multi-connection mode or a multi-SCG mode;

[0138] Perform at least one configuration operation for an SCG.

[0139] In the above, both the first information container and the second information container can be used to indicate at least one of the following:

[0140] Several SCG identifiers;

[0141] Several SCG wireless access types;

[0142] Added several SCG configurations;

[0143] Several SCG configuration modifications;

[0144] Release of several SCG configurations;

[0145] Establishment of multiple connections;

[0146] Release multiple connections;

[0147] Establishing multiple SCG configurations;

[0148] Release of multiple SCG configurations;

[0149] RLC layer parameters of several SCGs;

[0150] Several MAC layer parameters of SCG;

[0151] Several SCG PHY layer parameters.

[0152] In one embodiment of this application, after the terminal receives the target configuration information, the method further includes:

[0153] The terminal sends a response message, which includes a fourth information container used to indicate the terminal's response to the first service network element.

[0154] Please see Figure 3 , Figure 3 This is a flowchart of a multi-auxiliary cell group configuration method provided in an embodiment of this application. The multi-auxiliary cell group configuration method includes:

[0155] Step 301: The master node MN sends target configuration information to the terminal. The target configuration information is used to configure at least one secondary cell group (SCG) for the terminal.

[0156] After receiving the target configuration information, the terminal can perform a target configuration operation based on the target configuration information, so that the terminal can configure multiple SCGs. For example, the terminal can perform at least one of the following operations based on the target configuration information:

[0157] SCG creation operation;

[0158] Adding an SCG;

[0159] SCG modification operations;

[0160] SCG release operation;

[0161] SCG activation operation;

[0162] Deactivation of SCG;

[0163] SCG's sleep operation;

[0164] SCG switching operation.

[0165] In this embodiment, the master node (MN) sends target configuration information to the terminal. This target configuration information is used to configure at least one secondary cell group (SCG) for the terminal. The master node can send target configuration information to the terminal to configure multiple SCGs, thereby improving the terminal's communication performance.

[0166] Furthermore, the target configuration information is used to indicate at least one of the following:

[0167] Should the terminal be configured in multi-connection mode?

[0168] Should the terminal be configured as a multi-SCG mode?

[0169] Whether to configure the current secondary node SN of the terminal as the primary SN;

[0170] The number of SCGs;

[0171] The addition of at least one SCG;

[0172] Release of at least one SCG;

[0173] At least one SCG modification;

[0174] At least one SCG wireless access type;

[0175] Configuration information for at least one SCG;

[0176] The identifier of the SCG being activated for the first time;

[0177] The default SCG identifier;

[0178] The identifier for a dormant SCG.

[0179] Furthermore, the configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, the configuration of which is used to indicate at least one of the following:

[0180] Logical channel identifier;

[0181] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0182] The first radio bearer associated with the RLC radio bearer;

[0183] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0184] Furthermore, the target configuration information is used to configure a second radio bearer, which is a radio bearer associated with a first serving network element, and the first serving network element is used to provide additional resources on the basis of dual connectivity.

[0185] Furthermore, the configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0186] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0187] Furthermore, the master node MN sends target configuration information to the terminal, including:

[0188] The MN sends the target configuration information via the MCG. Furthermore, the MN can also send the target configuration information via the SCG. For example, when a radio link failure occurs in the MCG, the terminal may initiate an MCG recovery process via the SCG, and the MN will send a reconfiguration message to the terminal via the SCG, which may also carry the target configuration information.

[0189] Furthermore, the target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single-connection mode. Optionally, if the terminal is currently in dual-connection DC mode, the network can first control the terminal to release the DC configuration (which can be understood as canceling the dual-connection mode) before sending the first information container. The network can control the release of dual connections and the establishment of multiple connections through the same message.

[0190] Furthermore, the target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

[0191] Furthermore, before the MN sends the target configuration information to the terminal, the method further includes: the MN sending a secondary node (SN) add request message to the first target network element, the SN add request message being used to request the first target network element to configure the resources required by the terminal in multi-connection or multi-SCG mode.

[0192] Specifically, the first target network element is the network element that receives the SN add request message. In one scenario (e.g., an inter-SN multi-SCG scenario), the MN can initiate the SN add process to multiple SNs separately; in another scenario (e.g., an intra-SN or intra-CU scenario), the MN can send the SN add process to a target SN, requesting the configuration of multiple SCGs.

[0193] In the SN Add Request message, the MN indicates at least one of the following to the first target network element, that is, the SN Add Request message is also used to indicate at least one of the following:

[0194] Indicates whether the MN supports configuring multiple SCGs or multiple connection modes for the terminal;

[0195] Request the first target network element to configure multiple SCGs;

[0196] Indicates the desired configuration or initial state of the plurality of SCGs;

[0197] Request the radio bearer information configured in the first target network element;

[0198] The configuration information of the SCG that has been configured on the terminal is indicated;

[0199] Indicates the radio bearer configuration information of the terminal for other serving network elements besides the first target network element;

[0200] Indicates the capability information of the terminal;

[0201] Indicates resource collaboration information in the multi-connection mode of the terminal;

[0202] The request is to restore the wireless links of other network elements of the terminal in multi-connection mode through the first target network element; for example, the request to restore the wireless link of the MCG through the first target network element fails, or the request to restore the wireless link of a certain SCG through the first target network element fails, or the request to restore the wireless link of other CGs of the terminal through the first target network element fails.

[0203] In the above, after the MN sends the secondary node SN addition request message to the first target network element and before the MN sends the target configuration information to the terminal, the method further includes: the MN receiving a first response message from the first target network element to the SN addition request message, the first response message being used to indicate whether to accept or reject the SN addition request.

[0204] The first response message may also be used to indicate at least one of the following:

[0205] Configuration information for multiple SCGs; optionally, the configuration information for multiple SCGs can be carried through an SN RRC message container, and the MN may be invisible.

[0206] Activation indication information for multiple SCGs;

[0207] Deactivation instructions for multiple SCGs;

[0208] Hibernation indication information for multiple SCGs.

[0209] In one embodiment of this application, the method further includes:

[0210] The MN sends a first request to the second target network element, the first request being used to request that the second target network element be configured as the master SN.

[0211] The second target network element is the network element that receives the first request. Further, the first request is carried by at least one of the following:

[0212] Add a request message to the SN;

[0213] SN modification request message;

[0214] Main SN request message.

[0215] Furthermore, the MN can also send the SCG configuration information of other SNs of the UE to the second target network element in the first request, or send it to the second target network element after receiving the acceptance from the second target network element as a primary SN response.

[0216] After the MN sends the first request to the second target network element, the method further includes:

[0217] The MN receives a second response message from the second target network element, which indicates whether to accept or reject configuring the second target network element as the primary SN. The second target network element may send a response (e.g., a Primary SN request acknowledge message) to the MN, indicating whether to accept or reject being the primary SN.

[0218] In one embodiment of this application, the method further includes: the MN receiving a second request from a second serving network element of the terminal, the second request being used to request at least one of the following:

[0219] The MN initiates a path update process to the core network, for example, SN PDCP termination point change information;

[0220] The User Plane Function (UPF) path of the terminal is switched from the terminal's SN (which can be understood as the terminal's first SN) to another SN of the terminal, or from another SN of the terminal to the terminal's SN. For example, the MN requests the AMF to initiate a path update procedure to switch the UPF path from the primary SN to a secondary SN. Optionally, the first SN can be the primary SN and the other SNs can be secondary SNs, or the other SNs can be the primary SN and the first SN can be the secondary SN. The serving network element can be either the primary SN or the secondary SN.

[0221] Furthermore, the method further includes: the MN receiving first indication information sent by the third serving network element of the terminal, the first indication information being used to indicate one of the following:

[0222] Release all secondary cell groups configured in the third serving network element;

[0223] Release a portion of the secondary cell group configured by the third serving network element, for example, indicating the ID of the released SCG;

[0224] The release information of other service network elements of the terminal besides the third service network element, for example, the primary SN instructs the secondary SN to release information to the MN.

[0225] The third service element can be the terminal's primary SN or secondary SN.

[0226] Furthermore, the method further includes: the MN performing at least one of the following:

[0227] Receive configuration information for multiple SCGs sent by the source SN;

[0228] Send configuration information for multiple SCGs to the target SN;

[0229] Receive configuration information for multiple SCGs sent by the source master SN;

[0230] Send configuration information for multiple SCGs to the target master SN.

[0231] Optionally, the source SN can also directly send the configuration information of multiple SCGs to the target SN. Alternatively, the source master SN can also directly send the configuration information of multiple SCGs to the target master SN. Specifically, the source SN sends the configured multiple SCGs to the MN, and the MN passes the configuration to the target SN (e.g., in a multi-SCG scenario of an intra-gNB).

[0232] The source primary SN sends the configuration information of the secondary SN to the MN, and the MN passes the configuration information of the secondary SN to the target primary SN (for example, in the multi-SCG scenario of inter-gNB, the primary SN controls the secondary SN).

[0233] Please see Figure 4 , Figure 4 This is a flowchart of a multi-auxiliary cell group configuration method provided in an embodiment of this application. The multi-auxiliary cell group configuration method includes:

[0234] Step 401: The secondary node SN sends target configuration information to the terminal. The target configuration information is used to configure at least one secondary cell group (SCG) for the terminal.

[0235] It is understandable that the phrase "for configuring multiple secondary cell groups (SCGs) for the terminal" can be interpreted as follows: before the SN sends the target configuration information to the terminal, it may already be in dual-connectivity mode, i.e., it has one SCG. Then, the SN configures an additional SCG for the terminal through the target configuration information, ultimately resulting in the terminal being configured with multiple SCGs.

[0236] After receiving the target configuration information, the terminal can perform a target configuration operation based on the target configuration information to configure multiple SCGs. For example, the terminal can perform at least one of the following operations based on the target configuration information:

[0237] SCG creation operation;

[0238] Adding an SCG;

[0239] SCG modification operations;

[0240] SCG release operation;

[0241] SCG activation operation;

[0242] Deactivation of SCG;

[0243] SCG's sleep operation;

[0244] SCG switching operation.

[0245] In this embodiment, the SN can be a primary SN or a secondary SN. When the SN communicates with the primary SN, the SN can be considered a secondary SN; when the SN communicates with the secondary SN, the SN can be considered a primary SN; when the SN communicates with the terminal, the SN can be considered a primary SN; when the SN communicates with the MN, the SN can be considered a primary SN (e.g., SN addition process, SN modification process, SN release process). In some cases, the SN can also be a secondary SN (e.g., SN modification process, SN release process).

[0246] In this embodiment, the secondary node (SN) sends target configuration information to the terminal. This target configuration information is used to configure at least one secondary cell group (SCG) for the terminal. The terminal can configure multiple SCGs based on the target configuration information sent by the SN, thus improving the terminal's communication performance.

[0247] Furthermore, the target configuration information is used to indicate at least one of the following:

[0248] Should the terminal be configured in multi-connection mode?

[0249] Should the terminal be configured as a multi-SCG mode?

[0250] Whether to configure the current secondary node SN of the terminal as the primary SN;

[0251] The number of SCGs;

[0252] The addition of at least one SCG;

[0253] Release of at least one SCG;

[0254] At least one SCG modification;

[0255] At least one SCG wireless access type;

[0256] Configuration information for at least one SCG;

[0257] The identifier of the SCG being activated for the first time;

[0258] The default SCG identifier;

[0259] The identifier for a dormant SCG.

[0260] Furthermore, the configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, the configuration of which is used to indicate at least one of the following:

[0261] Logical channel identifier;

[0262] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0263] The first radio bearer associated with the RLC radio bearer;

[0264] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0265] Furthermore, the target configuration information is used to configure a second radio bearer, which is a radio bearer associated with a first serving network element, and the first serving network element is used to provide additional resources on the basis of dual connectivity.

[0266] Furthermore, the configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0267] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0268] Furthermore, the auxiliary node SN sends target configuration information to the terminal, including at least one of the following:

[0269] The SN sends the target configuration information through the configured first SCG, and the target configuration information is used to configure a second SCG other than the first SCG for the terminal.

[0270] The SN sends the target configuration information through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

[0271] Furthermore, the target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

[0272] Furthermore, before the SN sends the target configuration information to the terminal, the method also includes an SN addition process (initiated by the MN), that is, the SN receives an SN addition request message sent by the master node MN, the SN addition request message being used to request the SN to configure the resources required by the terminal in multi-connection or multi-SCG mode.

[0273] Furthermore, the SN add request message is also used to indicate at least one of the following:

[0274] Indicates whether the MN supports configuring multiple SCGs or multiple connection modes for the terminal;

[0275] The request is to configure the SN with multiple SCGs;

[0276] Indicates the desired configuration or initial state of the plurality of SCGs;

[0277] Request the radio bearer information configured in the SN;

[0278] The configuration information of the SCG that has been configured on the terminal is indicated;

[0279] Indicates the radio bearer configuration information of the terminal for other serving network elements besides the SN;

[0280] Indicates the capability information of the terminal;

[0281] Indicates resource collaboration information in the multi-connection mode of the terminal;

[0282] The request is to restore the wireless links of the terminal to other network elements in the multi-connection mode via the SN.

[0283] Furthermore, before the SN sends the target configuration information to the terminal, the method further includes: the SN sending a first response message to the MN regarding the SN addition request message, the first response message being used to indicate whether the SN addition request is accepted or rejected.

[0284] Furthermore, the method further includes: the SN receiving a first request sent by the MN, the first request being used to request that the SN be configured as a primary SN.

[0285] The first request is carried by at least one of the following:

[0286] Add a request message to the SN;

[0287] SN modification request message;

[0288] Main SN request message.

[0289] Furthermore, the first request carries the configuration information of the SCG already configured by the terminal. Optionally, the MN may also send the SCG configuration information of other SNs of the UE to the second target network element in the first request, or send it to the second target network element after receiving acceptance from the second target network element as a primary SN response.

[0290] Furthermore, after the SN receives the first request sent by the MN, the method further includes: the SN sending a second response message to the MN, the second response message being used to indicate whether to accept or reject configuring the SN as the main SN.

[0291] Furthermore, the method also includes an SN modification process: the SN sends a second request to the MN, the second request being sent to the MN by either the primary SN or the secondary SN, for requesting at least one of the following:

[0292] The MN initiates a path update process to the core network;

[0293] Switch the user plane function UPF path of the terminal from the SN to another SN of the terminal, or switch the terminal from another SN to the SN.

[0294] Furthermore, the method also includes an SN release procedure (initiated by the master SN): the SN sends a first indication message to the MN, the first indication message indicating the following:

[0295] Release all secondary cell groups configured in the SN;

[0296] Release a portion of the secondary cell group configured by the SN;

[0297] The release information of other service network elements of the terminal besides the SN, such as the release information of the secondary SN indicated by the primary SN to the MN.

[0298] Furthermore, the method also includes: the SN sending configuration information of multiple SCGs to the MN.

[0299] Furthermore, the method also includes an SN addition process (initiated by the primary SN): the SN sends a second SN addition request message to the secondary SN, the second SN addition request message being used to request the secondary SN to configure the resources required by the terminal in multi-connection or multi-SCG mode.

[0300] The second SN addition request message can be an SN addition request message sent from MN to SN, or it can be a newly defined SN addition request message.

[0301] The second SN adds a request message to indicate at least one of the following:

[0302] MCG configuration;

[0303] SCG configuration information configured in the main SN;

[0304] UE capability coordination information;

[0305] Security key information;

[0306] Is the SN addition process initiated by MN or the SN addition process initiated by the main SN?

[0307] The desired number of SCGs to be configured.

[0308] Furthermore, the method also includes an SN release procedure (initiated by the secondary SN): the SN sends a second indication message to the primary SN, the second indication message indicating one of the following:

[0309] Release all secondary cell groups configured in the SN;

[0310] Release a portion of the secondary cell group configured by the SN, optionally indicating the ID of the released SCG.

[0311] The following provides an example of the configuration method provided in this application.

[0312] In the first method, MN controls the addition, reconfiguration, and release operations of multiple SCGs:

[0313] Step 11: When the UE receives an RRC message (e.g., an RRC reconfiguration message) from the MN, which carries a first information container (e.g., mrmc-SecondaryCellGroupSet IE), the terminal will configure its working mode to multi-connection mode or multi-SCG mode.

[0314] Step 12: Based on the first information container, the UE performs at least one of the following:

[0315] 1) If the first information container carries an establishment instruction, the UE performs the establishment of multiple SCGs.

[0316] 2) If the first information container carries a release instruction, the UE performs the release of multiple SCGs, or cancels the multi-connection or multi-SCG working mode; the release instruction can be a release only, or a release followed by addition.

[0317] 3) If the first information container carries SCG configurations corresponding to different RAT types (e.g., SecondaryCellGroupNR, SecondaryCellGroupEUTRA, etc. IE), then the UE performs SCG configuration operations for each RAT type.

[0318] 4) If the first information container carries an SCG addition and modification list, the UE performs multiple SCG addition and / or modification operations. Each item in the list corresponds to an SCG, which can be identified by an SCG ID. When the terminal receives this list, if any item is an SCG not currently configured in the terminal's configuration, the terminal performs an SCG addition operation; if any item is an SCG already configured in the terminal, the terminal performs an SCG modification operation.

[0319] 5) If the first information container carries an SCG release list, this list may consist of multiple SCG IDs. The terminal will delete the relevant configuration of the SCG indicated by the SCG ID.

[0320] 6) If the first information container indicates the identifier of the first activated SCG (e.g., FirstActiveSCGId), the UE saves the identifier. Optionally, the SCG indicated by FirstActiveSCGId is activated immediately to activate other SCGs. Optionally, the UE immediately activates the SCG indicated by FirstActiveSCGId when one of the following conditions is met:

[0321] When the terminal receives an RRC Resume message;

[0322] When the terminal initiates an RRC resume;

[0323] When the terminal completes the RRC resume process;

[0324] When the terminal receives the MN handover command;

[0325] When the terminal handover is complete;

[0326] When the terminal execution condition changes;

[0327] When the SCG currently being used by the terminal fails. These failure conditions include Radio Link Failure (RLF), Synchronization Reconfiguration Failure, etc.

[0328] When the network reconfigures the FirstActiveSCGId parameter.

[0329] 7) Perform an SCG switch; for example, switch from the currently active SCG to the SCG indicated by FirstActiveSCGId or another SCG;

[0330] Optionally, the first information container described above may contain RRC messages (such as RRC reconfiguration messages) or OCTET STRING.

[0331] The second approach involves the SN controlling the addition, reconfiguration, and release operations of at least one SCG (defining a new SCG information container):

[0332] Step 21: After receiving the mrdc-SecondaryCellGroup IE, the terminal is configured to DC mode;

[0333] Step 22: The terminal receives an RRC message (e.g., an RRC reconfiguration message) from the SCG, which carries a second information container (e.g., AdditionalSecondaryCellGroup IE). Optionally, after receiving this container, the terminal configures itself to multi-connection mode or multi-SCG mode. Optionally, the second information container may contain instructions for establishing, releasing, adding, or modifying the SCG, the RAT type, and the SCG ID. Specific methods for this can refer to the first approach and will not be elaborated here. Optionally, upon receiving the second information container, the terminal configures its current SN as the primary SN and / or configures the SCG used to receive the container as the primary SCG.

[0334] The third approach involves the SN controlling all SCG addition, reconfiguration, and release operations (reusing the legacy MRDC information container):

[0335] After receiving the mrdc-SecondaryCellGroup IE from the network side, the terminal executes at least one of the following:

[0336] If the mrdc-SecondaryCellGroup IE is carried in the RRC message generated by the MN, the UE will perform the relevant MR-DC configuration based on this IE, such as adding, modifying, or releasing SCGs.

[0337] If the mrdc-SecondaryCellGroup IE is carried in the RRC message generated by the SN (optionally, received from SRB3 but not included in the DLInformationTransferMRDC), the UE performs the relevant MR-MC (multiple connections or multiple SCGs) configuration based on this IE, such as adding, modifying, or releasing multiple SCGs. Optionally, in this case, the terminal configures the current SN as the primary SN and / or configures the SCG used to receive the mrdc-SecondaryCellGroup IE as the primary SCG.

[0338] Optionally, a response message can be sent to the SN.

[0339] The fourth method involves reconfiguring multiple SCGs during the RRC resume process:

[0340] Step 31: The UE is configured with multiple SCGs;

[0341] Step 32: The UE is released to the RRC inactive state by the network side, which instructs the UE to release or save several SCGs. For example, it instructs the UE to release a certain SCG (which can be represented by the SCG ID), or instructs the UE to save a certain SCG.

[0342] Step 33: During the RRC inactive state, the UE saves the configuration of several SCGs according to the configuration;

[0343] Step 34: The UE sends an RRC resume request message;

[0344] Step 35: The UE receives an RRC resume message, which indicates at least one of the following:

[0345] 1) Configuration of multiple SCGs (see the RRC reconfiguration case in the first method);

[0346] 2) Restore SCG ID, indicating which SCGs to restore;

[0347] 3) The ID of the SCG to be activated immediately; optionally, if not indicated, the UE activates the SCG indicated by FirstActiveSCGId. Alternatively, all SCGs are in a deactivated state by default.

[0348] Step 36: The UE sends an RRC resume complete message.

[0349] In the fifth method, the RRC message is configured with a third message container.

[0350] Step 41: The UE receives RadioBearerConfig, and the terminal configures a first radio bearer. The first radio bearer is a first serving network element (e.g., if RadioBearerConfig indicates master, then the first serving network element is MN) that configures several SRBs and several DRBs for the terminal. Specifically, RadioBearerConfig contains the SDAP and / or PDCP layer configuration parameters for these several SRBs and several DRBs;

[0351] Step 42: The UE receives RadioBearerConfig2, and the terminal configures a second radio bearer. The second radio bearer is a second serving network element (e.g., if RadioBearerConfig's keytouse indicates Secondary, then the second serving network element is the first SN or primary SN) that configures several SRBs and several DRBs for the terminal. Specifically, RadioBearerConfig2 contains the SDAP and / or PDCP layer configuration parameters for these several SRBs and several DRBs;

[0352] Step 43: The UE configures a third radio bearer based on a third information container (e.g., RadioBearerConfigExt). This third radio bearer is a set of SRBs and DRBs configured for the terminal by a third serving network element (e.g., if the keytouse indicator in RadioBearerConfigExt is Secondary and keytouseSCG IE appears and is set to a certain value (e.g., 2), then the third serving network element is a second SN or a secondary SN). Specifically, RadioBearerConfigExt contains the SDAP and / or PDCP layer configuration parameters for these SRBs and DRBs.

[0353] Optionally, all serving network elements of the terminal can use RadioBearerConfig, RadioBearerConfig2, and RadioBearerConfigExt to configure their own radio bearers. For example, an MN or several SNs can use RadioBearerConfigExt to configure their own radio bearers, as long as the RadioBearerConfigExt clearly indicates which serving network element the radio bearer is associated with (e.g., indicating the key of the radio bearer).

[0354] Optionally, in the second and third methods, the SCG configuration indicates which network element, PDCP entity, key, or radio bearer the configured SCG is associated with. For example, the SCG configuration indicates the identifier of the serving radio bearer SRB or DRB for a specific RLC bearer or RLC entity. The RLC bearer or RLC entity in the terminal's MCG configuration and / or the first SCG configuration can also be associated with the radio bearer configured in RadioBearerConfigExt.

[0355] The sixth method is for MN to request SN as the primary SN.

[0356] Step 51: The MN sends a first request to the SN, requesting that the SN be configured as the UE's primary SN. The first request can be made when the SN is added, or it can be initiated after the SN is added;

[0357] Step 52: The SN sends a response to the MN, indicating whether it accepts the first request, that is, whether it accepts the SN as the terminal.

[0358] The seventh method is the SN addition process initiated by the primary SN:

[0359] Step 61: The primary SN sends an SN addition request to the secondary SN. Optionally, this request may include UE capabilities and MCG configuration information.

[0360] Step 62: The secondary SN sends an SN addition request acknowledge message to the primary SN, which carries SCG configuration information;

[0361] Step 63: The primary SN sends an SCG activation request to the secondary SN;

[0362] Step 64: After receiving confirmation of the SCG activation request from the secondary SN, the primary SN initiates an SN modification procedure to the MN, indicating the SN PDCP termination change. Further, it indicates the path information of the secondary SN;

[0363] Step 65: MN initiates path update process;

[0364] Step 66: The UPF switches the connection from the primary SN to the secondary SN.

[0365] The eighth method involves the MN transmitting the configuration of multiple SCGs during the main SN handover process.

[0366] Step 71: The source primary SN sends the configuration of multiple SCGs to the MN;

[0367] Step 72: The MN sends the configurations of multiple SCGs to the target primary SN;

[0368] Step 73: The target master SN sends a full configuration or a delta configuration of multiple SCGs to the terminal based on the configuration of the multiple SCGs.

[0369] Optionally, the source primary SN can also send a first request to a network element, requesting that the network element to act as the primary SN. After receiving the network element's acceptance response to the first request, the source primary SN directly sends the configuration of multiple SCGs to that network element, which will also become the target primary SN of the terminal.

[0370] The configuration method provided in this application can improve the flexibility of configuring multiple SCGs on the network side to adapt to different network deployments.

[0371] Please see Figure 5 , Figure 5 This is a structural diagram of a multi-auxiliary cell group configuration device provided in an embodiment of this application. The first multi-auxiliary cell group configuration device 500 includes:

[0372] The receiving module 501 is used to receive target configuration information, which is used to configure at least one secondary cell group (SCG) for the terminal.

[0373] The execution module 502 is used to perform a target configuration operation based on the target configuration information, so that the terminal is configured with multiple SCGs.

[0374] Furthermore, the target configuration information is used to indicate at least one of the following:

[0375] Should the terminal be configured in multi-connection mode?

[0376] Should the terminal be configured as a multi-SCG mode?

[0377] Whether to configure the current secondary node SN of the terminal as the primary SN;

[0378] The number of SCGs;

[0379] The addition of at least one SCG;

[0380] Release of at least one SCG;

[0381] At least one SCG modification;

[0382] At least one SCG wireless access type;

[0383] Configuration information for at least one SCG;

[0384] The identifier of the SCG being activated for the first time;

[0385] The default SCG identifier;

[0386] The identifier for a dormant SCG.

[0387] Furthermore, the configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, the configuration of which is used to indicate at least one of the following:

[0388] Logical channel identifier;

[0389] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0390] The first radio bearer associated with the RLC radio bearer;

[0391] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0392] Furthermore, the target configuration information is used to configure a second radio bearer, which is a radio bearer associated with a first serving network element, and the first serving network element is used to provide additional resources on the basis of dual connectivity.

[0393] Furthermore, the configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0394] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0395] Furthermore, the target configuration information is received through at least one of the following:

[0396] The target configuration information is received via MCG;

[0397] The target configuration information is received through the configured first SCG, and the target configuration information is used to configure a second SCG other than the first SCG for the terminal.

[0398] The target configuration information is received through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

[0399] Furthermore, the target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single-connection mode.

[0400] Furthermore, the execution module is configured to perform at least one of the following operations based on the first information container:

[0401] Configure the terminal to a multi-connection mode or a multi-SCG mode;

[0402] Perform at least one configuration operation for an SCG.

[0403] Furthermore, the target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

[0404] Furthermore, the execution module is configured to allow the terminal to perform at least one of the following operations based on the second information container:

[0405] Configure the terminal to a multi-connection mode or a multi-SCG mode;

[0406] Perform at least one configuration operation for an SCG.

[0407] Furthermore, the target configuration operation includes at least one of the following operations:

[0408] SCG creation operation;

[0409] Adding an SCG;

[0410] SCG modification operations;

[0411] SCG release operation;

[0412] SCG activation operation;

[0413] Deactivation of SCG;

[0414] SCG's sleep operation;

[0415] SCG switching operation.

[0416] Furthermore, the device also includes a sending module for sending response messages.

[0417] Furthermore, the response message includes a fourth information container, which is used to indicate the terminal's response to the first service network element.

[0418] The first multi-auxiliary cell group configuration device 500 in the embodiments of this application can be a device, or it can be a component, integrated circuit, or chip in a terminal.

[0419] The first multi-auxiliary cell group configuration device 500 in this embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this embodiment does not specifically limit its use.

[0420] The first multi-auxiliary cell group configuration device 500 provided in this application embodiment can achieve Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0421] Please see Figure 6 , Figure 6 This is a structural diagram of a multi-auxiliary cell group configuration device provided in an embodiment of this application. The second multi-auxiliary cell group configuration device 600 includes:

[0422] The first sending module 601 is used to send target configuration information to the terminal, wherein the target configuration information is used to configure at least one secondary cell group (SCG) for the terminal.

[0423] Furthermore, the target configuration information is used to indicate at least one of the following:

[0424] Should the terminal be configured in multi-connection mode?

[0425] Should the terminal be configured as a multi-SCG mode?

[0426] Whether to configure the current secondary node SN of the terminal as the primary SN;

[0427] The number of SCGs;

[0428] The addition of at least one SCG;

[0429] Release of at least one SCG;

[0430] At least one SCG modification;

[0431] At least one SCG wireless access type;

[0432] Configuration information for at least one SCG;

[0433] The identifier of the SCG being activated for the first time;

[0434] The default SCG identifier;

[0435] The identifier for a dormant SCG.

[0436] Furthermore, the configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, the configuration of which is used to indicate at least one of the following:

[0437] Logical channel identifier;

[0438] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0439] The first radio bearer associated with the RLC radio bearer;

[0440] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0441] Furthermore, the target configuration information is used to configure a second radio bearer, which is a radio bearer associated with a first serving network element, and the first serving network element is used to provide additional resources on the basis of dual connectivity.

[0442] Furthermore, the configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0443] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0444] Furthermore, the first sending module is configured to:

[0445] The MN sends the target configuration information via the MCG.

[0446] Furthermore, the target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single-connection mode.

[0447] Furthermore, the target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

[0448] Furthermore, the device also includes:

[0449] The second sending module is used to send a secondary node (SN) addition request message to the first target network element. The SN addition request message is used to request the first target network element to configure the resources required by the terminal in multi-connection or multi-SCG mode.

[0450] Furthermore, the SN add request message is also used to indicate at least one of the following:

[0451] Indicates whether the MN supports configuring multiple SCGs or multiple connection modes for the terminal;

[0452] Request the first target network element to configure multiple SCGs;

[0453] Indicates the desired configuration or initial state of the plurality of SCGs;

[0454] Request the radio bearer information configured in the first target network element;

[0455] The configuration information of the SCG that has been configured on the terminal is indicated;

[0456] Indicates the radio bearer configuration information of the terminal for other serving network elements besides the first target network element;

[0457] Indicates the capability information of the terminal;

[0458] Indicates resource collaboration information in the multi-connection mode of the terminal;

[0459] The request is to restore the wireless links of the terminal to other network elements in the multi-connection mode through the first target network element.

[0460] Furthermore, the device also includes a first receiving module, configured to receive a first response message from the first target network element to the SN addition request message, the first response message being used to indicate whether to accept or reject the SN addition request.

[0461] Furthermore, the device also includes a third sending module for sending a first request to the second target network element, the first request being used to request that the second target network element be configured as a master SN.

[0462] Furthermore, the device also includes a second receiving module for receiving a second response message sent by the second target network element, the second response message being used to indicate whether to accept or reject configuring the second target network element as a master SN.

[0463] Furthermore, the first request is carried by at least one of the following:

[0464] Add a request message to the SN;

[0465] SN modification request message;

[0466] Main SN request message.

[0467] Furthermore, the first request carries the configuration information of the SCG already configured on the terminal.

[0468] Furthermore, the device further includes a third receiving module, configured to receive a second request from a second serving network element of the terminal, the second request being for requesting at least one of the following:

[0469] The MN initiates a path update process to the core network;

[0470] Switch the user plane function UPF path of the terminal from SN to another SN of the terminal, or switch from another SN of the terminal to SN.

[0471] Furthermore, the device further includes a fourth receiving module, configured to receive first indication information sent by a third serving network element of the terminal, the first indication information indicating one of the following:

[0472] Release all secondary cell groups configured in the third serving network element;

[0473] Release a portion of the secondary cell group configured by the third service network element;

[0474] Release information of the terminal's other service network elements besides the third service network element.

[0475] Furthermore, the device also includes an execution module for performing at least one of the following:

[0476] Receive configuration information for multiple SCGs sent by the source SN;

[0477] Send configuration information for multiple SCGs to the target SN;

[0478] Receive configuration information for multiple SCGs sent by the source master SN;

[0479] Send configuration information for multiple SCGs to the target master SN.

[0480] The second multi-auxiliary cell group configuration device 600 provided in this application embodiment can achieve Figure 3 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0481] Please see Figure 7 , Figure 7 This is a structural diagram of a multi-auxiliary cell group configuration device provided in an embodiment of this application. The third multi-auxiliary cell group configuration device 700 includes:

[0482] The second sending module 701 is used to send target configuration information to the terminal, wherein the target configuration information is used to configure at least one secondary cell group (SCG) for the terminal.

[0483] Furthermore, the target configuration information is used to indicate at least one of the following:

[0484] Should the terminal be configured in multi-connection mode?

[0485] Should the terminal be configured as a multi-SCG mode?

[0486] Whether to configure the current secondary node SN of the terminal as the primary SN;

[0487] The number of SCGs;

[0488] The addition of at least one SCG;

[0489] Release of at least one SCG;

[0490] At least one SCG modification;

[0491] At least one SCG wireless access type;

[0492] Configuration information for at least one SCG;

[0493] The identifier of the SCG being activated for the first time;

[0494] The default SCG identifier;

[0495] The identifier for a dormant SCG.

[0496] Furthermore, the configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, the configuration of which is used to indicate at least one of the following:

[0497] Logical channel identifier;

[0498] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0499] The first radio bearer associated with the RLC radio bearer;

[0500] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0501] Furthermore, the target configuration information is used to configure a second radio bearer, which is a radio bearer associated with a first serving network element, and the first serving network element is used to provide additional resources on the basis of dual connectivity.

[0502] Furthermore, the configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0503] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0504] Furthermore, the target configuration information is sent via at least one of the following:

[0505] The SN sends the target configuration information through the configured first SCG, and the target configuration information is used to configure a second SCG other than the first SCG for the terminal.

[0506] The SN sends the target configuration information through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

[0507] Furthermore, the device also includes a first receiving module, configured to receive an SN add request message sent by the master node MN, the SN add request message being used to request the SN to configure the resources required by the terminal in multi-connection or multi-SCG mode.

[0508] Furthermore, the SN add request message is also used to indicate at least one of the following:

[0509] Indicates whether the MN supports configuring multiple SCGs or multiple connection modes for the terminal;

[0510] The request is to configure the SN with multiple SCGs;

[0511] Indicates the desired configuration or initial state of the plurality of SCGs;

[0512] Request the radio bearer information configured in the SN;

[0513] The configuration information of the SCG that has been configured on the terminal is indicated;

[0514] Indicates the radio bearer configuration information of the terminal for other serving network elements besides the SN;

[0515] Indicates the capability information of the terminal;

[0516] Indicates resource collaboration information in the multi-connection mode of the terminal;

[0517] The request is to restore the wireless links of the terminal to other network elements in the multi-connection mode via the SN.

[0518] Furthermore, the device also includes a third sending module for sending a first response message to the MN of the SN addition request message, the first response message being used to indicate acceptance or rejection of the SN addition request.

[0519] Furthermore, the device also includes a second receiving module for receiving a first request sent by the MN, the first request being for requesting that the SN be configured as the master SN.

[0520] Furthermore, the device also includes a fourth sending module for sending a second response message to the MN, the second response message being used to indicate whether to accept or reject configuring the SN as the master SN.

[0521] Furthermore, the first request is carried by at least one of the following:

[0522] Add a request message to the SN;

[0523] SN modification request message;

[0524] Main SN request message.

[0525] Furthermore, the first request carries the configuration information of the SCG already configured on the terminal.

[0526] Furthermore, the device also includes a fifth sending module for sending a second request to the MN, the second request being for requesting at least one of the following:

[0527] The MN initiates a path update process to the core network;

[0528] Switch the user plane function UPF path of the terminal from the SN to another SN of the terminal, or switch the terminal from another SN to the SN.

[0529] Furthermore, the device also includes a sixth transmitting module for transmitting first indication information to the MN, the first indication information indicating one of the following:

[0530] Release all secondary cell groups configured in the SN;

[0531] Release a portion of the secondary cell group configured by the SN;

[0532] Release information of the terminal's other service network elements besides the SN.

[0533] Furthermore, the device also includes a seventh transmitting module for transmitting configuration information of multiple SCGs to the MN.

[0534] Furthermore, the device also includes an eighth sending module, configured to send a second SN add request message to the second SN, the second SN add request message being used to request the second SN to configure the resources required by the terminal in multi-connection or multi-SCG mode.

[0535] The third multi-auxiliary cell group configuration device 700 provided in this application embodiment can achieve Figure 4 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0536] Optional, such as Figure 8 As shown, this application embodiment also provides a communication device 80, including a processor 81, a memory 82, and a program or instructions stored in the memory 82 and executable on the processor 81. For example, when the communication device 80 is a terminal, the program or instructions executed by the processor 81 implement the above-mentioned... Figure 2 The various processes of the multi-auxiliary cell group configuration method embodiment shown can achieve the same technical effect. When the communication device 80 is a network node, the program or instruction executed by the processor 81 implements the above. Figure 3 or Figure 4 The various processes of the multi-auxiliary cell group configuration method embodiment shown can achieve the same technical effect.

[0537] Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0538] The terminal 1000 includes, but is not limited to, the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0539] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0540] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0541] In this embodiment, the radio frequency unit 1001 receives downlink data from the network-side device and processes it for the processor 1010; additionally, it sends uplink data to the base station. Typically, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0542] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0543] Processor 1010 may include one or more processing units; optionally, processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1010.

[0544] The radio frequency unit 1001 is used to receive target configuration information, which is used to configure at least one secondary cell group (SCG) for the terminal.

[0545] The processor 1010 is configured to perform a target configuration operation based on the target configuration information, so that the terminal is configured with multiple SCGs.

[0546] Furthermore, the target configuration information is used to indicate at least one of the following:

[0547] Should the terminal be configured in multi-connection mode?

[0548] Should the terminal be configured as a multi-SCG mode?

[0549] Whether to configure the current secondary node SN of the terminal as the primary SN;

[0550] The number of SCGs;

[0551] The addition of at least one SCG;

[0552] Release of at least one SCG;

[0553] At least one SCG modification;

[0554] At least one SCG wireless access type;

[0555] Configuration information for at least one SCG;

[0556] The identifier of the SCG being activated for the first time;

[0557] The default SCG identifier;

[0558] The identifier for a dormant SCG.

[0559] Furthermore, the configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, the configuration of which is used to indicate at least one of the following:

[0560] Logical channel identifier;

[0561] The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer;

[0562] The first radio bearer associated with the RLC radio bearer;

[0563] The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

[0564] Furthermore, the target configuration information is used to configure a second radio bearer, which is a radio bearer associated with a first serving network element, and the first serving network element is used to provide additional resources on the basis of dual connectivity.

[0565] Furthermore, the configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0566] Furthermore, the configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

[0567] Furthermore, the target configuration information is received through at least one of the following:

[0568] The target configuration information is received via MCG;

[0569] The target configuration information is received through the configured first SCG, and the target configuration information is used to configure a second SCG other than the first SCG for the terminal.

[0570] The target configuration information is received through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

[0571] Furthermore, the target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single-connection mode.

[0572] Furthermore, the processor 1010 is configured to perform at least one of the following operations based on the first information container:

[0573] Configure the terminal to a multi-connection mode or a multi-SCG mode;

[0574] Perform at least one configuration operation for an SCG.

[0575] Furthermore, the target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

[0576] Furthermore, the processor 1010 is configured to perform at least one of the following operations based on the second information container:

[0577] Configure the terminal to a multi-connection mode or a multi-SCG mode;

[0578] Perform at least one configuration operation for an SCG.

[0579] Furthermore, the target configuration operation includes at least one of the following operations:

[0580] SCG creation operation;

[0581] Adding an SCG;

[0582] SCG modification operations;

[0583] SCG release operation;

[0584] SCG activation operation;

[0585] Deactivation of SCG;

[0586] SCG's sleep operation;

[0587] SCG switching operation.

[0588] Furthermore, the radio frequency module 1001 is also used to: send a response message.

[0589] Furthermore, the response message includes a fourth information container, which is used to indicate the terminal's response to the first service network element.

[0590] The terminal 1000 provided in the above embodiments can achieve Figure 2The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0591] Specifically, embodiments of this application also provide a network node (also known as a network-side device). For example... Figure 10 As shown, the network-side device 900 includes an antenna 91, a radio frequency (RF) device 92, and a baseband device 93. The antenna 91 is connected to the RF device 92. In the uplink direction, the RF device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be transmitted and sends it to the RF device 92. The RF device 92 processes the received information and then transmits it through the antenna 91.

[0592] The aforementioned frequency band processing device can be located in the baseband device 93. The method executed by the master node MN or the auxiliary node SN in the above embodiments can be implemented in the baseband device 93, which includes a processor 94 and a memory 95.

[0593] Baseband device 93 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 10 As shown, one of the chips, for example, is a processor 94, which is connected to a memory 95 to call the program in the memory 95 and execute the network device operation shown in the above method embodiment.

[0594] The baseband device 93 may also include a network interface 96 for exchanging information with the radio frequency device 92, such as a common public radio interface (CPRI).

[0595] Specifically, the network node in this embodiment of the invention further includes: instructions or programs stored in memory 95 and executable on processor 94, wherein processor 94 calls the instructions or programs in memory 95 to execute. Figure 6 or Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0596] This application embodiment also provides a readable storage medium storing a program or instructions that are executed by a processor. Figure 2 or Figure 3 The various processes in the method embodiments described herein can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0597] The processor mentioned above is the processor in the terminal or network node described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0598] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run network node programs or instructions to achieve the above. Figure 2 , Figure 3 The processes in the four method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0599] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0600] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0601] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network, etc.) to execute the methods described in the various embodiments of this application.

[0602] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for configuring multiple auxiliary cell groups, characterized in that, include: The terminal receives target configuration information, which is used to configure at least one secondary cell group (SCG) for the terminal. The terminal performs a target configuration operation based on the target configuration information, so that the terminal can configure multiple SCGs; The target configuration information is used to indicate at least one of the following: Whether to configure the current secondary node SN of the terminal as the primary SN; The identifier of the SCG being activated for the first time; The default SCG identifier; wherein, the default SCG identifier is the identifier of the SCG that the terminal switches to when no downlink scheduling and / or no uplink transmission is received on the currently working SCG; The identifier of the SCG that is activated for the first time is the identifier of the SCG activated by the terminal if at least one of the following conditions is met: The terminal receives a Radio Link Control (RRC) recovery message; The terminal initiates an RRC recovery; The terminal completes the RRC recovery process; The terminal receives a switch command from the master node MN; The terminal switching is complete; The terminal performs condition switching; The SCG currently being used by the terminal has failed. The identifier parameters of the SCG that is activated for the first time during network reconfiguration; Receive the first information container and configure multiple SCG configurations; The terminal is configured for multiple connections or multiple SCG modes.

2. The method of claim 1, wherein, The target configuration information is also used to indicate at least one of the following: At least one SCG wireless access type; The identifier for a dormant SCG; Should the terminal be configured in multi-connection mode? Should the terminal be configured as a multi-SCG mode? The number of SCGs; The addition of at least one SCG; Release of at least one SCG; At least one SCG modification; Configuration information for at least one SCG.

3. The method according to claim 2, characterized in that, The configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, and the configuration of the RLC radio bearer is used to indicate at least one of the following: Logical channel identifier; The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer; The first radio bearer associated with the RLC radio bearer; The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

4. The method according to claim 1, characterized in that, The target configuration information is used to configure the second radio bearer, which is a radio bearer related to the first serving network element. The first serving network element is used to provide additional resources on the basis of dual connectivity.

5. The method according to claim 3, characterized in that, The configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

6. The method according to claim 4, characterized in that, The configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

7. The method according to claim 1, characterized in that, The terminal receives target configuration information, including at least one of the following: The target configuration information is received via MCG; The target configuration information is received through the configured first SCG, and the target configuration information is used to configure a second SCG other than the first SCG for the terminal. The target configuration information is received through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

8. The method according to claim 1, characterized in that, The target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single connection mode.

9. The method according to claim 8, characterized in that, The terminal performs a target configuration operation based on the target configuration information, so that the terminal configures multiple SCGs, including: The terminal performs at least one of the following operations based on the first information container: Configure the terminal to a multi-connection mode or a multi-SCG mode; Perform at least one configuration operation for an SCG.

10. The method according to claim 1, characterized in that, The target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

11. The method according to claim 10, characterized in that, The terminal performs a target configuration operation based on the target configuration information, so that the terminal configures multiple SCGs, including: The terminal performs at least one of the following operations based on the second information container: Configure the terminal to a multi-connection mode or a multi-SCG mode; Perform at least one configuration operation for an SCG.

12. The method according to claim 1, characterized in that, The target configuration operation includes at least one of the following operations: SCG creation operation; Adding an SCG; SCG modification operations; SCG release operation; SCG activation operation; Deactivation of SCG; SCG hibernation operation; SCG switching operation.

13. The method according to claim 1, characterized in that, After the terminal receives the target configuration information, the method further includes: The terminal sends a response message.

14. The method according to claim 13, characterized in that, The response message includes a fourth information container, which is used to indicate the terminal's response to the first service network element.

15. A method for configuring multiple auxiliary cell groups, characterized in that, The method includes: The master node (MN) sends target configuration information to the terminal, the target configuration information being used to configure at least one secondary cell group (SCG) for the terminal. The target configuration information is used to indicate at least one of the following: Whether to configure the current secondary node SN of the terminal as the primary SN; The identifier of the SCG being activated for the first time; The default SCG identifier; The default SCG identifier is the identifier of the SCG that the terminal switches to when there is no downlink scheduling and / or no uplink transmission on the currently working SCG. The identifier of the SCG that is activated for the first time is the identifier of the SCG activated by the terminal if at least one of the following conditions is met: The terminal received an RRC recovery message; The terminal initiates an RRC recovery; The terminal completes the RRC recovery process; The terminal receives the MN switching command; The terminal switching is complete; The terminal performs condition switching; The SCG currently being used by the terminal has failed. The identifier parameters of the SCG that is activated for the first time during network reconfiguration; Receive the first information container and configure multiple SCG configurations; The terminal is configured for multiple connections or multiple SCG modes.

16. The method according to claim 15, characterized in that, The target configuration information is also used to indicate at least one of the following: At least one SCG wireless access type; The identifier for a dormant SCG; Should the terminal be configured in multi-connection mode? Should the terminal be configured as a multi-SCG mode? The number of SCGs; The addition of at least one SCG; Release of at least one SCG; At least one SCG modification; Configuration information for at least one SCG.

17. The method according to claim 16, characterized in that, The configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, and the configuration of the RLC radio bearer is used to indicate at least one of the following: Logical channel identifier; The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer; The first radio bearer associated with the RLC radio bearer; The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

18. The method according to claim 15, characterized in that, The target configuration information is used to configure the second radio bearer, which is a radio bearer related to the first serving network element. The first serving network element is used to provide additional resources on the basis of dual connectivity.

19. The method according to claim 17, characterized in that, The configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

20. The method according to claim 18, characterized in that, The configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

21. The method according to claim 15, characterized in that, The master node MN sends target configuration information to the terminal, including: The MN sends the target configuration information via the MCG.

22. The method according to claim 15, characterized in that, The target configuration information includes a first information container, which is used to configure multiple SCGs for the terminal when the terminal is in single connection mode.

23. The method according to claim 15, characterized in that, The target configuration information includes a second information container, which is used to configure at least one SCG for the terminal when the terminal is in dual-connection mode.

24. The method according to claim 15, characterized in that, Before the MN sends the target configuration information to the terminal, the method further includes: The MN sends a secondary node (SN) add request message to the first target network element. The SN add request message is used to request the first target network element to configure the resources required by the terminal in multi-connection or multi-SCG mode.

25. The method according to claim 24, characterized in that, The SN add request message is also used to indicate at least one of the following: Indicates whether the MN supports configuring multiple SCGs or multiple connection modes for the terminal; Request the first target network element to configure multiple SCGs; Indicates the desired configuration or initial state of the plurality of SCGs; Request the radio bearer information configured in the first target network element; The configuration information of the SCG that has been configured on the terminal is indicated; Indicates the radio bearer configuration information of the terminal for other serving network elements besides the first target network element; Indicates the capability information of the terminal; Indicates resource collaboration information in the multi-connection mode of the terminal; The request is to restore the wireless links of the terminal to other network elements in the multi-connection mode through the first target network element.

26. The method according to claim 24, characterized in that, Before the MN sends the target configuration information to the terminal, the method further includes: The MN receives a first response message from the first target network element in response to the SN addition request message. The first response message is used to indicate whether to accept or reject the SN addition request.

27. The method according to claim 15, characterized in that, The method further includes: The MN sends a first request to the second target network element, the first request being used to request that the second target network element be configured as the master SN.

28. The method according to claim 27, characterized in that, After the MN sends the first request to the second target network element, the method further includes: The MN receives a second response message sent by the second target network element, the second response message being used to indicate whether to accept or reject configuring the second target network element as the main SN.

29. The method according to claim 27, characterized in that, The first request is carried by at least one of the following: Add a request message to the SN; SN modification request message; Main SN request message.

30. The method according to claim 27, characterized in that, The first request carries the configuration information of the SCG that the terminal has configured.

31. The method according to claim 15, characterized in that, The method further includes: The MN receives a second request from the second serving network element of the terminal, the second request being used to request at least one of the following: The MN initiates a path update process to the core network; Switch the user plane function UPF path of the terminal from SN to another SN of the terminal, or switch from another SN of the terminal to SN.

32. The method according to claim 15, characterized in that, The method further includes: The MN receives first indication information sent by the third serving network element of the terminal, the first indication information being used to indicate the following: Release all secondary cell groups configured in the third serving network element; Release a portion of the secondary cell group configured by the third service network element; Release information of the terminal's other service network elements besides the third service network element.

33. The method according to claim 15, characterized in that, The method further includes: the MN performing at least one of the following: The MN receives configuration information of multiple SCGs sent by the source SN; The MN sends configuration information for multiple SCGs to the target SN; The MN receives configuration information of multiple SCGs sent by the source master SN; The MN sends configuration information for multiple SCGs to the target master SN.

34. A method for configuring multiple auxiliary cell groups, characterized in that, The method includes: The secondary node SN sends target configuration information to the terminal, the target configuration information being used to configure at least one secondary cell group (SCG) for the terminal; The target configuration information is used to indicate at least one of the following: Whether to configure the current secondary node SN of the terminal as the primary SN; The identifier of the SCG being activated for the first time; The default SCG identifier; The default SCG identifier is the identifier of the SCG that the terminal switches to when there is no downlink scheduling and / or no uplink transmission on the currently working SCG. The identifier of the SCG that is activated for the first time is the identifier of the SCG activated by the terminal if at least one of the following conditions is met: The terminal received an RRC recovery message; The terminal initiates an RRC recovery; The terminal completes the RRC recovery process; The terminal receives the MN switching command; The terminal switching is complete; The terminal performs condition switching; The SCG currently being used by the terminal has failed. The identifier parameters of the SCG that is activated for the first time during network reconfiguration; Receive the first information container and configure multiple SCG configurations; The terminal is configured for multiple connections or multiple SCG modes.

35. The method according to claim 34, characterized in that, The target configuration information is also used to indicate at least one of the following: At least one SCG wireless access type; The identifier for a dormant SCG; Should the terminal be configured in multi-connection mode? Should the terminal be configured as a multi-SCG mode? The number of SCGs; The addition of at least one SCG; Release of at least one SCG; At least one SCG modification; Configuration information for at least one SCG.

36. The method according to claim 35, characterized in that, The configuration information corresponding to the SCG includes the configuration of at least one Radio Link Control (RLC) radio bearer, and the configuration of the RLC radio bearer is used to indicate at least one of the following: Logical channel identifier; The Packet Data Convergence Protocol (PDCP) entity associated with the RLC radio bearer; The first radio bearer associated with the RLC radio bearer; The PDCP entity or the first radio bearer is associated with a first serving network element, which is used to provide additional resources on top of dual connectivity.

37. The method according to claim 34, characterized in that, The target configuration information is used to configure the second radio bearer, which is a radio bearer related to the first serving network element. The first serving network element is used to provide additional resources on the basis of dual connectivity.

38. The method according to claim 36, characterized in that, The configuration of the first radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

39. The method according to claim 37, characterized in that, The configuration of the second radio bearer is carried through a third information container, which is used to carry the radio bearer configuration of at least one other serving network element of the terminal.

40. The method according to claim 34, characterized in that, The target configuration information is sent via at least one of the following: The SN sends the target configuration information through the configured first SCG, and the target configuration information is used to configure a second SCG other than the first SCG for the terminal. The SN sends the target configuration information through the configured second SCG, and the target configuration information is used to reconfigure the second SCG.

41. The method according to claim 34, characterized in that, Before the SN sends the target configuration information to the terminal, the method further includes: The SN receives an SN add request message sent by the master node MN. The SN add request message is used to request the SN to configure the resources required by the terminal in multi-connection or multi-SCG mode.

42. The method according to claim 41, characterized in that, The SN add request message is also used to indicate at least one of the following: Indicates whether the MN supports configuring multiple SCGs or multiple connection modes for the terminal; The request is to configure the SN with multiple SCGs; Indicates the desired configuration or initial state of the plurality of SCGs; Request the radio bearer information configured in the SN; The configuration information of the SCG that has been configured on the terminal is indicated; Indicates the radio bearer configuration information of the terminal for other serving network elements besides the SN; Indicates the capability information of the terminal; Indicates resource collaboration information in the multi-connection mode of the terminal; The request is to restore the wireless links of the terminal to other network elements in the multi-connection mode via the SN.

43. The method according to claim 41, characterized in that, Before the SN sends the target configuration information to the terminal, the method further includes: The SN sends a first response message to the MN regarding the SN addition request message, the first response message indicating whether to accept or reject the SN addition request.

44. The method according to claim 34, characterized in that, The method further includes: The SN receives a first request sent by the MN, the first request being used to request that the SN be configured as the primary SN.

45. The method according to claim 44, characterized in that, After the SN receives the first request sent by the MN, the method further includes: The SN sends a second response message to the MN, the second response message being used to indicate whether to accept or reject configuring the SN as the master SN.

46. ​​The method according to claim 44, characterized in that, The first request is carried by at least one of the following: Add a request message to the SN; SN modification request message; Main SN request message.

47. The method according to claim 44, characterized in that, The first request carries the configuration information of the SCG that the terminal has configured.

48. The method according to claim 34, characterized in that, The method further includes: The SN sends a second request to the MN, the second request being used to request at least one of the following: The MN initiates a path update process to the core network; Switch the user plane function UPF path of the terminal from the SN to another SN of the terminal, or switch the terminal from another SN to the SN.

49. The method according to claim 34, characterized in that, The method further includes: The SN sends a first indication message to the MN, the first indication message being used to indicate one of the following: Release all secondary cell groups configured in the SN; Release a portion of the secondary cell group configured by the SN; Release information of the terminal's other service network elements besides the SN.

50. The method according to claim 34, characterized in that, The method further includes: the SN sending configuration information of multiple SCGs to the MN.

51. The method according to claim 34, characterized in that, The method further includes: The SN sends a second SN add request message to the second SN, which requests the second SN to configure the resources required by the terminal in multi-connection or multi-SCG mode.

52. A multi-auxiliary cell group configuration device, characterized in that, include: The receiving module is used to receive target configuration information, which is used to configure at least one secondary cell group (SCG) for the terminal. An execution module is used to perform target configuration operations based on the target configuration information, so that the terminal can be configured with multiple SCGs; The target configuration information is used to indicate at least one of the following: Whether to configure the current secondary node SN of the terminal as the primary SN; The identifier of the SCG being activated for the first time; The default SCG identifier; The default SCG identifier is the identifier of the SCG that the terminal switches to when there is no downlink scheduling and / or no uplink transmission on the currently working SCG. The identifier of the SCG that is activated for the first time is the identifier of the SCG activated by the terminal if at least one of the following conditions is met: The terminal received an RRC recovery message; The terminal initiates an RRC recovery; The terminal completes the RRC recovery process; The terminal receives the MN switching command; The terminal switching is complete; The terminal performs condition switching; The SCG currently being used by the terminal has failed. The identifier parameters of the SCG that is activated for the first time during network reconfiguration; Receive the first information container and configure multiple SCG configurations; The terminal is configured for multiple connections or multiple SCG modes.

53. The apparatus according to claim 52, characterized in that, The target configuration information is also used to indicate at least one of the following: At least one SCG wireless access type; The identifier for a dormant SCG; Should the terminal be configured in multi-connection mode? Should the terminal be configured as a multi-SCG mode? The number of SCGs; The addition of at least one SCG; Release of at least one SCG; At least one SCG modification; Configuration information for at least one SCG.

54. A multi-auxiliary cell group configuration device, applied to a master node, characterized in that, include: The sending module is used to send target configuration information to the terminal, wherein the target configuration information is used to configure at least one secondary cell group (SCG) for the terminal. The target configuration information is used to indicate at least one of the following: Whether to configure the current secondary node SN of the terminal as the primary SN; The identifier of the SCG being activated for the first time; The default SCG identifier; The default SCG identifier is the identifier of the SCG that the terminal switches to when there is no downlink scheduling and / or no uplink transmission on the currently working SCG. The identifier of the SCG that is activated for the first time is the identifier of the SCG activated by the terminal if at least one of the following conditions is met: The terminal received an RRC recovery message; The terminal initiates an RRC recovery; The terminal completes the RRC recovery process; The terminal receives the MN switching command; The terminal switching is complete; The terminal performs condition switching; The SCG currently being used by the terminal has failed. The identifier parameters of the SCG that is activated for the first time during network reconfiguration; Receive the first information container and configure multiple SCG configurations; The terminal is configured for multiple connections or multiple SCG modes.

55. The apparatus according to claim 54, characterized in that, The target configuration information is also used to indicate at least one of the following: At least one SCG wireless access type; The identifier for a dormant SCG; Should the terminal be configured in multi-connection mode? Should the terminal be configured as a multi-SCG mode? The number of SCGs; The addition of at least one SCG; Release of at least one SCG; At least one SCG modification; Configuration information for at least one SCG.

56. A multi-auxiliary cell group configuration device, applied to auxiliary nodes, characterized in that, include: The sending module is used to send target configuration information to the terminal, wherein the target configuration information is used to configure at least one secondary cell group (SCG) for the terminal. The target configuration information is used to indicate at least one of the following: Whether to configure the current secondary node SN of the terminal as the primary SN; The identifier of the SCG being activated for the first time; The default SCG identifier; The default SCG identifier is the identifier of the SCG that the terminal switches to when there is no downlink scheduling and / or no uplink transmission on the currently working SCG. The identifier of the SCG that is activated for the first time is the identifier of the SCG activated by the terminal if at least one of the following conditions is met: The terminal received an RRC recovery message; The terminal initiates an RRC recovery; The terminal completes the RRC recovery process; The terminal receives the MN switching command; The terminal switching is complete; The terminal performs condition switching; The SCG currently being used by the terminal has failed. The identifier parameters of the SCG that is activated for the first time during network reconfiguration; Receive the first information container and configure multiple SCG configurations; The terminal is configured for multiple connections or multiple SCG modes.

57. The apparatus according to claim 56, characterized in that, The target configuration information is also used to indicate at least one of the following: At least one SCG wireless access type; The identifier for a dormant SCG; Should the terminal be configured in multi-connection mode? Should the terminal be configured as a multi-SCG mode? The number of SCGs; The addition of at least one SCG; Release of at least one SCG; At least one SCG modification; Configuration information for at least one SCG.

58. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the multi-auxiliary cell group configuration method as described in any one of claims 1 to 14.

59. A network node, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the multi-secondary cell group configuration method as described in any one of claims 15 to 33, or, when the program or instructions are executed by the processor, they implement the steps of the multi-secondary cell group configuration method as described in any one of claims 34 to 51.

60. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the multi-secondary cell group configuration method as described in any one of claims 1 to 14; or, when executed by a processor, the program or instructions implement the steps of the multi-secondary cell group configuration method as described in any one of claims 15 to 33; or, when executed by the processor, the program or instructions implement the steps of the multi-secondary cell group configuration method as described in any one of claims 34 to 51.

Images