Communication method, apparatus and system

Abstract

The present application belongs to the technical field of communications. Provided are a communication method, an apparatus and a system. The method comprises: a first network device sends first information to a terminal device, the first information comprising first configuration information and first indication information, the first information being used for instructing to add a second network device, and the first indication information being used for indicating that a first radio bearer is also associated with a first functional unit, the first functional unit being used for processing data corresponding to the first network device, and a second functional unit being used for processing data corresponding to the second network device. During an auxiliary station adding process performed by the terminal device, a new functional unit can be configured while an original functional unit is kept not released. The original functional unit and the new functional unit both can perform data transmission, thus keeping data transmission of radio bearers, and avoiding the rate reduction during the process of terminal devices reconstructing protocol entities.

Description

Communication method, device and system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on January 31, 2024, with application number 202410153009.X and application name “Communication Methods, Devices and Systems”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more particularly, to a communication method, device, and system. Background Art

[0003] The network can configure the terminal device to add a secondary station, thereby achieving dual connectivity between the terminal device and the network, with both the primary station and the secondary station providing services to the terminal device. When a terminal device adds a secondary station, the protocol entities corresponding to some radio bearers may be reconfigured from the primary station to the secondary station. The terminal device needs to rebuild these protocol entities and change the underlying transmission resources, resulting in a decrease in the data transmission rate of these radio bearers.

[0004] Therefore, how to avoid the rate drop during the process of reestablishing the protocol entity in the terminal device is an urgent problem to be solved. Summary of the Invention

[0005] The present application provides a communication method, apparatus, and system that can avoid rate drops during the process of reestablishing a protocol entity in a terminal device.

[0006] In a first aspect, a communication method is provided, which can be executed by a first network device, or by a component in the first network device (for example, a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the functions of the first network device.

[0007] The method includes: receiving first configuration information from a second network device, the first configuration information being used to configure a second functional unit associated with a first wireless bearer, the first network device and the second network device providing services for a terminal device; sending first information to the terminal device, the first information including the first configuration information and first indication information, the first information being used to indicate adding the second network device, the first indication information being used to indicate that the first wireless bearer is also associated with a first functional unit, wherein the first functional unit is used to process data corresponding to the first network device, and the second functional unit is used to process data corresponding to the second network device.

[0008] Through the above embodiment, during the process of adding a secondary station to a terminal device, the original functional unit can be retained and a new functional unit can be configured. Both the original functional unit and the new functional unit can perform data transmission, thereby maintaining the data transmission of the radio bearer, avoiding the rate drop during the process of the terminal device reestablishing the protocol entity, and improving the user experience.

[0009] In some implementations, the method further includes: receiving second information, where the second information is used to indicate that the terminal device has successfully added the second network device; and stopping sending data of the first radio bearer to the terminal device.

[0010] Through the above embodiment, the first network device can stop sending data on the first radio bearer to the terminal device after confirming that the terminal device has added the second network device. Because the terminal device has successfully added the second network device, the second network device can perform downlink transmission on the first radio bearer with the terminal device. The above embodiment allows the terminal device to maintain downlink transmission during the process of reestablishing the protocol entity, thereby avoiding a rate drop.

[0011] In some implementations, the method further includes: sending the data of the first radio bearer to the second network device.

[0012] Through the above embodiment, the first network device can deliver the data of the first radio bearer to the second network device, so that the second network device can perform uplink and downlink data transmission, thereby improving the continuity of data transmission.

[0013] In some implementations, the method further includes: sending third information to the terminal device, where the third information is used to instruct the terminal device to release the first functional unit.

[0014] In some implementations, the method further includes: receiving fourth information, wherein the fourth information is used to indicate that the session modification of the protocol data unit is completed, the terminal device has submitted all data of the first functional unit, or the terminal device requests to release at least one item of the first functional unit.

[0015] In some implementations, sending the third information to the terminal device includes: sending the third information to the terminal device in response to the fourth information.

[0016] In some implementations, the method further includes: sending fifth information to the second network device, where the fifth information is used to instruct the second network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

[0017] In some implementations, the method further includes: receiving sixth information from the second network device, where the sixth information is used to instruct the second network device to determine to configure the first radio bearer to associate the first functional unit with the second functional unit.

[0018] In some implementations, the method further includes: receiving second indication information from the second network device, where the second indication information is used to instruct the first network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

[0019] In some implementations, the first information further includes third indication information, where the third indication information is used to indicate that the first configuration information is pre-configuration information.

[0020] In some implementations, the first configuration information corresponds to information of the second network device, wherein the method further includes: sending seventh information to the terminal device, the seventh information being used to activate the configuration of the first configuration information, the seventh information including information of the second network device.

[0021] In some implementations, the method further includes: sending fourth indication information to the second network device, where the fourth indication information is used to instruct the terminal device to add the second network device according to the first configuration information.

[0022] In some implementations, the method further includes: receiving a first message from the terminal device, the first message being used to indicate that the terminal device has successfully added the second network device, the first message including fifth indication information being used to indicate that the terminal device has completed the configuration corresponding to the second network device.

[0023] In some implementations, the method further includes: sending the fifth indication information to the second network device.

[0024] In some implementations, the method further includes: sending eighth information to a core network element, where the eighth information is used to instruct activation of a pre-configured tunnel corresponding to the second network device, where the pre-configured tunnel corresponding to the second network device is associated with data of the first radio bearer.

[0025] In some implementations, the method further includes: sending ninth information to the core network element, where the ninth information is used to instruct to release the pre-configured tunnels corresponding to the network devices other than the second network device.

[0026] In some implementations, the method further includes: activating a pre-configured tunnel between the first network device and the second network device.

[0027] In some implementations, the fifth information is used to request the second network device to preconfigure the first radio bearer to associate the first functional unit with the second functional unit.

[0028] In some implementations, the first configuration information includes the first indication information.

[0029] On the second aspect, a communication method is provided, which can be executed by a terminal device, or by a component in the terminal device (for example, a processor, chip, or chip system, etc.), or by a logic module or software that can implement all or part of the terminal device functions.

[0030] The method includes: receiving first information from a first network device, the first information including first configuration information and first indication information, the first configuration information being used to configure a second functional unit associated with the first wireless bearer, the first information being used to indicate adding the second network device, and the first indication information being used to indicate that the first wireless bearer is also associated with the first functional unit, wherein the first functional unit is used to process data corresponding to the first network device, the second functional unit is used to process data corresponding to the second network device, and the first network device and the second network device provide services for the terminal device; and establishing the second functional unit according to the first information, and adding the second network device.

[0031] In some implementations, the method further includes: sending second information to the second network device, where the second information is used to indicate that the terminal device has successfully added the second network device.

[0032] In some implementations, the method further includes: receiving third information from the first network device, the third information being used to instruct the terminal device to release the first functional unit; and releasing the first functional unit according to the third information.

[0033] In some implementations, the method further includes: sending fourth information to the first network device, where the fourth information is used to indicate that the terminal device has submitted all data of the first functional unit, or that the terminal device requests to release at least one item of the first functional unit.

[0034] In some implementations, the method also includes: establishing a second bearer and a third bearer based on the first information, wherein the second functional unit is used to process data corresponding to the second bearer and the third bearer, and the first functional unit is used to process data corresponding to the first bearer, the first bearer and the second bearer correspond to the first network device, and the third bearer corresponds to the second network device.

[0035] In some implementations, the first information further includes third indication information, where the third indication information is used to indicate that the first configuration information is pre-configuration information, and the first indication information is carried in the first configuration information.

[0036] In some implementations, the first configuration information corresponds to information of the second network device; wherein, the method further includes: receiving seventh information from the first network device, the seventh information including information of the second network device; wherein, establishing the second functional unit based on the first information includes: establishing the second functional unit based on the seventh information and the first configuration information, and adding the second network device.

[0037] In a third aspect, a communication method is provided, which can be executed by a second network device, or by a component in the second network device (for example, a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the functions of the second network device.

[0038] The method includes: sending first configuration information to a first network device, where the first configuration information is used to configure a second functional unit associated with a first wireless bearer for a terminal device, where the second functional unit is used to process data corresponding to the second network device; sending second indication information to the first network device, where the second indication information is used to indicate that the first wireless bearer is also associated with a first functional unit, where the first functional unit is used to process data corresponding to the first network device, and the first network device and the second network device provide services for the terminal device.

[0039] In some implementations, the method further includes: sending second information to the first network device, where the second information is used to indicate that the terminal device has successfully added the second network device.

[0040] In some implementations, the method further includes: receiving data of the first radio bearer from the first network device.

[0041] In some implementations, the method further includes: receiving fifth information from the first network device, where the fifth information is used to instruct the second network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

[0042] In some implementations, the method further includes: sending sixth information to the first network device, where the sixth information is used to instruct the second network device to determine to configure the first radio bearer to associate the first functional unit with the second functional unit.

[0043] In some implementations, the method further includes: sending second indication information to the first network device, where the second indication information is used to instruct the first network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

[0044] In some implementations, the method further includes: receiving fourth indication information from the first network device, where the fourth indication information is used to instruct the terminal device to add the second network device according to the first configuration information.

[0045] In some implementations, the method further includes: receiving fifth indication information from the first network device, where the fifth indication information is used to instruct the terminal device to complete the configuration corresponding to the second network device.

[0046] In some implementations, the fifth information is used to request the second network device to preconfigure the first radio bearer to associate the first functional unit with the second functional unit.

[0047] In some implementations, the method further includes: sending eighth information to a core network element, where the eighth information is used to instruct activation of a pre-configured tunnel corresponding to the second network device.

[0048] In some implementations, the method further includes: activating a pre-configured tunnel between the second network device and the first network device.

[0049] In a fourth aspect, a communication device is provided, comprising a processing circuit (also referred to as a processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used to input and / or output signals, the processing circuit being used to execute the first aspect and any possible method of the first aspect, or the processing circuit being used to execute the second aspect and any possible method of the second aspect, or the processing circuit being used to execute the third aspect and any possible method of the third aspect.

[0050] In certain implementations, the processor is configured to communicate with other devices via an interface circuit and execute the first aspect and any possible method of the first aspect, or execute the second aspect and any possible method of the second aspect, or execute the third aspect and any possible method of the third aspect. The processor includes one or more.

[0051] In a fifth aspect, a communication device is provided, which may include a device or module for performing the functions of the communication device.

[0052] In some implementations, the communication device may include a module or unit corresponding to the method / operation / step / action described in the first aspect and any possible implementation of the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0053] In some implementations, the communication device may include a module or unit corresponding to the method / operation / step / action described in the second aspect and any possible implementation of the second aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0054] In some implementations, the communication device may include a module or unit corresponding to the method / operation / step / action described in the third aspect and any possible implementation of the third aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0055] In a sixth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the first aspect and any possible method of the first aspect are executed, or the second aspect and any possible method of the second aspect are executed, or the third aspect and any possible method of the third aspect are executed.

[0056] In the seventh aspect, a computer program product is provided, comprising a computer program or instructions, which, when run on a computer, causes the first aspect and any possible method of the first aspect to be executed, or causes the second aspect and any possible method of the second aspect to be executed, or causes the third aspect and any possible method of the third aspect to be executed.

[0057] In an eighth aspect, a communication device is provided, comprising a processor connected to a memory and configured to call a program stored in the memory to execute any possible method of the first aspect, any possible method of the second aspect, or any possible method of the third aspect. The memory may be located within or outside the communication device. The processor may include one or more processors.

[0058] In one implementation, the communication device of the third aspect, fourth aspect, fifth aspect or eighth aspect may be a chip or a chip system.

[0059] In the ninth aspect, a chip is provided, comprising a processor for calling a computer program or computer instruction in a memory so that the processor executes any one of the implementation methods in the first aspect above, or so that the processor executes any one of the implementation methods in the second aspect above, or so that the processor executes any one of the implementation methods in the third aspect above.

[0060] In some implementations, the processor is coupled to the memory through an interface.

[0061] In the tenth aspect, a communication system is provided, including a terminal device, a first network device and a second network device, the first network device is used to execute the above-mentioned first aspect and any possible implementation of the first aspect, the terminal device is used to execute the above-mentioned second aspect and any possible implementation of the second aspect, and the second network device is used to execute the above-mentioned third aspect and any possible implementation of the third aspect.

[0062] The description of the advantageous effects of any of the second to tenth aspects, etc., may refer to the description of the advantageous effects of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] FIG1 is a schematic diagram of a possible architecture of a communication system applicable to an embodiment of the present application.

[0064] FIG2 is a schematic diagram of some possible architectures of a communication system applicable to an embodiment of the present application.

[0065] FIG3 is a schematic flow chart of a method for adding an auxiliary station.

[0066] FIG4 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0067] FIG5 is a schematic diagram of a protocol stack configuration provided in an embodiment of the present application.

[0068] FIG6 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0069] FIG7 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0070] FIG8 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0071] FIG9 is a schematic block diagram of another communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0072] The technical solution in this application will be described below with reference to the accompanying drawings.

[0073] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0074] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0075] The business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0076] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically stated. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically stated.

[0077] The technical solutions of the embodiments of the present application can be applied to various communication systems, including but not limited to: global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), long term evolution (LTE), LTE frequency division duplex (FDD), LTE time division duplex (TDD), world wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) LTE, LTE frequency division duplex (FDD), LTE time division duplex (TDD), and 5G LTE. th The 5G generation mobile communication system or new radio (NR) system, narrowband Internet of Things (NB-IoT) system, enhanced machine-type communication (eMTC) system, enhanced mobile broadband (eMBB) system, ultra-reliable low latency communications (URLLC) system, satellite communication system or LTE-machine-to-machine (LTE-M) system and the future sixth generation (6G) system. th generation, 6G) mobile communication systems, etc.

[0078] It should be noted that in the embodiments of this application, the term "communication" can also be described as "data transmission," "signal transmission," "information transmission," or "transmission." In the embodiments of this application, transmission can include sending or receiving. For example, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device.

[0079] Figure 1 is a schematic diagram of a possible architecture of a communication system applicable to an embodiment of the present application. As shown in Figure 1, terminal device 130 can establish connections with two network devices (network device 121 and network device 122) and perform uplink (UL) or downlink (DL) service transmission with core network 110. The core network can be a 4G, 5G, or 6G core network, which is not limited in this application.

