Communication method and apparatus, communication device, chip, storage medium, program, and program product

Abstract

Embodiments of the present application provide a communication method and apparatus, a communication device, a chip, a storage medium, and a program. The method comprises: a sending end performs, by using a first entity, one or more of the following operations on data sent by a higher layer: compression, encryption, integrity protection, packet discard instruction, packet discard processing, data segmentation, data retransmission, and routing.

Description

Communication methods and devices, communication equipment, chips, storage media, programs, and program products Technical Field

[0001] This application relates to the field of mobile communication technology, specifically to a communication method and apparatus, communication equipment, chip, storage medium, program, and program product. Background Technology

[0002] The New Radio (NR) user plane protocol stack's Layer 2 (L2) includes the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and other layers.

[0003] The PDCP and RLC layers can perform different functions, but some functions are redundant, such as data retransmission. For scenarios with high data transmission rate requirements, the execution of redundant functions in PDCP and RLC can lead to increased processing latency.

[0004] Summary of the Invention

[0005] This application provides a communication method and apparatus, a communication device, a chip, a storage medium, a program, and a program product.

[0006] In a first aspect, the communication method provided in the embodiments of this application includes:

[0007] The sending end performs one or more of the following operations on the data sent by the higher layer through the first entity: compression, encryption, integrity protection, packet drop indication, packet drop handling, data segmentation, data retransmission, and routing.

[0008] Secondly, the communication method provided in the embodiments of this application includes:

[0009] The receiving end performs one or more of the following operations on the data sent by the lower layer through the first entity: data retransmission request, data reassembly, integrity verification, packet drop indication, packet drop processing, decryption, decompression, and delivery of data packets to the higher layer.

[0010] Thirdly, the communication method provided in the embodiments of this application includes:

[0011] The sending end sends a first data packet, and the PDCP entity and the first RLC entity of the sending end use the same first sequence number (SN) information when operating on the first data packet.

[0012] Fourthly, the communication method provided in the embodiments of this application includes:

[0013] The first data packet received by the receiving end, the PDCP entity and the first RLC entity of the receiving end use the same first SN information when operating on the first data packet.

[0014] Fifthly, the communication device provided in the embodiments of this application includes:

[0015] The first processing unit is configured to perform one or more of the following operations on the data sent by the higher layer through the first entity: compression, encryption, integrity protection, packet drop indication, packet drop processing, data segmentation, and data retransmission.

[0016] Sixthly, the communication device provided in the embodiments of this application includes:

[0017] The second processing unit is configured to perform one or more of the following operations on the data sent by the lower layer through the first entity: data retransmission request, data reassembly, integrity verification, packet drop indication, packet drop processing, decryption, and decompression.

[0018] Seventhly, the communication device provided in the embodiments of this application includes:

[0019] The third communication unit is configured to send a first data packet, wherein the PDCP entity and the first RLC entity of the first communication unit use the same first SN information when operating on the first data packet.

[0020] Eighthly, the communication device provided in the embodiments of this application includes:

[0021] The fourth communication unit is configured to receive the first data packet, wherein the PDCP entity and the first RLC entity of the second communication unit use the same first SN information when operating on the first data packet.

[0022] Ninthly, the communication device provided in the embodiments of this application includes a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to execute the communication method described above.

[0023] The chip provided in this application embodiment is used to implement the above-described communication method.

[0024] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned communication method.

[0025] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to perform the above-described communication method.

[0026] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described communication method.

[0027] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described communication method.

[0028] This application provides a communication method in which the sending end performs one or more of the following operations on data sent by a higher layer through a first entity: compression, encryption, integrity protection, packet drop indication, packet drop processing, data segmentation, data retransmission, and routing. Correspondingly, the receiving end performs one or more of the following operations on data sent by a lower layer through the first entity: data retransmission request, data reassembly, integrity verification, packet drop indication, packet drop processing, decryption, decompression, and delivery of data packets to a higher layer. It can be seen that the first entity can not only implement the functions of the PDCP entity (compression / decompression, encryption / decryption, integrity protection / integrity verification, packet drop indication, packet drop processing, routing, and delivery of data packets to a higher layer), but also the functions of the RLC entity (data segmentation / reassembly and retransmission). This avoids repetitive operations of the same functions in the PDCP and RLC entities, simplifies the protocol stack, and reduces processing latency. Attached Figure Description

[0029] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0030] Figure 1 is a schematic diagram of an application scenario of an embodiment of this application;

[0031] Figure 2 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0032] Figure 3 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0033] Figure 4 is a schematic diagram of a communication method provided in an embodiment of this application;

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

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

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

[0037] Figure 8 is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0038] Figure 9 is a schematic structural diagram of a chip according to an embodiment of this application;

[0039] Figure 10 is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0041] Figure 1 is a schematic diagram of an application scenario of an embodiment of this application.

[0042] As shown in Figure 1, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0043] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as NR communication system), or future communication systems, etc.

[0044] In the communication system 100 shown in Figure 1, the network device 120 can be an access network device that communicates with the terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with the terminal device 110 located within that coverage area.

[0045] Network device 120 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or network device 120 may be a relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0046] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connections.

[0047] For example, terminal equipment 110 can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. An access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal equipment in a 5G network, or terminal equipment in a future evolved network, etc.

[0048] Terminal device 110 can be used for device-to-device (D2D) communication.

[0049] Figure 1 illustrates an exemplary network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0050] It should be noted that Figure 1 is merely an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably in this document.

[0051] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0052] It should be understood that the terms "first, second, third" used in the embodiments of this application are only used to distinguish similar objects and do not represent a specific order of objects. It is understood that "first, second, third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0053] It should also be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0054] It should also be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0055] It should also be understood that the term "correspondence" mentioned in the embodiments of this application may indicate a direct or indirect correspondence between the two, or an association between the two, or a relationship of instruction and being instructed, configuration and being configured, etc.

[0056] It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in the device (e.g., including the sending end and the receiving end), and this application does not limit the specific implementation method. For example, predefined can refer to what is defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit it.

[0057] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0058] Driven by the pursuit of speed, latency, high-speed mobility, and energy efficiency, and the increasing diversity and complexity of services in future lives, the 3rd Generation Partnership Project (3GPP) international standards organization began developing 5G. The main application scenarios for 5G are: Enhanced Mobile Broadband (eMBB), Ultra Reliable and Low Latency Communications (URLLC), and Massive Machine Type Communication (mMTC). A brief introduction to these three application scenarios follows.

[0059] eMBB aims to provide users with multimedia content, services, and data, and its demand is growing rapidly. Furthermore, because eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, its capabilities and needs vary considerably. Therefore, generalizations cannot be made; a detailed analysis based on the specific deployment scenario is necessary.

[0060] Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), and traffic safety assurance.

[0061] Typical characteristics of mMTC include: high connection density, small data volume, latency-insensitive services, low module cost, and long service life.

[0062] NR can also be deployed independently. In 5G network environments, to reduce air interface signaling, quickly restore radio connections, and quickly restore data services, a new Radio Resource Control (RRC) state is defined: the RRC Inactive (RRC_INACTIVE) state. This state is different from the RRC Idle (RRC_IDLE) and RRC Active (RRC_ACTIVE) states. The following is a brief explanation of these three states.

[0063] RRC_INACTIVE state: Mobility is based on cell selection and reselection of the terminal device, there is a connection between the Core Network (CN) and the NR, the terminal device's Access Stratum (AS) context exists on a satellite, paging is triggered by the RAN, the paging area based on the RAN is managed by the RAN, and the satellite knows the location of the terminal device at the paging area level based on the RAN.

[0064] RRC_IDLE state: Mobility is based on terminal device cell selection reselection; paging is initiated by the CN; the paging area is configured by the CN. There is no terminal device AS context on the network device side. No RRC connection exists.

[0065] RRC_ACTIVE state: An RRC connection exists, and the network device and the terminal device have an AS context. The network device knows the location of the terminal device at the cell level. Mobility is controlled by the network device. Unicast data can be transmitted between the terminal device and the network device.

[0066] The L2 layer of the NR user plane protocol stack can be divided into four sub-layers: Media Access Control (MAC) layer, RLC layer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer.

[0067] For uplink transmission, the PDCP layer is mainly responsible for processing the PDCP Service Data Units (SDUs) received from the SDAP layer, generating PDCP Protocol Data Units (PDUs), and then submitting them to the corresponding RLC layer.

[0068] For downlink transmission, the PDCP layer is primarily responsible for receiving PDCP PDUs from the RLC layer, processing them to remove the PDCP header, and then delivering them to the SDAP layer. There is a one-to-one correspondence between the PDCP layer and radio bearers; that is, each radio bearer (including the Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB)) is associated with a PDCP entity. Most of the functions provided by the NR PDCP layer are similar to those in LTE, and can mainly include the following aspects.

[0069] Maintenance of sequence numbers for the sender or receiver at the PDCP layer;

[0070] Header compression and decompression;

[0071] Encryption and decryption;

[0072] Integrity protection;

[0073] Timer-based PDCP SDU discarding;

[0074] Routing functionality;

[0075] Copy and transfer function;

[0076] Reordering and sequential submission functionality.

[0077] The PDCP layer is similar to LTE in its data transmission and reception process. The improvement of NR PDCP compared to LTE lies in its use of absolute count values ​​(COUNT) for local variable maintenance and condition comparisons during data transmission and reception. This improves protocol readability. The COUNT can include a serial number (SN) and a superframe number, with a fixed size of 32 bits. It's important to note that the header of the PDCP PDU still includes the SN, not the COUNT value, thus not increasing air interface transmission overhead.

[0078] For example, for uplink transmission, the PDCP transmission side maintains a local COUNT value for TX_NEXT, initially set to 0. Each time a new PDCP PDU is generated, the SN in the corresponding header is set to the value corresponding to TX_NEXT, and TX_NEXT is incremented by 1. The PDCP transmission side performs header compression, integrity protection, and encryption operations on the PDCP SDU sequentially according to the network configuration. For downlink transmission, the PDCP receiving side maintains a receive window based on the COUNT value of a local variable. This receive window is maintained by the following local variables.

[0079] RX_NEXT: The COUNT value corresponding to the next expected PDCP SDU.

[0080] RX_DELIV: The COUNT value corresponding to the next PDCP SDU expected to be delivered to the uplink. This variable determines the lower boundary of the receive window.

[0081] RX_REORD: The COUNT corresponding to the PDCP PDU that triggered the sorting timer.

[0082] Based on the PUSH window mechanism, the PDCP receiver processes the received PDCP PDU.

[0083] NR PDCP also supports data replication. Simply put, based on network-side configuration and activation commands, PDCP PDUs can be replicated into two identical copies and delivered to different RLC entities.

[0084] In related technologies, the PDCP layer and RLC layer can implement different functions, but some functions are redundant, such as data retransmission. Additionally, both PDCP and RLC require adding their respective serial number (SN) information to the packet header. For scenarios with high data transmission rate requirements, the execution of redundant functions, or the addition of multiple layers of SN information, can lead to increased processing latency.

[0085] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0086] It should be noted that data packets are mentioned multiple times in the following embodiments. It can be understood that, in general, the number of data packets can be one or more, and the embodiments of this application do not limit this.

[0087] It should be noted that the entities mentioned in the embodiments of this application can also be referred to as protocol layers or protocol layer entities, and the three are equivalent or interchangeable. PDCP entities can also be referred to as PDCP layers or PDCP, and the three are equivalent or interchangeable. RLC entities can also be referred to as RLC layers or RLC, and the three are equivalent or interchangeable.

[0088] It should also be noted that, in the embodiments of this application, the transmitting or receiving PDCP entity can be understood as a functional module in the transmitting or receiving end used to implement PDCP-related operations. Therefore, the execution of operations by the transmitting or receiving PDCP entity can be understood as the transmitting or receiving end performing operations through the functional module used to implement PDCP-related operations. In the embodiments of this application, the execution of operations by the transmitting or receiving PDCP entity can also be referred to as the transmitting or receiving end performing operations through the PDCP entity; the two are equivalent or interchangeable.

[0089] Correspondingly, in the embodiments of this application, the transmitting or receiving RLC entity can be understood as a functional module in the transmitting or receiving end used to implement RLC-related operations. Therefore, the execution of operations by the transmitting or receiving RLC entity can be understood as the transmitting or receiving end performing operations through the functional module used to implement PDCP-related operations. In the embodiments of this application, the execution of operations by the transmitting or receiving RLC entity can also be referred to as the transmitting or receiving end performing operations through the RLC entity; the two are equivalent or interchangeable.

[0090] Correspondingly, in the embodiments of this application, the first entity of the transmitting or receiving end can be understood as a functional module in the transmitting or receiving end used to implement at least some of the functions or operations in PDCP and / or RLC. Therefore, the execution of an operation by the first entity of the transmitting or receiving end can be understood as the transmitting or receiving end performing an operation through this functional module (i.e., the functional module used to implement at least some of the functions or operations in PDCP and / or RLC). In the embodiments of this application, the execution of an operation by the first entity of the transmitting or receiving end can also be referred to as the transmitting or receiving end performing an operation through the first entity; the two are equivalent or interchangeable.

[0091] Figure 2 is a flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 2, the method may include the following steps.

[0092] S210. The sending end performs one or more of the following operations on the data sent by the higher layer through the first entity: compression, encryption, integrity protection, packet drop indication, packet drop processing, data segmentation, data retransmission, and routing.

[0093] Accordingly, the receiving end performs one or more of the following operations on the data sent by the lower layer through the first entity: instructing the sending end whether to retransmit the data, reassemble the data, verify the integrity, indicate packet drop, handle packet drop, decrypt, decompress, and deliver the data packet to the higher layer.

[0094] It should be noted that the first entity can also be called the first protocol layer, or the first protocol layer entity; the three are equivalent or interchangeable.

[0095] It should also be noted that the sending end can be located on the terminal device side, and the receiving end can be located on the network device side; or, the sending end can be located on the network device side, and the receiving end can be located on the terminal device side.

[0096] It should be understood that the first entity of the sending end can be a sending entity, which can perform pre-transmission processing on the data sent by higher layers (such as SDAP entities or other protocol layer entities). In the embodiments of this application, the first entity of the sending end can perform compression, encryption, integrity protection, packet drop indication, packet drop processing, data segmentation, routing, and data retransmission on the data sent by higher layers.

[0097] It should be noted that compression can include header compression, uplink data compression (UDC), etc., and this application embodiment does not limit this. Among them, header compression can include robust header compression (ROHC), Ethernet header compression (EHC), etc., and this application embodiment does not limit this.

[0098] It should also be noted that the data retransmission function may include data retransmission in the Automatic Repeat reQuest (ARQ) mechanism, or data retransmission triggering, and this application embodiment does not limit this.

