Method for wireless transmission, terminal device, and network device

Abstract

Provided are a method for wireless communication, a terminal device, and a network device. The method for wireless communication comprises: a terminal device executes a first operation on a first protocol layer entity or a first protocol layer entity group, wherein the first operation includes one or more of the following: activation, deactivation, and selection; the first protocol layer entity belongs to a plurality of protocol layer entities associated with a first radio bearer, and the plurality of protocol layer entities belong to a same protocol layer; or the first protocol layer entity group belongs to a plurality of protocol layer entity groups associated with the first radio bearer.

Description

Method, terminal device and network device for wireless transmission TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and more particularly, to a method, a terminal device and a network device for wireless communication. BACKGROUND

[0002] In some communication systems (such as a 6G system), one radio bearer can be associated with multiple protocol layer entities or multiple protocol layer entity groups to support multiple parallel data processing modes and improve the data processing rate. In this scenario, how to coordinate or manage the multiple protocol layer entities or multiple protocol layer entity groups associated with one radio bearer is a problem to be solved.

[0003] SUMMARY

[0004] The present application provides a method, a terminal device and a network device for wireless communication. The various aspects involved in the present application are introduced below.

[0005] In a first aspect, a method for wireless communication is provided, comprising: performing, by a terminal device, a first operation on a first protocol layer entity or a first protocol layer entity group, the first operation comprising one or more of the following: activation, deactivation, selection; wherein the first protocol layer entity belongs to multiple protocol layer entities associated with a first radio bearer, and the multiple protocol layer entities belong to a same protocol layer; or the first protocol layer entity group belongs to multiple protocol layer entity groups associated with the first radio bearer.

[0006] In a second aspect, a method for wireless communication is provided, comprising: sending, by a network device, indication information to a terminal device, the indication information being used to indicate protocol layer entities that need to be activated and / or protocol layer entities that need to be deactivated in multiple protocol layer entities associated with a first radio bearer, the multiple protocol layer entities belonging to a same protocol layer; or the indication information being used to indicate protocol layer entity groups that need to be activated and / or protocol layer entity groups that need to be deactivated in multiple protocol layer entity groups associated with the first radio bearer.

[0007] In a third aspect, a terminal device is provided, comprising: an execution module configured to perform a first operation on a first protocol layer entity or a first protocol layer entity group, the first operation comprising one or more of the following: activation, deactivation, selection; wherein the first protocol layer entity belongs to multiple protocol layer entities associated with a first radio bearer, and the multiple protocol layer entities belong to a same protocol layer; or the first protocol layer entity group belongs to multiple protocol layer entity groups associated with the first radio bearer.

[0008] In a fourth aspect, a network device is provided, which comprises a first sending module configured to send indication information to a terminal device, the indication information being used to indicate a protocol layer entity that needs to be activated and / or a protocol layer entity that needs to be deactivated in a plurality of protocol layer entities associated with a first radio bearer, the plurality of protocol layer entities belonging to a same protocol layer; or the indication information being used to indicate a protocol layer entity group that needs to be activated and / or a protocol layer entity group that needs to be deactivated in a plurality of protocol layer entity groups associated with the first radio bearer.

[0009] In a fifth aspect, a terminal device is provided, which comprises a processor, a memory and a communication interface, the memory being configured to store one or more computer programs, and the processor being configured to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0010] In a sixth aspect, a network device is provided, which comprises a processor, a memory and a communication interface, the memory being configured to store one or more computer programs, and the processor being configured to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0011] In a seventh aspect, a communication system is provided, which comprises the terminal device and / or the network device described above. In another possible design, the system can further comprise other devices interacting with the terminal device or the network device in the solutions provided by the embodiments of the present application.

[0012] In an eighth aspect, a computer readable storage medium is provided, which stores a computer program, and the computer program causes a computer to perform some or all of the steps in the methods of the above aspects.

[0013] In a ninth aspect, a computer program product is provided, which comprises a non-transitory computer readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform some or all of the steps in the methods of the above aspects. In some implementations, the computer program product can be a software installation package.

[0014] In a tenth aspect, a chip is provided, which comprises a memory and a processor, and the processor can invoke and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0015] In the embodiments of the present application, the terminal device can perform the first operation on the multiple protocol layer entities or multiple protocol layer entity groups associated with the first radio bearer, thereby facilitating coordination or management of the multiple protocol layer entities or multiple protocol layer entity groups associated with one radio bearer, and ensuring normal communication. BRIEF DESCRIPTION OF DRAWINGS

[0016] FIG. 1 is an example diagram of a system architecture of a wireless communication system to which embodiments of the present application can be applied.

[0017] FIG. 2 is an example diagram of a processing flow of data in a user plane protocol stack.

[0018] FIG. 3 is an example diagram of two protocol stacks.

[0019] FIG. 4 is a flow diagram of a method for wireless communication provided by the embodiments of the present application.

[0020] FIG. 5 is a schematic diagram of a structure of a terminal device provided by the embodiments of the present application.

[0021] FIG. 6 is a schematic diagram of a structure of a network device provided by the embodiments of the present application.

[0022] FIG. 7 is a schematic structural diagram of a communication apparatus provided by the embodiments of the present application. DETAILED DESCRIPTION

[0023] Communication system architecture

[0024] FIG. 1 is an example diagram of a system architecture of a wireless communication system 100 to which embodiments of the present application can be applied. The wireless communication system 100 can include a network device 110 and a terminal device 120. The network device 110 can be a device that communicates with the terminal device 120. The network device 110 can provide communication coverage for a specific geographic area and can communicate with the terminal device 120 located within the coverage area.

[0025] FIG. 1 exemplarily shows one network device and two terminal devices. Alternatively, the wireless communication system 100 can include multiple network devices and each network device can include other numbers of terminal devices within its coverage, which is not limited in the embodiments of the present application.

[0026] Alternatively, the wireless communication system 100 can further include a network controller, a mobile management entity, and other network entities, which are not limited in the embodiments of the present application.

[0027] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a 5th generation (5G) system or new radio (NR), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), and the like. The technical solutions provided in the present application can also be applied to future communication systems, such as a 6th generation mobile communication system, a satellite communication system, and the like.

[0028] The terminal device in the embodiments of the present application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The terminal device in the embodiments of the present application can refer to a device that provides voice and / or data connectivity for a user, and can be used to connect people, things, and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, and the like. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a notebook computer, a palm computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, and the like. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity, which provides a sidelink signal between UEs in V2X or D2D, and the like. For example, a cellular phone and a car communicate with each other using a sidelink signal. The cellular phone and the smart home device communicate with each other without relaying the communication signal through the base station.

[0029] The network device in the embodiments of the present application can be a device for communicating with a terminal device, which can also be referred to as an access network device or a radio access network device, such as a network device, which can be a base station. The network device in the embodiments of the present application can refer to a radio access network (RAN) node (or device) that accesses a terminal device to a wireless network. The base station can broadly cover various names in the following or be replaced by the following names, such as: Node B (NodeB), evolved Node B (eNB), next generation Node B (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, modem or chip for being disposed in the foregoing devices or apparatuses. The base station can also be a mobile switching center and a device that undertakes a base station function in device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communication, a network side device in a 6G network, a device that undertakes a base station function in a future communication system, etc. The base station can support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0030] The base station can be fixed or mobile. For example, a helicopter or a drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or a drone can be configured to act as a device that communicates with another base station.

[0031] In some deployments, the network device in the embodiments of the present application can refer to a CU or a DU, or the network device includes a CU and a DU. The gNB can also include an AAU.

[0032] The network device and the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on the aircraft, balloon and satellite in the air. The scene where the network device and the terminal device are located is not limited in the embodiments of the present application.

[0033] It should be understood that all or part of the functions of the communication device in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform).

[0034] 5G application scenarios

[0035] Currently, with the pursuit of rate, delay, high mobility, energy efficiency and the diversity and complexity of services in future life, the 3rd generation partnership project (3rd generation partnership project, 3GPP) international standard organization begins to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (enhanced mobile broadband, eMBB), ultra-reliable low latency communications (ultra-reliable low latency communications, URLLC), and massive machine type communications (massive machine type communications, mMTC).

[0036] On the one hand, eMBB still aims to enable users to obtain multimedia content, services and data, and its demand is growing very rapidly. On the other hand, since eMBB can be deployed in different scenarios, such as indoor, urban, rural, etc., the difference between its capabilities and requirements is also relatively large, so it cannot be generalized and must be analyzed in detail in combination with the specific deployment scenario.

[0037] One of the key features of URLLC is low latency, in which scenario the connection latency can reach 1 millisecond or less, and can support high reliability connections in high-speed mobile situations, for example, at a speed of 500 kilometers / hour, the reliability can reach 99.999%. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety assurance, etc.

[0038] Typical mMTC features include: high connection density, small data volume, latency-insensitive traffic, low cost of modules, and long service life, etc. Based on this, mMTC can include one or more of the following communications: communication of industrial wireless sensor networks, communication in video surveillance scenarios, communication of wearable devices.

[0039] Radio resource control (RRC) state

[0040] In some scenarios, NR can be deployed independently. In order to reduce air interface signaling, quickly recover wireless connection, and quickly recover data traffic, 5G defines a new RRC state, i.e., RRC inactive (RRC_INACTIVE) state. This state is different from RRC idle (RRC_IDLE) state and RRC connected (RRC_CONNECTED) state. The following describes the three RRC states.

[0041] When the terminal device is in the RRC idle state, there is no RRC connection between the terminal device and the network device (e.g., a camping network device), there is no access stratum (AS) context of the terminal device on the network device side, and there is no connection between the network device and the core network for the terminal device. If the terminal device needs to enter the RRC connected state from the RRC idle state, it needs to initiate an RRC connection establishment process. In the RRC idle state, the core network can send a paging message to the terminal device, that is, the paging process can be triggered by the CN. Optionally, the paging area can also be configured by the CN. In some cases, for the terminal device in the RRC idle state, when the terminal device moves in location (e.g., moves from one cell to another), the terminal device can initiate a cell reselection process. In other cases, for the terminal device in the RRC idle state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection process. That is, the mobility management of the terminal device in the RRC idle state can include cell reselection and / or cell selection.

[0042] When the terminal device is in the RRC connected state, there is an RRC connection between the terminal device and the network device (e.g., a base station), there is an AS context of the terminal device on the network device, and unicast data can be transmitted between the terminal device and the network device. In the RRC connected state, the network device can determine the cell-level location information of the terminal device, that is, the network device can determine the cell to which the terminal device belongs. In the RRC connected state, when the terminal device moves in location, such as moving from one cell to another, the network device can control the terminal device to perform cell handover.

[0043] When the terminal device is in the RRC inactive state (referred to as the inactive state for short), there is a connection between the core network and the radio access network (RAN), and the AS context of the terminal device exists on the anchor network device. The RAN can send a paging message to the terminal device, that is, the paging process can be triggered by the RAN. The RAN-based paging area is managed by the RAN, and the network device can know the location of the terminal device based on the RAN-based paging area level. In some cases, for the terminal device in the RRC inactive state, when the terminal device moves in location (for example, moves from one cell to another cell), the terminal device can initiate a cell reselection process. In other cases, for the terminal device in the RRC inactive state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection process. That is, the mobility management of the terminal device in the RRC inactive state can include cell reselection and / or cell selection.

[0044] User plane protocol stack

[0045] The user plane protocol stack of the communication system can be divided into multiple sub-layers. Taking the NR system as an example, the user plane protocol stack of the NR system can be divided into four sub-layers, which are, from bottom to top, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaption protocol (SDAP) layer.

[0046] The MAC layer is responsible for one or more of the following functions: mapping between logical channels and transport channels, multiplexing between logical channels and transport channels, demultiplexing between logical channels and transport channels, uplink and downlink scheduling related processes, random access processes, and the like. Compared with the LTE system, the MAC layer in the NR system introduces some new features, such as bandwidth part (BWP) activation / deactivation processes, beam failure recovery processes, and the like.

[0047] The RLC layer is responsible for one or more of the following functions: data packet segmentation, data packet reassembly, error detection, and the like. Compared with the LTE system, the RLC layer in the NR system does not contain the function of data packet concatenation.

[0048] The PDCP layer is responsible for one or more of the following functions: data packet encryption, data packet decryption, integrity protection, packet header compression, sequence number maintenance, reordering, in-sequence delivery, etc. Compared with the LTE system, the PDCP layer in the NR system can support a non-in-sequence delivery function based on network configuration. In addition, the PDCP layer in the NR system can also support a data repetition transmission (or referred to as a duplicated data transmission) function, etc., to improve the transmission reliability of data packets.

[0049] The SDAP layer is mainly responsible for mapping between a quality of service (QoS) flow and a data radio bearer (DRB).