[0080] The network device 121 (or network device 122) can be any device with wireless transceiver functions, such as a base station for accessing the terminal device 130 to a radio access network (RAN). The base station is sometimes also referred to as an access network device or an access network node. It is understandable that in systems using different wireless access technologies, the names of devices with base station functions may be different. For the convenience of description, the embodiments of the present application will collectively refer to devices that provide wireless communication access functions for terminal devices as base stations. In the embodiments of the present application, the network device 121 (or network device 122) includes but is not limited to: various forms of macro base stations, micro base stations, pico base stations, small stations, balloon stations, relay stations, access points, etc. The network device 110 may include an evolved node B (eNB or eNodeB) in LTE, a next generation-evolved node B (ng-eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved node B (HNB), a base band unit (BBU), an access point, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission reception point (TRP) in a wireless fidelity (WIFI) system, and may also include a next generation node basestation (gNB) in a 5G system, an NR gNB or transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, network nodes that constitute a gNB or transmission point, such as a baseband unit (BBU) or distributed unit (DU), and may also include network equipment, servers, wearable devices, or vehicle-mounted devices in future 6G networks.

[0081] Network device 121 (or network device 122) may include a baseband unit (BBU) and a remote radio unit (RRU). The BBU and RRU may be located in different locations. For example, the RRU may be remotely located in a high-traffic area, while the BBU is located in a central computer room. The BBU and RRU may also be located in the same location, such as in the same computer room. The BBU and RRU may also be separate components within the same rack.

[0082] The network device 121 (or the network device 122) may also support an open RAN architecture. For example, the network device 121 (or the network device 122) may include a RAN device of a centralized unit (CU) node or a distributed unit (DU) node.

[0083] In the embodiment of the present application, the device for implementing the function of network device 121 (or network device 122) may be network device 121 (or network device 122), or may be a device capable of supporting network device 121 (or network device 122) to implement the function, such as a chip system, which may be installed in network device 121 (or network device 122). The chip system may be composed of a chip, or may include a chip and other discrete components.

[0084] The terminal device 130 may be a device that provides voice and / or data connectivity to a user. The terminal device 130 may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; may also be deployed on water (such as a ship); or may be deployed in the air (for example, on a drone, airplane, balloon, or satellite). The terminal device 130 may also be referred to as user equipment (UE), mobile terminal (MT), access terminal, terminal, subscriber unit (subscriber unit), user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user device. In the embodiment of the present application, the terminal device 130 includes, but is not limited to, a cellular phone, a mobile phone, a wireless data card, a wireless modem, a tablet computer, a laptop computer, a computer with wireless transceiver function, a cordless phone, a Session Initiation Protocol (SIP) phone, a smart phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle device, a terminal device in the Internet of Things or the Internet of Vehicles, and any form of terminal in a future network, a relay user device, or a terminal in a future evolved public land mobile communication network (PLMN). The terminal device 130 can also be a VR terminal device, an AR terminal device, a machine type communication (MTC) terminal, a terminal device in industrial control, a terminal device in self-driving, a terminal device in remote medical, a terminal device in a smart grid, a wireless terminal in transportation safety, a terminal device in a smart city, a terminal device in a smart home, a tactile terminal device, a vehicle-mounted terminal device, a wearable terminal device, etc., and the embodiments of the present application are not limited to this.

[0085] In the embodiment of the present application, the device for implementing the function of the terminal device 130 may be the terminal device 130, or may be a device capable of supporting the terminal device 130 to implement the function, such as a chip system, which may be installed in the terminal device 130. The chip system may be composed of a chip, or may include a chip and other discrete devices. In the technical solution of the embodiment of the present application, the device for implementing the function of the terminal device is a terminal device, which may also be referred to as a terminal. The following may take the terminal device as an example to describe the technical solution provided by the embodiment of the present application.

[0086] The core network 110 can provide user connections, user management, and service bearer services. It can also function as a bearer network, providing an interface to external networks. For example, the core network 110 can be a 4G, 5G, or 6G core network. The core network 110 can include one or more core network elements.

[0087] It should be understood that FIG1 is only a simplified schematic diagram for ease of understanding, and the communication system 100 may further include other network devices or other terminal devices, which are not shown in FIG1 .

[0088] The network device 121 (or the network device 122) and the terminal device 130 can communicate via a wireless link. The transmission link from the network device 121 (or the network device 122) to the terminal device 130 can be called a downlink (DL) or a downlink channel, which is used to transmit downlink signals. The transmission link from the terminal device 130 to the network device 121 (or the network device 122) can be called an uplink (UL) or an uplink channel, which is used to transmit uplink signals. Exemplarily, the network device 121 (or the network device 122) can send a downlink reference signal, such as a cell-specific reference signal (CRS) or a UE-specific reference signal (UE-specific reference signal), to the terminal device 130 via a downlink channel for measurement of channel state information, data demodulation, beam training, time-frequency parameter tracking, etc. The terminal device 130 can send an uplink reference signal, such as an SRS or a DMRS, to the network device 121 (or the network device 122) via an uplink channel for uplink and downlink channel measurement, data demodulation, etc. The network device 121 (or the network device 122 ) and the terminal device 130 may also perform downlink data transmission via a downlink channel and perform uplink data transmission via an uplink channel.

[0089] Wireless communication can also be performed between the network device 121 and the network device 122, and wireless communication can also be performed between the terminal device 130 and other terminal devices.

[0090] The scenario shown in Figure 1 may also be referred to as dual connectivity (DC). DC is the operating mode of terminal device 130 in the radio resource control (RRC) connected state. A scenario in which the network side (including network device 121 and network device 122) configures a master cell group (MCG) and a secondary cell group (SCG) for terminal device 130 in the connected state may be referred to as DC.

[0091] Figure 2 is a schematic diagram of some possible architectures of a communication system applicable to embodiments of the present application. There are multiple DC scenarios, and four scenarios are briefly described below in conjunction with Figure 2. However, the present application is not limited to the scenario shown in Figure 2 and may also be applicable to other dual connectivity scenarios.

[0092] Referring to (1) in FIG2 , the core network 110 may be an evolved packet core (EPC), i.e., a 4G core network. The network device 121 may be a long term evolution (LTE) base station, such as an eNB; the network device 122 may be a new radio (NR) base station, such as a gNB. LTE may serve as a master node (MN), and the NR base station may serve as a secondary node (SN). The above scenario may also be referred to as dual connectivity (E-UTRA-NR dual connectivity, EN-DC) between the 4G wireless access network and the 5G NR. An X2 interface may exist between the LTE base station and the NR base station. Through the X2 interface, there is at least a control plane connection between the LTE base station and the NR base station, and there may also be a user plane connection. An S1 interface may exist between the LTE base station and the EPC. Through the S1 interface, there is at least a control plane connection between the LTE base station and the EPC, and there may also be a user plane connection. An S1-U interface may exist between the NR base station and the EPC, i.e., there may be a user plane connection. The LTE base station can provide air interface resources for the terminal device 130 through at least one LTE cell, in which case the at least one LTE cell is called an MCG. Correspondingly, the NR base station can also provide air interface resources for the terminal device 130 through at least one NR cell, in which case the at least one NR cell is called an SCG.

[0093] Referring to (2) in FIG2 , the core network 110 may be a 5G core network (5G core network, 5GC). The network device 121 may be an NR base station, such as a gNB; the network device 122 may be an LTE base station, such as an eNB. LTE may serve as a master node (MN), and the NR base station may serve as a secondary node (SN). The NR base station may serve as an MN, and the LTE base station may serve as an SN. An Xn interface may exist between the NR base station and the LTE base station. Through the Xn interface, there is at least a control plane connection between the NR base station and the LTE base station, and there may also be a user plane connection. An NG interface may exist between the NR base station and the 5GC. Through the NG interface, there is at least a control plane connection between the NR base station and the 5GC, and there may also be a user plane connection. An NG-U interface may exist between the LTE base station and the 5GC, that is, there may be a user plane connection. The NR base station may provide air interface resources for the terminal device 130 through at least one NR cell, in which case the at least one NR cell is referred to as an MCG. Accordingly, the LTE base station may also provide air interface resources for the terminal device 130 through at least one LTE cell, in which case the at least one LTE cell is referred to as an SCG.

[0094] Referring to (3) in Figure 2, the core network 110 can be a 5GC. The network device 121 can be an LTE base station, such as an eNB; the network device 122 can be an NR base station, such as a gNB. The LTE base station can serve as an MN, and the NR base station can serve as an SN. Among them, an Xn interface can exist between the LTE base station and the NR base station. Through the Xn interface, there is at least a control plane connection between the LTE base station and the NR base station, and there can also be a user plane connection. An NG interface can exist between the LTE base station and the 5GC. Through the NG interface, there is at least a control plane connection between the LTE base station and the 5GC, and there can also be a user plane connection. An NG-U interface can exist between the NR base station and the 5GC, that is, there can be a user plane connection. The LTE base station can provide air interface resources for the terminal device 130 through at least one LTE cell, and in this case, the at least one LTE cell is called an MCG. Correspondingly, the NR base station can also provide air interface resources for the terminal device 130 through at least one NR cell, and in this case, the at least one NR cell is called an SCG.

[0095] Referring to (4) in Figure 2, the core network 110 can be a 5GC. The network device 121 and the network device 122 can both be NR base stations, such as gNBs. Among them, one NR base station serves as an MN and the other NR base station serves as an SN. Among them, an Xn interface can exist between the MN and the SN. Through the Xn interface, there is at least a control plane connection between the MN and the SN, and there can also be a user plane connection. There can be an NG interface between the MN and the 5GC. Through the NG interface, there is at least a control plane connection between the MN and the 5GC, and there can also be a user plane connection. There can be an NG-U interface between the SN and the 5GC, that is, there can be a user plane connection. The MN can provide air interface resources for the terminal device 130 through at least one NR cell, and in this case, the at least one NR cell is called an MCG. Correspondingly, the SN can also provide air interface resources for the terminal device 130 through at least one NR cell, and in this case, the at least one NR cell is called an SCG.

[0096] The communication system shown in Figure 1 or Figure 2 can also be referred to as a multi-radio access technology dual connectivity (MR-DC) architecture. The MR-DC architecture can support multiple radio bearer (RB) types. It should be noted that Figures 1 and 2 are merely exemplary, and the application scenarios of this application are not limited to dual connectivity scenarios and can also be applied to other scenarios.

[0097] A radio bearer is a general term for a series of protocol entities and configurations allocated by a network device to a terminal device. It can be a service provided by Layer 2 for transmitting user data between a terminal device and a network device. A radio bearer can include one or more of a packet data convergence protocol (PDCP) entity, a radio link control (RLC) protocol entity, a media access control (MAC) protocol entity, and a series of resources allocated by the physical layer (PHY). A radio bearer can include a data radio bearer (DRB) and a signaling radio bearer (SRB). DRBs can be used to carry data, and SRBs can be used to carry signaling messages. As an example, a radio bearer configuration generally includes the configuration of the PDCP layer and the SDAP layer. The protocol entities below the RLC layer are called RLC bearers, and the corresponding configuration is given in the RLC bearer configuration. In other words, the radio bearer configuration can include the configuration of the PDCP layer and the SDAP layer, but does not include the configuration of the RLC bearer. In some other optional manners, the configuration of the radio bearer may include configuration of the PDCP layer, the SDAP layer, and the RLC layer.

[0098] Exemplarily, the types of wireless bearers supported by the MR-DC architecture may include: at least one of: an MCG bearer terminated at the MN (MN terminated MCG bearer), an SCG bearer terminated at the MN (MN terminated SCG bearer), a split bearer terminated at the MN (MN terminated split bearer), an MCG bearer terminated at the SN (SN terminated MCG bearer), an SCG bearer terminated at the SN (SN terminated SCG bearer), or a split bearer terminated at the SN (SN terminated split bearer).

[0099] Among them, MCG bearer may refer to a bearer that only involves MCG air interface resources. SCG bearer may refer to a bearer that only involves SCG air interface resources. Split bearer may refer to a bearer that involves both MCG air interface resources and SCG air interface resources, and the split bearer can be diverted in the PDCP entity. MN or SN termination may refer to the PDCP entity being in the MN or SN, for example, the PDCP of the MN-terminated SCG bearer is in the MN, but the corresponding air interface resources at the bottom layer are in the SCG. Air interface resources may also be called wireless resources, wireless air interface resources or have other names.

[0100] FIG3 is a schematic flow chart of a method 300 for adding an auxiliary station. The method 300 is provided as an example only and does not limit the present application. The method 300 is described below in conjunction with FIG3 .

[0101] S310, the MN sends an SN addition request message to the SN.

[0102] The SN add request message may be used to request a target SN to allocate resources for one or more protocol data unit (PDU) sessions or quality of service (QoS) flows.

[0103] Optionally, the SN add request message may indicate QoS flow characteristics. For example, QoS flow level, QoS parameters, PDU session level, transport network layer (TNL) address information, and network slice information at the PDU session level. Optionally, in the SN add request message, the MN also provides UE measurement results for the SN to select and configure SCG cells. Optionally, for radio bearers that require SCG air interface resources, the MN also indicates information required by the SCG, such as UE capabilities.

[0104] S320: The SN sends an addition request acknowledgement message to the MN.

[0105] Optionally, before S320 , the method 300 further includes: the SN allowing the request of the MN; the SN allocating corresponding air interface resources; and the SN determining a radio bearer configuration according to the bearer type in the SN add request message.

[0106] Optionally, the add request confirmation message may include the radio bearer configuration. The radio bearer configuration may be sent to the UE via the MN.

[0107] S330: The MN sends an RRC reconfiguration message to the UE.

[0108] The RRC reconfiguration message may include the RRC configuration of the SN. The RRC configuration may be used for the UE to access the SN and obtain the air interface resources of the SN.

[0109] S340: The UE sends an RRC reconfiguration complete message to the MN.

[0110] The RRC reconfiguration complete message may be used to indicate configuration completion, and the RRC reconfiguration complete message may include an RRC reconfiguration complete message for the SN.

[0111] Optionally, before S340, the method 300 further includes: the UE performs configuration according to the RRC reconfiguration message.

[0112] S350, the MN sends an RRC reconfiguration completion message for the SN to the SN.

[0113] The RRC reconfiguration complete message for the SN may indicate to the SN that the UE has completed the dual connectivity configuration.

[0114] S360: The UE performs random access based on the RRC configuration of the SN and establishes an air interface connection with the SN.

[0115] It should be noted that for radio bearers terminating at the SN, the PDCP entity must be switched from the MN to the SN. Since the key corresponding to the PDCP entity has changed, the PDCP entity must be re-established to avoid key confusion. For MCG bearers or split bearers terminating at the SN, the RLC bearer originally established on the MCG also needs to be re-established or the logical channel changed to prevent data encrypted with the old key from being incorrectly transmitted.

[0116] In a related technical solution, after the UE receives the RRC reconfiguration message, it stops uplink data transmission with the MN and reestablishes the PDCP entity corresponding to the radio bearer, including: clearing all cached data, initializing PDCP entity-related processing parameters, and applying new parameters for encryption and integrity protection. After the UE accesses the SN (i.e., S360), it performs uplink or downlink data transmission with the SN. Between the time the UE receives the RRC reconfiguration message and the time it accesses the SN, the UE cannot transmit data on the radio bearer, resulting in a drop in transmission rate, i.e., a sudden decrease in transmission rate, thereby reducing the user experience.

[0117] Therefore, how to avoid the rate drop during the process of reestablishing the protocol entity in the terminal device is an urgent problem to be solved.

[0118] FIG4 is a schematic flow chart of a communication method 400 provided in an embodiment of the present application. The method 400 can avoid a rate drop during the process of reestablishing a protocol entity in a terminal device. The method 400 is described below with reference to FIG4 .

[0119] S410: A first network device receives first configuration information from a second network device. Correspondingly, the second network device sends the first configuration information to the first network device.

[0120] Optionally, the first configuration information may be used to configure a second functional unit associated with the first radio bearer. Optionally, the first network device and the second network device may provide services to the terminal device; in other words, the first network device and the second network device may be connected to the terminal device; in other words, the first network device and the second network device may establish a dual connection with the terminal device; in other words, the terminal device may access one or more cells of the first network device and the second network device.

[0121] The functional unit may include the functions of the PDCP entity. In some optional embodiments, the functional unit may be replaced by PDCP, PDCP entity, or PDCP protocol stack. The functional unit may have other names, such as function.

[0122] The first functional unit may be an existing (or configured) functional unit of the first radio bearer. In some optional embodiments, the first functional unit may be replaced by a first PDCP, a first PDCP function, a first PDCP entity, or a first PDCP protocol stack. The first functional unit may have other names, such as a first function.

[0123] The second functional unit may be a functional unit that requires new configuration for the first radio bearer. In some optional embodiments, the second functional unit may be replaced by a second PDCP, a second PDCP function, a second PDCP entity, or a second PDCP protocol stack. The second functional unit may have other names, such as a second function.

[0124] Optionally, the first functional unit and the second functional unit may represent different functions on one PDCP entity. Optionally, the first functional unit may represent a function on one PDCP entity, and the second functional unit may represent a function on another PDCP entity.

[0125] For example, taking the first network device as an MN and the second network device as an SN, the first configuration information can be carried in the SN add request confirmation message. However, this application is not limited to this, and the first configuration information can also be carried in other messages.

[0126] Optionally, before S410, method 400 further includes: the first network device sending a message to the second network device requesting the addition of the second network device. For example, an SN add request message. The specific content of the SN add request message can be found in the description related to S310 and is not further described here. Optionally, the second network device determines the first configuration information based on the SN add request message.

[0127] In some optional embodiments, the SN add request message may include the type of radio bearer. Optionally, the second network device may determine the first configuration information. Optionally, the second network device may determine the first configuration information based on the type of radio bearer.

[0128] In some optional embodiments, the first configuration information can be used to trigger the terminal device to access (or add) the second network device, thereby enabling the terminal device to communicate with the second network device. In some optional embodiments, the first configuration information can be used to configure an RLC bearer associated with the second functional unit. The RLC bearer can be an RLC bearer corresponding to the second network device. For example, the first configuration information can be used to instruct the terminal device to configure the second functional unit to associate with the RLC bearer of the first second network device.

[0129] In some optional embodiments, the first configuration information may include at least one of the configuration information of the first radio bearer, the configuration information of the PDCP, or the SCG configuration. For example, the SCG configuration may include the cell resource configuration of the SN. For example, the SCG configuration may be used to instruct the terminal device to add one or more cells of the second network device; in other words, the SCG configuration may be used to instruct the terminal device to add a group of cells of the second network device, the group of cells including one or more cells. Among them, the PDCP configuration information in the first configuration information may also be referred to as the configuration (or configuration information) of the second functional unit. For example, the configuration of the second functional unit may include at least one of an encryption parameter, a security parameter, or a robust header compression (RHCO) parameter.

[0130] For example, the second functional unit associated with the first radio bearer can process data of the first radio bearer. The second functional unit associated with the first radio bearer can also be expressed as the second functional unit corresponding to the first radio bearer, the second functional unit of the first radio bearer, etc.

[0131] It should be noted that this application does not limit the names of functional units. Functional units may be referred to as PDCP, protocol stack, PDCP protocol stack, PDCP entity, function, PDCP function, or other names. This application does not limit the names of RLC bearers. RLC bearers may be referred to as RLC, RLC entity, RLC function, bearer, logical channel, or other names.

[0132] S420: The first network device sends first information to the terminal device.

[0133] The first information may include the first indication information. The first indication information may be used to indicate that the first radio bearer is associated with the first functional unit. Optionally, the first information includes first configuration information.

[0134] The first indication information can be used to indicate that the first radio bearer is associated with the first functional unit; in other words, the first indication information can be used to indicate that a dual active protocol stack (DAPS) is configured for the first radio bearer, or to indicate that two sets of protocol stack functions are configured for the first radio bearer; in other words, the first indication information can be used to instruct the terminal device to maintain the first functional unit and establish a second functional unit; in other words, the first indication information can be used to instruct the terminal device to wait for the release indication of the first functional unit and establish the second functional unit; in other words, the first indication information can be used to instruct the terminal device not to release the first functional unit and establish the second functional unit.

[0135] Configuring a dual-active protocol stack for the first radio bearer may mean that the first radio bearer keeps an original protocol stack in an activated state and configures a new activated protocol stack.

[0136] The first functional unit may be a configured functional unit. For example, the first functional unit may be a functional unit configured before S420 is executed. The first functional unit may be associated with a first bearer (or referred to as a first RLC bearer). The first bearer may be associated with air interface resources of one or more cells of the first network device. The air interface resources of the one or more cells of the first network device may be referred to as air interface resources corresponding to the first bearer, or air interface resources associated with the first functional unit, or may have other names.

[0137] The first indication information may come from the second network device, that is, the second network device sends the first indication information to the first network device, and the first network device receives the indication information from the second network device. Optionally, the first indication information may be carried in the first configuration information. The second network device may add the first indication information to the first configuration information and send the first configuration information to the first network device. The first indication information may also be generated by the first network device. In other words, the first indication information may be independent of the first configuration information. The first network device may add the first indication information to the first information and send the first information to the terminal device. This application does not limit the source of the first indication information.

[0138] The first indication information may be called a dual-activation protocol stack indication, a dual-activation indication, or have other names, which is not limited in this application.

[0139] The first information may be used to instruct the terminal device to add the second network device. For example, the first information may be used to instruct the terminal device to add the second network device as an SN. Alternatively, the first information may be used to display instruction information to instruct the terminal device to add the second network device. Alternatively, the first configuration information may instruct the terminal device to add the second network device. Alternatively, the first instruction information may be used to instruct the terminal device to add the second network device.

[0140] Optionally, the first information can be used to instruct the terminal device to add one or more cells of the second network device; in other words, the first information can be used to instruct the terminal device to add a group of cells of the second network device, which group of cells includes one or more cells. Optionally, the first network device receives third configuration information from the second network device, and the third configuration information is used to instruct the terminal device to add one or more cells of the second network device. The third configuration information can be called SCG configuration or have other names. Optionally, the first configuration information includes the third configuration information. In addition, the above-mentioned one or more cells of the second network device associated with the second functional unit can be understood as the second functional unit being used to process data associated with one or more cells of the second network device.

[0141] Optionally, the first information may be used to instruct the terminal device to add one or more cells of the first network device.

[0142] Optionally, the first information may indicate that one or more cells of the first network device are associated with the second functional unit. It can be understood that the second functional unit is used to process data associated with one or more cells of the first network device. Optionally, the first information is used to indicate the configuration of a second bearer, which is a bearer of the first network device and is associated with the second functional unit. The configuration of the second bearer can be used to configure the second bearer. The configuration of the second bearer can be used to configure the air interface resources of one or more cells of the first network device. The air interface resources of the one or more cells of the first network device mentioned above can be referred to as the air interface resources corresponding to the second bearer. The air interface resources corresponding to the second bearer can be used as the air interface resources associated with the second functional unit.

[0143] The second bearer may also be referred to as a second RLC bearer or have other names. Optionally, the first network device may send the configuration of the second bearer to the terminal device. The configuration of the second bearer may be included in the first information or sent independently of the first information, which is not limited in this application.

[0144] Optionally, the first information may indicate the configuration of a third bearer, where the third bearer is a bearer of the second network device and is associated with the second functional unit. The configuration of the third bearer may be used to configure the third bearer. The configuration of the third bearer may be used to configure air interface resources of one or more cells of the second network device. The air interface resources of the one or more cells of the second network device may be referred to as the air interface resources corresponding to the third bearer. The air interface resources corresponding to the third bearer may serve as the air interface resources associated with the second functional unit.

[0145] It can be understood that the air interface resources associated with the second functional unit may include air interface resources corresponding to the second bearer and air interface resources corresponding to the third bearer.

[0146] The third bearer may also be referred to as a third RLC bearer or have other names. Optionally, the first network device may send the configuration of the third bearer to the terminal device. The configuration of the third bearer may be included in the first information or sent independently of the first information, which is not limited in this application.

[0147] When the first network device or the second network device determines to configure a split bearer for the first radio bearer, the configuration of the second bearer may be determined by the first network device, and the configuration of the third bearer may be determined by the second network device. Optionally, the first network device receives the configuration of the third bearer from the second network device. Optionally, the first configuration information includes the configuration of the third bearer. Optionally, the first indication information includes the configuration of the third bearer.

[0148] The first information may be called RRC reconfiguration information or have other names, which is not limited in this application.

[0149] In some optional embodiments, the first information may be carried in an RRC reconfiguration message, but this application is not limited to this, and the first information may be carried in other messages. In some optional embodiments, S420 may be replaced with: the first network device sends the first configuration information to the terminal device; the first network device sends the first indication information to the terminal device. In other words, the first configuration information and the first indication information may be carried in different messages, or the first configuration information and the first indication information may be sent separately.

[0150] The first functional unit may be used to process data corresponding to the first network device, and the second functional unit may be used to process data corresponding to the second network device.

[0151] The first functional unit may be configured to process data corresponding to the first network device; in other words, the first functional unit may correspond to (or be associated with) the first network device; in other words, the first functional unit may be configured to process data on a first radio bearer to be sent to or from the first network device; the first functional unit may be configured to process data on a first radio bearer to be sent to or from a third entity (e.g., a PDCP entity), the third entity corresponding to the first network device. The third entity corresponding to the first network device may be understood as the third entity being associated with the first network device, or as the third entity being located or configured on the first network device side.

[0152] The second functional unit may be configured to process data corresponding to the second network device; in other words, the second functional unit may correspond to (or be associated with) the second network device; in other words, the second functional unit may be configured to process data on a first radio bearer to be sent to or from the second network device; the second functional unit may be configured to process data on a first radio bearer to be sent to or from a fourth entity (e.g., a PDCP entity), the fourth entity corresponding to the second network device. The fourth entity corresponding to the second network device may be understood as the fourth entity being associated with the second network device, or as the fourth entity being located or configured on the second network device side.

[0153] In one possible manner, the third entity and the fourth entity are PDCP entities. The first functional unit and the second functional unit are PDCP entities or functional units of PDCP. The third entity and the fourth entity are associated with the first radio bearer. When the first network device or the second network device determines to configure a split bearer for the first radio bearer, the first network device configures an RLC bearer on the first network device side for the first radio bearer and associates it with the second functional unit, and the second network device configures an RLC bearer on the second network device side for the first radio bearer and associates it with the second functional unit. Correspondingly, the terminal device can receive data from the fourth entity based on the air interface resources of the first network device and the second network device, and submit it to the second functional unit for processing.

[0154] It can be understood that the first radio bearer is associated with the first functional unit and the second functional unit, indicating that the data of the first radio bearer can be processed by the first functional unit or the second functional unit. In other words, the terminal device configured with the first functional unit and the second functional unit can process the data corresponding to the first network device or the data corresponding to the second network device. For example, the terminal device can process the PDCP data from the first network device or the PDCP data from the second network device. For another example, the first functional unit can process the PDCP data from the first network device, and the second functional unit can process the PDCP data from the second network device.

[0155] In some optional embodiments, the terminal device may uniformly number the data processed by the first functional unit and the second functional unit. The data processed by the first functional unit is encrypted, secured, ROHC, and has a message header added, etc., using the configuration of the first functional unit. The data processed by the second functional unit is encrypted, secured, ROHC, and has a message header added, etc., using the configuration of the second functional unit. The data processed by the first functional unit is sent via the air interface resources associated with the first functional unit, and the data processed by the second functional unit is sent via the air interface resources associated with the second functional unit. The air interface resources associated with the first functional unit. It should be noted that the air interface resources associated with the second functional unit can be the air interface resources of the first network device or the air interface resources of the second network device.

[0156] In some optional embodiments, the terminal device can receive data from the first network device and the second network device respectively. The received data includes data submitted by the PDCP of the first network device and data submitted by the PDCP of the second network device. The terminal device can receive data through the air interface resources associated with the first network device and the second network device, and determine whether the received data comes from the first network device or the second network device. For example, the terminal device can distinguish the data from the first network device and the second network device through the RLC bearer identifier or the logical channel identifier, and submit the PDCP data from the first network device to the first functional unit for processing, and submit the PDCP data from the second network device to the second functional unit for processing.

[0157] The first functional unit and the second functional unit may correspond to the same PDCP entity, but this application is not limited to this. The first functional unit and the second functional unit may correspond to different PDCP entities, for example, the first functional unit corresponds to the first PDCP entity, and the second functional unit corresponds to the second PDCP entity. It is understandable that the functions of the first functional unit and the second functional unit may be implemented in the same PDCP entity or in different PDCP entities. In one possible implementation, the first functional unit corresponds to the PDCP function. Optionally, the terminal device has only one PDCP entity, and the PDCP entity corresponds to two functions, namely the first functional unit and the second functional unit. In another possible implementation, the first functional unit corresponds to the PDCP entity. Optionally, the terminal device establishes a PDCP entity corresponding to the second functional unit. At this time, after the new PDCP entity is established, the terminal device has two PDCP entities, one of which corresponds to the first functional unit, and the other corresponds to the second functional unit.

[0158] Optionally, the first information includes second configuration information. The second configuration information may be configuration information added by the first network device. Optionally, the first configuration information and the second configuration information may be carried in RRC configuration information. The RRC configuration information may include at least one of the configuration information of the first radio bearer, the configuration information of the PDCP, or the configuration information of the air interface resources associated with the first radio bearer. Optionally, the configuration information of the PDCP may include at least one of an encryption parameter, an integrity parameter, or an RHCO parameter. Among them, the configuration information of the PDCP in the RRC configuration information or the second configuration information may be referred to as the configuration (or configuration information) of the second functional unit. Optionally, the configuration information of the air interface resources associated with the first radio bearer may include at least one of an MCG configuration or an SCG configuration. For example, for a split bearer, the configuration information of the air interface resources associated with the first radio bearer may include an MCG configuration and an SCG configuration. Among them, the SCG configuration may be used to instruct the terminal device to add one or more cells of the second network device; in other words, the SCG configuration may be used to instruct the terminal device to add a group of cells of the second network device, the group of cells including one or more cells. For another example, for an MCG bearer, the configuration information of the air interface resources associated with the first radio bearer may include the RLC bearer configuration on the first network device side. For another example, for an SCG bearer, the configuration information of the air interface resources associated with the first radio bearer may include the RLC bearer configuration on the second network device side.

[0159] S430: The terminal device establishes a second functional unit according to the first information.

[0160] Optionally, the method 400 further includes: the terminal device adds a second network device according to the first information. Optionally, S430 may be replaced by: the terminal device establishes a second functional unit according to the first information and adds the second network device.

[0161] Establishing the second functional unit may also be referred to as configuring the second functional unit. Optionally, the terminal device maintains the first functional unit and establishes the second functional unit based on the first indication information. Optionally, the terminal device waits for a release instruction for the first functional unit based on the first indication information. Optionally, the terminal device does not release the first functional unit based on the first indication information. Optionally, the terminal device establishes the second functional unit before releasing the first functional unit based on the first indication information.

[0162] Optionally, the first indication information may be included in the first configuration information. Optionally, the terminal device maintains the first functional unit and establishes the second functional unit based on the first configuration information. Optionally, the terminal device waits for a release instruction for the first functional unit based on the first configuration information. Optionally, the terminal device does not release the first functional unit based on the first configuration information. Optionally, the terminal device establishes the second functional unit before releasing the first functional unit based on the first configuration information.

[0163] Optionally, the terminal device adds a second network device based on the first information. For example, the terminal device adds the second network device based on the first information to provide communication services for the terminal device. Optionally, the first configuration information instructs the addition of the second network device; the terminal device adds the second network device based on the first configuration information. For example, the terminal device adds the second network device as an SN (or to provide communication services for the terminal device) based on the first configuration information.

[0164] Optionally, the first information is used to instruct the terminal device to add one or more cells of the second network device. Optionally, the terminal device adds one or more cells of the second network device according to the first information, or adds a group of cells of the second network device, the group of cells including one or more cells.

[0165] Optionally, the first information includes third configuration information, and the third configuration information is used to instruct the terminal device to add one or more cells of the second network device. The third configuration information can be called SCG configuration or have other names. Optionally, the terminal device adds one or more cells of the second network device according to the third configuration information, or adds a group of cells of the second network device, where the group of cells includes one or more cells. Optionally, the first configuration information includes the third configuration information. In addition, the one or more cells of the second network device are associated with the second functional unit, which can be understood as the second functional unit being used to process data associated with one or more cells of the second network device.

[0166] Optionally, the first information may be used to instruct the terminal device to add one or more cells of the first network device. Optionally, the terminal device adds one or more cells of the first network device according to the first information.

[0167] Optionally, the first information is used to indicate the configuration of the second bearer. Optionally, the terminal device configures the second bearer based on the configuration of the second bearer, wherein the second bearer is a bearer of the first network device and the second bearer is associated with the second functional unit. Optionally, the terminal device configures the air interface resources of one or more cells of the first network device based on the configuration of the second bearer. The air interface resources of the one or more cells of the first network device can be referred to as the air interface resources corresponding to the second bearer. The air interface resources corresponding to the second bearer can be used as the air interface resources associated with the second functional unit.

[0168] The second bearer may also be referred to as a second RLC bearer or have other names. Optionally, the terminal device receives the configuration of the second bearer. The configuration of the second bearer may be included in the first information or sent independently of the first information, which is not limited in this application.

[0169] Optionally, the first information may indicate the configuration of a third bearer. Optionally, the terminal device configures a third bearer based on the configuration of the third bearer, wherein the third bearer is a bearer of the second network device and is associated with the second functional unit. Optionally, the terminal device configures air interface resources of one or more cells of the second network device based on the configuration of the third bearer. The air interface resources of the one or more cells of the second network device may be referred to as the air interface resources corresponding to the third bearer. The air interface resources corresponding to the third bearer may serve as the air interface resources associated with the second functional unit.

[0170] The third bearer may also be referred to as a third RLC bearer or have other names. Optionally, the terminal device receives the configuration of the third bearer. The configuration of the third bearer may be included in the first information or sent independently of the first information, which is not limited in this application.

[0171] Optionally, the first information includes second configuration information. The first configuration information and the second configuration information are carried in RRC configuration information. Optionally, the terminal device establishes a second functional unit and adds a second network device based on the RRC configuration information. Optionally, the terminal device configures at least one of the first radio bearer, PDCP, or air interface resources associated with the first radio bearer based on the RRC configuration information.

[0172] Optionally, the terminal device establishes an entity corresponding to the second functional unit based on the first information. For example, the terminal device may create a new PDCP entity. Optionally, the terminal device establishes the function corresponding to the second functional unit based on the first information. For example, the terminal device may reconfigure an existing PDCP entity to establish the function corresponding to the second functional unit.

[0173] Through the above embodiment, during the process of adding a secondary station to a terminal device, the original functional unit can be retained and a new functional unit can be configured. Both the original functional unit and the new functional unit can perform data transmission, thereby maintaining the data transmission of the radio bearer, avoiding the rate drop during the process of the terminal device reestablishing the protocol entity, and improving the user experience.

[0174] Optionally, the data corresponding to the first bearer, the second bearer, and the third bearer are data of the first radio bearer. The first bearer, the second bearer, and the third bearer can be used to process the data of the first radio bearer.

[0175] The term "bearer" may also be referred to as an RLC bearer, a logical channel, or have other names. The above solution is described below using FIG5 as an example.

[0176] Figure 5 is a schematic diagram of a protocol stack configuration provided by an embodiment of the present application. Figure 5 is merely an example for facilitating understanding of method 400 and does not constitute a limitation of the present application.

[0177] As shown in Figure 5(a), before a SN is added (e.g., before method 400 is executed), the UE is connected to the MN. PDCP 110 in the UE corresponds to PDCP 140 in the MN. During uplink transmission, the UE can submit data processed by PDCP 110 to RLC 120 for processing before sending it to the MN. After receiving the data, the MN can process it through RLC 130 and then submit it to PDCP 140 for processing. For example, PDCP 110 can be referred to as a first functional unit.

[0178] As shown in (b) of Figure 5, after the SN is added (for example, after S420 is executed), the UE is connected to the MN and the SN. The UE maintains the original PDCP 110 and establishes a new PDCP 112. The PDCP 112 can be used to process data corresponding to the PDCP 142. Optionally, the UE can establish RLC 122 and RLC 124 associated with the PDCP 112. The MN can establish RLC 132 associated with the PDCP 142 in the SN. The SN can establish PDCP 142 and establish RLC 134 associated with the PDCP 142. Exemplarily, the first bearer can be RLC 120, the second bearer can be RLC 122, and the third bearer can be RLC 124. Exemplarily, PDCP 114 can be referred to as a second functional unit. Exemplarily, PDCP 112 can be referred to as a second functional unit. Exemplarily, PDCP 112 and PDCP 114 can be referred to as a second functional unit.

[0179] It should be noted that PDCP 110 and PDCP 112 may be different PDCP entities or the same PDCP entity. For the latter, the UE side does not need to establish a new PDCP entity, but only needs to reconfigure different functional units in the original PDCP.

[0180] In some optional embodiments, the terminal device may uniformly number the data processed by PDCP 110 and PDCP 112. Optionally, the terminal device applies different configurations to perform operations such as encryption, security, ROHC, and adding message headers for PDCP 110 and PDCP 112. For example, the data of PDCP 110 is encrypted, secured, ROHC, and adding message headers using the configuration of PDCP 110 provided by the MN, and the data processed by PDCP 112 is encrypted, secured, ROHC, and adding message headers using the configuration of PDCP 112 provided by the SN. The data processed by PDCP 110 is sent via the air interface resources associated with PDCP 110. For example, the data processed by PDCP 110 is delivered to the RLC 120 associated with PDCP 110 for processing. The data processed by PDCP 112 is sent via the air interface resources associated with PDCP 112. For example, data processed by the PDCP 112 is delivered to the RLC 122 or RLC 124 associated with the PDCP 112 for processing.

[0181] In some optional embodiments, the terminal device can receive data from the first network device and the second network device. The received data includes data submitted by the PDCP 140 of the first network device and data submitted by the PDCP 142 of the second network device. The terminal device can receive data through the air interface resources of the first network device and the second network device associated with PDCP 140 and PDCP 142, and determine whether the received data comes from the first network device or the second network device. For example, different RLCs correspond to different logical channels. The terminal device can distinguish whether the data comes from the RLC entity associated with PDCP 140 (such as RLC 130) or the RLC entity associated with PDCP 142 (such as RLC 132 or RLC 134) by the logical channel identifier, and determine whether the data comes from the PDCP 140 of the first network device or the PDCP 142 of the second network device, and submit the data from the PDCP 140 of the first network device to PDCP 110 for processing, and submit the data from the PDCP 140 of the second network device to PDCP 112 for processing.

[0182] In some optional embodiments of the present application, after S410, the first network device may maintain downlink transmission, that is, the first network device may send data to the terminal device. Optionally, the first network device may deliver downlink data to the second network device through the inter-station interface. Optionally, the first network device may send a status report, and the status report may be used to indicate the downlink data that the terminal device has successfully transmitted on the first network device side; the second network device may clear the downlink data that the terminal device has successfully transmitted on the first network device side based on the status report. For example, the status report may indicate the sequence number of the next downlink PDCP. The present application does not limit the name of the status report, and the status report may also have other names.

[0183] In some optional embodiments of the present application, after S410, the terminal device may maintain uplink transmission with the first network device, that is, the terminal device may send data to the first network device. Optionally, the first network device may send uplink data to the core network element. Optionally, the first network device may deliver uplink data to the second network device through the inter-station interface. Optionally, the first network device may send a status report, and the status report may be used to indicate the uplink data that the terminal device has successfully transmitted on the first network device side; the second network device may clear the uplink data that the terminal device has successfully transmitted on the first network device side based on the status report. For example, the status report may indicate the sequence number corresponding to the first packet loss in the uplink data. The present application does not limit the name of the status report, and the status report may also have other names.

[0184] In some optional embodiments, after S420, method 400 further includes: the terminal device sending a reconfiguration completion message to the first network device. The reconfiguration completion message may be used to indicate that the configuration of the terminal device has taken effect, or that the terminal device has configured the second functional unit. Optionally, the reconfiguration completion message may be used to indicate that the terminal device has configured the RLC bearer associated with the second functional unit. This application does not limit the name of the reconfiguration completion message, and the reconfiguration completion message may also have other names.

[0185] In some optional embodiments, the above-mentioned reconfiguration completion message may carry an SN RRC reconfiguration completion message; the first network device may send an SN RRC reconfiguration completion message to the second network device. In other optional embodiments, the terminal device may send an SN RRC reconfiguration completion message to the second network device. The SN RRC reconfiguration completion message is used to indicate that the configuration of the terminal device is effective, or that the terminal device has configured the second functional unit. Optionally, the SN RRC reconfiguration completion message may be used to indicate that the terminal device has configured the RLC bearer associated with the second functional unit. This application does not limit the name of the SN RRC reconfiguration completion message, and the SN RRC reconfiguration completion message may also have other names. The SN RRC reconfiguration completion message may be sent by the first network device to the second network device through the inter-station interface.

[0186] In some optional embodiments, the terminal device may send an RRC reconfiguration completion message to the second network device. For example, the terminal device and the second network device may support direct transmission of SRB messages.

[0187] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device receives second information, and the second information can be used to indicate that the terminal device has successfully added the second network device.

[0188] As an optional implementation, the second network device may send the second information to the first network device. As another optional implementation, the terminal device may send the second information to the first network device.

[0189] The second network device may perform random access with the terminal device. In some optional embodiments, the second network device may perform random access with the terminal device after receiving the SN RRC reconfiguration complete message. However, this application is not limited to this. For example, the second network device or the terminal device may directly initiate random access.

[0190] The second information can be used to indicate that the terminal device has successfully added the second network device; in other words, the second information can be used to indicate that the terminal device has added the second network device; in other words, the second information can be used to indicate that the terminal device has successfully accessed the second network device; in other words, the second information can be used to indicate that the terminal device has accessed the second network device.

[0191] It should be noted that, in the relevant technical solution, the MN stops the downlink transmission of the corresponding radio bearer after sending the RRC reconfiguration message, and the terminal device stops the uplink transmission of the corresponding radio bearer after receiving the RRC reconfiguration message. After the terminal device accesses the SN, the uplink and downlink transmission of the corresponding radio bearer are restored. Therefore, in the relevant technical solution, the MN does not need to know whether the terminal device has successfully added the SN. In the present application, after sending the first information, the first network device still performs downlink transmission with the terminal device, so it is necessary to know the SN addition status of the terminal device in order to perform corresponding processing.

[0192] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device stops sending data of the first radio bearer to the terminal device, or in other words, the first network device stops downlink transmission of the first radio bearer with the terminal device. Optionally, after the first network device receives the second information, the first network device stops sending data of the first radio bearer to the terminal device. Optionally, after the first network device receives the second information, the first network device stops uplink scheduling (or uplink transmission) of the first radio bearer for the terminal device. Optionally, after the second network device sends the second information, the second network device sends data of the first radio bearer to the terminal device. Optionally, after the first network device receives the second information from the terminal device, the first network device sends indication information to the second network device, the indication information being used to instruct the second network device to perform downlink transmission of the first radio bearer or to send data of the first radio bearer to the terminal device. Optionally, the second network device performs downlink transmission of the first radio bearer or sends data of the first radio bearer to the terminal device based on the indication information. This application does not limit the name of the indication information, and the indication information may also have other names.

[0193] Through the above embodiment, the first network device can stop sending data on the first radio bearer to the terminal device after confirming that the terminal device has added the second network device. Because the terminal device has successfully added the second network device, the second network device can perform downlink transmission on the first radio bearer with the terminal device. The above embodiment allows the terminal device to maintain downlink transmission during the process of reestablishing the protocol entity, thereby avoiding a rate drop.

[0194] Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: the terminal device stops sending the data of the first radio bearer to the first network device, or in other words, the terminal device stops the uplink transmission of the first radio bearer with the first network device. Optionally, after the terminal device successfully adds the second network device, the terminal device stops sending the data of the first radio bearer to the first network device. Optionally, after the terminal device successfully adds the second network device, the second network device receives the data of the first radio bearer from the terminal device, or in other words, the second network device starts the uplink scheduling (or uplink transmission) of the first radio bearer of the terminal device. Optionally, the second network device can uniformly de-duplicate and reorder the uplink PDCP PDU submitted by the first network device and the uplink PDCP PDU sent by the terminal device, and submit them to the core network element. Optionally, the second network device can send the data of the first radio bearer to the core network element through the NG-U tunnel. Optionally, the SN add request received by the second network device from the first network device may include information of the uplink NG-U tunnel, and the second network device may send data of the first wireless bearer to the core network element based on the information of the uplink NG-U tunnel.

[0195] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device sending the data of the first radio bearer to the core network network element; and / or the first network device sending the data of the first radio bearer to the second network device. Accordingly, the second network device receives the data of the first radio bearer from the first network device.

[0196] Optionally, the data of the first radio bearer sent by the first network device to the core network element may be PDCP PDUs with continuous sequence numbers. Optionally, the data of the first radio bearer sent by the first network device to the second network device may be uplink PDCP PDUs with discontinuous sequence numbers. Optionally, the second network device may send the received data of the first radio bearer to the core network element.

[0197] Optionally, the data of the first radio bearer sent by the first network device to the second network device may be downlink data. Optionally, the second network device may send the received data of the first radio bearer to the terminal device.

[0198] Optionally, the first network device may send the data of the first radio bearer to the second network device through an inter-station interface.

[0199] Through the above embodiment, the first network device can deliver the data of the first radio bearer to the second network device, so that the second network device can perform uplink and downlink data transmission, thereby improving the continuity of data transmission.

[0200] Optionally, the first network device may send a PDU session modification indication to a core network network element, such as an access and mobility management function (AMF) network element. The PDU session modification indication may be used to instruct the AMF to modify the NG-U tunnel of the first radio bearer from the first network device side to the second network device side. The PDU session modification indication may also have other names. Optionally, the AMF network element may send a bearer modification indication to a core network network element, such as a user plane function (UPF) network element. The bearer modification indication may be used to instruct the UPF network element to establish an NG-U tunnel corresponding to the first radio bearer, and the NG-U tunnel is used for data transmission between the UPF and the second network device. Optionally, the UPF network element may send an end marker to the first network device. The end marker is used to indicate that the downlink data transmission of the first radio bearer between the UPF and the first network device is completed. Optionally, after the UPF network element sends the end indication, the UPF may send the downlink data of the first radio bearer to the second network device. Optionally, the AMF network element may send an indication message to the first network device to indicate that the PDU session modification is complete. The indication message may also have other names.

[0201] Optionally, the first network device may release at least one of an inter-station tunnel between the first network device and the second network device, an uplink NG-U tunnel between the first network device and a core network element, or a downlink NG-U tunnel between the first network device and the core network element. Optionally, the first network device may perform the above-mentioned release action in response to an indication message indicating that the PDU session modification is complete. In other words, the first network device may perform the above-mentioned release action after receiving an indication message indicating that the PDU session modification is complete.

[0202] Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: the first network device sends third information to the terminal device, where the third information is used to instruct the terminal device to release the first functional unit.

[0203] In some optional embodiments, the third information is used to instruct the terminal device to release the RLC bearer associated with the first functional unit. In other optional embodiments, the information instructing the terminal device to release the first functional unit and the information instructing the terminal device to release the RLC bearer associated with the first functional unit may be different information.

[0204] Optionally, the third information may be 1-bit indication information. As an example, the third information may be used to instruct all radio bearers configured with the dual-active protocol stack to release the original protocol stack resources. As another example, the third information may include or carry the identifier of the radio bearer, i.e., the first network device may instruct some radio bearers configured with the dual-active protocol stack to release the original protocol stack resources. Optionally, the identifier of the radio bearer may not be included in the third information, i.e., the first network device may send the third information along with the identifier of the radio bearer.

[0205] Optionally, in some other implementation scenarios of the above embodiment, method 400 further includes: the second network device sending third information to the terminal device. In other words, the second network device may instruct the terminal device to release the first functional unit. Optionally, the second network device receives instruction information from the first network device, the instruction information being used to instruct the second network device to release the first functional unit of the terminal device. Optionally, in response to the instruction information, or after the second network device receives the instruction information, the second network device sends third information to the terminal device. The above instruction information may have other names.

[0206] Optionally, the second network device may send the third information via the first network device. For example, the second network device may send instruction information to the first network device, instructing the first network device to release the first functional unit of the terminal device. Optionally, in response to the instruction information, or after the first network device receives the instruction information, the first network device may send the third information to the terminal device.

[0207] Optionally, in other implementation scenarios of the above embodiments, the method 400 also includes: the first network device receives fourth information, wherein the fourth information is used to indicate that the session modification of the protocol data unit is completed, the terminal device has submitted all data of the first functional unit, or the terminal device requests to release at least one item of the first functional unit.

[0208] The information indicating that the session modification of the protocol data unit is completed may come from a core network element. The information indicating that the terminal device has submitted all data of the first functional unit or that the terminal device requests to release the first functional unit may come from the terminal device.

[0209] Optionally, the first network device sends the third information to the terminal device, including: responding to the fourth information, or after the first network device receives the fourth information, the first network device sends the third information to the terminal device.

[0210] In one possible scenario, the MCG resource associated with the first functional unit may cache uplink data to be delivered to the first network device. Optionally, after delivering the uplink data of the first functional unit, the terminal device sends fourth information to the first network device.

[0211] This application does not limit the names of the third information and the fourth information, and the third information or the fourth information may also have other names.

[0212] Optionally, the first network device sends indication information to the second network device, where the indication information is used to indicate that the terminal device has released the first functional unit. The above indication information may have other names.

[0213] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the terminal device releasing the first functional unit based on the third information. In other words, the terminal device releases the first functional unit upon receiving the third information. In other words, the terminal device releases the first functional unit after receiving the third information. Optionally, the terminal device releases the RLC bearer associated with the first functional unit.

[0214] Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: the first network device sends fifth information to the second network device, where the fifth information is used to instruct the second network device to configure the first radio bearer to associate the first functional unit and the second functional unit.

[0215] The first network device sending the fifth information to the second network device can be understood as the first network device instructing the second network device to configure the dual-active protocol stack for the first radio bearer. Optionally, the first network device can indicate which radio bearers are configured with the dual-active protocol stack.

[0216] Optionally, the first network device instructs the second functional unit to associate air interface resources of the first network device and / or air interface resources of the second network device, i.e., indicates the bearer type of the first radio bearer. For example, the first network device instructs to configure a split bearer for the first radio bearer, i.e., the second functional unit associates air interface resources of the first network device and / or air interface resources of the second network device.

[0217] Optionally, the fifth information includes capability information of the terminal device. For example, the capability information of the terminal device may indicate that the terminal device is capable of supporting a dual-active protocol stack.

[0218] Optionally, the first network device determines to configure the first radio bearer to be associated with the first functional unit and the second functional unit; and the first network device sends fifth information to the second network device. That is, the first network device may decide to configure a dual-activation protocol stack for the first radio bearer. Optionally, the first network device may determine to configure the first radio bearer to be associated with the first functional unit and the second functional unit based on the capabilities of the terminal device. For example, if the capabilities of the terminal device support the dual-activation protocol stack, the first network device determines to configure the first radio bearer to be associated with the first functional unit and the second functional unit. For another example, if the capabilities of the terminal device do not support the dual-activation protocol stack, the first network device determines not to configure the first radio bearer to be associated with the first functional unit and the second functional unit.

[0219] The fifth information may be carried in the SN add request message, but this application does not limit this, and the fifth information may be carried in other messages. This application does not limit the name of the fifth information, and the fifth information may have other names.

[0220] In some optional embodiments, the first network device may send an SN add request message to the second network device, where the SN add request message includes an add instruction, where the add instruction is used to instruct the second network device to add the first radio bearer. Optionally, the add instruction is used to indicate that a functional unit of the first radio bearer is on the second network device side, i.e., the first radio bearer corresponds to, is associated with, or terminates on the second network device. Optionally, the SN add request message includes fifth information.

[0221] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device receiving sixth information from the second network device, the sixth information being used to instruct the second network device to determine to configure the first radio bearer to associate the first functional unit with the second functional unit. Accordingly, the second network device sends the sixth information to the first network device.

[0222] The second network device sending the sixth message to the first network device can be understood as the second network device indicating its agreement to configure the dual-active protocol stack for the first radio bearer. In other words, the second network device can agree to configure the dual-active protocol stack for the first radio bearer via the sixth message in response to the fifth message sent by the first network device.

[0223] Optionally, the fifth information includes capability information of the terminal device. For example, the capability information of the terminal device may indicate that the terminal device supports the dual-activation protocol stack. Optionally, the second network device determines whether to agree to configure the dual-activation protocol stack for the first radio bearer based on the capability information of the terminal device. For example, if the capability of the terminal device supports the dual-activation protocol stack, the second network device agrees to configure the dual-activation protocol stack for the first radio bearer. For another example, if the capability of the terminal device does not support the dual-activation protocol stack, the second network device does not agree to configure the dual-activation protocol stack for the first radio bearer.

[0224] In other optional embodiments, the second network device sends an indication message indicating that it is determined not to configure the first radio bearer to associate the first functional unit with the second functional unit. In other words, the second network device indicates that it does not agree to configure the dual-active protocol stack for the first radio bearer. The above indication message may also have other names, which are not limited in this application.

[0225] The sixth information can be carried in the SN add response message, but this application is not limited to this. The sixth information can be carried in other messages.

[0226] Optionally, the second network device determines to configure the first radio bearer to associate the first functional unit with the second functional unit; the second network device sends sixth information to the first network device. In other words, the second network device can determine whether to agree to configure the dual-active protocol stack for the first radio bearer.

[0227] Optionally, in some other implementation scenarios of the above embodiments, the method 400 also includes: the first network device receives second indication information from the second network device, and the second indication information is used to instruct the first network device to configure the first wireless bearer to associate the first functional unit and the second functional unit.

[0228] The second indication information can be carried in the SN add response message, but this application is not limited to this. The second indication information can be carried in other messages.

[0229] Optionally, the second network device determines to configure the first radio bearer to associate the first functional unit with the second functional unit, and the second network device sends second indication information to the first network device. In other words, the second network device may decide to configure a dual-active protocol stack for the first radio bearer.

[0230] Optionally, the first network device sends an SN add request message to the second network device to request that the first radio bearer be established on the second network device side. Optionally, the SN add request message may include capability information of the terminal device. For example, the capability information of the terminal device may indicate that the capability of the terminal device supports the dual-activation protocol stack. Optionally, the second network device determines whether to configure the dual-activation protocol stack for the first radio bearer based on the capability information of the terminal device. For example, if the capability of the terminal device supports the dual-activation protocol stack, the second network device determines to configure the dual-activation protocol stack for the first radio bearer. For another example, if the capability of the terminal device does not support the dual-activation protocol stack, the second network device determines not to configure the dual-activation protocol stack for the first radio bearer. Optionally, the second network device determines whether to configure the dual-activation protocol stack for the first radio bearer based on at least one of the type of the first radio bearer or the QoS requirement.

[0231] Optionally, during the process of establishing an inter-station interface between the first network device and the second network device, the first network device sends the capability information of the first network device to the second network device and receives the capability information of the second network device. During the process of establishing an inter-station interface between the second network device and the first network device, the second network device sends the capability information of the second network device to the first network device and receives the capability information of the first network device. The capability information of the first network device may be used to indicate whether the first network device is capable of configuring a first radio bearer to associate the first functional unit with the second functional unit. The capability information of the second network device may be used to indicate whether the second network device is capable of configuring a first radio bearer to associate the first functional unit with the second functional unit.

[0232] That is, the first network device and the second network device may negotiate in advance to obtain base station capability information, and learn whether the first network device or the second network device supports configuration of the dual-active protocol stack.

[0233] Optionally, in some other implementation scenarios of the above embodiment, the first information includes third indication information, and the third indication information is used to indicate that the first configuration information is pre-configuration information. Optionally, the first configuration information corresponds to the second network device.

[0234] The first configuration information may be pre-configuration information; in other words, the first configuration information may not be effective temporarily; in other words, the first configuration information may be configuration information to be activated; in other words, the first configuration information may be inactivated configuration information.

[0235] Optionally, the third indication information may be added by the first network device. Optionally, the third indication information may be added by the second network device. This application does not limit the source of the third indication information. Optionally, the first configuration information may include the third indication information. Optionally, the second network device sends indication information to the first network device, where the indication information is used to indicate to the first network device that the first configuration information is pre-configured information.

[0236] This application does not limit the name of the third indication information, and the third indication information may have other names.

[0237] The message carried by the first information may be called a pre-configuration message, an RRC pre-configuration message or have other names. In some optional embodiments, the third indication information may not be included in the first information, that is, the third indication information and the first configuration information are sent separately.

[0238] Optionally, the first network device sends fifth information to the second network device, where the fifth information is used to request the second network device to preconfigure the first radio bearer to be associated with the first functional unit and the second functional unit. Optionally, the second network device determines to the first network device to preconfigure the first radio bearer to be associated with the first functional unit and the second functional unit; and the first network device sends the fifth information to the second network device.

[0239] The first network device sending the fifth information to the second network device can be understood as the first network device instructing the second network device to pre-configure the dual-active protocol stack for the first radio bearer. Optionally, the first network device can indicate which radio bearers are pre-configured with the dual-active protocol stack. Optionally, the fifth information includes the terminal device's capability information. For example, the terminal device's capability information can indicate that the terminal device supports the dual-active protocol stack.

[0240] Optionally, the first network device determines to preconfigure the first radio bearer to be associated with the first functional unit and the second functional unit; and the first network device sends fifth information to the second network device. That is, the first network device may decide to preconfigure a dual-active protocol stack for the first radio bearer. Optionally, the first network device may determine to preconfigure the first radio bearer to be associated with the first functional unit and the second functional unit based on the capabilities of the terminal device. For example, if the capabilities of the terminal device support the dual-active protocol stack, the first network device determines to preconfigure the first radio bearer to be associated with the first functional unit and the second functional unit. For another example, if the capabilities of the terminal device do not support the dual-active protocol stack, the first network device determines not to preconfigure the first radio bearer to be associated with the first functional unit and the second functional unit.

[0241] Optionally, the fifth information includes information requesting the second network device to preconfigure the first radio bearer associated with the first functional unit and the second functional unit. Optionally, the information requesting the second network device to preconfigure the first radio bearer associated with the first functional unit and the second functional unit may be independent of the fifth information. For example, the first network device may send a first configuration message to the second network device requesting the second network device to preconfigure the first radio bearer associated with the first functional unit and the second functional unit.

[0242] Optionally, the sixth information is used to indicate the determination to pre-configure the first radio bearer to associate the first functional unit with the second functional unit. Optionally, the second network device determines to pre-configure the first radio bearer to associate the first functional unit with the second functional unit; the second network device sends the sixth information to the first network device.

[0243] The second network device sending the sixth information to the first network device can be understood as the second network device indicating its agreement to pre-configure the dual-active protocol stack for the first radio bearer. In other words, in response to the fifth information sent by the first network device, the second network device can agree to pre-configure the dual-active protocol stack for the first radio bearer through the sixth information.

[0244] Optionally, the sixth information includes information indicating that the pre-configured first radio bearer is associated with the first functional unit and the second functional unit. Optionally, the information indicating that the pre-configured first radio bearer is associated with the first functional unit and the second functional unit may be independent of the sixth information. For example, the second network device may send information indicating that the pre-configured first radio bearer is associated with the first functional unit and the second functional unit to the first network device.

[0245] Optionally, the second indication information is used to instruct the first network device to preconfigure the first radio bearer to associate the first functional unit with the second functional unit. Optionally, the second network device determines to preconfigure the first radio bearer to associate the first functional unit with the second functional unit; and the second network device sends the second indication information to the first network device.

[0246] Optionally, the second indication information includes information indicating that the first radio bearer is pre-configured to be associated with the first functional unit and the second functional unit. Optionally, the information indicating that the first radio bearer is pre-configured to be associated with the first functional unit and the second functional unit may be independent of the second indication information. For example, the second network device may send information indicating that the first radio bearer is pre-configured to be associated with the first functional unit and the second functional unit to the first network device.

[0247] Optionally, the first network device generates configuration information for at least one candidate third network device. The second network device of the present application is one of the at least one third network device. The difference is that the second network device is the network device that is ultimately selected, or in other words, the configuration information of the second network device (i.e., the first information) is ultimately effective. For example, the at least one candidate third network device can be at least one candidate SN. Optionally, the configuration information from the at least one third network device includes the first indication information.

[0248] Optionally, the first network device determines to perform pre-configuration for the terminal device to add a second network device. Optionally, the first network device determines at least one third network device based on the measurement report of the terminal device. Optionally, the first network device determines whether to perform pre-configuration for the terminal device to add a second network device based on the capability information of the terminal device. For example, if the capabilities of the terminal device support pre-configuration, the first network device determines to perform pre-configuration for the terminal device to add a second network device. For another example, if the capabilities of the terminal device do not support pre-configuration, the first network device determines not to perform pre-configuration for the terminal device to add a second network device.

[0249] Optionally, the first network device receives capability information of the second network device. For example, the first network device may receive capability information of the second network device during the process of establishing an inter-station connection. Optionally, the first network device determines whether the second network device can be added as a pre-configured candidate base station (or target base station) as the second network device.

[0250] Optionally, the SN add request message includes a pre-configuration request. Optionally, the pre-configuration request includes a radio bearer add indication.

[0251] Optionally, S410 includes: the first network device receives configuration information from at least one third network device. The second network device is one of the at least one third network device. Optionally, S420 includes: the first network device sends the configuration information of the at least one third network device to the terminal device. Optionally, the first network device sends third indication information, and the third indication information is used to indicate that at least one set of configuration information is pre-configuration information. Optionally, the first network device sends at least one third indication information, and the at least one third indication information corresponds to at least one set of configuration information, and the at least one third indication information is used to indicate that at least one set of configuration information is pre-configuration information. Optionally, one set of configuration information in the at least one set of configuration information and the third indication information corresponding to the configuration information can be carried in one message. Optionally, one or more sets of configuration information in the at least one set of configuration information from the first network device include the first indication information. Optionally, the third indication information includes the first indication information.

[0252] Optionally, the terminal device is pre-configured according to at least one set of configuration information. Optionally, the terminal device sends an RRC reconfiguration complete message to the first network device, where the RRC reconfiguration complete message is used to indicate that the terminal device has received at least one set of configuration information. This application does not limit the name of the RRC reconfiguration complete message, and the RRC reconfiguration complete message may also have other names.

[0253] Optionally, in some other implementation scenarios of the above embodiments, the first configuration information corresponds to the information of the second network device, wherein the method 400 also includes: the first network device sends seventh information to the terminal device, the seventh information is used to activate the configuration of the first configuration information, and the seventh information includes the information of the second network device.

[0254] The first configuration information corresponds to information about the second network device. Optionally, at least one set of configuration information has a mapping relationship with at least one candidate third network device. For example, a mapping table includes information about at least one set of configuration information and at least one candidate third network device. Optionally, an identifier of at least one set of configuration information has a mapping relationship with information about at least one candidate third network device. For example, a mapping table includes an identifier of at least one set of configuration information and information about at least one candidate third network device. The identifier of the configuration information corresponds to the configuration information.

[0255] The first configuration information corresponds to information about the second network device. Optionally, the first configuration information includes information about the second network device. Thus, the first configuration information can be matched based on the information about the second network device. However, this application is not limited to this, and the information about the second network device may not be included in the first configuration information. In other words, the information about the second network device and the first configuration information may be sent separately.

[0256] Exemplarily, the information of the second network device may include at least one of identification information of the second network device, numbering information of the second network device, identification information of a node of the second network device, or identification information of a cell of the second network device.

[0257] The present application does not limit the name of the seventh information, and the seventh information may also have other names, such as L1 indication or L2 indication. The seventh information may be lower layer indication information, such as a MAC control element (CE). Optionally, the seventh information includes the first indication information.

[0258] The seventh information is used to activate the configuration of the first configuration information; in other words, the seventh information is used to activate the application of the first configuration information. For example, the seventh information is used to trigger the terminal device to apply the first configuration information. For another example, the seventh information is used to activate or trigger the terminal device to apply the first configuration information (or pre-configuration information) corresponding to the second network device. It is understandable that the seventh information can indicate which set of pre-configurations the terminal device triggers.

[0259] Optionally, the first network device may indicate information of the second network device in the seventh information. For example, at least one of the identification information of the second network device, the numbering information of the second network device, the identification information of the node of the second network device, or the identification information of the cell of the second network device. The terminal device may determine the configuration information (i.e., the first information) that triggers the second network device based on the information of the second network device. Optionally, S430 includes: the terminal device establishes the second functional unit based on the seventh information and the first configuration information. In other words, the seventh information activates the configuration of the first configuration information. Optionally, S430 includes: the terminal device adds the second network device based on the seventh information and the first configuration information. Optionally, S430 includes: the terminal device establishes the second functional unit and adds the second network device based on the seventh information and the first configuration information.

[0260] Optionally, the terminal device matches the first configuration information corresponding to the second network device based on the information of the second network device; the terminal device establishes the second functional unit based on the first configuration information. In other words, the terminal device triggers the first configuration information of the second network device based on the information of the second network device.

[0261] It is understandable that the terminal device can apply the corresponding configuration according to the instructions of the first network device and access the second network device (or referred to as the target SN). For the radio bearer configured with the dual-activation protocol stack (i.e., the first radio bearer), the original PDCP (i.e., the first functional unit) and the associated underlying configuration (e.g., RLC bearer) will be maintained, and a new PDCP (i.e., the second functional unit) will be established and configured and associated with the corresponding underlying configuration. Optionally, the terminal device can maintain downlink synchronization with the candidate SN in advance based on the pre-configured information, thereby reducing the duration of access to the second network device.

[0262] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device receives a first message from the terminal device, the first message is used to indicate that the terminal device has successfully added the second network device, and the first message includes fifth indication information, and the fifth indication information is used to indicate that the terminal device has completed the configuration corresponding to the second network device. The first message can be called an RRC reconfiguration completion message or have other names. Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device sends the fifth indication information to the second network device.

[0263] Optionally, after receiving the first message, the first network device activates a preconfigured tunnel corresponding to the first network device. The preconfigured tunnel corresponding to the first network device may include at least one of a downlink Xn-U tunnel or an uplink Xn-U tunnel between the first network device and the second network device. Optionally, after receiving the fifth indication information, the second network device activates a preconfigured tunnel corresponding to the second network device. For example, the second network device activates an NG-U tunnel configuration between the second network device and a core network element, where the NG-U tunnel is used to send uplink data of the first radio bearer to the core network element.

[0264] Optionally, the fifth indication information includes an identifier of the terminal device. It is understood that, if multiple terminal devices pre-configure the candidate second network device, the second network device can trigger the pre-configuration corresponding to the terminal device based on the identifier of the terminal device. Optionally, the identifier of the terminal device may not be included in the fifth indication information. In other words, the identifier of the terminal device may be independent of the fifth indication information. Optionally, the first network device sends the identifier of the terminal device to the second network device.

[0265] Optionally, the first network device sends seventh information; the first network device activates the pre-configured tunnel. That is, after activating the pre-configuration information, the first network device activates the corresponding pre-configured tunnel.

[0266] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device activating a pre-configured tunnel between the first network device and the second network device.

[0267] Optionally, the terminal device sends fifth indication information to the second network device; the second network device activates the pre-configured tunnel corresponding to the second network device.

[0268] Optionally, the first network device sends fourth indication information to the second network device, where the fourth indication information is used to instruct the terminal device to add the second network device according to the first configuration information; the second network device activates a pre-configured tunnel corresponding to the second network device.

[0269] The preconfigured tunnel corresponding to the second network device may also be activated by the first network device. Optionally, in some other implementation scenarios of the above embodiment, method 400 further includes: the first network device sending eighth information to the core network element, the eighth information being used to instruct activation of the preconfigured tunnel corresponding to the second network device. Optionally, the preconfigured tunnel corresponding to the second network device is associated with data of the first radio bearer.

[0270] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device sends ninth information to the core network network element (e.g., AMF), where the ninth information is used to instruct to release the pre-configured tunnels corresponding to network devices other than the second network device. That is, after the first network device activates the pre-configuration information and the pre-configured tunnel, the first network device can release other pre-configured tunnels, such as the NG-U tunnel.

[0271] In another possible implementation, the first network device also configures multiple candidate third network devices for the terminal device through preconfiguration. However, the terminal device can actively trigger access to the second network device.

[0272] Figure 6 is a schematic flow chart of another communication method 600 provided in an embodiment of the present application. Method 600 can be combined with any embodiment of method 400. For portions not described in method 600, reference can be made to the description of method 400. The dashed arrows in Figure 6 may indicate the direction of data transmission. It should be noted that Figure 6 is provided for example only and does not constitute a limitation of the present application.

[0273] S601, MN sends a secondary station adding request message to SN.

[0274] S602: The SN sends a secondary station adding response message to the MN.

[0275] In S601 and S02, the MN and the SN may negotiate to determine whether to support dual-active protocol stack configuration.

[0276] One possible way is that the MN instructs the SN to configure a dual-active protocol stack for the corresponding radio bearer (eg, the first radio bearer). Detailed information can be found in the above description of the fifth information and the sixth information, which will not be repeated here.

[0277] Another possible way is that the SN determines that the corresponding radio bearer (eg, the first radio bearer) supports the dual-active protocol stack configuration. For details, please refer to the description of the second indication information above, which will not be repeated here.

[0278] Optionally, the MN and the SN may previously negotiate (for example, during the process of establishing an inter-station interface) to obtain base station capability information and learn whether the SN or the MN supports configuration of a dual-active protocol stack.

[0279] S603: The MN sends a tunnel establishment message to the SN.

[0280] The tunnel establishment message may be used to instruct the establishment of a tunnel on an inter-station interface. The tunnel may be used for downlink data transmission of an SN-terminated MCG bearer or a split bearer.

[0281] S604: The MN sends an RRC reconfiguration message to the UE.

[0282] The RRC reconfiguration message may be used to instruct the UE to add and configure a secondary station. Optionally, the RRC reconfiguration message may include first information. For details, please refer to the description of the first information above, which will not be repeated here.

[0283] S605: The UE performs random access with the SN.

[0284] The UE may connect to the SN via random access based on the RRC configuration in the RRC reconfiguration message. Optionally, the UE may maintain a connection with the MN. Exemplarily, the RRC configuration may include at least one of: configuration of an SN-terminated bearer, an SN PDCP configuration, or air interface resource configuration associated with the SN-terminated bearer. For details, refer to the description of the first configuration information and the second configuration information, which are not repeated here.

[0285] Based on the above configuration, the UE side will maintain two sets of PDCP corresponding protocol stacks and their processing. For details, please refer to the description of Figures 3 to 5, which will not be repeated here.

[0286] S606: The UE sends an RRC reconfiguration complete message to the MN.

[0287] Optionally, the RRC reconfiguration complete message may be used to indicate configuration completion, and the RRC reconfiguration complete message may include an SN RRC reconfiguration complete message.

[0288] S607: The MN sends an SN reconfiguration completion message to the SN.

[0289] The RRC reconfiguration complete message for the SN may indicate to the SN that the UE has completed the dual connectivity configuration.

[0290] It should be noted that this application does not limit the execution order of S605, S606, and S607. For example, the execution order can be: S606, S607, S605. For another example, the execution order can be: S606, S605, S607.

[0291] S608, SN sends a SN adding success message.

[0292] The SN add success message is used to indicate that the MN secondary station has been successfully added. Optionally, the MN stops sending downlink data and the SN starts sending downlink data to the UE. The description of the SN add success message can be found in the description of the second information in this application and is not repeated here.

[0293] S608 is an optional step. In other optional embodiments, S608 may be replaced by: the UE sends an SN adding success message.

[0294] S609: MN sends a status report instruction to SN.

[0295] For example, the status report indication may be used to indicate the next downlink PDCP sequence number. For another example, the status report indication may be used to indicate the sequence number corresponding to the first lost packet in the uplink data.

[0296] It should be noted that this application does not limit the execution order of S609. For example, S609 may be before S608.

[0297] S610: The MN sends a PDU session modification message to the AMF.

[0298] The PDU Session Modification message can be used to instruct the AMF to perform PDU session modification. In other words, the PDU Session Modification message can be used to instruct the corresponding bearer NG-U tunnel to switch from the MN side to the SN side.

[0299] S611, AMF sends a bearer modification message to UPF.

[0300] The bearer modification message is used to instruct the UPF to establish a corresponding downlink NG-U tunnel, which is used to send downlink data.

[0301] S612: UPF sends end marker information to MN.

[0302] Optionally, the UPF sends the end marker information through the downlink NG-U tunnel on the source MN side. The end marker information can be used to indicate the completion of downlink data transmission. Subsequently, the UPF sends the downlink data of the radio bearer through the SN. Optionally, S612 includes: the UPF sends the end marker information to the MN when the downlink data transmission is completed.

[0303] S613: AMF sends a PDU session modification confirmation message to the MN.

[0304] The PDU session modification confirmation message may be used to indicate that the PDU session modification is complete.

[0305] In the downlink data transmission direction, after sending the RRC reconfiguration message (S604), the MN maintains downlink transmission and delivers downlink data to the SN via the inter-station interface (established in S603) (the dotted arrow in the figure indicates the data forwarding process). Optionally, the MN can send a status report (S609) to indicate the clearing of successfully transmitted uplink and downlink data. This status report indicates the uplink and downlink data that the UE has successfully received on the MN side.

[0306] During the uplink data transmission process, after receiving the secondary station addition configuration (S604), the UE continues to send uplink data to the MN until it successfully randomly accesses the SN (S605). After sending the RRC reconfiguration message (S604), the MN maintains uplink scheduling (i.e., maintains uplink transmission) and submits the uplink data to the UPF.

[0307] After the UE successfully accesses the SN, the SN can indicate to the MN that the secondary station has been successfully added (S608). The MN stops uplink scheduling and simultaneously delivers uplink PDCP PDUs with consecutive sequence numbers to the core network and delivers uplink PDCP PDUs with discontinuous sequence numbers to the SN via the inter-station interface (the data delivery process is represented by the dotted arrow in the figure). The status report in S609 can indicate the uplink direction, that is, the sequence number corresponding to the first packet loss on the MN side.

[0308] Optionally, when the SN receives the secondary station addition request (S601), it includes uplink NG-U tunnel information. This uplink NG-U tunnel can be used to transmit data of the SN-terminated radio bearer to the UPF. After the UE successfully accesses the SN (S605), the SN can start uplink scheduling for the UE. The SN will uniformly de-duplicate and reorder the uplink PDCP PDU submitted by the MN and the uplink PDCP PDU received from the UE, and submit them to the core network.

[0309] Optionally, after receiving the PDU session modification confirmation message (S613), the MN releases the inter-station tunnel and the uplink and downlink NG-U tunnels with the core network. Optionally, the UE is instructed to release the dual activation protocol stack. After the UE side receives the dual activation release indication, the UE releases the configuration related to the original protocol stack, releases the original PDCP entity, and releases the RLC entity associated with the original PDCP. Optionally, the MN sends a dual activation protocol stack release indication to the SN, indicating that the UE side has released the dual activation protocol stack. Optionally, the SN instructs the UE to release the dual activation protocol stack, for example, based on the MN indication, or the SN can send the dual activation protocol stack indication to the UE through the MN. For details, please refer to the above description of the third information, which will not be repeated here.

[0310] Optionally, uplink data delivered to the MN may be cached on the MCG resource associated with the original PDCP on the UE side. After delivering the uplink data on the original protocol stack, the UE sends an end indication (i.e., the fourth information) to the MN. Upon receiving the end indication, the MN sends a dual-activation release indication to the UE based on the end indication. For details, please refer to the description of the fourth information above, which will not be repeated here.

[0311] Optionally, the MN sends an indication message to the SN, indicating that the UE side has released the dual-active protocol stack.

[0312] Figure 7 is a schematic flow chart of another communication method 700 provided in an embodiment of the present application. Method 700 can be combined with any embodiment of method 400. Method 700 is an embodiment related to preconfiguration. For any undescribed parts, please refer to the description of method 400. The dashed arrows in Figure 7 may indicate the direction of data transmission. It should be noted that Figure 7 is provided for illustrative purposes only and does not constitute a limitation of the present application.

[0313] S701: The MN sends a secondary station addition pre-configuration request message to at least one SN.

[0314] The at least one SN may be referred to as a candidate SN. The secondary station addition pre-configuration request message may be used to request the SN to perform pre-configuration for adding a secondary station. Optionally, the secondary station addition pre-configuration request message includes a radio bearer addition indication.

[0315] Optionally, the MN determines to pre-configure the secondary station addition for the UE. Optionally, the MN determines a target SN for the pre-configuration based on the measurement report of the UE. Optionally, the MN determines whether to pre-configure the secondary station addition for the UE based on the capabilities of the UE. Optionally, the MN obtains capability information of the SN based on previous inter-station interactions and determines whether the SN can serve as the target SN for the pre-configuration of the secondary station addition.

[0316] S702, the SN sends a secondary station addition pre-configuration response message to the MN.

[0317] It is understandable that at least one SN sends a secondary station add preconfiguration response message to the MN respectively. Optionally, the SN generates an RRC preconfiguration on the secondary station side and sends it to the MN via a secondary station add preconfiguration response message.

[0318] In one possible implementation, the MN determines whether to configure a dual-active protocol stack for a radio bearer and indicates this in the Secondary Station Add Pre-Configuration Request message in S701. Based on the MN's indication, the SN generates a radio bearer configuration, which includes a dual-active protocol stack configuration indication. Optionally, the SN may determine whether to configure the dual-active protocol stack and instruct the MN. In another possible implementation, the SN determines whether to configure the dual-active protocol stack. For example, based on the radio bearer type or QoS requirements, the SN determines to configure the dual-active protocol stack for the radio bearer and instructs the MN.

[0319] S703: The MN sends a tunnel establishment pre-configuration message to at least one SN.

[0320] Optionally, the MN indicates a pre-configured downlink Xn-U address to at least one SN for a radio bearer terminated by the SN.

[0321] S704: The MN sends an RRC reconfiguration message to the UE.

[0322] Optionally, the MN generates a configuration of one or more candidate SNs. In other words, the RRC reconfiguration message corresponds to at least one SN. The RRC reconfiguration message may include the RRC configuration in S702. Optionally, the RRC reconfiguration message may include third indication information, which may be used to indicate that the RRC reconfiguration message is a pre-configuration message. For details, refer to the description of the third indication information above and will not be repeated here.

[0323] Optionally, the RRC reconfiguration message includes identification information or number information corresponding to at least one SN, or node identification information or cell identification information corresponding to at least one SN. Optionally, after receiving the RRC reconfiguration message, the UE replies to the MN with an RRC reconfiguration complete message.

[0324] S705: The MN sends an activation instruction to the UE.

[0325] Optionally, the activation instruction may include seventh information. Please refer to the above description of the seventh information for details, which will not be repeated here.

[0326] Optionally, the MN determines to trigger the UE to apply the preconfiguration corresponding to the SN. For example, the MN determines that a triggering condition is met based on a measurement report of the UE.

[0327] S706: The UE and the SN perform random access.

[0328] For example, the UE applies the corresponding configuration based on the MN's activation indication and accesses the target SN. Meanwhile, for radio bearers configured with a dual-active protocol stack, the original PDCP and associated underlying configurations are maintained, while a new PDCP entity is established (or new PDCP functions are configured within the original PDCP entity) and the corresponding underlying configurations are configured and associated. Optionally, the UE can pre-synchronize downlink traffic with the candidate SN based on pre-configuration, thereby reducing the time required to access the target SN.

[0329] S707: The UE sends an RRC reconfiguration complete message to the MN.

[0330] The RRC reconfiguration complete message may be used to indicate that the UE has successfully accessed the SN.

[0331] S708, the MN sends an SN RRC reconfiguration completion message to the SN.

[0332] Optionally, the UE includes an RRC reconfiguration complete message for the SN in the RRC reconfiguration complete message (S707) sent to the MN. After receiving the RRC reconfiguration complete message, the MN parses the RRC reconfiguration complete message for the SN from the RRC reconfiguration complete message and forwards it to the SN.

[0333] In another possible implementation, if the UE and the SN support direct transmission of SRB messages, the UE may directly send the RRC reconfiguration complete message to the SN. That is, S708 may be replaced by: the UE sends the SN RRC reconfiguration complete message to the SN.

[0334] S709: MN sends a tunnel activation message to SN.

[0335] Among them, the tunnel activation message is used to activate the corresponding Xn-U / NG-U tunnel configuration. Optionally, the tunnel activation message includes the UE identifier. It is understandable that when multiple UEs pre-configure the candidate SN, the SN can trigger the pre-configuration corresponding to the UE based on the UE identifier. Optionally, the UE identifier may not be in the tunnel activation message. In other words, the UE identifier may be independent of the tunnel activation message. Optionally, the MN sends the UE identifier to the SN.

[0336] Specifically, the MN can activate the downlink Xn-U tunnel configuration from the SN to the MN, as well as the Xn-U tunnel configuration for data transmission. Optionally, the SN activates the NG-U tunnel configuration between the SN and the core network to forward uplink data of the radio bearer to the core network. In another possible manner, after S705, or when the conditions for executing S705 are met, the MN triggers the activation of the corresponding Xn-U tunnel and instructs the SN to activate the Xn-U tunnel configuration and the NG-U tunnel configuration between the SN and the core network. In other words, the execution order of S709 can be before S706 or S705.

[0337] Optionally, the MN stops sending downlink data and uplink scheduling, and performs data transmission.

[0338] S710, the MN sends status indication information to the SN, which is used to indicate the uplink and downlink data transmission status.

[0339] Optionally, S711 to S714 may refer to the description of S610 to S613 and are not repeated here.

[0340] S711 to S714 are optional steps and can be implemented through pre-configuration. After S701 or S702, the MN can trigger the PDU session modification on the core network side to establish the NG-U tunnel between the UPF and the SN in advance. Optionally, after S606, the MN instructs the AMF, and the AMF instructs the UPF to activate the PDU session modification to the target SN. At the same time, the MN will release the NG-U tunnel on the MN side. The SN can directly trigger the activation of the NG-U tunnel based on the configuration for uplink and downlink data transmission.

[0341] Optionally, based on the configuration currently in effect on the UE, the MN determines that there is no longer uplink and downlink data transmission between the UE and the MN's PDCP entity (or PDCP function), and instructs the UE to release the dual-active protocol stack. The solution for instructing the UE to release the dual-active protocol stack can be found in the description of the third information above and is not repeated here.

[0342] Optionally, the MN instructs the remaining candidate SNs to release the previous candidate configuration, and instructs the AMF to release the pre-configured NG-U tunnel between the SN and the core network.

[0343] Optionally, the MN configures a candidate SN for the UE through pre-configuration. The difference is that the UE triggers access to the target SN by itself. That is, the execution of S706 does not depend on S705, and the UE can actively execute S706.

[0344] The following is an introduction to the device embodiment corresponding to the method embodiment of the present application. The following is only a brief introduction to the device, and the specific implementation steps and details of the solution can be referred to the method embodiment above.

[0345] To implement the various functions of the method provided herein, the communication device may include hardware structures and / or software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0346] Figure 8 is a schematic block diagram of a communication device 800 according to an embodiment of the present application. The communication device 800 includes a processor 810 and a communication interface 820, which may be interconnected via a bus 830. The communication device 800 may be a first network device, a second network device, or a terminal device.