[0099] It should be understood that the first entity at the receiving end can be a receiving entity, which can process data sent by lower layers (such as MAC entities or other protocol layer entities). In the embodiments of this application, the first entity at the receiving end can perform decompression, deciphering, integrity verification, packet drop indication, packet drop processing, data reassembly, delivery of data packets to higher layers, data retransmission requests, and other processing on the data transmitted at lower layers.

[0100] It should be noted that packet dropping can also be called data dropping; the two are equivalent or interchangeable. In other words, a packet dropping instruction can also be understood as a data dropping instruction, and packet dropping processing can also be understood as data dropping processing.

[0101] Compared to the PDCP and RLC entities in related technologies, the first entity in this application embodiment can not only implement the compression / decompression, encryption / decryption, integrity protection / integrity verification, packet drop indication, packet drop processing, and routing functions of the PDCP entity, but also the data segmentation / reassembly and retransmission functions of the RLC entity. This avoids repetitive operations of the same functions in the PDCP and RLC entities, simplifies the protocol stack, and reduces processing latency.

[0102] In some embodiments, the first entity replaces the PDCP entity and the RLC entity; or...

[0103] The first entity is a PDCP entity, and the RLC entity does not exist; or,

[0104] The first entity is an RLC entity, and the PDCP entity does not exist.

[0105] It should be noted that replacing the PDCP and RLC entities with the first entity can be understood as creating a new entity distinct from the PDCP and RLC entities. This new entity possesses functions such as compression / decompression, encryption / decryption, integrity protection / integrity verification, packet drop indication, packet drop handling, data segmentation / reassembly, and data retransmission. In this case, the PDCP and RLC entities can still exist, but they will no longer possess the aforementioned functions.

[0106] It should also be noted that if the first entity is a PDCP entity and the RLC entity does not exist, it can be understood as removing the RLC entity and moving its functions (data segmentation, data reassembly, data retransmission, etc.) to the PDCP entity; or it can be understood as merging the functions of the RLC entity (data segmentation, data reassembly, data retransmission, etc.) into the PDCP entity. In this case, the PDCP entity can perform the same data segmentation, data reassembly, and data retransmission functions as the RLC entity.

[0107] It should also be noted that if the first entity is an RLC entity and the PDCP entity does not exist, it can be understood as removing the PDCP entity and moving its functions (compression / decompression, encryption / decryption, integrity protection / authentication, packet drop indication, packet drop handling, and routing) down to the RLC entity. Alternatively, it can be understood as merging the functions of the PDCP entity (compression / decompression, encryption / decryption, integrity protection / authentication, packet drop indication, packet drop handling, and routing) into the RLC entity. In this case, the RLC entity can implement functions such as compression / decompression, encryption / decryption, integrity protection / authentication, packet drop indication, packet drop handling, and routing as performed by the PDCP entity.

[0108] In some embodiments, the sending end receives first information, wherein the first information is used to configure the function of the first entity or the protocol layer corresponding to the first entity, and / or, the first information is used to configure parameters related to one or more of the following functions:

[0109] compression;

[0110] encryption;

[0111] Integrity protection;

[0112] Data segmentation;

[0113] Packet discard instruction;

[0114] Packet disposal;

[0115] Data retransmission;

[0116] routing.

[0117] It should be understood that the first sending entity, the corresponding protocol layer function of the first sending entity, and the parameters related to the corresponding protocol layer function of the first sending entity can be configured by the network. Specifically, the network can configure one or more of the following through the first information: the first sending entity, the corresponding protocol layer function of the first sending entity, and the parameters related to the corresponding protocol layer function of the first sending entity.

[0118] The first information can configure the first entity of the sending end to implement one or more of the following functions, or configure the protocol layer functions corresponding to the first entity of the sending end to include one or more of the following: compression, encryption, integrity protection, data segmentation, packet drop indication, packet drop processing, data retransmission, and routing.

[0119] In addition, the parameters related to the protocol layer functions corresponding to the first entity of the sending end may include parameters related to functions such as compression, encryption, integrity protection, data segmentation, packet drop indication, packet drop handling, routing, and data retransmission.

[0120] For example, parameters related to encryption functionality may include encryption algorithms, keys, and other parameters.

[0121] For example, parameters related to the data retransmission function of the sending end may include the maximum retransmission threshold (maxRetxThreshold), the polling protocol data unit number threshold (pollpdu), the poll retransmission timer (t-PollRetransmit), etc., and this application embodiment does not limit these parameters.

[0122] For example, the parameters related to the packet drop indication function may include packet drop timer parameters, packet drop indication identifier, packet drop indication format, etc., and this application embodiment does not limit these parameters.

[0123] It should be noted that the first information can be included / carried in Radio Resource Control (RRC) signaling. For example, the first information can be carried through RRC reconfiguration information, RRC resume information, or RRC setup information, and this application embodiment does not limit this.

[0124] In some embodiments, the first information is further used to configure the operating mode of the sending end first entity; wherein the operating mode includes at least Unacknowledged Mode (UM) and Acknowledged Mode (AM). Specifically, in AM mode, the sending end first entity configures or activates the data retransmission function; in UM mode, the sending end first entity does not configure or activate the data retransmission function.

[0125] It should be noted that the first entity in AM mode can be understood as the first entity with ARQ (with ARQ). The first entity in UM mode can be understood as the first entity without ARQ (without ARQ).

[0126] In some embodiments, the receiving end receives second information; the second information is used to configure the function of the first entity or the protocol layer corresponding to the first entity, and / or, the second information is used to configure parameters related to one or more of the following functions:

[0127] Decompress;

[0128] Decrypt;

[0129] Integrity verification;

[0130] Data retransmission;

[0131] Packet discard instruction;

[0132] Packet disposal;

[0133] Data restructuring;

[0134] Submit data packets to higher management.

[0135] It should be understood that the receiving end first entity, the protocol layer function corresponding to the receiving end first entity, and the parameters related to the protocol layer function corresponding to the receiving end first entity can also be configured by the network. Specifically, the network can configure one or more of the following through the second information: the receiving end first entity, the protocol layer function corresponding to the receiving end first entity, and the parameters related to the protocol layer function corresponding to the receiving end first entity.

[0136] The second information can configure the first entity of the receiving end to perform one or more of the following functions, or configure the protocol layer functions corresponding to the first entity of the receiving end to include one or more of the following: decompression, decryption, integrity verification, data reassembly, packet drop indication, packet drop processing, data retransmission, and delivery of data packets to higher layers.

[0137] In addition, the parameters related to the protocol layer functions corresponding to the first entity of the receiving end may include parameters related to functions such as decompression, decryption, integrity verification, data reassembly, packet drop indication, packet drop processing, delivery of data packets to higher layers, and data retransmission.

[0138] For example, parameters related to the decryption function may include decryption algorithms, keys, and other parameters.

[0139] For example, the parameters related to the data retransmission function of the receiving end may include a status report prohibition timer (t-StatusProhibit) or other parameters, and this application embodiment does not limit this.

[0140] For example, the parameters related to the packet drop indication function may include packet drop timer parameters, packet drop indication identifier, packet drop indication format, etc., and this application embodiment does not limit these parameters.

[0141] It should be noted that the second information can be included / carried in RRC signaling. For example, the second information can be carried through RRCReconfiguration, RRCResume, or RRCSetup, and this application embodiment does not limit this.

[0142] In some embodiments, the second information is further used to configure the operating mode of the first entity at the receiving end; wherein the operating mode includes at least UM and AM. Specifically, in AM mode, the first entity at the receiving end configures or activates the data retransmission function; in unacknowledged mode, the first entity at the receiving end does not configure or activate the data retransmission function.

[0143] It should be noted that the first entity in AM mode can be understood as the first entity with ARQ (with ARQ). The first entity in UM mode can be understood as the first entity without ARQ (without ARQ).

[0144] In some embodiments, for the sending end, the data segmentation operation performed by the first entity of the sending end can be performed after the compression operation; or, after the encryption operation; or, after the integrity protection operation.

[0145] Understandably, when the sending end first entity supports / has / is configured / activated to perform data segmentation, the data segmentation operation can be performed after the first entity has performed one or more of the following operations on the data sent from the higher layer: compression, encryption, or integrity protection. In other words, the sending end first entity can first perform one or more of the following operations on the data sent from the higher layer: compression, encryption, and integrity protection, and then the sending end first entity can perform data segmentation on the data after these operations have been completed.

[0146] Accordingly, in some embodiments, for the receiving end, the data reassembly operation of the first entity of the receiving end can be performed before the decompression operation, or before the decryption operation, or before the integrity verification operation.

[0147] Understandably, if the receiving end first entity supports / has / is configured / activated to perform data reassembly, the receiving end first entity can perform data reassembly after performing one or more of the following operations on the data sent by the sending end: decompression, decryption, or integrity verification. In other words, the receiving end first entity can first reassemble the data, and then perform one or more of the following operations: decompression, decryption, and integrity verification.

[0148] It should be noted that the terms "support", "have", "configured", and "activate" in the embodiments of this application can be used interchangeably, all indicating that the corresponding entity (such as the first entity in the above embodiments) can perform the corresponding function or operation.

[0149] In some embodiments, for the sending end, the data retransmission operation of the first entity of the sending end can be performed before the data segmentation operation, or after the data segmentation operation, or before the compression operation.

[0150] Understandably, if the first entity at the sending end supports / has / is configured / activated to perform data retransmission, the first entity at the sending end can perform data retransmission first and then perform data segmentation; or, the first entity at the sending end can perform data segmentation first and then perform data retransmission; or, the first entity at the sending end can perform data retransmission first and then perform compression.

[0151] It should be noted that the data retransmission operation after the data segmentation operation can be understood as the data retransmission operation being performed immediately after the sending end first entity performs data segmentation, or it can be understood as the sending end first entity performing other operations after performing data segmentation, and then performing the data retransmission operation after the other operations are completed. This application embodiment does not impose any restrictions on this.

[0152] It should be noted that the data retransmission operation before the data segmentation operation can be understood as the data segmentation operation being performed immediately after the first entity at the sending end performs the data retransmission operation, or it can be understood as the first entity at the sending end performing other operations after the data retransmission operation, and then performing the data segmentation operation after the other operations are completed. This application embodiment does not impose any restrictions on this.

[0153] It should also be noted that the data retransmission operation before the compression operation can be understood as either the first entity at the sending end performing the data retransmission operation and immediately performing the compression operation, or it can be understood as the first entity at the sending end performing the data retransmission operation and then performing other operations, and performing the compression operation after the other operations are completed. This application embodiment does not impose any restrictions on this.

[0154] For example, the sending end first entity may perform the following operations on the data from the higher layer in sequence: compression, encryption, integrity protection, data retransmission, and data segmentation.

[0155] For example, the sending end first entity performs the following operations on the data from the higher layer in sequence: compression, encryption, integrity protection, data segmentation, and data retransmission.

[0156] For example, the sending end first entity performs the following operations on the data from the higher layer in sequence: data retransmission, compression, encryption, integrity protection, and data segmentation.

[0157] In some embodiments, for the transmitting end, when the first entity of the transmitting end supports / has / is configured / activated to perform data segmentation, the PDU corresponding to the first entity may include segmentation indicator information (SI) and / or segmentation offset information (SO).

[0158] Accordingly, in some embodiments, for the receiving end, when the first entity of the receiving end supports / has / is configured / activated to perform data reassembly, the PDU corresponding to the first entity includes SI and / or SO.

[0159] In other words, when the first entity supports / has / is configured / activated to perform data segmentation and data segmentation, it can carry SI and / or SO in the PDU header of the first entity to indicate the segmentation information associated with each PDU.

[0160] For example, assuming the first entity is a PDCP entity and the RLC entity does not exist, if the PDCP entity can support / have / be configured / activated data segmentation functionality, then the receiving PDCP entity can carry SI and / or SO in the PDCP PDU header. SI and / or SO can occupy several bits in the existing PDCP PDU header, or the PDCP PDU header can use newly added bytes to carry SI and / or SO.

[0161] In some embodiments, for the sending end, if the first entity of the sending end supports / has / is configured / activated to perform data segmentation, and if the first entity does not support / does not have / is not configured / activated to perform data retransmission, then the sending end executes the parameter update mechanism related to UM mode; or...

[0162] If the first entity at the sending end supports / has / is configured / activated for data segmentation, and the first entity supports / has / is configured / activated for data retransmission, then the sending end executes the parameter update mechanism related to AM mode.

[0163] Accordingly, in some embodiments, for the receiving end, if the first entity of the receiving end supports / has / is configured / activated the data reassembly function, but the first entity of the receiving end does not support / does not have / is not configured / activated the data retransmission function, then the receiving end executes the parameter update mechanism related to UM mode.

[0164] Alternatively, if the first entity at the receiving end supports / has / is configured / activated to perform data reassembly, and if the first entity at the receiving end supports / has / is configured / activated to perform data retransmission, then the receiving end executes the parameter update mechanism related to AM mode.

[0165] In some embodiments, where the sending end first entity and the receiving end first entity support / have / are configured / activated for data retransmission functionality, the method provided in this application embodiment further includes:

[0166] The receiving end first entity sends a retransmission indication message to the sending end first entity;

[0167] The sending end first entity receives retransmission indication information sent by the receiving end first entity;

[0168] The first entity at the sending end executes a retransmission based on the retransmission instruction information.

[0169] It should be noted that the retransmission indication message can indicate whether data has been received or not.

[0170] It should be noted that retransmission indication information can be understood as confirmation information. For example, retransmission indication information can be NACK information or ACK information.

[0171] In one implementation, the retransmission indication message indicates that the data was not received, or the retransmission indication message is a NACK message, or the data is missing. The sending first entity can determine or consider that the data was not successfully transmitted, and / or the sending first entity can perform a retransmission.

[0172] For example, if the first entity is a PDCP entity and the RLC entity does not exist, the PDCP entity may consider packets (including PDCP SDU / PDU) that are indicated as not received, NACK, or missing to have been transmitted unsuccessfully, and / or perform a retransmission.

[0173] In one implementation, for data that has been received by a retransmission indication message or is an ACK message, the sending first entity may determine / consider that the data has been successfully transmitted, and / or, the sending first entity may not perform a retransmission, and / or, the sending first entity may perform a sender-discard.

[0174] In some embodiments, for the sending end, when the first entity of the sending end supports / has / is configured / activated with packet drop indication and / or packet drop processing functions, the method provided in this application embodiment may include one or more of the following:

[0175] The sending end first entity receives the first packet drop indication information sent by the receiving end first entity;

[0176] The sending end first entity determines whether a data packet is to be discarded or is not needed based on the first packet drop indication information;

[0177] The first entity execution packet at the sending end is discarded;

[0178] If the first entity at the sending end discards the packet after the first duration has been met;

[0179] The sending entity sends a second packet drop indication to the receiving entity; the second packet drop indication is used by the receiving entity to execute packet drop.

[0180] Parameters related to the handling of discarding the first entity update packet at the sending end.

[0181] Understandably, if the sending first entity supports / has / is configured / activated with packet drop indication and / or packet drop processing functions, the sending first entity can perform packet drop processing on the transmitted data, and / or indicate packet drop on the transmitted data.

