Communication method, device and system

Abstract

The invention provides a communication method, device and system, and belongs to the technical field of communication. The method comprises: a first network device sending first information to the terminal device, the first information comprising first configuration information and first indication information, the first information being used for indicating to add a second network device, the first indication information being used for indicating that a first radio bearer is also associated with a first functional unit, the first function unit is used for processing data corresponding to the first network device, and the second function unit is used for processing data corresponding to the second network device. In the auxiliary station adding process of the terminal equipment, the original function unit can be kept not released, and a new function unit can be configured. Both the original function unit and the new function unit can perform data transmission, so that the data transmission of the radio bearer is maintained, and the rate reduction in the process of reestablishing the protocol entity by the terminal equipment is avoided.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and more particularly, to a communication method, apparatus, and system. Background Art

[0002] The network side can configure a secondary station addition for a terminal device, thereby enabling dual connection between the terminal device and the network side. The master station and the secondary station provide services for the terminal device. During the process of adding a secondary station to the terminal device, protocol entities corresponding to some radio bearers may be reconfigured from the master station to the secondary station. The terminal device needs to reconstruct these protocol entities and change the underlying transmission resources, resulting in a decrease in the data transmission rate of these radio bearers.

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

[0004] This application provides a communication method, apparatus, and system, which can avoid the rate drop during the process of reconstructing protocol entities in the terminal device.

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

[0006] 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, and the first network device and the second network device provide services for the terminal device; sending first information to the terminal device, where the first information includes the first configuration information and a first indication information, and the first information is used to indicate the addition of the second network device, and the first indication information is used to indicate that the first radio 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 second functional unit is used to process data corresponding to the second network device.

[0007] Through the above embodiments, during the process of adding a secondary station to the terminal device, the original functional unit can be kept without being released, 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 reconstructing protocol entities in the terminal device, and improving the user experience.

[0008] In some implementation manners, 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; stopping sending data of the first radio bearer to the terminal device.

[0009] Through the above embodiments, when the first network device confirms that the terminal device adds the second network device, it may stop sending the data of the first radio bearer to the terminal device. Since the terminal device successfully adds the second network device, the second network device may perform downlink transmission of the first radio bearer. The above embodiments enable the terminal device to maintain downlink transmission during the process of reconstructing the protocol entity, thereby avoiding a rate drop.

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

[0011] Through the above embodiments, the first network device may deliver the data of the first radio bearer to the second network device, enabling the second network device to perform uplink and downlink data transmission, thereby enhancing the continuity of data transmission.

[0012] 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.

[0013] In some implementations, the method further includes: receiving fourth information, where the fourth information is used to indicate at least one of the completion of the session modification of the protocol data unit, the terminal device has delivered all the data of the first functional unit, or the terminal device requests to release the first functional unit.

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

[0015] 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 and the second functional unit.

[0016] In some implementations, the method further includes: receiving sixth information from the second network device, where the sixth information is used to indicate that the second network device determines to configure the first radio bearer to associate the first functional unit and the second functional unit.

[0017] 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 and the second functional unit.

[0018] 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-configured information.

[0019] 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, 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.

[0020] In some implementations, the method further includes: sending fourth indication information to the second network device, where the fourth indication information is used to indicate that the terminal device adds the second network device according to the first configuration information.

[0021] In some implementations, the method further includes: receiving a first message from the terminal device, where 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, where the fifth indication information is used to indicate that the terminal device completes the configuration corresponding to the second network device.

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

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

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

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

[0026] In some implementations, the fifth information is used to request the second network device to pre-configure the first radio bearer associated with the first functional unit and the second functional unit.

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

[0028] In a second aspect, a communication method is provided. The method can be executed by a terminal device, or by a component (such as a processor, a chip, or a chip system, etc.) in the terminal device, or by a logic module or software that can implement all or part of the functions of the terminal device.

[0029] The method includes: receiving first information from a first network device, where the first information includes first configuration information and first indication information, the first configuration information is used to configure a second functional unit associated with the first radio bearer, the first information is used to indicate the addition of the second network device, and the first indication information is used to indicate that the first radio 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, 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; establishing the second functional unit and adding the second network device according to the first information.

[0030] 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.

[0031] In some implementations, the method further includes: receiving third information from the first network device, where the third information is used to indicate that the terminal device releases the first functional unit; releasing the first functional unit according to the third information.

[0032] 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 delivered all data of the first functional unit, or the terminal device requests to release at least one of the first functional units.

[0033] In some implementations, the method further includes: establishing a second bearer and a third bearer according to the first information, where 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.

[0034] 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.

[0035] In some implementations, the first configuration information corresponds to information of the second network device; where the method further includes: receiving seventh information from the first network device, where the seventh information includes information of the second network device; where establishing the second functional unit according to the first information includes: establishing the second functional unit and adding the second network device according to the seventh information and the first configuration information.

[0036] In a third aspect, a communication method is provided. This method can be executed by a second network device, or by components in the second network device (such as 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.

[0037] 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 radio bearer for a 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, where the second indication information is used to indicate that the first radio bearer is further 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.

[0038] In some implementation manners, 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.

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

[0040] In some implementation manners, the method further includes: receiving fifth information from the first network device, where the fifth information is used to indicate that the second network device configures the first radio bearer to be associated with the first functional unit and the second functional unit.

[0041] In some implementation manners, the method further includes: sending sixth information to the first network device, where the sixth information is used to indicate that the second network device determines to configure the first radio bearer to be associated with the first functional unit and the second functional unit.

[0042] In some implementation manners, the method further includes: sending second indication information to the first network device, where the second indication information is used to indicate that the first network device configures the first radio bearer to be associated with the first functional unit and the second functional unit.

[0043] In some implementation manners, the method further includes: receiving fourth indication information from the first network device, where the fourth indication information is used to indicate that the terminal device adds the second network device according to the first configuration information.

[0044] In some implementation manners, the method further includes: receiving fifth indication information from the first network device, where the fifth indication information is used to indicate that the terminal device completes the configuration corresponding to the second network device.

[0045] In some implementations, the fifth piece of information is used to request the second network device to pre-configure the first radio bearer associated with the first functional unit and the second functional unit.

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

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

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

[0049] In some implementations, the processor is used to communicate with other devices through the interface circuit and execute the above-mentioned 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.

[0050] In a fifth aspect, a communication device is provided. The communication device may include devices or modules for performing communication device functions, etc.

[0051] In some implementations, the communication device may include modules or units corresponding one by one to the methods / operations / steps / actions described in the first aspect and any possible implementation manner of the first aspect. The module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software.

[0052] In some implementations, the communication device may include modules or units corresponding one by one to the methods / operations / steps / actions described in the second aspect and any possible implementation manner of the second aspect. The module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software.

[0053] In some implementations, the communication device may include modules or units corresponding one by one to the methods / operations / steps / actions described in the third aspect and any possible implementation manner of the third aspect. The module or unit may be a hardware circuit, or software, or a combination of a hardware circuit and software.

[0054] 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 runs on a computer, it 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.

[0055] In a seventh aspect, a computer program product is provided, which includes a computer program or instruction. When the computer program or the instruction runs on a computer, it 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.

[0056] In an eighth aspect, a communication device is provided, including a processor configured to be connected to a memory and to call a program stored in the memory to execute any possible method of the first aspect described above, or to execute any possible method of the second aspect described above, or to execute any possible method of the third aspect described above. The memory may be located inside the communication device or outside the communication device. And the processor includes one or more.

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

[0058] In a ninth aspect, a chip is provided, including a processor configured to call a computer program or computer instruction in a memory so that the processor executes any implementation of the first aspect described above, or so that the processor executes any implementation of the second aspect described above, or so that the processor executes any implementation of the third aspect described above.

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

[0060] In a 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 configured to execute the first aspect and any possible implementation of the first aspect, the terminal device is configured to execute the second aspect and any possible implementation of the second aspect, and the second network device is configured to execute the third aspect and any possible implementation of the third aspect.

[0061] For the description of the beneficial effects of any aspect from the second aspect to the tenth aspect, reference may be made to the description of the beneficial effects of the first aspect. Brief Description of the Drawings

[0062] Figure 1 FIG. is a schematic diagram of a possible architecture of a communication system applicable to the embodiments of the present application.

[0063] Figure 2 FIGS. are schematic diagrams of some possible architectures of a communication system applicable to the embodiments of the present application.

[0064] Figure 3 FIG. is a schematic flowchart of a secondary station addition method.

[0065] Figure 4 FIG. is a schematic flowchart of a communication method provided by the embodiments of the present application.

[0066] Figure 5 FIG. is a schematic diagram of a protocol stack configuration provided by the embodiments of the present application.

[0067] Figure 6 FIG. is a schematic flowchart of another communication method provided by the embodiments of the present application.

[0068] Figure 7 FIG. is a schematic flowchart of yet another communication method provided by the embodiments of the present application.

[0069] Figure 8 FIG. is a schematic block diagram of a communication device according to the embodiments of the present application.

[0070] Figure 9 FIG. is a schematic block diagram of another communication device according to the embodiments of the present application. Detailed Description of the Embodiments

[0071] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0072] The present application will present various aspects, embodiments or features around a system 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 the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. In addition, combinations of these solutions may also be used.

[0073] In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or more advantageous than other embodiments or design solutions. Rather, the use of the word "exemplary" is intended to present concepts in a specific manner.

[0074] The business scenarios described in the embodiments of this application are for more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As can be known to those of ordinary skill in the art, with the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0075] The references to "one embodiment" or "some embodiments" etc. described in this specification mean that specific features, structures, or characteristics described in connection with that embodiment are included in one or more embodiments of this application. Thus, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "comprising", "including", "having" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in another way.

[0076] The technical solutions of the embodiments of this 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) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Fifth Generation (5 thgeneration, 5G) mobile communication system or new radio (NR) system, narrow band 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 future sixth generation (6 th generation, 6G) mobile communication system, etc.

[0077] It should be noted that, in the embodiments of the present application, the term "communication" can also be described as "data transmission", "signal transmission", "information transmission" or "transmission", etc. In the embodiments of the present application, transmission can include sending or receiving. Exemplarily, the transmission can be an uplink transmission, for example, the terminal device can send a signal to the network device; the transmission can also be a downlink transmission, for example, the network device can send a signal to the terminal device.

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