[0347] Optionally, the communication device 800 may further include a memory 840. The memory 840 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM). The memory 840 is used for related instructions and data. The memory 840 may be integrated with the processor 810 or provided separately.

[0348] The processor 810 may be one or more central processing units (CPUs). In the case where the processor 810 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor 810 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application, or a portion of the circuitry used for processing functions in the aforementioned processor, chip, or integrated circuit. In addition, the communication interface 820 may also be an input / output interface, which is used for inputting or outputting signals or data, or may be an input / output circuit.

[0349] Exemplarily, the communication device 800 is a first network device, and the processor 810 is used to perform the following operations: receive first configuration information from a second network device, the first configuration information being used to configure a second functional unit associated with a first wireless bearer, and the first network device and the second network device providing services for a terminal device; send first information to the terminal device, the first information including the first configuration information and first indication information, the first information being used to indicate the addition of the second network device, the first indication information being used to indicate the association of the first wireless bearer with the first functional unit, wherein the first functional unit is used to process data corresponding to the first network device, and the second functional unit is used to process data corresponding to the second network device.

[0350] Exemplarily, the communication device 800 is a terminal device, and the processor 810 is used to perform the following operations: receive first information from a first network device, the first information including first configuration information and first indication information, the first configuration information being used to configure the second functional unit associated with the first wireless bearer, the first information being used to indicate the addition of the second network device, and the first indication information being used to indicate the first wireless bearer is associated with the first functional unit, wherein the first functional unit is used to process data corresponding to the first network device, the second functional unit is used to process data corresponding to the second network device, and the first network device and the second network device provide services for the terminal device; and according to the first information, establish the second functional unit and add the second network device.