[0182] In one implementation, the sending end first entity can perform packet dropping based on the first packet dropping indication information sent by the receiving end first entity. Specifically, the sending end first entity can determine which data packets to drop or are unnecessary based on the first packet dropping indication information, and perform packet dropping on the indicated data packets to be dropped or unnecessary.

[0183] In one implementation, the sending entity can discard the packet after a first duration has been satisfied.

[0184] For example, the first duration can be the runtime of the discard timer corresponding to the data packet to be sent by the first entity at the sending end or the set to which the data packet belongs. That is, the first entity at the sending end can execute packet discarding when the discard timer expires. The aforementioned timer can be a PDCP discard timer or a PDCP discard timer for Positioning State Information (PSI).

[0185] It should be noted that the first duration can be predefined or configured by the network, and this application embodiment does not impose any restrictions on it.

[0186] In one implementation, the sending end first entity can perform packet dropping based on the first packet drop indication information and if a first duration is met. It is understood that the sending end first entity can determine which data packets to drop or are unnecessary based on the first packet drop indication information, and perform packet dropping on these data packets if the first duration is met.

[0187] In addition, the sending end first entity can also send a second packet drop indication message to the receiving end first entity to inform that data packets have been dropped or are not needed.

[0188] It should be noted that the sending first entity can issue a packet drop indication when performing packet drop, meaning that the sending first entity can send a second packet drop indication message to the receiving first entity after performing packet drop processing. Alternatively, the sending first entity can also choose not to issue a packet drop indication when performing packet drop processing, meaning that the sending first entity can choose not to send a second packet drop indication message to the receiving first entity after performing packet drop processing.

[0189] In one implementation, the first entity at the sending end can update the packet dropping processing parameters when executing packet dropping, for example, after executing packet dropping, the first entity at the sending end can reset the packet dropping timer.

[0190] Accordingly, for the receiving end, if the first entity of the receiving end supports / has / is configured / activated the discard indication and / or packet discard processing function, the embodiments of this application further include one or more of the following:

[0191] The receiving end first entity sends the first packet drop indication information to the sending end first entity;

[0192] If the second duration is satisfied, the receiving end first entity sends a first packet drop indication information to the sending end first entity; wherein, the first packet drop indication information is used by the sending end first entity to determine lost or unwanted data packets, and / or to perform packet drop;

[0193] The receiving end first entity receives the second packet drop indication information sent by the sending end first entity;

[0194] The receiving end first entity determines which data packets to discard or are not needed based on the second packet drop indication information;

[0195] The first entity execution packet at the receiving end is discarded;

[0196] If the third time interval is met, the first entity at the receiving end will discard the packet.

[0197] Parameters related to the handling of discarding the first entity update packet at the receiving end.

[0198] Understandably, if the receiving end first entity supports / has / is configured / activated with packet drop indication and / or packet drop processing functions, the receiving end first entity can give packet drop indication and / or perform packet drop processing on the received data.

[0199] It should be noted that the receiving end first entity can determine which data packets are discarded or unnecessary.

[0200] In one implementation, after determining that a data packet is to be discarded or is not needed, the receiving end first entity can directly send a first packet discard indication message to the sending end first entity, indicating that the data packet is to be discarded or is not needed.

[0201] In one implementation, the receiving end first entity may also send a first packet drop indication message to the sending end first entity when the second duration is met, indicating that the data packet is to be dropped or is not needed, thereby avoiding frequent sending of drop indication messages to the sending end. The second duration may be predefined or network-configured, and this embodiment does not impose any restrictions on it.

[0202] Understandably, the receiving end's first entity can also discard the packet.

[0203] In one implementation, the receiving end first entity can perform packet discarding based on the second packet discarding indication information sent by the sending end first entity. Specifically, the receiving end first entity can determine which data packets to discard or are unnecessary based on the second packet discarding indication information, and perform packet discarding on the indicated discardable or unnecessary data packets.

[0204] In one implementation, the sending entity can discard the packet if a third duration is satisfied.

[0205] For example, the third duration can be the runtime of the discard timer corresponding to the received data packet or the set to which the data packet belongs. That is, the receiving end first entity can perform packet discarding when the discard timer expires. The aforementioned timer can be a PDCP discard timer or a PDCP discard timer for PSI.

[0206] It should be noted that the third duration can be predefined or configured by the network, and this application embodiment does not impose any restrictions on it.

[0207] In one implementation, the sending end first entity can perform packet discarding based on the second packet discarding indication information and if a third duration is met. It is understood that the receiving end first entity can determine which data packets to discard or are unnecessary based on the second packet discarding indication information, and perform packet discarding if these data packets meet the third duration.

[0208] In one implementation, the first entity at the receiving end can update the packet dropping processing parameters when executing packet dropping, for example, after the first entity at the receiving end executes packet dropping, it can reset the packet dropping timer.

[0209] In some embodiments, for the sending end, the data routing operation performed by the first entity at the sending end may include the first entity determining which data packets are transmitted from which link. For example, retransmitted data packets are transmitted from the first link, and non-retransmitted data packets are transmitted from the first link or the second link. For example, retransmitted data packets are transmitted from the first grant, and non-retransmitted data packets are transmitted from the first grant or the second grant.

[0210] The method provided in this application embodiment enables the first entity to perform not only the PDCP entity's functions of compression / decompression, encryption / decryption, integrity protection / integrity verification, packet drop indication, packet drop handling, routing, and data packet delivery to higher layers, but also the RLC entity's functions of data segmentation / reassembly and retransmission. This avoids redundant operations of the same functions in the PDCP and RLC entities, simplifies the protocol stack, and reduces processing time.

[0211] Figure 3 is a second flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 3, the method may include the following steps:

[0212] S310. The sending end sends a first data packet, wherein the PDCP entity and the first RLC entity of the sending end use the same first SN information when operating on the first data packet.

[0213] Accordingly, the receiving end receives the first data packet, wherein the PDCP entity and the first RLC entity of the receiving end use the same first SN information when operating on the first data packet.

[0214] It should be noted that the first data packet can be any one or more data packets transmitted between the sending end and the receiving end. For example, the first data packet can be one or more RLC PDUs (RLC data PDUs).

[0215] It should be noted that a PDCP entity can correspond to / be associated with one or more RLC entities. Specifically, the first RLC entity can be the RLC entity among one or more RLC entities used to transmit the first data packet, or the first RLC entity is the RLC entity among one or more RLC entities associated with the first data packet, or the first RLC entity is the RLC entity among one or more RLC entities associated with the first SN information.

[0216] It should be noted that the first SN information is the SN information corresponding to the first data packet. The first SN information corresponding to the first data packet can be assigned by the PDCP entity or by the first RLC entity; this embodiment of the application does not impose any restrictions on this.

[0217] In this embodiment of the application, the PDCP entity and the first RLC entity use the same first SN information when operating on the first data packet. This can be understood as the PDCP entity and the first RLC entity sharing the first SN information corresponding to the first data packet, or as the PDCP entity and the first RLC entity adding a first SN information to the first data packet, or as the PDCP entity and the first RLC entity adding a first SN information once to the first data packet.

[0218] It should be noted that the data packet includes a data packet header. The PDCP entity and the first RLC entity add the first SN information to the first data packet. This can be understood as the PDCP entity and the first RLC entity adding one or more SN information entries to the data packet header of the first data packet. The header of the first data packet can be equivalently replaced with the data packet header of the first data packet.

[0219] As can be seen, in the method provided in this application embodiment, the PDCP entity and RLC entity at the sending / receiving end can share the SN information of the data packet. When operating on the data packet, only one SN information needs to be added, or only one SN information needs to be added. In this way, the amount of data packet header information can be reduced, and the processing latency can be lowered.

[0220] In some embodiments, the sending end and / or receiving end may receive third information, which is used to indicate any of the following:

[0221] The PDCP entity and the first RLC entity share the SN information corresponding to the data packet;

[0222] The packets of the PDCP entity and the first RLC entity use the same SN information;

[0223] The PDCP entity and the first RLC entity support adding SN information once, or adding one SN information to the packet.

[0224] It should be noted that the sending and / or receiving end can receive third-party information sent by the network. The network can use this third-party information to instruct the PDCP entity and RLC entity to share the SN information corresponding to the data packet, or to instruct the PDCP entity and RLC entity to use the same SN information for their data packets, or to instruct the PDCP entity and RLC entity to add the SN information to the data packet only once, or to add only one SN information. This reduces the amount of data packet header information and lowers processing latency.

[0225] It should be noted that the third information can be included / carried in RRC signaling. For example, the third information can be carried through RRCReconfiguration, RRCResume, or RRCSetup, and this application embodiment does not limit this.

[0226] It should also be noted that the third information indicates the sending or receiving end, or indicates one or more data radio bearers (DRBs) of the sending or receiving end.

[0227] In one example, the third information indicates to either the sender or the receiver, and in this case, the third information may occupy 1 bit in the RRC signaling.

[0228] When the bit information is mapped to the first value (e.g., 0, 1, true, or false), the above function is enabled, that is, it instructs the PDCP entity and the RLC entity to share the SN information corresponding to the data packet, or instructs the PDCP entity and the RLC entity to use the same SN information for the data packets, or instructs the PDCP entity and the RLC entity to add SN information to the data packet only once, or to add one SN information.

[0229] When the bit information is mapped to the second value (1, 0, false or true), or when the bit information is defaulted, the above function is disabled. That is, it indicates that the PDCP entity and the RLC entity do not share the SN information corresponding to the data packet, or it indicates that the data packets of the PDCP entity and the RLC entity do not use the same SN information, or it indicates that the PDCP entity and the RLC entity do not support adding SN information to the data packet once, or adding SN information.

[0230] In one example, the third information, indicating one or more DRBs, can be presented as a bitmap for each DRB. The third information can consist of N bits, where N is the total number of DRBs. Each of the N bits corresponds to one DRB.

[0231] When the bit mapping corresponding to a DRB is the first value (e.g., 0 or 1), it indicates that the PDCP entity and RLC entity associated with that DRB share the SN information corresponding to the data packet, or use the same SN information, or add SN information to the data packet only once or add one SN information.

[0232] When the bit mapping corresponding to a DRB is a second value (e.g., 1 or 0), it indicates that the PDCP entity and RLC entity associated with that DRB do not share the SN information corresponding to the data packet, or do not use the same SN information, or do not support adding SN information to the data packet only once or adding one SN information.

[0233] The data packet processing process will be explained in detail from the perspectives of both the sending and receiving ends.

[0234] It should be noted that, in the embodiments of this application, the transmitting or receiving PDCP entity can be understood as a functional module in the transmitting or receiving end used to implement PDCP-related operations. Therefore, the execution of operations by the transmitting or receiving PDCP entity can be understood as the transmitting or receiving end performing operations through the functional module used to implement PDCP-related operations. In the embodiments of this application, the execution of operations by the transmitting or receiving PDCP entity can also be referred to as the transmitting or receiving end performing operations through the PDCP entity; the two are equivalent or interchangeable.

[0235] Correspondingly, in the embodiments of this application, the transmitting or receiving RLC entity can be understood as a functional module in the transmitting or receiving end used to implement RLC-related operations. Therefore, the execution of operations by the transmitting or receiving RLC entity can be understood as the transmitting or receiving end performing operations through the functional module used to implement PDCP-related operations. In the embodiments of this application, the execution of operations by the transmitting or receiving RLC entity can also be referred to as the transmitting or receiving end performing operations through the RLC entity; the two are equivalent or interchangeable.

[0236] The following describes the relevant operations of the sending PDCP entity.

[0237] It should be understood that the sending PDCP entity can receive the first data packet from the higher layer, add a PDCP PDU header to the first data packet, and / or deliver the first data packet with the added PDCP PDU header to the sending RLC entity.

[0238] It should be noted that during the PDCP entity processing at the sending end, the first data packet can be either a PDCP SDU or a PDCP PDU.

[0239] In some embodiments, the sending PDCP entity can determine or obtain the first SN information corresponding to the first data packet.

[0240] In one implementation, the sending PDCP entity can determine the first SN information corresponding to the first data packet.

[0241] It should be noted that the sending end PDCP entity determines the first SN information corresponding to the first data packet, which can be understood as the sending end PDCP entity assigning the corresponding first SN information to the first data packet.

[0242] Understandably, after the sending PDCP entity assigns the corresponding first SN information to the first data packet, it can send the first SN information corresponding to the first data packet to the first RLC entity. In this way, the first RLC entity can share the first SN information corresponding to the first data packet for subsequent processing and will not assign other SN information to the first data packet.

[0243] In another implementation, the sending PDCP entity can obtain the first SN information corresponding to the first data packet.

[0244] It should be noted that the sending end PDCP entity obtaining the first SN information corresponding to the first data packet can be understood as the sending end PDCP entity obtaining the first SN information corresponding to the first data packet from the first RLC entity.

[0245] Understandably, the sending PDCP entity may not assign the corresponding SN information to the first data packet, but instead directly deliver the first data packet with the added header to the first RLC entity, which will then assign the first SN information to the first data packet.

[0246] Correspondingly, after the first RLC entity allocates the first SN information for the first data packet, it can inform the sending PDCP entity of the first SN information corresponding to the first data packet. In this way, the sending PDCP entity can obtain the first SN information corresponding to the first data packet, and thus the sending PDCP entity can share the first SN information allocated by the first RLC entity for the first data packet.

[0247] It should be noted that the sending PDCP entity can correspond to one or more RLC entities. After determining the first SN information corresponding to the first data packet, the sending PDCP entity can send the first SN information corresponding to the first data packet to the RLC entity associated with the first SN information (referred to as the first RLC entity in this embodiment of the application).

[0248] Understandably, the first RLC entity can be associated with the first SN information.

[0249] It should be noted that the first RLC entity satisfies one or more of the following:

[0250] The first RLC entity is the main RLC entity among the plurality of RLC entities;

[0251] The first RLC entity is the RLC entity that activates PDCP replication transmission;

[0252] The first RLC entity is the secondary split RLC entity that activates PDCP;

[0253] The first RLC entity is the auxiliary RLC entity that activates PDCP;

[0254] The first RLC entity is the RLC entity determined by the transmitting end based on the implementation;

[0255] The first RLC entity is an RLC entity determined based on predefined rules.

[0256] In some embodiments, the sending end PDCP entity corresponds to multiple RLC entities, and the method provided in this application embodiment may further include:

[0257] The sending end sends fourth information to multiple RLC entities through the PDCP entity. The fourth information is used to at least indicate the SN information associated with the corresponding RLC entity.

[0258] Understandably, when a PDCP entity corresponds to multiple RLC entities, and split transmission is required, the sending PDCP entity can use the fourth information to inform each RLC entity of the associated SN information. The data packets corresponding to each SN are then transmitted through the RLC entity associated with that SN. In other words, the PDCP entity can use the fourth information to inform the lower-level RLC entities which SN information corresponds to which data packets are transmitted through which RLC entities.

