WO2023011219A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023011219A1
WO2023011219A1 PCT/CN2022/107481 CN2022107481W WO2023011219A1 WO 2023011219 A1 WO2023011219 A1 WO 2023011219A1 CN 2022107481 W CN2022107481 W CN 2022107481W WO 2023011219 A1 WO2023011219 A1 WO 2023011219A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
communication device
entity
pdu
data
Prior art date
Application number
PCT/CN2022/107481
Other languages
English (en)
French (fr)
Inventor
王君
吕永霞
王婷
张立清
马江镭
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22851933.6A priority Critical patent/EP4380226A1/en
Publication of WO2023011219A1 publication Critical patent/WO2023011219A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control

Definitions

  • the embodiments of the present application relate to the field of wireless communication, and in particular, to a communication method and device.
  • Ultra-reliability low latency communication is one of the important application scenarios of the fifth generation mobile network (5G).
  • the biggest feature of URLLC is low latency and high reliability. Therefore, it is widely used in the fields of automatic driving, industrial manufacturing, Internet of Vehicles and smart grid.
  • the New Radio (NR) protocol stipulates that there is a certain protocol layer structure between the devices that communicate with each other.
  • the data packets from the application (APP) layer at the sending end need to pass through the service data adaptation protocol (service data adaptation protocol).
  • SDAP packet data convergence layer protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio link control
  • MAC media access control
  • PHY physical (physical layer, PHY)
  • Embodiments of the present application provide a communication method and device, which are used to reduce air interface overhead and processing delay, and meet URLLC requirements for low delay and high reliability.
  • a communication method is provided.
  • the method is executed by an RLC entity of a first communication device as an example.
  • the first communication device is, for example, a base station or a terminal, which is not limited in this application.
  • the method includes: the RLC entity of the first communication device obtains the RLC SDU from the upper layer entity; the RLC entity of the first communication device generates the RLC PDU according to the RLC SDU; wherein, the RLC PDU includes a header and data, and the data is the first RLC SDU in the data of the RLC SDU.
  • the header includes a sequence number and a first index
  • the sequence number is used to identify the RLC SDU
  • the first index is used to identify the number of the first segment in the segment of the RLC SDU
  • the different segments in the RLC SDU are respectively Corresponding to different indexes; the RLC entity of the first communication device sends an RLC PDU.
  • a communication method is provided. Taking the method executed by an RLC entity of a second communication device as an example, the second communication device can communicate with the first communication device, and the second communication device is, for example, a base station or a terminal. Applications are not limited.
  • the method includes: the RLC entity of the second communication device receives the RLC PDU; wherein, the RLC PDU includes a header and data, the data is the first segment of the RLC SDU, the header includes a sequence number and a first index, and the sequence number is used to identify the RLC SDU, the first index is used to identify the number of the first segment in the segment of the RLC SDU, and different segments in the RLC SDU correspond to different indices; the RLC entity of the second communication device is determined according to the sequence number and the first index The data of the RLC PDU is the first segment of the segments of the RLC SDU.
  • the above solution uses an index to indicate which segment the data in each RLC PDU is in the RLC SDU, which can reduce the header overhead of the RLC PDU on the premise of ensuring the reliability of data transmission, thereby saving air interface overhead.
  • the value of the first index does not exceed the threshold.
  • the overhead corresponding to the first index does not exceed preset bits. For example, if the value range of the first index is 0 to 15, the corresponding binary representation is "1111", and the overhead of the first index is at most 4 bits.
  • a communication method is provided.
  • the method is executed by an RLC entity of a first communication device as an example.
  • the first communication device is, for example, a base station or a terminal, which is not limited in this application.
  • the method includes: the RLC entity of the first communication device obtains the RLC SDU from the upper layer entity; the RLC entity of the first communication device determines that the RLC SDU is not segmented according to configuration information, wherein the configuration information is used to indicate that the RLC SDU is not segmented; the first communication device
  • the RLC entity generates an RLC PDU according to the RLC SDU; wherein, the data of the RLC PDU is a complete RLC SDU; the RLC entity of the first communication device sends the RLC SDU.
  • a communication method is provided. Taking the method executed by an RLC entity of a second communication device as an example, the second communication device can communicate with the first communication device, and the second communication device is, for example, a base station or a terminal. Applications are not limited.
  • the method includes: the RLC entity of the second communication device receives the RLC PDU; according to the configuration information, it is determined that the data of the RLC PDU is a complete RLC SDU.
  • the network device (such as the first communication device or the second communication device or other devices) also generates and sends configuration information, where the configuration information is used to instruct the first communication device not to segment the RLC SDU.
  • the configuration granularity of configuration information may be determined by one or more of data radio bearer, quality of service flow, PDU session, network slice, logical channel identifier, terminal, PDCP entity or RLC entity.
  • the specific content of the configuration information may include: first indication information, used to indicate that the service type is an ultra-reliable low-latency communication service; and/or, second indication information, used to indicate that RLC SDU is allowed The maximum number of segments that can be segmented is 0 or the RLC SDU is not segmented.
  • the configuration information may include: first indication information, used to indicate that the service type corresponding to the first data radio bearer is an ultra-reliable low-latency communication service, and/or, a second indication Information, used to indicate that the maximum number of segments allowed for the RLC SDU corresponding to the first data radio bearer is 0 or that the RLC SDU corresponding to the first data radio bearer is not segmented.
  • the content of the configuration information can be implemented in multiple ways, which improves the flexibility of the solution.
  • a communication method is provided, and the method may be executed by a first communication device, such as a base station or a terminal, which is not limited in this application.
  • the method includes: the first communication device acquires configuration information of the radio bearer, wherein the configuration information is used to indicate that the transmission mode of the RLC entity corresponding to the radio bearer is a transparent mode; the first communication device transmits the transmission mode of the RLC entity corresponding to the radio bearer based on the configuration information The mode is configured as transparent mode.
  • a communication method which can be executed by a second communication device, and the second communication device can communicate with the first communication device.
  • the second communication device is, for example, a base station, which is not limited in this application.
  • the method includes: the second communication device generates radio bearer configuration information, wherein the configuration information is used to indicate that the transmission mode of the RLC entity corresponding to the radio bearer is a transparent mode; the second communication device sends the configuration information.
  • the radio bearer is one of a data radio bearer, a signaling radio bearer, or a computing radio bearer.
  • a communication method is provided.
  • the method is executed by a PDCP entity of a first communication device.
  • the first communication device is, for example, a base station or a terminal, which is not limited in this application.
  • the method includes: the PDCP entity of the first communication device obtains the PDCP SDU; the PDCP entity of the first communication device generates a PDCP PDU according to the PDCP SDU; wherein, the PDCP PDU includes a header and data, and the data is a segment in the PDCP SDU, and the header Including the sequence number, the sequence number is used to identify the PDCP SDU, the header also includes a segment offset or index, and the segment offset is used to indicate the byte offset of the first byte of a segment in the PDCP SDU, The index is used to identify the number of a segment in the segment of the RLC SDU.
  • a communication method is provided. Taking the method executed by the PDCP entity of the second communication device as an example, the second communication device can communicate with the first communication device, and the second communication device is, for example, a base station or a terminal. Applications are not limited.
  • the method includes: the PDCP entity of the second communication device obtains multiple PDCP PDUs; wherein, each PDCP PDU in the multiple PDCP PDUs includes a header and data, the data is a segment in the PDCP SDU, and the header includes a sequence number, The sequence number is used to identify the PDCP SDU, and the header also includes a segment offset or index.
  • the segment offset is used to indicate the byte offset of the first byte of a segment in the PDCP SDU, and the index is used to identify The number of a segment in the segment of the RLC SDU; wherein, the sequence numbers corresponding to multiple PDCP PDUs are the same; the PDCP entity of the second communication device generates a PDCP SDU according to multiple PDCP PDUs.
  • the functions of the RLC layer can be merged into the PDCP layer, thereby saving all header overheads of the RLC layer, so that air interface overhead can be reduced.
  • the PDCP entity of the first communication device may directly deliver the PDCP PDU to the media access control entity.
  • the PDCP entity of the second communication device may also directly acquire multiple PDCP PDUs from the MAC entity.
  • the processing process of the RLC layer can be directly omitted, thereby reducing the processing delay of the first communication device and the processing end.
  • a communication method is provided, and the method may be executed by a first communication device.
  • the first communication device is, for example, a base station or a terminal, which is not limited in this application.
  • the method includes: the first PDCP entity of the first communication device sends the first PDCP data PDU; the second PDCP entity of the first communication device sends the first PDCP control PDU; wherein, the first PDCP control PDU is associated with the first PDCP data PDU, The first PDCP entity is different from the second PDCP entity.
  • a communication method which can be executed by a second communication device, and the second communication device can communicate with the first communication device, and the second communication device is, for example, a terminal or a base station, which is not covered by this application. limit.
  • the method includes: the second communication device receives the first PDCP data PDU sent by the first PDCP entity of the first communication device; the second communication device receives the first PDCP control PDU sent by the second PDCP entity of the first communication device; wherein, the first A PDCP control PDU is associated with a first PDCP data PDU, and the first PDCP entity is different from the second PDCP entity.
  • PDCP data PDU and PDCP control PDU can be decoupled, and PDCP data PDU and PDCP control PDU can be sent by different PDCP entities, so that PDCP entities can be supported to send PDCP data PDUs in TM mode, reducing the header overhead of PDCP data PDUs , saving air interface overhead.
  • the first communication device also acquires configuration information; the first communication device determines according to the configuration information that the first PDCP entity sends the first PDCP data PDU, and the second PDCP entity sends the first PDCP control PDU. For example, if the first communication device is a terminal and the second communication device is a base station, the second communication device generates configuration information and sends the configuration information to the first communication device, and the first communication device receives the configuration information from the second communication device; or For example, if the second communication device is a terminal and the first communication device is a base station, the first communication device generates configuration information and sends the configuration information to the second communication device, and the second communication device receives the configuration information from the first communication device.
  • the configuration information may include: first indication information, used to indicate: the transmission entity of the PDCP data PDU of the first PDCP entity is separated from the transmission entity of the PDCP control PDU, or the transmission mode of the first PDCP entity for transparent mode.
  • the network side can explicitly indicate that the transport entity of the PDCP data PDU of the first PDCP entity is separated from the transport entity of the PDCP control PDU, and can also implicitly indicate that the transport entity of the PDCP data PDU of the first PDCP entity is separated from the PDCP control PDU
  • the separation of the transmission entity improves the flexibility of the solution.
  • the configuration information may also include at least one of the following: second indication information, used to indicate: the first PDCP entity is used to transmit PDCP data PDU; third indication information, used to indicate: the second PDCP entity Used to transmit the PDCP control PDU; the fourth indication information is used to indicate that the PDCP control PDU transmitted by the second PDCP entity is associated with the PDCP data PDU transmitted by the first PDCP entity.
  • the network side can more clearly indicate the manner in which the transmission entity of the PDCP data PDU at the terminal side is separated from the transmission entity of the PDCP control PDU, which improves the reliability of the solution.
  • the method further includes: sending the second PDCP data PDU by the third PDCP entity of the first communication device; sending the second PDCP control PDU by the fourth PDCP entity of the first communication device.
  • the second communication device receives the second PDCP data PDU sent by the third PDCP entity of the first communication device; the second communication device receives the second PDCP control PDU sent by the fourth PDCP entity of the first communication device.
  • the second PDCP control PDU is associated with the second PDCP data PDU, and any two entities among the third PDCP entity, the fourth PDCP entity, the first PDCP entity, and the second PDCP entity are different.
  • the association relationship between the PDCP entity transmitting the PDCP data PDU and the PDCP entity transmitting the PDCP control PDU may be a one-to-one association relationship.
  • the method further includes: the third PDCP entity of the first communication device sends a second PDCP data PDU; the second PDCP entity of the first communication device sends a second PDCP control PDU.
  • the second communication device receives the second PDCP data PDU sent by the third PDCP entity of the first communication device; the second communication device receives the second PDCP control PDU sent by the second PDCP entity of the first communication device.
  • the second PDCP control PDU is associated with the second PDCP data PDU, and any two entities among the third PDCP entity, the first PDCP entity, and the second PDCP entity are different.
  • the association relationship between the PDCP entity transmitting the PDCP data PDU and the PDCP entity transmitting the PDCP control PDU may be a many-to-one association relationship.
  • the first PDCP control PDU may carry the identifier of the first PDCP entity; the second The PDCP control PDU carries the identifier of the third PDCP entity or the identifier of the second PDCP data PDU.
  • a communication method is provided, and the method may be executed by a first communication device, such as a base station or a terminal, which is not limited in this application.
  • the method includes: the first PDCP entity of the first communication device sends the first PDCP data PDU; the first communication device RRC entity or NAS entity or SDAP entity or RLC entity or MAC entity or physical layer entity sends the first PDCP control PDU; wherein, The first PDCP control PDU is associated with the first PDCP data PDU.
  • a communication method which can be executed by a second communication device, and the second communication device can communicate with the first communication device, such as a terminal or a base station, which is not covered by this application. limit.
  • the method includes: the second communication device receives the first PDCP data PDU sent by the first PDCP entity of the first communication device; the second communication device receives the RRC entity or NAS entity or SDAP entity or RLC entity or MAC entity of the first communication device or The first PDCP control PDU sent by the physical layer entity; wherein, the first PDCP control PDU is associated with the first PDCP data PDU.
  • the decoupling of PDCP data PDU and PDCP control PDU can be realized, and PDCP control PDU can be sent through other layer entities, so that PDCP entity can be supported to send PDCP data PDU in TM mode, thereby reducing the header overhead of PDCP data PDU and saving air interface overhead.
  • a communication method is provided, and the method may be executed by a first communication device, such as a base station or a terminal, which is not limited in this application.
  • the method includes: the first communication device receives the data packet; wherein, the transmission modes of the PDCP entity and the RLC entity of the first communication device are both transparent modes; the first communication device receives the data packet according to the time domain position, sequence number and time domain position Mapping relationship to determine the sequence number corresponding to the data packet.
  • a communication method which can be executed by a second communication device, and the second communication device can communicate with the first communication device.
  • the second communication device is, for example, a terminal or a base station, which is not covered by this application. limit.
  • the method includes: the second communication device determines the time domain position corresponding to the data packet according to the mapping relationship between the sequence number and the time domain position and the sequence number corresponding to the data packet; wherein, the transmission modes of the PDCP entity and the RLC entity of the second communication device are both It is a transparent mode; the second communication device sends the first data packet at a position in the time domain corresponding to the data packet.
  • both the PDCP entity and the RLC entity can support TM, and at the same time, the first communication device can obtain the SN corresponding to the PDCP data PDU and the RLC data PDU, thereby saving air interface overhead and ensuring the reliability of data transmission.
  • mapping operation between the serial number and the time domain position may be performed by an entity corresponding to any protocol layer. For example:
  • the media access control entity of the first communication device may transmit the time domain position of the data packet to the PDCP entity of the first communication device; the PDCP entity of the first communication device receives the data according to the media access control entity
  • the time-domain position of the packet, the mapping relationship between the sequence number and the time-domain position determine the corresponding sequence number of the data packet.
  • the media access control entity of the first communication device can determine the sequence number corresponding to the data packet according to the time domain position of the received data packet, the mapping relationship between the sequence number and the time domain position, and then the first communication
  • the MAC entity of the device transmits the sequence number corresponding to the data packet to the PDCP entity of the first communication device.
  • the PDCP entity of the second communication device may also transfer the serial number corresponding to the data packet to the media access control entity of the second communication device, and then the media access control entity of the second communication device
  • the mapping relationship with the time domain position and the sequence number corresponding to the data packet determine the time domain position corresponding to the data packet.
  • the PDCP entity of the second communication device can determine the time domain position corresponding to the data packet according to the mapping relationship between the sequence number and the time domain position, and the sequence number corresponding to the data packet, and then the PDCP entity of the second communication device The entity transmits the time-domain position corresponding to the data packet to the medium access control entity of the second communication device.
  • the first communication device may acquire the mapping relationship between the sequence number and the time domain position from the network device. For example, if the first communication device is a terminal, the base station may send the mapping relationship between the sequence number and the time domain position, and then the first communication device receives the mapping relationship between the sequence number and the time domain position from the base station.
  • a communication device the device includes a transceiver module for communicating with other devices outside the device, and the processing module is used for controlling the communication module to perform any possible operation according to the first aspect or the first aspect Design or the second aspect or any possible design of the second aspect or the third aspect or any possible design of the third aspect or the fourth aspect or any possible design of the fourth aspect or the fifth aspect or any possible design of the fifth aspect Possible design or the sixth aspect or any possible design of the sixth aspect or the seventh aspect or any possible design of the seventh aspect or the eighth aspect or any possible design of the eighth aspect or the ninth aspect or the ninth aspect Any possible design or the tenth aspect or any possible design of the tenth aspect or any possible design of the eleventh aspect or the eleventh aspect or the twelfth aspect or any possible design of the twelfth aspect or A module of the method described in the thirteenth aspect or any possible design of the thirteenth aspect or the fourteenth aspect or any possible design of the fourteenth aspect.
  • a communication device including a processor and a memory; wherein the processor and the memory are coupled, the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions stored in the memory, so that the communication device executes
  • the communication device executes
  • the fifth aspect or any possible design of the fifth aspect or the sixth aspect or any possible design of the sixth aspect or the seventh aspect or any possible design of the seventh aspect or the eighth aspect or any possible design of the eighth aspect One possible design or the ninth aspect or any possible design of the ninth aspect or the tenth aspect or any possible design of the tenth aspect or the eleventh aspect or any possible design of the eleventh aspect or the twelfth aspect Or any possible design of the twelfth aspect, or the thirteenth aspect, or any possible design of the thirteenth aspect, or the method described in the
  • a chip including a logic circuit and an input-output interface; wherein, the input-output interface is used to receive signals from other communication devices outside the chip and transmit them to the logic circuit or send signals from the logic circuit to Other communication devices other than the chip, the logic circuit is used to realize the first aspect or any possible design of the first aspect or the second aspect or any possible design of the second aspect or the third aspect or any possible design of the third aspect or the fourth aspect or any possible design of the fourth aspect or the fifth aspect or any possible design of the fifth aspect or the sixth aspect or any possible design of the sixth aspect or the seventh aspect or any possible design of the seventh aspect.
  • a computer-readable storage medium is provided.
  • Computer programs or instructions are stored in the storage medium.
  • any possible design or design according to the first aspect or the first aspect can be realized.
  • Possible design or the tenth aspect or any possible design of the tenth aspect or the eleventh aspect or any possible design of the eleventh aspect or the twelfth aspect or any possible design of the twelfth aspect or the thirteenth aspect The method described in the aspect or any possible design of the thirteenth aspect, or the fourteenth aspect or any possible design of the fourteenth aspect.
  • a computer program product which, when running on a computer, makes the first aspect or any possible design of the first aspect or the second aspect or any possible design of the second aspect or the third aspect or any possible design of the third aspect or the fourth aspect or any possible design of the fourth aspect or the fifth aspect or any possible design of the fifth aspect or the sixth aspect or any possible design of the sixth aspect or
  • the method described in the aspect or any possible design of the fourteenth aspect is executed.
  • FIG. 1 is a schematic diagram of a user plane protocol stack in the NR protocol
  • Fig. 2 is the schematic diagram of RLC SDU segmentation
  • FIGS. 1A to Figure 3E are schematic diagrams of the format of the RLC data PDU in the unacknowledged mode
  • Figure 4A and Figure 4B are schematic diagrams of the formats of two PDCP data PDUs
  • FIG. 5 is a schematic structural diagram of a communication system applicable to an embodiment of the present application.
  • FIG. 6A is a flowchart of a communication method provided by an embodiment of the present application.
  • Figure 6B is a schematic diagram of a possible RLC PDU format provided by the embodiment of the present application.
  • FIG. 7 is a flow chart of another communication method provided by the embodiment of the present application.
  • FIG. 8A is a flow chart of another communication method provided by the embodiment of the present application.
  • FIG. 8B is a schematic diagram of another possible RLC PDU format provided by the embodiment of the present application.
  • FIG. 9A is a flow chart of another communication method provided by the embodiment of the present application.
  • Figure 9B and Figure 9C are schematic diagrams of the format of two possible PDCP data PDUs provided by the embodiment of the present application.
  • Figures 9D to 9F are schematic diagrams of the format of three possible PDCP control PDUs provided by the embodiment of the present application.
  • FIG. 10A is a schematic diagram of a possible PDCP PDU format provided by the embodiment of the present application.
  • FIG. 10B is a flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 10C is a flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 11A is a flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 11B is a schematic diagram of a single-carrier transmission scenario provided by an embodiment of the present application.
  • FIG. 11C is a schematic diagram of a dual-carrier transmission scenario provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another possible communication device provided by the embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a possible chip provided by an embodiment of the present application.
  • NR New Radio
  • FIG 1 is a schematic diagram of the user plane protocol stack for communication between the UE and the gNB, including the service data adaptation protocol (service data adaptation protocol (SDAP) layer, packet data convergence layer protocol (Packet Data Convergence Protocol, PDCP) layer, radio link control (Radio link control, RLC) layer, media access control (medium access control, MAC) layer, Physical (physical layer, PHY) layer, etc.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence layer protocol
  • RLC radio link control
  • media access control medium access control
  • MAC media access control
  • Physical physical layer, PHY
  • each layer protocol is executed by the entity of the corresponding layer.
  • the entity implementing the SDAP layer protocol is called the SDAP entity
  • the entity executing the PDCP layer protocol is called the PDCP entity.
  • An entity that executes the RLC layer protocol is called an RLC entity
  • an entity that executes the MAC layer protocol is called a MAC entity
  • an entity that executes a PHY layer protocol is called a PHY entity, and so on.
  • the processing of data at each layer on the UE side includes:
  • the SDAP entity on the UE side receives the data packet sent by the application (application, APP) layer, adds an SDAP header (header) to the data packet, and finally forms a protocol data unit (protocol data unit, PDU) of the SDAP layer, referred to as SDAP PDU , and passed to the PDCP entity;
  • application application
  • APP application
  • header header
  • PDU protocol data unit
  • the PDCP entity receives the SDAP PDU and uses it as a service data unit (service data unit, SDU) of the PDCP layer, referred to as PDCP SDU.
  • SDU service data unit
  • the PDCP header is added, and finally a PDCP PDU is formed and passed to the RLC entity;
  • the RLC entity receives the PDCP PDU and uses it as an SDU of the RLC layer, referred to as RLC SDU. After being processed by the RLC entity, the RLC header is added to finally form a PDU of the RLC layer, referred to as RLC PDU, and passed to the MAC entity;
  • the RLC entity when the RLC entity processes the RLC SDU, it can also segment the RLC SDU to generate multiple RLC SDU segments (Segement), and then add an RLC header to each segment, and finally form multiple RLC PDUs and submit them to the MAC. entity, as shown in Figure 2.
  • the MAC entity receives the RLC PDU and uses it as the SDU of the MAC layer, referred to as the MAC SDU.
  • the MAC subheader (Subheader) is added to generate a MAC subPDU, and multiple MAC sbuPDUs (if there are multiple APP data packets must be sent, then generate MAC sbuPDUs corresponding to multiple MAC SDUs; if there are MAC CEs to be sent, generate MAC subPDUs corresponding to MAC CEs) concatenate to generate MAC layer PDUs, referred to as MAC PDUs, and submit them to the PHY entity ;
  • the PHY entity After the PHY entity receives the MAC PDU from the MAC entity, it encodes the PHY entity and sends it to the base station from the air interface.
  • the transmission mode of the RLC entity has the following three types:
  • Unacknowledged mode Unacknowledged mode
  • the sending entity adds the necessary control protocol overhead to the high-level PDU, and then transmits it but does not guarantee delivery to the peer entity, and does not use the retransmission protocol.
  • the receiving entity marks the received erroneous data as an error and submits it, or discards it directly and reports it to the upper layer. Since the RLC PDU contains a sequence number (sequence number, SN), the integrity of the upper layer PDU can be detected.
  • UM's services include cell broadcasting and IP telephony.
  • Transparent mode The sending entity does not add any additional protocol overhead outside of control to the high-level data, and only decides whether to perform segmentation operations according to the type of business. If there is an error in the PDU received by the receiving entity, according to the configuration, it will be delivered after the error mark or discarded directly and reported to the upper layer.
  • Real-time voice services usually use the RLC transparent mode.
  • Acknowledged mode (acknowledged mode, AM): The sending side adds the necessary control protocol overhead to the high-level data and then transmits it, and ensures that it is delivered to the peer entity. Because of the automatic repeat request (auto repeat request, ARQ) capability, if the RLC receives an incorrect RLC PDU, it will notify the sender's RLC to retransmit the PDU. Since the RLC PDU contains sequence number information, it supports in-order/out-of-order delivery of data to higher layers.
  • AM mode is the standard mode for packet data transmission, such as www and e-mail downloads.
  • the RLC entity For the transmission of data packets in the URLLC service scenario, the RLC entity generally uses the UM.
  • the radio link control data protocol data unit (RLC data PDU) of UM supports the following formats:
  • the RLC data PDU includes a complete RLC SDU
  • the RLC data PDU includes a 6-bit SN (no segment offset (segment offset, SO));
  • the RLC data PDU includes a 12-bit SN (no SO);
  • the RLC data PDU includes a 6-bit SN and has an SO
  • the RLC data PDU includes a 12-bit SN and has an SO.
  • a data packet sent by the APP layer corresponds to an SN.
  • the SN of the RLC layer can generally be called an RLC SN;
  • the unit is byte (byte). After the complete data packet corresponding to an RLC SN is segmented, it is used to indicate where the segment is located in the complete RLC SN. For example, the first byte of the segment is in the PDCP The byte offset in the SDU (for example, the SO of the first segment is "0000000000000000”), and the length is 16 bits (bits);
  • Data upper layer data, for example: application layer data, or business data adaptation protocol data protocol data unit (SDAP data PDU), or business data adaptation protocol control protocol data unit (SDAP control PDU), etc.;
  • SDAP data PDU business data adaptation protocol data protocol data unit
  • SDAP control PDU business data adaptation protocol control protocol data unit
  • Segmentation Information (Segmentation Info, SI): used to further indicate the type of RLC PDU.
  • the data of the RLC PDU contains all bytes of the RLC SDU
  • the data of the RLC PDU contains the first segment of the RLC SDU;
  • the data of the RLC PDU contains the last segment of the RLC SDU
  • the data of the RLC PDU neither contains the first segment of the RLC SDU nor the last segment of the RLC SDU.
  • Octal octal, which means octal.
  • the packet data convergence layer protocol data protocol data unit (PDCP data PDU) supports the following two formats:
  • the PDCP data PDUs in the above two formats have an additional header overhead of 6 bytes and 7 bytes respectively.
  • D/C indicates the type of PDCP PDU, including "PDCP data PDU” (that is, carrying APP data), "packet data convergence layer protocol control protocol data unit PDCP control PDU” (that is, carrying the control signaling of the PDCP layer itself) possible;
  • the SN of the PDCP data PDU is the same as the SN of the corresponding RLC SDU.
  • the SN of the PDCP layer can be called PDCP SN;
  • Data upper layer data, for example: application layer data, or SDAP data PDU, or SDAP control PDU, etc.;
  • MAC-I Integrity protection field, used for integrity check at the receiving end.
  • the technical solution of the embodiment of the present application is provided, which is used to simplify the protocol layer structure between the devices communicating with each other, thereby reducing the processing delay of data packets on the devices and reducing the air interface overhead.
  • the embodiments of the present application can be applied to various communication systems, including but not limited to: satellite communication systems, Internet of things (Internet of things, IoT), narrowband Internet of things (Narrow band Internet of things, NB-IoT) systems, global mobile Communication system (global system for mobile communications, GSM), enhanced data rate for GSM evolution system (enhanced data rate for GSM evolution, EDGE), wideband code division multiple access system (wideband code division multiple access, WCDMA), code division multiple access 2000 system (code division multiple access, CDMA2000), time division-synchronization code division multiple access system (time division-synchronization code division multiple access, TD-SCDMA), long term evolution system (long term evolution, LTE), fifth-generation mobile communication technology ( 5th generation mobile network, 5G) system, such as 5G new radio (new radio, NR), and the enhanced mobile broadband (eMBB) of the three major application scenarios of the 5G mobile communication system, ultra-reliable, low-time Ultra reliable low latency communications (uRLLC) and massive machine type communications (m
  • embodiments of the present application are applicable not only to communication between base stations and terminals, but also to communication between base stations, communication between terminals, communication between Internet of Vehicles, Internet of Things, or Industrial Internet, etc.
  • FIG. 5 is a schematic structural diagram of a communication system 1000 applicable to this embodiment of the present application.
  • the communication system includes a radio access network 100 and a core network 200 , and optionally, the communication system 1000 may also include the Internet 300 .
  • the radio access network 100 may include at least one radio access network device (such as 110a and 110b in FIG. 5 ), and may also include at least one terminal (such as 120a-120j in FIG. 5 ).
  • the terminal is connected to the wireless access network device in a wireless manner, and the wireless access network device is connected to the core network in a wireless or wired manner.
  • the core network equipment and the wireless access network equipment can be independent and different physical equipment, or the functions of the core network equipment and the logical functions of the wireless access network equipment can be integrated on the same physical equipment, or it can be a physical equipment It integrates some functions of core network equipment and some functions of wireless access network equipment. Terminals and wireless access network devices may be connected to each other in a wired or wireless manner.
  • FIG. 5 is only a schematic diagram.
  • the communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG. 5 .
  • the radio access network equipment can be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point, TRP), and the next generation in the fifth generation (5th generation, 5G) mobile communication system
  • Base station (next generation NodeB, gNB), the next generation base station in the sixth generation (6th generation, 6G) mobile communication system, the base station in the future mobile communication system or the access node in the WiFi system, etc.; it can also complete the base station part
  • a functional module or unit for example, can be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU).
  • the CU here completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and also completes the function of the service data adaptation protocol (SDAP); the DU completes the functions of the base station
  • the functions of the radio link control (Radio link control, RLC) layer and the medium access control (medium access control, MAC) layer can also complete the functions of part or all of the physical layer.
  • RLC Radio link control
  • MAC medium access control
  • the radio access network device may be a macro base station (such as 110a in Figure 5), a micro base station or an indoor station (such as 110b in Figure 5), or a relay node or a donor node.
  • the embodiment of the present application does not limit the specific technology and specific equipment form adopted by the radio access network equipment.
  • a base station is used as an example of a radio access network device for description below.
  • a terminal may also be called terminal equipment, user equipment (user equipment, UE), mobile station, mobile terminal, and so on.
  • Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things ( internet of things, IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, etc.
  • Terminals can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal.
  • Base stations and terminals can be fixed or mobile. Base stations and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the base station and the terminal.
  • the helicopter or drone 120i in FIG. 5 can be configured as a mobile base station.
  • the helicopter or drone 120i in FIG. 5 can be configured as a mobile base station.
  • those terminals 120j that access the wireless access network 100 through base station for base station 110a, 120i is a terminal, that is, communication between 110a and 120i is performed through a wireless air interface protocol.
  • communication between 110a and 120i may also be performed through an interface protocol between base stations.
  • 120i is also a base station. Therefore, both the base station and the terminal can be collectively called a communication device, 110a and 110b in FIG. 5 can be called a communication device with a base station function, and 120a-120j in FIG. 5 can be called a communication device with a terminal function.
  • the communication between the base station and the terminal, between the base station and the base station, and between the terminal and the terminal can be carried out through the licensed spectrum, the communication can also be carried out through the unlicensed spectrum, and the communication can also be carried out through the licensed spectrum and the unlicensed spectrum at the same time; Communications may be performed on frequency spectrums below megahertz (gigahertz, GHz), or communications may be performed on frequency spectrums above 6 GHz, or communications may be performed using both frequency spectrums below 6 GHz and frequency spectrums above 6 GHz.
  • the embodiments of the present application do not limit the frequency spectrum resources used for wireless communication.
  • the functions of the base station may also be performed by modules (such as chips) in the base station, or may be performed by a control subsystem including the functions of the base station.
  • the control subsystem including base station functions here may be the control center in the above application scenarios such as smart grid, industrial control, intelligent transportation, and smart city.
  • the functions of the terminal may also be performed by a module (such as a chip or a modem) in the terminal, or may be performed by a device including the terminal function.
  • FIG. 5 is only an example of some communication scenarios to which the technical solution of the present application can be applied, rather than a specific limitation, and there may actually be other scenarios.
  • the number of base stations and the number of terminals in FIG. 5 are only examples, and the present application does not limit the number of base stations and terminals.
  • an index may be used instead of SO.
  • FIG. 6A it is a flow chart of a communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the RLC entity of the first communication device obtains the RLC SDU from the upper layer entity.
  • the first communication device may be any device in the scenario shown in FIG. 5 , such as a base station, or a terminal, which is not limited in this application.
  • the upper layer entity may be a PDCP entity.
  • the RLC entity of the first communication device obtains the RLC SDU from the PDCP entity can also be said to be that the RLC entity of the first communication device obtains the PDCP PDU from the PDCP entity.
  • the RLC entity of the first communication device generates an RLC PDU according to the RLC SDU.
  • the RLC entity of the first communication device may segment the RLC SDU to generate multiple RLC SDU segments, and then add an RLC header to each segment to finally form multiple RLC PDUs.
  • Each RLC PDU includes a header and data.
  • the data of each RLC PDU is a segment in the data of the RLC SDU.
  • the header of each RLC PDU includes SN and index, where SN is used for identification
  • the RLC SDU that is, the data of the RLC PDU is part of the data of the RLC SDU, for details, please refer to the definition of SN above
  • the index is used to identify the segment corresponding to each RLC PDU (that is, each RLC PDU PDU data) number in the segment of the RLC SDU, where different segments in the RLC SDU correspond to different indexes.
  • the data of the first RLC PDU is the first segment in the data of the RLC SDU
  • the first index in the header of the first RLC PDU is used to identify that the data of the first RLC PDU is the first segment of the RLC SDU.
  • the first segment in the segment of the SDU is used for identification
  • segment 1 becomes RLC PDU1 after the RLC header is added, the SN carried in it is 1, and the index value is 00 (indicating that the data in RLC PDU1 is the first segment in the RLC SDU with SN 1); Segment 2 is added After the RLC header becomes RLC PDU2, the SN carried in it is 1, and the index value is 01 (indicating that the data in RLC PDU2 is the second segment in the RLC SDU with SN being 1); after adding the RLC header, segment 3 becomes RLC PDU3, the SN carried in it is 1, and the index value is 10 (indicating that the data in RLC PDU3 is the third segment in the RLC SDU with SN of 1); segment 4 becomes RLC PDU4 after adding the RLC header, where The carried SN is 1, and the index value is 11 (indicating that the data
  • the RLC entity of the first communication device sends the RLC PDU, and correspondingly, the RLC entity of the second communication device receives the RLC PDU;
  • the process of sending the RLC PDU by the RLC entity of the first communication device includes: the entity of the RLC layer transmits the RLC PDU to the MAC for processing to obtain the MAC PDU, the MAC entity transmits the MAC PDU to the PHY entity, and finally the PHY entity encodes the PDU from Sent out over the air.
  • the process of sending the RLC PDU by the RLC entity of the first communication device includes: the entity of the RLC layer transmits the RLC PDU to the MAC for processing to obtain the MAC PDU, the MAC entity transmits the MAC PDU to the PHY entity, and finally the PHY entity encodes the PDU from Sent out over the air.
  • the process of receiving the RLC PDU by the RLC entity of the second communication device includes: the PHY entity of the second communication device decodes the received data packet to obtain the MAC PDU, the PHY entity transmits the MAC PDU to the MAC entity, and the MAC entity The PDU is unpacked to obtain the RLC PDU, and the MAC entity passes the RLC PDU to the RLC entity. It should be understood that if there are multiple RLC PDUs, the multiple RLC PDUs are sent in sequence.
  • the RLC entity of the second communication device determines according to the SN and the first index that the data of the RLC PDU is the first segment in the segments of the RLC SDU.
  • the second communication device is any device that can communicate with the first communication device.
  • the first communication device is any base station in the scene shown in FIG.
  • the RLC entity of the second communication device can determine according to the SN of each RLC PDU that the data of the RLC PDU is a segment of the RLC SDU, and determine which segment of the RLC SDU the data of the RLC PDU is according to the index.
  • index can also be defined as other names, such as segment identification, segment number, etc., as long as it can be used to identify which segment in the RLC SDU the data of the RLC PDU is.
  • the value of the first index does not exceed the threshold, in other words, the overhead corresponding to the first index does not exceed preset bits.
  • the value of the first index can be 0 to 15, and the corresponding binary representation is "1111", and the first index occupies at most 4 bits.
  • the RLC entity of the first communication device can count (accumulate or decrement) the corresponding RLC SDU of each segment when the RLC SDU is segmented, and accumulate or decrement once per segment. Decrement (+1 or -1), for each segment to be transmitted, if the count has reached the maximum value (corresponding to accumulation) or 0 (corresponding to decrement), for example, 15 segments have been obtained, that is, 16 have been obtained When segmenting, the segmenting is not continued, so as to ensure that the value of the first index does not exceed the threshold.
  • the network device needs to indicate which one to use Protocol stack (or which RLC PDU format) for data transmission.
  • the first communication device in the embodiment shown in FIG. 6A is a terminal
  • the terminal sends a data packet based on the method shown in FIG.
  • the RLC PDU format shown is for data transmission
  • the network device parses the data sent by the terminal device based on the RLC PDU format shown in 6B.
  • the two communicating devices can be guaranteed to reach a consistent RLC PDU format to ensure the reliability of the communication.
  • the RLC entity may support a non-segmentation function (that is, the RLC PDU may not carry SO).
  • FIG. 7 it is a flow chart of another communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the RLC entity of the first communication device obtains the RLC SDU from the upper layer entity
  • step S71 For the specific implementation of step S71, reference may be made to the relevant introduction in S61 above, which will not be repeated here.
  • the RLC entity of the first communication device determines that the RLC SDU is not segmented according to the configuration information, where the configuration information is used to indicate that the RLC SDU is not segmented.
  • the configuration granularity of configuration information includes but is not limited to the following situations:
  • the configuration granularity of the configuration information is determined by the data radio bearer (DRB).
  • the configuration information may indicate that the RLC SDU corresponding to each DRB is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first DRB is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second DRB is segmented.
  • the RLC SDU acquired by the RLC entity of the first communication device from the upper layer entity corresponds to the first DRB, then according to the configuration information corresponding to the first DRB, it can be known that the RLC SDU is not segmented.
  • the configuration granularity of the configuration information is determined by the quality of service (QoS) flow.
  • the configuration information may indicate whether the RLC SDU corresponding to each QoS flow is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first QoS flow is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second QoS flow is segmented.
  • the RLC SDU obtained by the RLC entity of the first communication device from the upper layer entity corresponds to the first QoS flow, then according to the configuration information corresponding to the first QoS flow, it can be known that the RLC SDU is not segmented.
  • the configuration granularity of the configuration information is determined by the PDU session.
  • the configuration information may indicate whether the RLC SDU corresponding to each PDU session is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first PDU session is not segmented, and of course the configuration information may also indicate the RLC SDU segment corresponding to the second PDU session.
  • the RLC SDU obtained by the RLC entity of the first communication device from the upper layer entity corresponds to the first PDU session, then according to the configuration information corresponding to the first PDU session, it can be known that the RLC SDU is not segmented.
  • the configuration granularity of the configuration information is determined by the network slice.
  • the configuration information may indicate whether the RLC SDU corresponding to each network slice is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first network slice is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second network slice is segmented.
  • the RLC SDU obtained by the RLC entity of the first communication device from the upper layer entity corresponds to the first network slice, and then according to the configuration information corresponding to the first network slice, it can be known that the RLC SDU is not segmented.
  • the configuration granularity of the configuration information is determined by the logical channel identifier.
  • the configuration information may indicate that the RLC SDU corresponding to each logical channel identifier is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first logical channel identifier is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second logical channel identifier is segmented.
  • the RLC SDU obtained by the RLC entity of the first communication device from the upper layer entity corresponds to the first logical channel identifier, and then according to the configuration information corresponding to the first logical channel identifier, it can be known that the RLC SDU is not segmented.
  • the configuration information may indicate whether the corresponding RLC SDU of each terminal is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first terminal is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second terminal is segmented.
  • the first communication device is the first terminal, then according to the configuration information corresponding to the first terminal, it can be known that the RLC SDU is not segmented.
  • the configuration granularity of the configuration information is determined by the RLC entity.
  • the configuration information may indicate whether the RLC SDU corresponding to each RLC entity is/is not segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first RLC entity is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second RLC entity is segmented.
  • the RLC entity in S71 is the first RLC entity, then according to the configuration information corresponding to the first RLC entity, it can be known that the RLC SDU is not segmented.
  • the configuration information can indicate whether the RLC SDU (ie PDCP PDU) corresponding to each PDCP entity is segmented or not.
  • the configuration information may indicate that the RLC SDU corresponding to the first PDCP entity is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second PDCP entity is segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first PDCP entity is not segmented, and of course the configuration information may also indicate that the RLC SDU corresponding to the second PDCP entity is segmented.
  • the configuration information may indicate that the RLC SDU corresponding to the first PDCP entity is not segmented.
  • the RLC SDU obtained by the RLC entity of the first communication device from the upper layer entity corresponds to the first QoS flow in the first PDU session
  • the RLC entity of the first communication device configures the information according to the first QoS flow in the first PDU session It is determined that the RLC SDU is not fragmented.
  • DRB configuration granularity
  • the configuration information used to indicate that the RLC SDU is not segmented includes but is not limited to the following two:
  • the configuration information carries first indication information, where the first indication information is used to indicate that the service type is a preset service.
  • the protocol stipulates or the first communication device and the second communication device agree that the RLC SDU corresponding to the URLLC service is not segmented, and the RLC SDU corresponding to the eMBB service can be segmented. If the first indication information specifically indicates that the service type carried by the first DRB is URLLC service, the RLC entity of the first communication device determines that the RLC SDU corresponding to the first DRB is not segmented. It should be understood that this is only an example rather than a specific limitation. In actual application, the protocol also stipulates that the RLC SDUs corresponding to other service types are not segmented, or the first communication device and the second communication device can also agree on the RLC SDU corresponding to other service types. RLC SDUs are not fragmented.
  • the configuration information carries second indication information, where the second indication information is used to indicate that the RLC SDU is not segmented.
  • the configuration information corresponding to each DRB carries the first field, which is used to indicate the on/off (on/off) of the segmentation function of the RLC SDU corresponding to the DRB, for example, a value of 1 indicates the segmentation function Enabled, a value of 0 indicates that the segmentation function is disabled. If the value of the first field carried in the configuration information corresponding to the first DRB is 0, the RLC entity of the first communication device determines that the RLC SDU corresponding to the first DRB is not segmented .
  • the configuration information carries third indication information, where the third indication information is used to indicate that the maximum number of segments allowed for the RLC SDU is 0 or 1.
  • the maximum segmentable number is 0, which can be understood as no segmentation, that is, only one RLC PDU is generated according to the RLC SDU; the maximum segmentable number is 1, which can be understood as only one segment is generated, so according to the RLC SDU Only one RLC PDU is generated. Therefore, no matter which description is used, the final effect is the same.
  • the maximum number of segments allowed for an RLC SDU is 0 as an example.
  • the value of N may not be 0, and correspondingly, the RLC entity of the first communication device also handles it differently.
  • the following RLC PDU part performs segmentation operation, fills the RLC header for the obtained segment, and generates the third RLC PDU, corresponding counter + 1, counter
  • the configuration information may be generated by the first communication device, and the first communication device may also send the configuration information to the terminal, so that the terminal communicates with the network device according to the configuration information .
  • the first communication device may obtain the configuration information from the network device, for example, the network device generates the configuration information and sends the configuration information, and the terminal receives the configuration information sent by the network device.
  • the RLC entity of the first communication device generates an RLC PDU according to the RLC SDU.
  • the data that generates the RLC PDU is a complete RLC SDU.
  • the format of generating the RLC PDU can refer to Figure 3A, Figure 3B or Figure 3C.
  • the RLC entity of the first communication device sends the RLC PDU, and correspondingly, the RLC entity of the second communication device receives the RLC PDU.
  • step S74 For the specific implementation of step S74, reference may be made to the relevant introduction in S63 above, and details will not be repeated here.
  • the RLC entity of the second communication device determines, according to the configuration information, that the data of the RLC PDU is a complete RLC SDU.
  • the RLC entity configuration corresponding to the DRB may support TM mode configuration (that is, the RLC PDU may not carry SN and SO).
  • FIG. 8A it is a flowchart of another communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the first communication device acquires configuration information of the radio bearer, where the configuration information is used to indicate that the transmission mode of the RLC entity corresponding to the radio bearer is TM;
  • the first communication device may be any device in the scenario shown in FIG. 5 , such as a base station, or a terminal, which is not limited in this application.
  • the radio bearer refers to a channel used to carry data transmission in layers such as SDAP/PDCP/RLC/MAC/PHY (where the PHY layer is optional).
  • the radio bearer can be divided into various types according to the content of the bearer, such as including but not limited to: 1), DRB, that is, the content of the radio bearer is data; 2), signaling radio bearer (radio bearer, SRB), that is, bearer 3) computing radio bearer (computing radio bearer, CRB), that is, the content of the bearer is computing resources, such as the processing capability of the CPU.
  • the current NR protocol stipulates that the RLC entity configuration corresponding to DRB can only support AM (referred to as RLC AM mode) or UM (referred to as RLC AM mode), and the configuration content is as follows:
  • the RLC entity configuration corresponding to the DRB can also support TM (RLC TM mode for short), and the configuration content is as follows:
  • the configuration information of DRB is as follows:
  • the part in bold above indicates the configuration corresponding to the RLC TM mode.
  • the configuration information may be generated by a network device and sent to other devices (such as other network devices or terminals).
  • the first communication device if the first communication device is a terminal and the second communication device is a base station, the second communication device generates configuration information and sends it to the first communication device.
  • the first communication device obtains configuration information of radio bearers as follows: first The communication device receives configuration information from the second communication device; or for example, the first communication device is a base station and the second communication device is a terminal, then the first communication device generates configuration information and sends it to the second communication device, correspondingly, the first communication device Acquiring the configuration information of the radio bearer by the device specifically includes: generating the configuration information by the first communication device.
  • the network device may carry the configuration information in RRC layer signaling, or in PDCP layer signaling or MAC layer signaling, which is not limited in this application.
  • the first communication device configures the transmission mode of the RLC entity corresponding to the radio bearer as TM.
  • TM means that the sending entity does not add any additional control protocol overhead to the high-level data. Therefore, after the RLC entity of the first communication device obtains the RLC SDU from the upper entity, it does not add any control information and directly Using the entire RLC SDU as an RLC PDU or each segment of the RLC SDU as an RLC PDU, the generated RLC PDU has only data, as shown in Figure 8B.
  • RLC TM can not only be used for public channels such as paging/system information block (SIB), but also can be configured with a single DRB or SRB or CRB to support RLC TM mode for point-to-point data transmission. , thereby effectively reducing the header overhead of RLC PDUs and saving air interface overhead.
  • SIB paging/system information block
  • the functions of the RLC layer can be merged into other layers, so as to save all RLC header overheads of the RLC layer.
  • FIG. 9A it is a flow chart of another communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the PDCP entity of the first communication device acquires the PDCP SDU.
  • the first communication device may be any device in the scenario shown in FIG. 5 , such as a base station, or a terminal, which is not limited in this application.
  • the PDCP entity of the first communication device obtains the PDCP SDU from the upper layer entity, for example, the PDCP entity receives the SDAP PDU delivered by the SDAP entity, and uses it as the PDCP SDU.
  • the PDCP entity of the first communication device generates multiple PDCP PDUs according to the PDCP SDUs.
  • each PDCP PDU includes a header and data, where the data is a segment in the PDCP SDU, the header includes a serial number, and the serial number is used to identify the PDCP SDU (that is, the PDCP SN, the definition can refer to the relevant introduction above),
  • the header also includes SO, which is used to indicate the byte offset of the first byte of the segment in the PDCP SDU.
  • Figure 9B and Figure 9C are schematic diagrams of the format of two possible PDCP data PDUs.
  • the difference from Figure 4A and Figure 4B is that the SI field and the SO field are added to the PDCP header.
  • the meaning of the SO field can refer to the above figure 4A and the introduction in the relevant embodiments of FIG. 4B will not be repeated here.
  • the SI field here is used to further indicate the type (segmentation type) of the PDCP data PDU (ie RLC data PDU), where different values of SI correspond to different PDCP data PDU types.
  • the corresponding meanings can be as follows: 00: PDCP PDU data contains all bytes of PDCP SDU; 01: PDCP PDU data contains the first segment of PDCP SDU; 10: PDCP PDU data contains The last segment of the PDCP SDU; 11: The data of the PDCP PDU neither contains the first segment of the PDCP SDU nor the last segment of the PDCP SDU. It should be understood that this is only an example, and in actual implementation, there may be other implementation manners for the correspondence between SI values and PDCP PDU types.
  • FIG. 9D to FIG. 9F are schematic diagrams of three possible formats of PDCP control PDUs.
  • PDU type is used to indicate the type of PDCP control PDU, for example, Fig. 9D to Fig. 9F respectively exemplify PDCP control PDU of three different PDU types.
  • the PDCP control PDU shown in Figure 9D is used to transmit the user PDCP status report (status report, SR).
  • SR user PDCP status report
  • the PDCP SR corresponding to the uplink data transmission is sent by the gNB to the UE
  • the PDCP SR corresponding to the downlink data transmission is The PDCP SR is sent by the UE to the gNB.
  • FMC is the number of the first unsuccessfully transmitted data packet: a bitmap (bitmap) indicates whether the data packet after the first unsuccessful data packet is successfully transmitted, for example, 1 indicates success, and 0 indicates failure.
  • the PDCP control PDU shown in FIG. 9E is used to transmit feedback information of robust header compression (RObust header compression, ROHC).
  • the PDCP control PDU shown in FIG. 9F is used for feedback information of Ethernet header compression (EHC).
  • the SI field in Figure 9D to Figure 9F is used to further indicate the type (segmentation type) of PDCP control PDU (that is, RLC control PDU).
  • PDCP control PDU that is, RLC control PDU.
  • the SNs in the PDCP control PDU and the SNs in the PDCP data PDU can be numbered consecutively or discontinuously, which is not limited in this application.
  • the PDCP entity of the first communication device sends multiple PDCP PDUs; correspondingly, the PDCP entity of the second communication device receives the multiple PDCP PDUs.
  • the PDCP entity of the first communication device If the PDCP entity of the first communication device performs a segmentation operation on the PDCP SDU, the PDCP entity of the first communication device will sequentially send multiple PDCP PDUs corresponding to the PDCP SDU, and correspondingly, the PDCP entity of the second communication device will receive the PDCP SDU in sequence Corresponding multiple PDCP PDUs. It should be understood that the actual transmission process still needs to be processed by lower-layer entities (such as MAC entities, PHY entities, etc.). For details, refer to the relevant introduction above, and details will not be repeated here.
  • lower-layer entities such as MAC entities, PHY entities, etc.
  • the PDCP entity of the second communication device generates a PDCP SDU according to the multiple PDCP PDUs.
  • the PDCP entity of the second communication device determines that the multiple PDCP PDUs correspond to the same PDCP SDU according to the same SN in the multiple PDCP PDUs, and then determines the multiple PDCP PDUs according to the SO of each PDCP PDU in the multiple PDCP PDUs. PDUs are combined in sequence into a complete PDCP SDU.
  • the RLC layer also supports the function of not segmenting the RLC SDU, so the function of the RLC layer supporting the non-segmentation of the RLC SDU can also be incorporated into the PDCP layer, which will not be described in detail here.
  • the PDCP entity of the first communication device may directly deliver the PDCP PDU to the MAC layer.
  • the PDCP entity of the second communication device can directly obtain the PDCP PDU from the MAC entity.
  • the PDCP entity of the first communication device can also send the PDCP PDU to the RLC entity first, and the RLC entity can directly deliver the PDCP PDU to the MAC entity without any processing, and the MAC entity of the second communication device
  • the MAC SDU can also be delivered to the RLC entity, and the RLC entity can directly deliver the MAC SDU (that is, the PDCP PDU) to the PDCP entity without any processing.
  • the above is an example of combining the functions of the RLC layer into the PDCP layer.
  • the functions of the RLC layer may also be combined into other layers (such as RRC layer, MAC layer, etc.), which is not limited in this application.
  • the PDCP entity may support TM, thereby saving all PDCP header overhead at the PDCP layer.
  • the PDCP data PDU also carries additional PDCP header overhead: 6bytes and 7bytes (if the full protection function is enabled), or 2bytes and 3bytes (if the full protection function off).
  • This embodiment mainly discusses the saving of PDCP header overhead by PDCP data PDU, which is divided into the following two situations: 1) D/C, PDCP SN: If the PDCP data PDU does not carry the PDCP SN, it means that the PDCP encryption function is not supported at all (because the current PDCP encryption relies on PDCP SN as input); if the PDCP data PDU does not carry D/C, it means that the related PDCP Control PDU cannot be transmitted in the same PDCP entity (because the existing technology uses the D/C field to indicate that the type of PDCP PDU is PDCP data PDU or PDCP Control PDU); 2) MAC-I: If the PDCP data PDU does not carry MAC-I, it means that the full protection function is always not supported.
  • the embodiment of the present application designs a new type of PDCP PDU format to support the TM of the PDCP entity (referred to as PDCP TM).
  • PDCP TM the TM of the PDCP entity
  • the specific format is shown in Figure 10A. Add any additional protocol overhead out of control.
  • the DRB configuration in this embodiment can support PDCP TM, which will not be described in detail here.
  • the PDCP PDU transmitted by the PDCP entity cannot carry the D/C field, if the PDCP data PDU and PDCP control PDU originally transmitted by the PDCP entity are in the PDCP entity at the same time For transmission, the PDCP data PDU and PDCP control PDU cannot be distinguished, so the PDCP data PDU and PDCP control PDU originally transmitted by the PDCP entity cannot be transmitted within the PDCP entity at the same time.
  • the following method provided by this embodiment can realize the separate transmission of PDCP data PDU and PDCP control PDU, thereby saving the header overhead of PDCP data PDU and distinguishing between PDCP data PDU and PDCP control PDU.
  • FIG. 10B it is a flow chart of another communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the first PDCP entity of the first communication device sends a PDCP data PDU; correspondingly, the fifth PDCP entity of the second communication device receives the PDCP data PDU sent by the first PDCP entity of the first communication device.
  • the first communication device may be any device in the scenario shown in FIG. 5 , such as a base station, or a terminal, which is not limited in this application.
  • the second communication device is another device capable of communicating with the first communication device, such as a terminal, or such as a base station, which is not limited in this application.
  • the second PDCP entity of the first communication device sends a PDCP control PDU, and correspondingly, the sixth PDCP entity of the second communication device receives the PDCP control PDU sent by the second PDCP entity of the first communication device.
  • the PDCP data PDU sent by the first PDCP entity is associated with the PDCP control PDU sent by the second PDCP entity, and the first PDCP entity is different from the second PDCP entity.
  • the PDCP data PDU received by the fifth PDCP entity is associated with the PDCP control PDU received by the sixth PDCP entity, and the fifth PDCP entity is different from the sixth PDCP entity.
  • the first PDCP entity is used to send PDCP data PDU instead of PDCP control PDU; the second PDCP entity is used to send PDCP control PDU instead of PDCP data PDUs.
  • the fifth PDCP entity is used to receive PDCP data PDUs instead of PDCP control PDUs; the sixth PDCP entity is used to receive PDCP control PDUs instead of PDCP data PDUs.
  • the realization of the first communication device side corresponds to the realization of the second communication device side
  • the specific realization of the second communication device side can refer to the specific implementation of the first communication device side. accomplish.
  • the PDCP data PDU sent by the first PDCP entity is associated with the PDCP control PDU sent by the second PDCP entity, which means: the PDCP control PDU sent by the second PDCP entity is used to control the transmission of the PDCP data PDU sent by the first PDCP entity, or in other words,
  • the PDCP data PDU sent by the first PDCP entity and the PDCP control PDU sent by the second PDCP entity should originally be transmitted in the same PDCP entity, but they are separated and transmitted on two different PDCP entities.
  • the PDCP control PDU sent by the first PDCP entity is associated with the PDCP data PDU sent by the second PDCP entity, which can also be described as the association between the first PDCP entity and the second PDCP entity.
  • the PDCP entity used to transmit PDCP data PDUs may be referred to as a data (data) PDCP entity hereinafter
  • the PDCP entity used to transmit PDCP control PDUs may be referred to as a control (control) PDCP entity hereinafter.
  • the first communication device may acquire configuration information.
  • the configuration information can be used to indicate which PDCP entities the PDCP data PDU transmission entity is separated from the PDCP control PDU transmission entity.
  • the configuration information can also be used to indicate which PDCP entities are data PDCP entities (that is, used to send PDCP data PDUs), which PDCP entities are control PDCP entities (that is, used to send PDCP control PDUs), and data PDCP entities and control PDCP entity association relationship.
  • the first communication device may determine according to the configuration information: which PDCP entities have the PDCP data PDU transmission entities separated from the PDCP control PDU transmission entities, which PDCP entities are data PDCP entities, which PDCP entities are control PDCP entities, and data Association relationship between PDCP entity and control PDCP entity, etc.
  • the specific way for the first communication device to obtain configuration information for example, if the first communication device is a network device and the second communication device is a terminal, then the first communication device can generate configuration information, and can also send the configuration information to the second communication device or for example, if the first communication device is a terminal and the second communication device is a network device, then the second communication device may generate configuration information, and the first communication device receives configuration information from the second communication device.
  • the configuration granularity of the configuration information may be determined by the PDCP entity, that is, one PDCP entity corresponds to one piece of configuration information.
  • the configuration information may include:
  • the first configuration information may specifically carry:
  • the first indication information is used to indicate: the transmission entity of the PDCP data PDU of the first PDCP entity is separated from the transmission entity of the PDCP control PDU, or the transmission mode of the first PDCP entity is TM.
  • the first configuration information may explicitly indicate that the transmission entity of the PDCP data PDU of the first PDCP entity is separated from the transmission entity of the PDCP control PDU, that is, the first configuration information directly indicates the transmission entity of the PDCP data PDU of the first PDCP entity and the PDCP control PDU The transport entities are separated.
  • the first configuration information may also implicitly indicate that the transmission entity of the PDCP data PDU is separated from the transmission entity of the PDCP control PDU.
  • the first configuration information indicates that the transmission mode of the first PDCP entity is TM, then the first PDCP entity can determine itself according to TM It is only used to transmit PDCP data PDU, so it can be further determined that the transmission entity of its own PDCP data PDU is separated from the transmission entity of PDCP control PDU.
  • the second indication information is used to indicate: the first PDCP entity is used to transmit PDCP data PDU;
  • the fourth indication information is used to indicate that: the PDCP data PDU transmitted by the first PDCP entity is associated with the PDCP control PDU transmitted by the second PDCP entity.
  • the second configuration information may specifically carry:
  • the third indication information is used to indicate that: the second PDCP entity is used to transmit the PDCP control PDU.
  • the fifth indication information is used to indicate that the transmission entity of the PDCP data PDU of the second PDCP entity is separated from the transmission entity of the PDCP control PDU;
  • the PDCP control PDU transmitted by the second PDCP entity is associated with the PDCP data PDU transmitted by the first PDCP entity.
  • the configuration information may only carry some but not all of the above six types of information, for example: the first indication information, the second indication information, and the fourth indication information have been carried in the first configuration information
  • the second configuration information does not need to carry the fifth indication information and the sixth indication information; on the contrary, if the second configuration information already carries the third indication information, the fifth indication information, and the sixth indication information, the sixth indication information
  • the second configuration information may not carry the first indication information and the fourth indication information, which can save configuration overhead.
  • the above various indication information may be multiple information elements (information element, IE), or may be the same information element, which is not limited in this application.
  • the configuration information includes multiple information elements, and each information element corresponds to only one of the above indication information, and different information elements correspond to different indication information; or, for example, the configuration information includes one or more information elements, wherein the first information element can be At the same time, it corresponds to the above at least two kinds of indication information.
  • the association relationship between the data PDCP entity and the control PDCP entity may be a one-to-one association relationship (that is, one data PDCP entity is associated with one control PDCP entity, and different data The PDCP entity is associated with different control PDCP entities).
  • the first PDCP entity of the first communication device sends the first PDCP data PDU;
  • the second PDCP entity of the first communication device sends the first PDCP control PDU;
  • the third PDCP entity of the first communication device sends the second PDCP data PDU ;
  • the fourth PDCP entity of the first communication device sends a second PDCP control PDU.
  • the first PDCP control PDU is associated with the first PDCP data PDU
  • the second PDCP control PDU is associated with the second PDCP data PDU
  • any two of the third PDCP entity, the fourth PDCP entity, the first PDCP entity, and the second PDCP entity entities are different.
  • the association relationship between the data PDCP entity and the control PDCP entity may also be a many-to-one association relationship (that is, multiple data PDCP entities are associated with the same control PDCP entity).
  • the first PDCP entity of the first communication device sends the first PDCP data PDU; the second PDCP entity of the first communication device sends the first PDCP control PDU; the third PDCP entity of the first communication device sends the second PDCP data PDU ;
  • the second PDCP entity of the first communication device sends a second PDCP control PDU.
  • the first PDCP control PDU is associated with the first PDCP data PDU
  • the second PDCP control PDU is associated with the second PDCP data PDU
  • any two entities among the third PDCP entity, the first PDCP entity, and the second PDCP entity are different.
  • the configuration information of each PDCP entity can refer to the above configuration information of the first PDCP entity or the second PDCP entity, which will not be repeated here.
  • the network device can also configure the control PDCP entity to carry in the PDCP control PDU the identifier of the data PDCP entity corresponding to the PDCP control PDU and/or The ID of the PDCP data PDU corresponding to the PDCP control PDU, so that the receiving end can distinguish different PDCP control PDUs in the same control PDCP entity.
  • the first PDCP entity of the first communication device sends the first PDCP data PDU; the second PDCP entity of the first communication device sends the first PDCP control PDU; the third PDCP entity of the first communication device sends the second PDCP data PDU; the second PDCP entity of the first communication device sends the second PDCP control PDU
  • the first PDCP control PDU can carry the identity of the first PDCP entity or the identity of the first PDCP data PDU
  • the second PDCP control PDU may carry the identifier of the third PDCP entity or the identifier of the second PDCP data PDU.
  • the second communication device receives the first PDCP data PDU, the first PDCP control PDU, the second PDCP data PDU, and the second PDCP control PDU, it can The identification or the identification of the first PDCP data PDU determines that the first PDCP control PDU is associated with the first PDCP data PDU, and determines the second PDCP entity according to the identification of the third PDCP entity carried in the second PDCP control PDU or the identification of the second PDCP data PDU.
  • the PDCP control PDU is associated with a second PDCP data PDU.
  • the PDCP data PDU and PDCP control PDU are decoupled and sent through different PDCP entities, so that the PDCP entity can send PDCP data PDUs in TM mode, thereby reducing the header overhead of PDCP data PDUs and saving air interface overhead.
  • FIG. 10C it is a flow chart of another communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the first PDCP entity of the first communication device sends the first PDCP data PDU, and correspondingly, the second PDCP entity of the second communication device receives the first PDCP data PDU sent by the first PDCP entity of the first communication device.
  • the entity of the RRC/NAS/SDAP/RLC/MAC/PHY layer of the first communication device sends the first PDCP control PDU, and correspondingly, the non-PDCP layer (such as RRC/NAS/SDAP/RLC/MAC) of the second communication device /PHY layer) entity receives the first PDCP control PDU sent by the non-PDCP layer (such as RRC/NAS/SDAP/RLC/MAC/PHY layer) entity of the first communication device.
  • the non-PDCP layer such as RRC/NAS/SDAP/RLC/MAC/PHY layer
  • the first PDCP control PDU is associated with the first PDCP data PDU.
  • the meaning of the association between the first PDCP control PDU and the first PDCP data PDU here can refer to the relevant introduction above, and will not be repeated here.
  • the PDCP control PDU needs to carry the corresponding PDCP entity identifier and/or the corresponding PDCP The identification of the data PDU in order to distinguish different PDCP control PDUs in entities of the same RRC/NAS/SDAP/RLC/MAC/PHY layer.
  • the PDCP data PDU is decoupled from the PDCP control PDU, and the PDCP control PDU is sent through other layer entities, so that the PDCP entity can use the TM mode to send the PDCP data PDU, thereby reducing the header overhead of the PDCP data PDU and saving air interface overhead.
  • the PDCP entity and the RLC entity can support TM at the same time, so as to save all header overheads of the PDCP layer and the RLC layer.
  • both the PDCP entity and the RLC entity support TM, neither the PDCP data PDU nor the RLC data PDU carries SN and SO. This will lead to the loss of some functions of the PDCP layer and the RLC layer, such as but not limited to the following functions: 1) PDCP encryption and decryption: because both encryption and decryption need to rely on the PDCP SN (that is, the SN in the PDCP header) as input, if Without PDCP SN, PDCP SN cannot be completed; 2) PDCP reordering and in-order delivery (Reordering and in-order delivery): because the receiving end PDCP entity needs to reorder according to PDCP SN and deliver it to the upper layer entity in order, If there is no PDCP SN, reordering and sequential delivery cannot be completed; 3) PDCP duplicate discarding (Duplicate discarding): because the PDCP entity at the receiving end needs to judge whether different PDCP PDUs are the same data packet according to the
  • the following method provided by this embodiment can realize that both the PDCP entity and the RLC entity support TM, and at the same time, the receiving end can obtain the SN corresponding to the PDCP data PDU and the RLC data PDU.
  • FIG. 11A it is a flow chart of another communication method provided by the embodiment of the present application.
  • the method is applied to the application scenario shown in FIG. 5 as an example.
  • the flow of this method is described as follows:
  • the second communication device determines the time domain position corresponding to the data packet according to the mapping relationship between the SN and the time domain position (or time domain range) and the SN corresponding to the data packet; wherein, the PDCP entity and the RLC entity of the second communication device
  • the transmission modes are all TM.
  • the second communication device may be any device in the scenario shown in FIG. 5 , such as a base station, or a terminal, which is not limited in this application.
  • the data packet may be a data packet delivered by the upper entity of the PDCP layer of the second communication device, for example, a data packet delivered by the SDAP layer, that is, a PDCP SDU.
  • the operation of determining the time domain position corresponding to the data packet according to the mapping relationship between the SN and the time domain position and the SN corresponding to the data packet may be performed by an entity corresponding to any protocol layer on the second communication device.
  • the PDCP entity of the second communication device transmits the SN corresponding to the data packet to the MAC entity of the second communication device, and then the MAC entity of the second communication device determines the data The time domain position corresponding to the packet.
  • the PDCP entity of the second communication device determines the time domain position corresponding to the data packet according to the mapping relationship between the SN and the time domain position and the SN corresponding to the data packet, and then the PDCP entity of the second communication device sends the MAC address of the second communication device The entity transmits the time domain position corresponding to the data packet.
  • this operation may also be performed by other layers (such as the RLC layer), which is not specifically limited in this application.
  • the second communication device sends the data packet at the time domain position corresponding to the data packet; correspondingly, the first communication device receives the data packet at the time domain position; wherein, the transmission mode of the PDCP entity and the RLC entity of the first communication device Both are TM.
  • the actual transmission process also includes the processing process of other layers (such as MAC layer, PHY layer, etc.).
  • processing process of other layers you can refer to the relevant description above, and will not repeat them here.
  • the second communication device may discard the data packet, that is, no longer send it, so as to prevent the data packet from falling in the time domain position corresponding to other data packets and causing confusion to the first communication device.
  • the first communication device determines the SN corresponding to the data packet according to the time domain position at which the data packet is received and the mapping relationship between the SN and the time domain position.
  • the first communication device may be any device capable of communicating with the second communication device, such as a base station, or a terminal, which is not limited in this application.
  • the operation of determining the SN corresponding to the data packet according to the time domain position of the received data packet and the mapping relationship between the SN and the time domain position may be performed by an entity corresponding to any protocol layer on the first communication device.
  • the MAC entity of the first communication device transmits the time domain position of the data packet to the PDCP entity of the first communication device, and then the PDCP entity of the first communication device receives the time domain position of the data packet according to the MAC entity, the SN and the time domain position.
  • the mapping relationship determines the SN corresponding to the data packet.
  • the MAC entity of the first communication device determines the SN corresponding to the data packet according to the time domain position of the received data packet and the mapping relationship between the SN and the time domain position, and then the MAC entity of the first communication device sends the PDCP entity of the first communication device The SN corresponding to the delivery data packet.
  • this operation may also be performed by other layers (such as the RLC layer), which is not specifically limited in this application.
  • the SN can be used as the PDCP SN to perform other PDCP operations, such as PDCP decryption, PDCP reordering etc.
  • the network device can configure the mapping relationship between the serial number and the time domain position. For example, if the second communication device is a network device and the first communication device is a terminal, the second communication device configures the mapping relationship between the serial number and the time domain position, and sends the mapping relationship between the serial number and the time domain position to the first communication device The device, and then the second communication device sends the data packet according to the mapping relationship, and the first communication device receives the data packet according to the mapping relationship. Or for example, if the second communication device is a terminal and the first communication device is a network device, the first communication device configures the mapping relationship between the serial number and the time domain position, and sends the mapping relationship between the serial number and the time domain position to the second communication device. The communication device, and furthermore, the second communication device sends the data packet according to the mapping relationship, and the first communication device receives the data packet according to the mapping relationship.
  • the configuration granularity of the time-domain position can be at least one of a system frame number (System frame number, SFN), a subframe number (subframe number), a slot number (slot number) or a symbol (symbol number), etc.
  • SFN System frame number
  • subframe number subframe number
  • slot number slot number
  • symbol number symbol
  • the time domain position or time domain range corresponding to a data packet can be described as a transmission time interval (transmission time interval, TTI).
  • TTI transmission time interval
  • the base station sends data packet 1, data packet 2, and data packet 3 at TTI-1, TTI-2, and TTI-3 respectively.
  • the retransmission timing of the data packet is also within the TTI range corresponding to the data packet.
  • Figure 11B exemplifies a single-carrier scenario, and this application can also be applied to dual-carrier or multi-carrier scenarios, for example, as shown in Figure 11C, the base station sends data on component carrier (CC) 1 and CC2 in TTI-1 Packet 1; the base station sends data packet 2 on CC1 and CC2 in TTI-2; the base station sends data packet 3 on CC1 and CC2 in TTI-3.
  • CC component carrier
  • mapping relationship between the SN and the time domain position is an example of the mapping relationship between the SN and the time domain position.
  • the SO and the time domain position may also be mapped.
  • the first communication device according to the SO and time domain The mapping relationship of the location and the time of receiving the segment determine the SO corresponding to each segment.
  • both the PDCP entity and the RLC entity can support TM, and at the same time, the first communication device can obtain the SN corresponding to the PDCP data PDU and the RLC data PDU, thereby saving air interface overhead and ensuring the reliability of data transmission.
  • the above-mentioned embodiments provided in the present application may be implemented independently or in combination with each other.
  • the solution shown in FIG. 6A above can be combined with the solution shown in FIG. 9A , that is, the SO in the PDCP layer can be replaced by an index, which can further save air interface overhead.
  • the above schemes shown in Figure 8A, Figure 10B and Figure 11A can be implemented in combination, then both the PDCP layer and the RLC layer can support the TM mode (both do not carry SN), and at the same time ensure that the receiving end can obtain the corresponding SN of the data packet .
  • the above are only examples of some combinations, and there may be more combinations in practical applications, which will not be described in detail here.
  • each communication device includes a corresponding hardware structure and/or software module for performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of the examples described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.
  • FIG. 12 and FIG. 13 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication devices can be used to realize the functions in the foregoing method embodiments, and thus can also realize the beneficial effects possessed by the foregoing method embodiments.
  • the communication device may be one of the terminals 120a-120j shown in FIG. 5, or the base station 110a or 110b shown in FIG. 5, or a module applied to the terminal or the base station (such as chips).
  • the transceiver module 1201 is used for: obtaining RLC SDU;
  • the processing module 1202 is used for: generating RLC PDU according to RLC SDU; Wherein, RLC PDU comprises header and data, and data is the first segmentation in the data of RLC SDU, and header comprises serial number and first index, and serial number is used for Identify the RLC SDU, the first index is used to identify the number of the first segment in the segment of the RLC SDU, and the different segments in the RLC SDU correspond to different indices;
  • the transceiver module 1201 is also used for: sending RLC PDU.
  • the transceiver module 1201 is used for: receiving RLC PDU; Wherein, RLC PDU comprises header and data, and data is the first segmentation of RLC SDU, and header comprises serial number and first index, and serial number is used for identifying RLC SDU, and first The index is used to identify the number of the first segment in the segment of the RLC SDU, and different segments in the RLC SDU correspond to different indices;
  • the processing module 1202 is configured to: determine according to the sequence number and the first index that the data of the RLC PDU is the first segment in the segments of the RLC SDU.
  • processing module 1202 and the transceiver module 1201 can be directly obtained by referring to the relevant descriptions in the method embodiment shown in FIG. 6A , and will not be repeated here.
  • the processing module 1202 is used to: obtain the RLC SDU; determine that the RLC SDU is not segmented according to the configuration information, wherein the configuration information is used to indicate that the RLC SDU is not segmented; generate an RLC PDU according to the RLC SDU; wherein, the data of the RLC PDU is a complete RLC SDUs;
  • the transceiver module 1201 is used for: sending RLC SDU.
  • the transceiver module 1201 is used for: receiving RLC PDU;
  • the processing module 1202 is configured to: determine that the data of the RLC PDU is a complete RLC SDU according to the configuration information.
  • processing module 1202 and the transceiver module 1201 can be directly obtained by referring to the relevant descriptions in the method embodiment shown in FIG. 7 , and will not be repeated here.
  • the transceiver module 1201 is configured to acquire configuration information of the radio bearer, where the configuration information is used to indicate that the transmission mode of the RLC entity corresponding to the radio bearer is a transparent mode;
  • the processing module 1202 is configured to: configure the transmission mode of the RLC entity corresponding to the radio bearer as a transparent mode based on the configuration information.
  • processing module 1202 and the transceiver module 1201 can be directly obtained by referring to related descriptions in the method embodiment shown in FIG. 8A , and details are not repeated here.
  • the processing module 1202 is used to obtain the PDCP SDU; generate a PDCP PDU according to the PDCP SDU; wherein, the PDCP PDU includes a header and data, the data is a segment in the PDCP SDU, the header includes a sequence number, and the sequence number is used to identify the PDCP SDU , the header also includes a segment offset or index.
  • the segment offset is used to indicate the byte offset of the first byte of a segment in the PDCP SDU, and the index is used to identify a segment in the RLC SDU. the number in the segment;
  • Transceiver module 1201 configured to send PDCP SDU.
  • the transceiver module 1201 is used to: receive multiple RLC PDUs; wherein, each PDCP PDU in the multiple PDCP PDUs includes a header and data, the data is a segment in the PDCP SDU, the header includes a sequence number, and the sequence number is used for Identify the PDCP SDU, the header also includes a segment offset or index, the segment offset is used to indicate the byte offset of the first byte of a segment in the PDCP SDU, and the index is used to identify a segment in The number in the segment of the RLC SDU; among them, the sequence numbers corresponding to multiple PDCP PDUs are the same;
  • the processing module 1202 is configured to: generate a PDCP SDU according to multiple PDCP PDUs.
  • processing module 1202 and the transceiver module 1201 can be directly obtained by referring to related descriptions in the method embodiment shown in FIG. 9A , and details are not repeated here.
  • a processing module 1202 configured to create a first PDCP entity and a second PDCP entity
  • the transceiver module 1201 is configured to send the first PDCP data PDU based on the first PDCP entity; send the first PDCP control PDU based on the second PDCP entity; wherein, the first PDCP control PDU is associated with the first PDCP data PDU, and the first PDCP entity is associated with the first PDCP entity The second PDCP entity is different.
  • a processing module 1202 configured to create a fifth PDCP entity and a sixth PDCP entity
  • the transceiver module 1201 is configured to receive the first PDCP data PDU sent by the first PDCP entity of the first communication device; receive the first PDCP control PDU sent by the second PDCP entity of the first communication device; wherein, the first PDCP control PDU and The first PDCP data PDU is associated, and the first PDCP entity is different from the second PDCP entity;
  • the processing module 1202 is configured to process the first PDCP control PDU based on the fifth PDCP entity, and process the first PDCP data PDU based on the sixth PDCP entity.
  • processing module 1202 and the transceiver module 1201 can be directly obtained by referring to the relevant descriptions in the method embodiment shown in FIG. 10B , and will not be repeated here.
  • a transceiver module 1201 configured to receive data packets; wherein, the transmission modes of the PDCP entity and the RLC entity of the first communication device are both transparent modes;
  • the processing module 1202 is configured to determine the sequence number corresponding to the data packet according to the time domain position of the received data packet and the mapping relationship between the sequence number and the time domain position.
  • the processing module 1202 is configured to determine the time domain position corresponding to the data packet according to the mapping relationship between the sequence number and the time domain position and the sequence number corresponding to the data packet; wherein, the transmission modes of the PDCP entity and the RLC entity of the second communication device are both transparent mode;
  • the transceiver module 1201 is configured to send the first data packet at the time domain position corresponding to the data packet.
  • processing module 1202 and the transceiver module 1201 can be directly obtained by referring to the related descriptions in the method embodiment shown in FIG. 11A , and details are not repeated here.
  • a communication device 1300 includes a processor 1310 and an interface circuit 1320 .
  • the processor 1310 and the interface circuit 1320 are coupled to each other. It can be understood that the interface circuit 1320 may be a transceiver or an input/output interface.
  • the communication device 1300 may further include a memory 1330 for storing instructions executed by the processor 1310 or storing input data required by the processor 1310 to execute the instructions or storing data generated by the processor 1310 after executing the instructions.
  • the processor 1310 is used to realize the functions of the above-mentioned processing module 1202
  • the interface circuit 1320 is used to realize the functions of the above-mentioned transceiver module 1201 .
  • the terminal chip implements the functions of the terminal in the above method embodiment.
  • the terminal chip receives information from other modules in the terminal (such as radio frequency modules or antennas), and the information is sent to the terminal by the base station; or, the terminal chip sends information to other modules in the terminal (such as radio frequency modules or antennas), and the The information is sent by the terminal to the base station.
  • the base station module implements the functions of the base station in the above method embodiment.
  • the base station module receives information from other modules in the base station (such as radio frequency modules or antennas), and the information is sent to the base station by the terminal; or, the base station module sends information to other modules in the base station (such as radio frequency modules or antennas), the The information is sent by the base station to the terminal.
  • the base station module here may be a baseband chip of the base station, or a DU or other modules, and the DU here may be a DU under an open radio access network (O-RAN) architecture.
  • OF-RAN open radio access network
  • an embodiment of the present application also provides a chip, as shown in FIG. 14 , the chip may include logic circuits and input and output interfaces.
  • a memory may also be included.
  • the input-output interface can be used to receive code instructions (the code instructions are stored in the memory, can be read directly from the memory, or can also be read from the memory through other devices) and transmitted to the logic circuit; the logic circuit, It can be used to run the code instructions to execute the methods in the above method embodiments.
  • the input and output interface may also be a signal transmission interface circuit between the logic circuit and the transceiver.
  • the logic circuit is used to execute XX to obtain Y data (XX is a non-air interface operation, including but not limited to determining, judging, processing, calculating, searching, comparing and other operations); the input and output interface It can be used to send Y data to the transmitter (the transmitter is used to perform the transmission operation on the air interface).
  • the input and output interface may be used to receive Z data from a receiver (the receiver is used to perform a receiving operation on an air interface), and send the Z data to the logic circuit; the The logic circuit is used to perform XX processing on the Z data (XX is a non-air interface operation, including but not limited to determining, judging, processing, calculating, searching, comparing and other operations).
  • the logic circuit is used to: obtain the RLC SDU; generate the RLC PDU according to the RLC SDU; wherein, the RLC PDU includes a header and data, the data is the first segment in the data of the RLC SDU, the header includes a sequence number and the first index, and the sequence The number is used to identify the RLC SDU, the first index is used to identify the number of the first segment in the segment of the RLC SDU, and different segments in the RLC SDU correspond to different indices;
  • the input and output interfaces are used to: output RLC PDU.
  • the input and output interfaces are used to: input RLC PDU; wherein, RLC PDU includes header and data, data is the first segment of RLC SDU, header includes serial number and first index, serial number is used to identify RLC SDU, first The index is used to identify the number of the first segment in the segment of the RLC SDU, and different segments in the RLC SDU correspond to different indices;
  • the logic circuit is used to: determine that the data of the RLC PDU is the first segment in the segment of the RLC SDU according to the sequence number and the first index.
  • the logic circuit is used to: obtain the RLC SDU; determine that the RLC SDU is not segmented according to the configuration information, wherein the configuration information is used to indicate that the RLC SDU is not segmented; generate an RLC PDU according to the RLC SDU; wherein, the data of the RLC PDU is a complete RLC SDU ;
  • the input and output interfaces are used to: output RLC SDU.
  • the input and output interfaces are used to: input RLC PDU;
  • the logic circuit is used to: determine that the data of the RLC PDU is a complete RLC SDU according to the configuration information.
  • the input and output interface is used to input the configuration information of the radio bearer, wherein the configuration information is used to indicate that the transmission mode of the RLC entity corresponding to the radio bearer is a transparent mode;
  • the logic circuit is configured to: configure the transmission mode of the RLC entity corresponding to the radio bearer as a transparent mode based on the configuration information.
  • Logic circuit used to input PDCP SDU; generate PDCP PDU according to PDCP SDU; wherein, PDCP PDU includes header and data, data is a segment in PDCP SDU, header includes serial number, and serial number is used to identify PDCP SDU,
  • the header also includes a segment offset or index.
  • the segment offset is used to indicate the byte offset of the first byte of a segment in the PDCP SDU.
  • the index is used to identify the segment offset of a segment in the RLC SDU. the number in the segment;
  • Input and output interface used to output PDCP SDU.
  • the input and output interfaces are used to: input multiple RLC PDUs; among them, each PDCP PDU in multiple PDCP PDUs includes a header and data, the data is a segment in the PDCP SDU, the header includes a sequence number, and the sequence number is used for Identify the PDCP SDU, the header also includes a segment offset or index, the segment offset is used to indicate the byte offset of the first byte of a segment in the PDCP SDU, and the index is used to identify a segment in The number in the segment of the RLC SDU; among them, the sequence numbers corresponding to multiple PDCP PDUs are the same;
  • the logic circuit is used to: generate a PDCP SDU from multiple PDCP PDUs.
  • the input and output interface is used to output the first PDCP data PDU based on the first PDCP entity; output the first PDCP control PDU based on the second PDCP entity; wherein, the first PDCP control PDU is associated with the first PDCP data PDU, and the first PDCP entity is associated with the first PDCP entity
  • the second PDCP entity is different.
  • the input and output interface is used to input the first PDCP data PDU sent by the first PDCP entity of the first communication device; input the first PDCP control PDU sent by the second PDCP entity of the first communication device; wherein, the first PDCP control PDU and The first PDCP data PDU is associated, and the first PDCP entity is different from the second PDCP entity;
  • a logic circuit configured to process the first PDCP control PDU based on the fifth PDCP entity, and process the first PDCP data PDU based on the sixth PDCP entity.
  • the input and output interface is used to input data packets; wherein, the transmission modes of the PDCP entity and the RLC entity of the first communication device are both transparent modes;
  • the logic circuit is used to determine the sequence number corresponding to the data packet according to the time domain position of the input data packet and the mapping relationship between the sequence number and the time domain position.
  • the logic circuit is used to determine the time domain position corresponding to the data packet according to the mapping relationship between the serial number and the time domain position and the serial number corresponding to the data packet; wherein, the transmission modes of the PDCP entity and the RLC entity of the second communication device are both transparent model;
  • the input and output interface is used to output the first data packet at the time domain position corresponding to the data packet.
  • an embodiment of the present application also provides a computer-readable storage medium, in which a computer program or instruction is stored.
  • a computer program or instruction is stored.
  • the above-mentioned method embodiment is implemented.
  • the embodiment of the present application also provides a computer program product, which, when running on a computer, enables the method in the above method embodiment to be executed.
  • the processor in the embodiments of the present application can be a central processing unit (Central Processing Unit, CPU), and can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only Memory, registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC can be located in the base station or the terminal.
  • the processor and the storage medium may also exist in the base station or the terminal as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer program or instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website, computer, A server or data center transmits to another website site, computer, server or data center by wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; and it may also be a semiconductor medium, such as a solid state disk.
  • the computer readable storage medium may be a volatile or a nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship; in the formulas of this application, the character “/” indicates that the contextual objects are a “division” Relationship.
  • “Including at least one of A, B and C” may mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

