Information transmission method and communication apparatus

Abstract

The present application relates to the field of communications, and particularly relates to an information transmission method and a communication apparatus. An RLC layer collectively packages received control information or service information into RLC data PDUs, and then sends same in a chronological order of receipt, such that the transmission delay of the control information is large, thereby degrading the user-plane performance. In the method provided in the present application, a C-RLC entity independent of an RLC entity is configured, and control information is sent to the C-RLC entity and service information is sent to the RLC entity, such that a queuing delay introduced due to the control information and the service information queuing up for sending in a cache of the RLC entity can be avoided, and the transmission speed of the control information can be increased, thereby improving the user-plane performance.

Description

Information transmission methods and communication devices Technical Field

[0001] This application relates to the field of communication technology, and in particular to information transmission methods and communication devices. Background Technology

[0002] The New Radio (NR) air interface employs a layered protocol stack design. Specifically, the NR user plane protocol stack includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the physical layer. In the user plane protocol design, the transmitting and receiving ends can exchange control information from the protocol layers, such as control information from the PDCP layer. This control information is used to control the protocol layer to perform functions such as variable updates, transmit / receive window updates, buffer updates, packet dropping, packet retransmission, status reporting, and compression. Upon receiving the control information, the receiving end performs corresponding processing based on the type of control information received.

[0003] Significant transmission latency of control information can lead to performance degradation on the user plane. Therefore, reducing the transmission latency of control information is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] This application provides an information transmission method and apparatus to reduce the transmission latency of control information and improve user plane performance.

[0005] In a first aspect, embodiments of this application provide an information transmission method, which can be executed by a communication device, or by a component of the communication device, such as a processor, chip, or chip system of the communication device, or by a logic module or software that can implement all or part of the functions of the communication device.

[0006] The method provided in the first aspect includes: a first entity of a communication device sending service information to at least one second entity of the communication device, and the first entity of the communication device sending control information of the first entity to at least one third entity of the communication device; the first entity is used to implement a packet data aggregation function, the second entity is used to implement a wireless link control function, and the third entity is used to implement the function of the first entity or the function of the second entity; when the third entity is used to implement the function of the second entity, the second entity receiving the service information is independent of the third entity receiving the control information.

[0007] In this embodiment, by sending control information to a third entity independent of the second entity, the queuing delay caused by the control information and service information queuing in the second entity's cache can be avoided, thereby improving the transmission speed of control information and thus improving user plane performance.

[0008] The method provided in the first aspect further includes: when a third entity of the communication device is used to implement the function of a first entity of the communication device, the third entity of the communication device sends control information and instruction information to a fourth entity of the communication device, wherein the instruction information is used to instruct the first entity and the fourth entity is used to implement the wireless link control function; or, when a third entity of the communication device is used to implement the function of a second entity of the communication device, the third entity of the communication device sends control information and instruction information to a fourth entity of the communication device, wherein the instruction information is used to instruct the first entity and the fourth entity is used to implement the media access control function.

[0009] In this embodiment of the application, when multiple first entities submit control information to a third entity, the indication information is used to mark which specific first entity the control information comes from, so that after the receiving third entity receives the control information, it can submit it to the corresponding receiving first entity for processing.

[0010] The method provided in the first aspect further includes: when the third entity and the fourth entity of the communication device are entities included in the user plane bearer, the third entity of the communication device sends control information and instruction information to the fourth entity of the communication device; or, when the third entity and the fourth entity of the communication device are entities included in the control plane bearer, the third entity of the communication device is further used to send control information of the fifth entity of the communication device to the fourth entity of the communication device, the fifth entity being used to implement the radio resource control function.

[0011] In this embodiment, by sending control information to a third entity belonging to the control plane, the queuing latency introduced by the control information and service information queuing together in the second entity's cache can be avoided, thus improving the transmission speed of control information and thereby enhancing user plane performance. Furthermore, this embodiment does not require additional configuration of a third entity, reducing the number of entities and simplifying processing complexity.

[0012] In one possible implementation, when there are multiple third entities, the first entity sends control information to the third entity with the fewest cached data packets or the smallest cached data volume among the multiple third entities.

[0013] In one possible implementation, when multiple first entities are associated with the same third entity, the control information of the multiple first entities can be sent to the third entity in a first-in-first-out (FIFO) or first-in-last-out (FILO) manner.

[0014] In one possible implementation, the first entity is an entity of the Packet Data Convergence Protocol (PDCP) layer, the second entity is an entity of the Radio Link Control (RLC) layer, the third entity is an entity of the PDCP layer or the RLC layer, and the fourth entity is an entity of the RLC layer or the Media Access Control (MAC) layer.

[0015] In one possible implementation, the first entity is used to implement the service data adaptation function, the second entity is used to implement the packet data aggregation function, the third entity is used to implement either the service data adaptation function or the packet data aggregation function, and the fourth entity is used to implement either the packet data aggregation function or the radio link control function.

[0016] In one possible implementation, the first entity is an entity of the Service Data Adaptation Protocol (SDAP) layer, the second entity is an entity of the PDCP layer, the third entity is an entity of the SDAP layer or the PDCP layer, and the fourth entity is an entity of the PDCP layer or the RLC layer.

[0017] In one possible implementation, the first entity is used to implement the service data adaptation function, the second entity is used to implement the packet data aggregation function, the third entity is used to implement the wireless link control function, and the fourth entity is used to implement the media access control function.

[0018] In one possible implementation, the first entity is an entity of the SDAP layer, the second entity is an entity of the PDCP layer, the third entity is an entity of the RLC layer, and the fourth entity is an entity of the MAC layer.

[0019] In one possible implementation, the communication device may be a terminal device or a network device.

[0020] In one possible implementation, the communication device can be a master node (MN) or a secondary node (SN).

[0021] In one possible implementation, the third entity associated with the first entity of a bearer terminated by the master node is configured to use master cell group (MCG) resources, that is, the master node determines the association between the first entity and the third entity of the bearer terminated by the master node; the third entity associated with the first entity of a bearer terminated by the secondary node is configured to use secondary cell group (SCG) resources, that is, the secondary node determines the association between the first entity and the third entity of the bearer terminated by the secondary node.

[0022] Secondly, embodiments of this application provide an information transmission method, which can be executed by a communication device, or by a component of the communication device, such as the processor, chip or chip system of the communication device, or by a logic module or software that can implement all or part of the functions of the communication device.

[0023] The method provided in the second aspect includes: a first entity of the communication device sending data packets and indication information to a second entity of the communication device, the indication information being used to indicate the priority of the data packets; and based on the priority of the data packets, the second entity of the communication device sending data packets to a third entity of the communication device.

[0024] In one possible implementation, when the indication information indicates that the data packet includes control information, the second entity sends the data packet to the third entity preferentially.

[0025] In one possible implementation, when the indication information indicates that the data packet is of a type that needs to be prioritized, the second entity sends the data packet to the third entity with priority.

[0026] In this embodiment, based on the priority of the data packets indicated by the indication information, the second entity prioritizes the transmission of control information or data packets that need to be processed first, which can improve the transmission speed of control information or data packets that need to be processed first, thereby improving user plane performance.

[0027] In one possible implementation, when the communication device adopts a separate architecture of central unit (CU) and distributed unit (DU), the CU submits a first data frame to the DU, and the first data frame includes the indication information.

[0028] In one possible implementation, the first entity is used to implement packet data aggregation function, the second entity is used to implement wireless link control function, and the third entity is used to implement media access control function.

[0029] In one possible implementation, the first entity is an entity of the PDCP layer, the second entity is an entity of the RLC layer, and the third entity is an entity of the MAC layer.

[0030] In one possible implementation, the communication device may be a terminal device or a network device.

[0031] Thirdly, embodiments of this application provide a data transmission method, which can be executed by a first communication device, or by a component of the first communication device, such as the processor, chip, or chip system of the first communication device, or by a logic module or software that can implement all or part of the functions of the first communication device.

[0032] The method provided in the third aspect includes: a first entity of a first communication device receiving first data from a first entity of a second communication device, the first data not including control information of the first entity of the second communication device; the first entity of the first communication device sending first indication information to a second entity of the first communication device, the first indication information indicating that the first entity of the first communication device will no longer wait for the second data to be received from the first entity of the second communication device, the second data not including control information of the first entity of the second communication device; and based on the first indication information, the second entity of the first communication device determining whether to update the set of data to be received.

[0033] In one possible implementation, the set of data to be received is represented by a receiving window, which includes a set of sequence numbers of the data to be received, and the lower boundary of the receiving window is the minimum value in the set of sequence numbers of the data to be received.

[0034] In one possible implementation, when the sequence number of the second data is equal to the lower boundary of the receiving window, the second entity of the first communication device updates the lower boundary of the receiving window to the sequence number of the second data plus 1.

[0035] In this embodiment of the application, the first entity of the first communication device indicates to the second entity of the first communication device that it will no longer wait for the data packet to be received. The second entity of the first communication device regards the data packet as successfully received, and then updates the receiving window and no longer receives the data packet, which can improve the utilization rate of air interface resources.

[0036] The method provided in the third aspect further includes: a second entity of the first communication device sending a second instruction message to a second entity of the second communication device, the second instruction message being used to instruct the second entity of the second communication device to stop sending the second data.

[0037] In one possible implementation, the second indication information includes an acknowledgment (ACK) message associated with the second data.

[0038] In one possible implementation, the second indication information does not include negative acknowledgment (NACK) information associated with the second data.

[0039] The second type of information is, for example, an RLC status report.

[0040] In this embodiment of the application, the second entity of the first communication device instructs the second entity of the second communication device to stop sending the second data, which can terminate the unnecessary data packet retransmission process and improve the utilization rate of air interface resources.

[0041] The method provided in the third aspect further includes: when the second entity of the first communication device receives all or part of the second data, the second entity of the first communication device discards all or part of the second data.

[0042] In one possible implementation, the first entity is used to implement the packet data aggregation function, and the second entity is used to implement the wireless link control function.

[0043] In one possible implementation, the first entity is an entity of the PDCP layer, and the second entity is an entity of the RLC layer.

[0044] In one possible implementation, the first communication device and the second communication device are respectively a terminal device and a network device; or, the first communication device and the second communication device are respectively a network device and a terminal device; or, the first communication device and the second communication device are respectively a first terminal device and a second terminal device.