[0351] Exemplarily, the communication device 800 is a second network device, and the processor 810 is used to perform the following operations: sending first configuration information to the first network device, the first configuration information is used to configure a second functional unit associated with a first wireless bearer for the terminal device, and the second functional unit is used to process data corresponding to the second network device; sending second indication information to the first network device, the second indication information is used to indicate that the first wireless bearer is associated with a first functional unit, and the first functional unit is used to process data corresponding to the first network device, and the first network device and the second network device provide services for the terminal device.

[0352] The above contents are merely exemplary descriptions. The communication device 800 is responsible for executing the methods or steps related to the first network device, the terminal device, or the second network device in the above method embodiments.

[0353] It is understood that the communication interface 820 may also be referred to as a transceiver. The transceiver may include a transmitter and a receiver, where the transmitter is used to perform a transmission operation and the receiver is used to perform a reception operation. For example, the processor 810 is used to control the transceiver to receive and / or transmit signals.

[0354] It should be noted that the communication device 800 may include a transmitter but not a receiver. Alternatively, the communication device 800 may include a receiver but not a transmitter. The specific implementation depends on whether the above solution executed by the communication device 800 includes a sending action and a receiving action.

[0355] The above description is merely exemplary. For details, please refer to the contents of the above method embodiments. The implementation of each operation in FIG8 may also correspond to the corresponding description of the method embodiments shown in FIG3 to FIG7.

