Data transmission method, terminal device and network node

Abstract

Provided are a data transmission method, a terminal device, and a network node, the method comprising: the terminal device receives first configuration information, the first configuration information being used to configure a small data transmission configuration corresponding to a data radio bearer DRB; the terminal device performs small data transmission according to the first configuration information.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and more specifically, to a data transmission method, a terminal device, and a network node. Background Art

[0002] In a New Radio (NR) communication system, small data transmission of a terminal in an inactive state can be supported.

[0003] The NR system also supports Multi-RAT Dual Connectivity (MR-DC) scenarios, where data transmission on different bearers uses different radio resources and keys.

[0004] In order to save energy for the terminal, the concept of deactivating the secondary cell group (SCG) is introduced, that is, the transmission on the SCG side will be suspended even if the terminal is in a connected state. In this way, how to transmit small data without activating the radio resources on the SCG side in the MR-DC scenario is an urgent problem to be solved. Summary of the invention

[0005] Provided are a data transmission method, terminal equipment and network node, which can realize small data transmission without activating SCG side wireless resources.

[0006] In a first aspect, a data transmission method is provided, including: a terminal device receives first configuration information, where the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB; and the terminal device performs small data transmission according to the first configuration information.

[0007] In a second aspect, a data transmission method is provided, including: a first node sends first configuration information to a terminal device, wherein the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB.

[0008] In a third aspect, a terminal device is provided, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the terminal device includes a unit for executing the method in the first aspect or any possible implementation of the first aspect.

[0009] In a fourth aspect, a network device is provided, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the network device includes a unit for executing the method in the second aspect or any possible implementation of the second aspect.

[0010] In a fifth aspect, a terminal device is provided, the terminal device comprising: a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.

[0011] In a sixth aspect, a network device is provided, the network device comprising: a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manner.

[0012] In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or in each of their implementations.

[0013] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of the first to second aspects or in each of their implementations.

[0014] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0015] In a ninth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method in any one of the first to second aspects or their respective implementations.

[0016] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.

[0017] Based on the above technical solution, the network device can configure the DRB for small data transmission, for example, configure the SCG bearer not to be used for small data transmission, or configure the SCG bearer to be used for small data transmission, and configure the method for performing small data transmission on the SCG bearer. When small data arrives at the DRB, the terminal device can perform small data transmission according to the small data transmission configuration corresponding to the DRB, thereby enabling small data transmission without activating the wireless resources on the SCG side. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 and Figure 2 It is a schematic block diagram of the system framework provided by this application.

[0019] Figure 3 and Figure 4 They are Figure 2 An example of a specific scenario for EN-DC is shown.

[0020] Figure 5 yes Figure 2 The schematic structural diagram of the load under the EN-DC system is shown.

[0021] Figure 6 This is a schematic structural diagram of DC bearer in a 5GC system provided in an embodiment of the present application.

[0022] Figure 7 This is a schematic diagram of a terminal device state transition provided by the present application.

[0023] Figure 8 It is a schematic diagram of an inactive terminal device RNA provided in this application.

[0024] Fig. 9 This is a schematic flowchart of an RNAU with context migration provided by the present application.

[0025] Fig.10 It is a schematic flowchart of a context-free RNAU provided in this application.

[0026] Fig.11 It is a schematic flow chart of a small data transmission provided by this application.

[0027] Fig.12 It is a schematic diagram of a data transmission method provided in an embodiment of the present application.

[0028] Fig.13 It is a schematic diagram of a data transmission method provided in another embodiment of the present application.

[0029] Fig.14 It is a schematic diagram of a data transmission method provided in yet another embodiment of the present application.

[0030] Fig.15 yes Fig.14 The specific flow chart of the data transmission method shown.

[0031] Figures 16 to 22 This is a schematic diagram of the MAC SDU header format.

[0032] Fig.23 It is a schematic interactive diagram of a data transmission method provided in yet another embodiment of the present application.

[0033] Fig.24 yes Fig.23 The specific flow chart of the data transmission method shown.

[0034] Fig.25It is a schematic block diagram of a network node provided in an embodiment of the present application.

[0035] Fig.26 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0036] Fig. 27 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0037] Fig.28 It is a schematic block diagram of the chip provided in the embodiment of the present application.

[0038] Fig.29 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0040] Figure 1 is a schematic diagram of a system 100 according to an embodiment of the present application. Figure 1 As shown, the terminal device 110 is connected to a first network device 130 under a first communication system and a second network device 120 under a second communication system. For example, the first network device 130 is a network device under Long Term Evolution (LTE), and the second network device 120 is a network device under New Radio (NR).

[0041] The first network device 130 and the second network device 120 may include multiple cells.

[0042] It should be understood that Figure 1 This is an example of a communication system in an embodiment of the present application. The embodiment of the present application is not limited to Figure 1 shown.

[0043] As an example, the communication system to which the embodiments of the present application are applicable may include at least a plurality of network devices under the first communication system and / or a plurality of network devices under the second communication system.

[0044] For example, Figure 1The system 100 shown may include a main network device under a first communication system and at least one auxiliary network device under a second communication system. The at least one auxiliary network device is respectively connected to the one main network device to form multiple connections, and is respectively connected to the terminal device 110 to provide services for it. Specifically, the terminal device 110 can establish a connection through the main network device and the auxiliary network device at the same time.

[0045] Optionally, the connection established between the terminal device 110 and the primary network device is a primary connection, and the connection established between the terminal device 110 and the secondary network device is a secondary connection. The control signaling of the terminal device 110 can be transmitted through the primary connection, and the data of the terminal device 110 can be transmitted through the primary connection and the secondary connection at the same time, or can be transmitted only through the secondary connection.

[0046] As another example, the first communication system and the second communication system in the embodiment of the present application are different, but the specific categories of the first communication system and the second communication system are not limited.

[0047] For example, the first communication system and the second communication system can be various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), etc.

[0048] exist Figure 1 In the system 100 shown, the first network device 130 is taken as a main network device, and the second network device 120 is taken as an auxiliary network device as an example.

[0049] The first network device 130 may be an LTE network device, and the second network device 120 may be an NR network device. Alternatively, the first network device 130 may be an NR network device, and the second network device 120 may be an LTE network device. Alternatively, both the first network device 130 and the second network device 120 may be NR network devices. Alternatively, the first network device 130 may be a GSM network device, a CDMA network device, etc., and the second network device 120 may also be a GSM network device, a CDMA network device, etc. Alternatively, the first network device 130 may be a macrocell, and the second network device 120 may be a microcell, a picocell, or a femtocell, etc.

[0050] Optionally, the first network device 130 and the second network device 120 may be any access network devices.

[0051] Optionally, the access network device can be a base station (Base Transceiver Station, BTS) in the Global System of Mobilecommunication (GSM) system or Code Division Multiple Access (CDMA), a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (LTE) system.

[0052] Optionally, the access network device may also be a next generation radio access network (NG RAN), or a base station (gNB) in a NR system, or a wireless controller in a cloud radio access network (CRAN), or the access network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, or a network device in a future evolved public land mobile network (PLMN).

[0053] Taking the first network device 130 as an LTE network device and the second network device 120 as an NR network device as an example, the technical solution of the embodiment of the present application can be applied to the wide area long-term evolution (Long Term Evolution, LTE) coverage and the island coverage mode of NR. Optionally, a tight interworking working mode between LTE and NR. Among them, the main application scenarios of 5G include: Enhanced Mobile Broadband (Enhance Mobile Broadband, eMBB), Ultra-Reliable and Low Latency Communication (Ultra-Reliable and Low Latency Communication, URLLC), and massive machine type communication (massive machine type of communication, mMTC). Among them, eMBB aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. Since eMBB may be deployed in different scenarios. For example, indoors, urban areas, rural areas, etc., the differences in their capabilities and needs are also relatively large, so they cannot be generalized, and can be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety assurance, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost of modules and long service life.

[0054] Optionally, the terminal device 110 can be any terminal device. The terminal device can communicate with one or more core networks (Core Network) via a radio access network (Radio Access Network, RAN), and can also be called an access terminal, user equipment (User Equipment, UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. For example, it can be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (Wireless Local Loop, WLL) station, a Personal Digital Assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a terminal device in a 5G network, etc.

[0055] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0056] Figure 2 is a schematic block diagram of an EN-DC network architecture 200 according to an embodiment of the present invention.

[0057] like Figure 2 As shown, the network architecture 200 can be LTE-NR Dual Connectivity (EN-DC). That is, LTE is used as a master node (MN) and NR is used as a secondary node (SN). In other alternative embodiments, MN is also called MeNB and SN is also called SeNB.

[0058] In the embodiment of the present application, the NR network architecture is added to the LTE architecture to form a network architecture 200, such as Figure 2As shown, the network architecture 200 may include MME / S-GW 211, MME / S-GW 212, 5G base station (gNB) 221, gNB 222, evolved Node B (eNB) 231, and eNB 232. Among them, MME / S-GW 211 is connected to gNB 221 and gNB 222 through an S1-U interface, and MME / S-GW 211 is connected to eNB 231 and eNB 232 through an S1 interface. MME / S-GW 212 is connected to gNB 221 and gNB 222 through an S1-U interface, and MME / S-GW 212 is connected to eNB 231 and eNB 232 through an S1 interface. gNB 221 and gNB 222 are connected through X2-U. eNB 231 and eNB 232 are connected through X2. Similarly, eNB231 and gNB 221 are connected via X2. gNB 222 and eNB 232 are connected via X2. In other words, eNBs are directly interconnected using the X2 interface, and eNBs are connected to EPC via the S1 interface. The S1 interface supports many-to-many connections between MME / S-GW and eNBs, that is, one eNB can be connected to multiple MME / S-GWs, and multiple eNBs can also be connected to the same MME / S-GW at the same time. Similarly, gNBs are directly interconnected using the X2-U interface, and gNBs are connected to EPC via the S1-U interface. The S1-U interface supports many-to-many connections between MME / S-GW and gNBs, that is, one gNB can be connected to multiple MME / S-GWs, and multiple gNBs can also be connected to the same MME / S-GW at the same time.

[0059] like Figure 2 As shown, in the embodiment of the present application, MME / S-GW 211 and MME / S-GW 212 belong to the Evolved Packet Core (EPC) of the LTE network, and gNB 221, gNB 222, eNB 231 and eNB 232 constitute an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). However, the embodiment of the present application is not limited thereto, for example, the MME / S-GW 211 and MME / S-GW 212 can be replaced by any core network device that communicates with an access network device.

[0060] Optionally, the core network device may be a 5G core network device, such as an Access and Mobility Management Function (AMF), or a Session Management Function (SMF). Optionally, the core network device may also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF + PGW-C) device.