[0079] The network device 121 (or network device 122) can be any device with wireless transceiver capabilities. For example, it can be a base station used to connect the terminal device 130 to a radio access network (RAN). A base station is sometimes also referred to as an access network device or an access network node. It can be understood that in systems using different radio access technologies, the names of the devices with base station functions may vary. For ease of description, in the embodiments of this application, the devices that provide wireless communication access functions for terminal devices are collectively referred to as base stations. In the embodiments of this 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 can include evolved node B (eNB or eNodeB) in LTE, next generation-evolved node B (ng-eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved node B (or home node B, HNB), base band unit (BBU), access points in a wireless fidelity (WIFI) system, wireless relay nodes, wireless backhaul nodes, transmission points (TP) or transmission reception points (TRP), etc. It can also include next generation node basestation (gNB), NR gNB or transmission point (TRP or TP) in a 5G system, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, network nodes that make up a gNB or a transmission point, such as a base band unit (BBU) or a distributed unit (DU). It can also include network devices, servers, wearable devices, or in-vehicle devices in a future 6G network.

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

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

[0082] In the embodiments of the present application, the device for implementing the functions of the network device 121 (or network device 122) may be the network device 121 (or network device 122), or may be a device capable of supporting the network device 121 (or network device 122) to implement such functions, such as a chip system. This device may be installed in the network device 121 (or network device 122). The chip system may be composed of chips or may include chips and other discrete devices.

[0083] 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; it may also be deployed on water (such as a ship, etc.); it may also be deployed in the air (such as a drone, an airplane, a balloon, a satellite, etc.). The terminal device 130 may also be referred to as a user equipment (UE), a mobile terminal (MT), an access terminal, a terminal, a subscriber unit, a user station, a mobile station, a mobile station (MS), a remote station, a remote terminal, a mobile device, a user terminal, a wireless network device, a user agent, or a user device. In the embodiments 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 (pad), 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 devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device, a terminal device in the Internet of Things or the Internet of Vehicles, and any form of terminal, relay user equipment, or terminal in a future evolved public land mobile network (PLMN) in the future network. The terminal device 130 may 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 haptic terminal device, a vehicle-mounted terminal device, a wearable terminal device, etc., and the embodiments of the present application do not limit this.

[0084] In the embodiments of this application, the device for implementing the functions of the terminal device 130 may be the terminal device 130 or a device capable of supporting the terminal device 130 to implement such functions, such as a chip system, and this device may be installed in the terminal device 130. The chip system may be composed of chips or may include chips and other discrete devices. In the technical solutions of the embodiments of this application, the device for implementing the functions of the terminal device is the terminal device, which may also be referred to as a terminal. Below, the technical solutions provided in the embodiments of this application will be described by taking the terminal device as a UE as an example.

[0085] The core network 110 may provide user connection, user management, and bearer for services. The core network 110 may serve as a bearer network and provide an interface to an external network. For example, the core network 110 may be a core network of 4G, 5G, or 6G. The core network 110 may include one or more core network elements.

[0086] It should be understood that Figure 1 only a simplified schematic diagram for easy understanding is shown, and the communication system 100 may further include other network devices or other terminal devices, Figure 1 which are not drawn in the figure.

[0087] There may be wireless communication between the network device 121 (or network device 122) and the terminal device 130. The transmission link from the network device 121 (or network device 122) to the terminal device 130 may be referred to as a downlink (DL) or a downlink channel for transmitting downlink signals. The transmission link from the terminal device 130 to the network device 121 (or network device 122) may be referred to as an uplink (UL) or an uplink channel for transmitting uplink signals. Exemplarily, the network device 121 (or network device 122) may send downlink reference signals to the terminal device 130 through the downlink channel, such as cell-specific reference signals (CRS), UE-specific reference signals, for channel state information measurement, data demodulation, beam training, time-frequency parameter tracking, etc. The terminal device 130 may send uplink reference signals, such as SRS, DMRS, to the network device 121 (or network device 122) through the uplink channel for uplink and downlink channel measurement, data demodulation, etc. There may also be downlink data transmission between the network device 121 (or network device 122) and the terminal device 130 through the downlink channel and uplink data transmission through the uplink channel.

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

[0089] Figure 1 The scenario shown can also be referred to as dual connectivity (DC). DC is an operation mode of terminal device 130 in the radio resource control (RRC) connected state. In the scenario where the network side (including network device 121 and network device 122) configures a master cell group (MCG) and a secondary cell group (SCG) for the connected terminal device 130, it can be called DC.

[0090] Figure 2 are some possible schematic diagrams of the communication system applicable to the embodiments of this application. There are multiple scenarios for DC. The following briefly introduces four scenarios in combination with Figure 2 But this application is not limited to Figure 2 the scenario shown, and can also be applicable to other dual connectivity scenarios.

[0091] Refer to Figure 2 in (1). The core network 110 can be an evolved packet core (EPC), that is, the core network of 4G. Network device 121 can be a long term evolution (LTE) base station, such as an eNB; network device 122 can be a new radio (NR) base station, such as a gNB. LTE can be used as the master node (MN), and the NR base station can be used as the secondary node (SN). The above scenario can also be called the dual connectivity of 4G radio access network and 5G NR (E-UTRA-NR dual connectivity, EN-DC). Among them, there can be an X2 interface 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 can also be a user plane connection. There can be an S1 interface 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 can also be a user plane connection. There can be an S1-U interface between the NR base station and the EPC, that is, there can be a user plane connection. The LTE base station can provide radio interface resources for terminal device 130 through at least one LTE cell. At this time, the at least one LTE cell is called MCG. Correspondingly, the NR base station can also provide radio interface resources for terminal device 130 through at least one NR cell. At this time, the at least one NR cell is called SCG.

[0092] Refer to Figure 2 In (2) thereof, the core network 110 may be a 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. Among them, there may be an Xn interface 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. There may be an NG interface 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. There may be an NG-U interface between the LTE base station and the 5GC, that is, there may be a user plane connection. The NR base station may provide radio access resources for the terminal device 130 through at least one NR cell, and at this time, the at least one NR cell is called a MCG. Correspondingly, the LTE base station may also provide radio access resources for the terminal device 130 through at least one LTE cell, and at this time, the at least one LTE cell is called a SCG.

[0093] Refer to Figure 2 In (3) thereof, the core network 110 may be a 5GC. The network device 121 may be an LTE base station, such as an eNB; the network device 122 may be an NR base station, such as a gNB. The LTE base station may serve as an MN, and the NR base station may serve as an SN. Among them, there may be an Xn interface 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 may also be a user plane connection. There may be an NG interface 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 may also be a user plane connection. There may be an NG-U interface between the NR base station and the 5GC, that is, there may be a user plane connection. The LTE base station may provide radio access resources for the terminal device 130 through at least one LTE cell, and at this time, the at least one LTE cell is called a MCG. Correspondingly, the NR base station may also provide radio access resources for the terminal device 130 through at least one NR cell, and at this time, the at least one NR cell is called a SCG.

[0094] Refer to Figure 2In (4) thereof, the core network 110 may be a 5GC. Both the network device 121 and the network device 122 may be NR base stations, such as gNBs. Among them, one NR base station serves as the MN, and the other NR base station serves as the SN. There may be an Xn interface 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 may also be a user plane connection. There may 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 may also be a user plane connection. There may be an NG-U interface between the SN and the 5GC, that is, there may be a user plane connection. The MN may provide radio air interface resources for the terminal device 130 through at least one NR cell, and at this time, at least one NR cell is called the MCG. Correspondingly, the SN may also provide radio air interface resources for the terminal device 130 through at least one NR cell, and at this time, at least one NR cell is called the SCG.

[0095] Figure 1 or Figure 2 The communication system shown may also be referred to as an architecture of multi-radio access technology dual connectivity (MR-DC). The MR-DC architecture may support various types of radio bearers (RB). It should be noted that Figure 1 and Figure 2 are merely exemplary, and the application scenarios of the present application are not limited to the dual connectivity scenario and may also be applied to other scenarios.

[0096] A radio bearer can be the general term for a series of protocol entities and configurations allocated by a network device for a terminal device, and can be a service provided by layer 2 for transmitting user data between the terminal device and the 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). Among them, the DRB can be used to carry data, and the SRB can be used to carry signaling messages. As an example, a radio bearer configuration generally includes the configurations of the PDCP layer and the SDAP layer. The protocol entities below the RLC layer are called RLC bearers, and the corresponding configurations are given in the RLC bearer configuration. In other words, the configuration of a radio bearer can include the configurations of the PDCP layer and the SDAP layer, but does not include the configuration of the RLC bearer. In some other alternative ways, the configuration of a radio bearer can include the configurations of the PDCP layer, the SDAP layer, and the RLC layer.

[0097] Exemplarily, the types of radio bearers supported by the MR-DC architecture can 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).

[0098] Among them, the MCG bearer may refer to a bearer that only involves MCG radio access network (RAN) resources. The SCG bearer may refer to a bearer that only involves SCG RAN resources. The split bearer may refer to a bearer that involves both MCG RAN resources and SCG RAN resources, and the split bearer can be split at the PDCP entity. The MN or SN termination may refer to the PDCP entity at the MN or SN. For example, the PDCP of the SCG bearer terminated at the MN is at the MN, but the corresponding underlying RAN resources are at the SCG. The RAN resources may also be referred to as radio resources, radio RAN resources, or have other names.

[0099] Figure 3 It is a schematic flowchart of an auxiliary station addition method 300. The method 300 is only an example and does not limit the present application. The following describes the method 300 in conjunction with Figure 3 introduce the method 300.

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

[0101] The SN addition request message can be used to request the target SN to allocate resources for one or more protocol data unit (PDU) sessions or quality of service (QoS) flows.

[0102] Optionally, the SN addition request message can 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, etc. Optionally, in the SN addition request message, the MN also provides the UE's measurement results for the SN to select and configure the SCG cell. Optionally, for radio bearers that require SCG RAN resources, the MN also indicates the information required by the SCG, such as UE capabilities, etc.

[0103] S320, the SN sends an addition request acknowledgement message to the MN.

[0104] Optionally, before S320, the method 300 further includes: the SN permits the MN's request; the SN allocates corresponding RAN resources; the SN determines the radio bearer configuration according to the bearer type in the SN addition request message.