[0045] Fourthly, this application provides a communication device that has the functions of the first aspect described above. For example, the communication device includes modules, units, or means that perform the operations involved in the first aspect. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0046] Fifthly, this application provides a communication device that has the functions of the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect above. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0047] Sixthly, this application provides a communication device that has the functions of the third aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the third aspect above. The modules, units, or means can be implemented by software, hardware, or a combination of software and hardware.

[0048] In a seventh aspect, this application provides a communication device comprising a memory and one or more processors. The memory stores part or all of the necessary computer programs or instructions for implementing the functions involved in any of the possible designs of the first to third aspects described above. The one or more processors are executable to carry out the computer programs or instructions, which, when executed, cause the communication device to implement the methods of any of the possible designs or implementations of the first to third aspects described above.

[0049] In one possible design, the communication device may further include an interface circuit, wherein the processor is used to communicate with other devices or components through the interface circuit.

[0050] In one possible design, the communication device may also include the memory.

[0051] The aforementioned communication device may be a terminal, a communication module in a terminal, or a chip in a terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip that contains a modem module.

[0052] The aforementioned communication device may be a base station, or a communication module in a base station, or a chip in a base station that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0053] Eighthly, this application provides a communication system for implementing the methods in any of the possible designs of the first to third aspects described above.

[0054] Ninthly, this application provides a computer-readable storage medium storing computer-readable instructions that, when read and executed by a computer, cause the computer to perform any of the possible designs in the first to third aspects described above.

[0055] In a tenth aspect, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform any of the possible designs in the first to third aspects described above.

[0056] In one aspect, this application provides a chip including a processor and a communication interface for communicating with external or internal devices, and the processor for implementing the methods in any of the possible designs of the first to third aspects described above. Attached Figure Description

[0057] Figure 1 is a schematic diagram of a communication system provided in an embodiment of this application;

[0058] Figure 2 is a schematic diagram of the layered protocol stack design used in the NR air interface provided in the embodiments of this application;

[0059] Figure 3 is a schematic diagram of data transmission provided in an embodiment of this application;

[0060] Figure 4 is a flowchart illustrating an information transmission method provided in an embodiment of this application;

[0061] Figure 5A is a schematic diagram of a protocol stack configured with C-RLC entities provided in an embodiment of this application;

[0062] Figure 5B is a schematic diagram of another protocol stack configured with C-RLC entities provided in an embodiment of this application;

[0063] Figure 5C is a schematic diagram of a protocol stack configured with a C-RLC entity in a dual-connectivity scenario provided by an embodiment of this application;

[0064] Figure 6A is a schematic diagram of a protocol stack configured with a C-PDCP entity provided in an embodiment of this application;

[0065] Figure 6B is a schematic diagram of another protocol stack configured with a C-PDCP entity provided in an embodiment of this application;

[0066] Figure 6C is a schematic diagram of a protocol stack with a C-PDCP entity configured in a dual-connectivity scenario provided by an embodiment of this application;

[0067] Figure 7A is a schematic diagram of another protocol stack configured with a C-PDCP entity provided in an embodiment of this application;

[0068] Figure 7B is a schematic diagram of another protocol stack configured with a C-PDCP entity provided in an embodiment of this application;

[0069] Figure 7C is a schematic diagram of a protocol stack configured with a C-PDCP entity in another dual-connection scenario provided by an embodiment of this application;

[0070] Figure 8A is a schematic diagram of the structure of a C-RLC data PDU provided in an embodiment of this application;

[0071] Figure 8B is a schematic diagram of the structure of a C-PDCP data PDU provided in an embodiment of this application;

[0072] Figure 8C is a schematic diagram of the structure of another C-PDCP data PDU provided in the embodiment of this application;

[0073] Figure 9 is a flowchart illustrating another information transmission method provided in an embodiment of this application;

[0074] Figure 10 is a schematic diagram of the structure of a data frame provided in an embodiment of this application;

[0075] Figure 11 is a flowchart illustrating a data transmission method provided in an embodiment of this application;

[0076] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0077] Figure 13 is a schematic diagram of another communication device provided in an embodiment of this application;

[0078] Figure 14 is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0079] The embodiments of this application will be further described below with reference to the accompanying drawings.

[0080] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0081] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0082] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the correspondence between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0083] The system architecture of the embodiments of this application is described below:

[0084] To facilitate understanding of the technical solutions in the embodiments of this application, the system architecture of the methods provided in the embodiments of this application will be briefly described below. It is understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions in the embodiments of this application and does not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0085] The technical solutions of this application embodiment can be applied to various communication systems, such as satellite communication systems and traditional mobile communication systems. The satellite communication system can be integrated with traditional mobile communication systems (i.e., terrestrial communication systems). Examples of communication systems include: wireless local area network (WLAN) communication systems, wireless fidelity (WiFi) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, 5th generation (5G) systems, or new radio (NR) systems, and other future communication systems. It also supports communication systems that integrate multiple wireless technologies. For example, it can also be applied to systems that integrate non-terrestrial networks (NTN) with terrestrial mobile communication networks, such as drones, satellite communication systems, and high altitude platform station (HAPS) communication.

[0086] Figure 1 illustrates an example of a communication system applicable to embodiments of this application. The communication system includes at least one network device and at least one terminal device. Figure 1 uses a network device and multiple terminal devices as examples. These multiple terminal devices can be cellular phones, smartphones, laptops, handheld communication devices, handheld computing devices, satellite radio devices, global positioning systems, personal digital assistants (PDAs), and / or any other suitable devices for communication over a wireless communication system, and all can be connected to the network device. These multiple terminal devices are all capable of communicating with the network device; in addition, communication between terminal devices is also possible. Of course, the number of terminal devices and network devices in Figure 1 is merely an example, and there may be fewer or more.

[0087] The terminal device involved in the embodiments of this application, which can also be simply referred to as a terminal, is an entity on the user side used to receive or transmit signals. A terminal device can be a device that provides voice and / or data connectivity to a user, such as a handheld device with wireless connectivity, an in-vehicle device, etc. A terminal device can also be other processing devices connected to a wireless modem. The terminal device can communicate with a radio access network (RAN). A terminal device can also be called a wireless terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, user equipment, or UE, etc. A terminal device can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-embedded, or in-vehicle mobile device that exchanges voice and / or data with the radio access network. For example, the terminal device can also be a personal communication service (PCS) telephone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or other similar devices. Common terminal devices include mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), and wearable devices such as smartwatches, smart bracelets, and pedometers, but the embodiments in this application are not limited to these.

[0088] The embodiments of this application do not limit the device form of the terminal device. The device used to implement the function of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the function, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0089] A network device is an entity on the network side used to transmit signals, or receive signals, or both. A network device can be a means deployed in a radio access network (RAN) to provide wireless communication functionality to terminals.

[0090] In one possible scenario, network equipment can be devices with base station functions, such as evolved NodeBs (eNodeBs), transmitting and receiving points (TRPs), transmitting points (TPs), next-generation NodeBs (gNBs), next-generation base stations in future mobile communication systems, integrated access and backhaul (IAB) nodes, and non-terrestrial network equipment, i.e., equipment that can be deployed on high-altitude platforms or satellites. Network equipment can also be transmitting and receiving points (TRPs), base stations, and various forms of control nodes, such as network controllers and wireless controllers. Specifically, network equipment can be various forms of macro base stations, micro base stations (also known as small cells) in heterogeneous network (HetNet) scenarios, relay stations, access points (APs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs, or home node Bs (HNBs)), baseband units (BBUs) and remote radio units (RRUs) in distributed base station scenarios, transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, etc., and can also be base station antenna panels. Control nodes can connect to multiple base stations and configure resources for multiple terminals covered by multiple base stations. In systems employing different wireless access technologies, the names of devices with base station functions may differ. For example, it could be a gNB in ​​5G, or a network-side device in a network after 5G, or a network device in a future evolved public land mobile network (PLMN) network, or a device that performs base station functions in device-to-device (D2D) communication, machine-to-machine (M2M) communication, or vehicle-to-everything (V2X) communication, etc. This application does not limit the specific name of the network device.Network equipment can also be open RAN (O-RAN or ORAN), baseband pool (BBU pool) and RRU under cloud radio access network (CRAN), etc.

[0091] In another possible scenario, multiple network devices collaborate to assist terminals in achieving wireless access, with each network device performing a portion of the base station's functions. For example, network devices may include a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs may be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network devices can be CU nodes, DU nodes, or devices comprising both CU and DU nodes. Furthermore, CUs can be classified as network devices in the access network (RAN) or the core network (CN), without limitation.

[0092] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0093] In this embodiment, the form of the network device is not limited. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0094] Figure 2 shows the layered protocol stack design for the NR air interface. Specifically, the NR user plane protocol stack includes the SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer.

[0095] The main function of the SDAP layer is to map the Quality of Service (QoS) flow to the data radio bearer (DRB).

[0096] The PDCP layer is located between the SDAP layer and the RLC layer, providing message forwarding functions for the user plane / control plane, security functions (encryption / integrity protection), header compression / data compression, timed discarding, reordering, and in-order delivery.

[0097] The RLC layer, located between the PDCP and MAC layers, provides functions such as data transmission, segmentation / reassembly, automatic repeat request (ARQ), and duplicate detection. The RLC layer supports three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).

[0098] -TM mode is used to transmit data of signaling radio bearer 0 (SRB0), paging data, and broadcast system messages. These messages cannot be segmented, and the data is transparently transmitted through the RLC protocol layer. Among them, SRB0 is used to transmit RRC messages carried by the CCCH (common control channel) logical channel.

[0099] -UM mode is suitable for real-time services with high latency requirements and high tolerance for errors. Once a data packet is transmitted through the UM RLC entity, the transmission is considered complete. Even if the data packet is lost during air interface transmission, the RLC layer will not retransmit it.

[0100] AM mode is suitable for non-real-time services with high reliability requirements, such as web browsing, file transfer protocol (FTP) file downloads, and signaling transmission. These services need to minimize data transmission loss. The AM RLC entity uses the ARQ mechanism to ensure lossless data transmission. The basic idea of ​​ARQ is that the receiving RLC entity can send an RLC status report (carried by the RLC control PDU) to the sending end, indicating which data packets were successfully received and which failed to be received. The sending RLC entity can then retransmit the failed data packets based on the RLC status report.

[0101] The main functions of the MAC layer are to provide radio resource selection, scheduling information reporting, MAC layer service data unit (SDU) multiplexing and demultiplexing, and hybrid automatic repeat request (HARQ) transmission of data packets.