[0061] It should be understood that SMF+PGW-C can simultaneously implement the functions that SMF and PGW-C can implement.

[0062] Optionally, in an embodiment of the present application, AMF may exchange information with SMF, for example, SMF obtains some information on the wireless access network side from AMF.

[0063] Figure 3 and Figure 4 They are Figure 2 An example of a specific scenario for EN-DC is shown.

[0064] like Figure 3 As shown, in one scenario, MN and SN have S1-U connections with the Evolved Packet Core network (EPC), or SN and MN are connected to EPC through S1-U interfaces. For example, MN can be a Long Term Evolution (LTE) Evolved Node B (eNB), and SN is a 5G base station (gNB). S1-C on the control plane terminates at LTE eNB). After the data flow is split in the core network, it is transmitted independently via MN and SN, and SN plays a role in load sharing. This architecture can also be called 3a mode or scenario 3A. In this mode, there are no special requirements for the backhaul between base stations, and the layer 2 protocol layer does not need to be specially configured. There is no load sharing function between base stations, and its peak rate depends entirely on the wireless capabilities of MN and SN themselves; in addition, the core network needs to participate in the switching process, and there is a problem of possible data interruption.

[0065] like Figure 4As shown in the figure, in another scenario, the MN has an S1-U connection with the Evolved Packet Core network (EPC), or the MN is connected to the EPC through the S1-U interface. For example, the MN can be an Evolved Node B (eNB) of Long Term Evolution (LTE), and the SN is a 5G base station (gNB). On the control plane, S1-C terminates at the LTE eNB. All downlink data flows are first transmitted to the MN, and then the MN divides them according to a certain algorithm and ratio, and then sends part of the data to the SN through the X2 interface, and finally sends data to the UE on the MN and SN at the same time. This architecture can also be called mode 3 or scenario 3. In this way, the user obtains downlink data from two systems, which is convenient for realizing load sharing and resource coordination functions, and is also conducive to improving user speed. In addition, the switching process has little impact on the core network, and because there are multiple wireless links, the switching delay is low. Its disadvantages are that it has high requirements for the backhaul between base stations, high requirements for the complexity of the layer 2 protocol, and the backhaul between base stations needs to implement functions such as flow control. In addition, the split bearer mode is only applicable to the downlink direction. In the uplink direction, the data flow is not split and can be transmitted via the MN or the SN.

[0066] In addition, in a dual-connection network architecture (such as network architecture 200), the data wireless bearer can be independently served by the MN or the SN, or can be served by both the MN and the SN at the same time. When it is served only by the MN, it is called an MCG bearer, that is, a service cell group controlled by the MN; when it is served only by the SN, it is called an SCG bearer, that is, a service cell group controlled by the SN; when it is served by both the MN and the SN at the same time, it is called a split bearer, also known as a forked bearer. Specifically, it can be divided into MCG split bearer and SCG split bearer. The difference between the MCG split bearer and the SCG split bearer is mainly in the different functions of the Packet Data Convergence Protocol (PDCP) layer and the different keys of the PDCP layer.

[0067] Figure 5 yes Figure 2 The schematic structural diagram of the load under the EN-DC system is shown.

[0068] like Figure 5As shown, the bearers of the terminal device under DC may include: MCG bearer with termination point at MN (MN terminated MCG bearer), forked bearer with termination point at MN (MN terminated split bearer), SCG bearer with termination point at MN (MN terminated SCG bearer), MCG bearer with termination point at SN (SN terminatedMCG bearer), forked bearer with termination point at SN (SN terminated split bearer) and SCG bearer with termination point at SN (SN terminated SCG bearer).

[0069] In other words, the bearer can be divided into a bearer with an endpoint at the MN or SN based on whether the Packet Data Convergence Protocol (PDCP) the bearer passes through is located at the MN or SN, and can also be divided into an MCG bearer or an SCG bearer based on the Radio Link Control (RLC) the bearer passes through.

[0070] Among them, the MCG bearer, SCG bearer and split bearer served by the MN and / or SN pass through the corresponding Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control (RLC) or New Radio (NR) RLC layer to reach the corresponding E-UTRA or NR Media Access Control (MAC) layer. Optionally, the split bearer with the termination point at the MN and the split bearer with the termination point at the SN can be collectively referred to as a split bearer. Optionally, the split bearer can also be called a split bearer.

[0071] It should be understood that each sublayer can send data to the designated layer of the receiving end according to the different data of the protocol data unit. The data that enters each sublayer without being processed is called the service data unit (SDU), and the data in a specific format after being processed by the sublayer is called the protocol data unit (PDU). SDU is an information unit transmitted from the high-level protocol to the low-level protocol. The original data of SDU is the PDU of the upper layer of the protocol. In other words, the PDU formed by this layer is the SDU of the next layer.

[0072] For example, each logical channel of each terminal device has an RLC entity. The data received by the RLC entity from the PDCP layer or sent to the PDCP layer can be called RLC SDU (or PDCP PDU). The data received by the RLC entity from the MAC layer or sent to the MAC layer can be called RLC PDU (or MAC SDU).

[0073] For example, in the embodiment of the present application, the RLC layer is located between the PDCP layer and the MAC layer, and the RLC layer can communicate with the PDCP layer through a service access point (SAP) and communicate with the MAC layer through a logical channel. However, the embodiment of the present application is not limited thereto.

[0074] It should be noted that Figures 1 to 5 This is only an example of the present application and should not be construed as limiting the present application.

[0075] For example, Figure 2 The network architecture 200 shown is only an exemplary description of a dual-connection (DC) network architecture, and the embodiments of the present invention are not limited thereto. For example, in other alternative embodiments, the network architecture 200 may also be simply deformed. For example, as an example, the MN and SN may not be connected to the EPC core network, but to the 5GC core network, that is, the DC network framework under the 5GC core network. Exemplarily, the DC network architecture includes but is not limited to: NE-DC, 5GC-EN-DC, and NR DC. In NE-DC, NR acts as an MN node, eLTE acts as an SN node, and MN and SN are respectively connected to the 5GC core network. In 5GC-EN-DC, eLTE acts as an MN node, NR acts as an SN node, and MN and SN are respectively connected to the 5GC core network. In NR DC, NR acts as an MN node, NR acts as an SN node, and MN and SN are respectively connected to the 5GC core network.

[0076] Figure 6 It is a schematic block diagram of DC bearer under the 5GC core network provided in an embodiment of the present application.

[0077] like Figure 6As shown, the bearer of the terminal device under DC may also include: MCG bearer with termination point at MN (MN terminated MCG bearer), forked bearer with termination point at MN (MN terminated split bearer), SCG bearer with termination point at MN (MN terminated SCG bearer), MCG bearer with termination point at SN (SN terminatedMCG bearer), forked bearer with termination point at SN (SN terminated split bearer) and SCG bearer with termination point at SN (SN terminated SCG bearer).

[0078] Among them, MN and SN are connected to the 5GC core network respectively, MN is connected to SN through the Xn interface, MN and SN can respectively receive the quality of service (QoS) flow sent by the 5GC core network, and the QoS flow can be carried on the corresponding bearer after passing the service data adaptation protocol (SDAP). The MCG bearer, SCG bearer and split bearer served by MN and / or SN pass through the corresponding MN RLC layer or SNRLC layer and reach the corresponding MN MAC layer or NR MAC layer.

[0079] In the embodiment of the present application, the bearer with the termination point at MN may also be referred to as an MN-terminated bearer, and the bearer with the termination point at SN may also be referred to as an SN-terminated bearer.

[0080] In a Multi-RAT Dual Connectivity (MR-DC) scenario, the bearer types from the perspective of the UE side and the network side may include: dividing the bearer into an MN-terminated bearer and an SN-terminated bearer from the node where the PDCP is located.

[0081] From the perspective of wireless resources used, it is divided into: MCG bearer, SCG bearer and split bearer.

[0082] Each DRB is an MCG, SCG or split bearer terminated by the MN or SN.

[0083] The network side configures the key used for each DRB, namely the master key or secondary key.

[0084] In order to reduce air interface signaling and quickly restore wireless connections and data services in the 5G network environment, a new Radio Resource Control (RRC) state is defined, namely the RRC_INACTIVE state. This state is different from the RRC_IDLE and RRC_CONNECTED states.

[0085] In the RRC_IDLE state: mobility is based on the cell selection reselection of the terminal device, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no terminal device access stratum (AS) context on the base station side, and there is no RRC connection.

[0086] In the RRC_CONNECTED state: an RRC connection exists, and a terminal device AS context exists between the base station and the terminal device. The network device knows the location of the terminal device at the specific cell level. Mobility is mobility controlled by the network device. Unicast data can be transmitted between the terminal device and the base station.

[0087] RRC_INACTIVE: Mobility is based on cell selection reselection of the terminal device. There is a connection between CN and NR. The AS context of the terminal device exists on a certain base station. Paging is triggered by the Radio Access Network (RAN). The RAN-based paging area is managed by the RAN. The network equipment knows the location of the terminal device based on the RAN paging area level.

[0088] It should be noted that in the embodiments of the present application, the non-activated state may also be referred to as the deactivated state, and the present application does not limit this.

[0089] The network device can control the state transition of the terminal device, for example Figure 7 As shown, a terminal device in the RRC_CONNECTED state can enter the RRC_IDLE state by releasing the RRC connection; a terminal device in the RRC_IDLE state can enter the RRC_CONNECTED state by establishing an RRC connection; a UE in the RRC_CONNECTED state can enter the RRC_INACTIVE state by suspending (Release with Suspend) the RRC connection; a UE in the RRC_INACTIVE state can enter the RRC_CONNECTED state by resuming (Resume) the RRC connection, and can also enter the RRC_IDLE state by releasing the RRC connection.

[0090] It should be noted that the terminal device is in the RRC_INACTIVE state. The terminal device returns to the idle state autonomously in the following situations:

[0091] When receiving the CN initial paging message;

[0092] When initiating an RRC recovery request, start timer T319. If the timer times out;

[0093] When the integrity protection verification of contention-based random access message 4 (Message 4, MSG4) fails;

[0094] When the cell reselects to another radio access technology (Radio Access Technology, RAT);

[0095] Enter the camp on any cell state.

[0096] Characteristics of the RRC_INACTIVE state:

[0097] The connection between RAN and CN is maintained;

[0098] The terminal device and at least one gNB store the AS context;

[0099] The terminal device is reachable to the RAN side, and the relevant parameters are configured by the RAN;