[0105] Optionally, the addition request acknowledgement message may include the above radio bearer configuration. The above radio bearer configuration can be sent to the UE by the MN.

[0106] S330, the MN sends an RRC reconfiguration message to the UE.

[0107] Among them, the RRC reconfiguration message may include the RRC configuration of the SN. The RRC configuration can be used for the UE to access the SN and obtain the radio interface resources of the SN.

[0108] S340, the UE sends an RRC reconfiguration complete message to the MN.

[0109] Among them, the RRC reconfiguration complete message can be used to indicate the completion of the configuration, and the RRC reconfiguration complete message may include the RRC reconfiguration complete message for the SN.

[0110] Optionally, before S340, method 300 further includes: the UE configures according to the RRC reconfiguration message.

[0111] S350, the MN sends an RRC reconfiguration complete message for the SN to the SN.

[0112] The RRC reconfiguration complete message for the SN can indicate to the SN that the UE has completed the dual-connection configuration.

[0113] S360, the UE performs random access based on the RRC configuration of the SN and establishes a radio interface connection with the SN.

[0114] It should be noted that for the radio bearer terminated at the SN, the PDCP entity needs to be switched from the MN to the SN. Since the key corresponding to the PDCP entity changes, the PDCP entity needs to be re-established to avoid key confusion. For the MCG bearer or split bearer terminated at the SN, the RLC bearer originally established on the MCG also needs to be re-established or the logical channel needs to be changed to avoid the incorrect transmission of data encrypted with the old key.

[0115] In the related technical solution, after the UE receives the RRC reconfiguration message, the uplink data transmission with the MN is stopped, and the PDCP entity corresponding to the radio bearer is re-established, including: clearing all buffered data, initializing the processing parameters related to the PDCP entity, and applying the new parameters for encryption and integrity protection processing. After the UE accesses the SN (i.e., S360), the uplink or downlink data transmission with the SN is performed. Between the UE receiving the RRC reconfiguration message and accessing the SN, the UE cannot transmit the data of this radio bearer, resulting in a drop in the transmission rate, that is, the transmission rate suddenly decreases, thus reducing the user experience.

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

[0117] Figure 4It is a schematic flowchart of a communication method 400 provided by an embodiment of the present application. The method 400 can avoid the rate drop during the process of the terminal device reconstructing the protocol entity. The following will introduce the method 400 in combination with Figure 4 to introduce the method 400.

[0118] S410, the first network device receives first configuration information from the second network device. Correspondingly, the second network device sends the first configuration information to the first network device.

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

[0120] Among them, the functional unit can include the functions of the PDCP entity. In some alternative embodiments, the functional unit can be replaced by PDCP, PDCP entity, or PDCP protocol stack. The functional unit can have other names, such as function, etc.

[0121] The first functional unit can be the original (or already configured) functional unit of the first radio bearer. In some alternative embodiments, the first functional unit can be replaced by the first PDCP, first PDCP function, first PDCP entity, or first PDCP protocol stack. The first functional unit can have other names, such as the first function, etc.

[0122] The second functional unit can be a functional unit that needs to be newly configured for the first radio bearer. In some alternative embodiments, the second functional unit can be replaced by the second PDCP, second PDCP function, second PDCP entity, or second PDCP protocol stack. The second functional unit can have other names, such as the second function, etc.

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

[0124] Exemplarily, taking the first network device as the MN and the second network device as the SN as an example, the first configuration information can be carried in the SN addition request confirmation message. However, the present application is not limited thereto, and the first configuration information can also be carried in other messages.

[0125] Optionally, before S410, method 400 further includes: a first network device sending a message for requesting to add a second network device to the second network device. For example, an SN addition request message. For the specific content of the SN addition request message, reference may be made to the description related to S310, which will not be elaborated here. Optionally, the second network device determines first configuration information according to the SN addition request message.

[0126] In some alternative embodiments, the SN addition 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 according to the type of radio bearer.

[0127] In some alternative embodiments, the first configuration information may be used to trigger the access (or addition) of a terminal device to the second network device, so that the terminal device can communicate with the second network device. In some alternative embodiments, the first configuration information may be used to configure the RLC bearer associated with the second functional unit. Wherein, the RLC bearer may be the RLC bearer corresponding to the second network device. For example, the first configuration information may be used to instruct the terminal device to configure the RLC bearer of the second network device associated with the second functional unit.

[0128] In some alternative embodiments, the first configuration information may include at least one of the configuration information of the first radio bearer, the configuration information of 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, and the group of cells includes one or more cells. Wherein, the configuration information of PDCP 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 encryption parameters, integrity protection parameters, or robust header compression (RHCO) parameters.

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

[0130] It should be noted that this application does not limit the name of the functional unit. The functional unit may be called PDCP, protocol stack, PDCP protocol stack, PDCP entity, function, PDCP function or have other names. This application does not limit the name of the RLC bearer. The RLC bearer may be called RLC, RLC entity, RLC function, bearer, logical channel or have other names.

[0131] In S420, the first network device sends first information to the terminal device.

[0132] Among them, 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.

[0133] The first indication information may be used to indicate that the first radio bearer is associated with the first functional unit; in other words, the first indication information may be used to indicate configuring a dual active protocol stack (DAPS) for the first radio bearer, or to indicate the function of configuring two sets of protocol stacks for the first radio bearer; in other words, the first indication information may be used to indicate that the terminal device maintains the first functional unit and establishes the second functional unit; in other words, the first indication information may be used to indicate that the terminal device waits for the release indication of the first functional unit and establishes the second functional unit; in other words, the first indication information may be used to indicate that the terminal device does not release the first functional unit and establishes the second functional unit.

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

[0135] The first functional unit may be a pre-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 the first bearer (or referred to as the first RLC bearer). The first bearer may be associated with the radio interface resources of one or more cells of the first network device. The radio interface resources of the one or more cells of the first network device mentioned above may be referred to as the radio interface resources corresponding to the first bearer, or the radio interface resources associated with the first functional unit, or have other names.

[0136] 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.

[0137] The first indication information may be referred to as a dual active protocol stack indication, a dual active indication, or have other names, and this application does not limit this.

[0138] Among them, the first piece of information can be used to indicate adding a second network device. The first piece of information can be used to indicate that the terminal device adds a second network device. For example, the first piece of information can be used to indicate that the terminal device adds a second network device as an SN. Optionally, the first piece of information can use a display indication message to indicate that the terminal device adds a second network device. Optionally, the first configuration information can indicate that the terminal device adds a second network device. Optionally, the first indication message can be used to indicate that the terminal device adds a second network device.

[0139] Optionally, the first piece of information can be used to indicate that the terminal device adds one or more cells of the second network device; in other words, the first piece of information can be used to indicate that the terminal device adds a group of cells of the second network device, and the 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 indicate that the terminal device adds one or more cells of the second network device. The third configuration information can be referred to as SCG configuration or have other names. Optionally, the first configuration information includes the third configuration information. In addition, one or more cells of the second network device indicated above are associated with a 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 second network device.

[0140] Optionally, the first piece of information can be used to indicate that the terminal device adds one or more cells of the first network device.

[0141] Optionally, the first piece of information can indicate that one or more cells of the first network device are associated with a 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 piece of information is used to indicate the configuration of a second bearer, and the second bearer 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 radio interface resources of one or more cells of the first network device. Among them, the radio interface resources of one or more cells of the first network device above can be referred to as the radio interface resources corresponding to the second bearer. The radio interface resources corresponding to the second bearer can be used as the radio interface resources associated with the second functional unit.

[0142] The second bearer can also be referred to as a second RLC bearer or have other names. Optionally, the first network device can send the configuration of the second bearer to the terminal device. The configuration of the second bearer can be in the first piece of information or can be sent independently of the first piece of information, and this application does not limit this.

[0143] Optionally, the first information may indicate the configuration of a third bearer, which 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 the radio access network resources of one or more cells of the second network device. Among them, the radio access network resources of one or more cells of the second network device mentioned above may be referred to as the radio access network resources corresponding to the third bearer. The radio access network resources corresponding to the third bearer may be used as the radio access network resources associated with the second functional unit.

[0144] It can be understood that the radio access network resources associated with the second functional unit may include the radio access network resources corresponding to the second bearer and the radio access network resources corresponding to the third bearer.

[0145] The third bearer may also be referred to as the 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 may be sent independently of the first information, and this application does not limit this.

[0146] In the case where 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.

[0147] The first information may be referred to as RRC reconfiguration information or have other names, and this application does not limit this.

[0148] In some alternative embodiments, the first information may be carried in an RRC reconfiguration message, but this application does not limit this, and the first information may be carried in other messages. In some alternative 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. That is to say, the first configuration information and the first indication information may be carried in different messages, or in other words, the first configuration information and the first indication information may be sent separately.

[0149] Among them, the first functional unit may be used to process the data corresponding to the first network device, and the second functional unit may be used to process the data corresponding to the second network device.

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

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

[0152] In a possible manner, the above-mentioned third entity and 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 it is determined by the first network device or the second network device that a split bearer is configured for the first radio bearer, the first network device configures an RLC bearer on the side of the first network device for the first radio bearer and associates it with the second functional unit, and the second network device configures an RLC bearer on the side of the second network device 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 radio resources of the first network device and the second network device and deliver it to the second functional unit for processing.

[0153] 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 either 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 both data corresponding to the first network device and data corresponding to the second network device. For example, the terminal device can process PDCP data from the first network device or PDCP data from the second network device. Another example is that the first functional unit can process PDCP data from the first network device and the second functional unit can process PDCP data from the second network device.

[0154] In some alternative 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, integrity protected, ROHC processed, and packet headers are added using the configuration of the first functional unit. The data processed by the second functional unit is encrypted, integrity protected, ROHC processed, and packet headers are added using the configuration of the second functional unit. The data processed by the first functional unit is sent through the radio access network resources associated with the first functional unit, and the data processed by the second functional unit is sent through the radio access network resources associated with the second functional unit. Herein, the radio access network resources associated with the first functional unit. It should be noted that the radio access network resources associated with the second functional unit may be the radio access network resources of the first network device or the radio access network resources of the second network device.

[0155] In some alternative embodiments, the terminal device may receive data from the first network device and the second network device respectively. The received data includes the data handed over by the PDCP of the first network device and the data handed over by the PDCP of the second network device. The terminal device may receive data through the radio access network 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 may distinguish the data from the first network device and the second network device through the RLC bearer identifier or the logical channel identifier, and hand over the PDCP data from the first network device to the first functional unit for processing, and hand over the PDCP data from the second network device to the second functional unit for processing.