[0356] For example, the communication device 800 may be used to implement the solutions shown in FIG. 3 to FIG. 7 .

[0357] Exemplarily, the communication apparatus 800 is a first network device, and the communication interface 820 may be configured to receive first configuration information from a second network device; and to send first information to the terminal device.

[0358] Exemplarily, the communication apparatus 800 is a terminal device, and the communication interface 820 may be configured to receive first information from a first network device.

[0359] Exemplarily, the communication apparatus 800 is a second network device, and the communication interface 820 may be configured to send first configuration information to a first network device; and to send second indication information to the first network device.

[0360] For other implementations, please refer to the detailed description of the embodiments shown in Figures 3 to 7 above, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been detailed in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0361] Figure 9 is a schematic block diagram of another communication device 900 according to an embodiment of the present application. Communication device 900 may be a terminal device, a first network device, or a second network device, or may be a chip or module within the terminal device, the first network device, or the second network device, and is configured to implement the methods described in the embodiments of Figures 2 to 7 . For details, please refer to the relevant descriptions of the aforementioned method embodiments.

[0362] The communication device 900 includes a transceiver unit 910. The transceiver unit 910 is described below by way of example.

[0363] The transceiver unit 910 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting action of the communication device, and the receiving unit is used to perform the receiving action of the communication device. For ease of description, the embodiments of the present application combine the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later. The transceiver unit 910 can implement corresponding communication functions. The transceiver unit 910 can also be referred to as a communication interface or communication module.