[0100] When the terminal device moves within the RAN Notification area (RNA) configured by the RAN, it does not need to notify the network side (core network equipment), but when it moves out of the RNA, it needs to notify the network side (core network equipment);

[0101] The UE moves within the RNA according to the cell selection and reselection method.

[0102] It should be noted that RNA can be specifically Figure 8 As shown, in Figure 8 In the RNA shown, the terminal device does not need to notify the network side when it moves between base station 1 and base station 5, but needs to notify the network side when the terminal device moves to base station 6 or base station 7.

[0103] When the terminal device is in the RRC_INACTIVE state, the network device will configure the RRC_INACTIVE configuration parameters for the terminal device through the RRC Release dedicated signaling, for example, configure RNA. RNA is used to control the area where the terminal device performs cell selection reselection in the inactive state, which is also the initial paging range area of ​​the RAN.

[0104] When the terminal device moves within the RNA area, it does not need to notify the network side and follows the mobility behavior in the idle state, that is, the cell selection and reselection principle. When the terminal device moves out of the paging area configured by the RAN, it will trigger the terminal device to restore the RRC connection and reacquire the paging area configured by the RAN. When downlink data arrives at the terminal device, the gNB that maintains the connection between the RAN and CN for the terminal device will trigger all cells in the RAN paging area to send a paging message to the terminal device, so that the terminal device in the INACTIVE state can restore the RRC connection and receive data. The terminal device in the INACTIVE state is configured with a RAN paging area. In order to ensure the reachability of the terminal device within this area, the terminal device needs to perform periodic location updates according to the period configured by the network.

[0105] Therefore, the scenarios that trigger the terminal device to perform RNA update include RAN Notification Area Update (RNAU) timer expiration or UE moving to an area outside the RNA.

[0106] It should be noted that when the target base station for the terminal device to initiate the RRC connection recovery process is not the anchor base station, the anchor base station determines whether the context of the terminal device needs to be transferred to the target base station. Therefore, the target base station generally sends the cause value (cause) carried in the RRC connection recovery request message initiated by the terminal device to the anchor base station during the terminal device context request process, and the anchor base station determines whether the context of the terminal device needs to be transferred to the target base station. For example, periodic RAN location updates generally do not require context transfer.

[0107] For example, Fig. 9 As shown, RNAU with context migration is implemented by the process described in S11 to S19 below.

[0108] S11. The terminal device (UE) sends an RRC connection resumption request (Resume Request) to the target base station (gNB), and the RRC connection resumption request is used for RNA update;

[0109] S12. The target base station sends a RETRIEVE UE CONTEXT REQUEST to the anchor base station (also referred to as the last serving base station (Last ServinggNB));

[0110] S13. The anchor base station sends a RETRIEVE UE CONTEXTRESPONSE response to the target base station;

[0111] S14. Set the UE to an inactive state (Send UE to INACTIVE);

[0112] S15. The target base station sends a data forwarding address indication (DATA FORWARDING ADDRESS INDICATION) to the anchor base station (optionally);

[0113] S16. The target base station sends a path switching request to the access and mobility management function (Access and Mobility Management Function, AMF) entity;

[0114] S17. The AMF entity sends a path switching response to the target base station;

[0115] S18. The target base station sends an RRC release message to the terminal device;

[0116] S19. The target base station sends a UE context release message to the anchor base station.

[0117] For example, Fig.10 As shown, RNAU without context migration is implemented by the process described in S21 to S24 below.

[0118] S21. The terminal device (UE) sends an RRC connection resumption request (Resume Request) to the target base station (gNB), and the RRC connection resumption request is used for RNA update;

[0119] S22. The target base station sends a RETRIEVE UE CONTEXT REQUEST to the anchor base station (also referred to as the last serving base station (Last ServinggNB));

[0120] S23. The anchor base station sends a RETRIEVE UE CONTEXT FAILURE message to the target base station.

[0121] S24. The target base station sends an RRC release message to the terminal device.

[0122] In LTE, early data transmission (EDT) is introduced. During this process, the terminal device may always remain in an idle state, a suspended state, or an inactive state to complete the transmission of uplink and / or downlink small data packets. For example, Fig.11 As shown, the user plane data transmission solution can be specifically implemented by the process described in the following S31 to S38.

[0123] S31. The UE sends an RRC connection resumption request (Resume Request) to the eNB, where the RRC connection resumption request includes uplink data (i.e., small data transmission) sent by the UE;

[0124] S32. The eNB sends a UE CONTEXT RESUME REQUEST to the Mobility Management Entity (MME);

[0125] S33. Modify the bearer between MME and Serving Gateway (SGW);

[0126] S34.MME sends a UE CONTEXT RESUME RESPONSE to the eNB;

[0127] S35. The eNB sends the uplink data sent by the UE to the SGW (ie, small data transmission);

[0128] S36. The SGW receives the downlink data sent by the eNB (optionally);

[0129] S37 suspends the process between eNB and SGW, and modifies the bearer between MME and SGW;

[0130] S38. The eNB sends an RRC connection release message to the UE. Optionally, the RRC connection release message includes downlink data.

[0131] At the same time, the R17 DCCA enhancement topic introduces the concept of SCG deactivation, that is, the transmission on the SCG side will be suspended even if the UE is in the RRC connection state. The introduction of SCG deactivation is mainly for the purpose of UE energy saving. Therefore, a data transmission configuration method and a key configuration method in the MR-DC scenario are required, so that the data transmission in the MR-DC scenario does not activate the SCG side wireless resources as much as possible, thereby achieving the purpose of energy saving of the UE during small data transmission.

[0132] It should be understood that the embodiments of the present application can be applicable to small data transmission scenarios, and of course can also be applicable to normal data transmission scenarios, and the present application is not limited to this.

[0133] It should also be understood that the embodiments of the present application can be applied to MR-DC scenarios, or can also be applied to other dual-connection or multi-connection scenarios described in the aforementioned embodiments, and the present application is not limited thereto.

[0134] First combine Fig.12 A method for configuring data transmission in an MR-DC scenario is described, which is referred to as Embodiment 1.

[0135] Embodiment 1

[0136] Fig.12 4 is a schematic interactive diagram of a data transmission method 400 provided in an embodiment of the present application. Fig.12 As shown, the method 400 includes at least part of the following.

[0137] S401, a terminal device receives first configuration information, where the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB;

[0138] S402: The terminal device performs small data transmission according to the first configuration information.

[0139] Optionally, the first configuration information may be configured by a first node, and the first node may be a master node (MN) or a secondary node (SN). Figure 2 Any one of the 5G base stations (gNB) 221, gNB 222, evolved Node B (eNB) 231, and eNB 232 shown in FIG. The terminal device may be as follows Figure 1 The terminal device shown.

[0140] In some embodiments, when the terminal device is in a connected state, the first node may configure the first configuration information to the terminal device via a downlink message. As an example, the downlink message may be RRC signaling.

[0141] The first configuration information may be used to configure a DRB that is capable of performing small data transmission when the terminal device is in an inactive state, or a DRB that is not capable of performing small data transmission when the terminal device is in an inactive state.

[0142] Optionally, in the embodiment of the present application, the DRB may include the following types:

[0143] MN terminated MCG bearer, MN terminated split bearer, MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer, SN terminated SCG bearer.

[0144] Example 1: The first configuration information is used to configure the DRB that can be used for small data transmission when the terminal device is in an inactive state, including: MN terminated MCG bearer. That is, only MN terminated MCG bearer can be used for small data transmission when the UE is in an inactive state.

[0145] Example 2: The first configuration information is used to configure the DRB that can be used for small data transmission when the terminal device is in an inactive state, including: MN terminated MCG bearer and SN terminated MCG bearer, that is, only the MCG bearer can be used for small data transmission when the UE is in an inactive state.

[0146] Example 3: The first configuration information is used to configure DRBs that can be used for small data transmission when the terminal device is in an inactive state, including: MN terminated MCG bearer, MN terminated split bearer, SNterminated MCG bearer and SN terminated split bearer. That is, only the SCG bearer cannot be used for small data transmission when the UE is in an inactive state.

[0147] The embodiment of the present application does not limit the presentation form of the first configuration information, and may be in a table form, as shown in Table 1 as an example.

[0148] Table 1

[0149] DRB Option 1 Option 2 Option 3 MN terminated MCG bearer 1 1 1 MN terminated split bearer 1 0 0 MN terminated SCG bearer 0 0 0 SN terminated MCG bearer 1 1 0 SN terminated split bearer 1 0 0 SN terminated SCG bearer 0 0 0

[0150] Among them, "1" indicates that the corresponding bearer can be used for small data transmission, and "0" indicates that the corresponding bearer cannot be used for small data transmission.

[0151] Option 1 may correspond to Example 3, Option 2 may correspond to Example 2, and Option 3 may correspond to Example 1.

[0152] For DRBs that are not configured to transmit small data, when small data arrives, the terminal device needs to enter the connected state to transmit the data.

[0153] In some embodiments, if the configured split bearer can be used for small data transmission, in order not to activate the wireless resources on the SCG side, in an embodiment of the present application, the first configuration information can also be used to configure the path, or leg, activated when using the split bearer for small data transmission.

[0154] For example, for MN terminated split bearer and SN terminated split bearer, the path activated when performing small data transmission can be configured as MCG path, that is, MCG leg. In this way, when using split bearer for small data transmission, SCG path can be deactivated, and the radio resources on the SCG side can also be deactivated.

[0155] For option 1, information about the activated path for small data transmission may be further configured, as shown in Table 2 below.

[0156] Table 2

[0157]

[0158]

[0159] Combination Fig.13 The following describes a method for configuring a key in an MR-DC scenario, which is referred to as Embodiment 2.

[0160] Embodiment 2

[0161] Fig.13 FIG. 5 is a schematic diagram of a data transmission method 500 provided in another embodiment of the present application. Fig.13 As shown, the method 500 includes at least part of the following.

[0162] S501, when specific conditions are met, the terminal device generates an SCG key according to the main cell group MCG key and the secondary cell group SCG count value, and the SCG key is used for encryption and decryption of the small data.

[0163] In the second embodiment, in order to support the transmission of small data on the SN-terminated bearer, a corresponding key configuration method is designed.

[0164] Optionally, in some embodiments, the MCG key is a master key before the terminal device initiates small data transmission, or a master key updated by triggering small data transmission.

[0165] For uplink small data transmission, the SCG key can be used for encryption of uplink small data.

[0166] For example, when small uplink data arrives, or uplink data arrives, or uplink data arrives at the SN-terminated PDCP entity or small uplink data arrives at the bearer associated with the "secondary" key, the terminal device can generate the SCG key based on the MCG key and the SCG count value.