[0259] In some embodiments, after determining the first SN information corresponding to the first data packet, the sending PDCP entity may not add the first SN information to the header of the first data packet, but instead directly send the first data packet and the first SN information corresponding to the first data packet to the first RLC entity, and the first RLC entity will add the first SN information to the header of the first data packet.

[0260] In some embodiments, after determining the first SN information corresponding to the first data packet, the sending end PDCP entity may also add the first SN information to the header of the first data packet. Correspondingly, the first RLC entity used by the sending end to transmit the first data packet will no longer add any other SN information to the first data packet.

[0261] In this way, the sending PDCP entity and RLC entity can share the SN information of the data packet, adding only one or two SN information entries to the packet header, thus reducing processing latency.

[0262] In one example, if the first RLC entity is operating in UM mode and the first RLC entity does not support / does not have / is not configured / activated one or more of the following functions: data segmentation, split bearer, data copy transmission, duplicate packet detection, the sending PDCP entity may do the following: not send the first SN information to the first RLC entity, and / or add the first SN information to the header of the first data packet.

[0263] In one example, if the first RLC entity is operating in UM mode and the first RLC entity does not support / does not have / is not configured / activated one or more of the following functions: data segmentation, split bearer, data copy transmission, duplicate packet detection, if the first data packet needs to be or is configured to be delivered in order, the sending PDCP entity performs the following operations: sends the first SN information to the first RLC entity, and / or adds the first SN information to the header of the first data packet.

[0264] In some embodiments, a PDCP entity corresponds to multiple RLC entities, and the method provided in this application further includes:

[0265] The sending PDCP entity sends first status information to the receiving PDCP entity. The first status information is used by the receiving PDCP entity to determine the relationship between the RLC entity and the SN information, and / or to perform data reassembly, and / or to indicate any of the following:

[0266] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0267] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0268] Understandably, a PDCP entity corresponds to multiple RLC entities. When split transmission is required, the sending PDCP entity can generate and / or send first status information. This first status information indicates to the receiving PDCP the relationship between the RLC entities and the SN information. In other words, the first status information indicates which RLC entity should transmit the data corresponding to the SN information. After receiving the first status information, the receiving PDCP entity determines the relationship between the RLC entities and the SN information based on the first status information, and / or, the receiving PDCP entity can perform data reassembly based on this relationship.

[0269] In some embodiments, the first status information may be the PDCP status PDU.

[0270] In some embodiments, the first status information may be sent based on periodic transmission or event triggering.

[0271] In one implementation, the sending PDCP entity can send first status information to the receiving PDCP entity based on a period or a periodic timer.

[0272] It should be noted that the period or periodic timer can be predefined or network-configured, and this application embodiment does not impose any restrictions on it.

[0273] In another implementation, the first status information is sent based on an event-driven mechanism, where the event may include one or more of the following:

[0274] There is a gap between the SN information of data packets received by multiple RLC entities;

[0275] There are gaps between the SN information of the data packets received by the first RLC entity;

[0276] N RLC PDUs were sent; N is an integer greater than or equal to 1;

[0277] The first RLC PDU was sent;

[0278] The size of the transmitted RLC PDU is the first data amount or an RLC PDU that has transmitted the first data amount;

[0279] No third status information was received from the receiving end;

[0280] The duration during which no third status information is received from the receiving end is the fourth duration.

[0281] It should be noted that there are intervals between SN information, which can be understood as the SN information being discontinuous or discrete.

[0282] It should be noted that the unit of the first data volume can be a byte or a bit, and this application embodiment does not limit this.

[0283] It should be noted that the third status information can be sent by the receiving end, and the third information can indicate the reception status or transmission status of the data packets sent by the sending end. For example, the third information can indicate that the reception status of the data packets / data packet segments corresponding to each SN information is confirmed, or indicate that the data packets / data packet segments corresponding to each SN information were successfully transmitted or received. After determining the reception status or transmission status of the data packets sent by the sending end, the receiving end can send the third status information to the sending end in a periodic or event-triggered manner.

[0284] It should be noted that the above events are predefined or network-configured, and this application embodiment does not impose any restrictions on them.

[0285] It should also be noted that one or more of N, the first byte, the first data volume, and the fourth duration in the above events are predefined parameters or configured by the network, and this application embodiment does not impose any restrictions on them.

[0286] In some embodiments, the sending PDCP entity can receive fourth status information; wherein the fourth status information includes the reception status or transmission status of the data packets sent by the sending PDCP. For example, the third information can indicate whether the reception status of the data packets / data packet segments corresponding to each SN information is an acknowledged reception, or indicate whether the data packets / data packet segments corresponding to each SN information have been successfully transmitted or received.

[0287] The above method clarifies the relevant operational behaviors of the sending-end PDCP entity during the process of sharing SN information between the sending-end PDCP entity and the RLC entity.

[0288] The following describes the relevant operations of the sending RLC entity.

[0289] It should be understood that the sending RLC entity can receive the first data packet from the sending PDCP entity, add an RLC PDU header to the first data packet, and / or deliver the first data packet with the added RLC PDU header to the sending MAC entity.

[0290] It should be noted that during the RLC entity processing at the sending end, the first data packet can be either an RLC SDU or an RLC PDU.

[0291] In one embodiment of this application, the method provided in this application embodiment may include the following steps:

[0292] The sending end receives the first data packet sent by the sending end's PDCP entity through the first RLC entity; and / or,

[0293] The sending end determines or obtains the first SN information corresponding to the first data packet through the first RLC entity.

[0294] In one implementation, the first RLC entity at the sending end determines the first SN information corresponding to the first data packet.

[0295] It should be noted that the sending end's first RLC entity determines the first SN information corresponding to the first data packet, which can be understood as the sending end's first RLC entity assigning the corresponding first SN information to the first data packet.

[0296] Understandably, the sending end PDCP does not assign a corresponding SN to the first data packet; instead, the sending end first RLC entity assigns the corresponding first SN information to the first data packet. Optionally, after assigning the corresponding first SN information to the first data packet, the sending end first RLC entity can send the first SN information to the sending end PDCP entity. In this way, the sending end PDCP entity and the sending end first RLC entity can use the same first SN information for the first data packet, achieving SN information sharing.

[0297] In another implementation, the first RLC entity at the sending end obtains the first SN information corresponding to the first data packet.

[0298] It should be noted that the first RLC entity at the sending end obtaining the first SN information corresponding to the first data packet can be understood as the first RLC entity at the sending end obtaining the first SN information corresponding to the first data packet from the PDCP entity at the sending end.

[0299] Understandably, the sending end's first RLC entity does not allocate corresponding SN information for the first data packet. Instead, the sending end's PDCP entity allocates the corresponding first SN information for the first data packet and sends the first SN information to the sending end's first RLC entity. Correspondingly, the first RLC entity can receive the first SN information sent by the sending end's PDCP entity. In this way, the first RLC entity can share the first SN information corresponding to the first data packet for subsequent processing and does not allocate other SN information for the first data packet.

[0300] In some embodiments, the sending end PDCP entity can add the first SN information to the header of the first data packet, so that the sending end first RLC entity can obtain the first SN information corresponding to the first data packet from the header of the first data packet.

[0301] In other embodiments, the sending PDCP entity may not add the first SN information to the header of the first data packet. Instead, the sending PDCP entity may send the first data packet and the corresponding first SN information to the sending first RLC entity. In this way, the sending first RLC entity can obtain the first SN information corresponding to the first data packet.

[0302] It should be noted that if the sending end PDCP entity does not add the first SN information to the header of the first data packet, then the sending end first RLC entity can add the first SN information to the header of the first data packet after determining or obtaining the first SN information corresponding to the first data packet.

[0303] It should also be noted that if the first RLC entity at the sending end supports / has / is configured / activated to perform data segmentation, and if the first RLC entity needs to segment the first data packet, the first RLC entity can add the first SN information to the header of each RLC PDU carrying the segmented data of the first data packet.

[0304] In some embodiments, if the sending end PDCP entity has already added the first SN information to the header of the first data packet, then the sending end first RLC entity can directly use the first SN information corresponding to the first data packet for subsequent operations, such as data segmentation, data retransmission, etc. The sending end first RLC entity will not add any other SN information to the first data packet.

[0305] In some embodiments, if the sending end first RLC entity supports / has / is configured / activated for data segmentation, the sending end first RLC entity may add SI and / or SO to the header of the first data packet.

[0306] Understandably, when the first RLC entity at the sending end performs data segmentation on the data packet, the first RLC entity at the sending end can add SI and / or SO to the header of the segmented data packet (RLC PDU).

[0307] In some embodiments, when the first RLC entity at the sending end supports / has / is configured / activated for data segmentation, first SN information is added to the header of the packet carrying the segmented data corresponding to the first data packet.

[0308] Understandably, when the first RLC entity at the sending end performs data segmentation on the data packet, the first RLC entity at the sending end can add the SN information corresponding to the data packet to the header of the segmented data packet (RLC PDU).

[0309] In some embodiments, where a PDCP entity corresponds to multiple RLC entities, the method provided in this application further includes:

[0310] The sending end sends second status information to the receiving end's first RLC entity through the first RLC entity. The second status information is used by the receiving end's first RLC entity to determine the relationship between the RLC entity and the SN information, and / or by the receiving end's first RLC entity to perform data reassembly, and / or by indicating any of the following:

[0311] The first SN information associated with the first RLC entity;

[0312] The SN information associated with the data packets transmitted by the first RLC entity;

[0313] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0314] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0315] Understandably, a PDCP entity corresponds to multiple RLC entities. When split transmission is required, the sending end's first RLC entity can generate and / or send second status information. This second status information indicates to the receiving end's first RLC entity the relationship between the RLC entity and the SN information. In other words, the second status information indicates which RLC entity should transmit the data corresponding to the SN information. Upon receiving the second status information, the receiving end's first RLC entity determines the relationship between the RLC entity and the SN information based on the second status information, and / or, the receiving end's first RLC entity performs data reassembly based on this relationship.

[0316] It should be noted that when a PDCP entity corresponds to multiple RLC entities, each of the multiple RLC entities can generate and / or send second status information. The second status information generated by each RLC entity may include only the relationship between that RLC entity and the SN information, or it may include the relationships between other RLC entities and the SN information; this application embodiment does not impose any limitations on this.

[0317] In some embodiments, the second status information may be an RLC status PDU.

[0318] In some embodiments, the second status information is sent based on periodic transmission or event triggering.

[0319] In one implementation, the sending end first RLC entity can send second status information to the receiving end first RLC entity based on a period or a periodic timer.

[0320] It should be noted that the period or periodic timer can be predefined or network-configured, and this application embodiment does not impose any restrictions on it.

[0321] In another implementation, the second status information is sent based on an event-driven mechanism, where the event may include one or more of the following:

[0322] There is a gap between the SN information of multiple RLC received data packets;

[0323] There are gaps between the SN information of the data packets received by the first RLC;

[0324] N RLC PDUs were sent; N is an integer greater than or equal to 1;

[0325] The first RLC PDU was sent;

[0326] The size of the transmitted RLC PDU is the first byte or the size of the transmitted RLC PDU containing the first amount of data.

[0327] No third status information was received from the receiving end;

[0328] The duration during which no third status information is received from the receiving end is the fourth duration.

[0329] It should be noted that the description of the second state information can refer to the relevant description of the first state information in the above embodiments, and for the sake of brevity, it will not be repeated here.

[0330] It should also be noted that the first status information and the second status information have similar functions. In practical applications, the sending end can generate or send one of these types of information. For example, if the sending end PDCP entity generates and sends the first status information, the sending end first RLC entity may not generate and send the second status information; conversely, if the sending end first RLC entity generates and sends the second status information, the sending end PDCP entity may not generate and send the first status information to avoid excessive signaling overhead.

[0331] In some embodiments, the following steps are also included:

[0332] The sending end receives the third status information sent by the receiving end's first RLC entity through the first RLC entity; the third status information includes the reception status or transmission status of the data packet sent by the sending end;

[0333] The first RLC entity at the sending end updates the status parameters based on the third status information.

[0334] It should be noted that the third status information can indicate the reception status or transmission status of the data packets sent by the sender. For example, the third information can indicate whether the reception status of the data packets / data packet segments corresponding to each SN information is an acknowledgment of reception, or whether the data packets / data packet segments corresponding to each SN information have been successfully transmitted or received.

[0335] After receiving the third status information, the first RLC entity at the sending end can update the status parameters related to data transmission, such as one or more of RX_Next, RX_Next_Status_Trigger, RX_Highest_Status, and RX_Next_Highest.

[0336] The above method clarifies the relevant operational behaviors of the sending end RLC entity during the process of sharing SN information between the sending end PDCP entity and the RLC entity.

[0337] The following describes the relevant operations of the receiver RLC entity.

[0338] It should be understood that the receiving RLC entity can receive the first data packet from the lower layer, remove the RLC PDU header from the first data packet, and / or send the first data packet with the RLC PDU header removed to the corresponding PDCD entity.

[0339] It should be noted that during the RLC entity processing at the receiving end, the first data packet can be either an RLC SDU or an RLC PDU.

[0340] In some embodiments, the receiving end determines or obtains the first SN information corresponding to the first data packet through the first RLC entity.

[0341] In one implementation, the receiving end's first RLC entity can determine the first SN information corresponding to the first data packet.

[0342] Understandably, the RLC PDU header of the first data packet contains the first SN information corresponding to the first data packet. The receiving end's first RLC entity determines the first SN information corresponding to the first data packet. This can be understood as the receiving end's first RLC entity being able to determine the first SN information based on the RLC PDU header of the first data packet. Simply put, the first RLC entity can determine the first SN information corresponding to the first data packet by disassembling the packet.

[0343] Accordingly, after determining the first SN information corresponding to the first data packet, the first RLC entity at the receiving end can send the first SN information corresponding to the first data packet to the PDCP entity at the receiving end so that the PDCP entity can perform related operations based on the first SN information.

[0344] In another implementation, the receiving end's first RLC entity can obtain the first SN information corresponding to the first data packet.

[0345] Understandably, the first SN information corresponding to the first data packet is added to the PDCP PDU header of the first data packet. The receiving end's first RLC entity obtains the first SN information corresponding to the first data packet, which can be understood as the receiving end's first RLC entity obtaining the first SN information sent by the receiving end's PDCP entity.

[0346] It should be noted that if the sending PDCP entity adds first SN information to the header of the first data packet, the receiving PDCP entity can remove the PDCP PDU header from the first data packet to obtain the first SN information corresponding to the first data packet. Furthermore, the receiving PDCP entity can send the first SN information corresponding to the first data packet to the receiving first RLC entity. In this way, the first RLC entity can obtain the first SN information corresponding to the first data packet and perform relevant operations based on the first SN information.

