WO2026036408A1 - Procédé de transmission sans fil, dispositif termina, et dispositif réseau - Google Patents

Procédé de transmission sans fil, dispositif termina, et dispositif réseau

Info

Publication number
WO2026036408A1
WO2026036408A1 PCT/CN2024/112912 CN2024112912W WO2026036408A1 WO 2026036408 A1 WO2026036408 A1 WO 2026036408A1 CN 2024112912 W CN2024112912 W CN 2024112912W WO 2026036408 A1 WO2026036408 A1 WO 2026036408A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol layer
layer entity
data
entities
entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/112912
Other languages
English (en)
Chinese (zh)
Inventor
林雪
卢前溪
付喆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2024/112912 priority Critical patent/WO2026036408A1/fr
Publication of WO2026036408A1 publication Critical patent/WO2026036408A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • This application relates to the field of communication technology, and more specifically, to a method, terminal device, and network device for wireless communication.
  • a single radio bearer can be associated with multiple protocol layer entities or groups of protocol layer entities to support multiple parallel data processing methods and improve data processing speed.
  • how to coordinate or manage the multiple protocol layer entities or groups of protocol layer entities associated with a single radio bearer is a problem that needs to be solved.
  • This application provides a method, terminal device, and network device for wireless communication.
  • the various aspects covered in this application are described below.
  • a method for wireless communication comprising: a terminal device performing a first operation on a first protocol layer entity or a first protocol layer entity group, the first operation including 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 a first radio bearer.
  • a method for wireless communication comprising: a network device sending indication information to a terminal device, the indication information being used to indicate, among a plurality of protocol layer entities associated with a first radio bearer, a protocol layer entity that needs to be activated and/or a protocol layer entity that needs to be deactivated, the plurality of protocol layer entities belonging to the same protocol layer; or, the indication information being used to indicate, among a plurality of protocol layer entity groups associated with a first radio bearer, a group of protocol layer entities that needs to be activated and/or a group of protocol layer entities that needs to be deactivated.
  • a terminal device comprising: an execution module for performing a first operation on a first protocol layer entity or a first protocol layer entity group, the first operation including 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 a first radio bearer.
  • a network device comprising: a first transmitting module, configured to transmit indication information to a terminal device, the indication information being configured to indicate, among a plurality of protocol layer entities associated with a first radio bearer, a protocol layer entity that needs to be activated and/or a protocol layer entity that needs to be deactivated, the plurality of protocol layer entities belonging to the same protocol layer; or, the indication information being configured to indicate, among a plurality of protocol layer entity groups associated with a first radio bearer, a group of protocol layer entities that needs to be activated and/or a group of protocol layer entities that needs to be deactivated.
  • a terminal device including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used 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.
  • a network device including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used 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.
  • embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.
  • embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects.
  • the computer program product may be a software installation package.
  • embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.
  • the terminal device can perform a first operation on multiple protocol layer entities or multiple protocol layer entity groups associated with a first radio bearer, thereby facilitating the coordination or management of multiple protocol layer entities or multiple protocol layer entity groups associated with a radio bearer and ensuring normal communication.
  • Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.
  • Figure 2 is an example diagram of the data processing flow in the user plane protocol stack.
  • Figure 3 shows two example diagrams of protocol stacks.
  • Figure 4 is a flowchart illustrating a method for wireless communication provided in an embodiment of this application.
  • Figure 5 is a schematic diagram of the structure of the terminal device provided in the embodiment of this application.
  • Figure 6 is a schematic diagram of the structure of the network device provided in an embodiment of this application.
  • Figure 7 is a schematic structural diagram of the communication device provided in an embodiment of this application.
  • FIG. 1 is a system architecture example diagram of a wireless communication system 100 to which embodiments of this application can be applied.
  • the wireless communication system 100 may include a network device 110 and a terminal device 120.
  • the network device 110 may be a device that communicates with the terminal device 120.
  • the network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located within that coverage area.
  • Figure 1 illustrates an exemplary network device and two terminal devices.
  • the wireless communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.
  • the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.
  • 5G 5th generation
  • NR new radio
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • 6th generation mobile communication systems satellite communication systems, and so on.
  • the terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • remote station remote terminal
  • mobile device user terminal
  • terminal wireless communication device
  • user agent user agent
  • user device can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • the terminal device in this application embodiment can be a device that provides voice and/or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc.
  • the terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc.
  • the UE can act as a base station.
  • the UE can act as a scheduling entity, providing sidelink signals between UEs in V2X or D2D, etc.
  • cellular phones and cars communicate with each other using sidelink signals.
  • Cellular phones and smart home devices communicate without relaying communication signals through a base station.
  • the network device in this application embodiment can be a device for communicating with a terminal device.
  • This network device can also be called an access network device or a wireless access network device, such as a base station.
  • the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network.
  • RAN radio access network
  • a base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, secondary SeNB, multi-mode 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.
  • a base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof.
  • a base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus.
  • a base station can also be a mobile switching center, or a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device performing base station functions in future communication systems.
  • Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.
  • Base stations can be fixed or mobile.
  • a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station.
  • a helicopter or drone can be configured as a device to communicate with another base station.
  • the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU.
  • the gNB may also include an AAU.
  • Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.
  • 5G 3rd Generation Partnership Project
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communications
  • mMTC massive machine-type communications
  • eMBB still aims to provide users with multimedia content, services, and data, and its demand is growing rapidly.
  • eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, its capabilities and needs vary considerably. Therefore, generalizations cannot be made, and a detailed analysis must be conducted in conjunction with the specific deployment scenario.
  • Typical applications of URLLC include industrial automation, power system automation, remote medical operations (surgery), and traffic safety.
  • Typical characteristics of mMTC include: high connection density, small data volume, latency-insensitive services, low module cost, and long lifespan. Based on this, mMTC can include one or more of the following communication methods: communication in industrial wireless sensor networks, communication in video surveillance scenarios, and communication in wearable devices.
  • NR can be deployed independently.
  • RRC_INACTIVE the RRC Inactive
  • RRC_IDLE the RRC Idle
  • RRC_CONNECTED RRC Connected
  • RRC idle state When a terminal device is in RRC idle state, there is no RRC connection between the terminal device and network devices (e.g., camped network devices).
  • the network device does not have an access stratum (AS) context for the terminal device, and no connection is established between the network device and the core network for that terminal device.
  • AS access stratum
  • the terminal device needs to transition from RRC idle state to RRC connected state, it needs to initiate an RRC connection establishment process.
  • the core network can send paging messages to the terminal device; that is, the paging process can be triggered by the CN.
  • the paging area can also be configured by the CN.
  • the terminal device can initiate a cell reselection process.
  • the terminal device can initiate a cell selection process.
  • mobility management for a terminal device in RRC idle state can include cell reselection and/or cell selection.
  • RRC connected state When a terminal device is in RRC connected state, an RRC connection exists between the terminal device and a network device (such as a base station). The network device and the terminal device share an AS context, and unicast data can be transmitted between them.
  • the network device In RRC connected state, the network device can determine the terminal device's cell-level location information; that is, the network device can determine the cell to which the terminal device belongs.
  • the network device In RRC connected state, if the terminal device moves, such as from one cell to another, the network device can control the terminal device to perform a cell handover.
  • a terminal device When a terminal device is in RRC inactive state (referred to as inactive state), a connection exists between the core network and the radio access network (RAN), and the terminal device's AS context resides on the anchor network device.
  • the RAN can send paging messages to the terminal device; that is, the paging process can be triggered by the RAN.
  • RAN-based paging areas are managed by the RAN, and network devices can determine the terminal device's location at the RAN-based paging area level.
  • the terminal device can initiate a cell reselection process.
  • a terminal device in RRC inactive state when the terminal device needs to access a cell, the terminal device can initiate a cell selection process.
  • mobility management for a terminal device in RRC inactive state can include cell reselection and/or cell selection.
  • the user plane protocol stack of a 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, from bottom to top, are the medium access control (MAC) layer, the radio link control (RLC) layer, the packet data convergence protocol layer, and the packet data convergence protocol layer. PDCP layer, Service Data Adaptation Protocol (SDAP) layer.
  • MAC medium access control
  • RLC radio link control
  • SDAP Service Data Adaptation Protocol
  • 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 procedures, random access procedures, etc.
  • 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 procedures, random access procedures, etc.
  • the MAC layer in NR systems introduces some new features, such as the activation/deactivation procedure of the bandwidth part (BWP) and the beam failure recovery procedure.
  • BWP bandwidth part
  • the RLC layer is responsible for one or more of the following functions: packet segmentation, packet reassembly, error detection, etc. Unlike LTE systems, the RLC layer in NR systems does not include packet concatenation functionality.
  • the PDCP layer is responsible for one or more of the following functions: packet encryption, packet decryption, integrity protection, header compression, sequence number maintenance, reordering, and in-order delivery.
  • the PDCP layer in NR systems can support out-of-order delivery based on network configuration.
  • the PDCP layer in NR systems can also support functions such as data duplication (or data replication) to improve the reliability of data packet transmission.
  • the SDAP layer is primarily responsible for mapping between Quality of Service (QoS) streams and data radio bearers (DRBs).
  • QoS Quality of Service
  • DRBs data radio bearers
  • user plane data first arrives at the SDAP layer via QoS streams.
  • the SDAP layer is responsible for mapping data from different QoS streams to different DRBs and adding QoS stream identifiers to the data according to network configuration, generating SDAP packet data units (PDUs) and submitting them to the PDCP layer.
  • the PDCP layer processes the SDAP PDUs (e.g., header compression, encryption, integrity protection) and generates PDCP PDUs, which are then submitted 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.
  • SDUs RLC service data units
  • the MAC layer is responsible for multiplexing the data from the logical channel into a MAC PDU (also called a transport block (TB)).
  • This MAC PDU can include multiple RLC SDUs or segments of RLC SDUs. These RLC SDUs can come from different logical channels or from the same logical channel.
  • a MAC PDU (i.e., TB) can contain one or more MAC SDUs.
  • One MAC SDU can correspond to a complete RLC SDU or a segment of an RLC SDU.
  • the PDCP layer is primarily responsible for processing PDCP SDUs received from the SDAP layer. For example, it processes the received PDCP SDUs to generate PDCP PDUs, which are then delivered to the corresponding RLC layer.
  • the PDCP layer is primarily responsible for receiving PDCP PDUs delivered from the RLC layer, processing them (such as removing the PDCP header), and then delivering them to the SDAP layer.
  • the PDCP layer provides one or more of the following functions: maintenance of the PDCP sender's sequence number (SN), maintenance of the PDCP receiver's SN, packet header compression and decompression, packet encryption and decryption, packet integrity protection, timer-based PDCP SDU discarding, routing in split bearer scenarios, copy transmission, reordering, and in-order delivery.
  • SN sequence number
  • PDCP receiver's SN packet header compression and decompression
  • packet encryption and decryption packet integrity protection
  • timer-based PDCP SDU discarding routing in split bearer scenarios, copy transmission, reordering, and in-order delivery.
  • the PDCP transmitter can maintain a local counter value of TX_NEXT (such as a COUNT value). This counter value can be initially set to 0. Each time a new PDCP PDU is generated, the SN in the corresponding header is set to the value corresponding to TX_NEXT, and TX_NEXT is incremented by 1. TX_NEXT indicates the SN of the next PDCP PDU to be constructed. Furthermore, the PDCP transmitter can sequentially perform header compression, integrity protection, and encryption operations on the PDCP SDU according to the network configuration. For downlink reception, the PDCP receiver can maintain a receive window based on the local counter value. This receive window can be maintained by the following local variables: RX_NEXT, RX_DELIV, and RX_REORD.
  • RX_NEXT indicates the count value corresponding to the next expected PDCP SDU.
  • RX_DELIV indicates the count value corresponding to the next PDCP SDU expected to be sent uplink.
  • the RX_DELIV variable can be used to determine the lower boundary of the receive window.
  • RX_REORD indicates the count value corresponding to the PDCP PDU that triggered the sorting timer.
  • NR systems use an absolute count-based method for maintaining local variables and performing conditional comparisons during data transmission and reception. This improves protocol readability.
  • the count consists of a serial number (SN) and a superframe number, with a fixed size of 32 bits.
  • SN serial number
  • superframe number a serial number
  • the header of the PDCP PDU still includes the SN, not the count, thus avoiding increased overhead for air interface transmission.
  • the RLC layer is located between the PDCP layer and the MAC layer. It can process the PDU data of the PDCP layer into SDU and then hand it over to the MAC layer.
  • the RLC layer provides three transmission modes for different types of data: transparent mode (TM), unacknowledge mode (UM), and acknowledge mode (AM).
  • TM transparent mode
  • UM unacknowledge mode
  • AM acknowledge mode
  • TM the RLC layer does not process data and directly delivers it to the MAC layer. Therefore, TM processing is the simplest and most efficient. TM is mainly used for the transmission of paging messages, system information broadcasts, and signaling radio bearer 0 (SRB 0).
  • UM can also be called unreliable mode.
  • 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 latency.
  • UM can be used for the transmission of services with high real-time requirements such as audio DRB and video.
  • UM while not guaranteeing correct transmission, is more complex.
  • the sender needs to segment (if necessary) and add headers to the RLC SDU to construct the UM data PDU (UM data PDU, UMD PDU).
  • the receiver needs to remove the header and reassemble the UMD PDU (if necessary). Segmentation and reassembly are necessary because the MAC entity informs the UM RLC entity of the MAC layer's acceptable UMD PDU size limit. Due to this size limit, for excessively large RLC SDUs, a single PDU might not contain a complete SDU when constructing it into a UMD PDU. Therefore, the RLC SDU needs to be segmented into multiple RLC SDU segments.
  • Each PDU's data field contains only one RLC SDU segment, and a header is added to construct the UMD PDU before sending it to the MAC layer for transmission.
  • segmentation/reassembly and header addition/removal are the main differences between UM and TM.
  • AM can also be called Reliable Mode.
  • the RLC layer provides full-featured processing.
  • the RLC has the functionality of UM (Unified Management Module) and also supports data reception status feedback. Because retransmissions exist in AM, transmission efficiency is lower. That is, AM supports retransmissions based on status feedback reports, ensuring data transmission reliability but increasing data transmission latency.
  • AM is suitable for dedicated control and dedicated services, generally requiring high reliability. For example, AM can be applied to SRBs other than SRB 0, file transfer protocol (FTP), web browsing, and other error-sensitive services.
  • FTP file transfer protocol
  • AM RLC entities Similar to UM, AM RLC entities also perform segmentation and reassembly, as well as header addition and removal, when necessary. Unlike TM/UM, AM ensures the correctness of data transmission, so the sender must retransmit as needed based on the receiver's reception status.
  • the RLC layer can provide one or more of the following functions: segmentation, concatenation and reassembly of RLC SDUs, reordering of RLC SDUs, error correction based on automatic repeat reQuest (ARQ), filtering of duplicate packets of received RLC SDUs, resegmentation, and discarding of RLC SDUs.
  • segmentation concatenation and reassembly of RLC SDUs
  • reordering of RLC SDUs reordering of RLC SDUs
  • ARQ automatic repeat reQuest
  • the RLC layer provides functionalities applicable to different transmission modes. These are described below.
  • RLC layer segmentation, concatenation, and reassembly of RLC SDUs can be applied to UM and AM.
  • RLC layer segmentation, concatenation, and reassembly of RLC SDUs can be understood as the RLC layer combining multiple PDCP layer PDUs into a single SDU for transmission.
  • the RLC layer's reordering of received RLC SDUs can be applied to UM and AM.
  • the RLC layer can be applied to AM through ARQ error correction.
  • Duplicate packets of RLC SDUs received by the RLC layer can be applied to AM, where the duplicate packets are caused by retransmission.
  • RLC layer resegmentation can be applied in AM.
  • RLC layer resegmentation can refer to the RLC layer resegmenting retransmitted packets.
  • RLC SDU discarding can be applied to AM and UM.
  • Radio bearers are used by network devices to allocate different layer protocol entities and configurations to terminal devices. These can include PDCP entities, RLC entities, MAC entities, and resources allocated by the physical layer. Radio bearers can include DRBs and signaling radio bearers (SRBs).
  • PDCPs and radio bearers can be in one-to-one correspondence, meaning that each radio bearer can be associated with a PDCP entity.
  • Terminal devices in a multi-radio access technology dual connectivity (MR-DC) configuration have three types of radio bearers: master cell group bearer (MCG bearer), secondary cell group bearer (SCG bearer), and separate bearer.
  • MCG bearer master cell group bearer
  • SCG bearer secondary cell group bearer
  • separate bearer separate bearer
  • the radio bearer When the RLC, MAC, and physical protocol stack (the protocol stack can also be understood as a protocol layer or protocol entity, which will not be elaborated on later) of a radio bearer are located on the master node (MN), the radio bearer is called an MCG bearer.
  • the radio bearer When the RLC, MAC, and physical protocol stack of a radio bearer are located on a secondary node (SN), the radio bearer is called an SCG bearer.
  • the split bearer has radio links on both the MN and SN, but only one PDCP protocol stack.
  • the PDCP protocol stack is located on the MN side. In other embodiments, the PDCP protocol stack is located on the SN side.
  • the purpose of the split bearer is to improve the traffic of the radio interface. In some cases, for example, when the PDCP layer allows retransmission of PDCP packets between different links, the split bearer can also improve the reliability of the radio bearer.
  • its associated PDCP entity can be associated with two RLC entities.
  • One RLC entity serves as the primary path, and the other as the secondary path.
  • data packets from the same radio bearer can only undergo serial processing within the current protocol stack.
  • data packets from the same radio bearer can only undergo parallel processing on the primary and secondary paths in scenarios involving repeated transmissions; otherwise, only the primary path performs serial processing.
  • protocol stack design is based on the existing protocol stack architecture, with functional enhancements and optimizations made to the current protocol stack for new service types.
  • the PDCP layer introduces a retransmission mechanism.
  • This design approach has driven the construction of a unified protocol stack architecture that can cover various transmission needs, but this design approach has some drawbacks.
  • the size and complexity of the protocol stack will continue to increase.
  • the current protocol stack design cannot meet the transmission characteristics and requirements of different scenarios. For example, the headers of each protocol layer are designed according to the functions and processes they support, which results in inconsistent header lengths between different protocol layers.
  • the header length of the MAC layer is 2-5 bytes
  • the header length of the RLC layer is 0-5 bytes
  • the header length of the PDCP layer is 2-3 bytes.
  • one protocol stack can handle low-data-rate services and control plane (CP) processes, while the other protocol stack can handle high-data-rate services.
  • CP control plane
  • Figure 3 illustrates two protocol stacks.
  • the two protocol stacks can include an anchor protocol stack (APS) and a fast protocol stack (FPS).
  • APS anchor protocol stack
  • FPS fast protocol stack
  • some communication systems may associate a single radio bearer with multiple protocol layer entities or groups of protocol layer entities to support multiple parallel data processing methods.
  • FPS Fast Per Second
  • RPUs radio processing units
  • one RPU may correspond to one PDCP entity, one RLC entity, and one MAC entity.
  • embodiments of this application provide a method, terminal device, and network device for wireless communication, capable of performing a first operation on a first protocol layer entity or a first protocol layer entity group, thereby facilitating the coordination or management of multiple protocol layer entities or multiple protocol layer entity groups associated with a radio bearer and ensuring normal communication.
  • first protocol layer entity and/or the first protocol layer entity group of this application will be introduced below.
  • the first radio bearer may be associated with multiple protocol layer entities, or in other words, the first radio bearer may be associated with N protocol layer entities, where N is an integer greater than 1.
  • the embodiments of this application do not limit the first wireless bearer.
  • the first wireless bearer may be an MCG bearer.
  • the first wireless bearer may be an SCG bearer.
  • the first wireless bearer may be a separate bearer.
  • the multiple protocol layer entities associated with the first radio bearer can be used to process data in parallel.
  • the multiple protocol layer entities associated with the first radio bearer can process data in parallel under UM.
  • the multiple protocol layer entities associated with the first radio bearer can process data in parallel under AM.
  • the multiple protocol layer entities associated with the first radio bearer can process data in parallel under TM.
  • the multiple protocol layer entities associated with the first radio bearer may belong to the same protocol layer. That is, the first radio bearer may associate multiple protocol layer entities at one protocol layer.
  • the multiple protocol layer entities associated with the first radio bearer may all belong to the PDCP layer, meaning the first radio bearer can associate multiple protocol layer entities at the PDCP layer.
  • the multiple protocol layer entities associated with the first radio bearer may all belong to the RLC layer, meaning the first radio bearer can associate multiple protocol layer entities at the RLC layer.
  • the multiple protocol layer entities associated with the first radio bearer may all belong to the MAC layer, meaning the first radio bearer can associate multiple protocol layer entities at the MAC layer.
  • the first protocol layer entity belongs to a plurality of protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity can be any one or more protocol layer entities among the plurality of protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity can be one or more inactive protocol layer entities (or, one or more protocol layer entities in an inactive state) among the plurality of protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity can be one or more activated protocol layer entities (or, one or more protocol layer entities in an active state) among the plurality of protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity when the first protocol layer entity is activated, can be any one or more protocol layer entities among the multiple protocol layer entities associated with the first radio bearer, or the first protocol layer entity can be one or more inactive protocol layer entities among the multiple protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity when deactivating the first protocol layer entity, can be multiple protocols associated with the first radio bearer. One or more protocol layer entities that are already active in the layer entity.
  • the first protocol layer entity when selecting the first protocol layer entity, can be any one or more protocol layer entities among the plurality of protocol layer entities associated with the first radio bearer, or the first protocol layer entity can be one or more protocol layer entities that are already active among the plurality of protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity may include one of the following: PDCP layer entity, RLC layer entity, MAC layer entity, physical layer entity, or first entity.
  • the first entity described above may be used to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression, data segmentation, and data retransmission.
  • This application does not limit the implementation method of the first entity performing data retransmission.
  • the first entity can perform data retransmission through ARQ, or the first entity can perform data retransmission through HARQ, etc.
  • the first entity may include some or all of the functions of at least two of the following entities: PDCP layer entity, RLC layer entity, MAC layer entity, and physical layer entity. That is, the first entity may combine the functions of at least two of the PDCP layer entity, RLC layer entity, MAC layer entity, and physical layer entity. Therefore, in some embodiments, the first entity may also be referred to as or understood as a combined entity.
  • the aforementioned first protocol layer entity can be associated with a protocol layer.
  • the first protocol layer entity can be a PDCP layer entity associated with the PDCP layer.
  • the first protocol layer entity can be an RLC layer entity associated with the RLC layer.
  • the first protocol layer entity can be a MAC entity associated with the MAC layer.
  • the first protocol layer entity can be a physical layer entity associated with the physical layer.
  • the first protocol layer entity can be a first entity associated with the first protocol layer.
  • the first protocol layer may be a protocol layer introduced in a future communication system (such as a 6G system).
  • the first protocol layer may have one or more of the following functions: data encryption, data integrity protection, packet header compression, data compression, data segmentation, and data retransmission.
  • the first protocol layer may have some or all of the functions of at least two of the following protocol layers: PDCP layer, RLC layer, MAC layer, and physical layer.
  • the first protocol layer may have some or all of the functions of the PDCP layer and some or all of the functions of the RLC layer.
  • the first protocol layer may have some or all of the functions of the RLC layer and some or all of the functions of the MAC layer.
  • the first protocol layer may have some or all of the functions of the PDCP layer, some or all of the functions of the RLC layer, and some or all of the functions of the MAC layer.
  • the first protocol layer may also be referred to as or understood as a combined protocol layer.
  • the PDCP layer described above may include a first sublayer and a second sublayer.
  • the first sublayer may be used to perform one or more of the following functions: assigning sequence numbers, header compression, and data compression.
  • the second sublayer may be used to perform one or more of the following functions: data encryption, data integrity protection, header compression, and data compression.
  • the first sublayer may be located above the second sublayer.
  • the first sublayer may be referred to as or understood as the higher sublayer of the PDCP layer
  • the second sublayer may be referred to as or understood as the lower sublayer of the PDCP layer.
  • the PDCP layer entity mentioned in this application may include an entity of the second sublayer of the PDCP layer, that is, the first protocol layer entity may include an entity of the second sublayer of the PDCP layer.
  • the PDCP layer entity mentioned in this application may perform one or more of the following functions: data encryption, data integrity protection, header compression, and data compression.
  • the first protocol layer entity has been introduced above.
  • the first protocol layer entity group will be introduced below.
  • the first radio bearer may be associated with multiple protocol layer entity groups, or in other words, the first radio bearer may be associated with N protocol layer entity groups, where N is an integer greater than 1. A description of the first radio bearer can be found above and will not be repeated here.
  • the plurality of protocol layer entity groups associated with the first radio bearer can be used to process data in parallel.
  • the plurality of protocol layer entity groups associated with the first radio bearer can process data in parallel under UM.
  • the plurality of protocol layer entity groups associated with the first radio bearer can process data in parallel under AM.
  • the plurality of protocol layer entity groups associated with the first radio bearer can process data in parallel under TM.
  • the multiple protocol entity groups associated with the first radio bearer may be understood as or referred to as multiple RPUs.
  • RPUs For a related introduction to RPUs, please refer to the above.
  • the first protocol layer entity group belongs to a plurality of protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group can be any one or more protocol layer entity groups among the plurality of protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group can be one or more inactive protocol layer entity groups (or, one or more protocol layer entity groups in an inactive state) among the plurality of protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group can be one or more active protocol layer entity groups (or, one or more protocol layer entity groups in an active state) among the plurality of protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group when the first protocol layer entity group is activated, can be any one or more protocol layer entity groups among the multiple protocol layer entity groups associated with the first radio bearer, or the first protocol layer entity group can be one or more inactive protocol layer entity groups among the multiple protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group when deactivating the first protocol layer entity group, can be one or more protocol layer entity groups that are already activated among the multiple protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group when selecting the first protocol layer entity group, can be any one or more protocol layer entity groups among the multiple 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 that are already active among the multiple protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity group may include one or more protocol layer entities. This embodiment of the application does not specifically limit the protocol layer entities included in the first protocol layer entity group.
  • the first protocol layer entity group may include one or more of the following protocol layer entities: PDCP layer entity, RLC layer entity, MAC layer entity, physical layer entity, and first entity.
  • the first protocol layer entity group may include the first entity.
  • the first protocol layer entity group may include PDCP layer entities and RLC layer entities.
  • the first protocol layer entity group may include RLC layer entities and MAC layer entities.
  • the first protocol layer entity group may include MAC layer entities and the first entity.
  • the first protocol layer entity group may include PDCP layer entities, RLC layer entities, and MAC layer entities.
  • the first protocol layer entity group may include RLC layer entities, MAC layer entities, and physical layer entities.
  • the first protocol layer entity group may include a MAC layer entity, a physical layer entity, and a first entity.
  • the first protocol layer entity group may include PDCP layer entities, RLC layer entities, MAC layer entities, and physical layer entities.
  • the terminal device can perform a first operation on a first protocol layer entity or a first protocol layer entity group to coordinate or manage multiple protocol layer entities or multiple protocol layer entity groups associated with a radio bearer, ensuring normal communication.
  • the first operation is described below.
  • the first operation may include one or more of the following operations: activation, deactivation, and selection.
  • the terminal device may activate a first protocol layer entity or a first protocol layer entity group.
  • the terminal device may deactivate a first protocol layer entity or a first protocol layer entity group.
  • the terminal device may select a first protocol layer entity or a first protocol layer entity group.
  • the terminal device may activate a first protocol layer entity or a 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).
  • the terminal device may determine the first protocol layer entity from among the inactive protocol layer entities of a plurality of protocol layer entities associated with the first radio bearer, and activate the first protocol layer entity.
  • the terminal device may determine the first protocol layer entity group from among the inactive protocol layer entity groups of a plurality of protocol layer entity groups associated with the first radio bearer, and activate the first protocol layer entity group.
  • the terminal device may determine the first protocol layer entity from among the activated protocol layer entities of a plurality of protocol layer entities associated with the first radio bearer, and deactivate the first protocol layer entity.
  • the terminal device may determine the first protocol layer entity group from among the activated protocol layer entity groups of a plurality of protocol layer entity groups associated with the first radio bearer, and deactivate the first protocol layer entity group.
  • the terminal device may select a first protocol layer entity from among the activated protocol layer entities of a plurality of protocol layer entities associated with the first radio bearer to perform data transmission using the first protocol layer entity.
  • the terminal device may select a first protocol layer entity group from among the activated protocol layer entity groups of a plurality of protocol layer entity groups associated with the first radio bearer to perform data transmission using the first protocol layer entity group.
  • the terminal device may determine a first protocol layer entity from among the inactive protocol layer entities of a plurality of protocol layer entities associated with a first radio bearer, activate the first protocol layer entity, and select the first protocol layer entity for data transmission.
  • the terminal device may determine a first protocol layer entity group from among the inactive protocol layer entity groups of a plurality of protocol layer entity groups associated with the first radio bearer, activate the first protocol layer entity group, and select the first protocol layer entity group for data transmission.
  • the protocol layer entities that can be activated/deactivated include all (all) protocol layer entities associated with the first radio bearer.
  • the protocol layer entity group that can be activated/deactivated includes all protocol layer entity groups associated with the first radio bearer.
  • the protocol layer entities that can be activated/deactivated include a subset of the protocol layer entities associated with the first radio bearer.
  • the protocol layer entities that can be activated/deactivated include other protocol layer entities besides the main protocol layer entity.
  • the group of protocol layer entities that can be activated/deactivated includes a subset of the protocol layer entity groups associated with the first radio bearer.
  • the group of protocol layer entities that can be activated/deactivated includes other protocol layer entity groups besides the main protocol layer entity group.
  • the plurality of protocol layer entities associated with the first radio bearer include one or more primary protocol layer entities, or the plurality of protocol layer entity groups associated with the first radio bearer include one or more protocol layer entity groups.
  • the primary protocol layer entity or primary protocol layer entity group can always be used for data transmission (always in an active state). In other words, the primary protocol layer entity or primary protocol layer entity group can always be in an active state.
  • the embodiments of this application are not limited to this, and the embodiments of this application may not define the primary protocol layer entity or primary protocol layer entity group. The state is acceptable as long as it can always be used for data transmission.
  • the terminal device can determine the main protocol layer entity or the main protocol layer entity group through configuration information sent by the network device.
  • the terminal device can determine the main protocol layer entity by the identifier of the protocol layer entity, or by the identifier of the protocol layer entity group.
  • the protocol can predefine protocol layer entities identified by a specific value (such as "0") as main protocol layer entities.
  • the protocol can predefine protocol layer entity groups identified by a specific value (such as "0") as main protocol layer entity groups.
  • the activation and/or deactivation of a first protocol layer entity is triggered based on one or more of the following: a first condition, and indication information sent by a network device.
  • the activation and/or deactivation of a first protocol layer entity group is triggered based on one or more of the following: a first condition, and indication information sent by a network device.
  • the activation and/or deactivation of a first protocol layer entity (or a first protocol layer entity group) is triggered based on a first condition.
  • the activation and/or deactivation of a first protocol layer entity (or a first protocol layer entity group) is triggered based on indication information sent by a network device.
  • the activation and/or deactivation of a first protocol layer entity (or a first protocol layer entity group) is triggered based on both a first condition and indication information sent by a network device.
  • the first condition and/or the indication information sent by the network device may be used to determine one or more of the following: whether to activate/deactivate a protocol layer entity associated with the first radio bearer (such as a first protocol layer entity), whether to activate/deactivate a group of protocol layer entities associated with the first radio bearer (such as a first protocol layer entity group), the number of activated/deactivated protocol layer entities, and the number of activated/deactivated protocol layer entity groups.
  • the first condition may be a pre-configured or pre-defined condition; for example, the first condition may be a protocol-predefined condition.
  • the first condition may be a condition configured by the network device, for example, a condition configured by the network device through higher-layer signaling (such as RRC signaling).
  • the first condition may be associated with one or more of the following: whether data has arrived on the first radio bearer, the amount of data to be transmitted on the first radio bearer, the time interval during which the first protocol layer entity has not received data, and the time interval during which the first protocol layer entity group has not received data.
  • a first condition is used to activate a first protocol layer entity or a first protocol layer entity group.
  • the first condition may be associated with one or more of the following information: whether data has arrived on the first radio bearer, and the amount of data to be transmitted on the first radio bearer.
  • a first condition is used to activate a first protocol layer entity or a first protocol layer entity group.
  • the first condition may include one or more of the following: data has arrived on the first radio bearer, and the amount of data to be transmitted on the first radio bearer is greater than or equal to a first threshold.
  • the first condition is used to activate a first protocol layer entity or a first protocol layer entity group, and the first condition may include the arrival of data on the first radio bearer. For example, if multiple protocol layer entities or multiple protocol layer entity groups associated with the first radio bearer are all in a deactivated state, the first condition may include the arrival of data on the first radio bearer.
  • the first condition is used to activate a first protocol layer entity or a first protocol layer entity group.
  • the first condition may include the amount of data to be transmitted by the first radio bearer being greater than or equal to a first threshold. For example, if some protocol layer entities among the multiple protocol layer entities associated with the first radio bearer are active or if a master protocol layer entity exists among the multiple protocol layer entities associated with the first radio bearer, or if some protocol layer entity groups among the multiple protocol layer entity groups associated with the first radio bearer are active or if a master protocol layer entity group exists among the multiple protocol layer entity groups associated with the first radio bearer, the first condition may include the amount of data to be transmitted by the first radio bearer being greater than or equal to the first threshold.
  • whether data has arrived on the first wireless bearer can be used to trigger the terminal device to determine whether the first condition is met. For example, when data arrives on the first wireless bearer, the terminal device can be triggered to determine whether the amount of data to be transmitted on the first wireless bearer is greater than or equal to the first threshold. If the amount of data to be transmitted on the first wireless 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 protocol layer entity group based on the first condition.
  • the first condition may include the arrival of data on the first radio bearer, and the amount of data to be transmitted on the first radio bearer being greater than or equal to a first threshold. For example, if some of the protocol layer entities associated with the first radio bearer are active, or if a master protocol layer entity exists among the multiple protocol layer entities associated with the first radio bearer, or if some of the protocol layer entity groups associated with the first radio bearer are active, or if a master protocol layer entity group exists among the multiple protocol layer entity groups associated with the first radio bearer, the first condition may include the arrival of data on the first radio bearer, and the amount of data to be transmitted on the first radio bearer being greater than or equal to the first threshold.
  • the first threshold is determined based on the 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 the number of activated protocol layer entity groups among the plurality of protocol layer entity groups associated with the first radio bearer. For example, when one protocol layer entity or one protocol layer entity group is activated, the first threshold is 1; when two protocol layer entities or two protocol layer entity groups are activated, the first threshold can be any value. 2. When three protocol layer entities or three protocol layer entity groups have been activated, the first threshold can be set to a value of 3, and so on.
  • the values 2, 3, etc. are determined based on value 1; that is, value 1 can be used as the base value, and other values are calculated based on value 1.
  • value 2 can be equal to twice the value 1
  • value 3 can be equal to three times the value 1, etc. It should be understood that the embodiments of this application are not limited to this; for example, value 2 can be equal to the sum of value 1 and the first offset value, and value 3 can be equal to the sum of value 2 and the first offset value (i.e., value 3 is equal to the sum of value 1 and twice the first offset value).
  • This application does not limit the method for determining whether data has arrived on the first radio bearer. For example, when one or more of the following conditions are met, it can be considered that data has arrived on the first radio bearer: the first sublayer of the PDCP layer receives an SDU from the upper layer (such as the SDAP layer or the application layer), or the first sublayer of the PDCP layer receives a data arrival indication from the upper layer.
  • the first sublayer of the PDCP layer receives an SDU from the upper layer (such as the SDAP layer or the application layer), or the first sublayer of the PDCP layer receives a data arrival indication from the upper layer.
  • the amount of data to be transmitted in the first radio bearer may include one or more of the following: the amount of data in the first sublayer of the PDCP layer, the amount of data to be transmitted in the primary protocol layer entity among a plurality of protocol layer entities, the amount of data to be transmitted in the activated protocol layer entities among a plurality of protocol layer entities, the amount of data to be transmitted in the primary protocol layer entity group among a plurality of protocol layer entity groups, the amount of data to be transmitted in the activated protocol layer entity group among a plurality of protocol layer entity groups, and the amount of data indicated by the application layer that has not yet reached the access layer.
  • the amount of data to be transmitted in the first radio bearer may include one or more of the following: the amount of data in the first sublayer of the PDCP layer, the amount of data to be transmitted in the primary protocol layer entity among multiple protocol layer entities, the amount of data to be transmitted in the activated protocol layer entity among multiple protocol layer entities, and the amount of data indicated by the application layer that has not yet reached the access layer.
  • the amount of data to be transmitted in the first radio bearer may include one or more of the following: the amount of data in the first sublayer of the PDCP layer, the amount of data to be transmitted in the primary protocol layer entity group among multiple protocol layer entity groups, the amount of data to be transmitted in the activated protocol layer entity group among multiple protocol layer entity groups, and the amount of data indicated by the application layer that has not yet reached the access layer.
  • the data volume of the first sublayer of the PDCP layer may include one or more of the following: SDUs received by the first sublayer of the PDCP layer from the upper layer, PDUs processed by the first sublayer of the PDCP layer but not yet delivered to lower layers (such as the second sublayer of the PDCP layer, RLC layer, MAC layer, etc.), and SDUs/PDUs that need to be retransmitted based on status reports (SR).
  • SDUs received by the first sublayer of the PDCP layer from the upper layer PDUs processed by the first sublayer of the PDCP layer but not yet delivered to lower layers (such as the second sublayer of the PDCP layer, RLC layer, MAC layer, etc.), and SDUs/PDUs that need to be retransmitted based on status reports (SR).
  • SR status reports
  • the amount of data that the application layer indicates has not yet reached the access layer may include the amount of data that the application layer indicates has not yet reached the user plane protocol stack.
  • the number of protocol layer entities to be activated among the plurality of protocol layer entities associated with the first radio bearer is determined based on the amount of data to be transmitted in the first radio bearer.
  • the number of protocol layer entity groups to be activated among the plurality of protocol layer entity groups associated with the first radio bearer is determined based on the amount of data to be transmitted in the first radio bearer.
  • the total number of activated protocol layer entities or protocol layer entity groups can be M; if the amount of data to be transmitted in the first radio bearer is greater than a third threshold and less than or equal to a fourth threshold, the total number of activated protocol layer entities or protocol layer entity groups can be P; if the amount of data to be transmitted in the first radio bearer is greater than a fourth threshold, the total number of activated protocol layer entities or protocol layer entity groups can be Q, and so on. In some embodiments, Q > P > M.
  • M, P, and Q represent the total number of protocol layer entities or protocol layer entity groups that need to be activated. That is, if there are already activated protocol layer entities or protocol layer entity groups among the multiple protocol layer entities or multiple protocol layer entity groups associated with the first radio bearer, the number of protocol layer entities or protocol layer entity groups that need to be activated (i.e., those that actually still need to be activated) can be equal to M, P, or Q minus the number of already activated protocol layer entities or protocol layer entity groups.
  • the terminal device can determine the protocol layer entities that need to be activated from among the multiple protocol layer entities associated with the first radio bearer. Alternatively, after determining the number of groups of protocol layer entities that need to be activated, the terminal device can determine the groups of protocol layer entities that need to be activated from among the multiple groups of protocol layer entities associated with the first radio bearer. For example, the terminal device can determine the protocol layer entities that need to be activated from among the inactive protocol layer entities in the multiple protocol layer entities, or the terminal device can determine the groups of protocol layer entities that need to be activated from among the groups of inactive protocol layer entities in the multiple groups of protocol layer entities.
  • the terminal device may determine the protocol layer entity to be activated based on one or more of the following: randomly selecting an inactive protocol layer entity from a plurality of protocol layer entities, sorting the identifiers of the plurality of protocol layer entities, and measurement results corresponding to the plurality of protocol layer entities.
  • the activation of the first protocol layer entity is determined based on one or more of the following: randomly selecting an active protocol layer entity from a plurality of protocol layer entities, sorting the identifiers of the plurality of protocol layer entities, and measurement results corresponding to the plurality of protocol layer entities.
  • the terminal device may determine the protocol layer entity group to be activated based on one or more of the following: randomly selecting an inactive protocol layer entity group from a plurality of protocol layer entity groups, the sorting of the identifiers of the plurality of protocol layer entity groups, and the measurement results corresponding to the plurality of protocol layer entity groups.
  • the activation of the first protocol layer entity group is determined based on one or more of the following: randomly selecting an active protocol layer entity group from an inactive protocol layer entity group from a plurality of protocol layer entity groups, the sorting of the identifiers of the plurality of protocol layer entity groups, and the measurement results corresponding to the plurality of protocol layer entity groups.
  • the terminal device can randomly select from multiple protocols based on the number of protocol layer entities or groups of protocol layer entities that need to be activated.
  • One or more protocol layer entities can be selected from the layer entities to activate, or one or more protocol layer entity groups can be randomly selected from multiple protocol layer entity groups to activate.
  • the terminal device can select one or more protocol layer entities to activate based on the number of protocol layer entities or groups of protocol layer entities that need to be activated, in ascending order of the identifiers of the multiple protocol layer entities, or select one or more protocol layer entity groups to activate in ascending order of the identifiers of the multiple protocol layer entity groups.
  • the terminal device can select one or more protocol layer entities to activate based on the number of protocol layer entities or groups of protocol layer entities that need to be activated, in descending order of the identifiers of the multiple protocol layer entities, or select one or more protocol layer entity groups to activate in descending order of the identifiers of the multiple protocol layer entity groups.
  • the terminal device can select one or more protocol layer entities to activate based on the number of protocol layer entities or groups of protocol layer entities that need to be activated, or select one or more groups of protocol layer entities to activate based on the measurement results corresponding to multiple protocol layer entities. For example, the terminal device can activate protocol layer entities whose measurement results satisfy (e.g., are greater than) a fifth threshold based on the measurement results corresponding to multiple protocol layer entities; or, the terminal device can activate groups of protocol layer entities whose measurement results satisfy a fifth threshold based on the measurement results corresponding to multiple groups of protocol layer entities.
  • the measurement quantity corresponding to the above measurement results may include one or more of the following: reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), and signal to interference plus noise ratio (SINR).
  • RSRP reference signal receiving power
  • RSRQ reference signal receiving quality
  • SINR signal to interference plus noise ratio
  • the terminal device may send a report to the network device.
  • This report may indicate one or more of the following: the number of protocol layer entities or protocol layer entity groups that need to be activated, and the identifiers of protocol layer entities or protocol layer entity groups that do not satisfy the fifth threshold. In this way, the network device can instruct the terminal device on subsequent operations based on the report sent by the terminal device.
  • a first condition is used to deactivate a first protocol layer entity or a first protocol layer entity group.
  • the first condition may be associated with a time interval during which the first protocol layer entity or the first protocol layer entity group has not received data.
  • the first condition may include: the time interval during which the first protocol layer entity or the first protocol layer entity group has not received data is greater than or equal to a first time threshold.
  • the time interval during which a first protocol layer entity or a group of first protocol layer entities does not receive data can be indicated by a timer.
  • a first condition is used to deactivate a first protocol layer entity or a first protocol layer entity group.
  • the first condition may include: a first timer timeout.
  • the first timer may be started or restarted when the first protocol layer entity is activated and/or when data is received, or the first timer may be started or restarted when the first protocol layer entity group is activated and/or when data is received.
  • the first timer may be started when the first protocol layer entity or the first protocol layer entity group is activated, and restarted when the first protocol layer entity or the first protocol layer entity group receives data.
  • receiving data by the first protocol layer entity or the first protocol layer entity group may include receiving SDU/PDU sent by the upper layer, and/or receiving SDU/PDU sent by the lower layer.
  • the first timer may be a timer introduced by a future communication system (such as a 6G system), or the first timer may be an existing timer (such as a discard timer).
  • the conditions for activating and/or deactivating the first protocol layer entity or the first protocol layer entity group have been described above.
  • the instructions for activating and/or deactivating the first protocol layer entity or the first protocol layer entity group are described below.
  • the indication information sent by the network device may be used to indicate which protocol layer entities among the plurality of protocol layer entities associated with the first radio bearer need to be activated and/or deactivated.
  • the indication information sent by the network device may be used to indicate which group of protocol layer entities among the plurality of protocol layer entities associated with the first radio bearer need to be activated and/or deactivated.
  • the indication information sent by the network device may be explicit.
  • the indication information may include the identifiers of protocol layer entities that need to be activated and/or deactivated.
  • the indication information may include the identifiers of groups of protocol layer entities that need to be activated and/or deactivated.
  • the aforementioned indication information may be received via an anchor protocol stack. In some embodiments, the aforementioned indication information may be received via a primary protocol layer entity among a plurality of protocol layer entities associated with the first radio bearer. In some embodiments, the aforementioned indication information may be received via a primary protocol layer entity group among a plurality of protocol layer entity groups associated with the first radio bearer.
  • the indication information sent by the network device may be based on a request from the terminal device (i.e., the request information hereinafter).
  • the request information sent by the terminal device to the network device may be used to request the network device to send the aforementioned indication information.
  • the request information may include one or more of the following: the amount of data to be transmitted in the first radio bearer, measurement results corresponding to multiple protocol layer entities, and measurement results corresponding to multiple protocol layer entity groups.
  • the measurement results corresponding to multiple protocol layer entities may include the measurement results of some or all of the multiple protocol layer entities.
  • the measurement results corresponding to multiple protocol layer entities may include the measurement results of each of the multiple protocol layer entities.
  • the measurement results corresponding to multiple protocol layer entities may include the measurement results of inactive protocol layer entities.
  • the measurement results corresponding to multiple protocol layer entities may include the measurement results of active protocol layer entities.
  • the measurement results corresponding to multiple protocol layer entity groups may include the measurement results of some or all of the protocol layer entity groups.
  • the measurement results corresponding to multiple protocol layer entity groups may include the measurement results of each protocol layer entity group in the multiple protocol layer entity groups.
  • the measurement results corresponding to multiple protocol layer entity groups may include the measurement results of inactive protocol layer entity groups in the multiple protocol layer entity groups.
  • the measurement results corresponding to multiple protocol layer entity groups may include the measurement results of active protocol layer entity groups in the multiple protocol layer entity groups.
  • the terminal device can report measurement results corresponding to multiple protocol layer entities or multiple protocol layer entity groups. In some embodiments, if multiple protocol layers can be associated with a single wireless transmission link (i.e., a unified wireless transmission link), the terminal device can report measurement results based on the number of wireless transmission links.
  • the request information may be sent based on one or more of the following conditions (or, the sending of the request information may be triggered based on one or more of the following conditions): data has arrived on the first radio bearer; there are currently no active protocol layer entities among the plurality of protocol layer entities; there are currently no active protocol layer entity groups among the plurality of protocol layer entity groups; and the amount of data to be transmitted on the first radio bearer is greater than or equal to a first threshold.
  • a first threshold For a detailed explanation of the amount of data to be transmitted on the first radio bearer and the first threshold, please refer to the above text; for brevity, it will not be repeated here.
  • the request information is sent via an anchor protocol stack. In some embodiments, the request information is sent via a primary protocol layer entity among multiple protocol layer entities. In some embodiments, the request information is sent via a primary protocol layer entity group among multiple protocol layer entity groups.
  • the above section introduced the activation and/or deactivation of the first protocol layer entity or the first protocol layer entity group.
  • the following section introduces the selection of the first protocol layer entity or the first protocol layer entity group.
  • the terminal device may select a first protocol layer entity or a first protocol layer entity to perform data transmission (such as PDU transmission). For example, the terminal device may select a first protocol layer entity or a first protocol layer entity to transmit PDUs generated by the first sublayer of the PDCP layer.
  • the first protocol layer entity is selected from the activated protocol layer entities among a plurality of protocol layer entities associated with the first radio bearer.
  • the first protocol layer entity group is selected from the activated protocol layer entity group among a plurality of protocol layer entity groups associated with the first radio bearer.
  • the first protocol layer entity is selected based on one or more of the following: randomly selected from activated protocol layer entities among a plurality of protocol layer entities, the amount of data to be transmitted from activated protocol layer entities among a plurality of protocol layer entities, and the sorting of the identifiers of activated protocol layer entities among a plurality of protocol layer entities.
  • the first protocol layer entity is randomly selected from the active protocol layer entities among a plurality of protocol layer entities.
  • the first protocol layer entity is selected based on the amount of data to be transmitted from the active protocol layer entities among a plurality of protocol layer entities. For example, the terminal device can select a protocol layer entity from the active protocol layer entities whose amount of data to be transmitted is less than or equal to a sixth threshold for data transmission.
  • the determination of the first protocol layer entity can be done in various ways, and this application embodiment does not limit this.
  • the terminal device can randomly select one of the multiple protocol layer entities whose data to be transmitted is less than or equal to the sixth threshold as the first protocol layer entity.
  • the terminal device can select the protocol layer entity with the smallest amount of data to be transmitted from the multiple protocol layer entities whose data to be transmitted is less than or equal to the sixth threshold as the first protocol layer entity.
  • the terminal device can select the protocol layer entity with the smallest (or largest) identifier from the multiple protocol layer entities whose data to be transmitted is less than or equal to the sixth threshold as the first protocol layer entity, and so on.
  • the first protocol layer entity is selected based on the sorting of the identifiers of the active protocol layer entities among a plurality of protocol layer entities. For example, the first protocol layer entity is selected in ascending order based on the identifiers of the active protocol layer entities among a plurality of protocol layer entities. Alternatively, the first protocol layer entity is selected in descending order based on the identifiers of the active protocol layer entities among a plurality of protocol layer entities.
  • the first protocol layer entity is selected based on a ranking of the amount of data to be transmitted from the activated protocol layer entities among a plurality of protocol layer entities, and the identifiers of the activated protocol layer entities among the plurality of protocol layer entities. For example, the terminal device may select the protocol layer entity with the smallest identifier and the amount of data to be transmitted less than or equal to a sixth threshold from the activated protocol layer entities for data transmission. Alternatively, the terminal device may select the protocol layer entity with the largest identifier and the amount of data to be transmitted less than or equal to the sixth threshold from the activated protocol layer entities for data transmission.
  • the first protocol layer entity group is selected based on one or more of the following: randomly selected from multiple protocol layer entity groups. Select from the already activated protocol layer entity groups, the amount of data to be transmitted from the already activated protocol layer entity groups, and the sorting of the identifiers of the already activated protocol layer entity groups.
  • the first protocol layer entity group is randomly selected from the active protocol layer entity groups among a plurality of protocol layer entity groups.
  • the first protocol layer entity group is selected based on the amount of data to be transmitted in the active protocol layer entity groups among a plurality of protocol layer entity groups. For example, the terminal device can select a protocol layer entity group from the active protocol layer entity groups whose amount of data to be transmitted is less than or equal to a sixth threshold for data transmission.
  • the determination of the first protocol layer entity group can be done in various ways, and this application embodiment does not limit this.
  • the terminal device can randomly select one of the multiple protocol layer entity groups whose data to be transmitted is less than or equal to the sixth threshold as the first protocol layer entity group.
  • the terminal device can select the protocol layer entity group with the smallest amount of data to be transmitted from the multiple protocol layer entity groups whose data to be transmitted is less than or equal to the sixth threshold as the first protocol layer entity group.
  • the terminal device can select the protocol layer entity group with the smallest (or largest) identifier from the multiple protocol layer entity groups whose data to be transmitted is less than or equal to the sixth threshold as the first protocol layer entity group, and so on.
  • the first protocol layer entity group is selected based on the sorting of the identifiers of the active protocol layer entity groups among a plurality of protocol layer entity groups. For example, the first protocol layer entity group is selected in ascending order based on the identifiers of the active protocol layer entity groups among a plurality of protocol layer entity groups. Alternatively, the first protocol layer entity group is selected in descending order based on the identifiers of the active protocol layer entity groups among a plurality of protocol layer entity groups.
  • the first protocol layer entity group is selected based on a ranking of the amount of data to be transmitted from the active protocol layer entity groups among multiple protocol layer entity groups and the identifiers of the active protocol layer entity groups among multiple protocol layer entity groups. For example, the terminal device can select the protocol layer entity group with the smallest identifier and the amount of data to be transmitted that is less than or equal to a sixth threshold from the active protocol layer entity groups for data transmission. Alternatively, the terminal device can select the protocol layer entity group with the largest identifier and the amount of data to be transmitted that is less than or equal to the sixth threshold from the active protocol layer entity groups for data transmission.
  • the first protocol layer entity is selected by the terminal device when there is data to be transmitted in the upper protocol layer of the first protocol layer entity. For example, if the first protocol layer entity is an entity of the second sublayer of the PDCP layer, the first protocol layer entity may be selected when there is data to be transmitted in the first sublayer of the PDCP layer or the SDAP layer. Similarly, if the first protocol layer entity is an entity of the RLC layer, the first protocol layer entity may be selected when there is data to be transmitted in the first or second sublayer of the PDCP layer or the SDAP layer.
  • the first protocol layer entity group is selected by the terminal device when there is data to be transmitted in the upper protocol layer of the first protocol layer entity group. For example, if the first protocol layer entity group includes a second sublayer of the PDCP layer and the RLC layer, the first protocol layer entity group may be selected when there is data to be transmitted in the first sublayer of the PDCP layer or the SDAP layer. Similarly, if the first protocol layer entity group includes the RLC layer and the MAC layer, the first protocol layer entity group may be selected when there is data to be transmitted in the first or second sublayer of the PDCP layer or the SDAP layer.
  • Figure 4 is a flowchart illustrating a method for wireless communication provided in an embodiment of this application.
  • the method shown in Figure 4 is described from the perspective of interaction between a terminal device and a network device, which can be, for example, the terminal device 120 and the network device 110 shown in Figure 1.
  • the method shown in Figure 4 includes step S410, which will be described below.
  • step S410 the terminal device performs a first operation on the first protocol layer entity or the first protocol layer entity group.
  • the method of FIG4 may further include step S406.
  • the network device sends indication information to the terminal device.
  • the indication information may be used to indicate which protocol layer entities among a plurality of protocol layer entities need to be activated and/or which protocol layer entities need to be deactivated.
  • the indication information may be used to indicate which protocol layer entity groups among a plurality of protocol layer entity groups need to be activated and/or which protocol layer entity groups need to be deactivated.
  • the method of FIG4 may further include step S404.
  • step S404 the terminal device sends request information to the network device. This request information may be used to request the network device to send indication information.
  • the method of FIG4 may further include step S402.
  • step S402 the network device sends configuration information to the terminal device.
  • the configuration information may be used to determine multiple protocol layer entities or multiple protocol layer entity groups associated with a first radio bearer.
  • the configuration information used to determine multiple protocol layer entities or multiple protocol layer entity groups associated with a first radio bearer includes one or more of the following: the configuration information is used to determine whether the first radio bearer is associated with multiple protocol layer entities; the configuration information is used to determine the first... Whether a radio bearer is associated with multiple protocol layer entity groups, the configuration information is used to determine the number of multiple protocol layer entities associated with the first radio bearer, and the configuration information is used to determine the number of multiple protocol layer entity groups associated with the first radio bearer.
  • the configuration information may be used to determine the primary protocol layer entity among a plurality of protocol layer entities associated with the first radio bearer, or the configuration information may be used to determine the primary protocol layer entity group among a plurality of protocol layer entity groups associated with the first radio bearer.
  • the terminal device may establish a corresponding protocol layer entity or protocol layer entity group based on the configuration information sent by the network device.
  • FIG. 5 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application.
  • the terminal device 500 shown in Figure 5 includes 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 including 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 a first radio bearer.
  • 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.
  • the first condition is associated with one or more of the following: whether data has arrived on the first radio bearer; the amount of data to be transmitted on the first radio bearer; the time interval during which the first protocol layer entity has not received data; and the time interval during which the first protocol layer entity group has not received data.
  • the first condition is used to activate the first protocol layer entity or the first protocol layer entity group, and the first condition includes one or more of the following: data has arrived on the first radio bearer; the amount of data to be transmitted on the first radio bearer is greater than or equal to a first threshold.
  • the first threshold is determined based on the number of activated protocol layer entities among the plurality of protocol layer entities, or the first threshold is determined based on the number of activated protocol layer entity groups among the plurality of protocol layer entity groups.
  • the number of protocol layer entities that need to be activated among the plurality of protocol layer entities or the number of protocol layer entity groups that need to be activated among the plurality of protocol layer entity groups are determined based on the amount of data to be transmitted in the first radio bearer.
  • the activation of the first protocol layer entity is determined based on one or more of the following: randomly selecting an active protocol layer entity from among the plurality of inactive protocol layer entities, the sorting of the identifiers 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 active protocol layer entity group from among the plurality of protocol layer entity groups, the sorting of the identifiers of the plurality of protocol layer entity groups, and the measurement results corresponding to the plurality of protocol layer entity groups.
  • the first condition is used to deactivate the first protocol layer entity or the first protocol layer entity group.
  • the first condition includes: a first timer timeout, wherein the first timer is started or restarted when the first protocol layer entity is activated and/or when data is received, or the first timer is started or restarted when the first protocol layer entity group is activated and/or when data is received.
  • the terminal device further includes: a first receiving module 520, configured to receive indication information sent by a network device, the indication information being used to indicate which protocol layer entities among the plurality of protocol layer entities need to be activated and/or which protocol layer entities need to be deactivated; or, the indication information being used to indicate which protocol layer entity groups among the plurality of protocol layer entity groups need to be activated and/or which protocol layer entity groups need to be deactivated.
  • a first receiving module 520 configured to receive indication information sent by a network device, the indication information being used to indicate which protocol layer entities among the plurality of protocol layer entities need to be activated and/or which protocol layer entities need to be deactivated.
  • 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; wherein, the request information includes one or more of the following: the amount of data to be transmitted in the first radio bearer, the measurement results corresponding to the plurality of protocol layer entities, and the measurement results corresponding to the plurality of protocol layer entity groups.
  • the request information is sent based on one or more of the following conditions: data has arrived on the first radio bearer; there is currently no activated protocol layer entity among the plurality of protocol layer entities; there is currently no activated protocol layer entity group among the plurality of protocol layer entity groups; the amount of data to be transmitted on the first radio bearer is greater than or equal to a first threshold.
  • the request information is sent through the anchor protocol stack, or the request information is sent through the main protocol layer entity among the plurality of protocol layer entities, or the request information is sent through the main protocol layer entity group among the plurality of protocol layer entity groups.
  • the indication information is received through the anchor protocol stack, or the indication information is received through the main protocol layer entity among the plurality of protocol layer entities, or the indication information is received through the main protocol layer entity group among the plurality of protocol layer entity groups.
  • the first protocol layer entity is selected based on one or more of the following: randomly selected from the plurality of activated protocol layer entities, wherein the data to be transmitted of the activated protocol layer entities is... The quantity, the sorting of the identifiers 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 selected from the activated protocol layer entity groups in the plurality of protocol layer entities, the amount of data to be transmitted in the activated protocol layer entity groups in the plurality of protocol layer entity groups, and the sorting of the identifiers of the activated protocol layer entity groups in the plurality of protocol layer entity groups.
  • the first protocol layer entity is selected by the terminal device when there is data to be transmitted in the 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 in the upper protocol layer of the first protocol layer entity group.
  • the amount of data to be transmitted in the first radio bearer includes one or more of the following: the amount of data in the first sublayer of the PDCP layer, the amount of data to be transmitted in the primary protocol layer entity among the plurality of protocol layer entities, the amount of data to be transmitted in the activated protocol layer entities among the plurality of protocol layer entities, the amount of data to be transmitted in the primary protocol layer entity group among the plurality of protocol layer entity groups, the amount of data to be transmitted in the activated protocol layer entity group among the plurality of protocol layer entity groups, and the amount of data indicated by the application layer that has not yet reached the access layer.
  • the PDCP layer includes a first sublayer and a second sublayer, wherein the first sublayer is configured to perform one or more of the following functions: assigning sequence numbers, packet 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, packet header compression, and data compression.
  • the first protocol layer entity includes one of the following: PDCP layer entity, RLC layer entity, MAC layer entity, physical layer entity, and first entity;
  • the first protocol layer entity group includes one or more of the following: PDCP layer entity, RLC layer entity, MAC layer entity, physical layer entity, and first entity; wherein the first entity is used to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression, data segmentation, and data retransmission.
  • the PDCP layer entity includes an entity of a second sublayer of the PDCP layer, the second sublayer being used to perform one or more of the following functions: data encryption, data integrity protection, packet header compression, and data compression.
  • the terminal device further includes: a second receiving module, configured to receive configuration information sent by a network device, the configuration information being used to determine the plurality of protocol layer entities or the plurality of protocol layer entity groups.
  • the plurality of protocol layer entities or the group of the plurality of protocol layer entities are used to process data in parallel.
  • the execution module 510 may be a processor 710.
  • the terminal device 500 may also include a memory 720 and a transceiver 730, as shown in FIG7.
  • FIG. 6 is a schematic diagram of the structure of a network device provided in an embodiment of this application.
  • the network device 600 shown in Figure 6 may include a first transmitting module 610.
  • the first transmitting module 610 may be used to transmit indication information to a terminal device.
  • the indication information is used to indicate which protocol layer entities need to be activated and/or which protocol layer entities need to be deactivated among a plurality of protocol layer entities associated with a first radio bearer, wherein the plurality of protocol layer entities belong to the same protocol layer; or, the indication information is used to indicate which protocol layer entity group needs to be activated and/or which protocol layer entity group needs to be deactivated among a plurality of protocol layer entity groups associated with a first radio bearer.
  • 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: the amount of data to be transmitted in the first radio bearer, the measurement results corresponding to the plurality of protocol layer entities, and the measurement results corresponding to the plurality of protocol layer entity groups.
  • the request information is sent based on one or more of the following conditions: data has arrived on the first radio bearer; there is currently no activated protocol layer entity among the plurality of protocol layer entities; there is currently no activated protocol layer entity group among the plurality of protocol layer entity groups; the amount of data to be transmitted on the first radio bearer is greater than or equal to a first threshold.
  • the first threshold is determined based on the number of activated protocol layer entities among the plurality of protocol layer entities, or the first threshold is determined based on the number of activated protocol layer entity groups among the plurality of protocol layer entity groups.
  • the request information is sent through the anchor protocol stack, or the request information is sent through the main protocol layer entity among the plurality of protocol layer entities, or the request information is sent through the main protocol layer entity group among the plurality of protocol layer entity groups.
  • the indication information is received through the anchor protocol stack, or the indication information is received through the main protocol layer entity among the plurality of protocol layer entities, or the indication information is received through the main protocol layer entity group among the plurality of protocol layer entity groups.
  • the number of protocol layer entities that need to be activated among the plurality of protocol layer entities or the number of protocol layer entity groups that need to be activated among the plurality of protocol layer entity groups are determined based on the amount of data to be transmitted in the first radio bearer.
  • the amount of data to be transmitted in the first radio bearer includes one or more of the following: the amount of data in the first sublayer of the PDCP layer, the amount of data to be transmitted in the primary protocol layer entity among the plurality of protocol layer entities, the amount of data to be transmitted in the activated protocol layer entities among the plurality of protocol layer entities, the amount of data to be transmitted in the primary protocol layer entity group among the plurality of protocol layer entity groups, the amount of data to be transmitted in the activated protocol layer entity group among the plurality of protocol layer entity groups, and the amount of data indicated by the application layer that has not yet reached the access layer.
  • the PDCP layer includes a first sublayer and a second sublayer, the first sublayer being configured to perform one of the following functions One or more: assigning sequence numbers, packet header compression, data compression; the second sublayer is used to perform one or more of the following functions: data encryption, data integrity protection, packet header compression, data compression.
  • the plurality of protocol layer entities includes one of the following: PDCP layer entity, RLC layer entity, MAC layer entity, physical layer entity, and a first entity; any one of the plurality of protocol layer entity groups includes one or more of the following: PDCP layer entity, RLC layer entity, MAC layer entity, physical layer entity, and a first entity; wherein the first entity is used to perform one or more of the following functions: data encryption, data integrity protection, header compression, data compression, data segmentation, and data retransmission.
  • the PDCP layer entity includes an entity of a second sublayer of the PDCP layer, the second sublayer being used to perform one or more of the following functions: data encryption, data integrity protection, packet header compression, and data compression.
  • the network device further includes: 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.
  • the plurality of protocol layer entities or the group of the plurality of protocol layer entities are used to process data in parallel.
  • the first transmitting module 610 may be a processor 710.
  • the network device 600 may also include a memory 720 and a transceiver 730, as shown in FIG7.
  • Figure 7 is a schematic structural diagram of a communication device according to an embodiment of this application.
  • the dashed lines in Figure 7 indicate that the unit or module is optional.
  • This device 700 can be used to implement the methods described in the above method embodiments.
  • Device 700 can be a chip, a terminal device, or a network device.
  • the apparatus 700 may include one or more processors 710.
  • the processor 710 may support the apparatus 700 in implementing the methods described in the preceding method embodiments.
  • the processor 710 may be a general-purpose processor or a special-purpose processor.
  • the processor may be a central processing unit (CPU).
  • the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the apparatus 700 may also include one or more memories 720.
  • the memories 720 store a program that can be executed by the processor 710, causing the processor 710 to perform the methods described in the preceding method embodiments.
  • the memories 720 may be independent of the processor 710 or integrated within the processor 710.
  • the device 700 may also include a transceiver 730.
  • the processor 710 can communicate with other devices or chips via the transceiver 730.
  • the processor 710 can send and receive data with other devices or chips via the transceiver 730.
  • This application also provides a computer-readable storage medium for storing a program.
  • This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.
  • the application also provides a computer program product.
  • the computer program product includes a program.
  • This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.
  • This application also provides a computer program.
  • This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.
  • the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship.
  • a instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and/or other information.
  • correlate can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.
  • the term “comprising” can refer to direct inclusion or indirect inclusion.
  • “comprising” in the embodiments of this application can be replaced with “instructing” or “used to determine”.
  • "A includes B” can be replaced with "A instructs B” or "A is used to determine B”.
  • predefined or “preconfigured” can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices).
  • predefined can refer to what is defined in the protocol.
  • the "protocol” may refer to a standard protocol in the field of communications, such as the LTE protocol, NR protocol, etc. This application does not limit the scope of related protocols to be applied in future communication systems.
  • the term "and/or” is merely a description of the relationship between related objects, indicating that three relationships can exist.
  • a and/or B can represent: A existing alone, A and B existing simultaneously, or B existing alone.
  • the character "/" in this document generally indicates that the preceding and following related objects have an "or" relationship.
  • the disclosed systems, apparatuses, and methods can be implemented in other ways.
  • the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separate.
  • the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
  • the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
  • implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof.
  • software When implemented using software, it can be implemented entirely or partially 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 this application are generated.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte à un procédé de communication sans fil, à un dispositif terminal et à un dispositif réseau. Le procédé de communication sans fil comprend les étapes suivantes : un dispositif terminal exécute une première opération sur une première entité de couche de protocole ou sur un groupe de premières entités de couche de protocole, la première opération comprenant une ou plusieurs des actions suivantes : une activation, une désactivation et une sélection ; la première entité de couche de protocole fait partie d'une pluralité d'entités de couche de protocole associées à une première porteuse radio, et la pluralité d'entités de couche de protocole fait partie d'une même couche de protocole ; ou le groupe de premières entités de couche de protocole fait partie d'une pluralité de groupes d'entités de couche de protocole associés à la première porteuse radio.