[0156] The first functional unit and the second functional unit may correspond to the same PDCP entity, but the present application is not limited thereto. 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 can be understood 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 manner, the first functional unit corresponds to the PDCP function. Optionally, the terminal device has only one PDCP entity, and this PDCP entity corresponds to two functions, namely the first functional unit and the second functional unit. In another possible implementation manner, the first functional unit corresponds to a 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.

[0157] 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 configuration information of a first radio bearer, configuration information of PDCP, or configuration information of radio access network resources associated with the first radio bearer. Optionally, the configuration information of PDCP may include at least one of encryption parameters, integrity protection parameters, or RHCO parameters. Among them, the configuration information of 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 radio access network resources associated with the first radio bearer may include at least one of MCG configuration or SCG configuration. For example, for a split bearer, the configuration information of radio access network resources associated with the first radio bearer may include MCG configuration and 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 set of cells of the second network device, and the set of cells includes one or more cells. For another example, for an MCG bearer, the configuration information of radio access network resources associated with the first radio bearer may include the RLC bearer configuration on the side of the first network device. For still another example, for an SCG bearer, the configuration information of radio access network resources associated with the first radio bearer may include the RLC bearer configuration on the side of the second network device.

[0158] S430, the terminal device establishes a second functional unit according to the first information.

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

[0160] Among them, 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 according to the first indication information. Optionally, the terminal device waits for a release indication of the first functional unit according to the first indication information. Optionally, the terminal device does not release the first functional unit according to the first indication information. Optionally, the terminal device establishes the second functional unit before releasing the first functional unit according to the first indication information.

[0161] Optionally, the first indication information may be carried in the first configuration information. Optionally, the terminal device maintains the first functional unit and establishes the second functional unit according to the first configuration information. Optionally, the terminal device waits for the release indication of the first functional unit according to the first configuration information. Optionally, the terminal device does not release the first functional unit according to the first configuration information. Optionally, the terminal device establishes the second functional unit before releasing the first functional unit according to the first configuration information.

[0162] Optionally, the terminal device adds a second network device according to the first information. For example, the terminal device adds a second network device according to the first information to provide communication services for the terminal device. Optionally, the first configuration information indicates adding a second network device; the terminal device adds a second network device according to the first configuration information. For example, the terminal device adds a second network device as an SN (or to provide communication services for the terminal device) according to the first configuration information.

[0163] Optionally, the first information is used to indicate one or more cells of the second network device to be added by the terminal 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, where the group of cells includes one or more cells.

[0164] Optionally, the first information includes third configuration information, and the third configuration information is used to indicate one or more cells of the second network device to be added by the terminal device. The third configuration information may be referred to as 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. It can be understood that the second functional unit is used to process data associated with one or more cells of the second network device.

[0165] Optionally, the first information may be used to indicate one or more cells of the first network device to be added by the terminal device. Optionally, the terminal device adds one or more cells of the first network device according to the first information.

[0166] Optionally, the first information is used to indicate the configuration of the second bearer. Optionally, the terminal device configures the second bearer according to the configuration of the second bearer, where the second bearer is a bearer of the first network device and is associated with the second functional unit. Optionally, the terminal device configures the radio interface resources of one or more cells of the first network device according to the configuration of the second bearer. Among them, the radio interface resources of one or more cells of the first network device described above can be referred to as the radio interface resources corresponding to the second bearer. The radio interface resources corresponding to the second bearer can be used as the radio interface resources associated with the second functional unit.

[0167] The second bearer can also be referred to as the second RLC bearer or have other names. Optionally, the terminal device receives the configuration of the second bearer. The configuration of the second bearer can be in the first information or can be sent independently of the first information, and this application does not limit this.

[0168] Optionally, the first information can indicate the configuration of the third bearer. Optionally, the terminal device configures the third bearer according to the configuration of the third bearer, where the third bearer is a bearer of the second network device and is associated with the second functional unit. Optionally, the terminal device configures the radio interface resources of one or more cells of the second network device according to the configuration of the third bearer. Among them, the radio interface resources of one or more cells of the second network device described above can be referred to as the radio interface resources corresponding to the third bearer. The radio interface resources corresponding to the third bearer can be used as the radio interface resources associated with the second functional unit.

[0169] The third bearer can also be referred to as the third RLC bearer or have other names. Optionally, the terminal device receives the configuration of the third bearer. The configuration of the third bearer can be in the first information or can be sent independently of the first information, and this application does not limit this.

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

[0171] Optionally, the terminal device establishes an entity corresponding to the second functional unit according to the first information. For example, the terminal device can create a new PDCP entity. Optionally, the terminal device establishes a function corresponding to the second functional unit according to the first information. For example, the terminal device can reconfigure the original PDCP entity to establish the function corresponding to the second functional unit.

[0172] Through the above embodiments, during the secondary station addition process of the terminal device, the original functional units can be kept without release, and new functional units can be configured. Both the original functional units and the new functional units can perform data transmission, thereby maintaining the data transmission of the radio bearer, avoiding the rate drop during the process of the terminal device reconstructing the protocol entity, and improving the user experience.

[0173] Optionally, the data corresponding to the first bearer, the second bearer, and the third bearer is the 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.

[0174] Among them, the term "bearer" can also be referred to as an RLC bearer, a logical channel, or have other names. The following takes Figure 5 as an example to introduce the above solution.

[0175] Figure 5 is a schematic diagram of a protocol stack configuration provided by an embodiment of the present application. Figure 5 It is only an example shown for the convenience of understanding method 400 and does not constitute a limitation on the present application.

[0176] As Figure 5 shown in (a) of, before the SN addition (for example, before method 400 is executed), the UE is connected to the MN. Among them, PDCP 110 in the UE corresponds to PDCP 140 in the MN. In the uplink transmission, the UE can deliver the data processed by PDCP 110 to RLC 120 for processing and then send it to the MN. After receiving the data, the MN can process it through RLC 130 and then deliver it to PDCP 140 for processing. Exemplarily, PDCP 110 can be referred to as the first functional unit.

[0177] As Figure 5 shown in (b) of, after the SN addition (for example, after S420 is executed), the UE is connected to the MN and the SN. The UE keeps the original PDCP 110 and establishes a new PDCP 112. PDCP 112 can be used to process the data corresponding to PDCP 142. Optionally, the UE can establish RLC 122 and RLC 124 associated with PDCP 112. The MN can establish RLC 132 associated with PDCP 142 in the SN. The SN can establish PDCP 142 and establish RLC 134 associated with 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 the second functional unit. Exemplarily, PDCP 112 can be referred to as the second functional unit. Exemplarily, PDCP 112 and PDCP 114 can be referred to as the second functional unit.

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

[0179] In some alternative embodiments, the terminal device can uniformly number the data processed by PDCP 110 and PDCP 112. Optionally, the terminal device applies different configurations to perform operations such as encryption, integrity protection, ROHC, and header addition for PDCP 110 and PDCP 112. For example, the data of PDCP 110 is encrypted, integrity protected, ROHC processed, and header added using the configuration of PDCP 110 provided by the MN, and the data processed by PDCP 112 is encrypted, integrity protected, ROHC processed, and header added using the configuration of PDCP 112 provided by the SN. The data processed by PDCP 110 is sent through the radio 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 through the radio interface resources associated with PDCP 112. For example, the data processed by PDCP 112 is delivered to the RLC 122 or RLC 124 associated with PDCP 112 for processing.

[0180] In some alternative embodiments, the terminal device can receive data from a first network device and a second network device. The received data includes the data delivered by PDCP 140 of the first network device and the data delivered by PDCP 142 of the second network device. The terminal device can receive data through the radio 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, through the logical channel identifier, whether the data comes from the RLC entity (such as RLC 130) associated with PDCP 140 or the RLC entity (such as RLC 132 or RLC 134) associated with PDCP 142, and determine whether the data comes from PDCP 140 of the first network device or PDCP 142 of the second network device, and deliver the data from PDCP 140 of the first network device to PDCP 110 for processing, and deliver the data from PDCP 140 of the second network device to PDCP 112 for processing.

[0181] In some alternative 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 an inter-station interface. Optionally, the first network device may send a status report, which may be used to indicate the situation of the downlink data successfully transmitted on the side of the first network device by the terminal device; the second network device may, according to the status report, clear the downlink data successfully transmitted on the side of the first network device by the terminal device. 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.

[0182] In some alternative 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 the uplink data to the core network element. Optionally, the first network device may deliver the uplink data to the second network device through an inter-station interface. Optionally, the first network device may send a status report, which may be used to indicate the situation of the uplink data successfully transmitted on the side of the first network device by the terminal device; the second network device may, according to the status report, clear the uplink data successfully transmitted on the side of the first network device by the terminal device. 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.

[0183] In some alternative embodiments, after S420, method 400 further includes: the terminal device sends a reconfiguration complete message to the first network device. Among them, the reconfiguration complete message may be used to indicate that the configuration of the terminal device takes effect, or the terminal device has configured the second functional unit. Optionally, the reconfiguration complete message may be used to indicate that the terminal device has configured the RLC bearer associated with the second functional unit. The present application does not limit the name of the reconfiguration complete message, and the reconfiguration complete message may also have other names.

[0184] In some alternative embodiments, the above reconfiguration completion message may carry an SN RRC reconfiguration completion message; the first network device may send the SN RRC reconfiguration completion message to the second network device. In some other alternative embodiments, the terminal device may send the 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 becomes effective or the terminal device has configured a second functional unit. Optionally, the SN RRC reconfiguration completion message may be used to indicate that the terminal device has configured an RLC bearer associated with the second functional unit. The present 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 an inter-station interface.

[0185] In some alternative embodiments, the terminal device may send an RRC reconfiguration completion message to the second network device. For example, direct transmission of SRB messages may be supported between the terminal device and the second network device.

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

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

[0188] The second network device may perform random access with the terminal device. In some alternative embodiments, the second network device may perform random access with the terminal device after receiving the SN RRC reconfiguration completion message. However, the present application is not limited thereto. For example, the second network device or the terminal device may directly initiate random access.

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