[0167] For downlink small data transmission, the SCG key can be used for decryption of the downlink small data.

[0168] For example, when small downlink data arrives at the bearer terminated by the SN, the SN can send a first message to the MN, where the first message is used to trigger the MN to page the terminal device, and further carry instructions related to small data transmission and / or key generation in the paging message.

[0169] Optionally, in some embodiments, the first message includes at least one of the following:

[0170] Small data arrival indication, used to indicate whether small data has arrived;

[0171] SCG key derivation indication, used to indicate whether to generate SCG key;

[0172] List of DRB IDs where small data arrives.

[0173] Optionally, in some embodiments, the paging message includes at least one of the following:

[0174] Small data arrival indication, used to indicate whether small data has arrived;

[0175] SCG key derivation indication, used to indicate whether to generate SCG key;

[0176] List of DRB IDs where small data arrives.

[0177] Optionally, in some embodiments, the terminal device may generate the SCG key according to the MCG key and the SCG count value upon receiving the paging message, regardless of whether the paging message indicates the generation of the SCG key.

[0178] Optionally, in some other embodiments, the terminal device may generate the SCG key according to the MCG key and the SCG count value when receiving the paging message indicating the arrival of downlink data, or the arrival of small downlink data, or the arrival of small downlink data at the SN terminated bearer, regardless of whether the paging message indicates the generation of the SCG key.

[0179] Optionally, in some further embodiments, the terminal device may generate the SCG key according to the MCG key and the SCG count value upon receiving the paging message indicating that the SCG key has been generated, regardless of whether the paging message indicates that the SCG key has been generated.

[0180] Optionally, in some embodiments, the SCG count value is configured by a radio resource control RRC release message.

[0181] Combination Figures 14 to 25 The data transmission method on the SCG bearer terminated by the SN in the MR-DC scenario is described as Embodiment 3. There are two scenarios: a downlink data arrival scenario and an uplink data arrival scenario.

[0182] It should be understood that the third embodiment can be implemented independently, that is, when small data arrives at the SCG bearer terminated by the SN, the small data transmission on the SCG bearer without using SCG resources is realized through the cooperation between the terminal device, SN and MN. Alternatively, the third embodiment can also be implemented in combination with other embodiments. For example, the third embodiment can be a case where the first configuration information in the first embodiment configures the SCG bearer terminated by the SN to be able to perform small data transmission, and the small data transmission on the SCG bearer without using SCG resources is realized through the cooperation between the terminal device, SN and MN.

[0183] Optionally, in some embodiments, the first configuration information may also be used to configure the data transmission method in Embodiment 3. Thus, the terminal device may implement small data transmission without activating SCG resources when small data arrives at the SCG bearer terminated by the SN based on the first configuration information.

[0184] Combination Figures 14 to 23 Describe the technical solution for the downlink data arrival scenario.

[0185] Fig.14 FIG. 6 is a schematic interactive diagram of a data transmission method 600 provided in another embodiment of the present application. Fig.14 As shown, the method 600 includes at least part of the following.

[0186] S601, when small downlink data arrives on the first secondary cell group SCG bearer terminated on the secondary node SN, the SN sends information about the small downlink data to the primary node MN,

[0187] S602, the MN generates a first media access control MAC protocol data unit PDU according to the information of the downlink small data, where the first MAC PDU includes an RLC PDU or a PDCP PDU corresponding to the downlink small data from the SN;

[0188] S603: The MN sends the first MAC PDU to the terminal device.

[0189] Correspondingly, the terminal device receives the first MAC PDU sent by the MN.

[0190] Optionally, in some embodiments, the MN and SN may be Figure 2Any two of the 5G base stations (gNB) 221, gNB 222, evolved Node B (eNB) 231, and eNB 232 shown in FIG. The terminal device may be as follows Figure 1 The terminal device shown.

[0191] Optionally, in some embodiments, the downlink small data information includes at least one of the following:

[0192] The radio link control RLC PDU or PDCP PDU corresponding to the downlink small data;

[0193] A logical channel identifier (Logic Channel Identify, LCID) to which the downlink small data belongs;

[0194] The DRB ID to which the downlink small data belongs;

[0195] Quality of Service (QoS) parameters corresponding to the downlink small data.

[0196] Combination Fig.15 Describe the specific implementation process.

[0197] like Fig.15 As shown, when the downlink small data arrives at the first SCG bearer, the SN may generate an RLC PDU or a PDCP PDU on the first SCG bearer, and further may send the RLC PDU or the PDCP PDU corresponding to the downlink small data and / or the configuration corresponding to the downlink small data to the MN, and the configuration of the downlink small data may include at least one of the following:

[0198] The LCID to which the downlink small data belongs;

[0199] The DRB ID to which the downlink small data belongs, that is, the DRB ID carried by the first SCG;

[0200] The QoS parameters corresponding to the downlink small data.

[0201] The configuration of the downlink small data may be used by the MN to generate a corresponding MAC PDU.

[0202] In some embodiments, the information of the downlink small data can be sent through interface signaling between network devices, such as Xn interface signaling, or can be sent to the MN through an RRC Transfer message. When the RRC Transfer message is used to carry the above information, the RLC PDU or PDCP PDU corresponding to the downlink small data is included in the RRC Transfer message in the form of a container.

[0203] After the MAC entity of the MN receives the information of the downlink small data sent by the SN, it can generate a first MAC PDU according to the RLC PDU or PDCP PDU corresponding to the downlink small data. In some embodiments, the RLC PDU or PDCP PDU corresponding to the downlink small data and the message carried in the common control channel (CCCH) can be multiplexed in the first MAC PDU. That is, the MN can generate the first MAC PDU according to the RLC PDU or PDCP PDU and the message in the CCCH.

[0204] In some embodiments, the first MAC PDU may include first indication information for indicating that the downlink small data comes from the first SCG bearer, that is, the first MAC PDU includes data from the SCG bearer.

[0205] In some embodiments, the first indication information is carried in a header of a first MAC SDU in the first MAC PDU, wherein the first MAC SDU is a MAC SDU in the first MAC PDU used to carry an RLC PDU or a PDCP PDU. For example, the first indication information is carried in a reserved (R) field in a header of the first MAC SDU.

[0206] Figure 16-Figure 22 Several typical MAC SDU header formats are shown. For example, the R field value can be set to 0 to indicate that the data in the MAC SDU comes from the MCG bearer, and the value can be set to 1 to indicate that it comes from the SCG side bearer, or vice versa.

[0207] Optionally, the LCID in the header of the first MAC SDU can be generated according to the LCID corresponding to the downlink small data.

[0208] After MN generates the first MAC PDU, it can submit the first MAC PDU to the physical layer of the MN and further send it to the terminal device. After the MCG MAC entity of the terminal device receives the first MAC PDU, it can decode the first MAC PDU. The method for determining the key used for decoding can refer to the relevant description in Example 2.

[0209] After decoding the first MAC PDU, obtain the first indication information in the first MAC SDU in the first MAC PDU, and determine whether the data in the first MAC SDU comes from the SCG bearer. If it is determined to be from the SCG bearer, the MCG MAC entity of the terminal device can send the LCID corresponding to the first MAC SDU and / or the downlink small data to the SCG MAC entity of the terminal device.

[0210] Further, the SCG MAC entity of the terminal device may deliver the received first MAC SDU to a higher layer. Specifically, the SCG MAC entity of the terminal device may decode the first MAC SDU according to the LCID corresponding to the downlink small data, and deliver the decoded data to a higher layer of the terminal device.

[0211] It should be understood that in the embodiment of the present application, the MCG MAC entity of the terminal device may refer to the MAC entity of the terminal device on the MN side, the SCG MAC entity of the terminal device may refer to the MAC entity of the terminal device on the SN side, and the terminal device may correspond to corresponding MAC entities on the MN side and the SN side respectively.

[0212] Combination Fig.23 and Fig.24 Explain the technical solution for the scenario where small uplink data arrives

[0213] Fig.23 FIG. 7 is a schematic interactive diagram of a data transmission method 700 provided in another embodiment of the present application. Fig.23 As shown, the method 700 includes at least part of the following.

[0214] S701, when small uplink data arrives on a second secondary cell group SCG bearer terminated on the secondary node SN, the terminal device sends a second MAC PDU to the primary node MN, where the second MAC PDU includes an RLC PDU or a PDCP PDU corresponding to the small uplink data;

[0215] S702, the MN decodes the second MAC PDU, and sends a second MAC SDU carrying the RLC PDU or PDCP PDU corresponding to the uplink small data in the second MAC PDU to the SN;

[0216] S703: The SN decodes the second MAC SDU.

[0217] Further optionally, the SN delivers the decoded data to the core network side, such as a UPF entity.

[0218] Optionally, in some embodiments, the MN and SN may be Figure 2 Any two of the 5G base stations (gNB) 221, gNB 222, evolved Node B (eNB) 231, and eNB 232 shown in FIG. The terminal device may be as follows Figure 1 The terminal device shown.

[0219] Combination Fig.24 Describe the specific implementation process.

[0220] like Fig.24 As shown, when the uplink small data arrives at the second SCG bearer, the terminal device can generate an RLC PDU or PDCP PDU on the second SCG bearer, and further send the RLC PDU or PDCP PDU corresponding to the uplink small data and / or the configuration corresponding to the downlink small data to the MCG MAC entity of the terminal device, and the configuration of the downlink small data may include at least one of the following:

[0221] The LCID to which the uplink small data belongs;

[0222] The DRB ID to which the uplink small data belongs, that is, the DRB ID carried by the first SCG;

[0223] The QoS parameters corresponding to the uplink small data.

[0224] After receiving the above information, the MCG MAC entity of the terminal device can generate a second MAC PDU according to the above information, wherein the second MAC PDU includes the RLC PDU or PDCP PDU corresponding to the uplink small data.

[0225] In some embodiments, the RLC PDU or PDCP PDU corresponding to the uplink small data and the message carried in the CCCH (e.g., RRC message) can be multiplexed in the second MAC PDU. That is, the MCG MAC entity of the terminal device can generate the second MAC PDU based on the RLC PDU or PDCP PDU and the message in the CCCH.

[0226] Optionally, in some embodiments, the second MAC PDU may include second indication information for indicating that the uplink small data comes from the SCG bearer, that is, the second MAC PDU includes data from the SCG bearer.

[0227] In some embodiments, the second indication information is carried in a header of a second MAC SDU in the second MAC PDU, and the second MAC SDU is a MAC SDU in the second MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data.

[0228] In some embodiments, the second indication information is carried in the header of the second MAC SDU, such as the R field of the second MAC SDU.