PCT/CN2024/112912 2024-08-16 2024-08-16 Procédé de transmission sans fil, dispositif termina, et dispositif réseau Pending WO2026036408A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/112912 WO2026036408A1 (fr) 2024-08-16 2024-08-16 Procédé de transmission sans fil, dispositif termina, et dispositif réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/112912 WO2026036408A1 (fr) 2024-08-16 2024-08-16 Procédé de transmission sans fil, dispositif termina, et dispositif réseau

Publications (1)

Publication Number Publication Date
WO2026036408A1 true WO2026036408A1 (fr) 2026-02-19

Family

ID=98780642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/112912 Pending WO2026036408A1 (fr) 2024-08-16 2024-08-16 Procédé de transmission sans fil, dispositif termina, et dispositif réseau

Country Status (1)

Country Link
WO (1) WO2026036408A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391639A (zh) * 2017-08-02 2019-02-26 维沃移动通信有限公司 一种激活及去激活数据复制的方法及终端
CN110225600A (zh) * 2018-03-01 2019-09-10 华为技术有限公司 通信方法及装置
CN117395611A (zh) * 2022-07-05 2024-01-12 华为技术有限公司 通信方法及装置
CN117917177A (zh) * 2021-09-15 2024-04-19 高通股份有限公司 针对辅小区组去激活的分组数据汇聚协议处理

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391639A (zh) * 2017-08-02 2019-02-26 维沃移动通信有限公司 一种激活及去激活数据复制的方法及终端
CN110225600A (zh) * 2018-03-01 2019-09-10 华为技术有限公司 通信方法及装置
CN117917177A (zh) * 2021-09-15 2024-04-19 高通股份有限公司 针对辅小区组去激活的分组数据汇聚协议处理
CN117395611A (zh) * 2022-07-05 2024-01-12 华为技术有限公司 通信方法及装置