[0347] In this way, the receiving end PDCP entity and the receiving end RLC entity can share the SN information of the data packet. When the receiving end PDCP entity and the receiving end RLC entity perform related operations on the first data packet, they can use the same SN information.

[0348] In some embodiments, a PDCP entity may correspond to multiple RLC entities. The method provided in this application also includes:

[0349] The receiving end's first RLC entity receives second status information sent by the sending end's first RLC entity; the second status information is used by the receiving end's first RLC entity to determine the relationship between the RLC entity and the SN information, and / or, by the receiving end's first RLC entity to perform data reassembly, and / or, by the second status information to indicate any of the following:

[0350] The first SN information associated with the first RLC entity;

[0351] The SN information associated with the data packets transmitted by the first RLC entity;

[0352] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0353] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0354] It should be noted that the second state information can be referred to the relevant description of the sending end RLC entity in the above embodiments, which will not be repeated here for the sake of brevity.

[0355] In some embodiments, the method provided in this application further includes:

[0356] The first RLC entity at the receiving end performs one or more of the following actions based on the second state information:

[0357] Determine the relationship between RLC entities and SN information.

[0358] Determine the relationship between the data packets transmitted by the RLC entity and the SN information.

[0359] Perform data reorganization.

[0360] Determine the SN information contained in the third status information transmitted by the first RLC at the receiving end;

[0361] Determine the existence of SN information with intervals;

[0362] Send first indication information to the receiving end PDCP entity. The first indication information is used to indicate the SN information associated with at least one or each of the multiple RLC entities, and / or the SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0363] It should be noted that if the receiving end PDCP entity does not receive the first status information, or the PDCP entity is not configured with the first status information, the receiving end RLC entity, after receiving the second status information, may indicate to the PDCP entity the SN information associated with at least one or each of the multiple RLC entities in the second status information, and / or the SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0364] In some embodiments, where a PDCP entity corresponds to multiple RLC entities, the receiving end first RLC entity can receive the first data packet corresponding to the first SN information associated with the first RLC.

[0365] Understandably, when a PDCP entity corresponds to multiple RLC entities, the first RLC entity can determine the SN information associated with it based on the second state information mentioned above. In this way, the first RLC entity can receive the data packets corresponding to that SN information.

[0366] For example, the first RLC entity is associated with the first SN information, therefore, the first RLC entity can receive the first data packet corresponding to the first SN information.

[0367] In some embodiments, the method provided in this application further includes:

[0368] The receiving end sends third status information to the sending end's first RLC entity through the first RLC entity; the third status information includes the reception status or transmission status of the data packet sent by the sending end's first RLC entity.

[0369] It should be noted that when a PDCP entity corresponds to multiple RLC entities, each RLC entity at the receiving end can generate its own third state information and send the generated third state information to the sending end RLC entity corresponding to the receiving end RLC entity.

[0370] In one implementation, the receiving end determines or considers that the data packet corresponding to the SN information not associated with the first RLC has been received, or does not need to be received, or is maintained by other RLC entities, or does not need to be included in the third status information of the RLC entity.

[0371] In other words, each RLC entity may only indicate the reception or transmission status of data packets transmitted through its own RLC entity. The reception or transmission status of data packets corresponding to SN information not associated with this RLC entity may not be indicated.

[0372] In another implementation, the reception status corresponding to the SN information that is not associated with the first RLC in the third status information is confirmed reception, or the third status information indicates that the data packet / data packet segmentation corresponding to the SN was successfully transmitted or the transmission was received.

[0373] In other words, each RLC entity can carry the reception status or transmission status of all data packets corresponding to the SN information in the third status information. For data packets corresponding to SN information that are not associated with this RLC entity, it can be set to acknowledge receipt or transmission success.

[0374] The above method clarifies the relevant operational behaviors of the receiving RLC entity during the process of the PDCP entity and the RLC entity sharing SN information.

[0375] The following describes the relevant operations of the receiving end PDCP entity.

[0376] It should be understood that the receiving end PDCP entity can receive the first data packet from the receiving end RLC entity, perform decompression, decryption, integrity verification and other processing on the first data packet, and / or deliver the processed first data packet to the higher layer.

[0377] It should be noted that during the PDCP entity processing at the receiving end, the first data packet can be either a PDCP SDU or a PDCP PDU.

[0378] In some embodiments, the receiving end determines or obtains the first SN information corresponding to the first data packet through the PDCP entity.

[0379] In one implementation, the receiving PDCP entity can determine the first SN information corresponding to the first data packet.

[0380] Understandably, the first SN information corresponding to the first data packet is added to the PDCP PDU header of the first data packet. The receiving end PDCP entity determines the first SN information corresponding to the first data packet. This can be understood as the receiving end PDCP entity being able to determine the first SN information based on the PDCP PDU header of the first data packet. Simply put, the PDCP entity can determine the first SN information corresponding to the first data packet by disassembling the packet.

[0381] Accordingly, after determining the first SN information corresponding to the first data packet, the receiving end PDCP entity can send the first SN information corresponding to the first data packet to the receiving end first RLC entity so that the first RLC entity can perform related operations based on the first SN information.

[0382] In another implementation, the receiving PDCP entity can obtain the first SN information corresponding to the first data packet.

[0383] Understandably, the first SN information corresponding to the first data packet is added to the RLC PDU header of the first data packet. The receiving end PDCP entity obtains the first SN information corresponding to the first data packet, which can be understood as the receiving end PDCP entity obtaining the first SN information sent by the receiving end first RLC entity.

[0384] It should be noted that if the sending end's first RLC entity adds first SN information to the header of the first data packet, the receiving end's first RLC entity can remove the RLC PDU header from the first data packet to obtain the first SN information corresponding to the first data packet. Furthermore, the receiving end's first RLC entity can send the first SN information corresponding to the first data packet to the receiving end's PDCP entity. In this way, the PDCP entity can obtain the first SN information corresponding to the first data packet and perform related operations such as decompression, decryption, and integrity verification based on the first SN information.

[0385] In this way, the receiving end PDCP entity and the receiving end RLC entity can share the SN information of the data packet. When the receiving end PDCP entity and the receiving end RLC entity perform related operations on the first data packet, they can use the same SN information.

[0386] In some embodiments, a PDCP entity may correspond to multiple RLC entities. The method provided in this application also includes:

[0387] The receiving PDCP entity receives first status information sent by the sending PDCP entity; the first status information is used by the receiving PDCP entity to determine the relationship between the RLC entity and the SN information, and / or to perform data reassembly, and / or to indicate any of the following:

[0388] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0389] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0390] It should be noted that the first state information can be referred to the relevant description of the sending end PDCP entity in the above embodiments, which will not be repeated here for the sake of brevity.

[0391] In some embodiments, the method provided in this application further includes:

[0392] The receiving PDCP entity performs at least one of the following actions based on the first state information:

[0393] Determine the relationship between the RLC entity and the SN information.

[0394] Determine the relationship between the data packets transmitted by the RLC entity and the SN.

[0395] Perform data reorganization.

[0396] Determine the SN information contained in the fourth status information sent by the PDCP entity at the receiving end;

[0397] Determine the existence of SN information with intervals;

[0398] Send a second indication information to the receiving RLC entity, the second indication information being used to indicate the SN information associated with at least one or each of the plurality of RLC entities, and / or the SN information corresponding to the data packets transmitted by at least one or each of the plurality of RLC entities.

[0399] It should be noted that if the first RLC entity at the receiving end does not receive the second status information, or if the RLC entity is not configured with the second status information, the PDCP entity at the receiving end, after receiving the first status information, may indicate to the first RLC entity the SN information associated with at least one or each of the multiple RLC entities in the first status information, and / or the SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0400] In some embodiments, the method provided in this application further includes:

[0401] The receiving PDCP entity sends fourth status information to the sending PDCP entity, which includes the reception status or transmission status of the data packets sent by the sending PDCP.

[0402] It should be noted that when a PDCP entity corresponds to multiple RLC entities, the receiving PDCP entity can generate fourth state information and send the generated fourth state information to the receiving PDCP entity.

[0403] The above methods clarify the relevant operational behaviors of the receiving PDCP entity during the process of the PDCP entity and the RLC entity sharing SN information.

[0404] The communication method provided in the embodiments of this application will be described in detail below with reference to specific application scenarios.

[0405] Example 1: Remove the RLC entity and move the existing RLC entity functions to the PDCP entity. The PDCP entity includes ARQ, segmentation, and re-assembly functions. In this way, the RLC entity functions are implemented in the PDCP entity, simplifying the protocol stack.

[0406] In Implementation 1, the RLC entity is removed and the existing RLC functions are moved to the PDCP entity. For example, the PDCP entity can perform one or more of the following operations: ARQ, Segmentation, and re-assembly.

[0407] PDCP includes one or more of the following:

[0408] Define AM and UM modes for PDCP entities, or use an ARQ-like data retransmission mechanism in PDCP entities.

[0409] Define a reassembly-like retx in PDCP for the reassembly functionality;

[0410] Data segmentation occurs after compression, or after encryption, or after integrity verification.

[0411] The PDCP header contains SI and / or SO information for the segmented SDU.

[0412] The above functions are described below.

[0413] (1) Configure the PDCP entity in the network to implement the functions related to the RLC entity.

[0414] Specifically, the receiving end can receive RRC configuration information, which can be used to construct a PDCP entity. The RRC configuration information may include at least one of the following parameters: ARQ, segmentation, or re-assembly.

[0415] For example, for the sending end, the RRC configuration information may include at least one of the following parameters: t-PollRetransmit, pollPDU, pollByte, maxRetxThreshold.

[0416] For example, for the receiving end, the RRC configuration information may include at least one of the following parameters: t-Reassembly, t-StatusProhibit.

[0417] Optionally, the RRC configuration information can also configure PDCP in a specific mode, such as configuring AM PDCP (PDCP with ARQ) and UM PDCP (PDCP without ARQ).

[0418] (2) Clarify the position of ARQ, segmentation, and re-assembly functions in the PDCP entity functional modules when configuring ARQ, segmentation, and re-assembly functions in the PDCP entity.

[0419] For the sending end, if PDCP supports / has / is configured / activated for segmentation, then segmentation is located after compression, or after ciphering, or after integrity.

[0420] For the receiving end, if PDCP supports / has / is configured / activated to perform re-assembly, then re-assembly occurs before decompression, or before deciphering, or before integrity.

[0421] Additionally, if PDCP supports / has / is configured / activated for ARQ, then ARQ occurs either before segmentation, after segmentation, or before header compression.

[0422] (3) The PDCP header carries SI and / or SO information.

[0423] Understandably, if a PDCP entity supports / has / is configured / activated to perform segmentation and re-assembly, it will carry the SI and / or SO in the PDCP PDU header.

[0424] It should be noted that SI and SO can occupy the R bit position in the existing PDCP header, or the information can be carried by adding a new byte. Here, R is an integer greater than or equal to 1.

[0425] (4) Clarify the parameter update mechanism of PDCP entities.

[0426] If the PDCP entity supports / has / is configured / activated with segmentation and re-assembly capabilities, and ARQ is not configured at the same time, the PDCP entity performs a parameter update mechanism similar to RLC UM for both the sender and / or receiver.

[0427] If the PDCP entity supports / has / is configured / activated for segmentation and re-assembly, and if it also supports / has / is configured / activated for ARQ, then the PDCP entity performs a parameter update mechanism similar to RLC AM for the sender and / or receiver.

[0428] (5) Clarify the data transmission function of PDCP.

[0429] The sending PDCP entity can receive retransmission indication information from the receiving PDCP and perform retransmission based on the retransmission execution information.

[0430] For example, a data packet (PDCP SDU / PDU) that is indicated as not received, NACK, or missing by the retransmission indication information is considered to have been transmitted unsuccessfully, and / or a retransmission is performed.

[0431] For example, a data packet (PDCP SDU / PDU) that is indicated as received or ACK by the retransmission indication information is considered to have been successfully transmitted, and / or, no retransmission is performed, and / or, the sending end is discarded.

[0432] Example 2

[0433] In this embodiment, the functions of the PDCP entity and RLC entity remain unchanged, but the SN information is shared between the PDCP entity and the RLC entity. That is, only one SN information is carried in the RLC data PDU, or only the SN information is added once to an RLC data PDU. In this way, the amount of data packet header information can be reduced, simplifying processing time.

[0434] Understandably, PRCP entities and RLC entities share SN information, and not performing function migration can include examples such as the following (Shared SN at RLC and PDCP with no functions migration, e.g.):

[0435] The transmitting PDCP determines the SN information for each PDCP and indicates the SN information to the associated RLC entity.

[0436] The sending RLC entity adds SN, SI, and SO information to the RLC header.

[0437] The receiving RLC entity transmits the SDU and SN information to the PDCP entity, and the receiving PDCP entity uses the SN information for in-order delivery.

[0438] The above functions are described below.

[0439] (1) Configure relevant functions for PDCP entities and RLC entities in the network.

[0440] Optionally, indication information can be carried via RRC signaling to indicate whether the PDCP entity and the RLC entity share SN information, or use only one SN information, or add SN information to the packet header only once.

[0441] Optionally, the indication information may be for the Data Radio Bearer (DRB) or for the UE (including the transmitter or receiver).

[0442] Optionally, the indication information occupies 1 bit, or can be configured as a DRB bitmap.

[0443] Optionally, the indication information is 1 or true, which means the function is enabled; otherwise, the function is disabled.

[0444] Optionally, the instruction information is left blank, which means the function is disabled.

[0445] (2) Define the behavior of the sending PDCP entity.

[0446] The sending PDCP entity receives data packets from a higher layer, adds a PDCP PDU header and / or forwards the deliver PDU to the RLC, and performs at least one of the following actions:

[0447] 1. For each data packet or PDCP SDU / PDU, determine (or assign) SN information.

[0448] 2. For each data packet or PDCP SDU / PDU, deliver the determined SN information to the corresponding RLC entity.

[0449] Optionally, if the RLC entity is a UM RLC and one or more of the segmentation, split, duplication, and duplicate packet detection functions are not configured, then the SN information does not need to be submitted to the RLC entity, and / or the SN information is still added to the PDCP header.

[0450] Optionally, if the RLC entity is a UM RLC and one or more of the segmentation, split, duplication, and duplicate packet detection functions are not configured, but sequential delivery is required, then the SN information needs to be delivered to the RLC entity, and / or the SN information is still added to the PDCP packet header.

[0451] If a PDCP entity corresponds to multiple RLC entities, then the PDCP entity will deliver the SN information to the corresponding RLC entity.

[0452] It should be noted that the corresponding RLC entity is all RLC entities, or one of them (optionally, the RLC entity is determined based on the UE implementation, or determined by specific rules, or is a primary RLC entity, or a secondary RLC entity, or a secondary split RLC entity), or an RLC entity that activates PDCP replication transmission.

[0453] 3. If a PDCP entity corresponds to multiple RLC entities, and for split transmission, the sending PDCP entity can inform the lower-level RLC entity which SN information data packets are transmitted through which RLC entity.