[0190] It should be noted that, in related technical solutions, 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 transmissions of the corresponding radio bearer are restored. Therefore, in related technical solutions, the MN does not need to know whether the terminal device has successfully added the SN. However, in this application, after the first network device sends the first information, it still conducts downlink transmission with the terminal device. Therefore, it is necessary to know the SN addition situation of the terminal device to perform corresponding processing.

[0191] 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 the 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 the uplink scheduling (or uplink transmission) of the first radio bearer of 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, and the indication information is used to instruct the second network device to perform downlink transmission of the first radio bearer or 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 according to the above indication information. The name of the above indication information is not limited in this application, and the above indication information may also have other names.

[0192] Through the above embodiment, the first network device can stop sending data of the first radio bearer to the terminal device when it is confirmed that the terminal device has added the second network device. Since the terminal device has successfully added the second network device, the second network device can perform downlink transmission of the first radio bearer with the terminal device. The above embodiment enables the terminal device to maintain downlink transmission during the process of reconstructing the protocol entity, thereby avoiding a rate drop.

[0193] Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: the terminal device stops sending 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 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 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 may perform unified deduplication and reordering processing on the uplink PDCP PDUs submitted by the first network device and the uplink PDCP PDUs sent by the terminal device, and submit them to the core network element. Optionally, the second network device may send data of the first radio bearer to the core network element through the NG-U tunnel. Optionally, the SN addition request received by the second network device from the first network device may include information about the uplink NG-U tunnel, and the second network device may send data of the first radio bearer to the core network element according to the information about the uplink NG-U tunnel.

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

[0195] Optionally, the data of the first radio bearer sent by the first network device to the core network element may be PDCP PDUs with consecutive 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 non-consecutive sequence numbers. Optionally, the second network device may send the received data of the first radio bearer to the core network element.

[0196] 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.

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

[0198] Through the above embodiments, the first network device can submit data of the first radio bearer to the second network device, enabling the second network device to perform uplink and downlink data transmission, thereby improving the continuity of data transmission.

[0199] Optionally, the first network device may send a PDU session modification indication to a core network element, for example, 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 element, for example, 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 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, and 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 marker, the UPF may send the downlink data of the first radio bearer to the second network device. Optionally, the AMF network element may send indication information to the first network device to indicate the completion of the PDU session modification. The indication information may also have other names.

[0200] Optionally, the first network device may perform at least one of releasing the inter-station tunnel between the first network device and the second network device, releasing the uplink NG-U tunnel between the first network device and the core network element, or releasing the downlink NG-U tunnel between the first network device and the core network element. Optionally, the first network device may perform the above release actions in response to the indication information indicating the completion of the PDU session modification. In other words, the first network device may perform the above release actions after receiving the indication information indicating the completion of the PDU session modification.

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

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

[0203] Optionally, the third information may be 1-bit indication information. As an example, the third information may be used to indicate the release of the original protocol stack resources for all radio bearers configured with a dual-active protocol stack. As another example, the third information may include or carry an identifier of the radio bearer, that is, the first network device may indicate the release of the original protocol stack resources for some radio bearers configured with a dual-active protocol stack. Optionally, the identifier of the radio bearer may not be carried in the third information, that is, the first network device may send the third information and the identifier of the radio bearer.

[0204] Optionally, in some other implementation scenarios of the foregoing embodiments, the method 400 further includes: the second network device sends third information to the terminal device. That is, the second network device may indicate to the terminal device to release the first functional unit. Optionally, the second network device receives indication information from the first network device, where the indication information is used to indicate the second network device to release the first functional unit of the terminal device. Optionally, in response to the indication information, or after the second network device receives the indication information, the second network device sends the third information to the terminal device. The foregoing indication information may have other names.

[0205] Optionally, the second network device may send the third information through the first network device. For example, the second network device sends indication information to the first network device, where the indication information is used to indicate the first network device to release the first functional unit of the terminal device. Optionally, in response to the indication information, or after the first network device receives the indication information, the first network device sends the third information to the terminal device.

[0206] Optionally, in some other implementation scenarios of the foregoing embodiments, the method 400 further includes: the first network device receives fourth information, where the fourth information is used to indicate at least one of the completion of the session modification of the protocol data unit, the terminal device has delivered all data of the first functional unit, or the terminal device requests to release the first functional unit.

[0207] Among them, the information indicating the completion of the session modification of the protocol data unit may come from a core network element. The information indicating that the terminal device has delivered all data of the first functional unit, or the information indicating that the terminal device requests to release the first functional unit may come from the terminal device.

[0208] Optionally, the first network device sends the third information to the terminal device, including: in response 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.

[0209] In a possible scenario, uplink data to be delivered to the first network device may be cached on the MCG resources associated with the first functional unit. Optionally, after delivering the uplink data of the first functional unit, the terminal device sends fourth information to the first network device.

[0210] 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.

[0211] Optionally, the first network device sends indication information to the second network device, and 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.

[0212] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the terminal device releases the first functional unit according to the third information. In other words, the terminal device releases the first functional unit when 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.

[0213] Optionally, in some other implementation scenarios of the above embodiment, the method 400 further includes: the first network device sends fifth information to the second network device, and the fifth information is used to instruct the second network device to configure the first radio bearer to be associated with the first functional unit and the second functional unit.

[0214] 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 a dual-active protocol stack for the first radio bearer. Optionally, the first network device may indicate which radio bearers are configured with a dual-active protocol stack.

[0215] Optionally, the first network device instructs the second functional unit to be associated with the air interface resources of the first network device and / or the air interface resources of the second network device, that is, to indicate 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, that is, the second functional unit is associated with the air interface resources of the first network device and / or the air interface resources of the second network device.

[0216] Optionally, the fifth information includes the 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 a dual-active protocol stack.

[0217] 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; the first network device sends fifth information to the second network device. That is to say, the first network device can decide to configure a dual-active protocol stack for the first radio bearer. Optionally, the first network device can determine to configure the first radio bearer to be associated with the first functional unit and the second functional unit according to the capabilities of the terminal device. For example, when the capabilities of the terminal device support a dual-active 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, when the capabilities of the terminal device do not support a dual-active 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.

[0218] The fifth information may be carried in an SN addition request message, but this application is not limited thereto, and the fifth information may be carried in other messages. This application is also not limited to the name of the fifth information, and the fifth information may also have other names.

[0219] In some alternative embodiments, the first network device may send an SN addition request message to the second network device, and the SN addition request message includes an addition indication for indicating the second network device to add the first radio bearer. Optionally, the addition indication is used to indicate that the functional unit of the first radio bearer is on the side of the second network device, that is, the first radio bearer corresponds to, is associated with, or terminates at the second network device. Optionally, the SN addition request message includes the fifth information.

[0220] Optionally, in some other implementation scenarios of the foregoing embodiments, the method 400 further includes: the first network device receives sixth information from the second network device, and the sixth information is used to indicate that the second network device determines to configure the first radio bearer to be associated with the first functional unit and the second functional unit. Correspondingly, the second network device sends the sixth information to the first network device.

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

[0222] Optionally, the fifth information includes the capability information of the terminal device. For example, the capability information of the terminal device may indicate that the terminal device's capability supports the dual-active protocol stack. Optionally, the second network device determines whether to agree to configure the dual-active protocol stack for the first radio bearer according to the capability information of the terminal device. For example, when the terminal device's capability supports the dual-active protocol stack, the second network device agrees to configure the dual-active protocol stack for the first radio bearer. For another example, when the terminal device's capability does not support the dual-active protocol stack, the second network device does not agree to configure the dual-active protocol stack for the first radio bearer.

[0223] In some other alternative embodiments, the second network device sends indication information for indicating that it is determined not to configure the first radio bearer to associate the first functional unit and 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 information may have other names, which are not limited in this application.

[0224] The sixth information may be carried in the SN addition response message, but this application is not limited thereto, and the sixth information may be carried in other messages.

[0225] Optionally, the second network device determines to configure the first radio bearer to associate the first functional unit and the second functional unit; the second network device sends the sixth information to the first network device. That is to say, the second network device may determine whether to agree to configure the dual-active protocol stack for the first radio bearer.

[0226] Optionally, in some other implementation scenarios of the above embodiments, the method further 400 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 radio bearer to associate the first functional unit and the second functional unit.

[0227] The second indication information may be carried in the SN addition response message, but this application is not limited thereto, and the second indication information may be carried in other messages.

[0228] Optionally, the second network device determines to configure the first radio bearer to associate the first functional unit and the second functional unit; the second network device sends the second indication information to the first network device. That is to say, the second network device may decide to configure the dual-active protocol stack for the first radio bearer.

[0229] Optionally, the first network device sends an SN addition request message to the second network device to request the establishment of a first radio bearer on the second network device side. Optionally, the SN addition request message may include the capability information of the terminal device. For example, the capability information of the terminal device may indicate that the terminal device's capability 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 according to the capability information of the terminal device. For example, when the terminal device's capability 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, when the terminal device's capability 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 according to at least one of the type of the first radio bearer or the QoS requirement.

[0230] Optionally, during the establishment of the 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 establishment of the 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. Among them, the capability information of the first network device can be used to indicate whether the first network device can configure a first radio bearer to associate a first functional unit and a second functional unit. The capability information of the second network device can be used to indicate whether the second network device can configure a first radio bearer to associate a first functional unit and a second functional unit.

[0231] That is to say, the first network device and the second network device can negotiate in advance to obtain the base station capability information to know whether the first network device or the second network device supports the configuration of the dual activation protocol stack.

[0232] Optionally, in some other implementation scenarios of the foregoing embodiments, 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.

[0233] The first configuration information may be pre-configuration information; in other words, the first configuration information may not take effect temporarily; in other words, the first configuration information may be configuration information to be activated; in other words, the first configuration information may be unactivated configuration information.

[0234] 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. The present 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, and the indication information is used to indicate to the first network device that the first configuration information is pre-configuration information.

[0235] The present application does not limit the name of the third indication information, and the third indication information may have other names.

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

[0237] Optionally, the first network device sends fifth information to the second network device, and the fifth information is used to request the second network device to pre-configure the first radio bearer to associate the first functional unit and the second functional unit. Optionally, the second network device determines to pre-configure the first radio bearer to associate the first functional unit and the second functional unit; the first network device sends the fifth information to the second network device.