Similar Documents

Publication Publication Date Title
KR102376115B1 (ko) 차세대 이동 통신 시스템에서 pdcp 버전 변경에 따른 재설정 방법 및 장치
KR102816414B1 (ko) 무선 통신 시스템에서 핸드 오버 절차를 수행하는 방법 및 장치
US20200045766A1 (en) Wireless node communication method and apparatus in wireless communication system
KR102856249B1 (ko) 무선 통신 시스템에서 데이터를 송수신하는 방법 및 장치
KR20030060026A (ko) 고속하향링크패킷접속（ｈｓｄｐａ）시스템에서재정리버퍼의 설정방법
CN113766571B (zh) 数据传输的方法和通信设备
KR20200032560A (ko) 무선 통신 시스템에서 데이터를 송수신하는 방법 및 장치
WO2021056589A1 (fr) Procédé et appareil de transmission de données
US12556301B2 (en) Wireless communication method and apparatus
US20240284287A1 (en) Method and device for handover without suspension of data transmission and reception in next generation mobile communication system
CN102934388A (zh) 无线电接口共同重配置
WO2022120541A1 (fr) Procédé et appareil de transmission de données
KR102597038B1 (ko) 무선 통신 시스템에서의 무선 노드 통신 방법 및 장치
KR102656608B1 (ko) 무선 통신 시스템에서 무선 노드 통신 방법 및 장치
CN116156560B (zh) 无线通信方法及装置
US20250175285A1 (en) Method for communication, communication device, and network device
JPWO2020090442A1 (ja) 無線通信方法及び装置
WO2026036408A1 (fr) Procédé de transmission sans fil, dispositif termina, et dispositif réseau
WO2023071699A1 (fr) Procédé de transmission de données pour un service de multidiffusion, dispositif de communication et moyen de stockage
WO2022056746A1 (fr) Procédé de communication et appareil de communication
WO2026000379A1 (fr) Procédé de communication et dispositifs de communication
US20240381177A1 (en) Wireless communication method and apparatus
WO2025147912A1 (fr) Procédé de communication sans fil et dispositif de communication
TW202516978A (zh) 一種通信方法及裝置
KR20260017759A (ko) 무선 통신 시스템에서 핸드오버를 위한 pdcp 계층 일련번호 간격 보고 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24951085

Country of ref document: EP

Kind code of ref document: A1