[0102] The NR air interface protocol stack internally generates and processes access stratum (AS) control packets. For example, the PDU types generated by the PDCP layer include data PDUs and control PDUs. PDCP data PDUs are used to transmit packets generated by protocol layers above the PDCP layer (such as service packets or radio resource control (RRC) layer messages), while PDCP control PDUs are used to transmit control type packets generated by PDCP layer entities. For PDCP data PDUs or PDCP control PDUs sent by the PDCP layer, the RLC layer encapsulates them into RLC data PDUs and then transmits them in the order they were received. The PDCP control PDUs include at least the following types:

[0103] • PDCP status PDU: Used to report the reception status of the current PDCP data PDU to the sending PDCP entity during handover and other processes.

[0104] • RoHC (robust header compression) feedback: Used for transmitting RoHC compression control information between PDCP entities.

[0105] • EHC (Ethernet Header Compression) feedback: Used for transmitting EHC context acknowledgment information between PDCP entities.

[0106] • UDC (uplink data compression) feedback: Used for transmitting UDC feedback information between PDCP entities.

[0107] • PDCP SN (sequence number) gap report: used by the PDCP entity at the sending end to indicate to the PDCP entity at the receiving end the sequence number information of PDCP data PDUs that have been actively discarded.

[0108] Immersive communication is a communication technology that prioritizes user experience, allowing users to feel as if they are actually there. Examples include virtual reality (VR), augmented reality (AR), and holographic projection. In immersive communication, network lag can ruin the user experience; therefore, immersive communication requires high network speeds.

[0109] In immersive communication, rapid information exchange is required between PDCP layers. For example, after the sender actively discards a data frame, data packet set, or data packet, it needs to quickly notify the receiver to avoid introducing unnecessary PDCP layer reordering delays. For instance, as shown in Figure 3, the PDCP layer sends burst 1 and burst 2 to the RLC layer sequentially. The RLC layer buffers burst 1 and burst 2 in its buffer. For example, at time t0, the RLC buffer contains burst 1 and burst 2. The length of the discard timer associated with the data packets in burst 1 is set to the PDU set delay budget (PSDB). If the data packet corresponding to burst 1 is not sent or is only partially sent before the timer expires, the unsent data packets in burst 1 can be discarded by the sender after the timer expires. Correspondingly, the PDCP layer generates a PDCP control PDU to indicate the sequence number information of the discarded data packets in burst 1. After the PDCP layer sends the PDCP control PDU to the RLC layer, the PDCP control PDU is buffered in the RLC buffer. Since the PDCP control PDU arrives in the RLC buffer later than burst 2, it is queued after burst 2 and can only be sent after burst 2 is completed. For example, at time t1, the RLC buffer contains both burst 2 and the PDCP control PDU; the PDCP control PDU is queued after burst 2, and burst 1 in the RLC buffer is discarded. Therefore, the queuing time for the PDCP control PDU is long. This queuing delay accumulates in the reordering delay of the PDCP on the receiving side, affecting the user's service experience. Therefore, how to reduce the transmission delay of control information is an urgent technical problem to be solved.

[0110] To reduce the transmission latency of control information, this application proposes an information transmission method, as shown in Figure 4. The executing entity of this information transmission method can be a communication device or a component within the communication device (e.g., a chip, circuit, etc.). This application does not limit the executing entity of the method. The communication device can be a terminal device or a network device in the communication system shown in Figure 1. The network device can be a master node (MN) or a secondary node (SN), where the master node is a radio access node providing control plane connections to the core network, and the secondary node is a radio access node providing additional air interface resources. As shown in Figure 4, the information transmission method includes:

[0111] S401. The first entity submits business information to at least one second entity and submits the first entity's control information to at least one third entity.

[0112] A communication device may include at least one first entity, at least one second entity, at least one third entity, and at least one fourth entity. An entity is a logical module that specifically implements a protocol layer function, capable of performing all or part of the functions corresponding to that protocol layer. For example, an entity at the SDAP layer can implement the mapping function from QoS flows to DRBs; an entity at the RRC layer can implement the function of radio resource control; an entity at the PDCP layer can implement functions such as security protection, data compression, or reordering; an entity at the RLC layer can implement functions such as segmentation, reassembly, ARQ, or duplicate detection; and an entity at the MAC layer can implement functions such as resource selection, scheduling information reporting, MAC SDU multiplexing and demultiplexing, and HARQ transmission of data packets. For a single protocol layer, the communication device can be configured with multiple entities, each capable of processing different types of service data or data from different sources.

[0113] Information / data interaction between different entities within a communication device can be described as delivery, transmission, transmission, sending, etc. To avoid confusion, the term "delivery" will be used uniformly in the following text.

[0114] The first entity of the communication device can generate service information and control information, and submit the service information to at least one second entity and the control information to at least one third entity. It should be noted that the first entity can simultaneously submit service information to the second entity and control information to the third entity, or it can submit the service information to the second entity first and then the control information to the third entity, or it can submit the control information to the third entity first and then the service information to the second entity. This embodiment does not limit the scope of the application.

[0115] The second and third entities can correspond to entities in the same protocol layer, while the first entity can correspond to an entity in another protocol layer.

[0116] In one possible implementation, the first entity can be an entity of the PDCP layer, simply referred to as the PDCP entity; the second entity can be an entity of the RLC layer, simply referred to as the RLC entity; and the third entity can also be an entity of the RLC layer, and the third entity and the second entity are different RLC layer entities. That is, the third entity and the second entity are different entities that implement the functions of the RLC layer, or it can be said that the third entity is used to implement the functions of the second entity. In this embodiment, the third entity can be independent of the second entity. To distinguish it from the second entity, the third entity can be referred to, for example, as a C-RLC (control-RLC) entity.

[0117] The PDCP entity delivers its business information and control information to the RLC entity and C-RLC entity respectively. This avoids the queuing latency caused by both control information and business information being queued in the RLC entity's cache, thus improving the speed of control information transmission and thereby enhancing user plane performance.

[0118] For the sake of simplicity, entities carried by the user plane can be called user plane entities, and similarly, entities carried by the control plane can be called control plane entities.

[0119] For example, the first entity may be a PDCP entity of the user plane, the second entity may be an RLC entity of the user plane, and the third entity may be a C-RLC entity of the user plane.

[0120] For example, the first entity may be a PDCP entity of the user plane, the second entity may be an RLC entity of the user plane, and the third entity may be a C-RLC entity of the control plane. The C-RLC entity is also used to transmit data packets generated by the PDCP layer of the control plane. The PDCP entity of the control plane is used to submit messages generated by the RRC layer of the control plane to the C-RLC entity. The RRC layer messages include RRC reconfiguration messages, RRC reconfiguration completion messages, UE assistance information, etc.

[0121] For example, the first entity may be a PDCP entity of the user plane, the second entity may be an RLC entity of the user plane, and the third entity may include N C-RLC entities of the user plane and M C-RLC entities of the control plane, where N and M are integers greater than or equal to 1.

[0122] The service information of a PDCP entity can be a PDCP data PDU, used to transmit data packets generated by protocol layers above the PDCP layer (such as IP data packets, SDAP layer PDUs, or RRC layer messages). The control information of a PDCP entity can be a PDCP control PDU, used to transmit control information generated by the PDCP entity itself to the peer PDCP entity. The types of PDCP control PDUs are as described above and will not be repeated here.

[0123] At least one DRB, or at least one PDCP entity corresponding to a DRB, can be associated with a C-RLC entity. This C-RLC entity is used to submit the PDCP control PDU generated by the associated PDCP entity to the associated MAC entity. As shown in Figures 5A and 5B, each rectangle represents an entity, the text within the rectangle represents the entity's name, and the solid or dashed lines between rectangles represent the connection relationship between entities, also known as the association relationship. In Figures 5A and 5B, the PDCP data PDUs generated by the three PDCP entities in the user plane can be submitted to the three RLC entities in the user plane respectively through the RLC channel (as shown by the solid line). The PDCP control PDUs generated by the three PDCP entities in the user plane can be submitted to one C-RLC entity through the RLC C-channel (as shown by the dashed line). The RLC C-channel is an RLC channel specifically used for PDCP entities to submit PDCP control PDUs to the C-RLC entity. In Figure 5A, the single C-RLC entity is an RLC entity of the user plane; in Figure 5B, the single C-RLC entity is an RLC entity of the control plane.

[0124] C-RLC entities can be configured in AM RLC mode or UM RLC mode. For example, at least one AM DRB or the PDCP entity corresponding to at least one AM DRB can be associated with a C-RLC entity, which can be configured in AM RLC mode. At least one UM DRB or the PDCP entity corresponding to at least one UM DRB can be associated with a C-RLC entity in AM RLC mode or a C-RLC entity in UM RLC mode.

[0125] When multiple PDCP entities are associated with the same C-RLC entity, PDCP control PDUs generated by different PDCP entities can be delivered to the same C-RLC entity in a first-in-first-out (FIFO) manner. It is understood that the above example uses the FIFO method; PDCP control PDUs generated by different PDCP entities can also be delivered to the same C-RLC entity in other ways, such as first-in-last-out (FILO), etc. This application does not limit this approach.

[0126] Furthermore, a DRB or its corresponding PDCP entity can be associated with multiple C-RLC entities. These multiple C-RLC entities submit the PDCP control PDUs generated by the associated PDCP entities to their respective associated MAC entities. These multiple C-RLC entities can be configured in AM RLC mode or UM RLC mode. For specific configuration details, please refer to the previous description, which will not be repeated here.

[0127] When a PDCP entity delivers the generated PDCP control PDU to multiple associated C-RLC entities, the method includes, but is not limited to: (1) the PDCP entity delivers the generated PDCP control PDU to the C-RLC entity that is the least idle among the multiple associated C-RLC entities, where “most idle” means that the C-RLC entity has the fewest number of data packets to be transmitted and / or retransmitted in its buffer, or the least total amount of data packets to be transmitted and / or retransmitted.

[0128] (2) After the PDCP entity copies the generated PDCP control PDU, it delivers it to at least two of the associated C-RLC entities. Further, the communication device can initialize at least one of the multiple C-RLC entities to receive the PDCP control PDU generated by the PDCP entity. It can also modify or adjust the C-RLC entities used to receive the PDCP control PDU generated by the PDCP entity through RRC messages or media access control element (MAC CE) commands, including adding one or more C-RLC entities and / or deleting one or more C-RLC entities to receive the PDCP control PDU generated by the PDCP entity, based on the aforementioned at least one C-RLC entity.