[0238] 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 a dual activation protocol stack for the first radio bearer. Optionally, the first network device may indicate which radio bearers to pre-configure the dual activation protocol stack. Optionally, the fifth information includes the capability information of the terminal device. For example, the capability information of the terminal device may indicate that the terminal device's capability supports the dual activation protocol stack.

[0239] Optionally, the first network device determines to pre-configure the first radio bearer to associate the first functional unit and the second functional unit; the first network device sends the fifth information to the second network device. That is, the first network device may decide to pre-configure a dual activation protocol stack for the first radio bearer. Optionally, the first network device may determine to pre-configure the first radio bearer to associate the first functional unit and the second functional unit according to the capability of the terminal device. For example, when the terminal device's capability supports the dual activation protocol stack, the first network device determines to pre-configure the first radio bearer to associate the first functional unit and the second functional unit. For another example, when the terminal device's capability does not support the dual activation protocol stack, the first network device determines not to pre-configure the first radio bearer to associate the first functional unit and the second functional unit.

[0240] Optionally, the fifth information includes information for requesting the second network device to pre-configure a first radio bearer associated with a first functional unit and a second functional unit. Optionally, the information for requesting the second network device to pre-configure a first radio bearer associated with a first functional unit and a second functional unit may be independent of the fifth information. For example, the first network device may send a first configuration request to the second network device to pre-configure the information for a first radio bearer associated with a first functional unit and a second functional unit.

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

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

[0243] Optionally, the sixth information includes information indicating the determination to pre-configure a first radio bearer associated with a first functional unit and a second functional unit. Optionally, the information indicating the determination to pre-configure a first radio bearer associated with a first functional unit and a second functional unit may be independent of the sixth information. For example, the second network device may send information indicating the determination to pre-configure a first radio bearer associated with a first functional unit and a second functional unit to the first network device.

[0244] Optionally, the second indication information is used to indicate the first network device to pre-configure the first radio bearer associated with the first functional unit and the second functional unit. Optionally, the second network device determines to pre-configure the first radio bearer associated with the first functional unit and the second functional unit; the second network device sends the second indication information to the first network device.

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

[0246] Optionally, the first network device generates configuration information of at least one candidate third network device. The second network device of this application is one of the at least one third network devices. The difference is that the second network device is the finally selected network device, or in other words, the configuration information of the second network device (i.e., the first information) finally takes effect. For example, the at least one candidate third network device may be at least one candidate SN. Optionally, the configuration information from at least one third network device includes first indication information.

[0247] Optionally, the first network device determines a pre-configuration for adding a second network device to the terminal 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 it is possible to perform a pre-configuration for adding a second network device to the terminal device according to the capability information of the terminal device. For example, when the capability of the terminal device supports pre-configuration, the first network device determines to perform a pre-configuration for adding a second network device to the terminal device. For another example, when the capability of the terminal device does not support pre-configuration, the first network device determines not to perform a pre-configuration for adding a second network device to the terminal device.

[0248] Optionally, the first network device receives the capability information of the second network device. For example, the first network device may receive the 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 used as a candidate base station (or called a target base station) for adding a second network device pre-configuration.

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

[0250] Optionally, S410 includes: the first network device receives configuration information from at least one third network device. Among them, the second network device is one of the at least one third network devices. 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 at least one third indication information corresponds to at least one set of configuration information respectively, and at least one third indication information is respectively used to indicate that at least one set of configuration information is pre-configuration information. Optionally, one set of configuration information in at least one set of configuration information and the third indication information corresponding to this configuration information may be carried in one message. Optionally, one or more sets of configuration information in at least one set of configuration information from the first network device include first indication information. Optionally, the third indication information includes first indication information.

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

[0252] Optionally, in some other implementation scenarios of the foregoing embodiments, the first configuration information corresponds to information of the second network device. Wherein, the method 400 further includes: the first network device sends seventh information to the terminal device, and 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.

[0253] The first configuration information corresponds to information of 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, the mapping table includes at least one set of configuration information and information of at least one candidate third network device. Optionally, the identifier of at least one set of configuration information has a mapping relationship with the information of at least one candidate third network device. For example, the mapping table includes the identifier of at least one set of configuration information and the information of at least one candidate third network device. Wherein, the identifier of the configuration information corresponds to the configuration information.

[0254] The first configuration information corresponds to information of the second network device. Optionally, the first configuration information includes information of the second network device. In this way, the first configuration information can be matched according to the information of the second network device. However, the present application does not limit this, and the information of the second network device may not be in the first configuration information, that is to say, the information of the second network device and the first configuration information may be sent separately.

[0255] Exemplarily, the information of the second network device may include at least one of the identification information of the second network device, the number 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.

[0256] 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, etc. The seventh information may be underlying indication information, for example, a MAC control element (CE). Optionally, the seventh information includes first indication information.

[0257] 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. Another example, in other words, 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 can be understood that the seventh information can indicate which set of pre-configurations the terminal device should trigger.

[0258] Optionally, the first network device may indicate information about the second network device in the seventh information. For example, at least one of the identification information of the second network device, the number 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) of the second network device to be triggered according to the information of the second network device. Optionally, S430 includes: the terminal device establishes the second functional unit according to 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 according to 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 according to the seventh information and the first configuration information.

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

[0260] It can be understood that the terminal device can apply the corresponding configuration according to the indication of the first network device and access the second network device (or referred to as the target SN). For the radio bearer with a dual-activated 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 at the same time, a new PDCP (i.e., the second functional unit) will be established and the corresponding underlying configuration will be configured and associated. Optionally, the terminal device can maintain the downlink synchronization with the candidate SN in advance according to the pre-configuration information, so as to reduce the access time to the second network device.

[0261] Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: The first network device receives a first message from the terminal device, where 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, where 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 may be referred to as an RRC reconfiguration complete message or have other names. Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: The first network device sends the fifth indication information to the second network device.

[0262] Optionally, after the first network device receives the first message, the first network device activates a pre-configured tunnel corresponding to the first network device. Among them, the pre-configured 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 the second network device receives the fifth indication information, it activates a pre-configured tunnel corresponding to the second network device. For example, the second network device activates the NG-U tunnel configuration between the second network device and the core network element, and the NG-U tunnel is used to send the uplink data of the first radio bearer to the core network element.

[0263] Optionally, the fifth indication information includes the identifier of the terminal device. It can be understood that in the case where multiple terminal devices pre-configure the candidate second network device, the second network device can trigger the pre-configuration corresponding to the terminal device according to the identifier of the terminal device. Optionally, the identifier of the terminal device may not be 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.

[0264] Optionally, the first network device sends seventh information; the first network device activates the above-mentioned pre-configured tunnel. That is to say, after the first network device activates the pre-configuration information, it activates the corresponding pre-configured tunnel.

[0265] Optionally, in some other implementation scenarios of the above embodiments, the method 400 further includes: The first network device activates the pre-configured tunnel between the first network device and the second network device.

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

[0267] Optionally, the first network device sends fourth indication information to the second network device, where the fourth indication information is used to indicate that the terminal device adds the second network device according to the first configuration information; the second network device activates the pre-configured tunnel corresponding to the second network device.

[0268] 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.

[0269] 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.

[0270] 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.

[0271] Figure 6 600 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 parts not described in method 600, please refer to the description of method 400. Figure 6 The dotted arrow in the figure can indicate the direction of data transmission. Figure 6 This is only an example and does not limit the present application.

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

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

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

[0275] 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.

[0276] 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.

[0277] Optionally, MN and SN may negotiate to obtain base station capability information previously (e.g., during the process of establishing an inter-station interface), and determine whether SN or MN supports configuring a dual-active protocol stack.

[0278] S603, MN sends a tunnel establishment message to SN.

[0279] Among them, the tunnel establishment message can be used to indicate the establishment of a tunnel on the inter-station interface. This tunnel can be used for the downlink data transmission of the MCG bearer or split bearer terminated by SN.

[0280] S604, MN sends an RRC reconfiguration message to UE.

[0281] The RRC reconfiguration message can be used to indicate UE to perform secondary station addition and configuration. Optionally, the RRC reconfiguration message can include first information. For details, refer to the previous description of the first information, which will not be elaborated here.

[0282] S605, UE performs random access with SN.

[0283] UE can connect to SN through random access based on the RRC configuration in the RRC reconfiguration message. Optionally, UE can maintain the connection with MN. Exemplarily, the RRC configuration can include at least one of the following: configuration of the bearer terminated by SN, SN PDCP configuration, or configuration of the radio interface resources associated with the bearer terminated by SN. For details, refer to the description of the first configuration information and the second configuration information, which will not be elaborated here.

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

[0285] S606, UE sends an RRC reconfiguration complete message to MN.

[0286] Optionally, the RRC reconfiguration complete message can be used to indicate the completion of configuration. The RRC reconfiguration complete message can include the SN RRC reconfiguration complete message.

[0287] S607, MN sends an SN reconfiguration complete message to SN.

[0288] The RRC reconfiguration complete message for SN can indicate to SN that UE has completed the dual-connection configuration.

[0289] 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. Another example, the execution order can be: S606, S605, S607.

[0290] S608, the SN sends an SN addition success message.

[0291] The SN addition success message is used to indicate that the addition of the MN secondary station is successful. Optionally, the MN stops sending downlink data, and the SN starts to send downlink data to the UE. For the description of the SN addition success message, reference can be made to the description of the second information in this application, which will not be elaborated here.

[0292] Among them, S608 is an optional step. In some other optional embodiments, S608 can be replaced with: the UE sends an SN addition success message.

[0293] S609, the MN sends a status report indication to the SN.

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

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

[0296] S610, the MN sends a PDU session modification message to the AMF.

[0297] This PDU session modification message can be used to instruct the AMF to perform a PDU session modification. In other words, this PDU session modification message can be used to instruct the NG-U tunnel corresponding to the bearer to be switched from the MN to the SN side.

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

[0299] This bearer modification message is used to instruct the UPF to establish the corresponding downlink NG-U tunnel, and this downlink NG-U tunnel is used to send downlink data.

[0300] S612, the UPF sends an end marker information to the MN.

[0301] Optionally, the UPF sends this end marker information through the downlink NG-U tunnel on the source MN side. This 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 an end marker information to the MN when the downlink data transmission is completed.

[0302] S613, the AMF sends a PDU session modification confirmation message to the MN.

[0303] This PDU session modification confirmation message can be used to indicate the completion of the PDU session modification.