[0050] Taking the process of transmitting end processing data in the user plane as an example, the user plane data first reaches the SDAP layer in the form of a QoS flow. The SDAP layer is responsible for mapping data of different QoS flows to different DRBs, and adding a QoS flow identifier to the data according to network configuration, generating an SDAP packet data unit (PDU) and delivering it to the PDCP layer. The PDCP layer processes the SDAP PDU (such as header compression, encryption, integrity protection, etc.), and generates a PDCP PDU and delivers it to the RLC layer. The RLC layer processes RLC service data units (SDUs) according to the configured RLC mode, such as RLC SDU segmentation and retransmission management, etc. The MAC layer is responsible for multiplexing data of logical channels into a MAC PDU (also referred to as a transport block (TB)), which can include multiple RLC SDUs or segments of RLC SDUs. These RLC SDUs can come from different logical channels or the same logical channel.

[0051] For ease of understanding, the following describes the processing flow of data in the user plane protocol stack in combination with FIG. 2. As shown in FIG. 2, for a certain protocol layer, the data received from the upper layer is referred to as an SDU, and the data generated after processing by the protocol layer and adding the corresponding protocol layer header is referred to as a PDU. For example, for the RLC layer, the data received from the PDCP layer is referred to as an RLC SDU, and the data generated after processing by the RLC layer and adding the RLC layer header is referred to as an RLC PDU. Continuing to refer to FIG. 2, it can be seen that a MAC PDU (i.e., a TB) can contain one or more MAC SDUs, wherein one MAC SDU can correspond to a complete RLC SDU or a segment of an RLC SDU.

[0052] For ease of understanding, the PDCP layer and the RLC layer are described in more detail below.

[0053] For uplink, the PDCP layer is mainly responsible for processing PDCP SDUs received from the SDAP layer, e.g., processing the received PDCP SDUs to generate PDCP PDUs, after which the PDCP layer can deliver the generated PDCP PDUs to the corresponding RLC layer. For downlink, the PDCP layer is mainly responsible for receiving PDCP PDUs delivered from the RLC layer, processing them (e.g., stripping the PDCP header) and delivering them to the SDAP layer.

[0054] The functions provided by the PDCP layer mainly include one or more of the following: a maintenance function of a sequence number (SN) of a PDCP sender, a maintenance function of a SN of a PDCP receiver, a header compression and decompression function, a data packet encryption and decryption function, a data packet integrity protection function, a timer-based PDCP SDU discard function, a routing function in a split bearer scenario, a duplicate transmission function, a reordering function, and an in-sequence delivery function.

[0055] In a data transceiving process, for uplink transmission, the PDCP sender can maintain a local COUNT value (e.g., a COUNT value) of TX_NEXT, which can be initially set to 0. Each time a new PDCP PDU is generated, the SN in the header of the PDCP PDU is set to the value corresponding to the TX_NEXT, and the TX_NEXT is incremented by 1. The TX_NEXT indicates the SN of the next PDCP PDU to be constructed. In addition, the PDCP sender can perform header compression, integrity protection, and encryption operations on PDCP SDUs in sequence according to network configuration. For downlink reception, the PDCP receiver can maintain a reception window according to a local COUNT value, which can be maintained by the following local variables: RX_NEXT, RX_DELIV, and RX_REORD.

[0056] The RX_NEXT indicates the COUNT value corresponding to the next PDCP SDU expected to be received.

[0057] The RX_DELIV indicates the COUNT value corresponding to the next PDCP SDU expected to be transmitted to the uplink. In some embodiments, the RX_DELIV variable can be used to determine the lower boundary of the reception window.

[0058] The RX_REORD indicates the COUNT value corresponding to the PDCP PDU triggering the reordering timer.

[0059] It should be noted that, unlike the LTE system, in the NR system, the PDCP layer uses an absolute count value based method for maintaining local variables of data transceiving procedures and conditional comparison when data is transceived, which can improve the readability of the protocol. Specifically, in the NR system, the count value is composed of an SN and a hyper frame number, and the size is fixed at 32 bits. It should be further noted that, in the NR system, the header part of the PDCP PDU still contains the SN instead of the count value, so the air interface transmission overhead is not increased.

[0060] The RLC layer is between the PDCP layer and the MAC layer, and can process the PDU data of the PDCP layer into SDUs and then hand over the SDUs to the MAC layer.

[0061] The RLC layer provides three transmission modes for different types of data: transparent mode (TM), unacknowledge mode (UM) and acknowledge mode (AM).

[0062] In TM, the RLC layer does not process data and directly hands over the data to the MAC layer. Therefore, TM is the simplest and most efficient. TM is mainly used for transmission of paging messages, system information broadcast and signaling radio bearer 0 (SRB 0).

[0063] UM can also be referred to as unreliable mode. In UM, the RLC layer does not perform ARQ processing. UM does not support retransmission, and is generally suitable for services that do not have high requirements for data reliability but are sensitive to delay, such as audio DRB, video and other real-time services.

[0064] Different from TM, UM, although not guaranteeing correct transmission, is more complex. For example, in UM, the sending end needs to segment and add headers to RLC SDUs, to build UM data PDU (UM data PDU, UMD PDU), and correspondingly, the receiving end needs to remove headers and reassemble (if necessary) UMD PDU. The segmentation and reassembly are because the MAC entity informs the UM RLC entity of the size limit of the UMD PDU that the MAC layer can receive. Because of the size limit, for a RLC SDU that is too large, the RLC entity may not be able to include a complete SDU in a PDU when building it into a UMD PDU. Therefore, the RLC SDU needs to be segmented into multiple RLC SDU segments, and each PDU contains only one RLC SDU segment in the data field, and then a header is added to build a UMD PDU and sent to the MAC layer for transmission. That is, segmentation / reassembly and header addition / removal are the main differences between UM and TM.

[0065] AM can also be referred to as a reliable mode. In AM, the RLC layer provides full-featured processing. Or in other words, in AM, the RLC has the functions of UM, and can also support data reception state feedback. Because of the retransmission in AM, the transmission efficiency is relatively low. That is, AM supports retransmission based on state feedback reports, which can guarantee the reliability of data transmission, but also increases the delay of data transmission. AM is suitable for exclusive control and exclusive services, and generally has relatively high reliability requirements. For example, AM can be applied to the transmission of error-sensitive services such as SRB 0, file transfer protocol (file transfer protocol, FTP), Web browsing, and the like.

[0066] The same as UM is that the AM RLC entity also needs to segment and reassemble, and add and remove headers if necessary. Different from TM / UM is that AM needs to guarantee the correctness of data transmission, so the sending end needs to retransmit if necessary according to the receiving situation of the receiving end.

[0067] The RLC layer can provide one or more of the following functions: segmenting, concatenating, and reassembling RLC SDUs, reordering RLC SDUs, error correction based on automatic repeat reQuest (automatic repeat reQuest, ARQ), filtering duplicate packets of received RLC SDUs, re-segmenting, and RLC SDU discarding.

[0068] The functions provided by the RLC layer can be applied to different transmission modes. This is introduced as follows.

[0069] RLC layer segmentation, concatenation and reassembly of RLC SDUs can be applied in UM and AM. In some embodiments, RLC layer segmentation, concatenation and reassembly of RLC SDUs can be understood as that the RLC layer can combine multiple PDCP layer PDUs into one SDU for transmission.

[0070] RLC layer reordering of received RLC SDUs can be applied in UM and AM.

[0071] RLC layer error correction by ARQ can be applied in AM.

[0072] RLC layer filtering of duplicate packets of received RLC SDUs can be applied in AM, which are caused by retransmission.

[0073] RLC layer re-segmentation can be applied in AM. In some embodiments, RLC layer re-segmentation can refer to that the RLC layer re-segments the retransmission packets.

[0074] RLC SDU discard can be applied in AM and UM.

[0075] Radio bearer (RB)

[0076] Radio bearer is used for network equipment to allocate different layer protocol entities and configurations for terminal equipment, which can include PDCP entity, RLC entity, MAC entity and physical layer allocated resources, etc. Radio bearer can include DRB and signaling radio bearer (SRB).

[0077] In some embodiments, PDCP and radio bearer can be one-to-one correspondence, that is, each radio bearer can be associated with one PDCP entity.

[0078] Terminal equipment in multi-radio access technology dual connectivity (MR-DC) configuration has three types of radio bearers, which are master cell group bearer (MCG bearer), secondary cell group bearer (SCG bearer) and split bearer.

[0079] When the RLC, MAC and physical protocol stack of a radio bearer are located in the master node (MN), the radio bearer is called MCG bearer.

[0080] When the RLC, MAC, physical protocol stack of a radio bearer is located at the secondary node (SN), the radio bearer is called SCG bearer.

[0081] Split bearer has radio links on both MN and SN, but only one PDCP protocol stack. In some embodiments, the PDCP protocol stack is located at the MN side. In some embodiments, the PDCP protocol stack is located at the SN side. In some cases, the purpose of split bearer is to improve the traffic of the radio interface. In some cases, for example, when the PDCP layer allows the retransmission of PDCP packets between different links, split bearer can also improve the reliability of the radio bearer.

[0082] In some embodiments, for a split bearer, its associated PDCP entity can be associated with two RLC entities. One RLC entity acts as the primary path, and the other RLC entity acts as the secondary path.

[0083] For MCG bearer and SCG bearer, packets from the same radio bearer can only perform serial processing in the current protocol stack. For split bearer, packets from the same radio bearer can only perform parallel processing by the primary path and the secondary path in the scenario of repeated transmission, and only the primary path performs serial processing of the packets in other scenarios.

[0084] Currently, the design of the protocol stack is based on the architecture of the current protocol stack, and the functions and processes of the current protocol stack are enhanced and optimized for new service types. For example, in the design of the NR protocol stack, in order to support the URLLC scenario and meet the transmission requirements of low latency and high reliability, the PDCP layer introduces a repeated transmission mechanism. This design idea promotes the construction of a unified protocol stack architecture that can cover various transmission requirements, but this design idea has some drawbacks. On the one hand, as new service types continue to emerge, the size and complexity of the protocol stack will continue to rise. On the other hand, the current design of the protocol stack cannot meet the transmission characteristics and requirements of different scenarios. For example, the packet header of each protocol layer is designed according to the functions and processes it supports, which results in inconsistent lengths of the packet headers of different protocol layers. For example, the length of the MAC layer packet header is 2-5 bytes, the length of the RLC layer packet header is 0-5 bytes, and the length of the PDCP layer packet header is 2-3 bytes. This design of inconsistent lengths of packet headers is beneficial in low data rate scenarios, as there is no large amount of redundant information in the packet header, which helps to transmit more effective data in bandwidth-limited scenarios and provides data transmission efficiency. However, for high data rate scenarios, different lengths of packet headers can affect the processing speed of data streams, and more complex software and hardware support is required.

[0085] To solve the above problems, related technologies propose that two protocol stacks can be introduced to handle different service transmission requirements. For example, one protocol stack can be responsible for handling low data rate services and control plane (CP) processes; another protocol stack can be responsible for handling high data rate services.

[0086] FIG. 3 shows a schematic diagram of two protocol stacks. As shown in FIG. 3, the two protocol stacks can include an anchor protocol stack (APS) and a fast protocol stack (FPS). The APS can be responsible for handling low data rate services and control plane processes, and the FPS can be responsible for handling high data rate services.

[0087] To improve the processing rate of data, in some communication systems (such as 6G systems), one radio bearer can be associated with multiple protocol layer entities or multiple protocol layer entity groups to support multiple parallel data processing methods. For example, the FPS can support multiple parallel data processing methods by introducing multiple radio processing units (RPUs) to improve data processing. In some implementations, one RPU can correspond to one PDCP entity, one RLC entity, and one MAC entity.

[0088] Therefore, how to coordinate or manage the multiple protocol layer entities or the multiple protocol layer entity groups associated with the wireless bearer is a problem to be solved.

[0089] To solve the above problem, the embodiments of the present application provide a method, a terminal device and a network device for wireless communication, which can perform a first operation on a first protocol layer entity or a first protocol layer entity group, thereby facilitating coordination or management of the multiple protocol layer entities or the multiple protocol layer entity groups associated with the wireless bearer, and ensuring normal communication.

[0090] For ease of understanding, the first protocol layer entity and / or the first protocol layer entity group of the present application will be introduced first.

[0091] In some embodiments, the first wireless bearer can be associated with multiple protocol layer entities, or in other words, the first wireless bearer can be associated with N protocol layer entities, N being an integer greater than 1.

[0092] The embodiments of the present application do not limit the first wireless bearer. For example, the first wireless bearer can be an MCG bearer. Alternatively, the first wireless bearer can be an SCG bearer. Alternatively, the first wireless bearer can be a split bearer.

[0093] In some embodiments, the multiple protocol layer entities associated with the first wireless bearer can be used for parallel processing of data. For example, the multiple protocol layer entities associated with the first wireless bearer can perform parallel processing of data in UM. Alternatively, the multiple protocol layer entities associated with the first wireless bearer can perform parallel processing of data in AM. Alternatively, the multiple protocol layer entities associated with the first wireless bearer can perform parallel processing of data in TM.