[0129] Understandably, by associating at least one DRB or the PDCP entity corresponding to at least one DRB with a C-RLC entity, and by associating a DRB or the PDCP entity corresponding to a DRB with multiple C-RLC entities, it is possible to associate multiple DRBs or the PDCP entities corresponding to multiple DRBs with multiple C-RLC entities, which will not be elaborated further here.

[0130] In a dual-connectivity scenario, as shown in Figure 5C, the C-RLC entity associated with the PDCP entity of a bearer terminated by the master node is configured to use master cell group (MCG) resources. That is, the configuration of the C-RLC entity is determined by the master node (MN), and this configuration includes the association between the C-RLC entity and the PDCP entity of the bearer terminated by the master node. The C-RLC entity associated with the PDCP entity of a bearer terminated by the secondary node is configured to use secondary cell group (SCG) resources. That is, the configuration of the C-RLC entity is determined by the secondary node (SN), and this configuration includes the association between the C-RLC entity and the PDCP entity of the bearer terminated by the secondary node.

[0131] Considering that entities in the SDAP layer also generate control information, in another possible implementation, the first entity can be an SDAP layer entity, simply referred to as an SDAP entity; the second entity can be a PDCP entity; and the third entity can also be a PDCP layer entity. Furthermore, the third entity and the second entity are different PDCP layer entities; that is, the third entity and the second entity are different entities implementing the functions of the PDCP layer. Alternatively, it can be said that the third entity is used to implement the functions of the second entity, and the third entity is independent of the second entity. To distinguish it from the second entity, the third entity can, for example, be called a C-PDCP (control-PDCP) entity.

[0132] The SDAP entity delivers its service information and control information to the PDCP entity and C-PDCP entity respectively. This avoids the queuing latency caused by both control information and service information being queued in the cache for delivery. This cache includes the cache of the PDCP entity and the cache of the RLC entity associated with the PDCP entity, which can improve the transmission speed of control information and thus improve user plane performance.

[0133] For example, the first entity may be a user plane SDAP entity, the second entity may be a user plane PDCP entity, and the third entity may be a user plane C-PDCP entity.

[0134] For example, the first entity may be the SDAP entity of the user plane, the second entity may be the PDCP entity of the user plane, and the third entity may be the C-PDCP entity of the control plane. The C-PDCP entity is also used to deliver messages generated by the RRC layer of the control plane to the associated RLC entity.

[0135] For example, the first entity may be the SDAP entity of the user plane, the second entity may be the PDCP entity of the user plane, and the third entity may include N C-PDCP entities of the user plane and M C-PDCP entities of the control plane, where N and M are integers greater than or equal to 1.

[0136] The service information of an SDAP entity can be an SDAP data PDU, used to transmit data packets generated by protocol layers above the SDAP layer (such as the IP layer). The control information of an SDAP entity can be an SDAP control PDU, used to transmit control type data packets generated by the SDAP entity itself, such as End-Marker control PDUs.

[0137] At least one SDAP entity can be associated with a C-PDCP entity, which is used to submit the SDAP control PDU generated by the associated SDAP entity to the associated RLC entity. As shown in Figures 6A and 6B, the SDAP data PDUs generated by the three SDAP entities in the user plane are respectively submitted to the three PDCP entities in the user plane, and the SDAP control PDUs generated by the three SDAP entities in the user plane are submitted to one C-PDCP entity for processing and transmission. In Figure 6A, this one C-PDCP entity is a PDCP entity in the user plane; in Figure 6B, this one C-PDCP entity is a PDCP entity in the control plane.

[0138] The RLC entity associated with the C-PDCP entity can be configured in AM RLC mode or UM RLC mode, and this application embodiment does not limit this.

[0139] When multiple SDAP entities are associated with the same C-PDCP entity, the SDAP control PDUs generated by different SDAP entities can be delivered to the same C-PDCP entity in either FIFO or FILO manner. This application does not limit this.

[0140] Furthermore, an SDAP entity can be associated with multiple C-PDCP entities, which respectively submit the SDAP control PDU generated by the associated SDAP entity to the associated RLC entities. The RLC entities associated with the multiple C-PDCP entities can be configured in AM RLC mode or UM RLC mode, which is not limited in this embodiment.

[0141] When an SDAP entity delivers a generated SDAP control PDU to multiple associated C-PDCP entities, the methods include, but are not limited to:

[0142] (1) The SDAP entity delivers the generated SDAP control PDU to the C-PDCP entity that is the least idle among the multiple associated C-PDCP entities. "Most idle" means that the number of packets to be transmitted and / or retransmitted in the buffer of the C-PDCP entity or in the buffer of the C-PDCP entity and the associated RLC entity is the smallest, or the total amount of data packets to be transmitted and / or retransmitted is the smallest.

[0143] (2) After the SDAP entity copies the generated SDAP control PDU, it delivers it to at least two of the associated C-PDCP entities. Further, the communication device can initialize at least one of the multiple C-PDCP entities to receive the SDAP control PDU generated by the SDAP entity. It can also modify or adjust the C-PDCP entity used to receive the SDAP control PDU generated by the SDAP entity via RRC messages or MAC CE commands, including adding one or more C-PDCP entities and / or deleting one or more C-PDCP entities to receive the SDAP control PDU generated by the SDAP entity, based on the aforementioned at least one C-PDCP entity.

[0144] Understandably, by combining at least one SDAP entity with a C-PDCP entity, and by associating one SDAP entity with multiple C-PDCP entities, it is possible to associate multiple SDAP entities with multiple C-PDCP entities, which will not be elaborated further here.

[0145] In a dual-connectivity scenario, as shown in Figure 6C, the C-PDCP entity associated with the SDAP entity of the bearer terminated by the primary node is configured to use MCG resources. That is, the configuration of the C-PDCP entity is determined by the MN, and this configuration includes the association relationship between the C-PDCP entity and the SDAP entity of the bearer terminated by the primary node. The C-PDCP entity associated with the SDAP entity of the bearer terminated by the secondary node is configured to use SCG resources. That is, the configuration of the C-PDCP entity is determined by the SN, and this configuration includes the association relationship between the C-PDCP entity and the SDAP entity of the bearer terminated by the secondary node.

[0146] The first entity and the third entity can correspond to entities in the same protocol layer, while the second entity can correspond to entities in another protocol layer.

[0147] In one possible implementation, the first entity can be a PDCP entity, the second entity can be an RLC entity, and the third entity can also be an entity of the PDCP layer. The third entity is different from the first entity; that is, the third entity and the first entity are different entities implementing the functions of the PDCP layer. Alternatively, it can be said that the third entity is used to implement the functions of the first entity, and the third entity is independent of the first entity. To distinguish it from the first entity, the third entity can, for example, be called a C-PDCP entity.

[0148] For example, the first entity may be a PDCP entity on the user plane, the second entity may be an RLC entity on the user plane, and the third entity may be a C-PDCP entity on the user plane.

[0149] For example, the first entity may be a PDCP entity of the user plane, the second entity may be an RLC entity of the user plane, and the third entity may be a C-PDCP entity of the control plane. The C-PDCP entity is also used to deliver messages generated by the RRC layer of the control plane to the associated RLC entity.

[0150] For example, the first entity may be a PDCP entity of the user plane, the second entity may be an RLC entity of the user plane, and the third entity may include N C-PDCP entities of the user plane and M C-PDCP entities of the control plane, where N and M are integers greater than or equal to 1.

[0151] As mentioned above, the business information of a PDCP entity can be a PDCP data PDU, and the control information of a PDCP entity can be a PDCP control PDU.

[0152] At least one DRB, or at least one PDCP entity corresponding to a DRB, can be associated with a C-PDCP entity. This C-PDCP entity is used to submit the PDCP control PDU generated by the associated PDCP entity to the associated RLC entity. As shown in Figures 7A and 7B, the PDCP data PDUs generated by the three PDCP entities in the user plane are submitted to the three RLC entities in the user plane, and the PDCP control PDUs generated by the three PDCP entities in the user plane are submitted to one C-PDCP entity. In Figure 7A, this one C-PDCP entity is a PDCP entity in the user plane; in Figure 7B, this one C-PDCP entity is a PDCP entity in the control plane.

[0153] The RLC entity associated with a C-PDCP entity can be configured in AM RLC mode or UM RLC mode. For example, at least one AM DRB or the PDCP entity corresponding to at least one AM DRB can be associated with a C-PDCP entity, and the RLC entity associated with that C-PDCP entity can be configured in AM RLC mode. The RLC entity associated with a C-PDCP entity to which at least one UM DRB or the PDCP entity corresponding to at least one UM DRB is associated can be configured in AM RLC mode or UM RLC mode.

[0154] When multiple PDCP entities are associated with the same C-PDCP entity, the PDCP control PDUs generated by different PDCP entities can be delivered to the same C-PDCP entity in either FIFO or FILO manner. This application does not limit this.

[0155] Furthermore, a DRB or a DRB's PDCP entity can be associated with multiple C-PDCP entities. These multiple C-PDCP entities submit the PDCP control PDUs generated by the associated PDCP entities to the associated multiple RLC entities. The RLC entities associated with these multiple C-PDCP entities can be configured in AM RLC mode or UM RLC mode. For specific configuration details, please refer to the previous description, which will not be repeated here.

[0156] When a PDCP entity delivers a generated PDCP control PDU to multiple associated C-PDCP entities, the methods include, but are not limited to:

[0157] (1) The PDCP entity can deliver the PDCP control PDU to the most idle C-PDCP entity among the multiple associated C-PDCP entities. For the description of "the most idle C-PDCP entity", please refer to the previous description, which will not be repeated here.

[0158] (2) The PDCP entity can copy the generated PDCP control PDU and deliver it to at least two of the associated C-PDCP entities. The initialization configuration and modification method of the at least one C-PDCP entity can be referred to the previous description, and will not be repeated here.

[0159] Understandably, by associating at least one DRB or the PDCP entity corresponding to at least one DRB with a C-PDCP entity, and by associating a DRB or the PDCP entity corresponding to a DRB with multiple C-PDCP entities, it is possible to associate multiple DRBs or the PDCP entities corresponding to multiple DRBs with multiple C-PDCP entities, which will not be elaborated further here.