[0229] Figures 16 to 22 Several typical MAC SDU header formats are shown. For example, the R field value can be set to 0 to indicate that the data comes from the MCG bearer, and the value can be set to 1 to indicate that the data comes from the SCG side bearer, or vice versa.

[0230] Optionally, the LCID in the header of the second MAC SDU can be generated according to the LCID corresponding to the uplink small data.

[0231] After the MCG MAC entity of the terminal device generates the second MAC PDU, it can submit the second MAC PDU to the physical layer and further send it to the MN. After the MAC entity of the MN receives the second MAC PDU, it can decode the second MAC PDU.

[0232] After decoding the second MAC PDU, obtain the second indication information in the second MAC SDU in the second MAC PDU, and determine whether the data in the second MAC SDU comes from the SCG bearer. If it comes from the SCG bearer, the MAC entity of the MN can send the second MAC SDU and / or the LCID corresponding to the uplink small data to the SN.

[0233] In some embodiments, the second MAC SDU and / or the LCID corresponding to the uplink small data may be sent via interface signaling between network devices, such as Xn interface signaling, or may be sent to the MN via an RRC Transfer message. When the RRC Transfer message is used to carry the above message, the RLC PDU or PDCP PDU corresponding to the uplink small data is included in the RRC Transfer message in the form of a container.

[0234] Furthermore, after the SN receives the second MAC SDU and / or the LCID corresponding to the uplink small data, it can decode the second MAC SDU according to the LCID corresponding to the uplink small data, and further submit the decoding result to the core network side, such as the UPF entity.

[0235] In summary, when small data arrives at the bearer terminated by SN, the small data to be transmitted is forwarded by MN, thereby transmitting the small data to be transmitted to the target end without activating the wireless resources on the SCG side, thereby achieving the node purpose of UE in small data transmission.

[0236] It should be understood that the above-mentioned Embodiment 1, Embodiment 2 and Embodiment 3 may be implemented separately or in combination with each other, and this application does not make any reference to this.

[0237] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.

[0238] Combination of the above Figures 12 to 24 , describes in detail the method embodiment of the present application, and the following is combined with Figure 25 to Figure 29 , describe in detail the device embodiments of the present application.

[0239] Fig.25 FIG. 8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application. Fig.25 As shown, the terminal device 800 includes:

[0240] The communication unit 810 is configured to receive first configuration information, where the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB; and

[0241] Small data transmission is performed according to the first configuration information.

[0242] Optionally, in some embodiments, the first configuration information is used to configure a wireless data bearer DRB that can be used for small data transmission and / or a DRB that cannot be used for small data transmission.

[0243] Optionally, in some embodiments, the DRB that can be used for small data transmission includes: a primary cell group MCG bearer whose termination point is a primary node MN.

[0244] Optionally, in some embodiments, the DRB that can be used for small data transmission includes: an MCG bearer with a termination point at the MN; an MCG bearer with a termination point at the secondary node SN.

[0245] Optionally, the DRB that can be used for small data transmission includes: an MCG bearer with a termination point at the MN; a split bearer with a termination point at the MN; an MCG bearer with a termination point at the SN; and a split bearer with a termination point at the SN.

[0246] Optionally, in some embodiments, if the DRB that can be used for small data transmission includes a split bearer, the first configuration information is also used to configure a path activated when the split bearer is used for small data transmission.

[0247] Optionally, in some embodiments, the path activated when using the split bearer for small data transmission is the MCG path corresponding to the split bearer.

[0248] Optionally, the terminal device further includes: a processing unit, configured to generate an SCG key based on the MCG key and the SCG count value when specific conditions are met, wherein the SCG key is used for encryption and decryption of small data.

[0249] Optionally, in some embodiments, the specific condition includes at least one of the following:

[0250] Small data arrives at the Packet Data Convergence Protocol (PDCP) entity of the bearer whose termination point is at the SN;

[0251] Small data arrives at the PDCP entity associated with the secondary key;

[0252] Small uplink data arrives;

[0253] Uplink data arrives;

[0254] receiving a paging message from the MN, the paging message being used to indicate receiving small data or generating the SCG key;

[0255] Receive the paging message from MN.

[0256] Optionally, in some embodiments, the paging message includes at least one of the following: a small data arrival indication, used to indicate whether small data has arrived;

[0257] SCG key derivation indication, used to indicate whether to generate SCG key;

[0258] List of DRB IDs where small data arrives.

[0259] Optionally, in some embodiments, the SCG count value is configured by a radio resource control RRC release message.

[0260] Optionally, in some embodiments, the MCG key is a master key before the terminal device initiates small data transmission, or a master key updated by triggering small data transmission.

[0261] Optionally, in some embodiments, if small downlink data arrives at the first SCG bearer whose endpoint is SN, the communication unit 810 is also used to: receive a first media access control MAC protocol data unit PDU sent by MN, and the first MAC PDU includes an RLC PDU or PDCP PDU corresponding to the small downlink data from the SN.

[0262] Optionally, in some embodiments, the RLC PDU corresponding to the downlink small data and the message carried by the common control channel CCCH are multiplexed in the first MAC PDU; or the PDCP PDU corresponding to the downlink small data and the message carried by CCCH are multiplexed in the first MAC PDU.

[0263] Optionally, the first MAC PDU also includes first indication information and / or a logical channel identifier LCID corresponding to the downlink small data, wherein the first indication information is used to indicate whether the downlink small data comes from an SCG bearer.

[0264] Optionally, in some embodiments, the first indication information is carried in the header of the first MAC service data unit SDU, the LCID corresponding to the downlink small data is carried in the header of the first MAC SDU, the first MAC PDU includes the first MAC SDU, and the first MAC SDU is the MAC SDU in the first MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the downlink small data.

[0265] Optionally, the first indication information is carried in a reserved field in the first MAC SDU.

[0266] Optionally, the terminal device 800 further includes: a processing unit, which determines, at an MCG MAC layer, according to the first indication information in the first MAC PDU, that the data in the first MAC PDU comes from an SCG bearer;

[0267] The communication unit 810 is further used to: send the LCID corresponding to the first MAC SDU and / or the downlink small data to the SCG MAC layer at the MCG MAC layer.

[0268] Optionally, the processing unit is also used to: decode the first MAC SDU according to the LCID corresponding to the downlink small data at the SCG MAC layer, and submit the decoded data to the upper layer of the terminal device.

[0269] Optionally, in some embodiments, if small uplink data arrives at the second SCG bearer whose termination point is SN, the communication unit 810 is also used to: send a second MAC PDU to the MN at the MCG MAC layer, and the second MAC PDU includes the RLC PDU or PDCP PDU corresponding to the small uplink data.

[0270] Optionally, in some embodiments, the RLC PDU corresponding to the uplink small data and the message carried by CCCH are multiplexed in the second MAC PDU; or the PDCP PDU corresponding to the uplink small data and the message carried by CCCH are multiplexed in the second MAC PDU.

[0271] Optionally, in some embodiments, the terminal device 800 further includes:

[0272] A processing unit is used to generate a radio link control RLC PDU from the uplink small data at the SCG RLC layer, and send the RLC PDU to the MCG MAC entity of the terminal device; or to generate a PDCP PDU from the uplink small data at the SCG PDCP layer, and send the PDCP PDU to the MCG MAC entity of the terminal device.

[0273] Optionally, the processing unit is also used to send at least one of the following information to the MCG MAC layer at the SCG RLC layer or the SCG PDCP layer: the LCID corresponding to the uplink small data, the DRB ID carried by the second SGC, and the quality of service QoS parameters of the uplink small data.

[0274] Optionally, in some embodiments, the processing unit is also used to generate the second MAC PDU at the MCG MAC layer according to the RLC PDU and CCCH corresponding to the uplink small data; or to generate the second MAC PDU at the MCG MAC layer according to the PDCP PDU and CCCH corresponding to the uplink small data.

[0275] Optionally, in some embodiments, the second MAC PDU also includes second indication information and / or an LCID corresponding to the uplink small data, wherein the second indication information is used to indicate that the uplink small data comes from an SCG bearer.

[0276] Optionally, in some embodiments, the second indication information is carried in the header of the second MAC SDU, the LCID corresponding to the uplink small data is carried in the header of the second MAC SDU, the second MAC PDU includes the second MAC SDU, and the second MAC SDU is a MAC SDU in the second MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data.

[0277] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0278] It should be understood that the terminal device 800 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 800 are respectively for implementing the corresponding processes of the terminal device in the method embodiment, which will not be repeated here for the sake of brevity.

[0279] Fig.26 is a schematic block diagram of a network node according to an embodiment of the present application. Fig.26 The network node 900 comprises:

[0280] The communication unit 910 is used to send first configuration information to the terminal device, where the first configuration information is used to configure the small data transmission configuration corresponding to the data radio bearer DRB.

[0281] Optionally, in some embodiments, the first configuration information is used to configure a wireless data bearer DRB that can be used for small data transmission and / or a DRB that cannot be used for small data transmission.

[0282] Optionally, the DRB that can be used for small data transmission includes: a primary cell group MCG bearer whose termination point is a primary node MN.

[0283] Optionally, the DRB that can be used for small data transmission includes: an MCG bearer whose termination point is the MN;

[0284] The termination point is the MCG bearer of the secondary node SN.

[0285] Optionally, in some embodiments, the DRB that can be used for small data transmission includes: an MCG bearer with a termination point at the MN; a split bearer with a termination point at the MN; an MCG bearer with a termination point at the SN; and a split bearer with a termination point at the SN.

[0286] Optionally, in some embodiments, if the DRB that can be used for small data transmission includes a split bearer, the first configuration information is also used to configure a path activated when the split bearer is used for small data transmission.

[0287] Optionally, in some embodiments, the path activated when using the split bearer for small data transmission is the MCG path corresponding to the split bearer.

[0288] Optionally, in some embodiments, the first node is a MN.

[0289] Optionally, in some embodiments, the first node is further used to configure an SCG count value for the terminal device, and the SCG count value is used by the terminal device to generate an SCG key for encryption and decryption of the small data based on the MCG key and the SCG count value.

[0290] Optionally, in some embodiments, the communication unit 910 is further configured to:

[0291] receiving a first message from the SN, where the first message is used to trigger the MN to page the terminal device, wherein the SN sends the first message when small downlink data arrives at a bearer of the termination point at the SN;

[0292] According to the first message, a paging message is sent to the terminal device, where the paging message includes relevant indications of small data arrival and / or key generation.

[0293] Optionally, in some embodiments, the first message includes at least one of the following:

[0294] Small data arrival indication, used to indicate whether small data has arrived;