[0094] In some embodiments, the multiple protocol layer entities associated with the first wireless bearer can belong to the same protocol layer. That is, the first wireless bearer can be associated with multiple protocol layer entities in one protocol layer. For example, the multiple protocol layer entities associated with the first wireless bearer can all belong to the PDCP layer, i.e., the first wireless bearer can be associated with multiple protocol layer entities in the PDCP layer. Alternatively, the multiple protocol layer entities associated with the first wireless bearer can all belong to the RLC layer, i.e., the first wireless bearer can be associated with multiple protocol layer entities in the RLC layer. Alternatively, the multiple protocol layer entities associated with the first wireless bearer can all belong to the MAC layer, i.e., the first wireless bearer can be associated with multiple protocol layer entities in the MAC layer.

[0095] In some embodiments, the first protocol layer entity belongs to a plurality of protocol layer entities associated with the first radio bearer. For example, the first protocol layer entity can be any one or more of the plurality of protocol layer entities associated with the first radio bearer. For another example, the first protocol layer entity can be one or more of the plurality of protocol layer entities associated with the first radio bearer that are not activated (or, in other words, are in an inactivated state). For yet another example, the first protocol layer entity can be one or more of the plurality of protocol layer entities associated with the first radio bearer that are activated (or, in other words, are in an activated state).

[0096] As an example, when the first protocol layer entity is activated, the first protocol layer entity can be any one or more of the plurality of protocol layer entities associated with the first radio bearer, or the first protocol layer entity can be one or more of the plurality of protocol layer entities associated with the first radio bearer that are not activated.

[0097] As another example, when the first protocol layer entity is deactivated, the first protocol layer entity can be one or more of the plurality of protocol layer entities associated with the first radio bearer that are activated.

[0098] As yet another example, when the first protocol layer entity is selected, the first protocol layer entity can be any one or more of the plurality of protocol layer entities associated with the first radio bearer, or the first protocol layer entity can be one or more of the plurality of protocol layer entities associated with the first radio bearer that are activated.

[0099] Embodiments of the present application do not limit the first protocol layer entity, and by way of example, the first protocol layer entity can include one of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, a first entity.

[0100] In some embodiments, the first entity described above can be used to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression, data segmentation, data retransmission.

[0101] Embodiments of the present application do not limit the implementation of the first entity performing data retransmission, and by way of example, the first entity can perform data retransmission through ARQ, or the first entity can perform data retransmission through HARQ, etc.

[0102] In some embodiments, the first entity described above can comprise part or all of the functionalities of at least two of the following entities: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity. That is, the first entity can jointly the functionalities of at least two of the PDCP layer entity, the RLC layer entity, the MAC layer entity, the physical layer entity, and thus, in some embodiments, the first entity can also be referred to or understood as a joint entity.

[0103] It should be appreciated that the first protocol layer entity described above can be associated with a protocol layer. For example, the first protocol layer entity can be a PDCP layer entity associated with a PDCP layer. Or, the first protocol layer entity can be an RLC layer entity associated with an RLC layer. Or, the first protocol layer entity can be a MAC entity associated with a MAC layer. Or, the first protocol layer entity can be a physical layer entity associated with a physical layer. Or, the first protocol layer entity can be a first entity associated with a first protocol layer.

[0104] Embodiments of the present application do not limit the first protocol layer, which can be a protocol layer introduced by a future communication system (e.g., a 6G system). In some embodiments, the first protocol layer can have one or more of the following functions: data encryption, data integrity protection, header compression, data compression, data segmentation, data retransmission. Or, the first protocol layer can have part or all of the functionalities of at least two of the following protocol layers: a PDCP layer, an RLC layer, a MAC layer, a physical layer. For example, the first protocol layer can have part or all of the functionalities of the PDCP layer and part or all of the functionalities of the RLC layer. Or, the first protocol layer can have part or all of the functionalities of the RLC layer and part or all of the functionalities of the MAC layer. Or, the first protocol layer can have part or all of the functionalities of the PDCP layer, part or all of the functionalities of the RLC layer, and part or all of the functionalities of the MAC layer. In some embodiments, the first protocol layer can also be referred to or understood as a joint protocol layer.

[0105] In some embodiments, the PDCP layer described above can comprise a first sub-layer and a second sub-layer. In some embodiments, the first sub-layer can be configured to perform one or more of the following functions: assigning a sequence number, header compression, data compression. In some embodiments, the second sub-layer can be configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression.

[0106] In some embodiments, the first sub-layer described above can be located above the second sub-layer. Or, the first sub-layer described above can be referred to or understood as a high sub-layer of the PDCP layer, and the second sub-layer can be referred to or understood as a low sub-layer of the PDCP layer.

[0107] In some embodiments, the PDCP layer entity mentioned by the embodiments of the present application can comprise an entity of the second sublayer of the PDCP layer, i.e., the first protocol layer entity can comprise an entity of the second sublayer of the PDCP layer. That is, the PDCP layer entity mentioned by the embodiments of the present application can perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression.

[0108] The first protocol layer entity is introduced above, and the first protocol layer entity group is introduced below.

[0109] In some embodiments, the first radio bearer can be associated with multiple protocol layer entity groups, or in other words, the first radio bearer can be associated with N protocol layer entity groups, N being an integer greater than 1. The introduction of the first radio bearer can be referred to the above, and will not be repeated here.

[0110] In some embodiments, the multiple protocol layer entity groups associated with the first radio bearer can be used for parallel processing of data. For example, the multiple protocol layer entity groups associated with the first radio bearer can be used for parallel processing of data in UM. For another example, the multiple protocol layer entity groups associated with the first radio bearer can be used for parallel processing of data in AM. For another example, the multiple protocol layer entity groups associated with the first radio bearer can be used for parallel processing of data in TM.

[0111] In some embodiments, the multiple protocol entity groups associated with the first radio bearer can be understood or referred to as multiple RPUs. The related introduction of RPU can be referred to the above.

[0112] In some embodiments, the first protocol layer entity group belongs to the multiple protocol layer entity groups associated with the first radio bearer. For example, the first protocol layer entity group can be any one or more of the multiple protocol layer entity groups associated with the first radio bearer. For another example, the first protocol layer entity group can be one or more of the multiple protocol layer entity groups associated with the first radio bearer which are not activated (or in other words, one or more of the multiple protocol layer entity groups which are in the inactivated state). For another example, the first protocol layer entity group can be one or more of the multiple protocol layer entity groups associated with the first radio bearer which are activated (or in other words, one or more of the multiple protocol layer entity groups which are in the activated state).

[0113] As an example, when the first protocol layer entity group is activated, the first protocol layer entity group can be any one or more of the multiple protocol layer entity groups associated with the first radio bearer, or the first protocol layer entity group can be one or more of the multiple protocol layer entity groups associated with the first radio bearer which are not activated.

[0114] As another example, the first protocol layer entity group can be one or more protocol layer entity groups of the plurality of protocol layer entity groups associated with the first radio bearer that have been activated when the first protocol layer entity group is deactivated.

[0115] As yet another example, the first protocol layer entity group can be any one or more protocol layer entity groups of the plurality of protocol layer entity groups associated with the first radio bearer, or the first protocol layer entity group can be one or more protocol layer entity groups of the plurality of protocol layer entity groups associated with the first radio bearer that have been activated when the first protocol layer entity group is selected.

[0116] In an embodiment of the present application, the first protocol layer entity group can include one or more protocol layer entities. The embodiment of the present application does not make specific limitation on the protocol layer entities included in the first protocol layer entity group. For example, the first protocol layer entity group can include one or more of the following protocol layer entities: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, and a first entity.

[0117] As an example, the first protocol layer entity group can include the first entity.

[0118] As another example, the first protocol layer entity group can include a PDCP layer entity and an RLC layer entity.

[0119] As yet another example, the first protocol layer entity group can include an RLC layer entity and a MAC layer entity.

[0120] As yet another example, the first protocol layer entity group can include a MAC layer entity and a first entity.

[0121] As yet another example, the first protocol layer entity group can include a PDCP layer entity, an RLC layer entity, and a MAC layer entity.

[0122] As yet another example, the first protocol layer entity group can include an RLC layer entity, a MAC layer, and a physical layer entity.

[0123] As yet another example, the first protocol layer entity group can include a MAC layer entity, a physical layer entity, and a first entity.

[0124] As yet another example, the first protocol layer entity group can include a PDCP layer entity, an RLC layer entity, a MAC layer entity, and a physical layer entity.

[0125] In an embodiment of the present application, the terminal device can perform a first operation on the first protocol layer entity or the first protocol layer entity group to coordinate or manage the plurality of protocol layer entities or the plurality of protocol layer entity groups associated with one radio bearer, and ensure normal communication. The first operation is described below.

[0126] The first operation is not limited by embodiments of the present application. Illustratively, the first operation can include one or more of the following operations: activating, deactivating, selecting. For example, the terminal device can activate the first protocol layer entity or the first protocol layer entity group. Alternatively, the terminal device can deactivate the first protocol layer entity or the first protocol layer entity group. Alternatively, the terminal device can select the first protocol layer entity or the first protocol layer entity group. Alternatively, the terminal device can activate the first protocol layer entity or the first protocol layer entity group, and select the first protocol layer entity or the first protocol layer entity group for data transmission (or data processing).

[0127] In some embodiments, the terminal device can determine the first protocol layer entity from the unactivated protocol layer entities associated with the first radio bearer, to activate the first protocol layer entity. Alternatively, the terminal device can determine the first protocol layer entity group from the unactivated protocol layer entity groups associated with the first radio bearer, to activate the first protocol layer entity group.

[0128] In some embodiments, the terminal device can determine the first protocol layer entity from the activated protocol layer entities associated with the first radio bearer, to deactivate the first protocol layer entity. Alternatively, the terminal device can determine the first protocol layer entity group from the activated protocol layer entity groups associated with the first radio bearer, to deactivate the first protocol layer entity group.

[0129] In some embodiments, the terminal device can select the first protocol layer entity from the activated protocol layer entities associated with the first radio bearer, to utilize the first protocol layer entity for data transmission. Alternatively, the terminal device can select the first protocol layer entity group from the activated protocol layer entity groups associated with the first radio bearer, to utilize the first protocol layer entity group for data transmission.

[0130] In some embodiments, the terminal device can determine the first protocol layer entity from the unactivated protocol layer entities associated with the first radio bearer, to activate the first protocol layer entity and select the first protocol layer entity for data transmission. Alternatively, the terminal device can determine the first protocol layer entity group from the unactivated protocol layer entity groups associated with the first radio bearer, to activate the first protocol layer entity group and select the first protocol layer entity group for data transmission.

[0131] In some embodiments, the protocol layer entity that can be activated / deactivated among the plurality of protocol layer entities associated with the first radio bearer comprises all (all) protocol layer entities associated with the first radio bearer. Alternatively, in some embodiments, the protocol layer entity group that can be activated / deactivated among the plurality of protocol layer entity groups associated with the first radio bearer comprises all protocol layer entity groups associated with the first radio bearer.

[0132] In some embodiments, the protocol layer entity that can be activated / deactivated among the plurality of protocol layer entities associated with the first radio bearer comprises part of the protocol layer entities associated with the first radio bearer. For example, the protocol layer entity that can be activated / deactivated among the plurality of protocol layer entities associated with the first radio bearer comprises other protocol layer entities except the primary protocol layer entity. Alternatively, in some embodiments, the protocol layer entity group that can be activated / deactivated among the plurality of protocol layer entity groups associated with the first radio bearer comprises part of the protocol layer entity groups associated with the first radio bearer. For example, the protocol layer entity group that can be activated / deactivated among the plurality of protocol layer entity groups associated with the first radio bearer comprises other protocol layer entity groups except the primary protocol layer entity group.

[0133] In some embodiments, the plurality of protocol layer entities associated with the first radio bearer comprises one or more primary protocol layer entities, or the plurality of protocol layer entity groups associated with the first radio bearer comprises one or more primary protocol layer entity groups. The primary protocol layer entity or the primary protocol layer entity group can always be used for data transmission (always in working state). Alternatively, the primary protocol layer entity or the primary protocol layer entity group can always be activated. Of course, the embodiments of the present application are not limited thereto, and the embodiments of the present application can not define the state of the primary protocol layer entity or the primary protocol layer entity group, as long as it can always be used for data transmission.

[0134] The embodiments of the present application do not limit the implementation of the terminal device to determine the primary protocol layer entity or the primary protocol layer entity group. As an implementation, the terminal device can determine the primary protocol layer entity or the primary protocol layer entity group through the configuration information sent by the network device. As another implementation, the terminal device can determine the primary protocol layer entity through the identification of the protocol layer entity, or determine the primary protocol layer entity group through the identification of the protocol layer entity group. For example, the protocol can predefine the protocol layer entity with a specific value (such as “0”) as the primary protocol layer entity. Alternatively, the protocol can predefine the protocol layer entity group with a specific value (such as “0”) as the primary protocol layer entity group.