[0160] In a dual-connectivity scenario, as shown in Figure 7C, the C-PDCP entity associated with the PDCP entity of the bearer terminated by the primary node is configured to use MCG resources. That is, the configuration of the C-PDCP entity is determined by the MN, and this configuration includes the association relationship between the C-PDCP entity and the PDCP entity of the bearer terminated by the primary node. The C-PDCP entity associated with the PDCP entity of the bearer terminated by the secondary node is configured to use SCG resources. That is, the configuration of the C-PDCP entity is determined by the SN, and this configuration includes the association relationship between the C-PDCP entity and the PDCP entity of the bearer terminated by the secondary node.

[0161] In one possible implementation, the first entity can be an SDAP entity, the second entity can be a PDCP entity, and the third entity can also be an entity of the SDAP layer. The third entity is different from the first entity; that is, the third entity and the first entity are different entities implementing the functions of the SDAP layer, and the third entity is independent of the first entity. To distinguish it from the first entity, the third entity can be called, for example, a C-SDAP entity. The relationship between SDAP entities and C-SDAP entities can be referred to the relationship between PDCP entities and C-PDCP entities mentioned earlier, and will not be repeated here.

[0162] The first entity, the second entity, and the third entity can each correspond to entities in different protocol layers.

[0163] In one possible implementation, the first entity can be an SDAP entity, the second entity can be a PDCP entity, and the third entity can be an RLC layer entity. The third entity is different from the RLC entity associated with the PDCP entity (second entity). To distinguish it from the RLC entity associated with the PDCP entity (second entity), the third entity can be, for example, called a C-RLC entity. The relationship between the SDAP entity and the C-RLC entity can be referred to the relationship between the SDAP entity and the C-PDCP entity mentioned earlier, and will not be repeated here.

[0164] In the above implementation, the RLC entity associated with the PDCP entity is only used to transmit the PDCP data PDU generated by the PDCP entity, and the C-RLC entity or C-PDCP entity associated with the PDCP entity is only used to transmit the PDCP control PDU generated by the PDCP entity; the PDCP entity associated with the SDAP entity is only used to transmit the SDAP data PDU generated by the SDAP entity, and the C-PDCP entity, C-SDAP entity or C-RLC entity associated with the SDAP entity is only used to transmit the SDAP control PDU generated by the SDAP entity.

[0165] S402. The third entity submits a data packet to the fourth entity, the data packet including control information and / or instruction information submitted by the first entity to the third entity.

[0166] After receiving the control information submitted by the first entity, the third entity can encapsulate it and generate a data packet, which is then delivered to the associated fourth entity. The data packet includes the control information and / or indication information submitted by the first entity, wherein the indication information is used to indicate the first entity associated with the control information.

[0167] In one possible implementation, the first entity can be a PDCP entity, the third entity can be a C-RLC entity, and the fourth entity can be an entity of the MAC layer, referred to simply as a MAC entity.

[0168] As mentioned earlier, the control information of a PDCP entity can be a PDCP control PDU. The C-RLC entity can encapsulate the received PDCP control PDU to generate a C-RLC data PDU. The C-RLC entity then submits this C-RLC data PDU to the associated MAC entity.

[0169] Optionally, the C-RLC data PDU may include a PDCP control PDU and indication information, wherein the indication information is used to indicate the PDCP entity that generated the PDCP control PDU or the DRB corresponding to the PDCP entity. For example, the indication information may be the index of the PDCP entity that generated the PDCP control PDU or the index of the DRB corresponding to the PDCP entity.

[0170] Optionally, when only one PDCP entity is associated with the C-RLC entity, the first indication information may be absent or filled with a default value.

[0171] As shown in Figure 8A, the C-RLC data PDU generated by the C-RLC entity includes a C-RLC SDU and a C-RLC hdr. The C-RLC SDU is a PDCP control PDU generated by the PDCP entity. The C-RLC hdr includes at least a C-RLC SN and an Index. The C-RLC SN represents the sequence number of the C-RLC data PDU, and the Index represents the index of the PDCP entity that generated the PDCP control PDU or the index of the DRB corresponding to the PDCP entity.

[0172] In one possible implementation, the first entity can be an SDAP entity, the third entity can be a C-PDCP entity, and the fourth entity can be an RLC entity associated with the C-PDCP entity.

[0173] As mentioned earlier, the control information of an SDAP entity can be an SDAP control PDU. The C-PDCP entity encapsulates the received SDAP control PDU to generate a C-PDCP data PDU. The C-PDCP entity then submits this C-PDCP data PDU to the associated RLC entity.

[0174] Optionally, the C-PDCP data PDU may include an SDAP control PDU and indication information, wherein the indication information is used to indicate the SDAP entity that generated the SDAP control PDU. For example, the indication information may be an index of the SDAP entity that generated the SDAP control PDU.

[0175] Optionally, when only one SDAP entity is associated with the C-PDCP entity, the indication information may be absent or filled with a default value.

[0176] As shown in Figure 8B, the C-PDCP data PDU generated by the C-PDCP entity includes a C-PDCP SDU and a C-PDCP hdr. The C-PDCP SDU is an SDAP control PDU generated by the SDAP entity. The C-PDCP hdr includes at least a C-PDCP SN and an Index. The C-PDCP SN represents the sequence number of the C-PDCP data PDU, and the Index represents the index of the SDAP entity that generated the SDAP control PDU.

[0177] In addition, the C-PDCP entity can be configured with security features, such as enabling packet encryption and integrity protection, to provide additional security protection for received SDAP control PDUs.

[0178] In one possible implementation, the first entity can be a PDCP entity, the third entity can be a C-PDCP entity, and the fourth entity can be an RLC entity associated with the C-PDCP entity.

[0179] As mentioned earlier, the control information of a PDCP entity can be a PDCP control PDU. The C-PDCP entity encapsulates the received PDCP control PDU to generate a C-PDCP data PDU. The C-PDCP entity then submits this C-PDCP data PDU to the associated RLC entity.

[0180] Optionally, the C-PDCP data PDU may include the PDCP control PDU and indication information. The indication information can be found in the previous description and will not be repeated here.

[0181] Optionally, when only one PDCP entity is associated with the C-PDCP entity, the indication information may be absent or filled with a default value.

[0182] As shown in Figure 8C, the C-PDCP data PDU generated by the C-PDCP entity includes a C-PDCP SDU and a C-PDCP hdr. The C-PDCP SDU is a PDCP control PDU generated by the PDCP entity. The C-PDCP hdr includes at least a C-PDCP SN and an Index. The C-PDCP SN represents the sequence number of the C-PDCP data PDU, and the Index represents the index of the PDCP entity that generated the PDCP control PDU or the index of the DRB corresponding to the PDCP entity.

[0183] In addition, the C-PDCP entity can be configured with security features, just like the associated PDCP entity, to provide additional security protection for the received PDCP control PDU.

[0184] In one possible implementation, the first entity can be an SDAP entity, the third entity can be a C-SDAP entity, and the fourth entity can be a PDCP entity associated with the C-SDAP entity.

[0185] As mentioned earlier, the control information of an SDAP entity can be an SDAP control PDU. The C-SDAP entity encapsulates the received SDAP control PDU to generate a C-SDAP data PDU. The C-SDAP entity then submits this C-SDAP data PDU to the associated PDCP entity. The frame structure of the C-SDAP data PDU can be referred to the previous description and will not be repeated here.

[0186] In one possible implementation, the first entity can be an SDAP entity, the third entity can be a C-RLC entity, and the fourth entity can be a MAC entity.

[0187] As mentioned earlier, the control information of an SDAP entity can be an SDAP control PDU. The C-RLC entity encapsulates the received SDAP control PDU to generate a C-RLC data PDU. The C-RLC entity then submits this C-RLC data PDU to the associated MAC entity. The frame structure of the C-RLC data PDU can be referred to the previous description and will not be repeated here.

[0188] In the above embodiments, by configuring a separate associated C-RLC entity or C-PDCP entity for the PDCP control PDU, the queuing delay introduced by the PDCP control PDU and PDCP data PDU queuing together in the RLC buffer for delivery can be avoided, thus improving the delivery speed of the PDCP control PDU and consequently improving user plane performance. For example, for compression mechanisms, the corresponding fast transmission of the PDCP control PDU can quickly activate the compression context, improve the compression ratio, and increase the utilization of air interface resources.

[0189] To reduce the transmission latency of control information, this application proposes another information transmission method, as shown in Figure 9. Compared with the information transmission method shown in Figure 4, the other information transmission method shown in Figure 9 does not require additional configuration of RLC entities or PDCP entities for submitting PDCP control PDUs, which can reduce the number of RLC entities or PDCP entities and reduce processing complexity.

[0190] The execution entity corresponding to the other information transmission method shown in Figure 9 can be a communication device or a component (e.g., a chip, circuit, etc.) within the communication device. This application embodiment does not limit the execution entity of the method. The communication device can be a terminal device or a network device in the communication system shown in Figure 1. As shown in Figure 9, the information transmission method includes:

[0191] S901. The first entity submits a data packet and indication information to the second entity. The indication information is used to indicate the priority of the data packet.

[0192] The communication device may include at least one first entity and at least one second entity. The data packets generated by the first entity include service information or control information. The first entity may submit data packets and indication information to the second entity. The indication information is used to indicate the priority of the data packets, so that the second entity can determine the delivery order of the data packets based on the indication information.

[0193] In one possible implementation, the first entity can be a PDCP entity, and the second entity can be an RLC entity associated with the PDCP entity. The PDCP entity can generate a PDCP PDU and submit the PDCP PDU and indication information to the associated RLC entity. The indication information is used to indicate the priority of the PDCP PDU.

[0194] Optionally, the indication information can be used to indicate the type of the PDCP PDU, where the PDCP PDU type includes data type (corresponding to PDCP data PDU) and control type (corresponding to PDCP control PDU), assuming that the PDCP control PDU has higher priority than the PDCP data PDU. For example, if the indication information indicates that the type of the PDCP PDU is a PDCP control PDU, then in the RLC entity associated with the PDCP entity, the PDCP control PDU will be delivered to the MAC entity associated with the RLC entity before the cached PDCP data PDU.

[0195] The above examples illustrate that PDCP PDUs include data types and control types. It is understood that PDCP PDUs may also include other types, and this application does not limit this.

[0196] Optionally, the indication information can be used to indicate whether the PDCP PDU is a type that needs to be prioritized. For example, the indication information can indicate that the PDCP PDU is a PDCP SN gap report, which is a type that needs to be prioritized. In this case, in the RLC entity associated with the PDCP entity, the PDCP SN gap report will be delivered to the MAC entity associated with the RLC entity before other PDCP PDUs in the cache.