[0364] It should be noted that the communication device 900 may include a sending unit but not a receiving unit. Alternatively, the communication device 900 may include a receiving unit but not a sending unit. The specific implementation depends on whether the above solution executed by the communication device 900 includes a sending action and a receiving action.

[0365] Exemplarily, the transceiver unit 910 is configured to receive first configuration information from a second network device.

[0366] Optionally, the communication device 900 may include a processing unit 920, which is used to execute the content of the communication device 900 involving processing, coordination and other steps.

[0367] Exemplarily, the transceiver unit 910 is configured to receive first information from a first network device.

[0368] Optionally, the communication device 900 may include a processing unit 920, which is used to execute the content of the communication device 900 involving processing, coordination and other steps.

[0369] Exemplarily, the transceiver unit 910 is configured to send first configuration information, etc. to the first network device.

[0370] Optionally, the communication device 900 may include a processing unit 920, which is used to execute the content of the communication device 900 involving processing, coordination and other steps.

[0371] The above contents are merely exemplary descriptions, and the communication device 900 is responsible for executing the relevant methods or steps in the above method embodiments.

[0372] Optionally, the communication device 900 includes a storage unit 930, which is used to store programs or codes for executing the aforementioned methods. In other words, the storage unit 930 can be used to store instructions and / or data, and the processing unit 920 can read the instructions and / or data in the storage unit 930 to enable the communication device 900 to implement the aforementioned method embodiments. For example, the communication device 900 can be used to implement the solutions shown in Figures 3 to 7.