[0135] In some embodiments, the activation and / or deactivation of the first protocol layer entity is triggered based on one or more of the following: the first condition, the indication information sent by the network device. Or, in some embodiments, the activation and / or deactivation of the first protocol layer entity group is triggered based on one or more of the following: the first condition, the indication information sent by the network device. As an example, the activation and / or deactivation of the first protocol layer entity (or the first protocol layer entity group) is triggered based on the first condition. As another example, the activation and / or deactivation of the first protocol layer entity (or the first protocol layer entity group) is triggered based on the indication information sent by the network device. As yet another example, the activation and / or deactivation of the first protocol layer entity (or the first protocol layer entity group) is triggered based on the first condition and the indication information sent by the network device.

[0136] The first condition and the indication information sent by the network device are introduced below, respectively.

[0137] In some embodiments, the first condition and / or the indication information sent by the network device can be used to determine one or more of the following: whether to activate / deactivate the protocol layer entity (such as the first protocol layer entity) associated with the first radio bearer, whether to activate / deactivate the protocol layer entity group (such as the first protocol layer entity group) associated with the first radio bearer, the number of activated / deactivated protocol layer entities, the number of activated / deactivated protocol layer entity groups.

[0138] In some embodiments, the first condition can be a pre-configured or pre-defined condition, for example, the first condition can be a protocol pre-defined condition. In some embodiments, the first condition can be a network device configured condition, for example, a condition configured by the network device through high layer signaling (such as RRC signaling).

[0139] In some embodiments, the first condition can be associated with one or more of the following information: whether the first radio bearer has data arrival, the amount of data to be transmitted of the first radio bearer, the time interval during which the first protocol layer entity does not receive data, the time interval during which the first protocol layer entity group does not receive data.

[0140] In some embodiments, the first condition is used to activate the first protocol layer entity or the first protocol layer entity group, and the first condition can be associated with one or more of the following information: whether the first radio bearer has data arrival, the amount of data to be transmitted of the first radio bearer.

[0141] In some embodiments, the first condition is used to activate the first protocol layer entity or the first protocol layer entity group, and the first condition can include one or more of the following: the first radio bearer has data arrival, the amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

[0142] As an example, the first condition is for activating the first protocol layer entity or the first group of protocol layer entities, and the first condition can comprise that the first radio bearer has data arrival. For example, if all of the multiple protocol layer entities or the multiple groups of protocol layer entities associated with the first radio bearer are in the deactivated state, the first condition can comprise that the first radio bearer has data arrival.

[0143] As another example, the first condition is for activating the first protocol layer entity or the first group of protocol layer entities, and the first condition can comprise that an amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold. For example, if part of the multiple protocol layer entities associated with the first radio bearer are in the activated state or there is a master protocol layer entity among the multiple protocol layer entities associated with the first radio bearer, or if part of the multiple groups of protocol layer entities associated with the first radio bearer are in the activated state or there is a master group of protocol layer entities among the multiple groups of protocol layer entities associated with the first radio bearer, the first condition can comprise that the amount of data to be transmitted of the first radio bearer is greater than or equal to the first threshold.

[0144] In some embodiments, in a case that the first condition comprises that the amount of data to be transmitted of the first radio bearer is greater than or equal to the first threshold, whether the first radio bearer has data arrival can be used to trigger the terminal device to determine whether the first condition is satisfied. For example, when the first radio bearer has data arrival, the terminal device can be triggered to determine whether the amount of data to be transmitted of the first radio bearer is greater than or equal to the first threshold, and if the amount of data to be transmitted of the first radio bearer is greater than or equal to the first threshold, the terminal device determines whether to activate the first protocol layer entity or the first group of protocol layer entities based on the first condition.

[0145] As yet another example, the first condition can comprise that the first radio bearer has data arrival and the amount of data to be transmitted of the first radio bearer is greater than or equal to the first threshold. For example, if part of the multiple protocol layer entities associated with the first radio bearer are in the activated state or there is a master protocol layer entity among the multiple protocol layer entities associated with the first radio bearer, or if part of the multiple groups of protocol layer entities associated with the first radio bearer are in the activated state or there is a master group of protocol layer entities among the multiple groups of protocol layer entities associated with the first radio bearer, the first condition can comprise that the first radio bearer has data arrival and the amount of data to be transmitted of the first radio bearer is greater than or equal to the first threshold.

[0146] In some embodiments, the first threshold is determined based on a number of activated protocol layer entities among the plurality of protocol layer entities associated with the first radio bearer, or the first threshold is determined based on a number of activated protocol layer entity groups among the plurality of protocol layer entity groups associated with the first radio bearer. For example, in a case that one protocol layer entity or one protocol layer entity group is activated, the first threshold can be set as a value 1, in a case that two protocol layer entities or two protocol layer entity groups are activated, the first threshold can be set as a value 2, in a case that three protocol layer entities or three protocol layer entity groups are activated, the first threshold can be set as a value 3, and so on.

[0147] In some embodiments, the value 2, the value 3, and so on are determined based on the value 1, i.e., the value 1 can be regarded as a basic value, and the other values are calculated based on the value 1. As an example, the value 2 can be equal to 2 times of the value 1, the value 3 can be equal to 3 times of the value 1, and so on. It should be understood that the embodiments of the present application are not limited thereto, for example, the value 2 can be equal to a sum of the value 1 and a first offset value, the value 3 can be equal to a sum of the value 2 and the first offset value (i.e., the value 3 is equal to a sum of the value 1 and 2 times of the first offset value).

[0148] The embodiments of the present application do not limit the manner of determining whether the first radio bearer has data arrived. Illustratively, when one or more of the following conditions is met, it can be considered that the first radio bearer has data arrived: the first sublayer of the PDCP layer receives an SDU from an upper layer (e.g., the SDAP layer, the application layer), the first sublayer of the PDCP layer receives an indication of data arrival from an upper layer.

[0149] In some embodiments, the amount of data to be transmitted of the first radio bearer can include one or more of the following: an amount of data of the first sublayer of the PDCP layer, an amount of data to be transmitted of the master protocol layer entity among the plurality of protocol layer entities, an amount of data to be transmitted of the activated protocol layer entity among the plurality of protocol layer entities, an amount of data to be transmitted of the master protocol layer entity group among the plurality of protocol layer entity groups, an amount of data to be transmitted of the activated protocol layer entity group among the plurality of protocol layer entity groups, an amount of data indicated by the application layer but not arrived at the access layer.

[0150] As an example, the amount of data to be transmitted of the first radio bearer can include one or more of the following: an amount of data of the first sublayer of the PDCP layer, an amount of data to be transmitted of the master protocol layer entity among the plurality of protocol layer entities, an amount of data to be transmitted of the activated protocol layer entity among the plurality of protocol layer entities, an amount of data indicated by the application layer but not arrived at the access layer.

[0151] As another example, the amount of data to be transmitted of the first radio bearer can comprise one or more of the following: the amount of data of the first sublayer of the PDCP layer, the amount of data to be transmitted of a master group of protocol layer entities among the plurality of groups of protocol layer entities, the amount of data to be transmitted of the activated groups of protocol layer entities among the plurality of groups of protocol layer entities, the amount of data indicated by the application layer that has not arrived at the access layer.

[0152] In some embodiments, the amount of data of the first sublayer of the PDCP layer can comprise one or more of the following: the SDUs received by the first sublayer of the PDCP layer from the upper layer, the PDUs processed by the first sublayer of the PDCP layer but not yet delivered to the lower layer (e.g., the second sublayer of the PDCP layer, the RLC layer, the MAC layer, etc.), the SDUs / PDUs determined to need retransmission based on a status report (SR).

[0153] In some embodiments, the amount of data indicated by the application layer that has not arrived at the access layer can comprise the amount of data indicated by the application layer that has not arrived at the user plane protocol stack.

[0154] In some embodiments, the number of protocol layer entities among the plurality of protocol layer entities associated with the first radio bearer that need to be activated is determined based on the amount of data to be transmitted of the first radio bearer. Alternatively, the number of groups of protocol layer entities among the plurality of groups of protocol layer entities associated with the first radio bearer that need to be activated is determined based on the amount of data to be transmitted of the first radio bearer. For example, in a case where the amount of data to be transmitted of the first radio bearer is greater than a second threshold value and less than or equal to a third threshold value, the total number of activated protocol layer entities or groups of protocol layer entities can be M; in a case where the amount of data to be transmitted of the first radio bearer is greater than the third threshold value and less than or equal to a fourth threshold value, the total number of activated protocol layer entities or groups of protocol layer entities can be P; in a case where the amount of data to be transmitted of the first radio bearer is greater than the fourth threshold value, the total number of activated protocol layer entities or groups of protocol layer entities can be Q, and so on. In some embodiments, Q > P > M.

[0155] In some embodiments, the above M, P, and Q are the total number of protocol layer entities or groups of protocol layer entities that need to be activated. That is, in a case where there are already activated protocol layer entities or groups of protocol layer entities among the plurality of protocol layer entities or the plurality of groups of protocol layer entities associated with the first radio bearer, the number of protocol layer entities or groups of protocol layer entities that need to be activated (i.e., actually need to be activated) can be equal to the above M or P or Q minus the number of already activated protocol layer entities or groups of protocol layer entities.

[0156] In some embodiments, after determining the number of protocol layer entities that need to be activated, the terminal device can determine the protocol layer entities that need to be activated from the plurality of protocol layer entities associated with the first radio bearer. Alternatively, after determining the number of protocol layer entity groups that need to be activated, the terminal device can determine the protocol layer entity groups that need to be activated from the plurality of protocol layer entity groups associated with the first radio bearer. For example, the terminal device can determine the protocol layer entities that need to be activated from the unactivated protocol layer entities in the plurality of protocol layer entities, or the terminal device can determine the protocol layer entity groups that need to be activated from the unactivated protocol layer entity groups in the plurality of protocol layer entity groups.

[0157] In some embodiments, the terminal device can determine the protocol layer entity that needs to be activated based on one or more of the following: randomly selecting from the unactivated protocol layer entities in the plurality of protocol layer entities, the order of the identifiers of the plurality of protocol layer entities, and the measurement results corresponding to the plurality of protocol layer entities. Taking the protocol layer entity that needs to be activated as including the first protocol layer entity as an example, the activation of the first protocol layer entity is determined based on one or more of the following: randomly selecting from the unactivated protocol layer entities in the plurality of protocol layer entities, the order of the identifiers of the plurality of protocol layer entities, and the measurement results corresponding to the plurality of protocol layer entities.

[0158] In some embodiments, the terminal device can determine the protocol layer entity group that needs to be activated based on one or more of the following: randomly selecting from the unactivated protocol layer entity groups in the plurality of protocol layer entity groups, the order of the identifiers of the plurality of protocol layer entity groups, and the measurement results corresponding to the plurality of protocol layer entity groups. Taking the protocol layer entity group that needs to be activated as including the first protocol layer entity group as an example, the activation of the first protocol layer entity group is determined based on one or more of the following: randomly selecting from the unactivated protocol layer entity groups in the plurality of protocol layer entity groups, the order of the identifiers of the plurality of protocol layer entity groups, and the measurement results corresponding to the plurality of protocol layer entity groups.

[0159] As an example, the terminal device can randomly select one or more protocol layer entities to activate from the plurality of protocol layer entities, or randomly select one or more protocol layer entity groups to activate from the plurality of protocol layer entity groups, based on the number of protocol layer entities or protocol layer entity groups that need to be activated.

[0160] As another example, the terminal device can select one or more protocol layer entities to activate in ascending order of the identifiers of the plurality of protocol layer entities, or select one or more protocol layer entity groups to activate in ascending order of the identifiers of the plurality of protocol layer entity groups, based on the number of protocol layer entities or protocol layer entity groups that need to be activated.

[0161] As a further example, the terminal device can select one or more protocol layer entities to activate, or one or more protocol layer entity groups to activate, according to a descending order of the identities of the protocol layer entities, or the identities of the protocol layer entity groups, based on the number of the protocol layer entities or the protocol layer entity groups that need to be activated.

[0162] As a further example, the terminal device can select one or more protocol layer entities to activate, or one or more protocol layer entity groups to activate, based on the measurement results corresponding to the protocol layer entities, or the measurement results corresponding to the protocol layer entity groups, based on the number of the protocol layer entities or the protocol layer entity groups that need to be activated. Illustratively, the terminal device can activate the protocol layer entities whose measurement results satisfy (e.g., are greater than) a fifth threshold, based on the measurement results corresponding to the protocol layer entities; or the terminal device can activate the protocol layer entity groups whose measurement results satisfy the fifth threshold, based on the measurement results corresponding to the protocol layer entity groups.

[0163] The present embodiments do not limit the measurement quantity corresponding to the measurement results. Illustratively, the measurement quantity corresponding to the measurement results can include one or more of the following: reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal to interference plus noise ratio (SINR).