[0197] Optionally, the indication information can be used to indicate the priority of PDCP PDUs, wherein the priority includes at least a first priority and a second priority, and the first priority is higher than the second priority. That is, in the RLC entity associated with the PDCP entity, the PDCP PDU corresponding to the first priority will be delivered to the MAC entity associated with the RLC entity before the PDCP PDU corresponding to the second priority in the cache. For example, the priority of the PDCP control PDU can be the first priority, and the priority of the PDCP data PDU can be the second priority. As another example, the priority of the PDCP SN gap report is the first priority, and the priority of other PDCP PDUs is the second priority.

[0198] The above example illustrates that PDCP PDU priorities include first and second priorities. It is understood that PDCP PDU priorities can also include more priorities, such as third, fourth, etc. For example, some PDCP control PDUs may have a first priority, while others may have a second priority; some PDCP data PDUs may have a third priority, while others may have a fourth priority, and so on. This application does not limit this.

[0199] In one possible implementation, the communication device is a network device, and the network device includes a CU and a DU. When the network device adopts a CU-DU separation architecture, the PDCP entity is located in the CU, and the RLC entity is located in the DU. Specifically, the PDCP entity can submit indication information to the RLC entity by having the CU submit a first data frame to the DU, which includes the indication information. The first data frame could be, for example, a downlink user data (DL USER DATA) frame.

[0200] Figure 10 illustrates a possible format of a first data frame provided in an embodiment of this application. This first data frame uses the format of a DL USER DATA frame submitted by the CU to the DU. The first data frame includes indication information, a PDU type field, a spare field, a downlink discard blocks field, a downlink flush field, a report polling field, a request out-of-order report field, a report delivered field, a user data existence flag field, an assistance Info.report polling flag field, a retransmission flag field, an NR-U sequence number field, a downlink discard NR PDCP PDU sequence number field, a downlink discard number of blocks field, a downlink discard NR PDCP PDU sequence number start field, and a discarded block size field. The fields include size, downlink NR PDCP PDU sequence number (DL report NR PDCP PDU SN), and padding.

[0201] The fields DL discard blocks, DL flush, report polling, request outofSeq report, report delivered, user data existence flag, assistance Info.report polling flag, retransmission flag, NR-U sequence number, DL discard NR PDCP PDU SN, DL discard number of blocks, DL discard NR PDCP PDU SN start, DL discard NR PDCP PDU SN start, discarded block size, and DL report NR PDCP PDU SN have the same meaning as their counterparts in the existing USER DATA frame format, and will not be repeated here. The Padding field is used to pad the size of the first data frame to (n×4-2) bytes, where n is a positive integer.

[0202] The indication information shown in Figure 10 is 1 bit long. For example, assuming that the indication information is used to indicate the type of PDCP PDU, bit "0" and bit "1" can represent control type and data type, respectively, or bit "0" and bit "1" can represent data type and control type, respectively.

[0203] For example, suppose the indication information is used to indicate whether the PDCP PDU is a type that needs to be prioritized. Bit "0" and bit "1" can represent types that need to be prioritized and types that do not need to be prioritized, respectively. Alternatively, bit "0" and bit "1" can represent types that do not need to be prioritized and types that need to be prioritized, respectively.

[0204] For example, assuming the indication information is used to indicate the priority of the PDCP PDU, bit "0" and bit "1" can represent the first priority and the second priority, respectively, or bit "0" and bit "1" can represent the second priority and the first priority, respectively.

[0205] It should be noted that when there are more than two types of PDCP PDUs, or more than two priorities of PDCP PDUs, the number of bits occupied by the indication information can exceed one to indicate more types or priorities. This application does not limit the name and field length of the indication information.

[0206] S902. The second entity delivers the data packet to the third entity based on the instruction information.

[0207] When the second entity receives the data packet and indication information submitted by the first entity, it can obtain the priority of the data packet and thus determine the submission order. The priority of the data packet can be referred to the previous description, and will not be repeated here.

[0208] In one possible implementation, the first entity can be a PDCP entity, the second entity can be an RLC entity associated with the PDCP entity, the third entity can be a MAC entity associated with the RLC entity, and the data packet can be a PDCP PDU generated by the PDCP entity.

[0209] Optionally, the indication information can be used to indicate the type of PDCP PDU. If the indication information indicates that the type of PDCP PDU is control type (corresponding to PDCP control PDU), the RLC entity can perform queue-jumping processing on the PDCP control PDU, that is, to insert the PDCP control PDU at the beginning of the RLC buffer and deliver it to the associated MAC entity first.

[0210] Optionally, the indication information can be used to indicate whether the PDCP PDU is a type that needs to be prioritized. If the indication information indicates that the PDCP PDU is a type that needs to be prioritized (e.g., PDCP SN gap report), the RLC entity can prioritize submitting the PDCP PDU to the associated MAC entity.

[0211] Optionally, the indication information can be used to indicate the priority of the PDCP PDU. If the indication information indicates that the priority of the PDCP PDU is first priority, for example, the priority of the PDCP control PDU is first priority, or the priority of the PDCP SN gap report is first priority, the RLC entity can submit the PDCP PDU to the associated MAC entity first.

[0212] In the above embodiments, when the PDCP entity submits the PDCP control PDU to the associated RLC entity, it can indicate that the type of the PDCP control PDU is a control type, or that the PDCP control PDU is a type that needs to be processed first, or that the priority of the PDCP control PDU is the first priority, so that the associated RLC entity submits the PDCP control PDU first, thereby improving the transmission speed of the PDCP control PDU and improving user plane performance.

[0213] In the NR protocol, the data packets sent from the sender to the receiver carry the corresponding SN (Signal Serial Number). The receiver has a corresponding receive window and only accepts data packets whose SN falls within the receive window. In other words, the data packets corresponding to the SN in the receive window are the data packets the receiver expects to receive. The size of the receive window is generally half the size of the SN space. For example, assuming the upper layer configures the SN size to be 12 bits, then the SN space size is 2. 12 =4096, then the size of the receive window is half of this space size, 2048. The lower boundary of the receive window is used to determine the starting position of the receive window. For example, if the lower boundary of the receive window is 10, then the receiver will receive data packets with SN from 10 to 2057, and will not process or pass data packets that fall outside the lower boundary of the receive window to the upper layer.

[0214] For example, the receiving end receives data packets in sequence. When the first data packet is successfully received and its SN is 0, the lower boundary of the receiving window is set to 1. At this time, the SNs corresponding to the receiving window are 1 to 2048. That is, data packets with SNs from 1 to 2048 can be processed and submitted to the upper layer after being successfully received by the receiving end. Further, when the receiving end receives the second data packet with its SN of 1, the lower boundary of the receiving window is updated to 2. At this time, the SNs corresponding to the receiving window are 2 to 2049. And so on.

[0215] Specifically, the receive window of the PDCP layer at the receiver is the range of PDCP SNs covered by RX_DELIV to RX_DELIV + window size. The lower boundary of the receive window is represented by the variable RX_DELIV, which represents the SN corresponding to the first PDCP SDU that has not yet been submitted to the upper layer. The window size of the receive window is half the size of the PDCP SN space.

[0216] It should be noted that the PDCP SN mentioned above can also be a PDCP count value (PDCP COUNT), and similarly, the RLC SN can also be an RLC count value (RLC COUNT). This application does not limit the specifics. For the sake of simplicity, PDCP SN or RLC SN will be used uniformly in the following description.

[0217] When a sequence number hole appears in the receive window of the PDCP layer at the receiving end, the PDCP entity starts a PDCP reordering timer. When the PDCP reordering timer expires, the PDCP entity pushes the receive window, that is, it updates the value of the variable RX_DELIV. This causes a change in the range of PDCP SNs covered by the PDCP layer's receive window, and some packets may fall outside the receive window. The PDCP entity then stops processing and submitting packets outside the receive window to the upper layer. However, for AM DRB, the ARQ mechanism of the RLC layer at the sending end continuously retransmits packets that were not successfully transmitted at the RLC layer. This can lead to a situation where a packet is considered to have timed out and is no longer waiting to be received at the receiving end's PDCP layer, but the sending end's RLC layer continues to retransmit these packets, and the receiving end's RLC layer continues to wait for packet retransmissions, resulting in unnecessary resource waste.

[0218] Furthermore, in the information transmission method shown in Figure 4, the RLC entity associated with the PDCP entity at the transmitting end is only used to transmit the PDCP data PDU generated by that PDCP entity, and the C-RLC entity associated with the PDCP entity at the transmitting end is only used to transmit the PDCP control PDU generated by that PDCP entity. Therefore, there is a fixed correspondence between the sequence number of the PDCP data PDU at the PDCP layer and the sequence number of the corresponding RLC layer. The sequence number of the RLC layer corresponding to the PDCP data PDU refers to the sequence number of the RLC SDU that includes the PDCP data PDU. For example, assuming that the sequence number PDCP SN of PDCP data PDU x at the PDCP layer is a, and the corresponding sequence number RLC SN at the RLC layer is b, then the sequence number PDCP SN of PDCP data PDU x+1 at the PDCP layer is a+1, and the corresponding sequence number RLC SN at the RLC layer is b+1.

[0219] Furthermore, to reduce resource waste, based on the information transmission method shown in Figure 4, this application proposes a data transmission method, as shown in Figure 11. The executing entity of this data transmission method can be a communication device or a component (e.g., a chip, circuit, etc.) within the communication device; this application does not limit the executing entity of the method. The communication device can be a terminal device or a network device in the communication system shown in Figure 1. As shown in Figure 11, the data transmission method includes:

[0220] S1101. The first entity of the first communication device submits first instruction information to the second entity of the first communication device. The first instruction information is used to instruct the first entity of the first communication device to no longer wait for the second data to be received.

[0221] The first communication device may be a receiving end, including at least one first entity and at least one second entity. The first entity may be a PDCP entity, and the second entity may be an RLC entity. The PDCP entity is associated with the RLC entity.

[0222] The PDCP data PDU successfully received by the PDCP entity at the receiving end can be referred to as the first data. As mentioned earlier, the update of the receiving window of the PDCP layer at the receiving end will cause some PDCP data PDUs to fall outside the receiving window. The PDCP entity at the receiving end does not receive this part of the PDCP data PDUs and will no longer receive it. This part of the PDCP data PDUs can be referred to as the second data.