[0373] Exemplarily, the processing unit 920 can be used to receive first configuration information from a second network device, the first configuration information being used to configure a second functional unit associated with a first wireless bearer, the first network device and the second network device providing services for a terminal device; and to send first information to the terminal device, the first information including the first configuration information and first indication information, the first information being used to indicate the addition of the second network device, the first indication information being used to indicate the association of the first wireless bearer with the first functional unit, wherein the first functional unit is used to process data corresponding to the first network device, and the second functional unit is used to process data corresponding to the second network device.

[0374] Exemplarily, the processing unit 920 can be used to receive first information from a first network device, the first information including first configuration information and first indication information, the first configuration information being used to configure the second functional unit associated with the first wireless bearer, the first information being used to indicate the addition of the second network device, and the first indication information being used to indicate the first wireless bearer being associated with the first functional unit, wherein the first functional unit is used to process data corresponding to the first network device, the second functional unit is used to process data corresponding to the second network device, and the first network device and the second network device provide services for the terminal device; and for establishing the second functional unit and adding the second network device based on the first information.

[0375] Exemplarily, the processing unit 920 can be used to send first configuration information to the first network device, where the first configuration information is used to configure a second functional unit associated with the first radio bearer for the terminal device, and the second functional unit is used to process data corresponding to the second network device; and to send second indication information to the first network device, where the second indication information is used to indicate that the first radio bearer is associated with the first functional unit, and the first functional unit is used to process data corresponding to the first network device, and the first network device and the second network device provide services for the terminal device.