[0454] Optionally, if one PDCP entity corresponds to multiple RLC entities, and for split transmission, the sending PDCP entity can generate and / or send a first PDCP state PDU (i.e., the first state information in the above embodiments) to the receiving PDCP entity. Specifically, this includes at least one of the following:

[0455] a) The first PDCP state PDU is used to indicate the relationship between SN information and delivered RLC entity, or to indicate which SN information passed through which RLC entity. The first PDCP state PDU is also used by the receiving end to perform a reassembly operation.

[0456] b) The first PDCP status PDU is sent in a periodic or event-triggered manner.

[0457] c) If the first PDCP state PDU is triggered periodically, then the duration of the period or periodic transmission timer is predefined or configured by the network.

[0458] d) If the first PDCP state PDU is triggered by an event, the event is either predefined or network-configured. The event can be at least one of the following:

[0459] In an RLC or when an SN gap occurs in that RLC, N RLC PDUs are sent, the first RLC PDU is sent, M bytes of RLC PDUs are sent, and no RLC status report is received from the peer. The duration of the delay in receiving the RLC status report from the peer is A duration.

[0460] (3) Define the behavior of the sending RLC entity.

[0461] The sending RLC entity receives data packets from the sending PDCP entity, adds an RLC PDU header and / or delivers a PDU to the MAC, and performs at least one of the following actions:

[0462] 1) Obtain the SN information corresponding to each RLC SDU / PDU, wherein the SN information corresponding to each RLC SDU / PDU is indicated by the PDCP entity of the sending end.

[0463] 2) Add the SN information corresponding to each RLC SDU / PDU to the packet header of the RLC PDU.

[0464] Optionally, if segmentation exists, add SI and SO to the RLC PDU header.

[0465] Optionally, if segmentation exists, the determined SN information is added to the header of the RLC PDU carrying the SDU segment.

[0466] 3) Deliver the RLC PDU to the corresponding MAC entity.

[0467] 4) Send AM RLC entity and update the status parameters according to the second RLC status PDU sent by the receiver (i.e., the third status information in the above embodiment).

[0468] 5) If one PDCP entity corresponds to multiple RLC entities, and for split transmission, the sending RLC entity can generate and / or send a first RLC status PDU (i.e., the second status information in the above embodiment) to the receiving RLC entity. Specifically, this includes at least one of the following:

[0469] a) The first RLC status PDU is used to indicate the relationship between SN information and the delivered RLC entity, or to indicate which SN information passed through which RLC entity. The first RLC status PDU is used by the receiving end to perform a re-assembly operation.

[0470] b) The first RLC status PDU is sent in a periodic or event-triggered manner;

[0471] c) If the first RLC state PDU is triggered periodically, then the duration of the period or periodic transmission timer is predefined or configured by the network.

[0472] d) If the first RLC status PDU is triggered by an event, the event is predefined or network-configured. The event can be at least one of the following: an RLC or an RLC experiencing an SN gap, N RLC PDUs are sent, the first RLC PDU is sent, an M-byte RLC PDU is sent, no RLC status report is received from the peer, and the duration of the absence of the peer's RLC status report is A duration.

[0473] (4) Clarify the behavior of the receiving RLC entity.

[0474] The receiving RLC entity can receive data packets from the lower layer, remove the RLC PDU header and / or deliver the RLC SDU to the corresponding PDCP entity, and perform at least one of the following actions:

[0475] 1) Determine the SN information corresponding to each RLC SDU / PDU, for example, by unpacking the RLC SDU / PDU to obtain the SN information corresponding to each RLC SDU / PDU.

[0476] 2) Deliver the SN information corresponding to each RLC SDU / PDU to the corresponding receiver PDCP entity.

[0477] Optionally, the receiving RLC entity can deliver SN information simultaneously when delivering SDU.

[0478] 3) If a PDCP entity corresponds to multiple RLC entities, and for split transmission, the receiving RLC entity determines the relationship between the SN information and the delivered RLC entity based on the received first RLC status PDU, and / or performs reassembly.

[0479] Optionally, for data packets corresponding to SN information that do not pass through this RLC entity, it is assumed that the data packet has been received, or that it does not need to be received. Then, the status parameters, such as RX_Next, RX_Next_Status_Trigger, RX_Highest_Status, RX_Next_Highest, etc., are updated.

[0480] Optionally, for data packets corresponding to SN information that do not pass through this RLC entity, it is assumed that the data packet has been received, or that it does not need to be received. Furthermore, the second RLC state PDU (i.e., the third state information in the above embodiment) indicates that the data packet status is ACK.

[0481] (5) Clarify the behavior of the receiving end PDCP.

[0482] The receiving end PDCP entity receives data packets from the receiving end RLC entity, performs decryption and other processing, and / or delivers SDUs to higher layers, and performs at least one of the following actions:

[0483] 1) Obtain the SN information corresponding to each PDCP SDU / PDU. The receiving RLC entity delivers the SN information corresponding to each PDCP SDU / PDU to the PDCP entity.

[0484] 2) If one PDCP entity corresponds to multiple RLC entities, and for split transmission, the receiving PDCP entity determines the relationship between the SN information and the delivered RLC entity based on the received first PDCP state PDU.

[0485] 3) Based on the SN information corresponding to the obtained PDCP SDU / PDU, perform operations such as decryption, integrity authentication, and re-ordering.

[0486] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0487] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0488] Figure 4 is a schematic diagram of the structure of a communication device provided in an embodiment of this application, applied to a transmitting end. As shown in Figure 4, the communication device includes:

[0489] The first processing unit 410 is configured to perform one or more of the following operations on the data sent by the higher layer through the first entity: compression, encryption, integrity protection, packet drop indication, packet drop processing, data segmentation, data retransmission, and routing.

[0490] In some embodiments, the first entity replaces the PDCP entity and the RLC entity; or...

[0491] The first entity is a PDCP entity, and the RLC entity does not exist; or,

[0492] The first entity is an RLC entity, and the PDCP entity does not exist.

[0493] In some embodiments, the communication device further includes a first communication unit configured to receive first information, the first information being used to configure the function of the first entity or the protocol layer corresponding to the first entity, and / or, the first information being used to configure parameters related to one or more of the following functions:

[0494] compression;

[0495] encryption;

[0496] Integrity protection;

[0497] Data segmentation;

[0498] Packet discard instruction;

[0499] Packet disposal;

[0500] Data retransmission;

[0501] routing.

[0502] In some embodiments, the first information is further used to configure the working mode of the first entity;

[0503] The operating modes include at least an unacknowledged mode and an acknowledged mode; in the acknowledged mode, the first entity configures or activates the data retransmission function; in the unacknowledged mode, the first entity does not configure or activate the data retransmission function.

[0504] In some embodiments, the data segmentation operation performed by the first entity on the data is performed after the compression operation; or, after the encryption operation; or, after the integrity protection operation.

[0505] In some embodiments, the first entity performs data retransmission before, after, or before the data segmentation operation.

[0506] In some embodiments, where the first entity supports data segmentation, and / or the first entity is configured or activated to perform data segmentation, the PDU corresponding to the first entity includes SI and / or SO.

[0507] In some embodiments, if the first entity supports data segmentation and / or the first entity is configured or activated to perform data segmentation, and if the first entity is not configured or activated to perform data retransmission, the first processing unit 410 is further configured to perform a parameter update mechanism related to the non-acknowledgment mode.

[0508] or,

[0509] If the first entity supports data segmentation and / or the first entity is configured or activated to perform data segmentation, and if the first entity is configured or activated to perform data retransmission, then the first processing unit 410 is further configured to perform a parameter update mechanism related to a defined mode.

[0510] In some embodiments, the first entity configures or activates the data retransmission function, and the first communication unit is further configured to receive retransmission indication information sent from the receiving end first entity through the first entity; and to perform retransmission through the first entity based on the retransmission indication information.

[0511] In some embodiments, the first entity configures or activates the packet drop indication and / or packet drop processing function, including one or more of the following:

[0512] The first communication unit is further configured to receive first packet drop indication information sent from the receiving end first entity via the first entity;

[0513] The first processing unit 410 is further configured to determine, through a first entity, data packets that are to be discarded or are not needed, based on the first packet drop indication information;

[0514] The first processing unit is further configured to discard via the first entity execution package;

[0515] The first processing unit 410 is further configured to discard the packet via the first entity execution package if the first duration is satisfied.

[0516] The first processing unit 410 is further configured to discard related parameters through the first entity update package;

[0517] The first communication unit is further configured to send a second packet drop indication information to a receiving end first entity through a first entity; the second packet drop indication information is used by the receiving end first entity to perform packet drop.

[0518] Figure 5 is a schematic diagram of the structure of a communication device provided in an embodiment of this application, applied to a receiving end. As shown in Figure 5, the communication device includes:

[0519] The second processing unit 510 is configured to perform one or more of the following operations on the data sent by the lower layer through the first entity: data retransmission request, data reassembly, integrity verification, packet drop indication, packet drop processing, decryption, decompression, and delivery of data packets to the higher layer.

[0520] In some embodiments, the first entity replaces the Packet Data Convergence Protocol (PDCP) entity and the Radio Link Control (RLC) entity; or...

[0521] The first entity is a PDCP entity, and the RLC entity does not exist; or,

[0522] The first entity is an RLC entity, and the PDCP entity does not exist.

[0523] In some embodiments, the communication device further includes a second communication unit configured to receive second information; the second information is used to configure the function of the first entity or the protocol layer corresponding to the first entity, and / or, the second information is used to configure parameters related to one or more of the following functions:

[0524] Decompress;

[0525] Decrypt;

[0526] Integrity verification;

[0527] Data retransmission;

[0528] Packet discard instruction;

[0529] Packet disposal;

[0530] Data restructuring;

[0531] Submit data packets to higher management.

[0532] In some embodiments, the second information is further used to configure the working mode of the first entity;

[0533] The operating modes include at least an unacknowledged mode and an acknowledged mode; in the acknowledged mode, the first entity configures or activates the data retransmission function; in the unacknowledged mode, the first entity does not configure or activate the data retransmission function.

[0534] In some embodiments, the data reconstruction operation performed by the first entity on the data is performed before the decompression operation, or before the decryption operation, or before the integrity verification operation.

[0535] In some embodiments, where the first entity supports data reassembly, and / or the first entity is configured or activated to perform data reassembly, the PDU corresponding to the first entity includes SI and / or SO.

[0536] In some embodiments, if the first entity supports data reassembly and / or the first entity is configured or activated to perform data reassembly, and if the first entity is not configured or activated to perform data retransmission, then the second processing unit 510 is configured to perform a parameter update mechanism related to the non-acknowledgment mode.

[0537] or,

[0538] If the first entity supports data reassembly, or if the first entity is configured or activated to perform data reassembly, then if the first entity is configured or activated to perform data retransmission, the second processing unit 510 is configured to execute a parameter update mechanism related to the determined mode.

[0539] In some embodiments, the first entity configures or activates the data retransmission function, and the second communication unit is configured to send retransmission indication information to the first entity of the sending end through the first entity.

[0540] In some embodiments, configuring or activating the drop indication and / or packet drop processing function by the first entity further includes one or more of the following:

[0541] The second communication unit is further configured to send a first packet drop indication message to the sending end first entity through the first entity;

[0542] The second communication unit is further configured to send a first packet drop indication to the first entity at the sending end when a second duration is met; wherein the first packet drop indication is used by the first entity at the sending end to determine lost or unwanted data packets, and / or to perform packet drop.

[0543] The second communication unit is further configured to receive a second packet drop indication message sent from the first entity at the sending end;

[0544] The second processing unit 510 is further configured to determine, through the first entity, data packets that are to be discarded or are not needed based on the second packet drop indication information;

[0545] The second processing unit 510 is further configured to discard via the first entity execution package;

[0546] The second processing unit 510 is further configured to discard the execution packet via the first entity if the third duration is satisfied;

[0547] The second processing unit 510 is further configured to update the packet dropping processing related parameters through the first entity.

[0548] Figure 6 is a schematic diagram of the structure of a communication device provided in an embodiment of this application, applied to a transmitting end. As shown in Figure 6, the communication device includes:

[0549] The third communication unit 610 is configured to send a first data packet, wherein the PDCP entity and the first RLC entity of the first communication unit use the same first SN information when operating on the first data packet.

[0550] In some embodiments, the third communication unit 610 is further configured to receive third information, the third information being used to indicate any one of the following:

[0551] The PDCP entity and the first RLC entity share the SN information corresponding to the data packet;

[0552] The data packets of the PDCP entity and the first RLC entity use the same SN information;

[0553] Does the PDCP entity and the first RLC entity support adding SN information once to the data packet, or adding one SN information?

[0554] In some embodiments, the third information indicates the transmitting end, or indicates one or more data radio bearers of the transmitting end.

[0555] In some embodiments, the communication device further includes a third processing unit configured to determine or obtain the first SN information corresponding to the first data packet through a PDCP entity.

[0556] In some embodiments, the third processing unit is further configured to send the first SN information to the first RLC entity through the PDCP entity.

[0557] In some embodiments, the PDCP entity corresponds to multiple RLC entities, the multiple RLC entities include the first RLC entity, and the first RLC entity is associated with the first SN information.

[0558] In some embodiments, any one of the following is included:

[0559] The first RLC entity is the main RLC entity among the plurality of RLC entities;

[0560] The first RLC entity is the RLC entity that activates PDCP replication transmission;

[0561] The first RLC entity is a secondary split RLC entity that activates PDCP;

[0562] The first RLC entity is a secondary RLC entity that activates PDCP;

[0563] The first RLC entity is the RLC entity determined by the sending end based on the implementation;

[0564] The first RLC entity is an RLC entity determined based on predefined rules.

[0565] In some embodiments, the PDCP entity corresponds to multiple RLC entities, and the third processing unit is further configured to send fourth information to the multiple RLC entities through the PDCP entity, wherein the fourth information is used to at least indicate the SN information associated with the corresponding RLC entity;

[0566] The plurality of RLC entities include a first RLC entity, which is associated with the first SN information.

[0567] In some embodiments, the third processing unit is further configured to add the first SN information to the header of the first data packet through the PDCP entity.

[0568] In some embodiments, the third processing unit is further configured to not send the first SN information to the first RLC entity when the first RLC entity is operating in unacknowledged mode and the first RLC entity has not configured or activated one or more of the functions of data segmentation, split bearer, data copy transmission, and duplicate packet detection, and / or to add the first SN information to the header of the first data packet through the PDCP entity.

[0569] In some embodiments, the third processing unit is further configured to, when the first RLC entity is operating in unacknowledged mode and the first RLC entity has not configured or activated one or more of the functions of data segmentation, split bearer, data copy transmission, and duplicate packet detection, send the first SN information to the first RLC entity through the PDCP entity if the first data packet needs to be delivered in order, and / or add the first SN information to the header of the first data packet through the PDCP entity.