[0223] In one possible implementation, the PDCP entity at the receiving end can submit a first indication message to the associated RLC entity at the receiving end. This first indication message indicates that the PDCP entity at the receiving end should no longer wait for the received PDCP data PDU (i.e., the second data). Upon receiving the first indication message, the RLC entity at the receiving end can determine the RLC layer sequence number (RLC SN) corresponding to the second data.

[0224] Optionally, if the PDCP entity at the receiving end maintains the correspondence between the PDCP SN and RLC SN corresponding to the PDCP data PDU, the first indication information may include the RLC SN of the RLC layer corresponding to the second data.

[0225] Optionally, if the correspondence between the PDCP SN and the RLC SN corresponding to the PDCP data PDU is maintained by the RLC entity at the receiving end, the first indication information may include the PDCP SN of the PDCP layer corresponding to the second data.

[0226] For example, when the reordering timer of the PDCP entity at the receiving end times out, the receiving window of the PDCP layer is updated, and the PDCP data PDUs corresponding to PDCP SNs {10, 11, 12} are not successfully received and fall outside the receiving window of the PDCP layer at the receiving end. Assuming that the PDCP entity at the receiving end maintains the correspondence between the PDCP SNs and RLC SNs corresponding to the PDCP data PDUs, the PDCP entity at the receiving end can submit first indication information to the RLC entity at the receiving end. This first indication information may include the RLC sequence numbers RLC SNs {a, a+1, a+2} corresponding to these three PDCP data PDUs. Upon receiving the first indication information, the RLC entity at the receiving end can determine that the RLC sequence numbers RLC SNs corresponding to these three PDCP data PDUs are {a, a+1, a+2}.

[0227] For example, the PDCP entity at the receiving end does not receive the PDCP data PDUs corresponding to PDCP SNs {10, 11, 12}, and these three PDCP data PDUs fall outside the receiving window of the PDCP layer at the receiving end. Assuming the RLC entity at the receiving end maintains the correspondence between the PDCP SNs and RLC SNs corresponding to the PDCP data PDUs, the PDCP entity at the receiving end can submit first indication information to the RLC entity at the receiving end. This first indication information may include the sequence numbers PDCP SNs {10, 11, 12} of the three PDCP data PDUs at the PDCP layer. Upon receiving the first indication information, the RLC entity at the receiving end can determine that the RLC sequence numbers RLC SNs corresponding to these three PDCP data PDUs are {a, a+1, a+2}.

[0228] In one possible implementation, the second communication device may be a transmitter, and the second data may be a PDCP data PDU discarded by the transmitter's PDCP entity.

[0229] When the discard timer corresponding to a PDCP data PDU expires, the transmitting PDCP entity discards the PDCP data PDU and triggers the transmission of a PDCP SN gap report to the receiving PDCP entity. Upon receiving the PDCP SN gap report, the receiving PDCP entity determines that the PDCP data PDU indicated by the report has been discarded and submits first indication information to the receiving RLC entity. This first indication information indicates the PDCP data PDU (i.e., the second data) discarded by the transmitting PDCP entity. Upon receiving the first indication information, the receiving RLC entity determines the RLC sequence number (RLC SN) corresponding to the second data.

[0230] Referring to the preceding description, the first indication information may include the RLC SN of the RLC layer corresponding to the second data, or the first indication information may include the PDCP SN of the PDCP layer corresponding to the second data, which will not be elaborated further here.

[0231] For example, when the transmitting end's PDCP entity discards the PDCP data PDUs corresponding to PDCP SNs {10, 11, 12} due to a timeout in the discard timer, the transmitting end's PDCP entity indicates to the receiving end's PDCP entity via a PDCP SN gap report that the PDCP data PDUs corresponding to PDCP SNs {10, 11, 12} have been discarded by the transmitting end. Assuming the receiving end's PDCP entity maintains the correspondence between the PDCP SNs and RLC SNs corresponding to the PDCP data PDUs, the receiving end's PDCP entity can submit first indication information to the associated receiving end's RLC entity. This first indication information may include the RLC layer sequence numbers RLC SNs {a, a+1, a+2} corresponding to these three PDCP data PDUs. Upon receiving the first indication information, the receiving end's RLC entity can determine that the RLC layer sequence numbers RLC SNs corresponding to these three PDCP data PDUs are {a, a+1, a+2}.

[0232] For example, the PDCP entity at the transmitting end indicates to the PDCP entity at the receiving end via a PDCP SN gap report that the PDCP data PDUs corresponding to PDCP SNs {10, 11, 12} have been discarded by the transmitting end. Assuming the receiving end's RLC entity maintains the correspondence between the PDCP SNs and RLC SNs corresponding to the PDCP data PDUs, the receiving end's PDCP entity can submit first indication information to the associated receiving end's RLC entity. This first indication information may include the PDCP layer sequence numbers PDCP SNs {10, 11, 12} corresponding to these three PDCP data PDUs. Upon receiving the first indication information, the receiving end's RLC entity can determine that the RLC layer sequence numbers RLC SNs corresponding to these three PDCP data PDUs are {a, a+1, a+2}.

[0233] S1102. Based on the first instruction information, the second entity of the first communication device determines whether to update the set of data to be received.

[0234] The first communication device can be a receiving end, the first entity can be the PDCP entity of the receiving end, and the second entity can be the RLC entity of the receiving end. Upon receiving the first indication information from the PDCP entity of the receiving end, the RLC entity of the receiving end can obtain the RLC sequence number (RLC SN) corresponding to the second data, and thus determine whether to update the set of data to be received.

[0235] In one possible implementation, the set of data that the RLC entity at the receiving end expects to receive can be represented by the receive window of the RLC layer. The receive window is the set of sequence numbers of the data that the RLC entity expects to receive, and the lower boundary of the receive window is the minimum value in the set of sequence numbers of the data that the RLC entity expects to receive.

[0236] For AM RLC entities, the lower boundary of the RLC layer's receive window is indicated by the variable RX_NEXT, which represents the SN corresponding to the next RLC SDU after the last RLC SDU received in sequence by the RLC layer. The size of the RLC layer's receive window is half the size of the RLC SN space. Updating the RLC layer's receive window means that when an RLC SDU is successfully received and its corresponding SN is equal to RX_NEXT, the RLC entity can update RX_NEXT to the SN corresponding to the next unreceived SDU in sequence.

[0237] Optionally, when the sequence number RLC SN of the RLC layer corresponding to the second data is equal to the lower boundary of the receiving window of the RLC layer, the RLC entity of the receiving end updates the receiving window of the RLC layer. For example, the RLC entity of the receiving end updates the lower boundary of the receiving window of the RLC layer to the sequence number RLC SN of the RLC layer corresponding to the second data plus 1.

[0238] Optionally, when the sequence number RLC SN of the RLC layer corresponding to the second data is not equal to the lower boundary of the receiving window of the RLC layer, the RLC entity of the receiving end does not update the receiving window of the RLC layer. In other words, the RLC entity of the receiving end does not update the lower boundary of the receiving window of the RLC layer.

[0239] For example, the RLC entity of the receiving end receives the first indication information submitted by the PDCP entity of the receiving end. The first indication information indicates that the PDCP layer sequence number PDCP SN corresponding to the second data is {10, 11, 12}. The RLC entity of the receiving end can determine that the RLC layer sequence number RLC SN corresponding to these three PDCP data PDUs is {a, a+1, a+2}, and thus can be considered that the RLC SDUs corresponding to these three PDCP data PDUs have been successfully received. Assuming the lower boundary of the receive window, RX_NEXT, is 'a', which is equal to the RLC layer sequence number RLC SN = 'a' corresponding to one of the three PDCP data PDUs, the RLC entity at the receiving end can update the lower boundary of the RLC layer's receive window to RX_NEXT = 'a+1'. Furthermore, if the updated lower boundary of the receive window, RX_NEXT, is equal to the RLC layer sequence number RLC SN = 'a+1' corresponding to another of the three PDCP data PDUs, the RLC entity at the receiving end can update the lower boundary of the RLC layer's receive window to RX_NEXT = 'a+2'. And if the updated lower boundary of the receive window, RX_NEXT, is equal to the RLC layer sequence number RLC SN = 'a+2' corresponding to another of the three PDCP data PDUs, the RLC entity at the receiving end can update the lower boundary of the RLC layer's receive window to RX_NEXT = 'a+3'. The RLC SDU corresponding to the sequence number RLC SN = a+3 of the RLC layer is the next SDU that was not received in sequence or was not considered a successful reception.

[0240] For example, the RLC entity of the receiving end receives the first indication information submitted by the PDCP entity of the receiving end. The first indication information indicates that the PDCP layer sequence number PDCP SN corresponding to the second data is {10, 11, 15}. The RLC entity of the receiving end can determine that the RLC layer sequence number RLC SN corresponding to these three PDCP data PDUs is {a, a+1, a+5}, and thus can consider that these three PDCP data PDUs have been successfully received. Assuming the lower boundary of the receive window, RX_NEXT, is 'a', and it matches the RLC layer sequence number RLC SN = 'a' corresponding to one of the three PDCP data PDUs, then the RLC entity at the receiving end can update the lower boundary of the RLC layer receive window to RX_NEXT = 'a+1'. Further, if the updated lower boundary RX_NEXT matches the RLC layer sequence number RLC SN = 'a+1' corresponding to another of the three PDCP data PDUs, then the RLC entity at the receiving end can update the lower boundary of the RLC layer receive window to RX_NEXT = 'a+2'. Further, if the updated lower boundary RX_NEXT does not match the RLC layer sequence number RLC SN = 'a+5' corresponding to another of the three PDCP data PDUs, then the RLC entity at the receiving end does not update the lower boundary of the RLC layer receive window. The RLC SDU corresponding to the RLC layer sequence number RLC SN = 'a+2' is the next SDU that was not received in order or was not considered a successful reception.

[0241] In one possible implementation, the second communication device can be a transmitting end, and the RLC entity of the receiving end can also send a second indication information to the RLC entity of the transmitting end. The second indication information is used to instruct the RLC entity of the transmitting end to stop sending the second data.

[0242] Optionally, the second indication information may include ACK information associated with the second data, such as the second indication information may include the SN of the second data.

[0243] Optionally, the second indication information may not include the NACK information associated with the second data; for example, the second indication information may not include the SN of the second data.

[0244] The second indication information can be an RLC status report, which can include one acknowledgment sequence number ACK_SN, L NACK_SNs and K NACK ranges, where L and K are integers greater than or equal to 0. NACK_SN represents the SN of the SDU that the receiver failed to receive. NACK range is after a certain NACK_SN and is used to indicate that the consecutive NACK range SDUs after that NACK_SN have not been received successfully. ACK_SN indicates that the RLC SDU whose SN is less than ACK_SN and was not indicated as unreceived by NACK_SN and NACK range has been successfully received.