[0164] In some embodiments, if the number of the protocol layer entities that satisfy the fifth threshold is less than the number of the protocol layer entities that need to be activated, or if the number of the protocol layer entity groups that satisfy the fifth threshold is less than the number of the protocol layer entity groups that need to be activated, the terminal device can send a report to the network device. The report can indicate one or more of the following: the number of the protocol layer entities or the protocol layer entity groups that need to be activated, the identities of the protocol layer entities or the protocol layer entity groups that do not satisfy the fifth threshold. In this way, the network device can instruct the terminal device on the subsequent operations of the terminal device according to the report sent by the terminal device.

[0165] In some embodiments, the first condition is used to deactivate the first protocol layer entity or the first protocol layer entity group, and the first condition can be associated with a time interval during which the first protocol layer entity or the first protocol layer entity group does not receive data. For example, the first condition can include that the time interval during which the first protocol layer entity or the first protocol layer entity group does not receive data is greater than or equal to a first time threshold.

[0166] In some embodiments, the time interval during which the first protocol layer entity or the first group of protocol layer entities does not receive data can be indicated by a timer.

[0167] In some embodiments, the first condition for deactivating the first protocol layer entity or the first group of protocol layer entities can comprise that the first timer expires. In some embodiments, the first timer can be started or restarted when the first protocol layer entity is activated and / or receives data, or the first timer can be started or restarted when the first group of protocol layer entities is activated and / or receives data. For example, the first timer can be started when the first protocol layer entity or the first group of protocol layer entities is activated, and restarted when the first protocol layer entity or the first group of protocol layer entities receives data.

[0168] In some embodiments, the first protocol layer entity or the first group of protocol layer entities receiving data can comprise the first protocol layer entity or the first group of protocol layer entities receiving SDU / PDU sent by an upper layer, and / or the first protocol layer entity or the first group of protocol layer entities receiving SDU / PDU sent by a lower layer.

[0169] The embodiments of the present application do not limit the first timer, for example, the first timer can be a timer introduced by a future communication system (such as a 6G system), or the first timer can be an existing timer (such as a discard timer).

[0170] The above describes the conditions for activating and / or deactivating the first protocol layer entity or the first group of protocol layer entities, and the following describes the indication information for activating and / or deactivating the first protocol layer entity or the first group of protocol layer entities.

[0171] In some embodiments, the indication information sent by the network device can be used to indicate the protocol layer entities in the plurality of protocol layer entities associated with the first radio bearer that need to be activated and / or deactivated. Alternatively, the indication information sent by the network device can be used to indicate the protocol layer entity groups in the plurality of protocol layer entity groups associated with the first radio bearer that need to be activated and / or deactivated.

[0172] In some embodiments, the indication information sent by the network device can be explicit indication information. For example, the indication information can comprise the identity of the protocol layer entity that needs to be activated and / or deactivated. Alternatively, the indication information can comprise the identity of the protocol layer entity group that needs to be activated and / or deactivated.

[0173] In some embodiments, the indication information can be received through an anchor protocol stack. In some embodiments, the indication information can be received through a master protocol layer entity of the multiple protocol layer entities associated with the first radio bearer. In some embodiments, the indication information can be received through a master protocol layer entity group of the multiple protocol layer entity groups associated with the first radio bearer.

[0174] In some embodiments, the indication information sent by the network device can be sent based on a request (i.e., the following request information) of the terminal device. In some embodiments, the request information sent by the terminal device to the network device can be used to request the network device to send the indication information.

[0175] In some embodiments, the request information can include one or more of the following information: a data amount to be transmitted of the first radio bearer, measurement results corresponding to the multiple protocol layer entities, measurement results corresponding to the multiple protocol layer entity groups.

[0176] In some embodiments, the measurement results corresponding to the multiple protocol layer entities can include measurement results of part or all of the multiple protocol layer entities. For example, the measurement results corresponding to the multiple protocol layer entities can include measurement results of each of the multiple protocol layer entities. Alternatively, the measurement results corresponding to the multiple protocol layer entities can include measurement results of the protocol layer entities that are not activated in the multiple protocol layer entities. Alternatively, the measurement results corresponding to the multiple protocol layer entities can include measurement results of the protocol layer entities that have been activated in the multiple protocol layer entities.

[0177] In some embodiments, the measurement results corresponding to the multiple protocol layer entity groups can include measurement results of part or all of the multiple protocol layer entity groups. For example, the measurement results corresponding to the multiple protocol layer entity groups can include measurement results of each of the multiple protocol layer entity groups. Alternatively, the measurement results corresponding to the multiple protocol layer entity groups can include measurement results of the protocol layer entity groups that are not activated in the multiple protocol layer entity groups. Alternatively, the measurement results corresponding to the multiple protocol layer entity groups can include measurement results of the protocol layer entity groups that have been activated in the multiple protocol layer entity groups.

[0178] In some embodiments, if each protocol layer is associated with a different radio transmission link, the terminal device can report the measurement results corresponding to the multiple protocol layer entities or the measurement results corresponding to the multiple protocol layer entity groups. In some embodiments, if multiple protocol layers can be associated with one radio transmission link (i.e., a unified radio transmission link), the terminal device can report the measurement results according to the number of radio transmission links.

[0179] In some embodiments, the request information can be sent (or in other words, the sending of the request information is triggered) based on one or more of the following conditions: the first radio bearer has data arrival, there is no already activated protocol layer entity in the plurality of protocol layer entities, there is no already activated protocol layer entity group in the plurality of protocol layer entity groups, and the amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold. For the amount of data to be transmitted of the first radio bearer and the first threshold, please refer to the above description, which will not be repeated here for brevity.

[0180] In some embodiments, the request information is sent through the anchor protocol stack. In some embodiments, the request information is sent through the master protocol layer entity in the plurality of protocol layer entities. In some embodiments, the request information is sent through the master protocol layer entity group in the plurality of protocol layer entity groups.

[0181] The above describes the activation and / or deactivation of the first protocol layer entity or the first protocol layer entity group. The following describes the selection of the first protocol layer entity or the first protocol layer entity group.

[0182] In some embodiments, the terminal device can select the first protocol layer entity or the first protocol layer entity for data transmission (such as PDU transmission). For example, the terminal device can select the first protocol layer entity or the first protocol layer entity to transmit the PDU generated by the first sublayer of the PDCP layer.

[0183] In some embodiments, the first protocol layer entity is selected from the already activated protocol layer entities associated with the first radio bearer. Alternatively, the first protocol layer entity group is selected from the already activated protocol layer entity groups associated with the first radio bearer.

[0184] In some embodiments, the first protocol layer entity is selected based on one or more of the following: randomly selecting from the already activated protocol layer entities in the plurality of protocol layer entities, the amount of data to be transmitted of the already activated protocol layer entities in the plurality of protocol layer entities, and the ordering of the identification of the already activated protocol layer entities in the plurality of protocol layer entities.

[0185] As an example, the first protocol layer entity is randomly selected from the already activated protocol layer entities in the plurality of protocol layer entities.

[0186] As another example, the first protocol layer entity is selected based on the amount of data to be transmitted of the already activated protocol layer entities in the plurality of protocol layer entities. For example, the terminal device can select the protocol layer entity with the amount of data to be transmitted less than or equal to a sixth threshold from the already activated protocol layer entities for data transmission.

[0187] In some embodiments, if there are multiple protocol layer entities whose to-be-transmitted data is less than or equal to the sixth threshold among the activated protocol layer entities, the terminal device can determine the first protocol layer entity in multiple manners, which are not limited in the embodiments of the present application. As an implementation, the terminal device can randomly select one protocol layer entity from the multiple protocol layer entities whose to-be-transmitted data is less than or equal to the sixth threshold as the first protocol layer entity. As another implementation, the terminal device can select a protocol layer entity with the smallest to-be-transmitted data from the multiple protocol layer entities whose to-be-transmitted data is less than or equal to the sixth threshold as the first protocol layer entity. As still another implementation, the terminal device can select a protocol layer entity with the smallest (or largest) identifier from the multiple protocol layer entities whose to-be-transmitted data is less than or equal to the sixth threshold as the first protocol layer entity, and the like.

[0188] As still another example, the first protocol layer entity is selected based on an ordering of identifiers of the activated protocol layer entities among the multiple protocol layer entities. For example, the first protocol layer entity is selected based on an ascending order of identifiers of the activated protocol layer entities among the multiple protocol layer entities. Or, the first protocol layer entity is selected based on a descending order of identifiers of the activated protocol layer entities among the multiple protocol layer entities.

[0189] As still another example, the first protocol layer entity is selected based on an ordering of identifiers of the activated protocol layer entities among the multiple protocol layer entities. For example, the first protocol layer entity is selected based on an ascending order of identifiers of the activated protocol layer entities among the multiple protocol layer entities. Or, the first protocol layer entity is selected based on a descending order of identifiers of the activated protocol layer entities among the multiple protocol layer entities.

[0190] In some embodiments, the first protocol layer entity group is selected based on one or more of the following: randomly from the activated protocol layer entity groups among the multiple protocol layer entity groups, to-be-transmitted data amounts of the activated protocol layer entity groups among the multiple protocol layer entity groups, and an ordering of identifiers of the activated protocol layer entity groups among the multiple protocol layer entity groups.

[0191] As an example, the first protocol layer entity group is selected randomly from the activated protocol layer entity groups among the multiple protocol layer entity groups.

[0192] As another example, the first protocol layer entity group is selected based on to-be-transmitted data amounts of the activated protocol layer entity groups among the multiple protocol layer entity groups. For example, the terminal device can select a protocol layer entity group with a to-be-transmitted data amount less than or equal to the sixth threshold from the activated protocol layer entity groups for data transmission.

[0193] In some embodiments, if there are multiple protocol layer entity groups whose to-be-transmitted data is less than or equal to the sixth threshold in the activated protocol layer entity groups, the terminal device can determine the first protocol layer entity group in various ways, which are not limited in the embodiments of the present application. As an implementation manner, the terminal device can randomly select one of the multiple protocol layer entity groups whose to-be-transmitted data is less than or equal to the sixth threshold as the first protocol layer entity group. As another implementation manner, the terminal device can select the protocol layer entity group with the smallest to-be-transmitted data from the multiple protocol layer entity groups whose to-be-transmitted data is less than or equal to the sixth threshold as the first protocol layer entity group. As still another implementation manner, the terminal device can select the protocol layer entity group with the smallest (or largest) identifier from the multiple protocol layer entity groups whose to-be-transmitted data is less than or equal to the sixth threshold as the first protocol layer entity group, and so on.

[0194] As still another example, the first protocol layer entity group is selected based on the ordering of the identifiers of the activated protocol layer entity groups in the multiple protocol layer entity groups. For example, the first protocol layer entity group is selected based on the ascending order of the identifiers of the activated protocol layer entity groups in the multiple protocol layer entity groups. Or, the first protocol layer entity group is selected based on the descending order of the identifiers of the activated protocol layer entity groups in the multiple protocol layer entity groups.

[0195] As still another example, the first protocol layer entity group is selected based on the to-be-transmitted data amount of the activated protocol layer entity groups in the multiple protocol layer entity groups and the ordering of the identifiers of the activated protocol layer entity groups in the multiple protocol layer entity groups. For example, the terminal device can select the protocol layer entity group with the smallest to-be-transmitted data amount and the smallest identifier from the activated protocol layer entity groups for data transmission. Or, the terminal device can select the protocol layer entity group with the smallest to-be-transmitted data amount and the largest identifier from the activated protocol layer entity groups for data transmission.

[0196] In some embodiments, the first protocol layer entity is selected by the terminal device when there is to-be-transmitted data in the upper protocol layer of the first protocol layer entity. Taking the first protocol layer entity as an entity of a second sublayer of a PDCP layer as an example, the first protocol layer entity can be selected when there is to-be-transmitted data in a first sublayer of the PDCP layer or an SDAP layer. Taking the first protocol layer entity as an entity of an RLC layer as an example, the first protocol layer entity can be selected when there is to-be-transmitted data in the first sublayer of the PDCP layer or the second sublayer of the PDCP layer or the SDAP layer.

[0197] In some embodiments, the first protocol layer entity group is selected by the terminal device when there is data to be transmitted at a protocol layer upper to the first protocol layer entity group. For example, when the first protocol layer entity group includes a second sub-layer of a PDCP layer and an RLC layer, the first protocol layer entity group can be selected when there is data to be transmitted at a first sub-layer of the PDCP layer or an SDAP layer. For example, when the first protocol layer entity group includes an RLC layer and a MAC layer, the first protocol layer entity group can be selected when there is data to be transmitted at the first sub-layer of the PDCP layer or the second sub-layer of the PDCP layer or the SDAP layer.

[0198] The first operation associated with the first protocol layer entity or the first protocol layer entity group is introduced above, and the flow of the embodiments of the present application is introduced below.