Landscapes

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

Abstract

本申请实施例提供一种通信方法及装置，第一通信设备获取无线承载的配置信息，其中该配置信息用于指示该无线承载对应的RLC实体的传输模式为透明模式；第一通信设备基于该配置信息，将该无线承载对应的RLC实体的传输模式配置为透明模式。通过将无线承载对应的RLC实体的传输模式配置为透明模式，可以有效减少该无线承载对应的RLC PDU的头开销、节省空口开销，更好地满足URLLC业务的低时延和高可靠性需求。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2021年08月03日提交中国专利局、申请号为202110884514.8、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及无线通信领域，尤其涉及一种通信方法及装置。
背景技术
超高可靠性低时延通信(ultra-reliability low latency communation，URLLC)是第五代移动通信技术(5 th generation mobile network，5G)的重要应用场景之一。URLLC最大的特点是低时延和高可靠性。因此，在自动驾驶、工业制造、车联网和智能电网等领域的广泛应用。
新无线(New radio，NR)协议规定，相互通信的设备之间具有一定的协议层结构，例如发送端应用(application，APP)层下来的数据包需要经过业务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)、无线链路控制(Radio link control，RLC)、媒体接入控制(medium access control，MAC)层、物理(physical layer，PHY)层等多个协议层的处理，每层的处理复杂，不仅带来较大的处理时延，还会增加额外的头开销，即增加了空口开销，所以难以满足URLLC的低时延和高可靠性需求。
因此，如何降低空口开销和处理时延，以满足URLLC的低时延和高可靠性需求，是亟需解决的技术问题。
发明内容
本申请实施例提供一种通信方法及装置，用以降低空口开销和处理时延，满足URLLC的低时延和高可靠性需求。
第一方面，提供一种通信方法，以方法由第一通信设备的RLC实体执行为例，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备的RLC实体从上层实体获取RLC SDU；第一通信设备的RLC实体根据RLC SDU生成RLC PDU；其中，RLC PDU包括头部和数据，数据为RLC SDU的数据中的第一分段，头部包括序列号和第一索引，序列号用于标识RLC SDU，第一索引用于标识第一分段在RLC SDU的分段中的编号，RLC SDU中的不同分段分别对应不同的索引；第一通信设备的RLC实体发送RLC PDU。
相应的，第二方面，提供一种通信方法，以方法由第二通信设备的RLC实体执行为例，第二通信设备能够与第一通信设备通信，第二通信设备例如是基站或终端，本申请不做限制。方法包括：第二通信设备的RLC实体接收RLC PDU；其中，RLC PDU包括头部和数据，数据为RLC SDU的第一分段，头部包括序列号和第一索引，序列号用于标识RLC SDU，第一索引用于标识第一分段在RLC SDU的分段中的编号，RLC SDU中的不同分段分别对 应不同的索引；第二通信设备的RLC实体根据序列号和第一索引确定RLC PDU的数据是RLC SDU的分段中的第一分段。
上述方案通过索引来指示每个RLC PDU中的数据是RLC SDU中的第几个分段，可以在保证数据传输可靠性的前提下，减少RLC PDU的头开销，进而节省空口开销。
一种可能的设计中，第一索引的取值不超过阈值。换而言之，第一索引对应的开销不超过预设比特。例如，第一索引的取值范围是0～15，则对应二进制表示为“1111”，则第一索引的开销最多为4bits。
如此，可以保证第一索引的开销在预设比特范围内，进而节省空口开销。
第三方面，提供一种通信方法，以方法由第一通信设备的RLC实体执行为例，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备的RLC实体从上层实体获取RLC SDU；第一通信设备的RLC实体根据配置信息确定RLC SDU不分段，其中配置信息用于指示RLC SDU不分段；第一通信设备的RLC实体根据RLC SDU生成RLC PDU；其中，RLC PDU的数据为完整的RLC SDU；第一通信设备的RLC实体发送RLC SDU。
相应的，第四方面，提供一种通信方法，以方法由第二通信设备的RLC实体执行为例，第二通信设备能够与第一通信设备通信，第二通信设备例如是基站或终端，本申请不做限制。法包括：第二通信设备的RLC实体接收RLC PDU；根据配置信息确定该RLC PDU的数据为完整的RLC SDU。
上述方案中，可以实现在RLC PDU中不携带SO字段，进而减少RLC PDU的头开销、节省空口开销。
一种可能的设计中，网络设备(例如是第一通信设备或第二通信设备或其它设备)还生成并发送配置信息，该配置信息用于指示第一通信设备的RLC SDU不分段。
一种可能的设计中，配置信息的配置粒度可以由数据无线承载、服务质量流、PDU会话、网络切片、逻辑信道标识、终端、PDCP实体或RLC实体中一项或多项确定。
如此，提供了配置信息的多种配置粒度，提高了方案的灵活性。
一种可能的设计中，配置信息的具体内容可以包括：第一指示信息，用于指示业务类型为超可靠低时延通信业务；和/或，第二指示信息，用于指示RLC SDU被允许的最大可分段数量为0或RLC SDU不分段。以配置粒度由数据无线承载确定为例，则配置信息可以包括：第一指示信息，用于指示第一数据无线承载对应的业务类型为超可靠低时延通信业务，和/或，第二指示信息，用于指示第一数据无线承载对应的RLC SDU被允许的最大可分段数量为0或者第一数据无线承载对应的RLC SDU不分段。
如此，配置信息的内容可以有多种实现方式，提高了方案的灵活性。
第五方面，提供一种通信方法，该方法可以由第一通信设备执行，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备获取无线承载的配置信息，其中配置信息用于指示无线承载对应的RLC实体的传输模式为透明模式；第一通信设备基于配置信息，将无线承载对应的RLC实体的传输模式配置为透明模式。
相应的，第六方面，提供一种通信方法，该方法可以由第二通信设备执行，第二通信设备能够与第一通信设备通信，第二通信设备例如是基站，本申请不做限制。方法包括：第二通信设备生成无线承载的配置信息，其中配置信息用于指示无线承载对应的RLC实体的传输模式为透明模式；第二通信设备发送配置信息。
基于上述方案中，可以实现单独配置某个无线承载支持RLC TM模式，进而有效减少 RLC PDU的头开销、节省空口开销。
一种可能的设计中，无线承载为数据无线承载、信令无线承载或计算无线承载中的一种。
第七方面，提供一种通信方法，以方法由第一通信设备的PDCP实体执行为例，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备的PDCP实体获取PDCP SDU；第一通信设备的PDCP实体根据PDCP SDU生成PDCP PDU；其中，PDCP PDU包括头部和数据，数据为PDCP SDU中的一个分段，头部包括序列号，序列号用于标识PDCP SDU，头部还包括分段偏移或索引，分段偏移用于指示一个分段的第一个字节在PDCP SDU中的字节偏移量，索引用于标识一个分段在RLC SDU的分段中的编号。
相应的，第八方面，提供一种通信方法，以方法由第二通信设备的PDCP实体执行为例，第二通信设备能够与第一通信设备通信，第二通信设备例如是基站或终端，本申请不做限制。方法包括：第二通信设备的PDCP实体获取多个PDCP PDU；其中，多个PDCP PDU中的每个PDCP PDU包括头部和数据，数据为PDCP SDU中的一个分段，头部包括序列号，序列号用于标识PDCP SDU，头部还包括分段偏移或索引，分段偏移用于指示一个分段的第一个字节在PDCP SDU中的字节偏移量，索引用于标识一个分段在RLC SDU的分段中的编号；其中，多个PDCP PDU对应的序列号相同；第二通信设备的PDCP实体根据多个PDCP PDU生成一个PDCP SDU。
基于上述方案，可以实现将RLC层的功能合并到PDCP层，进而省去RLC层的所有头开销，所以可以减少空口开销。
一种可能的设计中，第一通信设备的PDCP实体可以直接将PDCP PDU下发给媒体接入控制实体。相应的，第二通信设备的PDCP实体也可以直接从媒体接入控制实体获取多个PDCP PDU。
如此，可以直接省去了RLC层的处理过程，进而降低第一通信设备和处理端的处理时延。
第九方面，提供一种通信方法，该方法可以由第一通信设备执行，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备的第一PDCP实体发送第一PDCP data PDU；第一通信设备的第二PDCP实体发送第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联，第一PDCP实体与第二PDCP实体不同。
相对应的，第十方面，提供一种通信方法，该方法可以由第二通信设备执行，第二通信设备能够与第一通信设备通信，第二通信设备例如是终端或基站，本申请不做限制。方法包括：第二通信设备接收第一通信设备的第一PDCP实体发送的第一PDCP data PDU；第二通信设备接收第一通信设备的第二PDCP实体发送的第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联，第一PDCP实体与第二PDCP实体不同。
基于上述方案，可以实现PDCP data PDU与PDCP control PDU解耦，通过PDCP data PDU与PDCP control PDU不同的PDCP实体发送，如此可以支持PDCP实体采用TM模式发送PDCP data PDU，减少PDCP data PDU的头开销，节省空口开销。
一种可能的设计中，第一通信设备还获取配置信息；第一通信设备根据配置信息确定第一PDCP实体发送第一PDCP data PDU、第二PDCP实体发送第一PDCP control PDU。例如，第一通信设备是终端，第二通信设备是基站，则第二通信设备生成配置信息，并向 第一通信设备发送配置信息，第一通信设备接收来自第二通信设备的配置信息；或者例如，第二通信设备是终端，第一通信设备是基站，则第一通信设备生成配置信息，并向第二通信设备发送配置信息，第二通信设备接收来自第一通信设备的配置信息。
如此，可以实现网络侧给终端侧配置PDCP data PDU与PDCP control PDU解耦，提高了方案的可靠性。
一种可能的设计中，配置信息可以包括：第一指示信息，用于指示：第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，或者，第一PDCP实体的传输模式为透明模式。
如此，网络侧可以显式地指示第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，也可以隐式地指示第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，提高了方案的灵活性。
一种可能的设计中，配置信息还可以包括以下至少一种：第二指示信息，用于指示：第一PDCP实体用于传输PDCP data PDU；第三指示信息，用于指示：第二PDCP实体用于传输PDCP control PDU；第四指示信息，用于指示：第二PDCP实体传输的PDCP control PDU与第一PDCP实体传输的PDCP data PDU关联。
如此，网络侧还可更加清楚地指示终端侧PDCP data PDU的传输实体与PDCP control PDU的传输实体分离的方式，提高了方案的可靠性。
一种可能的设计中，该方法还包括：第一通信设备的第三PDCP实体发送第二PDCP data PDU；第一通信设备的第四PDCP实体发送第二PDCP control PDU。相对应的，第二通信设备接收第一通信设备的第三PDCP实体发送的第二PDCP data PDU；第二通信设备接收第一通信设备的第四PDCP实体发送的第二PDCP control PDU。其中，第二PDCP control PDU与第二PDCP data PDU关联，第三PDCP实体、第四PDCP实体、第一PDCP实体、第二PDCP实体中任意两个实体不同。
换而言之，传输PDCP data PDU的PDCP实体与传输PDCP control PDU的PDCP实体的关联关系可以是一对一的关联关系。
一种可能的设计中，该方法还包括：第一通信设备的第三PDCP实体发送第二PDCP data PDU；第一通信设备的第二PDCP实体发送第二PDCP control PDU。相对应的，第二通信设备接收第一通信设备的第三PDCP实体发送的第二PDCP data PDU；第二通信设备接收第一通信设备的第二PDCP实体发送的第二PDCP control PDU。其中，第二PDCP control PDU与第二PDCP data PDU关联，第三PDCP实体、第一PDCP实体、第二PDCP实体中任意两个实体不同。
换而言之，传输PDCP data PDU的PDCP实体与传输PDCP control PDU的PDCP实体的关联关系可以是多对一的关联关系。
一种可能的设计中，当第一通信设备的第二PDCP实体既发送第一PDCP control PDU又发送第二PDCP control PDU时，第一PDCP control PDU中可以携带第一PDCP实体的标识；第二PDCP control PDU中携带第三PDCP实体的标识或第二PDCP data PDU的标识。
如此，可以方便接收端区分第二PDCP实体中的不同PDCP control PDU，提高通信的可靠性。
第十一方面，提供一种通信方法，该方法可以由第一通信设备执行，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备的第一PDCP实体发送第一 PDCP data PDU；第一通信设备RRC实体或NAS实体或SDAP实体或RLC实体或MAC实体或物理层实体发送第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联。
相应的，第十二方面，提供一种通信方法，该方法可以由第二通信设备执行，第二通信设备能够与第一通信设备通信，第二通信设备例如是终端或基站，本申请不做限制。方法包括：第二通信设备接收第一通信设备的第一PDCP实体发送的第一PDCP data PDU；第二通信设备接收第一通信设备的RRC实体或NAS实体或SDAP实体或RLC实体或MAC实体或物理层实体发送的第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联。
基于上述方案，可以实现PDCP data PDU与PDCP control PDU解耦，通过其它层的实体发送PDCP control PDU，如此可以支持PDCP实体采用TM模式发送PDCP data PDU，进而减少PDCP data PDU的头开销，节省空口开销。
第十三方面，提供一种通信方法，该方法可以由第一通信设备执行，第一通信设备例如是基站或终端，本申请不做限制。方法包括：第一通信设备接收数据包；其中，第一通信设备的PDCP实体和RLC实体的传输模式均为透明模式；第一通信设备根据接收数据包的时域位置、序列号与时域位置的映射关系，确定数据包对应的序列号。
相应的，第十四方面，提供一种通信方法，该方法可以由第二通信设备执行，第二通信设备能够与第一通信设备通信，第二通信设备例如是终端或基站，本申请不做限制。方法包括：第二通信设备根据序列号与时域位置的映射关系、数据包对应的序列号，确定数据包对应的时域位置；其中，第二通信设备的PDCP实体和RLC实体的传输模式均为透明模式；第二通信设备在数据包对应的时域位置发送第一数据包。
基于上述方案，可以实现PDCP实体和RLC实体都支持TM，同时第一通信设备可以获得PDCP data PDU和RLC data PDU对应的SN，进而在实现节省空口开销的同时，保证数据传输的可靠性。
在本申请实施例中，对序列号与时域位置执行映射操作可以由任一协议层对应的实体执行。例如：
第一种可能的设计中，第一通信设备的媒体接入控制实体可以向第一通信设备的PDCP实体传递数据包的时域位置；第一通信设备的PDCP实体根据媒体接入控制实体接收数据包的时域位置、序列号与时域位置的映射关系，确定数据包对应的序列号。
第二种可能的设计中，第一通信设备的媒体接入控制实体可以根据接收数据包的时域位置、序列号与时域位置的映射关系，确定数据包对应的序列号，进而第一通信设备的媒体接入控制实体向第一通信设备的PDCP实体传递数据包对应的序列号。
第三种可能的设计中，第二通信设备的PDCP实体也可以向第二通信设备的媒体接入控制实体传递数据包对应的序列号，进而第二通信设备的媒体接入控制实体根据序列号与时域位置的映射关系、数据包对应的序列号，确定数据包对应的时域位置。
第四种可能的设计中，第二通信设备的PDCP实体可以根据序列号与时域位置的映射关系、数据包对应的序列号，确定数据包对应的时域位置，进而第二通信设备的PDCP实体向第二通信设备的媒体接入控制实体传递数据包对应的时域位置。
应理解，以上四种方式仅为示例而非限定。
一种可能的设计中，第一通信设备可以从网络设备获取序列号与时域位置的映射关系。 例如，第一通信设备是终端，则基站可以发送序列号与时域位置的映射关系，进而第一通信设备从基站接收序列号与时域位置的映射关系。
第十五方面，提供一种通信装置，该装置包括收发模块，用于与该装置之外的其它装置通信，处理模块用于通过控制通信模块执行如第一方面或第一方面任一可能的设计或第二方面或第二方面任一可能的设计或第三方面或第三方面任一可能的设计或第四方面或第四方面任一可能的设计或第五方面或第五方面任一可能的设计或第六方面或第六方面任一可能的设计或第七方面或第七方面任一可能的设计或第八方面或第八方面任一可能的设计或第九方面或第九方面任一可能的设计或第十方面或第十方面任一可能的设计或第十一方面或第十一方面任一可能的设计或第十二方面或第十二方面任一可能的设计或第十三方面或第十三方面任一可能的设计或第十四方面或第十四方面任一可能的设计中所述的方法的模块。
第十六方面，提供一种通信装置，包括处理器和存储器；其中，处理器和存储器耦合，存储器用于存储计算机执行指令，处理器用于执行存储器所存储的计算机执行指令，以使通信装置执行如第一方面或第一方面任一可能的设计或第二方面或第二方面任一可能的设计或第三方面或第三方面任一可能的设计或第四方面或第四方面任一可能的设计或第五方面或第五方面任一可能的设计或第六方面或第六方面任一可能的设计或第七方面或第七方面任一可能的设计或第八方面或第八方面任一可能的设计或第九方面或第九方面任一可能的设计或第十方面或第十方面任一可能的设计或第十一方面或第十一方面任一可能的设计或第十二方面或第十二方面任一可能的设计或第十三方面或第十三方面任一可能的设计或第十四方面或第十四方面任一可能的设计中所述的方法。
第十七方面，提供一种芯片，包括逻辑电路和输入输出接口；其中，输入输出接口用于接收来自芯片之外的其它通信装置的信号并传输至逻辑电路或将来自逻辑电路的信号发送给芯片之外的其它通信装置，逻辑电路用于实现如第一方面或第一方面任一可能的设计或第二方面或第二方面任一可能的设计或第三方面或第三方面任一可能的设计或第四方面或第四方面任一可能的设计或第五方面或第五方面任一可能的设计或第六方面或第六方面任一可能的设计或第七方面或第七方面任一可能的设计或第八方面或第八方面任一可能的设计或第九方面或第九方面任一可能的设计或第十方面或第十方面任一可能的设计或第十一方面或第十一方面任一可能的设计或第十二方面或第十二方面任一可能的设计或第十三方面或第十三方面任一可能的设计或第十四方面或第十四方面任一可能的设计中所述的方法。
第十八方面，提供一种计算机可读存储介质，存储介质中存储有计算机程序或指令，当计算机程序或指令被通信装置执行时，实现如第一方面或第一方面任一可能的设计或第二方面或第二方面任一可能的设计或第三方面或第三方面任一可能的设计或第四方面或第四方面任一可能的设计或第五方面或第五方面任一可能的设计或第六方面或第六方面任一可能的设计或第七方面或第七方面任一可能的设计或第八方面或第八方面任一可能的设计或第九方面或第九方面任一可能的设计或第十方面或第十方面任一可能的设计或第十一方面或第十一方面任一可能的设计或第十二方面或第十二方面任一可能的设计或第十三方面或第十三方面任一可能的设计或第十四方面或第十四方面任一可能的设计中所述的方法。
第十九方面，提供一种计算机程序产品，当其在计算机上运行时，使得如第一方面或 第一方面任一可能的设计或第二方面或第二方面任一可能的设计或第三方面或第三方面任一可能的设计或第四方面或第四方面任一可能的设计或第五方面或第五方面任一可能的设计或第六方面或第六方面任一可能的设计或第七方面或第七方面任一可能的设计或第八方面或第八方面任一可能的设计或第九方面或第九方面任一可能的设计或第十方面或第十方面任一可能的设计或第十一方面或第十一方面任一可能的设计或第十二方面或第十二方面任一可能的设计或第十三方面或第十三方面任一可能的设计或第十四方面或第十四方面任一可能的设计中所述的方法被执行。
附图说明
图1为NR协议中用户面协议栈的示意图；
图2为RLC SDU分段的示意图；
图3A～图3E，为非确认模式的RLC data PDU的格式示意图；
图4A、图4B为两种PDCP data PDU的格式示意图；
图5为本申请实施例适用的一种通信系统的架构示意图；
图6A为本申请实施例提供的一种通信方法的流程图；
图6B为本申请实施例提供的一种可能的RLC PDU格式的示意图；
图7为本申请实施例提供的另一种通信方法的流程图；
图8A为本申请实施例提供的另一种通信方法的流程图；
图8B为本申请实施例提供的另一种可能的RLC PDU格式的示意图；
图9A为本申请实施例提供的另一种通信方法的流程图；
图9B、图9C为本申请实施例提供的两种可能的PDCP data PDU的格式示意图；
图9D～图9F为本申请实施例提供的三种可能的PDCP control PDU的格式示意图；
图10A为本申请实施例提供的一种可能的PDCP PDU格式的示意图；
图10B为本申请实施例提供的另一种通信方法的流程图；
图10C为本申请实施例提供的另一种通信方法的流程图；
图11A为本申请实施例提供的另一种通信方法的流程图；
图11B为本申请实施例提供的单载波传输场景的示意图；
图11C为本申请实施例提供的双载波传输场景的示意图；
图12为本申请的实施例提供的一种可能的通信装置的结构示意图；
图13为本申请的实施例提供的另一种可能的通信装置的结构示意图；
图14为本申请的实施例提供的一种可能的芯片的结构示意图。
具体实施方式
新无线(New radio，NR)协议中，相互通信的设备之间具有一定的协议层结构，且基于该协议层结构通信。
以用户设备(user equipment，UE)与基站(gNB)通信为例，参见图1，为UE与gNB之间进行通信的用户面协议栈的示意图，从上之下依次包括业务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制(Radio link control，RLC)层、媒体接入控制(medium access control， MAC)层、物理(physical layer，PHY)层等(控制面协议栈和用户面协议栈类似，只需要将SDAP层替换成无线资源控制(radio resource control，RRC)层)。数据传输过程中，每一层协议由对应层的实体执行，为了便于理解，本申请以下实施例中将执行SDAP层协议的实体称为SDAP实体，将执行PDCP层协议的实体称为PDCP实体，将执行RLC层协议的实体称为RLC实体，将执行MAC层协议的实体称为MAC实体，将执行PHY层协议的实体称为PHY实体等。
在UE与gNB进行数据传输时，数据需要依次经过UE与gNB上的各个层并在各个层进行相应的处理。以上行传输为例，数据在UE侧的各个层的处理包括：
1)UE侧SDAP实体接收应用(application，APP)层下发的数据包，为该数据包增加SDAP头(header)，最终形成SDAP层的协议数据单元(protocol data unit，PDU)，简称SDAP PDU，并传递给PDCP实体；
2)PDCP实体收到SDAP PDU，将其作为PDCP层的业务数据单元(service data unit，SDU)，简称PDCP SDU经过PDCP实体处理后增加PDCP header，最终形成PDCP PDU，并传递给RLC实体；
3)RLC实体收到PDCP PDU，将其作为RLC层的SDU，简称RLC SDU经过RLC实体处理后，增加RLC header，最终形成RLC层的PDU，简称RLC PDU，并传递给MAC实体；
其中，RLC实体在处理RLC SDU时，还可以对RLC SDU进行分段，生成多个RLC SDU分段(Segement)，然后对每个分段分别增加RLC header，最终形成多个RLC PDU递交给MAC实体，如图2所示。
4)MAC实体收到RLC PDU，将其作为MAC层的SDU，简称MAC SDU经过MAC实体处理后，增加MAC子头(Subheader)，生成MAC subPDU，并将多个MAC sbuPDU(若同时有多个APP数据包都要发送，则生成多个MAC SDU对应的MAC sbuPDU；若有MAC CE要发送，则生成MAC CE对应的MAC subPDU)级联生成MAC层的PDU，简称MAC PDU，递交给PHY实体；
5)PHY实体从MAC实体收到MAC PDU后进行PHY实体编码并从空口发送给基站。
其中，RLC实体的传输模式有以下三种：
1)非确认模式(unacknowledged mode，UM)：发送实体在高层PDU上添加必要的控制协议开销，然后进行传送但并不保证传递到对等实体，且没有使用重传协议。接收实体对所接收到的错误数据标记为错误后递交，或者直接丢弃并向高层报告。由于RLC PDU包含有序列号(sequence number，SN)，因此能够检测高层PDU的完整性。UM的业务有小区广播和IP电话。
2)透明模式(transparent mode，TM)：发送实体在高层数据上不添加任何额外控制外协议开销，仅仅根据业务类型决定是否进行分段操作。接收实体接收到的PDU如果出现错误，则根据配置，在错误标记后递交或者直接丢弃并向高层报告。实时语音业务通常采用RLC透明模式。
3)确认模式(acknowledged mode，AM)：发送侧在高层数据上添加必要的控制协议开销后进行传送，并保证传递到对等实体。因为具有自动重传请求(auto repeat request，ARQ)能力，如果RLC接收到错误的RLC PDU，就通知发送方的RLC重传这个PDU。由于RLC PDU中包含有序列号信息，支持数据向高层的顺序/乱序递交。AM模式是分组 数据传输的标准模式，比如www和电子邮件下载。
针对URLLC业务场景的数据包的传输，RLC实体一般使用UM。参见图3A～图3D，UM的无线链路控制数据协议数据单元(RLC data PDU)，支持如下几种格式：
1)如图3A所示，RLC data PDU包括一个完整的RLC SDU；
2)如图3B所示，RLC data PDU包括6比特的SN(没有分段偏移(segement offset，SO))；
3)如图3C所示，RLC data PDU包括12比特的SN(没有SO)；
4)如图3D所示，RLC data PDU包括6比特的SN并且有SO；
5)如图3E所示，RLC data PDU包括12比特的SN并且有SO。
上述各字段的含义如下：
R：预留比特；
SN：RLC SDU对应的数据包的编号，一般APP层下发的一个数据包对应一个SN，RLC层的SN一般可称为RLC SN；
SO：单位为字节(byte)，在某个RLC SN对应的完整数据包进行分段后、用于指示该分段位于完整RLC SN的哪个位置，如分段的第一个字节在PDCP SDU中的字节偏移量(例如第一个分段的SO为"0000000000000000")，长度为16比特(bits)；
数据(Data)：上层数据，例如：应用层数据，或业务数据适配协议数据协议数据单元(SDAP data PDU)，或业务数据适配协议控制协议数据单元(SDAP control PDU)等；
分段信息(Segmentation Info，SI)：用于进一步指示RLC PDU的类型。
其中，针对SI的不同取值对应的含义如下：
00：RLC PDU的数据包含RLC SDU的所有字节；
01：RLC PDU的数据包含RLC SDU的第一段；
10：RLC PDU的数据包含RLC SDU的最后一段；
11：RLC PDU的数据既不包含RLC SDU的第一段，也不包含RLC SDU的最后一段。
Oct：octal，表示八进制的。
从PDCP层看，分组数据汇聚层协议数据协议数据单元(PDCP data PDU)支持如下两种格式：
1)如图4A所示，具有12位PDCP SN的PDCP data PDU；
2)如图4B所示，具有18位PDCP SN的PDCP data PDU。
从图4A和图4B可以看出，上述两种格式下的PDCP data PDU除了携带上层数据外，分别额外还有6bytes和7bytes的头开销。
各字段的含义如下：
D/C：指示PDCP PDU的类型，包括“PDCP data PDU”(即携带APP数据)、“分组数据汇聚层协议控制协议数据单元PDCP control PDU”(即携带PDCP层本身的控制信令)两种可能；
R：预留位；
SN：指示该PDCP data PDU中的本次发送的数据包对应的SN，PDCP data PDU的SN与其对应的RLC SDU的SN相同，PDCP层的SN可称为PDCP SN；
数据(Data)：上层数据，例如：应用层数据，或SDAP data PDU，或SDAP control PDU等；
MAC-I：完整性保护字段，用于接收端进行完整性校验。
基于以上描述可知，由于NR协议栈分为多层，且每层的处理复杂，会增加额外的头开销(如SN、SO等)，带来较大的空口开销；而且各层是串行处理，因此还会带来比较大的处理时延，例如，在上行传输中，UE侧封包时延增加，gNB侧解包时延增加；在下行传输中，gNB侧封包时延增加、UE侧解包时延增加。
鉴于此，提供本申请实施例的技术方案，用于简化相互通信的设备之间的协议层结构，进而降低数据包在设备上的处理时延以及降低空口开销。
本申请实施例可以应用于各种通信系统，例如包括但不限于：卫星通信系统、物联网(internet of things，IoT)、窄带物联网(narrow band internet of things，NB-IoT)系统、全球移动通信系统(global system for mobile communications，GSM)、增强型数据速率GSM演进系统(enhanced data rate for GSM evolution，EDGE)、宽带码分多址系统(wideband code division multiple access，WCDMA)、码分多址2000系统(code division multiple access，CDMA2000)、时分同步码分多址系统(time division-synchronization code division multiple access，TD-SCDMA)，长期演进系统(long term evolution，LTE)、第五代移动通信技术(5 th generation mobile network，5G)系统，具体例如5G新无线(new radio，NR)，以及5G移动通信系统的三大应用场景增强型移动带宽(enhanced mobile broadband，eMBB)，超可靠、低时延通信(ultra reliable low latency communications，uRLLC)和海量机器类通信(massive machine type communications，mMTC)，设备到设备(device-to-device，D2D)通信系统、机器到机器(machine to machine，M2M)通信系统、车联网通信系统，或者第六代移动通信技术(6th generation mobile network，6G)系统，或者未来演进的通信系统，或者其他通信系统等，本申请实施例对此不做限定。
进一步的，本申请实施例不仅可以适用于基站和终端的通信，也可以适用于基站和基站的通信，终端和终端的通信，车联网、物联网或工业互联网等的通信。
示例性的，参见图5，为本申请实施例适用的一种通信系统1000的架构示意图。如图5所示，该通信系统包括无线接入网100和核心网200，可选的，通信系统1000还可以包括互联网300。其中，无线接入网100可以包括至少一个无线接入网设备(如图5中的110a和110b)，还可以包括至少一个终端(如图5中的120a-120j)。终端通过无线的方式与无线接入网设备相连，无线接入网设备通过无线或有线方式与核心网连接。核心网设备与无线接入网设备可以是独立的不同的物理设备，也可以是将核心网设备的功能与无线接入网设备的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备的功能和部分的无线接入网设备的功能。终端和终端之间以及无线接入网设备和无线接入网设备之间可以通过有线或无线的方式相互连接。图5只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备，在图5中未画出。
无线接入网设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、第五代(5th generation，5G)移动通信系统中的下一代基站(next generation NodeB，gNB)、第六代(6th generation，6G)移动通信系统中的下一代基站、未来移动通信系统中的基站或WiFi系统中的接入节点等；也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)，也可以是分布式单元(distributed unit，DU)。这里的CU完成基站的无线资源控制协议和分组数据汇聚层协议(packet data convergence protocol，PDCP)的功能，还可以完成业务数 据适配协议(service data adaptation protocol，SDAP)的功能；DU完成基站的无线链路控制(Radio link control，RLC)层和媒体接入控制(medium access control，MAC)层的功能，还可以完成部分物理层或全部物理层的功能，有关上述各个协议层的具体描述，可以参考第三代合作伙伴计划(3rd generation partnership project，3GPP)的相关技术规范。无线接入网设备可以是宏基站(如图5中的110a)，也可以是微基站或室内站(如图5中的110b)，还可以是中继节点或施主节点等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。为了便于描述，下文以基站作为无线接入网设备的例子进行描述。
终端也可以称为终端设备、用户设备(user equipment，UE)、移动台、移动终端等。终端可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
基站和终端可以是固定位置的，也可以是可移动的。基站和终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对基站和终端的应用场景不做限定。
基站和终端的角色可以是相对的，例如，图5中的直升机或无人机120i可以被配置成移动基站，对于那些通过120i接入到无线接入网100的终端120j来说，终端120i是基站；但对于基站110a来说，120i是终端，即110a与120i之间是通过无线空口协议进行通信的。当然，110a与120i之间也可以是通过基站与基站之间的接口协议进行通信的，此时，相对于110a来说，120i也是基站。因此，基站和终端都可以统一称为通信装置，图5中的110a和110b可以称为具有基站功能的通信装置，图5中的120a-120j可以称为具有终端功能的通信装置。
基站和终端之间、基站和基站之间、终端和终端之间可以通过授权频谱进行通信，也可以通过免授权频谱进行通信，也可以同时通过授权频谱和免授权频谱进行通信；可以通过6千兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对无线通信所使用的频谱资源不做限定。
在本申请的实施例中，基站的功能也可以由基站中的模块(如芯片)来执行，也可以由包含有基站功能的控制子系统来执行。这里的包含有基站功能的控制子系统可以是智能电网、工业控制、智能交通、智慧城市等上述应用场景中的控制中心。终端的功能也可以由终端中的模块(如芯片或调制解调器)来执行，也可以由包含有终端功能的装置来执行。
需要说明的是，图5仅仅是对本申请技术方案可以应用到的部分通信场景的举例，而非具体限定，实际还可以有其它场景。另外，图5中基站的数量、终端的数量也只是举例，本申请不限制基站和终端的数量。
以下结合附图详细介绍本申请实施例提供的技术方案。
一种可能的实施例中，可以采用索引代替SO。
参见图6A，为本申请实施例提供的一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S61、第一通信设备的RLC实体从上层实体获取RLC SDU。
第一通信设备可以是图5所示场景中的任一设备，例如是基站，或者例如是终端，本申请不做限制。
示例性的，上层实体可以是PDCP实体。其中，第一通信设备的RLC实体从PDCP实体获取RLC SDU还可以说成第一通信设备的RLC实体从PDCP实体获取PDCP PDU。
S62、第一通信设备的RLC实体根据RLC SDU生成RLC PDU。
具体的，第一通信设备的RLC实体可以对RLC SDU进行分段，生成多个RLC SDU分段，然后对每个分段分别增加RLC header，最终形成多个RLC PDU。其中每个RLC PDU均包括头部和数据两部分，其中每个RLC PDU的数据为该RLC SDU的数据中的一个分段，每个RLC PDU的头部包括SN和索引，其中SN用于标识该RLC SDU(即表示该RLC PDU的数据是该RLC SDU的数据中的一部分，具体可参考上文中对SN的定义介绍)，索引用于标识每个RLC PDU对应的分段(即每个RLC PDU的数据)在该RLC SDU的分段中的编号，其中RLC SDU中的不同分段分别对应不同的索引。以一个RLC PDU为例：第一RLC PDU的数据是该RLC SDU的数据中第一分段，第一RLC PDU的头部中的第一索引则用于标识第一RLC PDU的数据是该RLC SDU的分段中第一分段。
示例性的，以第一通信设备的RLC实体对SN为1的RLC SDU进行分段共生成4个RLC SDU分段(分段1、分段2、分段3、分段4)为例：分段1增加RLC header后成为RLC PDU1，其中携带的SN为1，索引的值为00(表示RLC PDU1中的数据是SN为1的RLC SDU中的第1个分段)；分段2增加RLC header后成为RLC PDU2，其中携带的SN为1，索引的值为01(表示RLC PDU2中的数据是SN为1的RLC SDU中的第2个分段)；分段3增加RLC header后成为RLC PDU3，其中携带的SN为1，索引的值为10(表示RLC PDU3中的数据是SN为1的RLC SDU中的第3个分段)；分段4增加RLC header后成为RLC PDU4，其中携带的SN为1，索引的值为11(表示RLC PDU4中的数据是SN为1的RLC SDU中的第4个分段)。
应理解，当然实际应用时也可能不分段，那就不涉及需要标识分段，所以本实施例对不分段的情况不做过多的介绍，本实施例主要是以分段的情况为例。
S63、第一通信设备的RLC实体发送该RLC PDU，相应的，第二通信设备的RLC实体接收该RLC PDU；
应理解，实际传输过程还需经过下层实体(如MAC实体、PHY实体等)的处理。例如，第一通信设备的RLC实体发送RLC PDU的过程包括：RLC层的实体将RLC PDU传递给MAC进行处理获得MAC PDU，MAC实体将MAC PDU传递到PHY实体，最后由PHY实体进行编码后从空口发送出去。相应的，第二通信设备的RLC实体接收RLC PDU的过程包括：第二通信设备的PHY实体对接收到的数据包进行解码获得MAC PDU，PHY实体将MAC PDU传递给MAC实体，MAC实体对MAC PDU进行解包获得RLC PDU，MAC实体将RLC PDU传递给RLC实体。应理解，如果是多个RLC PDU，则依次发送多个RLC PDU。
S64、第二通信设备的RLC实体根据SN和第一索引确定该RLC PDU的数据是RLC SDU的分段中的第一分段。
第二通信设备是可以与第一通信设备段通信的任一设备，例如第一通信设备是图5所示场景中的任一基站，则第二通信设备可以是与该基站通信的终端或者与该基站通信的其它基站，或者例如第一通信设备是图5所示场景中的任一终端，则第二通信设备可以是与该终端通信的基站或者与该终端通信的其它终端，本申请对此不做限制。
第二通信设备的RLC实体可以根据每个RLC PDU的SN确定该RLC PDU的数据是该RLC SDU的一个分段，且根据索引确定该RLC PDU的数据是该RLC SDU中的哪一个分段。
继续以S62中例举的四个分段为例，第二通信设备的RLC实体接收到RLC PDU1后，根据RLC PDU1中携带的SN为1，和索引00确定RLC PDU1中的数据是SN为1的RLC SDU中的第1个分段；第二通信设备的RLC实体接收到RLC PDU2后，根据RLC PDU2中携带的SN为1，和索引01确定RLC PDU2中的数据是SN为1的RLC SDU中的第2个分段；第二通信设备的RLC实体接收到RLC PDU3后，根据RLC PDU3中携带的SN为1，和索引10确定RLC PDU3中的数据是SN为1的RLC SDU中的第3个分段；第二通信设备的RLC实体接收到RLC PDU4后，根据RLC PDU1中携带的SN为1，和索引11确定RLC PDU4中的数据是SN为1的RLC SDU中的第4个分段。
应理解，在具体实现时，上述索引还可以定义为其它名称，例如分段标识、分段编号等，只要其能够用于标识RLC PDU的数据是RLC SDU中的第几个分段，则均在本申请的保护范围之内。
在上述方案中，将原有RLC PDU中的SO替换为索引，通过索引来指示每个RLC PDU中的数据是RLC SDU中的第几个分段，可以在保证数据传输可靠性的前提下，减少RLC PDU的头开销，进而节省空口开销。例如，上文中所举例的四个分段，只需要分别采用索引00、01、10、11来表示即可，只需2bits的头开销，而在原有的SN协议中，采用SO来标识每个分段的地址时，每个RLC SDU的SO都需要16bits的头开销。
可选的，第一索引的取值不超过阈值，换而言之，第一索引对应的开销不超过预设比特。
例如，设定一个RLC SDU最多允许16个分段，则第一索引的取值可以是0～15，对应二进制表示为“1111”，则第一索引最多占据4bits。
如图6B示，作为举例，给出了一种可能的RLC PDU的格式设计，其中“第一索引”字段替代原先协议中的SO字段，相比图3D所示的RLC PDU的格式设计，可以节省12bits的头开销。
在具体实施时，第一通信设备的RLC实体在对RLC SDU进行分段操作时，可以对每个分段的对应的RLC SDU进行计数(累加或递减)，每分段一次就进行一次累加或递减(+1或-1)，针对每个待传输的分段，若计数已达到最大值(对应累加情况)或为0(对应递减情况)，例如已分段15次，即已获得16个分段时，则不再继续分段，进而保证第一索引的取值不超过阈值。
如此，可以保证第一索引不超过预设比特，进而节省空口开销。
可选的，如果系统中同时存在多种协议栈可用时(例如既可以采用图3D所示的RLC PDU格式，也可以采用图6B所示的RLC PDU格式)，则网络设备需要指示使用哪一个协议栈(或者说哪一种RLC PDU格式)进行数据传输。例如，设图6A所示实施例中的第一通信设备是终端，则终端在基于图6A所示的方法发送数据包之前，网络设备可以给终端 发送一个指示信息，用于指示终端设备采用6B所示的RLC PDU格式进行数据发送，相应的，网络设备基于6B所示的RLC PDU格式解析终端设备发送的数据。
如此，可以保证通信的两个设备达成一致的RLC PDU格式，保证通信的可靠性。
一种可能的实施例中，RLC实体可以支持不分段的功能(即RLC PDU可以不携带SO)。
参见图7，为本申请实施例提供的另一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S71、第一通信设备的RLC实体从上层实体获取RLC SDU；
步骤S71的具体实现可以参考上文S61中的相关介绍，此处不再赘述。
S72、第一通信设备的RLC实体根据配置信息确定该RLC SDU不分段，其中配置信息用于指示RLC SDU不分段。
在本申请实施例中，配置信息的配置粒度，包括但不限于以下几种情况：
情况1、配置信息的配置粒度由数据无线承载(data radio bearer，DRB)确定。换而言之，配置信息可以指示每个DRB对应的RLC SDU是/否分段。例如，配置信息可以指示第一DRB对应的RLC SDU不分段，当然配置信息也可以指示第二DRB对应的RLC SDU分段。具体例如，第一通信设备的RLC实体从上层实体获取的RLC SDU对应第一DRB，则根据第一DRB对应的配置信息可知该RLC SDU不分段。
情况2、配置信息的配置粒度由服务质量(QoS)流确定。换而言之，配置信息可以指示每个QoS流对应的RLC SDU是/否分段。例如，配置信息可以指示第一QoS流对应的RLC SDU不分段，当然配置信息也可以指示第二QoS流对应的RLC SDU分段。具体例如，第一通信设备的RLC实体从上层实体获取的RLC SDU对应第一QoS流，则根据第一QoS流对应的配置信息可知该RLC SDU不分段。
情况3、配置信息的配置粒度由PDU会话确定。换而言之，配置信息可以指示每个PDU会话对应的RLC SDU是/否分段。例如，配置信息可以指示第一PDU会话对应的RLC SDU不分段，当然配置信息也可以指示第二PDU会话对应的RLC SDU分段。具体例如，第一通信设备的RLC实体从上层实体获取的RLC SDU对应第一PDU会话，则根据第一PDU会话对应的配置信息可知该RLC SDU不分段。
情况4、配置信息的配置粒度由网络切片确定。换而言之，配置信息可以指示每个网络切片对应的RLC SDU是/否分段。例如，配置信息可以指示第一网络切片对应的RLC SDU不分段，当然配置信息也可以指示第二网络切片对应的RLC SDU分段。具体例如，第一通信设备的RLC实体从上层实体获取的RLC SDU对应第一网络切片，则根据第一网络切片对应的配置信息可知该RLC SDU不分段。
情况5、配置信息的配置粒度由逻辑信道标识确定。换而言之，配置信息可以指示每个逻辑信道标识对应的RLC SDU是/否分段。例如，配置信息可以指示第一逻辑信道标识对应的RLC SDU不分段，当然配置信息也可以指示第二逻辑信道标识对应的RLC SDU分段。具体例如，第一通信设备的RLC实体从上层实体获取的RLC SDU对应第一逻辑信道标识，则根据第一逻辑信道标识对应的配置信息可知该RLC SDU不分段。
情况6、配置信息的配置粒度由终端确定。换而言之，配置信息可以指示每个终端对应的RLC SDU是/否分段。例如，配置信息可以指示第一终端对应的RLC SDU不分段，当然配置信息也可以指示第二终端对应的RLC SDU分段。具体例如，第一通信设备是第 一终端，则根据第一终端对应的配置信息可知该RLC SDU不分段。
情况7、配置信息的配置粒度由RLC实体确定。换而言之，配置信息可以指示每个RLC实体对应的RLC SDU是/否分段。例如，配置信息可以指示第一RLC实体对应的RLC SDU不分段，当然配置信息也可以指示第二RLC实体对应的RLC SDU分段。具体例如，S71中的RLC实体是第一RLC实体，则根据第一RLC实体对应的配置信息可知该RLC SDU不分段。
情况8、配置信息的配置粒度由PDCP实体确定。换而言之，配置信息可以指示每个PDCP实体对应的RLC SDU(即PDCP PDU)是/否分段。例如，配置信息可以指示第一PDCP实体对应的RLC SDU不分段，当然配置信息也可以指示第二PDCP实体对应的RLC SDU分段。具体例如，S71中的RLC实体的上层实体是第一PDCP实体，则根据第一PDCP实体对应的配置信息可知该RLC SDU不分段。
需要说明的是，上述各种情况可以分别单独实施，也可以同时实施。同时实施例如：第一通信设备的RLC实体从上层实体获取的RLC SDU对应第一PDU会话中的第一QoS流，第一通信设备的RLC实体根据第一PDU会话中的第一QoS流配置信息确定该RLC SDU不分段。
为了便于描述，下文中以配置粒度为DRB为例。
在本申请实施例中，配置信息用于指示RLC SDU不分段的具体形式包括但不限于以下两种：
方式1、配置信息携带第一指示信息，其中第一指示信息用于指示业务类型为预设业务。
例如，协议规定或者第一通信设备和第二通信设备约定URLLC业务对应的RLC SDU不分段，eMBB业务对应的RLC SDU可分段，若第一指示信息具体指示第一DRB承载的业务类型为URLLC业务，则第一通信设备的RLC实体确定第一DRB对应的RLC SDU不分段。应理解，此处仅为举例而非具体限定，在实际应用时，协议还规定其它业务类型对应的RLC SDU不分段，或者第一通信设备和第二通信设备还可以约定其它业务类型对应的RLC SDU不分段。
方式2、配置信息携带第二指示信息，其中第二指示信息用于指示RLC SDU不分段。
例如，每个DRB对应的配置信息中携带第一字段，该第一字段用于指示DRB对应的RLC SDU的分段功能的开/关(on/off)，比如取值为1表示分段功能开启，取值为0表示分段功能关闭，若第一DRB对应的配置信息中携带的第一字段的值为0，则第一通信设备的RLC实体确定第一DRB对应的RLC SDU不分段。
方式3、配置信息携带第三指示信息，其中第三指示信息用于指示RLC SDU被允许的最大可分段数量为0或1。其中，最大可分段数量为0，可以理解为不分段，即根据该RLC SDU只生成一个RLC PDU；最大可分段数量为1，可以理解为只生成一个分段，所以根据该RLC SDU只生成一个RLC PDU。因此，无论采用哪种描述，最终效果是一致的。
RLC SDU被允许的最大可分段数量为0为例。例如，每个DRB对应的配置信息中携带第二字段，该第二字段的值N用于表示该DRB对应的RLC SDU被允许的最大可分段数量，其中N为0或正整数；若第一DRB对应的配置信息中携带的第二字段的值N＝0，则第一通信设备的RLC实体确定第一DRB对应的RLC SDU不分段。
当然，在实际应用中，N的值也可以不为0，相应的，第一通信设备的RLC实体的处 理方式也不同。例如，设N＝3，第一通信设备的RLC实体的计数器初始值为0，则第一通信设备的RLC实体接收到RLC SDU时，根据N＝3，计数器＝0，确定允许分段，执行分段操作，对获得的分段填充RLC头，生成第一个RLC PDU，对应的计数器+1，计数器＝1；根据N＝3，计数器＝1，确定允许分段，继续对剩下的RLC PDU部分执行分段操作，对获得的分段填充RLC头，生成第二个RLC PDU，对应的计数器+1，计数器＝2；根据N＝3，计数器＝2，确定允许分段，继续对剩下的RLC PDU部分执行分段操作，对获得的分段填充RLC头，生成第三个RLC PDU，对应的计数器+1，计数器＝3；根据N＝3，计数器＝3，确定不允许分段，不再执行分段和填充操作。应理解，以上仅为举例，本申请对计数器的初始值不做限定，例如初始值也可以是1。
应理解，上述三种方式可以单独实施，也可以相互结合实施，本申请不做限定。另外，上述三种方式仅为示例而非具体限定，具体实施时当然还可以采用其它方式指示RLC SDU不分段。
在具体实施时，如果第一通信设备是网络设备，则该配置信息可以是第一通信设备生成，另外第一通信设备还可以将配置信息发送给终端，以便终端按照该配置信息与网络设备通信。如果上述第一通信设备是终端，则第一通信设备可以从网络设备获取该配置信息，例如网络设备生成该配置信息并发送该配置信息，终端接收网络设备发送的该配置信息。
S73、第一通信设备的RLC实体根据该RLC SDU生成RLC PDU。
由于RLC SDU不分段，所以生成RLC PDU的数据为完整的RLC SDU。生成RLC PDU的格式可以参考图3A、图3B或图3C。
S74、第一通信设备的RLC实体发送该RLC PDU，相应的，第二通信设备的RLC实体接收该RLC PDU。
步骤S74的具体实现可以参考上文S63中的相关介绍，此处不再赘述。
S75、第二通信设备的RLC实体根据该配置信息确定该RLC PDU的数据为完整的RLC SDU。
在上述方案中，可以实现在RLC PDU中不携带SO字段，进而减少RLC PDU的头开销、节省空口开销。
一种可能的实施例中，DRB对应的RLC实体配置中可以支持TM模式配置(即RLC PDU中可以不携带SN和SO)。
参见图8A，为本申请实施例提供的另一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S81、第一通信设备获取无线承载的配置信息，其中配置信息用于指示无线承载对应的RLC实体的传输模式为TM；
第一通信设备可以是图5所示场景中的任一设备，例如是基站，或者例如是终端，本申请不做限制。
无线承载是指SDAP/PDCP/RLC/MAC/PHY等层(其中PHY层是可选的)中，用来承载数据传输的通道。无线承载根据承载的内容不同，可以划分为多种类型，例如包括但不限于：1)、DRB，即无线承载的内容为数据；2)、信令无线承载(radio bearer，SRB)，即承载的内容为信令；3)、计算无线承载(computing radio bearer，CRB)，即承载的内容为计算资源，例如CPU的处理能力等。
下面以DRB为例：
当前NR协议约定DRB对应的RLC实体配置仅能支持AM(简称RLC AM模式)或UM(简称RLC AM模式)，配置内容如下：
Figure PCTCN2022107481-appb-000001
而在本申请实施例中，DRB对应的RLC实体配置除了能支持AM(简称RLC AM)或UM(简称RLC AM模式)外，还可以支持TM(简称RLC TM模式)，配置内容如下：
，例如DRB的配置信息如下：
Figure PCTCN2022107481-appb-000002
Figure PCTCN2022107481-appb-000003
其中，上述黑体部分表示RLC TM模式对应的配置。
在本申请实施例中，配置信息可以由网络设备生成并发送给其它设备(如其它网络设备或终端)。例如，第一通信设备是终端，第二通信设备是基站，则第二通信设备生成配置信息并发送给第一通信设备，相应的，第一通信设备获取无线承载的配置信息具体为：第一通信设备从第二通信设备接收配置信息；或者例如，第一通信设备是基站，第二通信设备是终端，则第一通信设备生成配置信息并发送给第二通信设备，相应的，第一通信设备获取无线承载的配置信息具体为：第一通信设备生成配置信息。在具体实现时，网络设备可以将配置信息承载在RRC层信令中，也可以承载在PDCP层信令或MAC层信令中，本申请对此不做限制。
S82、第一通信设备基于配置信息，将无线承载对应的RLC实体的传输模式配置为TM。
根据上文介绍可知，TM是指发送实体在高层数据上不添加任何额外控制外协议开销，因此第一通信设备的RLC实体在从上侧实体获取到RLC SDU之后，不添加任何控制信息，直接将整个RLC SDU作为RLC PDU或者将RLC SDU的每个分段作为RLC PDU，生成的RLC PDU只有数据，如图8B所示。
基于上述方案，RLC TM不仅能给寻呼(paging)/系统信息块(system information block，SIB)等公共信道使用，对于点对点传输数据时，也可以单独配置一个DRB或SRB或CRB支持RLC TM模式，进而有效减少RLC PDU的头开销、节省空口开销。
一种可能的实施例中，RLC层的功能可以合并到其它层，以省去RLC层的所有RLC头开销。
参见图9A，为本申请实施例提供的另一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S91、第一通信设备的PDCP实体获取PDCP SDU。
第一通信设备可以是图5所示场景中的任一设备，例如是基站，或者例如是终端，本申请不做限制。
第一通信设备的PDCP实体从上层实体获取PDCP SDU，例如PDCP实体接收SDAP实体下发的SDAP PDU，将其作为PDCP SDU。
S92、第一通信设备的PDCP实体根据PDCP SDU生成多个PDCP PDU。
具体的，PDCP实体在处理PDCP SDU时，可以对PDCP SDU进行分段，生成多个PDCP SDU分段，然后对每个分段分别增加PDCP header，最终形成多个PDCP PDU。其中，每个PDCP PDU包括头部和数据，其中数据为PDCP SDU中的一个分段，头部包括序 列号，序列号用于标识PDCP SDU(即PDCP SN，定义可参考上文相关介绍)，头部还包括SO，SO用于指示该分段的第一个字节在PDCP SDU中的字节偏移量。
示例性的，图9B、图9C为两种可能的PDCP data PDU的格式示意图，与图4A和图4B的区别为PDCP头中增加了SI字段和SO字段，SO字段的含义可以参考上文图4A和图4B相关实施例中的介绍，此处不再赘述。这里的SI字段用于进一步指示PDCP data PDU(即RLC data PDU)的类型(分段类型)，其中SI的不同取值对应不同的PDCP data PDU类型。
例如，针对SI的不同取值，对应的含义可以如下：00：PDCP PDU的数据包含PDCP SDU的所有字节；01：PDCP PDU的数据包含PDCP SDU的第一段；10：PDCP PDU的数据包含PDCP SDU的最后一段；11：PDCP PDU的数据既不包含PDCP SDU的第一段，也不包含PDCP SDU的最后一段。应理解，此处仅为举例，实际实施时，SI取值和PDCP PDU类型的对应关系还可以有其它实现方式。
示例性的，图9D～图9F为三种可能的PDCP control PDU的格式示意图。其中“PDU类型”用于指示PDCP control PDU的类型，例如图9D～图9F分别例举了三种不同PDU类型的PDCP control PDU。
其中，图9D所示的PDCP control PDU用于传输用户PDCP状态报告(status report，SR)，比如上行数据传输对应的PDCP SR是由gNB将PDCP SR发送给UE，下行数据传输对应的PDCP SR是由UE将PDCP SR发送给gNB。其中FMC为首个没有传输成功的数据包的编号：位图(bitmap)表示首个未成功的数据包之后的数据包是否传输成功，例如1表示成功，0表示失败。
图9E所示的PDCP control PDU用于传输鲁棒头压缩(RObust header compression，ROHC)的反馈信息。图9F所示的PDCP control PDU用于以太头压缩(ethernet header compression，EHC)的反馈信息。
类似的，图9D～图9F中SI字段用于进一步指示PDCP control PDU(即RLC control PDU)的类型(分段类型)，具体定义可参考图9A、图9B中的相关介绍，此处不再赘述。
应理解，图9B～图9F中SI、SN、SO等字段的位置以及长度仅为举例而非限定。
另外，PDCP control PDU中的SN与PDCP data PDU中的SN可以连续编号，也可以不连续编号，本申请不做限制。
S93、第一通信设备的PDCP实体发送多个PDCP PDU；相应的，第二通信设备的PDCP实体接收多个PDCP PDU。
若第一通信设备PDCP实体对PDCP SDU执行了分段操作，则第一通信设备的PDCP实体将依次发送PDCP SDU对应的多个PDCP PDU，相应的，第二通信设备的PDCP实体依次接收PDCP SDU对应的多个PDCP PDU。应理解，实际传输过程还需经过下层实体(如MAC实体、PHY实体等)的处理，具体可参考上文相关介绍，此处不再赘述。
S94、第二通信设备的PDCP实体根据多个PDCP PDU生成一个PDCP SDU。
具体的，第二通信设备的PDCP实体根据该多个PDCP PDU中的SN相同确定该多个PDCP PDU对应同一PDCP SDU，然后根据该多个PDCP PDU中各PDCP PDU的SO，将该多个PDCP PDU按序组合为一个完整的PDCP SDU。
应理解，在实际上，RLC层也支持RLC SDU不分段的功能，所以RLC层支持RLC SDU不分段的功能也可以合并到PDCP层中，此处不再详述。
可选的，在本申请实施例中，第一通信设备PDCP实体获得PDCP PDU之后，可以将PDCP PDU直接下发到MAC层。相应的，第二通信设备的PDCP实体可以直接从MAC实体获取PDCP PDU。当然，实际应用时，第一通信设备的PDCP实体也可以将PDCP PDU先下发到RLC实体，而RLC实体可以不做任何处理，直接将PDCP PDU传递到MAC实体，第二通信设备的MAC实体也可以将MAC SDU传递到RLC实体，而RLC实体可以不做任何处理，直接将MAC SDU(即PDCP PDU)传递到PDCP实体。
应理解，以上是以将RLC层的功能合并到PDCP层为例，在实际应用中，也可以将RLC层的功能合并到其它层(如RRC层、MAC层等)，本申请不做限制。
基于上述方案，一方面，由于省去了RLC层的所有头开销，所以可以减少空口开销，另一方面，由于省去了RLC层的处理，所以还可以降低第一通信设备和处理端的处理时延。
一种可能的实施例中，PDCP实体可以支持TM，进而省去PDCP层的所有PDCP头开销。
如上文图4A、图4B中的相关介绍，PDCP data PDU除了携带上层应用数据外，额外还携带的PDCP头开销为：6bytes和7bytes(若完保功能开启)，或2bytes和3bytes(若完保功能关闭)。
本实施例主要讨论PDCP data PDU节省PDCP头开销，具体分为如下两种情况：1)D/C、PDCP SN：若PDCP数据PDU不携带PDCP SN，意味着PDCP加密功能始终不支持(因为当前PDCP加密依赖PDCP SN作为输入)；若PDCP数据PDU不携带D/C意味着相关的PDCP Control PDU无法在同一PDCP实体中进行传输(因为现有技术是采用D/C域指示PDCP PDU的类型是PDCP数据PDU或PDCP Control PDU)；2)MAC-I：若PDCP数据PDU不携带MAC-I，意味着完保功能始终不支持。在上述两种情况都成立的情况下，本申请实施例设计一种新型的PDCP PDU格式来支持PDCP实体的TM(简称PDCP TM)，具体格式如图10A所示，PDCP实体在高层数据上不添加任何额外控制外协议开销。与实施例三类似，本实施例中DRB配置可以支持PDCP TM，此处不再详述。
当某个PDCP实体支持TM来传输PDCP data PDU时，则该PDCP实体传输的PDCP PDU中无法携带D/C字段，如果该PDCP实体原本传输的PDCP数据PDU和PDCP control PDU同时在该PDCP实体内进行传输，则无法区分PDCP数据PDU和PDCP control PDU，因此该PDCP实体原本传输的PDCP数据PDU和PDCP control PDU无法同时在该PDCP实体内进行传输。
鉴于此，本实施例提供的以下方法，可以实现PDCP数据PDU和PDCP control PDU分离传输，进而在节省PDCP数据PDU头开销的同时，能够区分PDCP数据PDU和PDCP control PDU。
参见图10B，为本申请实施例提供的另一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S101B、第一通信设备的第一PDCP实体发送PDCP data PDU；相应的，第二通信设备的第五PDCP实体接收第一通信设备的第一PDCP实体发送的PDCP data PDU。
第一通信设备可以是图5所示场景中的任一设备，例如是基站，或者例如是终端，本申请不做限制。第二通信设备则是能够与第一通信设备的其它设备，例如是终端，或者例如是基站，本申请不做限制。
S102B、第一通信设备的第二PDCP实体发送PDCP control PDU，相应的，第二通信 设备的第六PDCP实体接收第一通信设备的第二PDCP实体发送的PDCP control PDU。
其中，第一PDCP实体发送的PDCP data PDU与第二PDCP实体发送的PDCP control PDU关联，第一PDCP实体与第二PDCP实体不同。相对应的，第五PDCP实体接收的PDCP data PDU与第六PDCP实体接收的PDCP control PDU关联，第五PDCP实体与第六PDCP实体不同。
在本申请实施例中，在第一通信设备侧，第一PDCP实体用于发送PDCP data PDU，而不用于发送PDCP control PDU；第二PDCP实体用于发送PDCP control PDU，而不用于发送PDCP data PDU。相应的，在第二通信设备侧，第五PDCP实体用于接收PDCP data PDU，而不用于接收PDCP control PDU；第六PDCP实体用于接收PDCP control PDU，而不用于接收PDCP data PDU。
由于第一通信设备侧的实现与第二通信设备侧的实现相对应，以下主要对第一通信设备侧的实现进行详细介绍，第二通信设备侧的具体实现可以参考第一通信设备侧的具体实现。
第一PDCP实体发送PDCP data PDU与第二PDCP实体发送的PDCP control PDU关联，是指：第二PDCP实体发送的PDCP control PDU是用于控制第一PDCP实体发送PDCP data PDU的传输，或者说，第一PDCP实体发送PDCP data PDU与第二PDCP实体发送的PDCP control PDU原本应当在同一PDCP实体传输，但它们被分离到两个不同的PDCP实体上传输。
应理解，第一PDCP实体发送的PDCP control PDU与第二PDCP实体发送的PDCP data PDU关联，也可以描述为第一PDCP实体与第二PDCP实体关联。另外，为了便于描述，用于传输PDCP data PDU的PDCP实体以下可称之为数据(data)PDCP实体，用于传输PDCP control PDU的PDCP实体以下可称之为控制(control)PDCP实体。
可选的，第一通信设备可以获取配置信息。其中，配置信息可以用于指示哪些PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离。进一步的，配置信息还可以用于指示哪些PDCP实体是data PDCP实体(即用于发送PDCP data PDU)、哪些PDCP实体是control PDCP实体(即用于发送PDCP control PDU)、以及data PDCP实体和control PDCP实体关联关系。相应的，第一通信设备可以根据配置信息确定：哪些PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离、哪些PDCP实体是data PDCP实体、哪些PDCP实体是control PDCP实体、以及data PDCP实体和control PDCP实体关联关系等。
第一通信设备获取配置信息的具体方式，例如，第一通信设备是网络设备，第二通信设备是终端，则第一通信设备可以生成配置信息，另外还可以将配置信息发送给第二通信设备；或者例如，第一通信设备是终端，第二通信设备是网络设备，则第二通信设备可以生成配置信息，第一通信设备从第二通信设备接收配置信息。
可选的，配置信息的配置粒度可以由PDCP实体确定，即一个PDCP实体单独对应一个配置信息。
以第一通信设备是终端，第一通信设备从网络设备接收的配置信息为例，配置信息可以包括：
1)针对第一PDCP实体的第一配置信息，第一配置信息具体可以携带：
A、第一指示信息，第一指示信息用于指示：第一PDCP实体的PDCP data PDU的传 输实体与PDCP control PDU的传输实体分离，或者，第一PDCP实体的传输模式为TM。
第一配置信息可以显式指示第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，即第一配置信息直接指示第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离。
第一配置信息也可以隐式指示PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，例如第一配置信息指示第一PDCP实体的传输模式为TM，则第一PDCP实体可根据TM确定自身仅用于传输PDCP data PDU，所以可进一步确定自身的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离。
B、第二指示信息，用于指示：第一PDCP实体用于传输PDCP data PDU；
C、第四指示信息，用于指示：第一PDCP实体传输的PDCP data PDU与第二PDCP实体传输的PDCP control PDU关联。
2)针对第二PDCP实体的第二配置信息，第二配置信息具体可以携带：
A、第三指示信息，用于指示：第二PDCP实体用于传输PDCP control PDU。
B、第五指示信息，用于指示第二PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离；
C、第六指示信息，第二PDCP实体传输的PDCP control PDU与第一PDCP实体传输的PDCP data PDU关联。
应理解，实际应用中，配置信息中可以仅携带上述六种信息中的部分而非全部，例如：在第一配置信息中已经携带了第一指示信息、第二指示信息、第四指示信息的情况下，第二配置信息可以不用携带第五指示信息和第六指示信息；反之，在第二配置信息中已经携带了第三指示信息、第五指示信息、第六指示信息的情况下，第二配置信息可以不用携带第一指示信息和第四指示信息，如此可以节省配置开销。
应理解，上述各种指示信息，在物理实现上，可以是多个信元(information element，IE)，也可以是同一个信元，本申请不做限制。例如，配置信息包含多个信元，而每个信元只对应上述一种指示信息，不同信元对应不同指示信息；或者例如，配置信息包含一个或多个信元，其中第一信元可以同时对应上述至少两种指示信息。
需要说明的是，以上均是以两个PDCP实体(即第一PDCP实体和第二PDCP实体)为例，而实际上，第一通信设备上可以有更多的PDCP实体。
在第一通信设备中PDCP实体的数量多于2个时，data PDCP实体与control PDCP实体的关联关系，可以是一对一的关联关系(即一个data PDCP实体关联一个control PDCP实体，不同的data PDCP实体关联不同的control PDCP实体)。具体例如：第一通信设备的第一PDCP实体发送第一PDCP data PDU；第一通信设备的第二PDCP实体发送第一PDCP control PDU；第一通信设备的第三PDCP实体发送第二PDCP data PDU；第一通信设备的第四PDCP实体发送第二PDCP control PDU。其中，第一PDCP control PDU与第一PDCP data PDU关联，第二PDCP control PDU与第二PDCP data PDU关联，第三PDCP实体、第四PDCP实体、第一PDCP实体、第二PDCP实体中任意两个实体均不同。
或者，data PDCP实体与control PDCP实体的关联关系，也可以是多对一的关联关系(即多个data PDCP实体关联同一个control PDCP实体)。具体例如：第一通信设备的第一PDCP实体发送第一PDCP data PDU；第一通信设备的第二PDCP实体发送第一PDCP control PDU；第一通信设备的第三PDCP实体发送第二PDCP data PDU；第一通信设备的 第二PDCP实体发送第二PDCP control PDU。其中，第一PDCP control PDU与第一PDCP data PDU关联，第二PDCP control PDU与第二PDCP data PDU关联，第三PDCP实体、第一PDCP实体、第二PDCP实体中任意两个实体不同。
在第一通信设备中PDCP实体的数量多于2个时，各PDCP实体的配置信息可以参考上文第一PDCP实体或第二PDCP实体的配置信息，此处不再赘述。
进一步的，当data PDCP实体与control PDCP实体的关联关系是多对一关联关系时，网络设备还可以配置control PDCP实体在PDCP control PDU中携带该PDCP control PDU对应的data PDCP实体的标识和/或该PDCP control PDU对应的PDCP data PDU的标识，以便接收端区分同一control PDCP实体中的不同PDCP control PDU。
沿用上文“第一通信设备的第一PDCP实体发送第一PDCP data PDU；第一通信设备的第二PDCP实体发送第一PDCP control PDU；第一通信设备的第三PDCP实体发送第二PDCP data PDU；第一通信设备的第二PDCP实体发送第二PDCP control PDU”的例子，则第一PDCP control PDU中可以携带第一PDCP实体的标识或者第一PDCP data PDU的标识，第二PDCP control PDU中可以携带第三PDCP实体的标识或者第二PDCP data PDU的标识。相应的，第二通信设备接收到第一PDCP data PDU、第一PDCP control PDU、第二PDCP data PDU、第二PDCP control PDU之后，就可以根据第一PDCP control PDU中携带的第一PDCP实体的标识或者第一PDCP data PDU的标识确定第一PDCP control PDU与第一PDCP data PDU关联，以及根据第二PDCP control PDU中携带的第三PDCP实体的标识或者第二PDCP data PDU的标识确定第二PDCP control PDU与第二PDCP data PDU关联。
基于上述方案，PDCP data PDU与PDCP control PDU解耦，通过非同一PDCP实体发送，如此可以使得PDCP实体采用TM模式发送PDCP data PDU，进而减少PDCP data PDU的头开销，节省空口开销。
参见图10C，为本申请实施例提供的另一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S101C、第一通信设备的第一PDCP实体发送第一PDCP data PDU，相应的，第二通信设备的第二PDCP实体接收第一通信设备的第一PDCP实体发送的第一PDCP data PDU。
S102C、第一通信设备的RRC/NAS/SDAP/RLC/MAC/PHY层的实体发送第一PDCP control PDU，相应的，第二通信设备的非PDCP层(例如RRC/NAS/SDAP/RLC/MAC/PHY层)的实体接收第一通信设备的非PDCP层(例如RRC/NAS/SDAP/RLC/MAC/PHY层)的实体发送的第一PDCP control PDU。
其中，第一PDCP control PDU与第一PDCP data PDU关联。此处第一PDCP control PDU与第一PDCP data PDU关联的含义可参考上文相关介绍，这里不再赘述。
同理，当同一RRC/NAS/SDAP/RLC/MAC/PHY层的实体发送多个PDCP实体对应的PDCP control PDU时，需要在PDCP control PDU中携带对应的PDCP实体的标识和/或对应的PDCP data PDU的标识，以便区分同一RRC/NAS/SDAP/RLC/MAC/PHY层的实体中的不同PDCP control PDU。
基于上述方案，PDCP data PDU与PDCP control PDU解耦，通过其它层的实体发送PDCP control PDU，如此可以使得PDCP实体采用TM模式发送PDCP data PDU，进而减少PDCP data PDU的头开销，节省空口开销。
一种可能的实施例中，PDCP实体和RLC实体可以同时支持TM，以省去PDCP层和 RLC层的所有头开销。
当PDCP实体和RLC实体都支持TM时，则PDCP data PDU和RLC data PDU中都不携带SN和SO。这将导致PDCP层和RLC层的部分功能缺失，例如包括但不限于以下几种功能：1)PDCP加解密：因为加密和解密均需要依赖PDCP SN(即PDCP头中的SN)作为输入，如果没有PDCP SN，则无法完成PDCP SN；2)PDCP重排序和按序递交(Reordering and in-order delivery)：因为接收端PDCP实体需要根据PDCP SN来进行重排序、并按序递交给上层实体，如果没有PDCP SN，则无法完成重排序和按序递交；3)PDCP重复丢弃(Duplicate discarding)：因为接收端的PDCP实体需要根据PDCP头中携带的PDCP SN来判断不同PDCP PDU是否是同一个数据包的多份复制包、从而无法准确丢弃重复包，如果没有PDCP SN，则无法完成重复丢弃；4)RLC SDU分段：因为接收端的RLC实体需要根据RLC SN(即RLC头中的SN)和SO才能对分段进行正确合并，如果没有RLC SN，则无法正确合并。应理解，以上四种仅为举例而非限定，实际还可以有更多的功能依赖SN和SO。
鉴于此，本实施例提供的以下方法，可以实现PDCP实体和RLC实体都支持TM，同时接收端可以获得PDCP data PDU和RLC data PDU对应的SN。
参见图11A，为本申请实施例提供的另一种通信方法的流程图，在下文的介绍过程中，以将该方法应用在图5所示的应用场景为例。该方法的流程介绍如下：
S111、第二通信设备根据SN与时域位置(或时域范围)的映射关系、数据包对应的SN，确定数据包对应的时域位置；其中，第二通信设备的PDCP实体和RLC实体的传输模式均为TM。
第二通信设备可以是图5所示场景中的任一设备，例如是基站，或者例如是终端，本申请不做限制。数据包可以是第二通信设备PDCP层上层实体下发的数据包，例如SDAP层下发的数据包，即PDCP SDU。
在本申请实施例中，根据SN与时域位置的映射关系、数据包对应的SN，确定数据包对应的时域位置的操作，可以是第二通信设备上任一协议层对应的实体执行。例如，第二通信设备的PDCP实体向第二通信设备的MAC实体传递数据包对应的SN，进而第二通信设备的MAC实体根据SN与时域位置的映射关系、数据包对应的SN，确定数据包对应的时域位置。或者例如，第二通信设备的PDCP实体根据SN与时域位置的映射关系、数据包对应的SN，确定数据包对应的时域位置，进而第二通信设备的PDCP实体向第二通信设备的MAC实体传递数据包对应的时域位置。应理解，以上两种方式仅为示例而非限定，在实际应用中，该操作还可以由其它层(如RLC层)执行，本申请不做具体限制。
S112、第二通信设备在数据包对应的时域位置发送数据包；相应的，第一通信设备在该时域位置接收该数据包；其中，第一通信设备的PDCP实体和RLC实体的传输模式均为TM。
当然，实际传输过程还包括其它层(如MAC层、PHY层等)的处理过程，对于其它层的处理过程，可以参考上文相关描述，此处不再赘述。
需要注意的是，如果第二通信设备检测到当前时间已经超出数据包对应的时域位置但还未发送该数据包，或者第二通信设备检测到当前时间已经超出数据包对应的时域位置但数据包未成功发送，则第二通信设备可以丢弃该数据包，即不再发送，以免该数据包落在其它数据包对应的时域位置，对第一通信设备造成混淆。
S113、第一通信设备根据接收该数据包的时域位置、SN与时域位置的映射关系，确定该数据包对应的SN。
第一通信设备可以是能够与第二通信设备通信的任一设备，例如是基站，或者例如是终端，本申请不做限制。
在本申请实施例中，根据接收数据包的时域位置、SN与时域位置的映射关系，确定数据包对应的SN的操作，可以是第一通信设备上任一协议层对应的实体执行。例如，第一通信设备的MAC实体向第一通信设备的PDCP实体传递数据包的时域位置，进而第一通信设备的PDCP实体根据MAC实体接收数据包的时域位置、SN与时域位置的映射关系，确定数据包对应的SN。例如，第一通信设备的MAC实体根据接收数据包的时域位置、SN与时域位置的映射关系，确定数据包对应的SN，进而第一通信设备的MAC实体向第一通信设备的PDCP实体传递数据包对应的SN。应理解，以上两种方式仅为示例而非限定，在实际应用中，该操作还可以由其它层(如RLC层)执行，本申请不做具体限制。
当第一通信设备根据接收该数据包的时域位置、SN与时域位置的映射关系确定该数据包对应的SN之后，就可以利用该SN作为PDCP SN进行其他PDCP操作，例如PDCP解密、PDCP重排序等。
可选的，网络设备可以配置序列号与时域位置的映射关系。例如，第二通信设备是网络设备，第一通信设备是终端，则第二通信设备配置序列号与时域位置的映射关系，并将该序列号与时域位置的映射关系发送给第一通信设备，进而第二通信设备按照该映射关系发送数据包，第一通信设备按照该映射关系接收数据包。或者例如，第二通信设备是终端，第一通信设备是网络设备，则第一通信设备配置序列号与时域位置的映射关系，并将该序列号与时域位置的映射关系发送给第二通信设备，进而第二通信设备按照该映射关系发送数据包，第一通信设备按照该映射关系接收数据包。
可选的，时域位置的配置粒度可以由系统帧号(System frame number，SFN)、子帧号(subframe number)、时隙号(slot number)或符号(symbol number)等中的至少一项确定。
为了便于描述，一个数据包对应的时域位置或时域范围，可以描述为一个传输时间间隔(transmission time interval，TTI)。例如，参见图11B，基站分别在TTI-1、TTI-2、TTI-3发送数据包1、数据包2、数据包3，相应的，终端分别在TTI-1、TTI-2、TTI-3接收数据包1、数据包2、数据包3。需要注意的是，如果有数据包需要重传，则该数据包重传的时机也是在该数据包对应TTI范围内。图11B举例的是单载波场景，本申请同样可以适用于双载波或多载波场景，例如图11C所示，基站在TTI-1中，在组成载波(component carrier，CC)1和CC2上发送数据包1；基站在TTI-2中，在CC1和CC2上发送数据包2；基站在TTI-3中，在CC1和CC2上发送数据包3。
应理解，上述是以SN和时域位置存在映射关系为例，在具体实施时，如果数据包存在分段，则也可以将SO与时域位置进行映射，第一通信设备根据SO与时域位置的映射关系和接收分段的时间确定各个分段对应的SO。
基于上述方案，可以实现PDCP实体和RLC实体都支持TM，同时第一通信设备可以获得PDCP data PDU和RLC data PDU对应的SN，进而在实现节省空口开销的同时，保证数据传输的可靠性。
可以理解的是，本申请提供的上述各实施例可以分别单独实施，也可以相互结合实施。 结合实施的情况，例如：可以将上述图6A所示的方案结合到图9A所示的方案中实施，即PDCP层中的SO可以替换为索引，如此可以进一步节省空口开销。例如，可以将上述图8A、图10B以及图11A所示的方案结合实施，则可以实现PDCP层和RLC层均支持TM模式(均不携带SN)，同时保证接收端可以获得数据包对应的SN。当然，以上仅仅是对部分结合方式的举例，实际应用时还可以有更多的结合方式，此处不再详述。
可以理解的是，为了实现上述实施例中功能，各通信装置包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图12和图13为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，通信装置可以是如图5所示的终端120a-120j中的一个，也可以是如图5所示的基站110a或110b，还可以是应用于终端或基站的模块(如芯片)。
示例性的，当通信装置1200用于实现图6A所示的方法实施例中第一通信设备的功能时：
收发模块1201用于：获取RLC SDU；
处理模块1202用于：根据RLC SDU生成RLC PDU；其中，RLC PDU包括头部和数据，数据为RLC SDU的数据中的第一分段，头部包括序列号和第一索引，序列号用于标识RLC SDU，第一索引用于标识第一分段在RLC SDU的分段中的编号，RLC SDU中的不同分段分别对应不同的索引；
收发模块1201还用于：发送RLC PDU。
当通信装置1200用于实现图6A所示的方法实施例中第二通信设备的功能时：
收发模块1201用于：接收RLC PDU；其中，RLC PDU包括头部和数据，数据为RLC SDU的第一分段，头部包括序列号和第一索引，序列号用于标识RLC SDU，第一索引用于标识第一分段在RLC SDU的分段中的编号，RLC SDU中的不同分段分别对应不同的索引；
处理模块1202用于：根据序列号和第一索引确定RLC PDU的数据是RLC SDU的分段中的第一分段。
有关上述处理模块1202和收发模块1201更详细的描述可以直接参考图6A所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当通信装置1200用于实现图7所示的方法实施例中第一通信设备的功能时：
处理模块1202用于：获取RLC SDU；根据配置信息确定RLC SDU不分段，其中配置信息用于指示RLC SDU不分段；发根据RLC SDU生成RLC PDU；其中，RLC PDU的数据为完整的RLC SDU；
收发模块1201用于：发送RLC SDU。
当通信装置1200用于实现图7所示的方法实施例中第二通信设备的功能时：
收发模块1201用于：接收RLC PDU；
处理模块1202用于：根据配置信息确定该RLC PDU的数据为完整的RLC SDU。
有关上述处理模块1202和收发模块1201更详细的描述可以直接参考图7所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当通信装置1200用于实现图8A所示的方法实施例中第一通信设备(以第一通信设备是终端为例)的功能时：
收发模块1201，用于获取无线承载的配置信息，其中配置信息用于指示无线承载对应的RLC实体的传输模式为透明模式；
处理模块1202用于：基于配置信息，将无线承载对应的RLC实体的传输模式配置为透明模式。
有关上述处理模块1202和收发模块1201更详细的描述可以直接参考图8A所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当通信装置1200用于实现图9A所示的方法实施例中第一通信设备的功能时：
处理模块1202，用于获取PDCP SDU；根据PDCP SDU生成PDCP PDU；其中，PDCP PDU包括头部和数据，数据为PDCP SDU中的一个分段，头部包括序列号，序列号用于标识PDCP SDU，头部还包括分段偏移或索引，分段偏移用于指示一个分段的第一个字节在PDCP SDU中的字节偏移量，索引用于标识一个分段在RLC SDU的分段中的编号；
收发模块1201，用于发送PDCP SDU。
当通信装置1200用于实现图9A所示的方法实施例中第二通信设备的功能时：
收发模块1201用于：接收多个RLC PDU；其中，多个PDCP PDU中的每个PDCP PDU包括头部和数据，数据为PDCP SDU中的一个分段，头部包括序列号，序列号用于标识PDCP SDU，头部还包括分段偏移或索引，分段偏移用于指示一个分段的第一个字节在PDCP SDU中的字节偏移量，索引用于标识一个分段在RLC SDU的分段中的编号；其中，多个PDCP PDU对应的序列号相同；
处理模块1202用于：根据多个PDCP PDU生成一个PDCP SDU。
有关上述处理模块1202和收发模块1201更详细的描述可以直接参考图9A所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当通信装置1200用于实现图10B所示的方法实施例中第一通信设备的功能时：
处理模块1202，用于创建第一PDCP实体和第二PDCP实体；
收发模块1201，用于基于第一PDCP实体发送第一PDCP data PDU；基于第二PDCP实体发送第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联，第一PDCP实体与第二PDCP实体不同。
当通信装置1200用于实现图10B所示的方法实施例中第二通信设备的功能时：
处理模块1202，用于创建第五PDCP实体和第六PDCP实体；
收发模块1201，用于接收第一通信设备的第一PDCP实体发送的第一PDCP data PDU；接收第一通信设备的第二PDCP实体发送的第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联，第一PDCP实体与第二PDCP实体不同；
处理模块1202，用于基于第五PDCP实体处理第一PDCP control PDU、基于第六PDCP实体处理第一PDCP data PDU。
有关上述处理模块1202和收发模块1201更详细的描述可以直接参考图10B所示的方 法实施例中相关描述直接得到，这里不加赘述。
示例性的，当通信装置1200用于实现图11A所示的方法实施例中第一通信设备的功能时：
收发模块1201，用于接收数据包；其中，第一通信设备的PDCP实体和RLC实体的传输模式均为透明模式；
处理模块1202，用于根据接收数据包的时域位置、序列号与时域位置的映射关系，确定数据包对应的序列号。
当通信装置1200用于实现图11A所示的方法实施例中第二通信设备的功能时：
处理模块1202，用于根据序列号与时域位置的映射关系、数据包对应的序列号，确定数据包对应的时域位置；其中，第二通信设备的PDCP实体和RLC实体的传输模式均为透明模式；
收发模块1201，用于在数据包对应的时域位置发送第一数据包。
有关上述处理模块1202和收发模块1201更详细的描述可以直接参考图11A所示的方法实施例中相关描述直接得到，这里不加赘述。
如图13所示，通信装置1300包括处理器1310和接口电路1320。处理器1310和接口电路1320之间相互耦合。可以理解的是，接口电路1320可以为收发器或输入输出接口。
可选的，通信装置1300还可以包括存储器1330，用于存储处理器1310执行的指令或存储处理器1310运行指令所需要的输入数据或存储处理器1310运行指令后产生的数据。
当通信装置1300用于实现图12所示的装置时，处理器1310用于实现上述处理模块1202的功能，接口电路1320用于实现上述收发模块1201的功能。
当上述通信装置为应用于终端的芯片时，该终端芯片实现上述方法实施例中终端的功能。该终端芯片从终端中的其它模块(如射频模块或天线)接收信息，该信息是基站发送给终端的；或者，该终端芯片向终端中的其它模块(如射频模块或天线)发送信息，该信息是终端发送给基站的。
当上述通信装置为应用于基站的模块时，该基站模块实现上述方法实施例中基站的功能。该基站模块从基站中的其它模块(如射频模块或天线)接收信息，该信息是终端发送给基站的；或者，该基站模块向基站中的其它模块(如射频模块或天线)发送信息，该信息是基站发送给终端的。这里的基站模块可以是基站的基带芯片，也可以是DU或其他模块，这里的DU可以是开放式无线接入网(open radio access network，O-RAN)架构下的DU。
基于同一技术构思，本申请实施例还提供一种芯片，参见图14，该芯片可以包括逻辑电路和输入输出接口。可选的，还可以包括存储器。其中，输入输出接口可以用于接收代码指令(代码指令存储在存储器中，可以直接从存储器读取，或也可以经过其他器件从存储器读取)并传输至所述逻辑电路；所述逻辑电路，可以用于运行所述代码指令以执行上述方法实施例中的方法。
或者，输入输出接口也可以为逻辑电路与收发机之间的信号传输接口电路。例如，在发送场景中，所述逻辑电路用于执行XX以得到Y数据(XX为非空口操作，包括但不限于确定，判断、处理、计算、查找、比较等操作)；所述输入输出接口可以用于将Y数据发送至发射机(发射机用于执行空口上的发送操作)。又例如，在接收场景中，所述输入输出接口可以用于从接收机接收Z数据(接收机用于执行空口上的接收操作)，并将所述Z 数据发送至所述逻辑电路；所述逻辑电路用于对所述Z数据做XX处理(XX为非空口操作，包括但不限于确定，判断、处理、计算、查找、比较等操作)。
示例性的，当芯片用于实现图6A所示的方法实施例中第一通信设备的功能时：
逻辑电路用于：获取RLC SDU；根据RLC SDU生成RLC PDU；其中，RLC PDU包括头部和数据，数据为RLC SDU的数据中的第一分段，头部包括序列号和第一索引，序列号用于标识RLC SDU，第一索引用于标识第一分段在RLC SDU的分段中的编号，RLC SDU中的不同分段分别对应不同的索引；
输入输出接口用于：输出RLC PDU。
当芯片用于实现图6A所示的方法实施例中第二通信设备的功能时：
输入输出接口用于：输入RLC PDU；其中，RLC PDU包括头部和数据，数据为RLC SDU的第一分段，头部包括序列号和第一索引，序列号用于标识RLC SDU，第一索引用于标识第一分段在RLC SDU的分段中的编号，RLC SDU中的不同分段分别对应不同的索引；
逻辑电路用于：根据序列号和第一索引确定RLC PDU的数据是RLC SDU的分段中的第一分段。
有关上述逻辑电路和输入输出接口更详细的描述可以直接参考图6A所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当芯片用于实现图7所示的方法实施例中第一通信设备的功能时：
逻辑电路用于：获取RLC SDU；根据配置信息确定RLC SDU不分段，其中配置信息用于指示RLC SDU不分段；发根据RLC SDU生成RLC PDU；其中，RLC PDU的数据为完整的RLC SDU；
输入输出接口用于：输出RLC SDU。
当芯片用于实现图7所示的方法实施例中第二通信设备的功能时：
输入输出接口用于：输入RLC PDU；
逻辑电路用于：根据配置信息确定该RLC PDU的数据为完整的RLC SDU。
有关上述逻辑电路和输入输出接口更详细的描述可以直接参考图7所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当芯片用于实现图8A所示的方法实施例中第一通信设备(以第一通信设备是终端为例)的功能时：
输入输出接口，用于输入无线承载的配置信息，其中配置信息用于指示无线承载对应的RLC实体的传输模式为透明模式；
逻辑电路用于：基于配置信息，将无线承载对应的RLC实体的传输模式配置为透明模式。
有关上述逻辑电路和输入输出接口更详细的描述可以直接参考图8A所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当芯片用于实现图9A所示的方法实施例中第一通信设备的功能时：
逻辑电路，用于输入PDCP SDU；根据PDCP SDU生成PDCP PDU；其中，PDCP PDU包括头部和数据，数据为PDCP SDU中的一个分段，头部包括序列号，序列号用于标识PDCP SDU，头部还包括分段偏移或索引，分段偏移用于指示一个分段的第一个字节在PDCP SDU中的字节偏移量，索引用于标识一个分段在RLC SDU的分段中的编号；
输入输出接口，用于输出PDCP SDU。
当芯片用于实现图9A所示的方法实施例中第二通信设备的功能时：
输入输出接口用于：输入多个RLC PDU；其中，多个PDCP PDU中的每个PDCP PDU包括头部和数据，数据为PDCP SDU中的一个分段，头部包括序列号，序列号用于标识PDCP SDU，头部还包括分段偏移或索引，分段偏移用于指示一个分段的第一个字节在PDCP SDU中的字节偏移量，索引用于标识一个分段在RLC SDU的分段中的编号；其中，多个PDCP PDU对应的序列号相同；
逻辑电路用于：根据多个PDCP PDU生成一个PDCP SDU。
有关上述逻辑电路和输入输出接口更详细的描述可以直接参考图9A所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当芯片用于实现图10B所示的方法实施例中第一通信设备的功能时：
逻辑电路，用于创建第一PDCP实体和第二PDCP实体；
输入输出接口，用于基于第一PDCP实体输出第一PDCP data PDU；基于第二PDCP实体输出第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联，第一PDCP实体与第二PDCP实体不同。
当芯片用于实现图10B所示的方法实施例中第二通信设备的功能时：
逻辑电路，用于创建第五PDCP实体和第六PDCP实体；
输入输出接口，用于输入第一通信设备的第一PDCP实体发送的第一PDCP data PDU；输入第一通信设备的第二PDCP实体发送的第一PDCP control PDU；其中，第一PDCP control PDU与第一PDCP data PDU关联，第一PDCP实体与第二PDCP实体不同；
逻辑电路，用于基于第五PDCP实体处理第一PDCP control PDU、基于第六PDCP实体处理第一PDCP data PDU。
有关上述逻辑电路和输入输出接口更详细的描述可以直接参考图10B所示的方法实施例中相关描述直接得到，这里不加赘述。
示例性的，当芯片用于实现图11A所示的方法实施例中第一通信设备的功能时：
输入输出接口，用于输入数据包；其中，第一通信设备的PDCP实体和RLC实体的传输模式均为透明模式；
逻辑电路，用于根据输入数据包的时域位置、序列号与时域位置的映射关系，确定数据包对应的序列号。
当芯片用于实现图11A所示的方法实施例中第二通信设备的功能时：
逻辑电路，用于根据序列号与时域位置的映射关系、数据包对应的序列号，确定数据包对应的时域位置；其中，第二通信设备的PDCP实体和RLC实体的传输模式均为透明模式；
输入输出接口，用于在数据包对应的时域位置输出第一数据包。
有关上述逻辑电路和输入输出接口更详细的描述可以直接参考图11A所示的方法实施例中相关描述直接得到，这里不加赘述。
基于同一技术构思，本申请实施例还提供一种计算机可读存储介质，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现上述方法实施例中的方法。
基于同一技术构思，本申请实施例还提供一种计算机程序产品，当其在计算机上运行 时，使得如上述方法实施例中的方法被执行。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于基站或终端中。当然，处理器和存储介质也可以作为分立组件存在于基站或终端中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
根据说明书是否用到可选：本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。“包括A，B和C中的至少一个”可以表示：包括A；包括B；包括C；包括A和B；包括A和C；包括B和C；包括A、B和C。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (36)

  1. 一种通信方法，其特征在于，包括：
    第一通信设备获取无线承载的配置信息，其中所述配置信息用于指示所述无线承载对应的无线链路控制RLC实体的传输模式为透明模式；
    所述第一通信设备基于所述配置信息，将所述无线承载对应的RLC实体的传输模式配置为透明模式。
  2. 如权利要求1所述的方法，其特征在于，所述无线承载为数据无线承载、信令无线承载或计算无线承载中的一种。
  3. 一种通信方法，其特征在于，包括：
    第二通信设备生成无线承载的配置信息，其中所述配置信息用于指示所述无线承载对应的RLC实体的传输模式为透明模式；
    所述第二通信设备发送所述配置信息。
  4. 如权利要求3所述的方法，其特征在于，所述无线承载为数据无线承载、计算无线承载中的一种。
  5. 一种通信方法，其特征在于，包括：
    第一通信设备的第一分组数据汇聚层协议PDCP实体发送第一分组数据汇聚层协议数据协议数据单元PDCP data PDU；
    所述第一通信设备的第二PDCP实体发送分组数据汇聚层协议控制协议数据单元第一PDCP control PDU；
    其中，所述第一PDCP control PDU与所述第一PDCP data PDU关联，所述第一PDCP实体与所述第二PDCP实体不同。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一通信设备获取配置信息；
    所述第一通信设备根据所述配置信息确定所述第一PDCP实体发送所述第一PDCP data PDU、所述第二PDCP实体发送所述第一PDCP control PDU。
  7. 如权利要求6所述的方法，其特征在于，所述配置信息包括：
    第一指示信息，用于指示：所述第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，或者，所述第一PDCP实体的传输模式为透明模式。
  8. 如权利要求7所述的方法，其特征在于，所述配置信息还包括以下至少一种：
    第二指示信息，用于指示：所述第一PDCP实体用于传输PDCP data PDU；
    第三指示信息，用于指示：所述第二PDCP实体用于传输PDCP control PDU；
    第四指示信息，用于指示：所述第二PDCP实体传输的PDCP control PDU与所述第一PDCP实体传输的PDCP data PDU关联。
  9. 如权利要求5-8任一项所述的方法，其特征在于，还包括：
    所述第一通信设备的第三PDCP实体发送第二PDCP data PDU；
    所述第一通信设备的第四PDCP实体发送第二PDCP control PDU；
    其中，所述第二PDCP control PDU与所述第二PDCP data PDU关联，所述第三PDCP实体、所述第四PDCP实体、所述第一PDCP实体、所述第二PDCP实体中任意两个实体不同。
  10. 如权利要求5-8任一项所述的方法，其特征在于，还包括：
    所述第一通信设备的第三PDCP实体发送第二PDCP data PDU；
    所述第一通信设备的所述第二PDCP实体发送第二PDCP control PDU；
    其中，所述第二PDCP control PDU与所述第二PDCP data PDU关联，所述第三PDCP实体、所述第一PDCP实体、所述第二PDCP实体中任意两个实体不同。
  11. 如权利要求10所述的方法，其特征在于，
    所述第一PDCP control PDU中携带所述第一PDCP实体的标识；
    所述第二PDCP control PDU中携带所述第三PDCP实体的标识或所述第二PDCP data PDU的标识。
  12. 一种通信方法，其特征在于，包括：
    第二通信设备接收第一通信设备的第一PDCP实体发送的第一PDCP data PDU；
    所述第二通信设备接收所述第一通信设备的第二PDCP实体发送的第一PDCP control PDU；
    其中，所述第一PDCP control PDU与所述第一PDCP data PDU关联，所述第一PDCP实体与所述第二PDCP实体不同。
  13. 如权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第二通信设备向所述第一通信设备发送配置信息。
  14. 如权利要求13所述的方法，其特征在于，所述配置信息包括：
    第一指示信息，用于指示：所述第一PDCP实体的PDCP data PDU的传输实体与PDCP control PDU的传输实体分离，或者，所述第一PDCP实体的传输模式为透明模式。
  15. 如权利要求14所述的方法，其特征在于，所述配置信息还包括以下至少一种：
    第二指示信息，用于指示：所述第一PDCP实体用于传输PDCP data PDU；
    第三指示信息，用于指示：所述第二PDCP实体用于传输PDCP control PDU；
    第四指示信息，用于指示：所述第二PDCP实体传输的PDCP control PDU与所述第一PDCP实体传输的PDCP data PDU关联。
  16. 如权利要求12-15任一项所述的方法，其特征在于，还包括：
    所述第二通信设备接收所述第一通信设备的第三PDCP实体发送的第二PDCP data PDU；
    所述第二通信设备接收所述第一通信设备的第四PDCP实体发送的第二PDCP control PDU；
    其中，所述第二PDCP control PDU与所述第二PDCP data PDU关联，所述第三PDCP实体、所述第四PDCP实体、所述第一PDCP实体、所述第二PDCP实体中任意两个实体不同。
  17. 如权利要求12-15任一项所述的方法，其特征在于，还包括：
    所述第二通信设备接收所述第一通信设备的第三PDCP实体发送的第二PDCP data PDU；
    所述第二通信设备接收所述第一通信设备的所述第二PDCP实体发送的第二PDCP control PDU；
    其中，所述第二PDCP control PDU与所述第二PDCP data PDU关联，所述第三PDCP实体、所述第一PDCP实体、所述第二PDCP实体中任意两个实体不同。
  18. 如权利要求17所述的方法，其特征在于，
    所述第一PDCP control PDU中携带所述第一PDCP实体的标识；
    所述第二PDCP control PDU中携带所述第三PDCP实体的标识或所述第二PDCP data PDU的标识。
  19. 一种通信方法，其特征在于，包括：
    第一通信设备接收数据包；其中，所述第一通信设备的PDCP实体和RLC实体的传输模式均为透明模式；
    所述第一通信设备根据接收所述数据包的时域位置、序列号与时域位置的映射关系，确定所述数据包对应的序列号。
  20. 如权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第一通信设备的媒体接入控制实体向所述第一通信设备的所述PDCP实体传递所述数据包的时域位置；
    所述第一通信设备根据接收所述数据包的时域位置、序列号与时域位置的映射关系，确定所述数据包对应的序列号，包括：
    所述第一通信设备的所述PDCP实体根据所述媒体接入控制实体接收所述数据包的时域位置、序列号与时域位置的映射关系，确定所述数据包对应的序列号。
  21. 如权利要求19所述的方法，其特征在于，所述第一通信设备根据接收所述数据包的时域位置、序列号与时域位置的映射关系，确定所述数据包对应的序列号，包括：
    所述第一通信设备的媒体接入控制实体根据接收所述数据包的时域位置、序列号与时域位置的映射关系，确定所述数据包对应的序列号；
    所述方法还包括：
    所述第一通信设备的所述媒体接入控制实体向所述第一通信设备的所述PDCP实体传递所述数据包对应的序列号。
  22. 如权利要求19-21任一项所述的方法，其特征在于，还包括：
    所述第一通信设备从网络设备获取所述序列号与时域位置的映射关系。
  23. 一种通信方法，其特征在于，包括：
    第二通信设备根据序列号与时域位置的映射关系、数据包对应的序列号，确定所述数据包对应的时域位置；其中，所述第二通信设备的PDCP实体和RLC实体的传输模式均为透明模式；
    所述第二通信设备在所述数据包对应的时域位置发送所述第一数据包。
  24. 如权利要求23所述的方法，其特征在于，所述方法还包括：
    所述第二通信设备的所述PDCP实体向所述第二通信设备的媒体接入控制实体传递所述数据包对应的序列号；
    所述第二通信设备根据序列号与时域位置的映射关系、数据包对应的序列号，确定所述数据包对应的时域位置，包括：
    所述第二通信设备的所述媒体接入控制实体根据序列号与时域位置的映射关系、数据包对应的序列号，确定所述数据包对应的时域位置。
  25. 如权利要求23所述的方法，其特征在于，所述第二通信设备根据序列号与时域位置的映射关系、数据包对应的序列号，确定所述数据包对应的时域位置，包括：
    所述第二通信设备的所述PDCP实体根据序列号与时域位置的映射关系、数据包对应 的序列号，确定所述数据包对应的时域位置；
    所述方法还包括：
    所述第二通信设备的所述PDCP实体向所述第二通信设备的媒体接入控制实体传递所述数据包对应的时域位置。
  26. 如权利要求23-25任一项所述的方法，其特征在于，还包括：
    所述第二通信设备从网络设备获取所述序列号与时域位置的映射关系。
  27. 一种通信装置，其特征在于，包括：
    收发模块，用于获取无线承载的配置信息，其中所述配置信息用于指示所述无线承载对应的RLC实体的传输模式为透明模式；
    处理模块，用于基于所述配置信息，将所述无线承载对应的RLC实体的传输模式配置为透明模式。
  28. 一种通信装置，其特征在于，包括：
    处理模块，用于生成无线承载的配置信息，其中所述配置信息用于指示所述无线承载对应的RLC实体的传输模式为透明模式；
    收发模块，用于发送所述配置信息。
  29. 一种通信装置，其特征在于，包括：
    处理模块，用于建立第一PDCP实体和第二PDCP实体；
    收发模块，用于基于所述第一PDCP实体发送第一PDCP data PDU，以及基于所述第二PDCP实体发送第一PDCP control PDU；
    其中，所述第一PDCP control PDU与所述第一PDCP data PDU关联，所述第一PDCP实体与所述第二PDCP实体不同。
  30. 一种通信装置，其特征在于，包括：
    处理模块，用于建立第五PDCP实体和第六PDCP实体；
    收发模块，用于接收第一通信设备的第一PDCP实体发送的第一PDCP data PDU，以及用于接收所述第一通信设备的第二PDCP实体发送的第一PDCP control PDU；
    处理模块，用于基于所述第五PDCP实体处理所述第一PDCP data PDU以及基于所述第六PDCP实体处理所述第一PDCP control PDU；
    其中，所述第一PDCP control PDU与所述第一PDCP data PDU关联，所述第一PDCP实体与所述第二PDCP实体不同，所述第五PDCP实体与所述第六PDCP实体不同。
  31. 一种通信装置，其特征在于，包括：
    收发模块，用于接收数据包；其中，所述装置的PDCP实体和RLC实体的传输模式均为透明模式；
    处理模块，用于根据接收所述数据包的时域位置、序列号与时域位置的映射关系，确定所述数据包对应的序列号。
  32. 一种通信装置，其特征在于，包括：
    处理模块，用于根据序列号与时域位置的映射关系、数据包对应的序列号，确定所述数据包对应的时域位置；其中，所述装置的PDCP实体和RLC实体的传输模式均为透明模式；
    收发模块，用于在所述数据包对应的时域位置发送所述第一数据包。
  33. 一种通信装置，其特征在于，包括处理器和存储器；
    其中，所述处理器和所述存储器耦合，所述存储器用于存储计算机执行指令，所述处理器用于执行所述存储器所存储的计算机执行指令，以使所述通信装置执行如权利要求1至26任一项所述的方法。
  34. 一种芯片，其特征在于，包括逻辑电路和输入输出接口；
    其中，所述输入输出接口用于接收来自所述芯片之外的其它通信装置的信号并传输至所述逻辑电路或将来自所述逻辑电路的信号发送给所述芯片之外的其它通信装置，所述逻辑电路用于实现如权利要求1至26中任一项所述的方法。
  35. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至26中任一项所述的方法。
  36. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得如权利要求1至26任一项所述的方法被执行。