[0376] For other implementations, please refer to the detailed description of the embodiments shown in Figures 3 to 7 above, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been detailed in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0377] The device embodiments shown in Figures 8 and 9 are used to implement the contents described in Figures 3 to 7. The specific execution steps and methods of the devices shown in Figures 8 and 9 can refer to the contents described in the above method embodiments.

[0378] The present application also provides a communication device, including a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call and execute the instructions stored in the memory, so that the communication device executes the methods in the above embodiments.

[0379] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above embodiments.

[0380] The present application also provides another chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to perform the methods described in each of the above embodiments. Optionally, the chip also includes a memory configured to store computer programs or code.

[0381] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions related to the communication device in any of the above embodiments.

[0382] In another embodiment of the present application, a computer program product including a computer program or instructions is provided. When the computer program product is run on a computer, the method of the aforementioned embodiment is implemented.

[0383] The present application also provides a computer program. When the computer program is executed in a computer, the methods of the aforementioned embodiments are implemented.

[0384] In another embodiment of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When the computer program is executed by a computer, the methods of the aforementioned embodiments are implemented.

[0385] The present application also provides a communication system, including a first network device, a second network device, and a terminal device, wherein the first network device, the second network device, and the terminal device are respectively configured to execute the steps and functions related to the first network device, the second network device, and the terminal device in the embodiments of the present application.

[0386] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0387] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0388] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0389] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0390] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0392] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method is applied to a first network device, and the method includes: receiving first configuration information from a second network device, where the first configuration information is used to configure a second functional unit associated with a first radio bearer, the first network device and the second network device providing services for a terminal device; Send first information to the terminal device, the first information including the first configuration information and first indication information, the first information is used to indicate the addition of the second network device, the first indication information is used to indicate that the first wireless bearer is also associated with a first functional unit, wherein the first functional unit is used by the terminal device to process data corresponding to the first network device, and the second functional unit is used by the terminal device to process data corresponding to the second network device.

2. The method according to claim 1, characterized in that The method further comprises: receiving second information, where the second information is used to indicate that the terminal device has successfully added the second network device; Stop sending data of the first radio bearer to the terminal device.

3. The method according to claim 1 or 2, characterized in that The method further comprises: Sending third information to the terminal device, where the third information is used to instruct the terminal device to release the first functional unit.

4. The method according to claim 3, characterized in that The method further comprises: Receive fourth information, wherein the fourth information is used to indicate that the session modification of the protocol data unit is completed, the terminal device has submitted all data of the first functional unit, or the terminal device requests to release at least one of the first functional units.

5. The method according to claim 4, characterized in that The sending the third information to the terminal device includes: In response to the fourth information, the third information is sent to the terminal device.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Fifth information is sent to the second network device, where the fifth information is used to instruct the second network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

7. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Second indication information is received from the second network device, where the second indication information is used to instruct the first network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

8. The method according to any one of claims 1 to 7, characterized in that The first information further includes third indication information, where the third indication information is used to indicate that the first configuration information is pre-configuration information.

9. The method according to claim 8, characterized in that The first configuration information corresponds to information of the second network device, wherein the method further includes: Send seventh information to the terminal device, where the seventh information is used to activate the configuration of the first configuration information, and the seventh information includes information of the second network device.

10. The method according to claim 9, characterized in that The method further comprises: Send fourth indication information to the second network device, where the fourth indication information is used to instruct the terminal device to add the second network device according to the first configuration information.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Send eighth information to the core network network element, where the eighth information is used to instruct activation of a pre-configured tunnel corresponding to the second network device, where the pre-configured tunnel corresponding to the second network device is associated with data of the first radio bearer.

12. The method according to any one of claims 1 to 11, characterized in that The first configuration information includes the first indication information.

13. A communication method, characterized in that: The method is applied to a terminal device, and the method includes: receiving first information from a first network device, the first information including first configuration information and first indication information, the first configuration information being used to configure a second functional unit associated with the first radio bearer, the first indication information being used to indicate that the first radio bearer is also associated with the first functional unit, and the first information being used to indicate adding a second network device, wherein the first functional unit is used to process data corresponding to the first network device, the second functional unit is used to process data corresponding to the second network device, and the first network device and the second network device provide services for the terminal device; According to the first information, the second functional unit is established and the second network device is added.

14. The method according to claim 13, characterized in that The method further comprises: receiving third information from the first network device, where the third information is used to instruct the terminal device to release the first functional unit; The first functional unit is released according to the third information.

15. The method according to claim 14, characterized in that The method further comprises: Sending fourth information to the first network device, where the fourth information is used to indicate that the terminal device has submitted all data of the first functional unit, or that the terminal device requests to release at least one item of the first functional unit.

16. The method according to any one of claims 13 to 15, characterized in that The method further comprises: Based on the first information, a second bearer and a third bearer are established, wherein the second functional unit is used to process data corresponding to the second bearer and the third bearer, the first functional unit is used to process data corresponding to the first bearer, the first bearer and the second bearer correspond to the first network device, and the third bearer corresponds to the second network device.

17. The method according to any one of claims 13 to 16, characterized in that The first information further includes third indication information, where the third indication information is used to indicate that the first configuration information is pre-configuration information, and the first indication information is carried in the first configuration information.

18. The method according to claim 17, characterized in that The first configuration information corresponds to information of the second network device; The method further comprises: receiving seventh information from the first network device, the seventh information including information of the second network device; The step of establishing the second functional unit according to the first information includes: According to the seventh information and the first configuration information, the second functional unit is established and the second network device is added.

19. A communication method, characterized in that: The method is applied to a second network device, and the method includes: Sending first configuration information to the first network device, where the first configuration information is used to configure a second functional unit associated with the first radio bearer for the terminal device, where the second functional unit is used by the terminal device to process data corresponding to the second network device; Send second indication information to the first network device, where the second indication information is used to indicate that the first wireless bearer is also associated with a first functional unit, and the first functional unit is used by the terminal device to process data corresponding to the first network device, and the first network device and the second network device provide services for the terminal device.

20. The method according to claim 19, characterized in that The method further comprises: Send second information to the first network device, where the second information is used to indicate that the terminal device has successfully added the second network device.

21. The method according to claim 19 or 20, characterized in that The method further comprises: Fifth information is received from the first network device, where the fifth information is used to instruct the second network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

22. The method according to claim 19 or 20, characterized in that The method further comprises: Second indication information is sent to the first network device, where the second indication information is used to instruct the first network device to configure the first radio bearer to associate the first functional unit with the second functional unit.

23. The method according to any one of claims 19 to 22, characterized in that The method further comprises: Receive fourth indication information from the first network device, where the fourth indication information is used to instruct the terminal device to add the second network device according to the first configuration information.

24. A communication device, characterized in that: The method comprises a processing circuit and an input / output interface, wherein the input / output interface is used to input and / or output signals, and the processing circuit is used to execute the method according to any one of claims 1 to 12, or the processing circuit is used to execute the method according to any one of claims 13 to 18, or the processing circuit is used to execute the method according to any one of claims 19 to 23.

25. A communication device, characterized in that: include: A processor and a memory, wherein the memory stores a computer program or instructions, and the processor is used to, by executing the computer program or the instructions, cause the communication device to perform the method of any one of claims 1 to 12, or cause the communication device to perform the method of any one of claims 13 to 18, or cause the communication device to perform the method of any one of claims 19 to 23.

26. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instructions, which, when executed on a computer, causes the method according to any one of claims 1 to 12 to be executed, or causes the method according to any one of claims 13 to 18 to be executed, or causes the method according to any one of claims 19 to 23 to be executed.

27. A computer program product, characterized in that The method comprises a computer program code, which, when executed, implements the method according to any one of claims 1 to 12, or implements the method according to any one of claims 13 to 18, or implements the method according to any one of claims 19 to 23.

28. A communication system, characterized in that: The method comprises a first network device, a terminal device and a second network device, wherein the first network device is used to execute the method according to any one of claims 1 to 12, the terminal device is used to execute the method according to any one of claims 13 to 18, and the second network device is used to execute the method according to any one of claims 19 to 23.

29. A chip, characterized in that: include: A processor, wherein the processor is configured to cause the chip to perform the method of any one of claims 1 to 12, or cause the chip to perform the method of any one of claims 13 to 18, or cause the chip to perform the method of any one of claims 19 to 23 by executing a computer program or instruction.

Images