[0199] FIG. 4 is a flow diagram of a method for wireless communication provided by an embodiment of the present application. The method shown in FIG. 4 is described from the perspective of a terminal device and a network device interacting with each other, which may, for example, be the terminal device 120 and the network device 110 shown in FIG. 1. The method shown in FIG. 4 includes step S410, which is described below.

[0200] In step S410, the terminal device performs a first operation on a first protocol layer entity or a first protocol layer entity group.

[0201] For related descriptions of the first protocol layer entity, the first protocol layer entity group, and the first operation, please refer to the above, which will not be repeated here.

[0202] In some embodiments, the method of FIG. 4 can further include step S406. In step S406, the network device sends indication information to the terminal device. The indication information can be used to indicate the protocol layer entity that needs to be activated and / or the protocol layer entity that needs to be deactivated in the plurality of protocol layer entities. Alternatively, the indication information can be used to indicate the protocol layer entity group that needs to be activated and / or the protocol layer entity group that needs to be deactivated in the plurality of protocol layer entity groups.

[0203] For related descriptions of the indication information, please refer to the above, which will not be repeated here for brevity.

[0204] In some embodiments, the method of FIG. 4 can further include step S404. In step S404, the terminal device sends request information to the network device. The request information can be used to request the network device to send the indication information.

[0205] For related descriptions of the request information, please refer to the above, which will not be repeated here for brevity.

[0206] In some embodiments, the method of FIG. 4 can further include step S402. In step S402, the network device sends configuration information to the terminal device.

[0207] In some embodiments, the configuration information can be used to determine the multiple protocol layer entities or the multiple protocol layer entity groups associated with the first radio bearer. In some embodiments, the configuration information being used to determine the multiple protocol layer entities or the multiple protocol layer entity groups associated with the first radio bearer comprises one or more of the following: the configuration information being used to determine whether the first radio bearer is associated with the multiple protocol layer entities, the configuration information being used to determine whether the first radio bearer is associated with the multiple protocol layer entity groups, the configuration information being used to determine the number of the multiple protocol layer entities associated with the first radio bearer, and the configuration information being used to determine the number of the multiple protocol layer entity groups associated with the first radio bearer.

[0208] In some embodiments, the configuration information can be used to determine a primary protocol layer entity among the multiple protocol layer entities associated with the first radio bearer, or the configuration information can be used to determine a primary protocol layer entity group among the multiple protocol layer entity groups associated with the first radio bearer.

[0209] In some embodiments, the terminal device can establish the corresponding protocol layer entity or the protocol layer entity group based on the configuration information sent by the network device.

[0210] The method embodiments of the present application are described in detail above in combination with FIG. 1 to FIG. 4, and the device embodiments of the present application are described in detail below in combination with FIG. 5 to FIG. 7. It should be understood that the description of the method embodiments and the description of the device embodiments correspond to each other, and therefore, the parts not described in detail can be referred to the method embodiments described above.

[0211] FIG. 5 is a structural schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 500 shown in FIG. 5 comprises an execution module 510. The execution module 510 can be used to perform a first operation on a first protocol layer entity or a first protocol layer entity group, the first operation comprising one or more of the following: activation, deactivation, and selection; wherein the first protocol layer entity belongs to multiple protocol layer entities associated with a first radio bearer, and the multiple protocol layer entities belong to the same protocol layer; or the first protocol layer entity group belongs to multiple protocol layer entity groups associated with the first radio bearer.

[0212] In some embodiments, the activation and / or deactivation of the first protocol layer entity is triggered based on a first condition; or the activation and / or deactivation of the first protocol layer entity group is triggered based on a first condition.

[0213] In some embodiments, the first condition is associated with one or more of the following information: whether the first radio bearer has data arriving, the amount of data to be transmitted of the first radio bearer, the time interval during which the first protocol layer entity does not receive data, and the time interval during which the first protocol layer entity group does not receive data.

[0214] In some embodiments, the first condition is for activating the first protocol layer entity or the first group of protocol layer entities, and the first condition comprises one or more of: the first radio bearer has data arrival; the amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

[0215] In some embodiments, the first threshold is determined based on the number of activated protocol layer entities in the plurality of protocol layer entities, or the first threshold is determined based on the number of activated groups of protocol layer entities in the plurality of groups of protocol layer entities.

[0216] In some embodiments, the number of protocol layer entities in the plurality of protocol layer entities that need to be activated or the number of groups of protocol layer entities in the plurality of groups of protocol layer entities that need to be activated is determined based on the amount of data to be transmitted of the first radio bearer.

[0217] In some embodiments, the activation of the first protocol layer entity is determined based on one or more of: randomly selecting from the unactivated protocol layer entities in the plurality of protocol layer entities, the order of the identities of the plurality of protocol layer entities, the measurement results corresponding to the plurality of protocol layer entities; or the activation of the first group of protocol layer entities is determined based on one or more of: randomly selecting from the unactivated groups of protocol layer entities in the plurality of groups of protocol layer entities, the order of the identities of the plurality of groups of protocol layer entities, the measurement results corresponding to the plurality of groups of protocol layer entities.

[0218] In some embodiments, the first condition is for deactivating the first protocol layer entity or the first group of protocol layer entities, and the first condition comprises: a first timer expires, the first timer is started or restarted when the first protocol layer entity is activated and / or data is received, or the first timer is started or restarted when the first group of protocol layer entities is activated and / or data is received.

[0219] In some embodiments, the terminal device further comprises a first receiving module 520, configured to receive indication information sent by the network device, the indication information being used to indicate the protocol layer entities in the plurality of protocol layer entities that need to be activated and / or the protocol layer entities that need to be deactivated; or the indication information being used to indicate the groups of protocol layer entities in the plurality of groups of protocol layer entities that need to be activated and / or the groups of protocol layer entities that need to be deactivated.

[0220] In some embodiments, the sending module is configured to send, to the network device, request information used to request the network device to send the indication information; wherein the request information comprises one or more of the following: an amount of data to be transmitted of the first radio bearer, a measurement result corresponding to the plurality of protocol layer entities, a measurement result corresponding to the plurality of protocol layer entity groups.

[0221] In some embodiments, the request information is sent based on one or more of the following conditions: the first radio bearer has data arrival; there is no activated protocol layer entity in the plurality of protocol layer entities; there is no activated protocol layer entity group in the plurality of protocol layer entity groups; the amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

[0222] In some embodiments, the request information is sent through an anchor protocol stack, or the request information is sent through a master protocol layer entity in the plurality of protocol layer entities, or the request information is sent through a master protocol layer entity group in the plurality of protocol layer entity groups.

[0223] In some embodiments, the indication information is received through an anchor protocol stack, or the indication information is received through a master protocol layer entity in the plurality of protocol layer entities, or the indication information is received through a master protocol layer entity group in the plurality of protocol layer entity groups.

[0224] In some embodiments, the first protocol layer entity is selected based on one or more of the following: randomly selecting from the activated protocol layer entities in the plurality of protocol layer entities, an amount of data to be transmitted of the activated protocol layer entities in the plurality of protocol layer entities, an ordering of the identities of the activated protocol layer entities in the plurality of protocol layer entities; or the first protocol layer entity group is selected based on one or more of the following: randomly selecting from the activated protocol layer entity groups in the plurality of protocol layer entities, an amount of data to be transmitted of the activated protocol layer entity groups in the plurality of protocol layer entity groups, an ordering of the identities of the activated protocol layer entity groups in the plurality of protocol layer entity groups.

[0225] In some embodiments, the first protocol layer entity is selected by the terminal device when there is data to be transmitted at a protocol layer above the first protocol layer entity; or the first protocol layer entity group is selected by the terminal device when there is data to be transmitted at a protocol layer above the first protocol layer entity group.

[0226] In some embodiments, the amount of data to be transmitted of the first radio bearer comprises one or more of the following: the amount of data of a first sublayer of the PDCP layer, the amount of data to be transmitted of a master protocol layer entity of the plurality of protocol layer entities, the amount of data to be transmitted of a protocol layer entity of the plurality of protocol layer entities that has been activated, the amount of data to be transmitted of a master protocol layer entity group of the plurality of protocol layer entity groups, the amount of data to be transmitted of a protocol layer entity group of the plurality of protocol layer entity groups that has been activated, the amount of data indicated by an application layer that has not reached an access layer.

[0227] In some embodiments, the PDCP layer comprises a first sublayer and a second sublayer, the first sublayer is configured to perform one or more of the following functions: assigning a sequence number, header compression, data compression; and the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression.

[0228] In some embodiments, the first protocol layer entity comprises one of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, a first entity; and the first protocol layer entity group comprises one or more of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, a first entity; wherein the first entity is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression, data segmentation, data retransmission.

[0229] In some embodiments, the PDCP layer entity comprises an entity of a second sublayer of the PDCP layer, the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression.

[0230] In some embodiments, the terminal device further comprises a second receiving module configured to receive configuration information sent by the network device, the configuration information being used to determine the plurality of protocol layer entities or the plurality of protocol layer entity groups.

[0231] In some embodiments, the plurality of protocol layer entities or the plurality of protocol layer entity groups are configured to perform parallel processing on data.

[0232] In some embodiments, the execution module 510 can be the processor 710. The terminal device 500 can further comprise a memory 720 and a transceiver 730, as shown in FIG. 7.

[0233] Fig. 6 is a structural schematic diagram of a network device provided in an embodiment of the present application. The network device 600 shown in Fig. 6 can include a first sending module 610. The first sending module 610 can be configured to send, to a terminal device, indication information, the indication information being used to indicate a protocol layer entity that needs to be activated and / or a protocol layer entity that needs to be deactivated in a plurality of protocol layer entities associated with a first radio bearer, the plurality of protocol layer entities belonging to a same protocol layer; or the indication information being used to indicate a protocol layer entity group that needs to be activated and / or a protocol layer entity group that needs to be deactivated in a plurality of protocol layer entity groups associated with the first radio bearer.

[0234] In some embodiments, the network device further includes a receiving module 620, configured to receive request information sent by the terminal device, the request information being used to request the network device to send the indication information; wherein the request information includes one or more of the following information: an amount of data to be transmitted of the first radio bearer, a measurement result corresponding to the plurality of protocol layer entities, a measurement result corresponding to the plurality of protocol layer entity groups.

[0235] In some embodiments, the request information is sent based on one or more of the following conditions: the first radio bearer has data arrival; there is no protocol layer entity that has been activated in the plurality of protocol layer entities; there is no protocol layer entity group that has been activated in the plurality of protocol layer entity groups; the amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold value.

[0236] In some embodiments, the first threshold value is determined based on a number of protocol layer entities that have been activated in the plurality of protocol layer entities, or the first threshold value is determined based on a number of protocol layer entity groups that have been activated in the plurality of protocol layer entity groups.

[0237] In some embodiments, the request information is sent through an anchor protocol stack, or the request information is sent through a master protocol layer entity in the plurality of protocol layer entities, or the request information is sent through a master protocol layer entity group in the plurality of protocol layer entity groups.

[0238] In some embodiments, the indication information is received through an anchor protocol stack, or the indication information is received through a master protocol layer entity in the plurality of protocol layer entities, or the indication information is received through a master protocol layer entity group in the plurality of protocol layer entity groups.

[0239] In some embodiments, a number of protocol layer entities that need to be activated in the plurality of protocol layer entities or a number of protocol layer entity groups that need to be activated in the plurality of protocol layer entity groups is determined based on the amount of data to be transmitted of the first radio bearer.

[0240] In some embodiments, the amount of data to be transmitted of the first radio bearer comprises one or more of the following: the amount of data of a first sublayer of the PDCP layer, the amount of data to be transmitted of a master protocol layer entity of the plurality of protocol layer entities, the amount of data to be transmitted of a protocol layer entity of the plurality of protocol layer entities that has been activated, the amount of data to be transmitted of a master protocol layer entity group of the plurality of protocol layer entity groups, the amount of data to be transmitted of a protocol layer entity group of the plurality of protocol layer entity groups that has been activated, the amount of data indicated by an application layer that has not reached an access layer.

[0241] In some embodiments, the PDCP layer comprises a first sublayer and a second sublayer, the first sublayer is configured to perform one or more of the following functions: assigning a sequence number, header compression, data compression; the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression.

[0242] In some embodiments, the plurality of protocol layer entities comprises one of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, a first entity; any protocol layer entity group of the plurality of protocol layer entity groups comprises one or more of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, a first entity; wherein the first entity is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression, data segmentation, data retransmission.

[0243] In some embodiments, the PDCP layer entity comprises an entity of a second sublayer of the PDCP layer, the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression.

[0244] In some embodiments, the network device further comprises a second sending module configured to send configuration information to the terminal device, the configuration information being used to determine the plurality of protocol layer entities or the plurality of protocol layer entity groups.

[0245] In some embodiments, the plurality of protocol layer entities or the plurality of protocol layer entity groups are configured to perform parallel processing on data.

[0246] In some embodiments, the first sending module 610 can be a processor 710. The network device 600 can further comprise a memory 720 and a transceiver 730, as shown in FIG. 7.