[0570] In some embodiments, the PDCP entity corresponds to multiple RLC entities, and further includes:

[0571] The third communication unit 610 is configured to send first status information to the receiving end PDCP entity. The first status information is used by the receiving end PDCP entity to determine the relationship between the RLC entity and the SN information, and / or to perform data reassembly, and / or to indicate any of the following:

[0572] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0573] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0574] In some embodiments, the first status information is sent based on periodic transmission or event triggering.

[0575] In some embodiments, the third processing unit is further configured to receive the first data packet sent by the PDCP entity through the first RLC entity; and / or to determine or obtain the first SN information corresponding to the first data packet through the first RLC entity.

[0576] In some embodiments, the third processing unit is further configured to receive the first SN information corresponding to the first data packet sent by the sending end PDCP entity through the first RLC entity.

[0577] In some embodiments, the third processing unit is further configured to add the first SN information to the header of the first data packet through the first RLC entity.

[0578] In some embodiments, when the first RLC entity is configured / activated to perform data segmentation, the third processing unit is further configured to add SI and / or SO to the header of the first data packet by the first RLC entity.

[0579] In some embodiments, when the first RLC entity is configured / activated to perform data segmentation, the third processing unit is further configured to add the first SN information to the header of the packet carrying the segmented data corresponding to the first data packet.

[0580] In some embodiments, the PDCP entity corresponds to multiple RLC entities, and the RLC entity includes the first RLC entity; the third communication unit 610 is further configured to send second status information to the receiving end first RLC entity through the first RLC entity, the second status information being used by the receiving end first RLC entity to determine the relationship between the RLC entity and SN information, and / or, the receiving end first RLC entity to perform data reassembly, and / or, the second status information being used to indicate any one of the following:

[0581] The first SN information associated with the first RLC entity;

[0582] The SN information associated with the data packets transmitted by the first RLC entity;

[0583] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0584] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0585] In some embodiments, the second status information is sent based on periodic transmission or event triggering.

[0586] In some embodiments, the event includes one or more of the following:

[0587] There are intervals between the SN information of the data packets received by the multiple RLC entities;

[0588] There are gaps between the SN information of the data packets received by the first RLC entity;

[0589] N RLC PDUs were sent;

[0590] The first RLC PDU was sent;

[0591] The size of the transmitted RLC PDU is the first data amount or an RLC PDU that has transmitted the first data amount;

[0592] No third status information was received from the receiving end;

[0593] The duration during which no third status information is received from the receiving end is the fourth duration.

[0594] In some embodiments, the third communication unit 610 is further configured to receive third status information sent by the first RLC entity of the receiving end through the first RLC entity; the third status information includes the reception status or transmission status of the data packet sent by the sending end; the third processing unit is further configured to update the status parameters based on the third status information.

[0595] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application, applied to a receiving end. As shown in Figure 7, the communication device includes:

[0596] The fourth communication unit 710 is configured to receive a first data packet, wherein the PDCP entity and the first RLC entity of the second communication unit use the same first SN information when operating on the first data packet.

[0597] In some embodiments, the fourth communication unit 710 is further configured to receive third information, the third information being used to indicate any one of the following:

[0598] The PDCP entity and the first RLC entity share the SN information corresponding to the data packet;

[0599] The data packets of the PDCP entity and the first RLC entity use the same SN information;

[0600] Does the PDCP entity and the first RLC entity support adding SN information once to the data packet, or adding one SN information?

[0601] In some embodiments, the third information indicates the receiving end, or indicates one or more data radio bearers of the receiving end.

[0602] In some embodiments, the communication device further includes a fourth processing unit configured to determine or obtain the first SN information corresponding to the first data packet through the first RLC entity.

[0603] In some embodiments, the fourth processing unit is further configured to receive first SN information sent by the receiving end PDCP entity through the first RLC entity.

[0604] In some embodiments, the fourth processing unit is further configured to send the first SN information to the receiving end PDCP entity through the first RLC entity.

[0605] In some embodiments, the PDCP entity corresponds to multiple RLC entities, the multiple RLC entities including the first RLC entity; the fourth communication unit 710 is further configured to receive second status information sent by the first RLC entity of the transmitting end through the first RLC entity; the second status information is used by the first RLC entity of the receiving end to determine the relationship between the RLC entity and the SN information, and / or, the first RLC entity of the receiving end to perform data reassembly, and / or, the second status information is used to indicate any one of the following:

[0606] The first SN information associated with the first RLC entity;

[0607] The SN information associated with the data packets transmitted by the first RLC entity;

[0608] SN information associated with each RLC entity in multiple RLC entities;

[0609] The SN information corresponding to the data packets transmitted by each of the multiple RLC entities.

[0610] In some embodiments, the fourth processing unit is further configured to perform at least one of the following actions:

[0611] Determine the relationship between the RLC entity and the SN.

[0612] Determine the relationship between the data packets transmitted by the RLC entity and the SN.

[0613] Perform data reorganization.

[0614] Determine the SN information contained in the third status information transmitted by the first RLC at the receiving end;

[0615] Determine the existence of SN information with intervals;

[0616] Send first indication information to the receiving end PDCP entity. The first indication information is used to indicate the SN information associated with at least one or each of the multiple RLC entities, and / or the SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0617] In some embodiments, the fourth communication unit 710 is further configured to receive a first data packet corresponding to the first SN information associated with the first RLC through the first RLC entity.

[0618] In some embodiments, the fourth communication unit 710 is further configured to send third status information to the sending end first RLC entity through the first RLC entity; the third status information includes the reception status or transmission status of the data packet sent by the sending end first RLC entity.

[0619] In some embodiments, the fourth processing unit is further configured to determine or consider that the data packet corresponding to the SN information not associated with the first RLC has been received, or does not need to be received, or is maintained by other RLC entities, or does not need to be included in the third status information of the RLC entity.

[0620] The reception status corresponding to the SN information that is not associated with the first RLC in the third status information is confirmed reception, or the data packet / data packet segmentation corresponding to the SN is successfully transmitted or received in the third status information.

[0621] In some embodiments, the fourth processing unit is further configured to determine or obtain the first SN information corresponding to the first data packet through the PDCP entity.

[0622] In some embodiments, the fourth processing unit is further configured to receive the first SN information sent by the first RLC entity of the receiving end via the PDCP entity.

[0623] In some embodiments, the PDCP entity corresponds to multiple RLC entities, and the fourth communication unit 710 is further configured to receive first status information sent by the transmitting PDCP entity through the PDCP entity; the first status information is used by the receiving PDCP entity to determine the relationship between the RLC entity and the SN information, and / or to perform data reassembly, and / or the first status information is used to indicate any of the following:

[0624] SN information associated with at least one or every RLC entity among multiple RLC entities;

[0625] The SN information corresponding to the data packets transmitted by at least one or each of the multiple RLC entities.

[0626] In some embodiments, the fourth processing unit is further configured to perform at least one of the following actions via the PDCP entity based on the first state information:

[0627] Determine the relationship between the RLC entity and the SN information.

[0628] Determine the relationship between the data packets transmitted by the RLC entity and the SN.

[0629] Perform data reorganization.

[0630] Determine the SN information contained in the fourth status information sent by the PDCP entity at the receiving end;

[0631] Determine the existence of SN information with intervals;

[0632] Send a second indication information to the receiving RLC entity, the second indication information being used to indicate the SN information associated with at least one or each of the plurality of RLC entities, and / or the SN information corresponding to the data packets transmitted by at least one or each of the plurality of RLC entities.

[0633] In some embodiments, the fourth communication unit 710 is further configured to send fourth status information to the sending PDCP entity via the PDCP entity, the fourth status information including the reception status or transmission status of the data packet sent by the sending PDCP.

[0634] Those skilled in the art should understand that the description of the communication device in the embodiments of this application can be understood with reference to the description of the communication method in the embodiments of this application.

[0635] Figure 8 is a schematic structural diagram of a communication device 800 provided in an embodiment of this application. This communication device can be a transmitting end or a receiving end as described in the above embodiments. The communication device 800 shown in Figure 8 includes a processor 810, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0636] Optionally, as shown in FIG8, the communication device 800 may further include a memory 820. The processor 810 may retrieve and run computer programs from the memory 820 to implement the methods described in the embodiments of this application.

[0637] The memory 820 can be a separate device independent of the processor 810, or it can be integrated into the processor 810.

[0638] Optionally, as shown in FIG8, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

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

[0640] Optionally, the communication device 800 may specifically be the sending end in the embodiments of this application, and the communication device 800 may implement the corresponding processes implemented by the sending end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0641] Optionally, the communication device 800 may specifically be the receiving end in the embodiments of this application, and the communication device 1800 may implement the corresponding processes implemented by the receiving end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0642] Figure 9 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 900 shown in Figure 9 includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0643] Optionally, as shown in FIG9, chip 1900 may further include memory 920. Processor 910 can retrieve and run computer programs from memory 920 to implement the methods in the embodiments of this application.

[0644] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0645] Optionally, the chip 900 may also include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0646] Optionally, the chip 900 may also include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0647] Optionally, the chip can be applied to the transmitting end in the embodiments of this application, and the chip can implement the corresponding processes implemented by the transmitting end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0648] Optionally, the chip can be applied to the receiving end in the embodiments of this application, and the chip can implement the corresponding processes implemented by the receiving end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0649] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0650] This application also provides a computer storage medium that stores one or more programs, which can be executed by one or more processors to implement the methods in this application.

[0651] Figure 10 is a schematic block diagram of a communication system 1000 provided in an embodiment of this application. As shown in Figure 10, the communication system 1000 includes a transmitter 1010 and a network device 1020.

[0652] The transmitting end 1010 can be used to implement the corresponding functions implemented by the transmitting end in the above method, and the network device 1020 can be used to implement the corresponding functions implemented by the receiving end in the above method. For the sake of brevity, these will not be described in detail here.

[0653] It should be understood that the processor in the embodiments of this application may 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 application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0654] 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 DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (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.

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

[0656] This application also provides a computer-readable storage medium for storing computer programs.

[0657] Optionally, the computer-readable storage medium can be applied to the sending end in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the sending end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0658] Optionally, the computer-readable storage medium can be applied to the receiving end in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the receiving end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0659] This application also provides a computer program product, including computer program instructions.

[0660] Optionally, the computer program product can be applied to the sending end in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the sending end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0661] Optionally, the computer program product can be applied to the receiving end in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the receiving end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0662] This application also provides a computer program.

[0663] Optionally, the computer program can be applied to the sending end in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the sending end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0664] Optionally, the computer program can be applied to the receiving end in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the receiving end in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

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

[0666] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0667] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0669] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0670] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0671] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of communication, the method comprising: performing, by a transmitting end, one or more of the following on data sent by a higher layer via a first entity: compression, ciphering, integrity protection, packet discard indication, packet discard handling, data segmentation, data retransmission, routing. 2.The method of claim 1, wherein, the first entity replaces a packet data convergence protocol (PDCP) entity and a radio link control (RLC) entity; or, the first entity is a PDCP entity, and an RLC entity is absent; or, the first entity is an RLC entity, and a PDCP entity is absent. 3.The method of claim 1 or 2, wherein, the transmitting end receives first information, the first information being used to configure a function of the first entity or a protocol layer corresponding to the first entity, and / or, the first information being used to configure a parameter related to one or more of the following functions: compression; ciphering; integrity protection; data segmentation; packet discard indication; packet discard handling; data retransmission; routing. 4.The method of claim 3, the first information is further used to configure a working mode of the first entity; the working mode comprises at least an unacknowledged mode and an acknowledged mode; the first entity configures or activates the data retransmission function in the acknowledged mode; the first entity does not configure or activate the data retransmission function in the unacknowledged mode. 5.The method of any one of claims 1 to 4, wherein, the first entity performs the data segmentation on the data after performing the compression; or, after performing the ciphering, or, after performing the integrity protection. 6.The method of any one of claims 1 to 5, wherein, the first entity performs the data retransmission on the data before performing the data segmentation, or, after performing the data segmentation, or, before performing the compression. 7.The method of any one of claims 1 to 6, wherein, in a case that the first entity supports data segmentation, and / or, the first entity is configured or activated with the data segmentation function, the protocol data unit (PDU) corresponding to the first entity includes segment indication information (SI) and / or segment offset information (SO). 8.The method of any one of claims 1 to 7, wherein, in a case that the first entity supports data segmentation, and / or, the first entity is configured or activated with the data segmentation function, if the first entity is not configured or activated with the data retransmission function, the transmitting end performs an unacknowledged mode related parameter update mechanism; or, in a case that the first entity supports data segmentation, and / or, the first entity is configured or activated with the data segmentation function, if the first entity is configured or activated with the data retransmission function, the transmitting end performs an acknowledged mode related parameter update mechanism. the first entity is configured or activated with the data retransmission function, the method further comprising:

9. The method according to any one of claims 1 to 8, wherein, the first entity of the transmitting end receives a retransmission indication information sent by the first entity of the receiving end; the first entity of the transmitting end performs the retransmission based on the retransmission indication information. ​ 10. The method according to any one of claims 1 to 9, wherein, The first entity of the sending end configures or activates the packet discard indication and / or packet discard processing function, including one or more of the following: The first entity of the sending end receives the first packet discard indication information sent by the first entity of the receiving end; The first entity of the sending end determines to discard or not to discard the data packet based on the first packet discard indication information; The first entity of the sending end performs packet discard; The first entity of the sending end performs packet discard when a first time length is met; The first entity of the sending end updates packet discard processing related parameters; The first entity of the sending end sends second packet discard indication information to the first entity of the receiving end; The second packet discard indication information is used by the first entity of the receiving end to perform packet discard.

11. A communication method, the method comprising: The receiving end performs one or more of the following operations on the data sent by the first entity of the lower layer: data retransmission request, data recombination, integrity verification, packet discard indication, packet discard processing, decryption, decompression, and submission of data packets to the upper layer.

12. The method of claim 11, wherein: The first entity replaces the packet data convergence protocol (PDCP) entity and the radio link control (RLC) entity; or The first entity is a PDCP entity, and the RLC entity does not exist; or The first entity is an RLC entity, and the PDCP entity does not exist.

13. The method of any one of claims 11 to 12, wherein, Further comprising: The receiving end receives second information; The second information is used to configure the function of the first entity or the protocol layer corresponding to the first entity, and / or the second information is used to configure parameters related to one or more of the following functions: Decompression; Decryption; Integrity verification; Data retransmission; Packet discard indication; Packet discard processing; Data recombination; Submission of data packets to the upper layer.

14. The method of any one of claims 11 to 13, wherein the second information is further used to configure the working mode of the first entity; The working mode at least includes unacknowledged mode and acknowledged mode; the first entity configures or activates the data retransmission function in the acknowledged mode; and the first entity does not configure or activate the data retransmission function in the unacknowledged mode.

15. The method of any one of claims 11 to 14, wherein: The data recombination operation of the first entity on the data is located before the decompression operation, or before the decryption operation, or before the integrity verification operation.