[0295] SCG key derivation indication, used to indicate whether to generate SCG key;

[0296] List of DRB IDs where small data arrives.

[0297] Optionally, in some embodiments, the paging message includes at least one of the following:

[0298] Small data arrival indication, used to indicate whether small data has arrived;

[0299] SCG key derivation indication, used to indicate whether to generate SCG key;

[0300] List of DRB IDs where small data arrives.

[0301] Optionally, in some embodiments, the SCG count value is configured via a radio resource control RRC release message.

[0302] Optionally, in some embodiments, the MCG key is a master key before the terminal device initiates small data transmission, or a master key updated by triggering small data transmission.

[0303] Optionally, in some embodiments, if the downlink small data arrives at the first SCG bearer whose termination point is at the SN, the communication unit is further configured to:

[0304] Receive downlink small data information sent by SN.

[0305] Optionally, in some embodiments, the downlink small data information includes at least one of the following:

[0306] The radio link control RLC PDU or packet data convergence protocol PDCP protocol data unit PDU corresponding to the downlink small data;

[0307] The logical channel identifier LCID to which the downlink small data belongs;

[0308] The DRB ID to which the downlink small data belongs;

[0309] The quality of service QoS parameter corresponding to the downlink small data.

[0310] Optionally, in some embodiments, the downlink small data information is transmitted via Xn interface signaling; or

[0311] The information of the downlink small data is carried by an RRC forwarding message, wherein the RLC PDU or the PDCP PDU is included in the RRC forwarding message in a container manner.

[0312] Optionally, in some embodiments, the communication unit 910 is further configured to:

[0313] A first media access control MAC protocol data unit (PDU) is sent to the terminal device, wherein the first MAC PDU includes an RLC PDU or PDCP PDU corresponding to the downlink small data from the SN.

[0314] Optionally, in some embodiments, the RLC PDU corresponding to the downlink small data and the message carried by the common control channel CCCH are multiplexed in the first MAC PDU; or the PDCP PDU corresponding to the downlink small data and the message carried by CCCH are multiplexed in the first MAC PDU.

[0315] Optionally, the first MAC PDU also includes first indication information and / or a logical channel LCID corresponding to the downlink small data, and the first indication information is used to indicate that the downlink small data comes from an SCG bearer.

[0316] Optionally, in some embodiments, the first indication information is carried in the header of the first MAC service data unit SDU, the LCID corresponding to the downlink small data is carried in the header of the first MAC SDU, the first MAC PDU includes the first MAC SDU, and the first MAC SDU is the MAC SDU in the first MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the downlink small data.

[0317] Optionally, in some embodiments, if the uplink small data arrives at the second SCG bearer of the termination point at the SN, the communication unit 910 is also used to: receive a second MAC PDU sent by the terminal device, and the second MAC PDU includes an RLC PDU or PDCP PDU corresponding to the uplink small data.

[0318] Optionally, in some embodiments, the RLC PDU corresponding to the uplink small data and the message carried by CCCH are multiplexed in the second MAC PDU; or

[0319] The PDCP PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU.

[0320] Optionally, in some embodiments, the second MAC PDU also includes second indication information and / or a logical channel LCID corresponding to the uplink small data, and the second indication information is used to indicate that the uplink small data comes from the second SCG bearer.

[0321] Optionally, in some embodiments, the second indication information is carried in the header of the second MAC SDU, the LCID corresponding to the uplink small data is carried in the header of the second MAC SDU, the second MAC PDU includes the second MAC SDU, and the second MAC SDU is a MAC SDU in the second MAC PDU used to carry the RLCPDU or PDCP PDU corresponding to the uplink small data.

[0322] Optionally, the second indication information is carried in a reserved field in the second MAC SDU.

[0323] Optionally, in some embodiments, the network node 900 further includes:

[0324] a processing unit, configured to determine, according to the second indication information in the second MAC PDU, that the data in the second MAC PDU comes from the SCG bearer;

[0325] The communication unit is also used to: send the LCID corresponding to the second MAC SDU and / or the uplink small data in the second MAC PDU to the SN.

[0326] Optionally, in some embodiments, the second MAC SDU and / or the LCID corresponding to the uplink small data are sent to the SN via Xn interface signaling; or, the second MAC SDU and / or the LCID corresponding to the uplink small data are sent to the SN via an RRC forwarding message.

[0327] Optionally, in some embodiments, the first node is a SN.

[0328] Optionally, in some embodiments, the communication unit 910 is further configured to:

[0329] When downlink data arrives at the termination point on the bearer of the SN, a first message is sent to the MN, where the first message is used to trigger the MN to page the terminal device.

[0330] Optionally, in some embodiments, the first message includes at least one of the following: a small data arrival indication, used to indicate whether small data has arrived;

[0331] SCG key derivation indication, used to indicate whether to generate SCG key;

[0332] List of DRB IDs where small data arrives.

[0333] Optionally, in some embodiments, if the downlink small data arrives at a termination point on the first SCG bearer of the SN, the communication unit is further used to: send information about the downlink small data to the MN.

[0334] Optionally, in some embodiments, the downlink small data information includes at least one of the following:

[0335] The radio link control RLC PDU or PDCP PDU corresponding to the downlink small data;

[0336] The logical channel identifier LCID to which the downlink small data belongs;

[0337] The DRB ID to which the downlink small data belongs;

[0338] The quality of service QoS parameter corresponding to the downlink small data.

[0339] Optionally, in some embodiments, the downlink small data information is transmitted via Xn interface signaling; or

[0340] The information of the downlink small data is carried by an RRC forwarding message, wherein the RLC PDU or PDCP PDU is included in the RRC forwarding message in a container manner.

[0341] Optionally, in some embodiments, if the uplink small data arrives at a termination point on the second SCG bearer of the SN, the communication unit is further configured to:

[0342] Receive the uplink small data information from the terminal device sent by the MN.

[0343] Optionally, in some embodiments, the uplink small data information is sent via Xn interface signaling; or, the uplink small data information is sent via an RRC forwarding message.

[0344] Optionally, in some embodiments, the uplink small data information includes at least one of the following:

[0345] A second MAC SDU corresponding to the uplink small data, wherein the second MAC SDU is used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data;

[0346] The logical channel identifier LCID to which the uplink small data belongs.

[0347] Optionally, in some embodiments, the network node further includes:

[0348] A processing unit, configured to decode the second MAC SDU according to the LCID to which the uplink small data belongs;

[0349] The communication unit is also used to submit the decoding result to the core network.

[0350] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0351] It should be understood that the network node 900 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the network node 900 are respectively for implementing the corresponding processes of SN or MN in the method embodiment. For the sake of brevity, they will not be repeated here.

[0352] Fig. 27 It is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application. Fig. 27 The communication device 1000 shown includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0353] Alternatively, if Fig.28 As shown, the communication device 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0354] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0355] Alternatively, if Fig.28 As shown, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0356] The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0357] Optionally, the communication device 1000 may specifically be a network node of an embodiment of the present application, such as a SN or MN, and the communication device 1000 may implement the corresponding processes implemented by the SN or MN in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0358] Optionally, the communication device 1000 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0359] Fig.28 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.28 The chip 1100 shown includes a processor 1110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0360] Alternatively, if Fig.28 As shown, the chip 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0361] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0362] Optionally, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0363] Optionally, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0364] Optionally, the chip can be applied to the network node in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the SN or MN in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0365] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0366] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0367] Fig.29 1 is a schematic block diagram of a communication system 1200 provided in an embodiment of the present application. Fig.29 As shown, the communication system 900 includes a terminal device 1210 and a network node 1220 .

[0368] Among them, the terminal device 1210 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network node 1220 can be used to implement the corresponding functions implemented by the network device, SN or MN in the above method. For the sake of brevity, they will not be repeated here.

[0369] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0370] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0371] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0372] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0373] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0374] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0375] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0376] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0377] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0378] The embodiment of the present application also provides a computer program.

[0379] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0380] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

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

[0382] 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 aforementioned method embodiments and will not be repeated here.

[0383] In the 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

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

[0387] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A data transmission method, characterized in that: include: The terminal device receives first configuration information, where the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB, the terminal device is in a multi-radio access technology RAT dual-connection MR-DC scenario, and the secondary cell group SCG of the terminal device is deactivated; The terminal device performs small data transmission according to the first configuration information; If downlink small data arrives at the first SCG bearer whose termination point is at the SN, the method further includes: The terminal device receives a first media access control MAC protocol data unit PDU sent by the MN, the first MAC PDU includes an RLC PDU or PDCP PDU corresponding to the downlink small data from the SN, and the first MAC PDU also includes first indication information and a logical channel identifier LCID corresponding to the downlink small data, wherein the first indication information is used to indicate whether the downlink small data comes from an SCG bearer, the first indication information is carried in a header of a first MAC service data unit SDU, the LCID corresponding to the downlink small data is carried in a header of the first MAC SDU, the first MAC PDU includes the first MAC SDU, and the first MAC SDU is a MAC SDU in the first MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the downlink small data; The MCG MAC entity of the terminal device determines, according to the first indication information in the first MAC PDU, that the data in the first MAC PDU comes from the SCG bearer; The MCG MAC entity of the terminal device sends the LCID corresponding to the first MAC SDU and the downlink small data to the SCG MAC entity of the terminal device.

2. The method according to claim 1, characterized in that The first configuration information is used to configure a wireless data bearer DRB that can be used for small data transmission and / or a DRB that cannot be used for small data transmission.

3. The method according to claim 2, characterized in that The DRB that can be used for small data transmission includes: a primary cell group MCG bearer whose termination point is a primary node MN.

4. The method according to claim 2, characterized in that: The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; The termination point is the MCG bearer of the secondary node SN.

5. The method according to claim 2, characterized in that: The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; Split bearer with termination point at MN; The termination point is the MCG bearer of SN; The termination point is the split bearer of SN.

6. The method according to any one of claims 2 to 5, characterized in that: If the DRB that can be used for small data transmission includes a split bearer, the first configuration information is further used to configure a path activated when the split bearer is used for small data transmission.

7. The method according to claim 6, characterized in that The path activated when the split bearer is used for small data transmission is the MCG path corresponding to the split bearer.

8. The method according to any one of claims 1 to 5, characterized in that The method further comprises: When specific conditions are met, the terminal device generates an SCG key based on the MCG key and the SCG count value, wherein the SCG key is used for encryption and decryption of small data.

9. The method according to claim 8, characterized in that The specific conditions include at least one of the following: Small data arrives at the Packet Data Convergence Protocol (PDCP) entity of the bearer whose termination point is at the SN; Small data arrives at the PDCP entity associated with the secondary key; Small uplink data arrives; Uplink data arrives; receiving a paging message from the MN, the paging message being used to indicate receiving small data or generating the SCG key; Receive the paging message from MN.