PCT/CN2022/107481 2021-08-03 2022-07-22 一种通信方法及装置 WO2023011219A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22851933.6A EP4380226A1 (en) 2021-08-03 2022-07-22 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110884514.8 2021-08-03
CN202110884514.8A CN115915253A (zh) 2021-08-03 2021-08-03 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2023011219A1 true WO2023011219A1 (zh) 2023-02-09

Family

ID=85155175

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/107481 WO2023011219A1 (zh) 2021-08-03 2022-07-22 一种通信方法及装置

Country Status (3)

Country Link
EP (1) EP4380226A1 (zh)
CN (1) CN115915253A (zh)
WO (1) WO2023011219A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018077043A1 (zh) * 2016-10-25 2018-05-03 中兴通讯股份有限公司 数据的传输方法和装置、用户设备及基站
CN110476445A (zh) * 2017-03-24 2019-11-19 诺基亚技术有限公司 利用分离承载的分组数据汇聚协议窗口
WO2020164533A1 (zh) * 2019-02-13 2020-08-20 华为技术有限公司 无线通信的方法、用户设备、网络设备及通信装置
CN111866796A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 用于获取无线承载配置的方法和装置
CN112313993A (zh) * 2018-06-18 2021-02-02 三星电子株式会社 用于移动通信系统中的高效分组重复传输的方法和装置
CN113079585A (zh) * 2020-01-03 2021-07-06 大唐移动通信设备有限公司 一种信息处理方法及终端

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018077043A1 (zh) * 2016-10-25 2018-05-03 中兴通讯股份有限公司 数据的传输方法和装置、用户设备及基站
CN110476445A (zh) * 2017-03-24 2019-11-19 诺基亚技术有限公司 利用分离承载的分组数据汇聚协议窗口
CN112313993A (zh) * 2018-06-18 2021-02-02 三星电子株式会社 用于移动通信系统中的高效分组重复传输的方法和装置
WO2020164533A1 (zh) * 2019-02-13 2020-08-20 华为技术有限公司 无线通信的方法、用户设备、网络设备及通信装置
CN111866796A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 用于获取无线承载配置的方法和装置
CN113079585A (zh) * 2020-01-03 2021-07-06 大唐移动通信设备有限公司 一种信息处理方法及终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Introducing TM DRB in PDCP", 3GPP DRAFT; R2-1805996 38323_CR(0005)_(REL-15)_INTRODUCING TM DRB IN PDCP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sanya, China; 20180416 - 20180420, 14 April 2018 (2018-04-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051429602 *