[0245] Therefore, in the RLC status report, ACK_SN can be set to be greater than the SN of the second data, and NACK_SN can be set to be not equal to the SN of the second data. The SN range of the SDUs that were not successfully received, indicated by NACK range, also does not include the SN of the second data.

[0246] In one possible implementation, if the receiving RLC entity receives the second data or a portion of the second data (e.g., a segment of the second data), it can discard it directly.

[0247] In one possible implementation, the first communication device and the second communication device are respectively a terminal device and a network device; or, the first communication device and the second communication device are respectively a network device and a terminal device; or, both the first communication device and the second communication device are terminal devices.

[0248] In the above embodiment, the PDCP entity of the receiving end indicates to the RLC entity of the receiving end that it will no longer wait for the sequence number of the data packet to be received. The RLC entity of the receiving end considers that the data packet has been successfully received, updates the lower boundary of the receiving window, and no longer feeds back NACK information through the RLC status report. This can terminate the unnecessary data packet retransmission process of the AM RLC entity of the sending end and improve the utilization of air interface resources.

[0249] It should be noted that some steps in the above embodiments are not essential; that is, some steps are optional and can be omitted or replaced by other steps. Furthermore, the above embodiments do not limit the execution order of the method steps.

[0250] To achieve the functions of the methods provided in the embodiments of this application, both the terminal device and the network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0251] Please refer to Figure 12, which shows a schematic diagram of a communication device according to an embodiment of this application. The communication device can be a terminal device or a network device, or a device compatible with a terminal device or a network device, or it can also be a chip system. In one possible implementation, the communication device may include modules or units corresponding to the methods / operations / steps / actions performed by the communication device in the method embodiments shown in Figures 4, 9, or 11. These units can be hardware circuits, software, or a combination of hardware circuits and software.

[0252] The communication device shown in Figure 12 may include a processing unit 1201 and a communication unit 1202. The processing unit 1201 is used for data processing. The communication unit 1202 integrates a receiving unit and a transmitting unit. The communication unit 1202 may also be referred to as a transceiver unit. Alternatively, the communication unit 1202 may be split into a receiving unit and a transmitting unit.

[0253] When the communication device is used to perform some or all of the functions in the method embodiment described in FIG4 above, the communication unit 1202 is used for the first entity of the communication device to send service information to at least one second entity of the communication device, and for the first entity of the communication device to send control information to at least one third entity of the communication device; the processing unit 1201 is used for the third entity of the communication device to encapsulate the received control information to generate a data packet; the communication unit 1202 is also used for the second entity of the communication device to receive the service information sent by the first entity of the communication device, and for the third entity of the communication device to receive the control information sent by the first entity of the communication device; the communication unit 1202 is also used for the third entity of the communication device to send a data packet to the fourth entity of the communication device, and for the fourth entity of the communication device to receive the data packet sent by the third entity of the communication device.

[0254] When the communication device is used to perform some or all of the functions in the method embodiment described in FIG9 above, the communication unit 1202 is used for the first entity of the communication device to send data packets and indication information to the second entity of the communication device, and for the second entity of the communication device to send data packets to the third entity of the communication device; the processing unit 1201 is used for the second entity of the communication device to determine the sending order of data packets based on the indication information; the communication unit 1202 is also used for the second entity of the communication device to receive data packets and indication information sent by the first entity of the communication device, and for the third entity of the communication device to receive data packets sent by the second entity of the communication device.

[0255] When the communication device is used to perform some or all of the functions in the method embodiment described in FIG11 above, the communication unit 1202 is used to send a first indication message to a second entity of the first communication device, and the second entity of the first communication device receives the first indication message sent by the first entity of the first communication device; the processing unit 1201 is used to determine whether to update the expected data set based on the first indication message, and to update the expected data set; the communication unit 1202 is also used to send a second indication message to a second entity of the second communication device.

[0256] Figure 13 shows a schematic diagram of another communication device. The communication device 1300 can be the communication device in the above method embodiments, or it can be a chip, chip system, or processor that supports the communication device in implementing the above methods. This communication device 1300 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0257] The communication device 1300 may include one or more processors 1301. The processor 1301 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute software programs, and process data from the software programs.

[0258] Optionally, the communication device 1300 may include one or more memories 1302, which may store instructions 1304 that can be executed on the processor 1301, causing the communication device 1300 to perform the methods described in the above method embodiments. Optionally, the memory 1302 may also store data. The processor 1301 and the memory 1302 may be provided separately or integrated together.

[0259] Optionally, the communication device 1300 may further include a transceiver 1305 and an antenna 1306. The transceiver 1305 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1305 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0260] The processor 1301 is used to perform data processing operations of the communication device in the above method embodiment, and the transceiver 1305 is used to perform data transmission and reception operations of the communication device in the above method embodiment.

[0261] In another possible design, the processor 1301 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0262] In another possible design, the processor 1301 may optionally store instructions 1303, which, when executed on the processor 1301, cause the communication device 1300 to perform the methods described in the above method embodiments. Instructions 1303 may be embedded in the processor 1301; in this case, the processor 1301 may be implemented in hardware.

[0263] In another possible design, the communication device 1300 may include circuitry that can perform the functions of sending, receiving, or communicating as described in the foregoing method embodiments. The processors and transceivers described in this application embodiment can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc.

[0264] The communication device described in the above embodiments can be a transmitting end or a receiving end, but the scope of the communication device described in the embodiments of this application is not limited thereto, and the structure of the communication device is not limited to FIG13. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be:

[0265] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0266] (2) A collection of one or more ICs, optionally including a storage component for storing data and instructions;

[0267] (3) ASIC, such as modem (mobile station modem, MSM);

[0268] (4) Modules that can be embedded in other devices;

[0269] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, cloud devices, artificial intelligence devices, etc.

[0270] (6) Others, etc.

[0271] For communication devices that can be chips or chip systems, please refer to the schematic diagram of the chip structure shown in Figure 14. The chip shown in Figure 14 includes a processor 1401 and an interface 1402. Optionally, it may also include a memory 1403. The number of processors 1401 can be one or more, and the number of interfaces 1402 can be multiple.

[0272] In one design, for a chip used to implement the function of the communication device in the embodiments of this application: the interface 1402 is used to input or output signals; the processor 1401 is used to execute the data processing operation of the communication device in the above method embodiments.

[0273] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the communication device given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0274] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

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

[0276] This application also provides a computer-readable medium for storing computer software instructions that, when executed by a communication device, implement the functions of any of the above method embodiments.

[0277] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0278] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer 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. For example, 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 accessible to a computer 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., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0279] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

Claims

A method of information transmission, characterized in that The method includes: A first entity of the communication device sends service information to at least one second entity of the communication device; The first entity of the communication device sends control information of the first entity to at least one third entity of the communication device; The first entity is used to implement the packet data aggregation function, the second entity is used to implement the radio link control function, and the third entity is used to implement the function of the first entity or the function of the second entity. When the third entity is used to implement the function of the second entity, the second entity that receives the service information is independent of the third entity that receives the control information. The method according to claim 1, characterized in that, When the third entity of the communication device is used to implement the function of the first entity of the communication device, the third entity of the communication device sends the control information and instruction information to the fourth entity of the communication device. The instruction information is used to instruct the first entity, and the fourth entity is used to implement the wireless link control function; or... When the third entity of the communication device is used to implement the function of the second entity of the communication device, the third entity of the communication device sends the control information and the instruction information to the fourth entity of the communication device. The instruction information is used to instruct the first entity, and the fourth entity is used to implement the media access control function. The method according to claim 2, characterized in that, When the third entity and the fourth entity of the communication device belong to the entities included in the user plane bearer, the third entity of the communication device sends the control information and the instruction information to the fourth entity of the communication device; or, When the third entity and the fourth entity of the communication device are entities included in the control plane, the third entity of the communication device is also used to send control information of the fifth entity of the communication device to the fourth entity of the communication device, and the fifth entity is used to implement the radio resource control function. The method according to any one of claims 1 to 3, characterized in that The first entity sends its control information to the at least one third entity, including: When there are multiple third entities, the first entity sends the control information to the third entity among the multiple third entities that has the fewest cached data packets or the smallest amount of cached data. The method according to any one of claims 1 to 4, characterized in that, The first entity is an entity of the Packet Data Convergence Protocol (PDCP) layer, the second entity is an entity of the Radio Link Control (RLC) layer, the third entity is an entity of the PDCP layer or the RLC layer, and the fourth entity is an entity of the RLC layer or the Media Access Control (MAC) layer. The method according to any one of claims 1 to 5, characterized in that The communication device is a terminal device or a network device. A method of information transmission, characterized in that The method includes: A first entity of the communication device sends a data packet and indication information to a second entity of the communication device, the indication information being used to indicate the priority of the data packet; Based on the priority of the data packet, the second entity of the communication device sends the data packet to the third entity of the communication device; The first entity is used to implement packet data aggregation function, the second entity is used to implement wireless link control function, and the third entity is used to implement media access control function. The method of claim 7, wherein When the indication information indicates that the data packet includes control information, the second entity sends the data packet to the third entity first. The method according to claim 7 or 8, characterized in that, The first entity is an entity of the Packet Data Convergence Protocol (PDCP) layer, the second entity is an entity of the Radio Link Control (RLC) layer, and the third entity is an entity of the Media Access Control (MAC) layer. The method according to any one of claims 7 to 9, characterized in that The communication device is a terminal device or a network device. A communication device characterized by comprising: The device includes a processor coupled to a memory for storing instructions that, when executed by the processor, cause the communication device to perform the method of any one of claims 1 to 6, or cause the communication device to perform the method of any one of claims 7 to 10. A computer-readable storage medium having instructions stored thereon, characterized in that, When the instructions are executed, they cause the computer to perform the method of any one of claims 1 to 6, or cause the computer to perform the method of any one of claims 7 to 10. A computer program product comprising instructions, characterized in that, When the instructions are executed, they cause the computer to perform the method of any one of claims 1 to 6, or cause the computer to perform the method of any one of claims 7 to 10. A chip characterized in that, The chip includes a processor and a communication interface, the communication interface being used to communicate with external or internal devices, and the processor being used to implement the method of any one of claims 1 to 6, or to implement the method of any one of claims 7 to 10.

Images