10. The method according to claim 9, characterized in that The paging message includes at least one of the following: a small data arrival indication, used to indicate whether small data has arrived; SCG key derivation indication, used to indicate whether to generate SCG key; List of DRB IDs where small data arrives.

11. The method according to claim 8, characterized in that The SCG count value is configured by a radio resource control RRC release message.

12. The method according to claim 8, characterized in that The MCG key is the master key before the terminal device initiates small data transmission, or is the master key updated when triggering small data transmission.

13. The method according to claim 1, characterized in that The RLC PDU corresponding to the downlink small data and the message carried by the common control channel CCCH are multiplexed in the first MAC PDU; or The PDCP PDU corresponding to the downlink small data and the message carried by the CCCH are multiplexed in the first MAC PDU.

14. The method according to claim 1, characterized in that The first indication information is carried in a reserved field in the first MAC SDU.

15. The method according to claim 1, characterized in that The method further comprises: The SCG MAC entity of the terminal device decodes the first MAC SDU according to the LCID corresponding to the downlink small data, and submits the decoded data to the upper layer of the terminal device.

16. The method according to any one of claims 1 to 5, characterized in that If small uplink data arrives at a second SCG bearer whose termination point is at the SN, the method further includes: The MCG MAC entity of the terminal device sends a second MAC PDU to the MN, where the second MAC PDU includes the RLC PDU or PDCP PDU corresponding to the uplink small data.

17. The method according to claim 16, characterized in that The RLC PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU; or The PDCP PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU.

18. The method according to claim 16, characterized in that The method further comprises: The SCG RLC entity of the terminal device generates a radio link control RLC PDU from the uplink small data and sends the RLC PDU to the MCG MAC entity of the terminal device; or The SCG PDCP entity of the terminal device generates a PDCP PDU from the uplink small data and sends the PDCP PDU to the MCG MAC entity of the terminal device.

19. The method according to claim 18, characterized in that The method further comprises: The SCG RLC entity or the SCG PDCP entity of the terminal device sends at least one of the following information to the MCG MAC entity of the terminal device: The LCID corresponding to the uplink small data, the DRB ID carried by the second SGC, and the quality of service QoS parameters of the uplink small data.

20. The method according to claim 18, characterized in that The method further comprises: The MCG MAC entity of the terminal device generates the second MAC PDU according to the RLC PDU corresponding to the uplink small data and the message in the CCCH; or The MCG MAC entity of the terminal device generates the second MAC PDU according to the PDCP PDU corresponding to the uplink small data and the message in the CCCH.

21. The method according to claim 16, characterized in that The second MAC PDU also includes second indication information and / or LCID corresponding to the uplink small data, wherein the second indication information is used to indicate that the uplink small data comes from the SCG bearer.

22. The method according to claim 21, characterized in that The second indication information is carried in the header of the second MAC SDU, the LCID corresponding to the uplink small data is carried in the header of the second MAC SDU, the second MAC PDU includes the second MAC SDU, and the second MAC SDU is the MAC SDU in the second MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data.

23. A data transmission method, characterized in that: include: A first node sends first configuration information to a terminal device, where the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB, and the first node is a MN; If the downlink small data arrives at the first SCG bearer whose termination point is the SN, the method further includes: The MN receives the downlink small data information sent by the SN; The MN sends a first media access control MAC protocol data unit PDU to the terminal device, the first MAC PDU includes the RLC PDU or PDCP PDU corresponding to the downlink small data from the SN, wherein the first MAC PDU also includes first indication information and a logical channel LCID corresponding to the downlink small data, the first indication information is used to indicate that the downlink small data comes from the SCG bearer, the first indication information is carried in the header of the first MAC service data unit SDU, the LCID corresponding to the downlink small data is carried in the header of the first MAC SDU, the first MAC PDU includes the first MAC SDU, the first MAC SDU is a MAC SDU in the first MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the downlink small data, and the first indication information is used for the terminal device to send the first MAC SDU and the LCID corresponding to the downlink small data to the SCG MAC entity of the terminal device when determining that the data in the first MAC PDU comes from the SCG bearer; The downlink small data information includes at least one of the following: The radio link control RLC PDU or packet data convergence protocol PDCP protocol data unit PDU corresponding to the downlink small data; The logical channel identifier LCID to which the downlink small data belongs; The DRB ID to which the downlink small data belongs; The quality of service QoS parameter corresponding to the downlink small data.

24. The method according to claim 23, characterized in that The first configuration information is used to configure a wireless data bearer DRB that can be used for small data transmission and / or a DRB that cannot be used for small data transmission.

25. The method according to claim 24, characterized in that The DRB that can be used for small data transmission includes: a primary cell group MCG bearer whose termination point is a primary node MN.

26. The method according to claim 24, characterized in that The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; The termination point is the MCG bearer of the secondary node SN.

27. The method according to claim 24, characterized in that The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; Split bearer with termination point at MN; The termination point is the MCG bearer of SN; The termination point is the split bearer of SN.

28. The method according to any one of claims 24 to 27, characterized in that If the DRB that can be used for small data transmission includes a split bearer, the first configuration information is further used to configure a path activated when the split bearer is used for small data transmission.

29. The method according to claim 28, characterized in that The path activated when the split bearer is used for small data transmission is the MCG path corresponding to the split bearer.

30. The method according to claim 23, characterized in that The first node is also used to configure an SCG count value for the terminal device, and the SCG count value is used by the terminal device to generate an SCG key for encryption and decryption of the small data according to the MCG key and the SCG count value.

31. The method according to claim 23, characterized in that The method further comprises: The MN receives a first message from the SN, where the first message is used to trigger the MN to page the terminal device, wherein when small downlink data arrives at a bearer of the termination point at the SN, the SN sends the first message; The MN sends a paging message to the terminal device according to the first message, where the paging message includes relevant indications of small data arrival and / or key generation.

32. The method according to claim 31, characterized in that The first message includes at least one of the following: a small data arrival indication, used to indicate whether small data has arrived; SCG key derivation indication, used to indicate whether to generate SCG key; List of DRB IDs where small data arrives.

33. The method according to claim 31, characterized in that The paging message includes at least one of the following: Small data arrival indication, used to indicate whether small data has arrived; SCG key derivation indication, used to indicate whether to generate SCG key; List of DRB IDs where small data arrives.

34. The method according to claim 30, characterized in that The SCG count value is configured via a radio resource control RRC release message.

35. The method according to claim 30, characterized in that The MCG key is the master key before the terminal device initiates small data transmission, or is the master key updated when triggering small data transmission.

36. The method according to claim 23, characterized in that The downlink small data information is transmitted via Xn interface signaling; or The information of the downlink small data is carried by an RRC forwarding message, wherein the RLC PDU or the PDCP PDU is included in the RRC forwarding message in a container manner.

37. The method according to claim 23, characterized in that The RLC PDU corresponding to the downlink small data and the message carried by the common control channel CCCH are multiplexed in the first MAC PDU; or The PDCP PDU corresponding to the downlink small data and the message carried by the CCCH are multiplexed in the first MAC PDU.

38. The method according to claim 23, characterized in that If the uplink small data arrives at the second SCG bearer whose termination point is the SN, the method further includes: The MN receives a second MAC PDU sent by the terminal device, where the second MAC PDU includes an RLC PDU or PDCP PDU corresponding to the uplink small data.

39. The method according to claim 38, characterized in that The RLC PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU; or The PDCP PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU.

40. The method according to claim 39, characterized in that The second MAC PDU also includes second indication information and / or a logical channel LCID corresponding to the uplink small data, and the second indication information is used to indicate that the uplink small data comes from the second SCG bearer.

41. The method according to claim 40, characterized in that The second indication information is carried in the header of the second MAC SDU, the LCID corresponding to the uplink small data is carried in the header of the second MAC SDU, the second MAC PDU includes the second MAC SDU, and the second MAC SDU is the MAC SDU in the second MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data.

42. The method according to claim 41, characterized in that The second indication information is carried in a reserved field in the second MAC SDU.

43. The method according to claim 41, characterized in that The method further comprises: The MN determines, according to the second indication information in the second MAC PDU, that the data in the second MAC PDU comes from the SCG bearer; The MN sends the LCID corresponding to the second MAC SDU and / or the uplink small data in the second MAC PDU to the SN.

44. The method according to claim 43, characterized in that The second MAC SDU and / or the LCID corresponding to the uplink small data are sent to the SN via Xn interface signaling; or, the second MAC SDU and / or the LCID corresponding to the uplink small data are sent to the SN via an RRC forwarding message.

45. A terminal device, characterized in that: include: A communication unit, configured to receive first configuration information, where the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB, the terminal device is in a multi-radio access technology RAT dual-connection MR-DC scenario, and the secondary cell group SCG of the terminal device is deactivated; Performing small data transmission according to the first configuration information; If there is downlink small data arriving at the first SCG bearer whose termination point is at the SN, the communication unit is further used for: Receive a first media access control MAC protocol data unit PDU sent by the MN, the first MAC PDU including the RLC PDU or PDCP PDU corresponding to the downlink small data from the SN, the first MAC PDU also including first indication information and a logical channel identifier LCID corresponding to the downlink small data, wherein the first indication information is used to indicate whether the downlink small data comes from the SCG bearer, the first indication information is carried in the header of the first MAC service data unit SDU, the LCID corresponding to the downlink small data is carried in the header of the first MAC SDU, the first MAC PDU includes the first MAC SDU, and the first MAC SDU is a MAC SDU in the first MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the downlink small data; The terminal device further includes: a processing unit, configured to determine, at the MCG MAC layer, based on the first indication information in the first MAC PDU, that the data in the first MAC PDU comes from the SCG bearer; The communication unit is also used to: send the first MAC SDU and the LCID corresponding to the downlink small data to the SCG MAC layer at the MCG MAC layer.

46. ​​The terminal device according to claim 45, characterized in that: The first configuration information is used to configure a wireless data bearer DRB that can be used for small data transmission and / or a DRB that cannot be used for small data transmission.

47. The terminal device according to claim 46, characterized in that: The DRB that can be used for small data transmission includes: a primary cell group MCG bearer whose termination point is a primary node MN.

48. The terminal device according to claim 46, characterized in that: The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; The termination point is the MCG bearer of the secondary node SN.

49. The terminal device according to claim 46, characterized in that: The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; Split bearer with termination point at MN; The termination point is the MCG bearer of SN; The termination point is the split bearer of SN.