[0304] In the downlink data transmission direction, after the MN sends the RRC reconfiguration message (S604), the MN maintains downlink transmission. The MN delivers downlink data to the SN through the inter-station interface (established in S603) (the data forwarding process is indicated by the dashed arrow in the figure). Optionally, the MN can indicate to clear the successfully transmitted uplink and downlink data by sending a status report (S609), and this status report indicates the situation of the uplink and downlink data successfully received by the UE on the MN side.

[0305] During the uplink data transmission process, after the UE receives 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 the MN sends the RRC reconfiguration message (S604), the MN maintains uplink scheduling (i.e., maintains uplink transmission) and delivers the uplink data to the UPF.

[0306] After the UE successfully accesses the SN, the SN can indicate to the MN that the secondary station addition is successful (S608). The MN stops uplink scheduling. At the same time, the MN delivers the uplink PDCP PDUs with continuous sequence numbers to the core network and delivers the uplink PDCP PDUs with discontinuous sequence numbers to the SN through the inter-station interface (the data delivery process is indicated by the dashed 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.

[0307] Optionally, in the SN side, the received secondary station addition request (S601) includes uplink NG-U tunnel information. This uplink NG-U tunnel can be used to transmit the 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 perform unified deduplication and reordering processing on the uplink PDCP PDUs delivered by the MN and the uplink PDCP PDUs received from the UE and deliver them to the core network.

[0308] Optionally, after the MN receives the PDU session modification confirmation message (S613), the MN releases the inter-station tunnel, releases the uplink and downlink NG-U tunnels with the core network. Optionally, it indicates to the UE to release the dual-active protocol stack. After the UE side receives the dual-active 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-active protocol stack release indication to the SN, indicating that the UE side has released the dual-active protocol stack. Optionally, the SN indicates to the UE to release the dual-active protocol stack. For example, based on the MN indication, or the SN can send the dual-active protocol stack indication to the UE through the MN. For details, please refer to the above description of the third piece of information and will not be elaborated here.

[0309] Optionally, the uplink data delivered to the MN may be cached on the MCG resources associated with the original PDCP on the UE side. After the UE delivers the uplink data on the original protocol stack, it sends an end indication (i.e., the fourth piece of information) to the MN. After receiving the end indication, the MN sends a dual activation release indication to the UE based on the end indication. For specific details, refer to the above description of the fourth piece of information, which will not be elaborated here.

[0310] Optionally, the MN sends indication information to the SN, indicating that the dual activation protocol stack on the UE side has been released.

[0311] Figure 7 It is a schematic flowchart of another communication method 700 provided by an embodiment of the present application. Method 700 can be combined with any embodiment of Method 400. Method 700 is an embodiment related to pre-configuration. For parts not described, refer to the description in Method 400. Among them, Figure 7 The dashed arrows in can indicate the direction of data transmission. It should be noted that Figure 7 Only as an example, it does not constitute a limitation to the present application.

[0312] S701, the MN sends a secondary station addition pre-configuration request message to at least one SN.

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

[0314] Optionally, the MN determines the pre-configuration for secondary station addition for the UE. Optionally, the MN determines the target SN for pre-configuration based on the measurement report of the UE. Optionally, the MN determines whether it can perform pre-configuration for secondary station addition for the UE based on the UE's capabilities. Optionally, the MN obtains the capability information of the SN based on previous inter-station interactions and determines whether the SN can be used as the target SN for secondary station addition pre-configuration.

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

[0316] It can be understood that at least one SN respectively sends a secondary station addition pre-configuration response message to the MN. Optionally, the SN generates the RRC pre-configuration on the secondary station side and sends it to the MN through the secondary station addition pre-configuration response message.

[0317] In a possible implementation, the MN determines a dual-active protocol stack for the radio bearer configuration and indicates it in the secondary station addition pre-configuration request message at S701. The SN generates a radio bearer configuration based on the indication of the MN, and the corresponding configuration includes a dual-active protocol stack configuration indication. Optionally, the SN can determine whether to configure or not configure the dual-active protocol stack and indicate the MN. In another possible implementation, it is the SN that determines to configure the dual-active protocol stack. For example, the SN determines to configure the dual-active protocol stack for the radio bearer based on the radio bearer type or QoS requirement and indicates the MN.

[0318] S703, the MN sends a tunnel establishment pre-configuration message to at least one SN.

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

[0320] S704, the MN sends an RRC re-configuration message to the UE.

[0321] Optionally, the MN generates a configuration of one or more candidate SNs. In other words, the RRC re-configuration message corresponds to at least one SN. Among them, the RRC re-configuration message may include the RRC configuration in S702. Optionally, the RRC re-configuration message may include third indication information, and the third indication information can be used to indicate that the RRC re-configuration message is a pre-configuration message. For the specific description of the third indication information above, it will not be elaborated here.

[0322] Optionally, the RRC re-configuration message includes identification information or number information corresponding to each of at least one SN, or node identification information or cell identification information corresponding to each of at least one SN. Optionally, after receiving the RRC re-configuration message, the UE sends an RRC re-configuration complete message to the MN.

[0323] S705, the MN sends an activation indication to the UE.

[0324] Optionally, the activation indication may include seventh information. For the specific description of the seventh information above, it will not be elaborated here.

[0325] Optionally, the MN determines to trigger the UE to apply the pre-configuration corresponding to the SN. For example, the MN determines that the trigger condition is met based on the measurement report of the UE.

[0326] S706, the UE performs random access with the SN.

[0327] For example, the UE applies corresponding configurations according to the activation indication of the MN and accesses the target SN. Meanwhile, for the radio bearers with dual-activated protocol stacks configured, the original PDCP and associated underlying configurations will be maintained, and at the same time, a new PDCP entity will be established (or new PDCP functions will be configured in the original PDCP entity) and the corresponding underlying configurations will be configured and associated. Optionally, the UE may maintain the downlink synchronization with the candidate SN in advance according to the pre-configuration, so as to reduce the duration of accessing the target SN.

[0328] S707, the UE sends an RRC reconfiguration complete message to the MN.

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

[0330] S708, the MN sends an SN RRC reconfiguration complete message to the SN.

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

[0332] In another possible implementation, if direct SRB message transmission is supported between the UE and the SN, the UE may directly send the RRC reconfiguration complete message to the SN. That is to say, S708 can be replaced by: the UE sends an SN RRC reconfiguration complete message to the SN.

[0333] S709, the MN sends a tunnel activation message to the SN.

[0334] 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 identifier of the UE. It can be understood that in the case where multiple UEs are pre-configured with this candidate SN, the SN can trigger the pre-configuration corresponding to the UE according to the identifier of the UE. Optionally, the identifier of the UE may not be in the tunnel activation message. In other words, the identifier of the UE can be independent of the tunnel activation message. Optionally, the MN sends the identifier of the UE to the SN.

[0335] Specifically, the MN may activate the downlink Xn-U tunnel configuration from the SN to the MN, as well as the Xn-U tunnel configuration for data transfer. Optionally, the SN activates the NG-U tunnel configuration between the SN and the core network for forwarding the uplink data of the radio bearer to the core network. In another possible way, 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, and the SN activates the Xn-U tunnel configuration and the NG-U tunnel configuration between the SN and the core network. That is, the execution order of S709 may be before S706 or S705.

[0336] Optionally, the MN stops sending downlink data and uplink scheduling and performs data transfer.

[0337] S7:10, the MN sends status indication information to the SN to indicate the uplink and downlink data transmission status.

[0338] Optionally, for S711 to S714, reference may be made to the descriptions of S610 to S613, which will not be elaborated here.

[0339] S711 to S714 are optional steps and can be implemented through pre-configuration. After S701 or S702, the MN may 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 may directly trigger the activation of the NG-U tunnel based on the configuration for uplink and downlink data transmission.

[0340] Optionally, based on the currently effective configuration of the UE, the MN determines that there is no longer uplink and downlink data transmission between the PDCP entity (or PDCP function) of the UE and the MN, and instructs the UE to release the dual-activated protocol stack. The scheme for instructing the UE to release the dual-activated protocol stack may refer to the description of the third information above, which will not be elaborated here.

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

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

[0343] The corresponding apparatus embodiments of the method embodiments of the present application are introduced below. Only a brief introduction to the apparatus is given below, and the specific implementation steps and details of the solution may refer to the foregoing method embodiments.

[0344] To implement each function in the method provided by this application, the communication device may include a hardware structure and / or software module, and implement the above functions in the form of a hardware structure, software module, or a combination of a hardware structure and a software module. Whether a certain function among the above functions is executed in the form of a hardware structure, software module, or a combination of a hardware structure and a software module depends on the specific application and design constraints of the technical solution.

[0345] Figure 8 FIG. 6 is a schematic block diagram of a communication device 800 according to an embodiment of this application. The communication device 800 includes a processor 810 and a communication interface 820, and the processor 810 and the communication interface 820 can be connected to each other through a bus 830. The communication device 800 can be a first network device, a second network device, or a terminal device.

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

[0347] The processor 810 can be one or more central processing units (CPUs). When the processor 810 is a single CPU, the CPU can be a single-core CPU or a multi-core CPU. Among them, the processor 810 can be a signal processor, a chip, or other integrated circuits that can implement the method of this application, or a partial circuit for processing functions in the foregoing processor, chip, or integrated circuit. In addition, the communication interface 820 can also be an input / output interface, and the input / output interface is used for input or output of signals or data, and can also be an input / output circuit.

[0348] Exemplarily, the communication device 800 is a first network device, and the processor 810 is configured to perform the following operations: receive 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, and the first network device and the second network device provide services for a terminal device; send first information to the terminal device, where the first information includes the first configuration information and first indication information, the first information is used to indicate adding the second network device, and the first indication information is used to indicate that the first radio bearer is associated with a first functional unit, where 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.

[0349] Exemplarily, the communication device 800 is a terminal device, and the processor 810 is configured to perform the following operations: receive first information from a first network device, where the first information includes first configuration information and first indication information, the first configuration information is used to configure a second functional unit associated with the first radio bearer, the first information is used to indicate adding the second network device, the first indication information is used to indicate that the first radio bearer is associated with a first functional unit, where 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 a second network device, and the first network device and the second network device provide services for the terminal device; establish the second functional unit and add the second network device according to the first information.

[0350] Exemplarily, the communication device 800 is a second network device, and the processor 810 is configured to perform the following operations: send 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 radio bearer for a terminal device, and the second functional unit is used 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 radio bearer is associated with a first functional unit, 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.

[0351] The above content is only described as an example. 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 foregoing method embodiments.

[0352] It can be understood that the communication interface 820 can also be referred to as a transceiver. The transceiver may include a transmitter and a receiver, where the transmitter is used to perform a sending operation, and the receiver is used to perform a receiving operation. For example, the processor 810 is used to control the transceiver to perform signal reception and / or sending.

[0353] Note 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. Specifically, it depends on whether the above-described solution executed by the communication device 800 includes a sending action and a receiving action.

[0354] The above description is only an exemplary description. For specific content, reference may be made to the content shown in the above method embodiments. Figure 8 The implementation of each operation in Figures 3 to 7 may also correspondingly refer to the corresponding description of the method embodiment shown in

[0355] For example, the communication device 800 may be used to execute Figures 3 to 7 the solution shown.

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

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

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

[0359] For other implementation manners, specific reference may be made to the detailed introduction of the foregoing Figures 3 to 7 shown embodiments, which will not be elaborated here. It should be understood that the specific processes for each component to execute the above corresponding processes have been described in detail in the above method embodiments. For the sake of brevity, they will not be elaborated here.

[0360] Figure 9 is a schematic block diagram of another communication device 900 according to an embodiment of the present application. The communication device 900 may be a terminal device, a first network device, or a second network device, or may be a chip or module in a terminal device, a first network device, or a second network device, and is used to implement Figures 2 to 7 the method involved in the shown embodiment. For specific reference, please refer to the relevant introduction in the above method embodiments.

[0361] The communication device 900 includes a transceiver unit 910. The transceiver unit 910 will be introduced exemplarily below.

[0362] 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, in the embodiments of this application, the transmitting unit and the receiving unit are combined into one transceiver unit. A unified description is made here and will not be repeated hereinafter. The transceiver unit 910 can implement corresponding communication functions. The transceiver unit 910 may also be referred to as a communication interface or a communication module.

[0363] It should be noted that the communication device 900 may include a transmitting unit but not a receiving unit. Or, the communication device 900 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described solution executed by the communication device 900 includes a transmitting action and a receiving action.

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

[0365] Optionally, the communication device 900 may include a processing unit 920, which is used to execute the content related to processing, coordination, etc. of the communication device 900.

[0366] Exemplarily, the transceiver unit 910 is used to receive first information, etc. from a first network device.

[0367] Optionally, the communication device 900 may include a processing unit 920, which is used to execute the content related to processing, coordination, etc. of the communication device 900.

[0368] Exemplarily, the transceiver unit 910 is used to send first configuration information, etc. to a first network device.

[0369] Optionally, the communication device 900 may include a processing unit 920, which is used to execute the content related to processing, coordination, etc. of the communication device 900.

[0370] The above content is only for exemplary description. The communication device 900 will be responsible for executing the relevant methods or steps in the foregoing method embodiments.

[0371] Optionally, the communication device 900 includes a storage unit 930, which is used to store programs or codes for executing the foregoing methods. Or rather, 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 so that the communication device 900 can implement the foregoing method embodiments. For example, the communication device 900 can be used to execute Figures 3 to 7 the solution shown.

[0372] Exemplarily, the processing unit 920 may be configured to receive 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, and the first network device and the second network device provide services for a terminal device; and to send first information to the terminal device, where the first information includes the first configuration information and first indication information, the first information is used to indicate adding the second network device, and the first indication information is used to indicate that the first radio bearer is associated with a first functional unit, where 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.

[0373] Exemplarily, the processing unit 920 may be configured to receive first information from a first network device, where the first information includes first configuration information and first indication information, the first configuration information is used to configure a second functional unit associated with the first radio bearer, the first information is used to indicate adding the second network device, the first indication information is used to indicate that the first radio bearer is associated with a first functional unit, where 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 a second network device, and the first network device and the second network device provide services for the terminal device; and to establish the second functional unit and add the second network device according to the first information.

[0374] Exemplarily, the processing unit 920 may be configured to send 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 radio bearer for a 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 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.

[0375] For other implementation manners, reference may specifically be made to the detailed introduction of the foregoing Figures 3 to 7 illustrated embodiments, which will not be elaborated here. It should be understood that the specific processes for each component to execute the above corresponding processes have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.

[0376] Figure 8 and Figure 9 the illustrated device embodiments are used to implement Figures 3 to 7 the content described above. Figure 8 and Figure 9 The specific execution steps and methods of the illustrated device may refer to the content described in the foregoing method embodiments.

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

[0378] The present application also provides a chip, including a processor, which is used to call and run the instructions stored in the memory from the memory, so that a communication device installed with the chip executes the methods in the above embodiments.

[0379] The present application also provides another chip, including: an input interface, an output interface, and a processor. The input interface, the output interface, and the processor are connected through an internal connection path. The processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the methods in the above embodiments. Optionally, the chip further includes a memory, which is used to store computer programs or code.

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

[0381] In another embodiment of the present application, a computer program product including a computer program or instructions is provided. When the computer program product runs on a computer, the methods in the foregoing embodiments are realized.

[0382] The present application also provides a computer program. When the computer program runs in a computer, the methods in the foregoing embodiments are realized.

[0383] In another embodiment of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the methods in the foregoing embodiments are realized.

[0384] The present application also provides a communication system, including a first network device, a second network device, and a terminal device. Among them, the first network device, the second network device, and the terminal device are respectively used 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.

[0385] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0386] Those skilled in the art can 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 foregoing method embodiments and will not be elaborated herein.