16. The method of any one of claims 11 to 15, wherein: In the case that the first entity supports data recombination and / or is configured or activated with the data recombination function, the protocol data unit (PDU) corresponding to the first entity includes segment indication information (SI) and / or segment offset information (SO).

17. The method of any one of claims 11 to 16, wherein: In the case that the first entity supports data recombination and / or is configured or activated with the data recombination function, if the first entity is not configured or activated with the data retransmission function, the receiving end performs a non-acknowledged mode related parameter update mechanism; Or, In the case that the first entity supports data recombination, or the first entity is configured or activated with a data recombination function, if the first entity is configured or activated with a data retransmission function, the receiving end performs a parameter update mechanism related to a determination mode.

18. The method of any one of claims 11 to 17, wherein, The first entity is configured or activated with the data retransmission function, and further comprises: The receiving end sends retransmission indication information to the first entity of the sending end through the first entity.

19. The method of any one of claims 11 to 18, wherein, The first entity of the receiving end sends first packet discard indication information to the first entity of the sending end; The first entity of the receiving end sends first packet discard indication information to the first entity of the sending end in the case that a second time length is met; wherein the first packet discard indication information is used for the first entity of the sending end to determine a data packet that is lost or not needed, and / or to perform packet discard; The first entity of the receiving end receives second packet discard indication information sent from the first entity of the sending end; The first entity of the receiving end determines a data packet that is lost or not needed based on the second packet discard indication information; The first entity of the receiving end performs packet discard; The first entity of the receiving end performs packet discard in the case that a third time length is met; The first entity of the receiving end updates a parameter related to the packet discard processing.

20. A communication method, the method comprising: A sending end sends a first data packet, and a PDCP entity and a first RLC entity of the sending end use a same first sequence number (SN) information when operating on the first data packet. Further comprising:

21. The method of claim 20, wherein, The sending end receives third information, and the third information is used to indicate any one of the following: The PDCP entity and the first RLC entity share SN information corresponding to a data packet; The PDCP entity and the first RLC entity use a same SN information for a data packet; Whether the PDCP entity and the first RLC entity support adding one SN information in a data packet, or adding one SN information.

22. The method of claim 20, wherein The third information is indicated for the sending end, or for one or more data radio bearers of the sending end. Further comprising:

23. The method of any one of claims 20 to 22, wherein, The sending end determines or obtains, through the PDCP entity, first SN information corresponding to the first data packet.

24. The method of claim 23, wherein The sending end sends, through the PDCP entity, the first SN information to the first RLC entity.

25. The method of claim 23 or 24, wherein The PDCP entity corresponds to a plurality of RLC entities, the plurality of RLC entities include the first RLC entity, and the first RLC entity is associated with the first SN information. Including any one of the following:

26. The method of claim 25, wherein, The first RLC entity is a master RLC entity in the plurality of RLC entities; The first RLC entity is an RLC entity that activates PDCP duplication transmission; The first RLC entity is a secondary split RLC entity that activates PDCP; ​ The first RLC entity is an auxiliary RLC entity with activated PDCP; The first RLC entity is a determined RLC entity based on implementation of the sending end; The first RLC entity is a determined RLC entity based on a predefined rule.

27. The method of any one of claims 23 to 26, wherein, The PDCP entity corresponds to multiple RLC entities, and further comprises: The sending end sends fourth information to the multiple RLC entities through the PDCP entity, and the fourth information is used to indicate at least SN information associated with a corresponding RLC entity; The multiple RLC entities comprise a first RLC entity, and the first RLC entity is associated with the first SN information.

28. The method of any one of claims 21 to 25, wherein The sending end adds the first SN information in a packet header of the first data packet through the PDCP entity.

29. The method of claim 23 or 28, wherein, In a case where the first RLC entity works in an unacknowledged mode, and the first RLC entity is not configured or activated with one or more of data segmentation, split bearer, data duplication transmission, and duplicate packet detection function, the PDCP entity does not send the first SN information to the first RLC entity, and / or the PDCP entity adds the first SN information in the packet header of the first data packet.

30. The method of any one of claims 23 to 28, wherein, In a case where the first RLC entity works in an unacknowledged mode, and the first RLC entity is not configured or activated with one or more of data segmentation, split bearer, data duplication transmission, and duplicate packet detection function, if the first data packet needs or is configured to be delivered in order, the PDCP entity sends the first SN information to the first RLC entity, and / or the PDCP entity adds the first SN information in the packet header of the first data packet.

31. The method of any one of claims 23 to 30, wherein, The PDCP entity corresponds to multiple RLC entities, and further comprises: The sending end PDCP entity sends first status information to a receiving end PDCP entity, the first status information is used for the receiving end PDCP entity to determine a relationship between an RLC entity and SN information, and / or perform data recombination, and / or the first status information is used to indicate any one of the following: SN information associated with at least one or each RLC entity in the multiple RLC entities; SN information corresponding to a data packet transmitted by at least one or each RLC entity in the multiple RLC entities.

32. The method of claim 31, wherein, The first status information is sent based on a periodic sending or event triggering mode.

33. The method of any one of claims 20 to 32, wherein The sending end receives the first data packet sent by the PDCP entity through the first RLC entity; and / or The sending end determines or obtains the first SN information corresponding to the first data packet through the first RLC entity.

34. The method of claim 33, wherein, The sending end obtains the first SN information corresponding to the first data packet through the first RLC entity, comprising: The sending end first RLC entity receives the first SN information corresponding to the first data packet sent by the sending end PDCP entity.

35. The method of claim 33 or 34, wherein The sending end adds the first SN information in the packet header of the first data packet through the first RLC entity.

36. The method of any one of claims 33 to 35, wherein, In the case that the first RLC entity is configured / activated with a data segmentation function, the sending end adds segmentation indication information SI and / or segmentation offset information SO in the packet header of the first data packet through the first RLC entity.

37. The method of claim 31 or 32, wherein, In the case that the first RLC entity is configured / activated with a data segmentation function, the sending end adds the first SN information in the packet header of the segment data corresponding to the first data packet through the first RLC entity.

38. The method of any one of claims 33 to 37, wherein, The PDCP entity corresponds to a plurality of RLC entities, and the RLC entities include the first RLC entity; and further include: The sending end sends second status information to a receiving end first RLC entity through the first RLC entity, the second status information is used for the receiving end first RLC entity to determine the relationship between the RLC entity and the SN information, and / or the receiving end first RLC entity to perform data recombination, and / or the second status information is used to indicate any one of the following: The first SN information associated with the first RLC entity; The SN information associated with the data packet transmitted by the first RLC entity; The SN information associated with at least one or each RLC entity of the plurality of RLC entities; The SN information corresponding to the data packet transmitted by at least one or each RLC entity of the plurality of RLC entities.

39. The method of claim 38, wherein, The second status information is sent based on a periodic sending or event triggering manner.

40. The method of claim 32 or 39, wherein, The event includes one or more of the following: There is a gap between the SN information of the data packets received by the plurality of RLC entities; There is a gap between the SN information of the data packets received by the first RLC entity; N RLC PDUs are sent; The first RLC PDU is sent; The size of the sent RLC PDU is a first data amount or the first data amount of RLC PDUs is sent; The third status information sent by the receiving end is not received; The time length for which the third status information sent by the receiving end is not received is a fourth time length.

41. The method of any one of claims 20 to 40, wherein, Further comprising: The sending end receives third status information sent by a receiving end first RLC entity through the first RLC entity; The third status information includes the reception status or transmission status of the data packet sent by the sending end; The sending end first RLC entity updates the status parameter based on the third status information.

42. A communication method, the method comprising: A receiving end receives a first data packet, and a PDCP entity and a first RLC entity of the receiving end use the same first SN information when operating on the first data packet.

43. The method of claim 42, wherein, Further comprising: The receiving end receives third information, and the third information is used to indicate any one of the following: The PDCP entity and the first RLC entity share the SN information corresponding to the data packet; The PDCP entity and the first RLC entity use the same SN information for the data packet; The PDCP entity and the first RLC entity support adding one-time SN information in a data packet, or adding one SN information.

44. The method of claim 43, wherein, The third information is indicated for the receiving end, or for one or more data radio bearers of the receiving end.

45. The method of any one of claims 42 to 44, wherein, Further comprising: The receiving end determines or obtains the first SN information corresponding to the first data packet through the first RLC entity.

46. The method of claim 45, wherein, The receiving end first RLC entity obtains the first SN information corresponding to the first data packet, comprising: The receiving end first RLC entity receives the first SN information sent by the receiving end PDCP entity.

47. The method of claim 45, wherein, Further comprising: The receiving end first RLC entity sends the first SN information to the receiving end PDCP entity.

48. The method of any one of claims 42 to 47, wherein, The PDCP entity corresponds to a plurality of RLC entities, and the plurality of RLC entities include the first RLC entity; further comprising: The receiving end first RLC entity receives the second status information sent by the sending end first RLC entity; the second status information is used for the receiving end first RLC entity to determine the relationship between the RLC entity and the SN information, and / or the receiving end first RLC entity to perform data recombination, and / or the second status information is used to indicate any one of the following: The first SN information associated with the first RLC entity; The SN information associated with the data packet transmitted by the first RLC entity; The SN information associated with each RLC entity in the plurality of RLC entities; The SN information corresponding to the data packet transmitted by each RLC entity in the plurality of RLC entities.

49. The method of claim 48, wherein, Further comprising: The receiving end first RLC entity performs at least one of the following behaviors according to the second status information: Determining the relationship between the RLC entity and the SN, Determining the relationship between the data packet transmitted by the RLC entity and the SN, Performing data recombination, Determining the SN information contained in the third status information sent by the receiving end first RLC; Determining that there is interval SN information; Sending first indication information to the receiving end PDCP entity, the first indication information is used to indicate the SN information associated with at least one or each RLC entity in the plurality of RLC entities, and / or the SN information corresponding to the data packet transmitted by at least one or each RLC entity in the plurality of RLC entities.

50. The method of claim 48 or 49, wherein, Further comprising: The receiving end receives the first data packet corresponding to the first SN information associated with the first RLC through the first RLC entity.

51. The method of any one of claims 42 to 50, wherein, Further comprising: The receiving end sends third status information to the sending end first RLC entity through the first RLC entity; The third status information includes the receiving state or transmission state of the data packet sent by the sending end first RLC entity.

52. The method of claim 49, wherein, Further comprising at least one of the following: The receiving end first RLC entity, or the receiving end, determines or believes that the data packet corresponding to the SN information not associated with the first RLC has been received, or does not need to be received, or is maintained by other RLC entities, or does not need to be included in the third status information of the RLC entity. The receiving state corresponding to the SN information in the third status information not associated with the first RLC is an acknowledgement receiving state, or the third status information indicates that the data packet / data packet segment corresponding to the SN is transmitted successfully or is received successfully.

53. The method of any one of claims 42 to 52, wherein, The receiving end determines or obtains the first SN information corresponding to the first data packet through a PDCP entity.

54. The method of claim 53, wherein, The receiving end obtains the first SN information corresponding to the first data packet through the PDCP entity, comprising: The receiving end PDCP entity receives the first SN information sent by the receiving end first RLC entity.

55. The method of claim 53 or 54, wherein, The PDCP entity corresponds to a plurality of RLC entities, and the RLC entities include the first RLC entity; further comprising: The PDCP entity of the receiving end receives the first status information sent by the PDCP entity of the sending end; the first status information is used for the PDCP entity of the receiving end to determine the relationship between the RLC entity and the SN information, and / or to perform data recombination, and / or the first status information is used to indicate any one of the following: SN information associated with at least one or each of the plurality of RLC entities; SN information corresponding to the data packet transmitted by at least one or each of the plurality of RLC entities.

56. The method of claim 55, wherein, Further comprising: The receiving end PDCP entity performs at least one of the following behaviors according to the first status information: determining the relationship between the RLC entity and the SN information, determining the relationship between the data packet transmitted by the RLC entity and the SN, performing data recombination, determining the SN information contained in the fourth status information sent by the PDCP entity of the receiving end; determining the interval SN information; sending second indication information to the receiving end RLC entity, the second indication information being used to indicate the SN information associated with at least one or each of the plurality of RLC entities, and / or the SN information corresponding to the data packet transmitted by at least one or each of the plurality of RLC entities.

57. The method of any one of claims 53 to 56, wherein, Further comprising: The receiving end PDCP entity sends the fourth status information to the sending end PDCP entity, and the fourth status information includes the receiving state or transmission state of the data packet sent by the sending end PDCP.

58. A communication device, the device comprising: a first processing unit configured to perform one or more of the following operations on data sent by a higher layer through a first entity: compression, encryption, integrity protection, packet discard indication, packet discard processing, data segmentation, data retransmission, routing.

59. A communication device, the device comprising: a second processing unit configured to perform one or more of the following operations on data sent by a lower layer through a first entity: data retransmission request, data recombination, integrity verification, packet discard indication, packet discard processing, decryption, decompression, submitting data packets to a higher layer.

60. A communication device, the device comprising: a third communication unit configured to send a first data packet, a PDCP entity and a first RLC entity of the first communication unit using the same first SN information when operating on the first data packet. 61.A communication device, the device comprising: a fourth communication unit configured to receive a first data packet, the PDCP entity and the first RLC entity of the second communication unit using the same first SN information when operating on the first data packet. 62.A communication device, the device comprising: a memory for storing a computer program; a processor connected with the memory, for calling and running the computer program from the memory, implementing the method of any one of claims 1 to 10, or, implementing the method of any one of claims 11 to 19, or, implementing the method of any one of claims 20 to 41, or, implementing the method of any one of claims 42 to 57; a transceiver for receiving and sending information in the process of transceiving information with other external devices. 63.A chip, the chip comprising: a memory for storing a computer program; a processor connected with the memory, for calling and running the computer program from the memory, so that the device installed with the chip implements the method of any one of claims 1 to 10, or, implements the method of any one of claims 11 to 19, or, implements the method of any one of claims 20 to 41, or, implements the method of any one of claims 42 to 57; a transceiver for receiving and sending information in the process of transceiving information with devices or chips. 64.A computer readable storage medium, the computer readable storage medium storing a computer program, the computer program being executed by at least one processor to implement the method of any one of claims 1 to 10, or, implement the method of any one of claims 11 to 19, or, implement the method of any one of claims 20 to 41, or, implement the method of any one of claims 42 to 57. 65.A computer program product, comprising a computer program or instructions, the computer program or instructions being executed by a processor to implement the steps of the method of any one of claims 1 to 10, or, implement the method of any one of claims 11 to 19, or, implement the method of any one of claims 20 to 41, or, implement the method of any one of claims 42 to 57. 66.A computer program, the computer program causing a computer to implement the method of any one of claims 1 to 10, or, implement the method of any one of claims 11 to 19, or, implement the method of any one of claims 20 to 41, or, implement the method of any one of claims 42 to 57.

Images