Also Published As

Publication number Publication date
EP4380226A1 (en) 2024-06-05
CN115915253A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
US10999890B2 (en) Data processing method, apparatus, and system
CN111971996A (zh) 利用服务数据适配协议层促进服务质量流重映射
WO2018165995A1 (zh) 一种数据处理方法及终端设备、基站
EP3737183B1 (en) Communication methods, apparatuses and computer-readable storage medium
WO2018059438A1 (zh) 消息传输方法、设备和系统
TWI791033B (zh) 無線通訊的方法、終端設備和網路設備
WO2018166517A1 (zh) 一种数据传输方法、数据发送设备及数据接收设备
WO2021218888A1 (zh) 通信方法和装置
US20220368494A1 (en) Uplink re-transmission with compact memory usage
US20220368782A1 (en) Baseband chip and method for layer 2 downlink data processing
US10880871B2 (en) Method and apparatus for asymmetrical up-link/down-link protocol stack and frame structure in a 5G NR communication system
KR102515923B1 (ko) 5ｇ ｎｒ 통신 시스템 내의 비대칭 업-링크/다운-링크 프로토콜 스택 및 프레임 구조를 위한 방법 및 장치
US20230075613A1 (en) Terminal device
WO2018103637A1 (zh) 数据处理的方法、发送设备和接收设备
WO2021155604A1 (zh) 信息处理方法及设备
WO2021051119A2 (en) Apparatus and method of layer 2 data processing using flexible layer 2 circuits
WO2020088255A1 (zh) 一种无线回传处理方法及通信装置
WO2023011219A1 (zh) 一种通信方法及装置
TWI685225B (zh) 通信方法和終端設備
WO2022137659A1 (ja) 端末及び通信方法
WO2021169732A1 (zh) 一种切换方法及通信装置
WO2018045521A1 (zh) 无线网络中传输信令的方法和装置
WO2021134639A1 (zh) 一种数据的反馈方法及装置
WO2020163849A1 (en) Multi-band single mac communication system
WO2020015617A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 22851933

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022851933

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022851933

Country of ref document: EP

Effective date: 20240228

NENP Non-entry into the national phase

Ref country code: DE