[0387] In several embodiments provided in the present 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 illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, 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 displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0388] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0390] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable 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 methods described in each embodiment of the present application. The foregoing storage medium includes: various media that can store program codes such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs.

[0391] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claimed rights.

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, and the first network device and the second network device provide services for a terminal device; Sending first information to the terminal device, where the first information includes the first configuration information and first indication information, and the first information is used to indicate adding the second network device, and the first indication information is used to indicate that the first radio bearer is further associated with a first functional unit, where the first functional unit is used for the terminal device to process data corresponding to the first network device, and the second functional unit is used for the terminal device to process data corresponding to the second network device.

2. The method according to claim 1, wherein 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; Stopping 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 includes: Sending third information to the terminal device, where the third information is used to indicate that the terminal device releases the first functional unit.

4. The method according to claim 3, characterized in that The method further includes: Receiving fourth information, where the fourth information is used to indicate at least one of completion of session modification of a protocol data unit, the terminal device has delivered all data of the first functional unit, or the terminal device requests to release the first functional unit.

5. The method according to claim 4, wherein The sending the third information to the terminal device includes: In response to the fourth information, sending the third information to the terminal device.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Sending fifth information to the second network device, where the fifth information is used to indicate that the second network device configures the first radio bearer to be associated with the first functional unit and the second functional unit.

7. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receiving second indication information from the second network device, where the second indication information is used to indicate that the first network device configures the first radio bearer to be associated with the first functional unit and 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, where the method further includes: Sending seventh information to the terminal device, where the seventh information is used to activate configuration of the first configuration information, and the seventh information includes information of the second network device.

10. The method according to claim 9, wherein The method further includes: Sending fourth indication information to the second network device, where the fourth indication information is used to indicate that the terminal device adds 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 includes: Sending eighth information to a core network element, where the eighth information is used to indicate activation of a pre-configured tunnel corresponding to the second network device, and 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: Receive first information from a first network device, where the first information includes first configuration information and first indication information. The first configuration information is used to configure a second functional unit associated with the first radio bearer, and the first indication information is used to indicate that the first radio bearer is also associated with a first functional unit. The first information is used to indicate the addition of a second network device. Here, 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. The first network device and the second network device provide services for the terminal device; Establish the second functional unit and add the second network device according to the first information.

14. The method according to claim 13, wherein The method further includes: Receive third information from the first network device, where the third information is used to indicate that the terminal device releases the first functional unit; Release the first functional unit according to the third information.

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

16. The method according to any one of claims 13 to 15, characterized in that, The method further includes: Establish a second bearer and a third bearer according to the first information. Here, 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; Here, the method further includes: Receive seventh information from the first network device, where the seventh information includes information of the second network device; Here, the establishing of the second functional unit according to the first information includes: Establish the second functional unit and add the second network device according to the seventh information and the first configuration information.

19. A communication method, characterized in that, The method is applied to a second network device, and the method includes: Send 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 radio bearer for a terminal device, and the second functional unit is used for 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 radio bearer is also associated with a first functional unit, and the first functional unit is used for the terminal device to process data corresponding to the first network device. The first network device and the second network device provide services for the terminal device.

20. The method according to claim 19, wherein The method further includes: 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 includes: Receive 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 and the second functional unit.

22. The method according to claim 19 or 20, characterized in that, The method further includes: Send 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 and the second functional unit.

23. The method according to any one of claims 19 to 22, characterized in that, The method further includes: 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, It includes a processing circuit and an input / output interface. The input / output interface is used to input and / or output signals. 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, It includes: A processor and a memory. A computer program or instruction is stored in the memory. The processor is used to, by executing the computer program or the instruction, cause the communication device to execute the method according to any one of claims 1 to 12, or cause the communication device to execute the method according to any one of claims 13 to 18, or cause the communication device to execute the method according to any one of claims 19 to 23.

26. A computer-readable storage medium, characterized in that, A computer program or instruction is stored on the computer-readable storage medium. When the computer program or the instruction runs on a computer, the method according to any one of claims 1 to 12 is caused to be executed, or the method according to any one of claims 13 to 18 is caused to be executed, or the method according to any one of claims 19 to 23 is caused to be executed.

27. A computer program product, characterized in that, It includes computer program code. When the computer program code runs, the method according to any one of claims 1 to 12 is implemented, or the method according to any one of claims 13 to 18 is implemented, or the method according to any one of claims 19 to 23 is implemented.

28. A communication system, characterized in that, It includes a first network device, a terminal device, and a second network device. Among them, 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, It includes: A processor. The processor is used to, by executing a computer program or instruction, cause the chip to execute the method according to any one of claims 1 to 12, or cause the chip to execute the method according to any one of claims 13 to 18, or cause the chip to execute the method according to any one of claims 19 to 23.

Images