50. The terminal device according to any one of claims 46 to 49, characterized in that: If the DRB that can be used for small data transmission includes a split bearer, the first configuration information is further used to configure a path activated when the split bearer is used for small data transmission.

51. The terminal device according to claim 50, characterized in that: The path activated when the split bearer is used for small data transmission is the MCG path corresponding to the split bearer.

52. The terminal device according to claim 45, characterized in that: The terminal device further includes: The processing unit is used to generate an SCG key according to the MCG key and the SCG count value when specific conditions are met, wherein the SCG key is used for encryption and decryption of small data.

53. The terminal device according to claim 52, characterized in that: The specific conditions include at least one of the following: Small data arrives at the Packet Data Convergence Protocol (PDCP) entity of the bearer whose termination point is at the SN; Small data arrives at the PDCP entity associated with the secondary key; Small uplink data arrives; Uplink data arrives; receiving a paging message from the MN, the paging message being used to indicate receiving small data or generating the SCG key; Receive the paging message from MN.

54. The terminal device according to claim 53, characterized in that: The paging message includes at least one of the following: a small data arrival indication, used to indicate whether small data has arrived; SCG key derivation indication, used to indicate whether to generate SCG key; List of DRB IDs where small data arrives.

55. The terminal device according to claim 52, characterized in that: The SCG count value is configured by a radio resource control RRC release message.

56. The terminal device according to claim 52, characterized in that: The MCG key is the master key before the terminal device initiates small data transmission, or is the master key updated when triggering small data transmission.

57. The terminal device according to claim 45, characterized in that: The RLC PDU corresponding to the downlink small data and the message carried by the common control channel CCCH are multiplexed in the first MAC PDU; or The PDCP PDU corresponding to the downlink small data and the message carried by the CCCH are multiplexed in the first MAC PDU.

58. The terminal device according to claim 45, characterized in that: The first indication information is carried in a reserved field in the first MAC SDU.

59. The terminal device according to claim 45, characterized in that: The processing unit is also used for: The SCG MAC layer decodes the first MAC SDU according to the LCID corresponding to the downlink small data, and delivers the decoded data to the upper layer of the terminal device.

60. The terminal device according to claim 45, characterized in that: If small uplink data arrives at the second SCG bearer whose termination point is at the SN, the communication unit is further used for: A second MAC PDU is sent to the MN at the MCG MAC layer, where the second MAC PDU includes the RLC PDU or PDCP PDU corresponding to the uplink small data.

61. The terminal device according to claim 60, characterized in that: The RLC PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU; or The PDCP PDU corresponding to the uplink small data and the message carried by the CCCH are multiplexed in the second MAC PDU.

62. The terminal device according to claim 60, characterized in that: The terminal device further includes: A processing unit is used to generate a radio link control RLC PDU from the uplink small data at the SCG RLC layer, and send the RLC PDU to the MCG MAC entity of the terminal device; or to generate a PDCP PDU from the uplink small data at the SCG PDCP layer, and send the PDCP PDU to the MCG MAC entity of the terminal device.

63. The terminal device according to claim 62, characterized in that: The processing unit is also used for: The SCG RLC layer or the SCG PDCP layer sends at least one of the following information to the MCG MAC layer: The LCID corresponding to the uplink small data, the DRB ID carried by the second SGC, and the quality of service QoS parameters of the uplink small data.

64. The terminal device according to claim 62, characterized in that: The processing unit is also used for: Generate the second MAC PDU at the MCG MAC layer according to the RLC PDU corresponding to the uplink small data and the message in the CCCH; or The second MAC PDU is generated at the MCG MAC layer according to the PDCP PDU corresponding to the uplink small data and the message in the CCCH.

65. The terminal device according to claim 60, characterized in that: The second MAC PDU also includes second indication information and / or LCID corresponding to the uplink small data, wherein the second indication information is used to indicate that the uplink small data comes from the SCG bearer.

66. The terminal device according to claim 65, characterized in that: The second indication information is carried in the header of the second MAC SDU, the LCID corresponding to the uplink small data is carried in the header of the second MAC SDU, the second MAC PDU includes the second MAC SDU, and the second MAC SDU is the MAC SDU in the second MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data.

67. A network node, characterized in that: include: A communication unit, configured to send first configuration information to a terminal device, wherein the first configuration information is used to configure a small data transmission configuration corresponding to a data radio bearer DRB, the network node is an MN, the terminal device is in a multi-radio access technology RAT dual-connection MR-DC scenario, and the secondary cell group SCG of the terminal device is deactivated; If the downlink small data arrives at the first SCG bearer whose termination point is SN, the communication unit is further used for: Receive downlink small data information sent by SN; Sending a first media access control MAC protocol data unit PDU to the terminal device, the first MAC PDU including the RLC PDU or PDCP PDU corresponding to the downlink small data from the SN, wherein the first MAC PDU also includes first indication information and a logical channel LCID corresponding to the downlink small data, the first indication information is used to indicate that the downlink small data comes from the SCG bearer, the first indication information is carried in the header of the first MAC service data unit SDU, the LCID corresponding to the downlink small data is carried in the header of the first MAC SDU, the first MAC PDU includes the first MAC SDU, the first MAC SDU is the MAC SDU used to carry the RLC PDU or PDCP PDU corresponding to the downlink small data in the first MAC PDU, and the first indication information is used for the terminal device to send the first MAC SDU and the LCID corresponding to the downlink small data to the SCG MAC entity of the terminal device when determining that the data in the first MAC PDU comes from the SCG bearer; The downlink small data information includes at least one of the following: The radio link control RLC PDU or packet data convergence protocol PDCP protocol data unit PDU corresponding to the downlink small data; The logical channel identifier LCID to which the downlink small data belongs; The DRB ID to which the downlink small data belongs; The quality of service QoS parameter corresponding to the downlink small data.

68. The network node according to claim 67, characterized in that The first configuration information is used to configure a wireless data bearer DRB that can be used for small data transmission and / or a DRB that cannot be used for small data transmission.

69. The network node according to claim 68, characterized in that The DRB that can be used for small data transmission includes: a primary cell group MCG bearer whose termination point is a primary node MN.

70. The network node according to claim 68, characterized in that The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; The termination point is the MCG bearer of the secondary node SN.

71. The network node according to claim 68, characterized in that The DRB that can be used for small data transmission includes: an MCG bearer whose termination point is at the MN; Split bearer with termination point at MN; The termination point is the MCG bearer of SN; The termination point is the split bearer of SN.

72. The network node according to claim 68, characterized in that If the DRB that can be used for small data transmission includes a split bearer, the first configuration information is further used to configure a path activated when the split bearer is used for small data transmission.

73. The network node according to claim 72, characterized in that The path activated when the split bearer is used for small data transmission is the MCG path corresponding to the split bearer.

74. The network node according to claim 67, characterized in that The network node is also used to configure an SCG count value for the terminal device, and the SCG count value is used by the terminal device to generate an SCG key for encryption and decryption of the small data based on the MCG key and the SCG count value.

75. The network node according to claim 67, characterized in that The communication unit is also used for: receiving a first message from the SN, where the first message is used to trigger the MN to page the terminal device, wherein the SN sends the first message when small downlink data arrives at a bearer of the termination point at the SN; According to the first message, a paging message is sent to the terminal device, where the paging message includes relevant indications of small data arrival and / or key generation.

76. The network node according to claim 75, characterized in that The first message includes at least one of the following: a small data arrival indication, used to indicate whether small data has arrived; SCG key derivation indication, used to indicate whether to generate SCG key; List of DRB IDs where small data arrives.

77. The network node according to claim 75, characterized in that The paging message includes at least one of the following: Small data arrival indication, used to indicate whether small data has arrived; SCG key derivation indication, used to indicate whether to generate SCG key; List of DRB IDs where small data arrives.

78. The network node according to claim 74, characterized in that The SCG count value is configured via a radio resource control RRC release message.

79. The network node according to claim 74, characterized in that The MCG key is the master key before the terminal device initiates small data transmission, or is the master key updated when triggering small data transmission.

80. The network node according to claim 67, characterized in that The downlink small data information is transmitted via Xn interface signaling; or The information of the downlink small data is carried by an RRC forwarding message, wherein the RLC PDU or the PDCP PDU is included in the RRC forwarding message in a container manner.

81. The network node according to claim 67, characterized in that The RLC PDU corresponding to the downlink small data and the message carried by the common control channel CCCH are multiplexed in the first MAC PDU; or The PDCP PDU corresponding to the downlink small data and the message carried by the CCCH are multiplexed in the first MAC PDU.

82. The network node according to claim 67, characterized in that If the uplink small data arrives at the second SCG bearer whose termination point is the SN, the communication unit is further used for: Receive a second MAC PDU sent by the terminal device, where the second MAC PDU includes the RLC PDU or PDCP PDU corresponding to the uplink small data.

83. The network node according to claim 82, characterized in that The RLC PDU corresponding to the uplink small data and the message carried by CCCH are multiplexed in the second MAC PDU; or the PDCP PDU corresponding to the uplink small data and the message carried by CCCH are multiplexed in the second MAC PDU.

84. The network node according to claim 83, characterized in that The second MAC PDU also includes second indication information and / or a logical channel LCID corresponding to the uplink small data, and the second indication information is used to indicate that the uplink small data comes from the second SCG bearer.

85. The network node according to claim 84, characterized in that The second indication information is carried in the header of the second MAC SDU, the LCID corresponding to the uplink small data is carried in the header of the second MAC SDU, the second MAC PDU includes the second MAC SDU, and the second MAC SDU is the MAC SDU in the second MAC PDU used to carry the RLC PDU or PDCP PDU corresponding to the uplink small data.

86. The network node according to claim 85, characterized in that The second indication information is carried in a reserved field in the second MAC SDU.

87. The network node according to claim 85, characterized in that The network node also includes: a processing unit, configured to determine, according to the second indication information in the second MAC PDU, that the data in the second MAC PDU comes from the SCG bearer; The communication unit is also used to: send the LCID corresponding to the second MAC SDU and / or the uplink small data in the second MAC PDU to the SN.

88. The network node according to claim 84, characterized in that The second MAC SDU and / or the LCID corresponding to the uplink small data are sent to the SN via Xn interface signaling; or, the second MAC SDU and / or the LCID corresponding to the uplink small data are sent to the SN via an RRC forwarding message.

89. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 22.

90. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 22.

91. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 22.

92. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 22.

93. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 23 to 44.

94. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 23 to 44.

95. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 23 to 44.

96. A computer program product, characterized in that Comprising computer program instructions causing a computer to perform the method as claimed in any one of claims 23 to 44.

Images