[0247] FIG. 7 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. The dashed line in FIG. 7 indicates that the unit or module is optional. The apparatus 700 can be used to implement the method described in the above method embodiments. The apparatus 700 can be a chip, a terminal device or a network device.

[0248] The apparatus 700 can include one or more processors 710. The processor 710 can support the apparatus 700 to implement the method described in the above method embodiments. The processor 710 can be a general purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, etc. The general purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0249] The apparatus 700 can also include one or more memories 720. The memory 720 stores a program, which can be executed by the processor 710, so that the processor 710 performs the method described in the above method embodiments. The memory 720 can be independent of the processor 710 or integrated in the processor 710.

[0250] The apparatus 700 can also include a transceiver 730. The processor 710 can communicate with other devices or chips through the transceiver 730. For example, the processor 710 can perform data transceiving with other devices or chips through the transceiver 730.

[0251] The embodiments of the present application also provide a computer readable storage medium for storing a program. The computer readable storage medium can be applied to the terminal device or the network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in the embodiments of the present application.

[0252] The embodiments of the present application also provide a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or the network device provided by the embodiments of the present application, and the program causes the computer to execute the method performed by the terminal device or the network device in the embodiments of the present application.

[0253] The embodiments of the present application further provide a computer program. The computer program can be applied to the terminal device or the network device provided by the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal device or the network device in the embodiments of the present application.

[0254] It should be understood that the terms "system" and "network" can be used interchangeably in the present application. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the drawings are used to distinguish different objects, and are not used to describe a particular order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0255] In the embodiments of the present application, the "indication" mentioned can be direct indication, or indirect indication, or can be an indication of an associated relationship. For example, A indicates B, which can mean that B can be obtained directly through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0256] In the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information.

[0257] In the embodiments of the present application, the term "corresponding" can mean a direct or indirect corresponding relationship between the two, or can mean an associated relationship between the two, or can mean an indication and being indicated, configuration and being configured, and the like.

[0258] In the embodiments of the present application, "including" mentioned can mean direct inclusion, or indirect inclusion. Alternatively, "including" mentioned in the embodiments of the present application can be replaced by "indicating" or "used to determine". For example, A includes B can be replaced by A indicates B, or A is used to determine B.

[0259] In the embodiments of the present application, "predefined" or "preconfigured" can be realized by pre-saving corresponding codes, tables or other means that can be used to indicate related information in the device (for example, including terminal device and network device), and the present application does not limit the specific implementation manner. For example, predefinition can mean definition in a protocol.

[0260] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, for example, it can include the LTE protocol, the NR protocol and the related protocol applied to the future communication system, and the present application does not limit this.

[0261] The term "and / or" in the embodiments of the present application is merely an association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in the present application generally represents an "or" relationship between the associated objects.

[0262] In various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0263] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other ways. For example, the device embodiments described above are only schematic, and the division of the units is only a logical function division, and there can be another division way in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0264] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiments of the present application.

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

[0266] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server, data center and the like integrated with one or more available media sets. The available media can be magnetic media (for example, floppy disk, hard disk, magnetic tape), optical media (for example, digital video disc (DVD)) or semiconductor media (for example, solid state disk (SSD)) and the like.

[0267] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for wireless communication, comprising: Comprising: The terminal device performs a first operation on a first protocol layer entity or a first protocol layer entity group, the first operation comprising one or more of the following: activation, deactivation, selection; Wherein the first protocol layer entity belongs to a plurality of protocol layer entities associated with a first radio bearer, and the plurality of protocol layer entities belong to the same protocol layer; or, the first protocol layer entity group belongs to a plurality of protocol layer entity groups associated with the first radio bearer.

2. The method of claim 1, wherein, The activation and / or deactivation of the first protocol layer entity is triggered based on a first condition; or, the activation and / or deactivation of the first protocol layer entity group is triggered based on a first condition.

3. The method of claim 2, wherein, The first condition is associated with one or more of the following information: Whether the first radio bearer has data arriving; The amount of data to be transmitted of the first radio bearer; The time interval during which the first protocol layer entity has not received data; The time interval during which the first protocol layer entity group has not received data.

4. The method according to claim 2 or 3, characterized in that, The first condition is used to activate the first protocol layer entity or the first protocol layer entity group, and the first condition comprises one or more of the following: The first radio bearer has data arriving; The amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

5. The method of claim 4, wherein, The first threshold is determined based on the number of activated protocol layer entities in the plurality of protocol layer entities, or the first threshold is determined based on the number of activated protocol layer entity groups in the plurality of protocol layer entity groups.

6. The method according to any one of claims 2-5, characterized in that, The number of protocol layer entities or the number of protocol layer entity groups that need to be activated in the plurality of protocol layer entities or the plurality of protocol layer entity groups is determined based on the amount of data to be transmitted of the first radio bearer.

7. The method of any one of claims 2-6, wherein: The activation of the first protocol layer entity is determined based on one or more of the following: randomly selecting an activated one from the unactivated protocol layer entities in the plurality of protocol layer entities, the order of the identities of the plurality of protocol layer entities, and the measurement results corresponding to the plurality of protocol layer entities; or, The activation of the first protocol layer entity group is determined based on one or more of the following: randomly selecting an activated one from the unactivated protocol layer entity groups in the plurality of protocol layer entity groups, the order of the identities of the plurality of protocol layer entity groups, and the measurement results corresponding to the plurality of protocol layer entity groups.

8. The method according to any one of claims 2-7, characterized in that, The first condition is used to deactivate the first protocol layer entity or the first protocol layer entity group, and the first condition comprises: a first timer timeout, the first timer being started or restarted when the first protocol layer entity is activated and / or data is received, or the first timer being started or restarted when the first protocol layer entity group is activated and / or data is received.

9. The method according to any one of claims 1-8, characterized in that, The method further comprises: The terminal device receives indication information sent by the network device, the indication information being used for indicating protocol layer entities in the plurality of protocol layer entities that need to be activated and / or protocol layer entities that need to be deactivated; or, the indication information being used for indicating protocol layer entity groups in the plurality of protocol layer entity groups that need to be activated and / or protocol layer entity groups that need to be deactivated.

10. The method of claim 9, wherein, The method further comprises: The terminal device sends request information to the network device, the request information being used for requesting the network device to send the indication information; The request information comprises one or more of the following information: an amount of data to be transmitted of the first radio bearer, measurement results corresponding to the plurality of protocol layer entities, and measurement results corresponding to the plurality of protocol layer entity groups.

11. The method of claim 10, wherein, The request information is sent based on one or more of the following conditions: The first radio bearer has data arrival; There is no protocol layer entity that has been activated in the plurality of protocol layer entities; There is no protocol layer entity group that has been activated in the plurality of protocol layer entity groups; The amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

12. The method according to claim 10 or 11, characterized in that, The request information is sent through an anchor protocol stack, or the request information is sent through a master protocol layer entity in the plurality of protocol layer entities, or the request information is sent through a master protocol layer entity group in the plurality of protocol layer entity groups.

13. The method according to any one of claims 9-12, characterized in that, The indication information is received through an anchor protocol stack, or the indication information is received through a master protocol layer entity in the plurality of protocol layer entities, or the indication information is received through a master protocol layer entity group in the plurality of protocol layer entity groups.

14. The method of any of claims 1-13, wherein: The first protocol layer entity is selected based on one or more of the following: randomly selecting from protocol layer entities in the plurality of protocol layer entities that have been activated, an amount of data to be transmitted of the protocol layer entities in the plurality of protocol layer entities that have been activated, and an ordering of identities of the protocol layer entities in the plurality of protocol layer entities that have been activated; or The first protocol layer entity group is selected based on one or more of the following: randomly selecting from protocol layer entity groups in the plurality of protocol layer entities that have been activated, an amount of data to be transmitted of the protocol layer entity groups in the plurality of protocol layer entities that have been activated, and an ordering of identities of the protocol layer entity groups in the plurality of protocol layer entities that have been activated.

15. The method of any one of claims 1-14, wherein, The first protocol layer entity is selected by the terminal device when there is data to be transmitted at an upper protocol layer of the first protocol layer entity; or the first protocol layer entity group is selected by the terminal device when there is data to be transmitted at an upper protocol layer of the first protocol layer entity group.

16. The method of any one of claims 1-15, wherein, The to-be-transmitted data amount of the first radio bearer includes one or more of the following: a data amount of a first sublayer of a packet data convergence protocol (PDCP) layer, a to-be-transmitted data amount of a master protocol layer entity in the plurality of protocol layer entities, a to-be-transmitted data amount of a protocol layer entity that has been activated in the plurality of protocol layer entities, a to-be-transmitted data amount of a master protocol layer entity group in the plurality of protocol layer entity groups, a to-be-transmitted data amount of a protocol layer entity group that has been activated in the plurality of protocol layer entity groups, and a data amount that has not yet arrived at an access layer and is indicated by an application layer.

17. The method of claim 16, wherein, The PDCP layer includes a first sublayer and a second sublayer, the first sublayer is configured to perform one or more of the following functions: assigning a sequence number, header compression, and data compression; and the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, and data compression.

18. The method of any one of claims 1-17, wherein: The first protocol layer entity includes one of the following: a PDCP layer entity, a radio link control (RLC) layer entity, a medium access control (MAC) layer entity, a physical layer entity, and a first entity. The first protocol layer entity group includes one or more of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, and a first entity. The first entity is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression, data segmentation, and data retransmission.

19. The method of claim 18, wherein, The PDCP layer entity includes an entity of a second sublayer of a PDCP layer, and the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, and data compression.

20. The method of any one of claims 1-19, wherein, The method further includes: The terminal device receives configuration information sent by the network device, and the configuration information is used to determine the plurality of protocol layer entities or the plurality of protocol layer entity groups.

21. The method of any one of claims 1-20, wherein, The plurality of protocol layer entities or the plurality of protocol layer entity groups are used to perform parallel processing on data.

22. A method for wireless communication, comprising: The method further includes: The network device sends indication information to the terminal device, the indication information is used to indicate a protocol layer entity that needs to be activated and / or a protocol layer entity that needs to be deactivated in a plurality of protocol layer entities associated with a first radio bearer, and the plurality of protocol layer entities belong to a same protocol layer; or the indication information is used to indicate a protocol layer entity group that needs to be activated and / or a protocol layer entity group that needs to be deactivated in a plurality of protocol layer entity groups associated with the first radio bearer.

23. The method of claim 22, wherein, The method further includes: The network device receives request information sent by the terminal device, and the request information is used to request the network device to send the indication information. The request information includes one or more of the following information: a to-be-transmitted data amount of the first radio bearer, a measurement result corresponding to the plurality of protocol layer entities, and a measurement result corresponding to the plurality of protocol layer entity groups.

24. The method of claim 23, wherein, The request information is sent based on one or more of the following conditions: The first radio bearer has data arriving; There is no protocol layer entity that has been activated in the plurality of protocol layer entities; There is no protocol layer entity that has been activated in the plurality of protocol layer entities; none of the plurality of protocol layer entity groups currently has an activated protocol layer entity group; an amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

25. The method of claim 24, wherein, The first threshold is determined based on a number of activated protocol layer entities in the plurality of protocol layer entities, or the first threshold is determined based on a number of activated protocol layer entity groups in the plurality of protocol layer entity groups.

26. The method of any one of claims 23-25, wherein, The request information is sent through an anchor protocol stack, or the request information is sent through a master protocol layer entity in the plurality of protocol layer entities, or the request information is sent through a master protocol layer entity group in the plurality of protocol layer entity groups.

27. The method of any one of claims 22-26, wherein, The indication information is received through an anchor protocol stack, or the indication information is received through a master protocol layer entity in the plurality of protocol layer entities, or the indication information is received through a master protocol layer entity group in the plurality of protocol layer entity groups.

28. The method of any one of claims 22-27, wherein, The number of protocol layer entities that need to be activated or the number of protocol layer entity groups that need to be activated in the plurality of protocol layer entity groups is determined based on the amount of data to be transmitted of the first radio bearer.

29. The method of any one of claims 22-28, wherein, The amount of data to be transmitted of the first radio bearer includes one or more of the following: an amount of data of a first sublayer of a packet data convergence protocol (PDCP) layer, an amount of data to be transmitted of a master protocol layer entity in the plurality of protocol layer entities, an amount of data to be transmitted of an activated protocol layer entity in the plurality of protocol layer entities, an amount of data to be transmitted of a master protocol layer entity group in the plurality of protocol layer entity groups, an amount of data to be transmitted of an activated protocol layer entity group in the plurality of protocol layer entity groups, an amount of data indicated by an application layer that has not arrived at an access layer.

30. The method of claim 29, wherein, The PDCP layer includes a first sublayer and a second sublayer, the first sublayer is configured to perform one or more of the following functions: assigning a sequence number, header compression, data compression; and the second sublayer is configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression.

31. The method of any of claims 22-30, wherein: The plurality of protocol layer entities includes one of the following: a PDCP layer entity, a radio link control (RLC) layer entity, a medium access control (MAC) layer entity, a physical layer entity, a first entity; Any protocol layer entity group in the plurality of protocol layer entity groups includes one or more of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, a first entity; The first entity is configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression, data segmentation, data retransmission.

32. The method of claim 31, wherein, The PDCP layer entity includes an entity of a second sublayer of a PDCP layer, the second sublayer is configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression.

33. The method of any one of claims 22-32, wherein, The method further includes: The network device sends configuration information to the terminal device, and the configuration information is used to determine the multiple protocol layer entities or the multiple protocol layer entity groups.

34. The method of any one of claims 22-33, wherein, The multiple protocol layer entities or the multiple protocol layer entity groups are used to perform parallel processing on data.

35. A terminal device, comprising: Comprise: The execution module is configured to perform a first operation on the first protocol layer entity or the first protocol layer entity group, and the first operation comprises one or more of the following: activation, deactivation, selection. The first protocol layer entity belongs to multiple protocol layer entities associated with a first radio bearer, and the multiple protocol layer entities belong to the same protocol layer; or the first protocol layer entity group belongs to multiple protocol layer entity groups associated with the first radio bearer.

36. The terminal device of claim 35, wherein, The activation and / or deactivation of the first protocol layer entity is triggered based on a first condition; or the activation and / or deactivation of the first protocol layer entity group is triggered based on a first condition.

37. The terminal device of claim 36, wherein, The first condition is associated with one or more of the following information: Whether the first radio bearer has data arriving; The amount of data to be transmitted of the first radio bearer; The time interval during which the first protocol layer entity does not receive data; The time interval during which the first protocol layer entity group does not receive data.

38. The terminal device of claim 36 or 37, wherein, The first condition is used to activate the first protocol layer entity or the first protocol layer entity group, and the first condition comprises one or more of the following: The first radio bearer has data arriving; The amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

39. The terminal device of claim 38, wherein, The first threshold is determined based on the number of activated protocol layer entities in the multiple protocol layer entities, or the first threshold is determined based on the number of activated protocol layer entity groups in the multiple protocol layer entity groups.

40. The terminal device of any one of claims 36-39, wherein, The number of protocol layer entities or the number of protocol layer entity groups that need to be activated in the multiple protocol layer entities or the multiple protocol layer entity groups is determined based on the amount of data to be transmitted of the first radio bearer.

41. The terminal device of any one of claims 36-40, characterized in that: The activation of the first protocol layer entity is determined based on one or more of the following: randomly selecting an activated one from the unactivated protocol layer entities in the multiple protocol layer entities, the order of the identities of the multiple protocol layer entities, and the measurement results corresponding to the multiple protocol layer entities; or The activation of the first protocol layer entity group is determined based on one or more of the following: randomly selecting an activated one from the unactivated protocol layer entity groups in the multiple protocol layer entity groups, the order of the identities of the multiple protocol layer entity groups, and the measurement results corresponding to the multiple protocol layer entity groups.

42. The terminal device of any one of claims 36-41, wherein, The first condition is used to deactivate the first protocol layer entity or the first protocol layer entity group, and the first condition comprises: a first timer timeout, the first timer being started or restarted when the first protocol layer entity is activated and / or data is received, or the first timer being started or restarted when the first protocol layer entity group is activated and / or data is received.

43. The terminal device of any one of claims 35-42, wherein, The terminal device further comprises: The first receiving module is configured to receive indication information sent by the network device, the indication information being used to indicate protocol layer entities in the plurality of protocol layer entities that need to be activated and / or protocol layer entities that need to be deactivated, or the indication information being used to indicate protocol layer entity groups in the plurality of protocol layer entity groups that need to be activated and / or protocol layer entity groups that need to be deactivated.

44. The terminal device of claim 43, wherein, The terminal device further includes: The sending module is configured to send request information to the network device, the request information being used to request the network device to send the indication information. The request information includes one or more of the following information: an amount of data to be transmitted of the first radio bearer, measurement results corresponding to the plurality of protocol layer entities, and measurement results corresponding to the plurality of protocol layer entity groups.

45. The terminal device of claim 44, wherein, The request information is sent based on one or more of the following conditions: The first radio bearer has data arrival; There is no activated protocol layer entity in the plurality of protocol layer entities currently; There is no activated protocol layer entity group in the plurality of protocol layer entity groups currently; The amount of data to be transmitted of the first radio bearer is greater than or equal to a first threshold.

46. The terminal device of claim 44 or 45, wherein, The request information is sent through an anchor protocol stack, or the request information is sent through a main protocol layer entity in the plurality of protocol layer entities, or the request information is sent through a main protocol layer entity group in the plurality of protocol layer entity groups.

47. The terminal device of any one of claims 43-46, wherein, The indication information is received through an anchor protocol stack, or the indication information is received through a main protocol layer entity in the plurality of protocol layer entities, or the indication information is received through a main protocol layer entity group in the plurality of protocol layer entity groups.

48. The terminal device of any of claims 35-47, wherein: The first protocol layer entity is selected based on one or more of the following: randomly selecting from activated protocol layer entities in the plurality of protocol layer entities, an amount of data to be transmitted of the activated protocol layer entities in the plurality of protocol layer entities, and an order of identification of the activated protocol layer entities in the plurality of protocol layer entities; or The first protocol layer entity group is selected based on one or more of the following: randomly selecting from activated protocol layer entity groups in the plurality of protocol layer entities, an amount of data to be transmitted of the activated protocol layer entity groups in the plurality of protocol layer entity groups, and an order of identification of the activated protocol layer entity groups in the plurality of protocol layer entity groups.

49. The terminal device of any one of claims 35-48, wherein, The first protocol layer entity is selected by the terminal device when there is data to be transmitted at an upper protocol layer of the first protocol layer entity; or the first protocol layer entity group is selected by the terminal device when there is data to be transmitted at an upper protocol layer of the first protocol layer entity group.

50. The terminal device of any one of claims 35-49, wherein, The to-be-transmitted data amount of the first radio bearer comprises one or more of the following: a data amount of a first sublayer of a packet data convergence protocol (PDCP) layer, a to-be-transmitted data amount of a master protocol layer entity in the plurality of protocol layer entities, a to-be-transmitted data amount of an activated protocol layer entity in the plurality of protocol layer entities, a to-be-transmitted data amount of a master protocol layer entity group in the plurality of protocol layer entity groups, a to-be-transmitted data amount of an activated protocol layer entity group in the plurality of protocol layer entity groups, and a data amount of an application layer indication that has not reached an access layer.

51. The terminal device of claim 50, wherein, The PDCP layer comprises a first sublayer and a second sublayer, the first sublayer is configured to perform one or more of the following functions: assigning a sequence number, header compression, and data compression; and the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, and data compression.

52. The terminal device of any one of claims 35-51, wherein: The first protocol layer entity comprises one of the following: a PDCP layer entity, a radio link control (RLC) layer entity, a medium access control (MAC) layer entity, a physical layer entity, and a first entity. The first protocol layer entity group comprises one or more of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, and a first entity. The first entity is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, data compression, data segmentation, and data retransmission.

53. The terminal device of claim 52, wherein, The PDCP layer entity comprises an entity of a second sublayer of the PDCP layer, and the second sublayer is configured to perform one or more of the following functions: data encryption, integrity protection of data, header compression, and data compression.

54. The terminal device of any one of claims 35-53, wherein, The terminal device further comprises: A second receiving module configured to receive configuration information sent by the network device, wherein the configuration information is used to determine the plurality of protocol layer entities or the plurality of protocol layer entity groups.

55. The terminal device of any one of claims 35-54, wherein, The plurality of protocol layer entities or the plurality of protocol layer entity groups are configured to perform parallel processing on data.

56. A network device, comprising: The network device comprises: A first sending module configured to send indication information to the terminal device, wherein the indication information is used to indicate protocol layer entities that need to be activated and / or protocol layer entities that need to be deactivated in a plurality of protocol layer entities associated with a first radio bearer, and the plurality of protocol layer entities belong to a same protocol layer; or the indication information is used to indicate protocol layer entity groups that need to be activated and / or protocol layer entity groups that need to be deactivated in a plurality of protocol layer entity groups associated with the first radio bearer.

57. The network device of claim 56, wherein, The network device further comprises: A receiving module configured to receive request information sent by the terminal device, wherein the request information is used to request the network device to send the indication information; The request information comprises one or more of the following information: a to-be-transmitted data amount of the first radio bearer, a measurement result corresponding to the plurality of protocol layer entities, and a measurement result corresponding to the plurality of protocol layer entity groups.

58. The network device of claim 57, wherein, The request information is sent based on one or more of the following conditions: Data of the first radio bearer arrives. none of the plurality of protocol layer entities is activated currently; none of the plurality of protocol layer entity groups is activated currently; the first radio bearer has a data amount to be transmitted greater than or equal to a first threshold.

59. The network device of claim 58, wherein, The first threshold is determined based on a number of activated protocol layer entities in the plurality of protocol layer entities, or the first threshold is determined based on a number of activated protocol layer entity groups in the plurality of protocol layer entity groups.

60. The network device of any of claims 57-59, wherein, The request information is sent through an anchor protocol stack, or the request information is sent through a master protocol layer entity in the plurality of protocol layer entities, or the request information is sent through a master protocol layer entity group in the plurality of protocol layer entity groups.

61. The network device of any of claims 56-60, wherein, The indication information is received through an anchor protocol stack, or the indication information is received through a master protocol layer entity in the plurality of protocol layer entities, or the indication information is received through a master protocol layer entity group in the plurality of protocol layer entity groups.

62. The network device of any of claims 56-61, wherein, The number of protocol layer entities that need to be activated in the plurality of protocol layer entities or the number of protocol layer entity groups that need to be activated in the plurality of protocol layer entity groups is determined based on the data amount to be transmitted of the first radio bearer.

63. The network device of any of claims 56-62, wherein, The data amount to be transmitted of the first radio bearer includes one or more of the following: a data amount of a first sublayer of a packet data convergence protocol (PDCP) layer, a data amount to be transmitted of a master protocol layer entity in the plurality of protocol layer entities, a data amount to be transmitted of an activated protocol layer entity in the plurality of protocol layer entities, a data amount to be transmitted of a master protocol layer entity group in the plurality of protocol layer entity groups, a data amount to be transmitted of an activated protocol layer entity group in the plurality of protocol layer entity groups, and a data amount indicated by an application layer and not yet arrived at an access layer.

64. The network device of claim 63, wherein, The PDCP layer includes a first sublayer and a second sublayer, the first sublayer is configured to perform one or more of the following functions: assigning a sequence number, header compression, and data compression, and the second sublayer is configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, and data compression.

65. The network device of any of claims 56-64, wherein: The plurality of protocol layer entities includes one of the following: a PDCP layer entity, a radio link control (RLC) layer entity, a medium access control (MAC) layer entity, a physical layer entity, and a first entity. Any protocol layer entity group in the plurality of protocol layer entity groups includes one or more of the following: a PDCP layer entity, an RLC layer entity, a MAC layer entity, a physical layer entity, and a first entity. The first entity is configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression, data segmentation, and data retransmission.

66. The network device of claim 65, wherein, The PDCP layer entity includes an entity of a second sublayer of a PDCP layer, and the second sublayer is configured to perform one or more of the following functions: data encryption, data integrity protection, header compression, and data compression. 67.The network device of any of claims 56-66, wherein, The network device further includes: A second sending module, configured to send configuration information to the terminal device, wherein the configuration information is used to determine the plurality of protocol layer entities or the plurality of protocol layer entity groups. 68.The network device according to any one of claims 56-67, wherein, The plurality of protocol layer entities or the plurality of protocol layer entity groups are used to perform parallel processing on data.

69. A terminal device, comprising: A terminal device comprising a memory for storing a program and a processor for invoking the program in the memory, so as to enable the terminal device to perform the method according to any one of claims 1-21.

70. A network device, comprising: A network device comprising a transceiver, a memory for storing a program and a processor for invoking the program in the memory and controlling the transceiver to receive or send signals, so as to enable the network device to perform the method according to any one of claims 22-34.

71. An apparatus, comprising: An apparatus comprising a processor for invoking a program from a memory, so as to enable the apparatus to perform the method according to any one of claims 1-21 or 22-34.

72. A chip, comprising: An apparatus comprising a processor for invoking a program from a memory, so as to enable a device installed with the apparatus to perform the method according to any one of claims 1-21 or 22-34.

73. A computer-readable storage medium, comprising: A computer program product having a program stored thereon, wherein the program causes a computer to perform the method according to any one of claims 1-21 or 22-34.

74. A computer program product, characterized in that, A computer program product having a program stored thereon, wherein the program causes a computer to perform the method according to any one of claims 1-21 or 22-34.

75. A computer program, characterized in that, The computer program product causes a computer to perform the method according to any one of claims 1-21 or 22-34.

Images