WO2018082433A1 - 一种进行数据发送和接收的方法及系统 - Google Patents

一种进行数据发送和接收的方法及系统 Download PDF

Info

Publication number
WO2018082433A1
WO2018082433A1 PCT/CN2017/105729 CN2017105729W WO2018082433A1 WO 2018082433 A1 WO2018082433 A1 WO 2018082433A1 CN 2017105729 W CN2017105729 W CN 2017105729W WO 2018082433 A1 WO2018082433 A1 WO 2018082433A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
pdu
module
rlc pdu
pdus
Prior art date
Application number
PCT/CN2017/105729
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 EP17867792.8A priority Critical patent/EP3537827A4/en
Priority to JP2019523796A priority patent/JP2019533395A/ja
Priority to KR1020197015912A priority patent/KR20190075119A/ko
Priority to US16/346,462 priority patent/US10986653B2/en
Publication of WO2018082433A1 publication Critical patent/WO2018082433A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1809—Selective-repeat protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors
    • H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
    • 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
    • H04W28/04—Error control
    • 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
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • 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
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a method and system for transmitting and receiving data.
  • the data transmission between the user equipment (UE) and the eNB (evolved base station) is usually through a PDCP (Packet Data Convergence Protocol) layer, an RLC (Radio Link Control) layer, The transmission of the MAC (Medium Access Control) layer and the PHY (Physical) layer, each layer performs different data processing.
  • the PDCP layer mainly performs security operations and header compression and decompression processing, such as encryption and integrity protection, ROHC (Robust Header Compression) compression and decompression, etc.; the RLC layer mainly performs segmentation cascading and sequential delivery of data.
  • FIG. 1 is a schematic diagram of a user plane protocol stack.
  • the main functions of the PDCP layer are security related operations (such as encryption/decryption, integrity protection/verification) and header compression/decompression processing.
  • the main function of the RLC layer is to complete segmentation, cascading and in-order delivery of data and ARQ.
  • the main function of the processing module is to perform uplink/downlink scheduling based on resources of the PHY layer.
  • the RLC layer performs the whole processing on the data packet when the transmission time arrives, so that the processing time of the whole process is relatively long.
  • the present invention provides a method and system for transmitting and receiving data, which is used to solve the problem that the RLC layer processes the data packet only when the transmission time arrives, so that the processing time of the whole process is relatively long.
  • the allocation module combines the received PDCP PDU into an RLC PDU, and allocates a corresponding RLC SN, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU;
  • the processing module combines data corresponding to the scheduling resource into a MAC PDU, and performs data transmission processing according to the MAC PDU.
  • the allocating module allocates a corresponding RLC SN, including:
  • the allocating module allocates a corresponding RLC SN according to the receiving order of each PDCP PDU of the same priority; or, the allocating module allocates a corresponding RLC SN according to the receiving order of each PDCP PDU set of the same priority, wherein the PDCP PDU At least one PDCP PDU is included in the combination.
  • the allocating module preferentially allocates a PDCP PDU with a high priority.
  • the generated RLC PDU includes at least one of the PDCP PDU and the allocated RLC SN; or, if the received PDCP SN of each PDCP PDU is in the same order as the allocated RLC SN, the generated The RLC PDU includes at least one of the PDCP PDUs.
  • the allocating module allocates a corresponding RLC SN, including:
  • the allocation module forms the received PDCP PDU into an RLC PDU before determining the number of scheduling resources; or the allocation module forms the received PDCP PDU into an RLC PDU after determining the number of scheduling resources.
  • the determining, by using the number of the scheduled resources, the data corresponding to the scheduling resource from the generated RLC PDU including:
  • the number of degrees of resources determines a target RLC PDU that needs to be segmented, and segments the target RLC PDU to generate a new RLC PDU.
  • the determining module performs segmentation processing on the target RLC PDU to generate a new RLC PDU, including:
  • the determining module generates a new RLC PDU according to the segmentation information and the segmented data
  • the segmentation information includes some or all of the following information:
  • the processing module combines the data corresponding to the scheduling resource into a MAC PDU, including:
  • the processing module sorts the RLC PDUs of the same logical channel according to the RLC SN, and sorts the RLC PDUs of different logical channels according to priorities;
  • the processing module groups the sorted RLC PDUs into MAC PDUs.
  • the processing module forms the sorted RLC PDU into a MAC PDU, including:
  • the processing module composes a MAC PDU according to the LCID of the sorted RLC PDU;
  • the MAC PDU includes a respective LCID of each RLC PDU; or the MAC PDU includes a different LCID, and the RLC PDUs corresponding to the same LCID share one LCID.
  • the RLC PDU is an initially transmitted RLC PDU and/or a retransmitted RLC PDU.
  • the allocating module, the determining module, and the processing module are located in the same entity; or, the allocating module, the determining module, and the processing module are located in the same entity; or The allocation module, the determining module, and the processing module are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the allocation module is located in the CU, and the determining module and the processing module are located in the DU.
  • the receiving module divides the received MAC PDU into multiple RLC PDUs
  • the transmission module sends the received RLC PDU to the parsing module
  • the parsing module After the parsing module determines that the parsing and/or the recombined RLC PDU is parsed, the parsing module obtains a PDCP PDU, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU.
  • the method further includes:
  • the parsing module generates feedback information according to the RLC SN of the received RLC PDU;
  • the feedback information includes the RLC SN of the lost RLC PDU; or if the fragmented RLC PDU is lost, the feedback information includes the original RLC PDU to which the lost RLC PDU belongs.
  • RLC SN information indicating the starting position of the lost RLC PDU in the original RLC PDU and the length information of the lost RLC PDU; or
  • the feedback information includes the number of RLC SNs and lost RLC PDUs of the first RLC PDU in the consecutive RLC PDUs; or, if If there are consecutive RLC PDUs lost and there are segmented RLC PDUs in the consecutive RLC PDUs, the feedback information includes the RLC SN of the first RLC PDU in the consecutive RLC PDUs, the information indicating the segmented RLC PDUs, and The number of lost RLC PDUs, where the fragmented RLC PDU is the first RLC PDU and/or the last RLC PDU of the consecutive RLC PDUs.
  • the transmitting module sends the received RLC PDU to the parsing module, including:
  • the transmitting module directly sends the received RLC PDU to the parsing module; or the transmitting module sorts and/or reassembles the received RLC PDU according to the RLC SN of the received RLC PDU, and then sends the received RLC PDU to the parsing module.
  • the receiving module, the transmitting module, and the parsing module are located in the same entity; or the receiving module, the transmitting module, and the parsing module are located in the same entity; or The receiving module, the transmitting module, and the parsing module are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the parsing module is located in the CU, and the receiving module and the transmitting module are located in the DU.
  • a system for transmitting data according to an embodiment of the present invention includes:
  • An allocation module configured to form the received PDCP PDU into an RLC PDU, and allocate a corresponding RLC SN, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU;
  • a determining module configured to determine data corresponding to the scheduling resource from the generated RLC PDU according to the number of scheduling resources
  • a processing module configured to form data corresponding to the scheduling resource into a MAC PDU, and perform data transmission processing according to the MAC PDU.
  • the allocation module is specifically configured to:
  • a corresponding RLC SN is allocated according to a receiving order of each PDCP PDU set of the same priority, wherein the PDCP PDU combination includes at least one PDCP PDU.
  • the allocation module is specifically configured to:
  • Priority is assigned to PDCP PDUs with high priority.
  • the generated RLC PDU includes at least one of the PDCP PDU and the allocated RLC SN; or, if the received PDCP SN of each PDCP PDU is in the same order as the allocated RLC SN, the generated The RLC PDU includes at least one of the PDCP PDUs.
  • the allocation module is specifically configured to:
  • the received PDCP PDUs are grouped into RLC PDUs before determining the number of scheduling resources; or, after determining the number of scheduling resources, the received PDCP PDUs are grouped into RLC PDUs.
  • the determining module is specifically configured to:
  • the target RLC PDU that needs to be segmented is determined according to the number of scheduling resources, and the target RLC PDU is segmented to generate a new RLC PDU.
  • the determining module is specifically configured to:
  • the segmentation information includes some or all of the following information:
  • processing module is specifically configured to:
  • the sorted RLC PDUs are grouped into MAC PDUs.
  • processing module is specifically configured to:
  • the MAC PDU includes a respective LCID of each RLC PDU; or the MAC PDU includes a different LCID, and the RLC PDUs corresponding to the same LCID share one LCID.
  • the RLC PDU is an initially transmitted RLC PDU and/or a retransmitted RLC PDU.
  • the allocating module, the determining module, and the processing module are located in the same entity; or, the allocating module, the determining module, and the processing module are located in the same entity; or The allocation module, the determining module, and the processing module are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the allocation module is located in the CU, and the determining module and the processing module are located in the DU.
  • a system for performing data reception according to an embodiment of the present invention includes:
  • a receiving module configured to divide the received MAC PDU into multiple RLC PDUs
  • a transmission module configured to send the received RLC PDU to the parsing module
  • a parsing module configured to parse the sorted and/or reassembled RLC PDU to obtain a PDCP PDU, where each RLC PDU corresponds to one RLC SN.
  • the parsing module is further configured to:
  • the feedback information includes the RLC SN of the lost RLC PDU; or if the fragmented RLC PDU is lost, the feedback information includes the original RLC PDU to which the lost RLC PDU belongs.
  • the feedback information includes the number of RLC SNs and lost RLC PDUs of the first RLC PDU in consecutive RLC PDUs; or, if there are consecutive RLC PDUs lost, and there are segments in consecutive RLC PDUs
  • the RLC PDU includes the RLC SN of the first RLC PDU in the consecutive RLC PDU, the information indicating the segmented RLC PDU, and the number of lost RLC PDUs, where the fragmented RLC PDU is a continuous RLC. The first RLC PDU and/or the last RLC PDU in the PDU.
  • the transmission module is specifically configured to:
  • the received RLC PDU is directly sent to the parsing module; or, according to the RLC SN of the received RLC PDU, the received RLC PDU is sorted and/or reassembled and sent to the parsing module.
  • the receiving module, the transmitting module, and the parsing module are located in the same entity; or the receiving module, the transmitting module, and the parsing module are located in the same entity; or The receiving module, the transmitting module, and the parsing module are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the parsing module is located in the CU, and the receiving module and the transmitting module are located in the DU.
  • a processor for reading a program in the memory performing the following process:
  • each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU; determining from the generated RLC PDU according to the number of scheduling resources Data corresponding to the scheduling resource;
  • the data corresponding to the scheduling resource constitutes a MAC PDU, and performs data transmission processing according to the MAC PDU.
  • a transceiver for receiving and transmitting data under the control of a processor.
  • a processor for reading a program in the memory performing the following process:
  • each RLC PDU includes at least one PDCP PDU.
  • a transceiver for receiving and transmitting data under the control of a processor.
  • a received PDCP PDU Packet Data Convergence Protocol, Protocol Data Unit, Protocol Data Unit
  • RLC PDU Packet Data Convergence Protocol, Protocol Data Unit, Protocol Data Unit
  • RLC SN SequenceNumber, sequence number
  • each RLC The PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU; the data corresponding to the scheduling resource is determined from the generated RLC PDU; and the data corresponding to the scheduling resource is formed into a MAC PDU for data transmission processing.
  • the embodiment of the present invention establishes a binding relationship between the PDCP PDU and the RLC PDU, and each RLC PDU includes at least one PDCP PDU, so that the allocation module can generate the RLC PDU after receiving the partial PDCP PDU, thereby shortening the layer 2 The length of time that the packet is processed.
  • FIG. 1 is a schematic diagram of a user plane protocol stack in the background art
  • FIG. 2 is a schematic flowchart of a method for transmitting data according to an embodiment of the present invention
  • FIG. 3A is a schematic diagram of a first group package according to an embodiment of the present invention.
  • 3B is a schematic diagram of a second group package according to an embodiment of the present invention.
  • 3C is a schematic diagram of a third grouping package according to an embodiment of the present invention.
  • 4A is a schematic diagram of downlink data transmission when a CU-DU is separated according to an embodiment of the present invention
  • 4B is a schematic diagram of uplink data transmission when a CU-DU is separated according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a method for receiving data according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a system for transmitting data according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a system for performing data reception according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a sending device according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a receiving device according to an embodiment of the present invention.
  • the method for transmitting data in the embodiment of the present invention includes:
  • Step 200 The allocating module combines the received PDCP PDU into an RLC PDU, and allocates a corresponding RLC SN, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU;
  • Step 201 The determining module determines data corresponding to the scheduling resource from the generated RLC PDU according to the number of scheduling resources.
  • Step 202 The processing module combines data corresponding to the scheduling resource into a MAC PDU, and performs data transmission processing according to the MAC PDU.
  • the received PDCP PDU is formed into an RLC PDU, and a corresponding RLC SN is allocated, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU; and the generated RLC PDU is determined from the generated RLC PDU.
  • the data corresponding to the scheduling resource is configured; the data corresponding to the scheduling resource is formed into a MAC PDU for data transmission processing.
  • the embodiment of the present invention establishes a binding relationship between the PDCP PDU and the RLC PDU, and each RLC PDU includes at least one PDCP PDU, so that the allocation module can generate the RLC PDU after receiving the partial PDCP PDU, thereby shortening the layer 2 The length of time that the packet is processed.
  • how many PDCP PDUs are included in each RLC PDU can be determined by a high-level configuration (such as how many PDCP PDUs are included in each RLC PDU, and the maximum number of bytes that can be included in each RLC PDU).
  • Static configuration can also be dynamically configured by the distribution module according to dynamic link conditions and/or load conditions (such as how many PDCP PDUs are included in each RLC PDU, or the maximum number of bytes that can be included in each RLC PDU. ).
  • the allocation module, the determination module, and the processing module are not in the same entity, because the link status and the load condition are counted in the determination module, if the allocation module is located in the CU (Central Unit), the determination module and the processing module are located in the DU. (Distributed Unit), the DU is required to feed back the relevant conditions to the CU, so that the CU's determining module can be configured.
  • the status of each DU may be different, and the allocation module supporting the CU may adopt different dynamic configurations for each DU according to different conditions of each DU.
  • each PDCP PDU corresponds to one RLC PDU
  • the number of PDCP PDUs included in one RLC PDU may be configured at the same time, and/or the size of one RLC PDU may be configured at the same time, that is, one RLC PDU may not exceed M bytes.
  • the consecutive N PDCP PDUs are formed into one RLC PDU, and one RLC SN is allocated;
  • the size of the RLC PDU is configured as the M byte, a plurality of consecutive PDCP PDUs not exceeding M bytes are formed into one RLC PDU when the RLC PDU is formed.
  • the PDCP PDU that constitutes the RLC PDU is the largest packet mode that is not greater than the M byte.
  • the PDCP PDU is a small packet, that is, if each packet is processed separately, the header overhead and the processing overhead are large, so that the cascading can be performed in advance to become a medium-sized RLC PDU, thereby reducing the head overhead. And processing overhead.
  • PDCP PDUs can be processed in the same manner in subsequent processing of the RLC PDU.
  • a Discard Timer is started for each data packet. After the timer expires, if the data packet has not been processed and sent, the data packet may be directly deleted.
  • the length of the timer can be configured by the RRC (Radio Resource Control), and the length is related to the QoS (Quality of Service) quality of the service, and is generally determined by the maximum transmission delay that the service can tolerate. .
  • the PDCP layer can perform certain buffering on the received high-level data, and can also perform PDCP layer processing on the data immediately.
  • the processing of the PDCP layer includes:
  • a sequence number SN For each data packet from the upper layer, a sequence number SN will be assigned, and the initial value of the SN is 0, that is, the SN assigned to the first SDU (Service Data Units) is 0, The SN of the two SDUs is 1, and so on;
  • header compression process is performed according to the configured header compression protocol
  • integrity protection and security operations on data packets are performed only on the data of the control plane, and encryption is performed on all data, including control. Face data and user face data;
  • the necessary PDCP header is added, and the PDCP header mainly includes PDCP SN and PDCP PDU type indication information, and the like;
  • the distribution module When the distribution module receives the data packet from the PDCP, it is the RLC SDU. Generally, it needs to store it in the transmission buffer, wait for an appropriate opportunity, form an RLC PDU, send it to the processing module, and then process it through the MAC and the physical layer. After that, it is sent at the air interface.
  • the allocation module, the determining module, and the processing module are located in the same entity in the embodiment of the present invention.
  • the allocation module, the determining module, and the processing module are partially located in the same entity; or
  • the allocation module, the determining module, and the processing module are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the allocation module is located in the CU, and the determining module and the processing module are located in the DU.
  • the manner in which the allocation module, the determining module, and the processing module are located in the same entity or in different entities or between the allocation module, the determining module, and the processing module is a non-ideal backhaul connection. Introduce.
  • the allocation module stores the received PDCP PDUs in the transmission buffer in order.
  • different priority data may be separately buffered, that is, the same priority data is sequentially cached according to the receiving order, and different priorities are used.
  • the data has different queues.
  • the allocating module of the allocating module allocates a corresponding RLC SN according to the receiving order of each PDCP PDU of the same priority; or
  • the allocating module allocates a corresponding RLC SN according to a receiving order of each PDCP PDU set of the same priority, wherein the PDCP PDU combination includes at least one PDCP PDU.
  • the allocating module may allocate a corresponding RLC SN for each PDCP PDU according to the order of each PDCP PDU, for example, assigning 0 to the first PDCP PDU, and the second PDCP PDU. Assign 1, and so on.
  • the SN of the PDCP PDU and the SN of the RLC PDU may be equal.
  • the PDCP SN 0, 1, 2, 3, 4... is the same as the RLC SN0, 1, 2
  • the 3, 4, ... numbers are the same.
  • the RLC SN can be omitted, and the PDCP SN can be directly multiplexed as the RLC SN to perform RLC related operations. That is, if the order of the PDCP SN of each PDCP PDU received is the same as the order of the RLC SNs allocated to each PDCP PDU, the generated RLC PDU includes at least one of the PDCP PDUs.
  • the PDCP SN may be discontinuous.
  • the PDCP SN received by one of the RLC transmitting entities may have the following order: PDCP SN 0, 2, 4,6,9... are mapped to RLC SN 0,1,2,3,4... in order, respectively, or the PDCP PDU is deleted due to timeout, and there may be a gap in the middle.
  • the PDCP SN received by an RLC entity may be The order is such that PDCP SN 0,1,2,5,6,7... are mapped to RLC SN 0,1,2,3,4,5... in order.
  • the RLC PDU includes multiple PDCP PDUs, such as RLC PDUs including 2 PDCP PDUs, PDCP SN 0,1 is mapped to RLC SN 0, PDCP SN 2,3 is mapped to RLC SN 1, and so on. That is, the generated RLC PDU includes at least one of the PDCP PDU and an RLC SN allocated to the PDCP PDU.
  • the RLC needs to ensure the sequential transmission of the data packets. Therefore, the RLC SNs are allocated in order, and there is no gap in the middle. When the PDCP SN satisfies this requirement, the RLC can reuse the PDCP SN to save the head overhead; when the PDCP SN does not When the order is met and the requirements are completely continuous, the RLC separately allocates the SN to ensure continuity. Specifically, how to select may be based on the configuration of the RRC, that is, whether the RLC SN appears to be determined by the RRC configuration.
  • the PDCP PDU and the RLC PDU are in a one-to-one correspondence, and may also be a one-to-many relationship in the implementation, as long as the allocation module can record the mapping relationship, for example, the fixed N PDCP PDUs are mapped to one RLC PDU. Or a PDCP PDU based on no more than M bytes can be mapped to one RLC PDU.
  • the allocation module may form each of the received PDCP PDUs into one RLC PDU; or one of them may form one RLC PDU, two of which form one RLC PDU, and some of which form one RLC PDU.
  • the number of scheduling resources is sent after the processing module is scheduled.
  • the allocation module may allocate the RLC SNs one by one after receiving the PDCP layer data, and form an RLC PDU (that is, the PDCP that the allocation module will receive before determining the number of scheduling resources).
  • the PDUs are composed of RLC PDUs.
  • the allocation module can allocate SNs in real time after receiving the number of scheduling resources (that is, the allocation module preferentially assigns corresponding RLC SNs to PDCP PDUs with high priority).
  • the RLC SDU can be processed according to a certain priority rather than a first-come-first-served principle.
  • the RLC SN and the organization RLC PDU cannot be allocated in advance, but when processed After the module notifies the scheduling resource, it determines which RLC SDUs to send according to the priority order, and the RLC SDU can be allocated the RLC SN and the organization RLC PDU.
  • the determining module may determine, in real time, how much data is sent to the processing module according to the number of the scheduling resources, for example, the first RLC.
  • the PDU size is 200 bytes
  • the second RLC PDU size is 300 bytes
  • the third RLC PDU size is 500 bytes
  • the number of scheduling resources is 800 bytes
  • the first and second RLC PDUs are totaled. 500 bytes) is completely sent to the processing module, and the first 300 bytes of the third RLC PDU are made into segmented RLC PDUs and sent to the processing module.
  • the determining module determines that segmentation processing is required according to the number of scheduling resources, determining a target RLC PDU that needs to be segmented according to the number of scheduling resources, and performing segmentation processing on the target RLC PDU to generate a new RLC PDU (which can be called RLC PDU segmentation).
  • the determining module generates a new RLC PDU according to the segmentation information and the segmented data
  • the segmentation information includes some or all of the following information:
  • the format of the RLC PDU segmentation is as follows:
  • the RLC SN needs to be carried.
  • the SNs carried by different segments must be the same SN, that is, corresponding to the original RLC PDU.
  • the starting position SO Segment offset
  • the starting position is 0 if it is the first segment, and 300-500 if it is the RLC PDU.
  • the starting position is 300;
  • the length of the segment needs to be carried in the RLC segment, for example, a segment of 0-200 bytes of the original RLC PDU, and the length is 200 bytes, and the length field is in the RLC segment header field.
  • the length may be reflected in the MAC group package;
  • LSF Last segment flag
  • 0 represents a non-last segment
  • 1 represents a last segment.
  • the RLC PDU of the embodiment of the present invention may be an initially transmitted RLC PDU and/or a retransmitted RLC PDU.
  • the RLC PDU may be segmented to accommodate the number of scheduling resources, thereby improving transmission efficiency without wasting transmission resources.
  • the retransmission segment of the RLC PDU is similar to the initial segment, that is, the RLC SN indicates which RLC PDU the segment belongs to, SO, LI.
  • the LSF indicates the location, length, and last segment of the segment in the original RLC PDU.
  • the processing module when the processing module combines the data corresponding to the scheduling resource into a MAC PDU, the RLC PDUs of the same logical channel are sorted according to the RLC SN, and the RLC PDUs of different logical channels are sorted according to priorities; The subsequent RLC PDUs constitute a MAC PDU.
  • RLC PDUs and RLC PDU segments from the same logical channel are organized as much as possible in SN order or priority order;
  • FIG. 3A A typical grouping process is shown in FIG. 3A, wherein the P-SN represents a PDCP SN, the R-SN represents an RLC SN, the LCID (Logical Channel ID) is a logical channel identifier, and LI is a length indication field. Since LCID1's data has a higher priority than LCID2, it can be placed in front of the MAC PDU and placed as close as possible to the RLC PDU of one logical channel. Since the data for LCID2 is a segment and is the first segment, the segment indicates that SO is zero. There is another simplified solution here to indicate that this is a segment and the first segment with 1 bit; for the second segment of LCID2 for the second transmission, the displayed SO indication needs to be carried.
  • the P-SN represents a PDCP SN
  • the R-SN represents an RLC SN
  • the LCID Logical Channel ID
  • LI is a length indication field. Since LCID1's data has a higher priority than LCID
  • FS First segment
  • FS takes a value of 1 for the first segment
  • FS takes a value of 0 for the non-first segment.
  • the processing module forms a MAC PDU according to the LCID of the sorted RLC PDU;
  • the MAC PDU includes a respective LCID of each RLC PDU.
  • the MAC PDU includes different LCIDs, and the RLC PDUs corresponding to the same LCID share one LCID. Specifically, as shown in FIG. 3B, in this example, data packets of the same LCID are grouped together and carry a unified LCID.
  • the allocation module and the determining module are located in the RLC layer, and the processing module is located in the MAC layer.
  • the allocation module, the determining module, and the processing module can all be placed in the MAC layer, as shown in FIG. 3C.
  • the determining module and the processing module can perform parallel processing in parallel, thereby saving processing time. For example, the determining module sends the processed MAC PDU to the processing module for subsequent processing, and determines that the module continues to process subsequent MAC PDUs.
  • each layer such as SN, LI, LCID, etc.
  • there may be other domains in the header such as type indication D. /C is used to indicate data or control, E domain is the extended indication field, LS is used to indicate the last segment, etc., and will not be enumerated here.
  • the manner in which the allocation module, the determining module, and the processing module are located in the same entity or in different entities or between the allocation module, the determining module, and the processing module is a non-ideal backhaul connection. Introduced in the follow-up.
  • the allocation module is located in the CU, and the determination module and the processing module are located in the DU.
  • Figure 4A shows the processing of a typical CU/DU entity of downlink data.
  • the CU is a centralized processing entity and the DU is a distributed processing entity.
  • RLC-H is the allocation module
  • RLC-L is the determining module, which is located in two physical entities, CU and DU.
  • the downlink data transmission process is as follows:
  • PDCP allocates the PDCP SN of the high-level data, performs security operations, compresses the header, adds the header, forms a PDCP PDU, and sends it to the corresponding RLC-H entity;
  • the RLC-H entity assigns the RLC SN to the received PDCP PDU in sequence, and the RLC PDU and the PDCP PDU have a one-to-one correspondence, and distributes the data and the corresponding RLC SN to one or more RLC-L entities.
  • the method of selecting is to select a path with better link conditions and lighter load according to flow control and feedback, or to send the same data to multiple RLC-L entities in order to meet the requirement of low transmission delay and high reliability. Simultaneous transmission;
  • the RLC-L entity located in the DU sends a suitable combination of the RLC PDU and the RLC PDU of the appropriate size to the MAC layer for subsequent transmission according to the transmission resource size scheduled by the MAC layer in real time, wherein the RLC PDU is segmented with the original PDCP.
  • the PDU is an object, carries the RLC SN allocated by the RLC-H, and performs segmentation indications in domains such as SO, LI, and LSF.
  • the embodiment of the present invention performs the air interface transmission after the MAC/PHY processing, and then passes through the opposite end.
  • the PHY/MAC process is handed over to the receiving end RLC-L and aggregated to the RLC-H.
  • the RLC-H completes the update of the receiving status, feedback, packet reassembly, and submits it to the PDCP.
  • PDCP supports out-of-order security and decompression operations.
  • the RLC-L may perform the reassembly of the RLC PDU first, and then submit the RLC PDU to the RLC-H, or directly support the RLC-L to deliver the RLC PDU segment to the RLC-H, and the final reorganization is performed by the RLC-H. Sort.
  • the RLC PDU segments from different paths can be reassembled by the RLC-H to speed up the reorganization and reduce the delay. Therefore, in the case of multipath repeated data transmission, the reassembly function of the RLC PDU segmentation may be located in the RLC-H, otherwise it may be located in the RLC-L, that is, configurable according to the situation.
  • the data processing method supported by the present invention can also support only the PDCP protocol located in the CU.
  • the RLC and the MAC are both located in the DU, or the PDCP and the multiple RLC-H protocols are located in the CU, and the multiple RLC-Ls and the MACs are located in the DU, and the data processing manner is similar, and details are not described herein again.
  • the method for receiving data in the embodiment of the present invention includes:
  • Step 500 The receiving module divides the received MAC PDU into multiple RLC PDUs.
  • Step 501 The transmission module sends the received RLC PDU to the parsing module.
  • Step 502 The parsing module parses the sorted and/or reassembled RLC PDU to obtain a PDCP PDU, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU.
  • the receiving module, the transmitting module, and the parsing module are located in the same entity in the embodiment of the present invention.
  • the receiving module, the transmitting module, and the parsing module are partially located in the same entity; or
  • the receiving module, the transmitting module, and the parsing module are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the parsing module is located in the CU, and the receiving module and the transmitting module are located in the DU.
  • the following three-layer entities of the entire user plane UP (User Plane), the receiving module, the transmission module and the parsing module are all located in the same physical entity or are ideal backhaul connections (That is, the transmission delay is much smaller than the order of milliseconds) as an example.
  • the manner in which the receiving module, the transmitting module, and the parsing module are located in the same entity or in different entities or between the receiving module, the transmitting module, and the parsing module is a non-ideal backhaul connection. Introduce.
  • the receiving end is the reverse process of the transmitting end. After the data is received by the physical layer from the air interface, after the physical layer processing, the format of the MAC PDU is restored.
  • the data is received, and different data blocks are solved according to the information such as the LCID and the LI carried therein, and the RLC PDUs belonging to different logical channels (which may also include the RLC PDUs for segmentation processing) may be determined according to the indication of the LCID.
  • the transmission module has two ways of processing after receiving the RLC PDU:
  • the transmission module directly sends the received RLC PDU to the parsing module.
  • the transmission module delivers the RLC PDU to the parsing module, and the RLC PDU that has been segmented is also directly delivered to the parsing module.
  • Mode 1 is actually a method similar to transparent transmission, that is, directly sending all received data to RLC Higher (ie, parsing module) for processing, such as Gap (interval) detection, reordering Treordering timer, and state feedback NACK. /ACK, etc.
  • RLC Higher ie, parsing module
  • the transmission module sorts and/or reassembles the received RLC PDU according to the RLC SN of the received RLC PDU, and sends the received RLC PDU to the parsing module.
  • the transmission module reorders the received RLC PDUs, re-sequences the RLC PDUs that are segmented, and then performs reordering, thereby eliminating the out-of-order caused by the MAC HARQ and submitting the information to the parsing module.
  • the Treordering_timer is started. If the complete RLC PDU is still not received after the Treordering_timer times out, The RLC PDU detected by the Treordering_timer is submitted to the parsing module, and may not be submitted to the parsing module, and is waiting for the completion of the receiving.
  • the ordering here refers to the update of the receiving state in the order of the RLC SN, for example:
  • the next SN of the highest SN is 4, and if the newly received SN is 4, it is considered to be received in order, and the next highest SN of the data will be received in order. Updated to 5 (of course, it is also possible to record only the highest SN here, not the next SN of the highest SN);
  • the T-reordering timer can be started to detect the out-of-order caused by the underlying transmission. If the PDU is not received after the T-reordering timer expires, the device waits for UM (Unacknowledged Mode) or the NACK status report is requested by the parsing module to retransmit (for AM (Acknowledged Mode) , confirm mode)).
  • UM Unacknowledged Mode
  • NACK status report is requested by the parsing module to retransmit (for AM (Acknowledged Mode) , confirm mode)).
  • the parsing module After the transmitting module sends the received RLC PDU to the parsing module, the parsing module generates feedback information according to the RLC SN of the received RLC PDU.
  • the feedback information can then be transmitted in accordance with a method transmitted by an embodiment of the present invention.
  • the content of the feedback information is different for different receiving situations, which are introduced separately below.
  • the feedback information includes an ACK (ACKnowledge) information.
  • the feedback information includes a NACK (Negative ACKnowledge) information.
  • the gap may be the entire RLC PDU loss, or the RLC PDU segmentation may be lost, or may be a continuous one. Serial RLC PDUs are continuously lost.
  • NACK_SN For a single RLC PDU loss, it is explicitly indicated by a separate NACK_SN; the RLC PDU is lost in segments, and the NACK_SN carries SO and LI to indicate explicitly; Multiple consecutive SN RLC PDUs are lost, The first NACK_SN carries the number of consecutively lost PDUs to indicate explicitly. Only the NACK information needs to be indicated one by one, and only one ACK_SN is required, indicating that all PDUs below the ACK_SN are correctly received except for the PDU or PDU segment indicating that the NACK is indicated.
  • the following is a description of the feedback information of the SN gap.
  • the feedback information includes the RLC SN of the lost RLC PDU.
  • the RLC PDU with the SN of 4 is confirmed to be lost, and 4 can be added to the feedback information.
  • the feedback information includes the RLC SN of the original RLC PDU to which the lost RLC PDU belongs, the information indicating the starting position of the lost RLC PDU in the original RLC PDU, and the lost information. Length information of the RLC PDU.
  • the length may be displayed by a length indication, or may be represented by an end position of the segment in the original RLC PDU.
  • the feedback information includes the number of RLC SNs and lost RLC PDUs of the first RLC PDU in the consecutive RLC PDUs.
  • the RLC PDU with the SNs of 4, 5, and 6 is determined to be lost, and the feedback information includes 4 (ie, the first RLC PDU).
  • RLC SN the first RLC PDU
  • 3 the number of lost RLC PDUs
  • the feedback information includes the RLC SN of the first RLC PDU in the consecutive RLC PDUs, and the RLC PDU indicating the segmentation. Information and the number of lost RLC PDUs, where the fragmented RLC PDU Is the first RLC PDU and/or the last RLC PDU in a continuous RLC PDU.
  • the feedback information includes 4 (ie, the RLC SN of the first RLC PDU) and 3 (the missing RLC PDU).
  • the number and the information used to indicate the segmented RLC PDU such as 00 indicates the first RLC PDU segment, 01 indicates the last RLC PDU segment, and 11 indicates the first and last RLC PDU segments).
  • the SN can represent the lost entire RLC PDU, if a partial segmentation of the RLC PDU is received, The segmentation information of the lost RLC PDU segment needs to be carried in the status report.
  • the lost RLC PDU is 3-8, 7 of which are segmented RLC PDUs, which can be in continuous mode from 3 to 6, 7 and 8 in separate mode, or 3 to 6 in continuous mode, and 7 and 8 in continuous mode. .
  • the parsing module can solve the PDCP PDU sent to the PDCP layer for early decryption, and the integrity is solved. Protection and unwinding and other processing.
  • the PDCP layer when receiving the PDCP PDU sent by the RLC layer, it performs reception judgment, determines whether it is a normal data packet within the receiving window, whether it is repeated, etc., decrypts the packet that meets the receiving condition, and decomposes the integrity. Operations such as protection and decompression header compression, and then reordering the data packets. If they meet the requirements for sequential delivery, they can be submitted to the upper layer. Otherwise, they need to be rearranged. The sequence waits, so that the subsequent gap data is complemented, and the high-level is submitted in order.
  • the manner in which the receiving module, the transmitting module, and the parsing module are located in the same entity or in different entities or between the receiving module, the transmitting module, and the parsing module is a non-ideal backhaul connection. Introduced in the follow-up.
  • Figure 4B shows the processing of a typical upstream data CU/DU entity.
  • parsing module is located in the CU, and the transmitting module and the receiving module are located in the DU.
  • the MAC layer of the DU parses the RLC PDU or the RLC PDU segment of the different logical channel, and sends it to the RLC Lower module of the DU (ie, the transmission module);
  • the RLC Lower module can be directly delivered to the RLC Higher module (ie, the parsing module) in the CU, or the RLC Lower module is reordered and reassembled, and then submitted to the RLC Higher module.
  • the RLC Higher module reorders and reassembles the RLC PDU or the RLC PDU, and reports the status report according to the provisions; the RLC Higher module sends the parsed PDCP PDU to the PDCP layer;
  • the PDCP layer performs decryption, de-integrity protection, decompression and other operations, and then reorders in the AM mode, and delivers them to the upper layer in order.
  • the embodiment of the present invention can enable the layer 2 data to be processed in real time and fast in parallel between layers, improve the real-time efficiency of the processing, and have uniformity for the initial segmentation and the retransmission segmentation.
  • the format and processing process simplify the processing complexity and improve the processing efficiency of Layer 2 for a large number of data packets, which will be more suitable for various 5G application scenarios in the future.
  • a system for transmitting data is provided in the embodiment of the present invention.
  • the principle of solving the problem is similar to the method for transmitting data in the embodiment of the present invention. Therefore, the implementation of the device can be implemented in the system. , the repetition will not be repeated.
  • the system for transmitting data includes:
  • the allocating module 600 is configured to form the received PDCP PDU into an RLC PDU, and allocate corresponding An RLC SN, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU;
  • a determining module 601 configured to determine data corresponding to the scheduling resource from the generated RLC PDU according to the number of scheduling resources
  • the processing module 602 is configured to form data corresponding to the scheduling resource into a MAC PDU, and perform data transmission processing according to the MAC PDU.
  • the allocating module 600 is specifically configured to:
  • the corresponding RLC SN is allocated in the order of reception of each PDCP PDU of the same priority.
  • the allocating module 600 is specifically configured to:
  • Priority is assigned to PDCP PDUs with high priority.
  • the generated RLC PDU includes at least one of the PDCP PDU and the allocated RLC SN; or
  • the generated RLC PDU includes at least one of the PDCP PDUs.
  • the allocating module 600 is specifically configured to:
  • the received PDCP PDUs are formed into RLC PDUs before determining the number of scheduled resources; or,
  • the received PDCP PDUs are grouped into RLC PDUs after determining the number of scheduling resources.
  • the determining module 601 is specifically configured to:
  • the target RLC PDU that needs to be segmented is determined according to the number of scheduling resources, and the target RLC PDU is segmented to generate a new RLC PDU.
  • the determining module 601 is specifically configured to:
  • the segmentation information includes some or all of the following information:
  • processing module 602 is specifically configured to:
  • the sorted RLC PDUs are grouped into MAC PDUs.
  • processing module 602 is specifically configured to:
  • the MAC PDU includes a respective LCID of each RLC PDU; or the MAC PDU includes a different LCID, and the RLC PDUs corresponding to the same LCID share one LCID.
  • the RLC PDU is an initially transmitted RLC PDU and/or a retransmitted RLC PDU.
  • the allocating module 600, the determining module 601, and the processing module 602 are located in the same entity; or
  • the allocation module 600, the determining module 601, and the processing module 602 are partially located in the same entity; or
  • the allocation module 600, the determining module 601, and the processing module 602 are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the allocation module 600, the determining module 601, and the processing module 602 are partially located in the same entity, the allocation module 600 is located in the CU, and the determining module 601 and the processing module 602 are located in the DU.
  • a system for receiving data is provided in the embodiment of the present invention.
  • the principle of solving the problem is similar to the method for receiving data in the embodiment of the present invention. Therefore, the implementation of the device can be implemented in the system. , the repetition will not be repeated.
  • the system for performing data reception in the embodiment of the present invention includes:
  • the receiving module 700 is configured to divide the received MAC PDU into multiple RLC PDUs
  • the transmitting module 701 is configured to send the received RLC PDU to the parsing module.
  • the parsing module 702 is configured to parse the sorted and/or recombined RLC PDUs to obtain PDCP PDUs, where each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU.
  • the parsing module 702 is further configured to:
  • the feedback information includes the RLC SN of the lost RLC PDU;
  • the feedback information includes the RLC SN of the original RLC PDU to which the lost RLC PDU belongs, information indicating the starting position of the lost RLC PDU in the original RLC PDU, and the lost RLC PDU. Length information; or,
  • the feedback information includes the number of RLC SNs and lost RLC PDUs of the first RLC PDU in the consecutive RLC PDUs;
  • the feedback information includes the RLC SN of the first RLC PDU in the consecutive RLC PDUs, and the information indicating the segmented RLC PDUs. And the number of lost RLC PDUs, wherein the fragmented RLC PDU is the first RLC PDU and/or the last RLC PDU of the consecutive RLC PDUs.
  • the transmission module 701 is specifically configured to:
  • the received RLC PDUs are sorted and/or reassembled according to the RLC SN of the received RLC PDU, and then sent to the parsing module.
  • the receiving module 700, the transmitting module 701, and the parsing module 702 are located in the same entity; or
  • the receiving module 700, the transmitting module 701, and the parsing module 702 are partially located in the same entity; or
  • the receiving module 700, the transmitting module 701, and the parsing module 702 are located in different entities.
  • the entity is a base station or a terminal or a DU;
  • the parsing module 702 is located in the CU, and the receiving module 700 and the transmitting module 701 are located in the DU. in.
  • the allocation module 600, the determination module 601, and the processing module 602 are in the same entity or both in different entities and in the structure of FIG. Similarly, the difference is in the function of which module (or modules) the processor processes, and will not be described here.
  • the embodiment of the present invention further provides a transmitting device.
  • the principle of solving the problem is similar to the method for transmitting data in the embodiment of the present invention. Therefore, the implementation of the device can be implemented in the system, and the method is repeated. I won't go into details here.
  • the sending device of the embodiment of the present invention includes:
  • the processor 801 is configured to read a program in the memory 804 and perform the following process:
  • each RLC PDU corresponds to one RLC SN, and each RLC PDU includes at least one PDCP PDU; determining from the generated RLC PDU according to the number of scheduling resources Data corresponding to the scheduling resource; data corresponding to the scheduling resource is formed into a MAC PDU, and data transmission processing is performed according to the MAC PDU.
  • the transceiver 802 is configured to receive and transmit data under the control of the processor 801.
  • the processor 801 is specifically configured to:
  • the corresponding RLC SN is allocated in the order of reception of each PDCP PDU of the same priority.
  • the processor 801 is specifically configured to:
  • Priority is assigned to PDCP PDUs with high priority.
  • the generated RLC PDU includes at least one of the PDCP PDU and the allocated RLC SN; or
  • the generated RLC PDU includes at least one of the PDCP PDUs.
  • the processor 801 is specifically configured to:
  • the received PDCP PDUs are formed into RLC PDUs before determining the number of scheduled resources; or,
  • the received PDCP PDUs are grouped into RLC PDUs after determining the number of scheduling resources.
  • the processor 801 is specifically configured to:
  • the target RLC PDU that needs to be segmented is determined according to the number of scheduling resources, and the target RLC PDU is segmented to generate a new RLC PDU.
  • the processor 801 is specifically configured to:
  • the segmentation information includes some or all of the following information:
  • the processor 801 is specifically configured to:
  • the sorted RLC PDUs are grouped into MAC PDUs.
  • the processor 801 is specifically configured to:
  • the MAC PDU includes a respective LCID of each RLC PDU; or the MAC PDU includes a different LCID, and the RLC PDUs corresponding to the same LCID share one LCID.
  • the RLC PDU is an initially transmitted RLC PDU and/or a retransmitted RLC PDU.
  • bus 800 may include any number of interconnected buses and bridges, and bus 800 will include one or more processors represented by processor 801 and memory represented by memory 804.
  • the various circuits are linked together.
  • the bus 800 can also be such as Various other circuits, such as peripherals, voltage regulators, power management circuits, and the like, are linked together and are well known in the art and, therefore, are not further described herein.
  • Bus interface 803 provides an interface between bus 800 and transceiver 802.
  • Transceiver 802 can be an element or a plurality of elements, such as multiple receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the processor 801 is transmitted over the wireless medium via the antenna 805. Further, the antenna 805 also receives the data and transmits the data to the processor 801.
  • the processor 801 is responsible for managing the bus 800 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 804 can be used to store data used by the processor 801 when performing operations.
  • the processor 801 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). , complex programmable logic devices).
  • CPU Central Embedded Device
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the embodiment of the present invention further provides a receiving device.
  • the principle of solving the problem is similar to the method for receiving data in the embodiment of the present invention. Therefore, the implementation of the device can be implemented in the system, and the method is repeated. I won't go into details here.
  • FIG. 9 shows an example of a receiving module 700, a transmitting module 701, and a parsing module 702 in the same entity.
  • the receiving module 700, the transmitting module 701, and the parsing module 702 are in the same entity or in different entities and the structure of FIG. Similarly, the difference is in the function of which module (or modules) the processor processes, and will not be described here.
  • the receiving device of the embodiment of the present invention includes:
  • the processor 901 is configured to read a program in the memory 904 and perform the following process:
  • each RLC PDU includes at least one PDCP PDU.
  • the transceiver 902 is configured to receive and transmit data under the control of the processor 901.
  • processor 901 is further configured to:
  • the feedback information includes the RLC SN of the lost RLC PDU;
  • the feedback information includes the RLC SN of the original RLC PDU to which the lost RLC PDU belongs, information indicating the starting position of the lost RLC PDU in the original RLC PDU, and the lost RLC PDU. Length information; or,
  • the feedback information includes the number of RLC SNs and lost RLC PDUs of the first RLC PDU in the consecutive RLC PDUs;
  • the feedback information includes the RLC SN of the first RLC PDU in the consecutive RLC PDUs, and the information indicating the segmented RLC PDUs. And the number of lost RLC PDUs, wherein the fragmented RLC PDU is the first RLC PDU and/or the last RLC PDU of the consecutive RLC PDUs.
  • the processor 901 is specifically configured to:
  • the received RLC PDUs are sorted and/or reassembled according to the RLC SN of the received RLC PDU, and then sent to the parsing module.
  • bus 900 can include any number of interconnected buses and bridges, and bus 900 will include one or more processors represented by processor 901 and memory represented by memory 904. The various circuits are linked together. The bus 900 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 903 provides an interface between bus 900 and transceiver 902.
  • Transceiver 902 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the processor 901 is transmitted over the wireless medium via the antenna 905. Further, the antenna 905 also receives the data and transmits the data to the processor 901.
  • the processor 901 is responsible for managing the bus 900 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 904 can be used to store data used by the processor 901 in performing operations.
  • the processor 901 can be a CPU, an ASIC, an FPGA, or a CPLD.
  • the application can also be implemented in hardware and/or software (including firmware, resident software, microcode, etc.). Still further, the application can take the form of a computer program product on a computer usable or computer readable storage medium having computer usable or computer readable program code embodied in a medium for use by an instruction execution system or Used in conjunction with the instruction execution system.
  • a computer usable or computer readable medium can be any medium that can contain, store, communicate, communicate, or transport a program for use by an instruction execution system, apparatus or device, or in conjunction with an instruction execution system, Used by the device or device.

Abstract

一种进行数据发送和接收的方法及系统，用以解决RLC层在传输时刻到达时才对数据包进行整块处理，使得整个过程的处理时间比较长的问题。本发明实施例将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN。每个RLC PDU中包括至少一个PDCP PDU；从生成的RLC PDU中确定调度资源对应的数据；将调度资源对应的数据组成MAC PDU进行数据发送处理。采用本发明实施例的方案可以缩短对层二的数据包处理的时长。

Description

一种进行数据发送和接收的方法及系统
本申请要求在2016年11月03日提交中国专利局、申请号为201610959950.6、发明名称为“一种进行数据发送和接收的方法及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术领域，特别涉及一种进行数据发送和接收的方法及系统。
背景技术
终端UE(User Equipment，用户设备)和eNB(演进基站)之间的数据传输，通常经过PDCP(Packet Data Convergence Protocol，分组数据聚合协议)层、RLC(Radio Link Control，无线链路控制)层、MAC(Medium Access Control，媒体接入控制)层和PHY(Physical，物理)层的传输，每一层完成不同的数据处理。PDCP层主要是进行安全操作和头压缩解压缩处理，例如加密和完整性保护，ROHC(Robust Header Compression，健壮头压缩)压缩和解压缩等；RLC层主要完成数据的分段级联和按序递交及ARQ(Automatic Repeat reQuest，自动重传请求)数据传输保障；处理模块主要完成调度和不同逻辑信道的级联处理及HARQ(Hybrid Automatic Repeat reQuest，混合自动重传请求)操作；物理层完成传输块成包和空口发送。图1为用户面协议栈示意图。
PDCP层主要功能是进行安全相关操作(例如加/解密、完整性保护/验证)和头压缩/解压缩处理。RLC层主要功能是完成数据的分段、级联和按序递交及ARQ。处理模块主要功能是基于PHY层的资源进行上/下行调度。
上述方案中，RLC层在传输时刻到达时才对数据包进行整块处理，使得整个过程的处理时间比较长。
发明内容
本发明提供一种进行数据发送和接收的方法及系统，用以解决RLC层在传输时刻到达时才对数据包进行整块处理，使得整个过程的处理时间比较长的问题。
本发明实施例提供的一种进行数据发送的方法，该方法包括：
分配模块将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
确定模块根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；
处理模块将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
可选的，所述分配模块分配对应的RLC SN，包括：
所述分配模块按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN；或，所述分配模块按照同一优先级每个PDCP PDU集合的接收顺序分配对应的RLC SN，其中所述PDCP PDU组合中包括至少一个PDCP PDU。
可选的，所述分配模块为优先级高的PDCP PDU优先分配。
可选的，生成的所述RLC PDU包括至少一个所述PDCP PDU和分配的RLC SN；或，若收到的每个PDCP PDU的PDCP SN的顺序与分配的RLC SN顺序相同，则生成的所述RLC PDU包括至少一个所述PDCP PDU。
可选的，所述分配模块分配对应的RLC SN，包括：
所述分配模块在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU；或，所述分配模块在确定调度资源的数量之后将收到的PDCP PDU组成RLC PDU。
可选的，所述确定模块根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据，包括：
若所述确定模块根据调度资源的数量确定需要进行分段处理，则根据调 度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU。
可选的，所述确定模块对所述目标RLC PDU进行分段处理生成新的RLC PDU，包括：
所述确定模块根据分段信息以及分段后的数据生成新的RLC PDU；
其中，所述分段信息包括下列信息中的部分或全部：
目标RLC PDU的RLC SN；
分段后的数据在目标RLC PDU中的起始位置信息；
分段后的数据的长度信息；
用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
可选的，所述处理模块将所述调度资源对应的数据组成MAC PDU，包括：
所述处理模块将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；
所述处理模块将排序后的RLC PDU组成MAC PDU。
可选的，所述处理模块将排序后的RLC PDU组成MAC PDU，包括：
所述处理模块根据排序后的RLC PDU的LCID组成MAC PDU；
其中，所述MAC PDU包括每个RLC PDU分别的LCID；或所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。
可选的，所述RLC PDU为初始传输的RLC PDU和/或重传的RLC PDU。
可选的，所述分配模块、所述确定模块和所述处理模块位于同一个实体中；或，所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中；或，所述分配模块、所述确定模块和所述处理模块位于不同实体中。
可选的，若所述分配模块、所述确定模块和所述处理模块位于同一个实体中，则所述实体为基站或终端或DU；
若所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中，则所述分配模块位于CU中，所述确定模块和所述处理模块位于DU中。
本发明实施例提供的一种进行数据接收的方法，该方法包括：
接收模块将收到的MAC PDU分成多个RLC PDU；
传输模块将收到的RLC PDU发送给解析模块；
解析模块在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU。
可选的，所述传输模块将收到的RLC PDU发送给解析模块之后，还包括：
所述解析模块根据收到的RLC PDU的RLC SN生成反馈信息；
其中，若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN；或，若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息；或，
若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量；或，若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
可选的，所述传输模块将收到的RLC PDU发送给解析模块，包括：
所述传输模块直接将收到的RLC PDU发送给解析模块；或，所述传输模块根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
可选的，所述接收模块、所述传输模块和所述解析模块位于同一个实体中；或，所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中；或，所述接收模块、所述传输模块和所述解析模块位于不同实体中。
可选的，若所述接收模块、所述传输模块和所述解析模块位于同一个实体中，则所述实体为基站或终端或DU；
若所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中，则所述解析模块位于CU中，所述所述接收模块和所述传输模块位于DU中。
本发明实施例提供的一种进行数据发送的系统，该系统包括：
分配模块，用于将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
确定模块，用于根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；
处理模块，用于将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
可选的，所述分配模块具体用于：
按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN；或，
按照同一优先级每个PDCP PDU集合的接收顺序分配对应的RLC SN，其中所述PDCP PDU组合中包括至少一个PDCP PDU。
可选的，所述分配模块具体用于：
为优先级高的PDCP PDU优先分配。
可选的，生成的所述RLC PDU包括至少一个所述PDCP PDU和分配的RLC SN；或，若收到的每个PDCP PDU的PDCP SN的顺序与分配的RLC SN顺序相同，则生成的所述RLC PDU包括至少一个所述PDCP PDU。
可选的，所述分配模块具体用于：
在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU；或，在确定调度资源的数量之后将收到的PDCP PDU组成RLC PDU。
可选的，所述确定模块具体用于：
若根据调度资源的数量确定需要进行分段处理，则根据调度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU。
可选的，所述确定模块具体用于：
根据分段信息以及分段后的数据生成新的RLC PDU；
其中，所述分段信息包括下列信息中的部分或全部：
目标RLC PDU的RLC SN；
分段后的数据在目标RLC PDU中的起始位置信息；
分段后的数据的长度信息；
用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
可选的，所述处理模块具体用于：
将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；
将排序后的RLC PDU组成MAC PDU。
可选的，所述处理模块具体用于：
根据排序后的RLC PDU的LCID组成MAC PDU；
其中，所述MAC PDU包括每个RLC PDU分别的LCID；或所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。
可选的，所述RLC PDU为初始传输的RLC PDU和/或重传的RLC PDU。
可选的，所述分配模块、所述确定模块和所述处理模块位于同一个实体中；或，所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中；或，所述分配模块、所述确定模块和所述处理模块位于不同实体中。
可选的，若所述分配模块、所述确定模块和所述处理模块位于同一个实体中，则所述实体为基站或终端或DU；
若所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中，则所述分配模块位于CU中，所述确定模块和所述处理模块位于DU中。
本发明实施例提供的一种进行数据接收的系统，该系统包括：
接收模块，用于将收到的MAC PDU分成多个RLC PDU；
传输模块，用于将收到的RLC PDU发送给解析模块；
解析模块，用于在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN。
可选的，所述解析模块还用于：
根据收到的RLC PDU的RLC SN生成反馈信息；
其中，若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN；或，若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息；或，若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量；或，若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
可选的，所述传输模块具体用于：
直接将收到的RLC PDU发送给解析模块；或，根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
可选的，所述接收模块、所述传输模块和所述解析模块位于同一个实体中；或，所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中；或，所述接收模块、所述传输模块和所述解析模块位于不同实体中。
可选的，若所述接收模块、所述传输模块和所述解析模块位于同一个实体中，则所述实体为基站或终端或DU；
若所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中，则所述解析模块位于CU中，所述所述接收模块和所述传输模块位于DU中。
本发明实施例提供的一种发送设备，包括：
处理器，用于读取存储器中的程序，执行下列过程：
将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；将所 述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
收发机，用于在处理器的控制下接收和发送数据。
本发明实施例提供的一种接收设备，包括：
处理器，用于读取存储器中的程序，执行下列过程：
将收到的MAC PDU分成多个RLC PDU；将收到的RLC PDU发送给解析模块；在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU。
收发机，用于在处理器的控制下接收和发送数据。
本发明实施例将收到的PDCP PDU(Packet Data Convergence Protocol，分组数据聚合协议；Protocol Data Unit，协议数据单元)组成RLC PDU，并分配对应的RLC SN(SequenceNumber，序列号)，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；从生成的RLC PDU中确定所述调度资源对应的数据；将所述调度资源对应的数据组成MAC PDU进行数据发送处理。由于本发明实施例将PDCP PDU与RLC PDU之间建立绑定关系，每个RLC PDU中包括至少一个PDCP PDU，使得分配模块在收到部分PDCP PDU后就可以生成RLC PDU，从而缩短对层二的数据包处理的时长。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简要介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为背景技术中用户面协议栈示意图；
图2为本发明实施例进行数据发送的方法流程示意图；
图3A为本发明实施例第一种组包示意图；
图3B为本发明实施例第二种组包示意图；
图3C为本发明实施例第三种组包示意图；
图4A为本发明实施例CU-DU分离时下行数据发送示意图；
图4B为本发明实施例CU-DU分离时上行数据发送示意图；
图5为本发明实施例进行数据接收的方法流程示意图；
图6为本发明实施例进行数据发送的系统结构示意图；
图7为本发明实施例进行数据接收的系统结构示意图；
图8为本发明实施例发送设备的结构示意图；
图9为本发明实施例接收设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部份实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
如图2所示，本发明实施例进行数据发送的方法包括：
步骤200、分配模块将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
步骤201、确定模块根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；
步骤202、处理模块将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
本发明实施例将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；从生成的RLC PDU中确定所述调度资源对应的数据；将所述调度资源对应的数据组成MAC PDU进行数据发送处理。由于本发明实施例将PDCP PDU与RLC PDU之间建立绑定关系，每个RLC PDU中包括至少一个PDCP PDU，使得分配模块在收到部分PDCP PDU后就可以生成RLC PDU，从而缩短对层二的数据包处理的时长。
在实施中，每个RLC PDU中包含多少PDCP PDU，可以由高层配置决定(比如配置每个RLC PDU中包含多少个PDCP PDU，也可以配置每个RLC PDU最多可以包含的字节数)，即静态配置；也可以由分配模块根据动态的链路情况和/或负荷情况进行动态配置(比如配置每个RLC PDU中包含多少个PDCP PDU，也可以配置每个RLC PDU最多可以包含的字节数)。
例如，链路状态较好且负荷较轻时，可以设置每个RLC PDU中包含的PDCP PDU多些，当链路状况不好或者负荷较重时，可以设置每个RLC PDU中包含的PDCP PDU少些。
如果分配模块、确定模块和处理模块不在同一个实体中，因为链路状态和负荷情况是在确定模块进行统计，因此如果分配模块位于CU(Central Unit，中央单元)，确定模块和处理模块位于DU(Distributed Unit，分布式单元)，则需要DU将相关的情况反馈给CU，以便于CU的确定模块进行配置。另外，在UE的一个承载通过多个DU传输时，每个DU的状态有可能不相同，也可以支持CU的分配模块根据每个DU的不同情况为每个DU采取不同的动态配置。
当配置了RLC PDU与PDCP PDU是一一映射关系时，则每个PDCP PDU对应于一个RLC PDU；
当配置了RLC PDU中可以包含多个PDCP PDU时，可以同时配置一个RLC PDU中包含的PDCP PDU的个数N，和/或同时配置一个RLC PDU的大小M字节，即一个RLC PDU不能超过M字节。
若配置了个数N，在组成RLC PDU时，将连续的N个PDCP PDU组成一个RLC PDU，并分配一个RLC SN；
若配置了RLC PDU的大小M字节，在组成RLC PDU时，将连续的若干个不超过M字节的PDCP PDU组成一个RLC PDU。可选的，组成RLC PDU得PDCP PDU是不大于该M字节的最大的组包方式。
具体实施中，当一个RLC PDU包含多个PDCP PDU时，多个PDCP PDU位于同一个RLC PDU中，并且对应同一个RLC SN。可将其视为提前将几个PDCP PDU进行组合，形成一个完整RLC PDU，以便于后续处理。这种实施方式下可以应对PDCP PDU是小包的情况，即如果每个小包分别处理，头开销和处理开销都很大，所以可以提前进行级联，变成中等大小的RLC PDU，从而减少头开销和处理开销。
不管RLC PDU中包括多少个PDCP PDU，在后续对RLC PDU的处理中都可以按相同的方式进行处理。
本发明实施例当数据包到达PDCP层之后，会为每个数据包启动一个Discard Timer(丢弃定时器)，在该定时器超时后，如果数据包还没有被处理和发送，可以直接删除，该定时器的长度可以由RRC(Radio Resource Control，无线资源控制)进行配置，长度与业务的QoS(Quality of Service，业务质量)服务质量有关，一般由该业务所能忍受的最大传输时延来确定。
一般来说，PDCP层可以对接收到的高层数据进行一定的缓存，也可以立即对数据进行PDCP层的处理，PDCP层的处理包括：
对与每个来自高层的数据包，将分配一个顺序排列的序列号SN，该SN的初值为0，即分配给第一个SDU(Service Data Units，业务数据单元)的SN为0，第二个SDU的SN为1，依次类推；
根据配置的要求：如果配置了需要进行头压缩，则根据配置的头压缩协议，执行头压缩过程；
根据安全的要求：对数据包进行完整性保护和安全操作，一般来说完整性保护操作仅对控制平面的数据进行，而加密是对所有的数据进行，包括控 制面数据和用户面数据；
增加必要的PDCP头部，PDCP头部中主要包括PDCP SN和PDCP PDU类型指示信息等；
发送至对应的RLC发送端实体。
当分配模块接收到来自PDCP的数据包，即为RLC SDU，一般来说，需要先将其存入发送缓存，等待合适的机会，形成RLC PDU，发送至处理模块，进而经过MAC和物理层处理后，在空口进行发送。
本发明实施例所述分配模块、所述确定模块和所述处理模块位于同一个实体中；或，
所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中；或，
所述分配模块、所述确定模块和所述处理模块位于不同实体中。
若所述分配模块、所述确定模块和所述处理模块位于同一个实体中，则所述实体为基站或终端或DU；
若所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中，则所述分配模块位于CU中，所述确定模块和所述处理模块位于DU中。
一、为了便于描述，下面以整个UP(User Plane，用户平面)的全部三层实体，所述分配模块、所述确定模块和所述处理模块均位于同一个物理实体，或者之间是理想回程连接(即传输时延远远小于毫秒量级)为例对本发明的方案进行描述。
所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中或位于不同实体中或所述分配模块、所述确定模块和所述处理模块之间是非理想回程连接的方式在后续进行介绍。
分配模块将接收到的PDCP PDU按顺序存入发送缓存。
可选的，如果这些数据包中，有不同的优先级标签，则可以对不同的优先级数据进行单独的缓存处理，即相同优先级的数据按照接收顺序进行按序队列缓存，不同优先级的数据有不同的队列。
所述分配模块所述分配模块按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN；或，
所述分配模块按照同一优先级每个PDCP PDU集合的接收顺序分配对应的RLC SN，其中所述PDCP PDU组合中包括至少一个PDCP PDU。
如果PDCP PDU和RLC PDU是一一对应关系，则分配模块可以按照每个PDCP PDU的顺序，为每个PDCP PDU分配对应的RLC SN，比如为第1个PDCP PDU分配0，第2个PDCP PDU分配1，以此类推。
其中，PDCP PDU的SN和RLC PDU的SN有可能是相等的，例如如果PDCP PDU和RLC PDU是一一对应关系，PDCP SN 0，1，2，3，4…就是与RLC SN0，1，2，3，4…数字相同，此时可以将RLC SN进行省略，直接复用PDCP SN作为RLC SN进行RLC的相关操作。即若收到的每个PDCP PDU的PDCP SN的顺序与分配给每个PDCP PDU的RLC SN顺序相同，则生成的所述RLC PDU包括至少一个所述PDCP PDU。
另一种情况，PDCP SN有可能是不连续的，例如一个承载被分配到两条路径去传输，那么其中一个RLC发送实体接收到的PDCP SN有可能顺序是这样的：PDCP SN 0，2，4，6，9…分别按顺序映射成RLC SN 0，1，2，3，4…，或者PDCP PDU由于超时被删除，中间有可能出现空档，如一个RLC实体接收到的PDCP SN有可能顺序是这样的：PDCP SN 0，1，2，5，6，7…分别按顺序映射成RLC SN 0，1，2，3，4，5…。如果RLC PDU包括多个PDCP PDU，比如RLC PDU包括2个PDCP PDU，则PDCP SN 0，1映射成RLC SN 0，PDCP SN 2，3映射成RLC SN 1，以此类推。即生成的所述RLC PDU包括至少一个所述PDCP PDU和分配给所述PDCP PDU的RLC SN。
实施中，RLC需要保证数据包的按序传输，因此RLC SN按顺序分配，中间不能有空档，当PDCP SN满足这个要求时，RLC可以复用PDCP SN以节约头部开销；当PDCP SN不满足顺序并完全连续的要求时，RLC单独分配SN以保证连续性。具体如何选择，可以基于RRC的配置，即RLC SN是否出现由RRC配置决定。
上面的例子中PDCP PDU和RLC PDU是一一对应关系，在实施中也可以是一对多的关系，只要分配模块能记录好这种映射关系，例如固定N个PDCP PDU映射到一个RLC PDU，或者基于不超过M个字节的PDCP PDU可以映射到一个RLC PDU。比如分配模块可以将收到的每两个PDCP PDU组成一个RLC PDU；也可以有的1个组成一个RLC PDU，有的2个组成一个RLC PDU，有的3个组成一个RLC PDU等。
其中，当处理模块调度完成之后，会发送调度资源的数量，例如N个字节。在实施中，当只有一个优先级队列时，分配模块可以在接收到PDCP层数据之后就逐一分配RLC SN，并形成RLC PDU(即所述分配模块在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU)；当有多个优先级队列时，分配模块可以在收到调度资源的数量后，再实时分配SN(即所述分配模块优先为优先级高的PDCP PDU分配对应的RLC SN，例如优先级队列A和B中A的优先级高，则优先为A队列分配对应的RLC SN)，并形成RLC PDU(即所述分配模块在确定调度资源的数量之后将收到的PDCP PDU组成RLC PDU)。前一种方式对实时处理效率的要求不高，在后台准备则可以是另一种可选的实现方式。在当RLC有多条不同优先级队列时，则可以按照一定的优先级而并非先到先处理的原则对RLC SDU进行处理，此时不能提前分配RLC SN和组织RLC PDU，而是在当处理模块通知调度资源后，按照优先级顺序决定发送哪些RLC SDU，此时RLC SDU就能够被分配RLC SN和组织RLC PDU。
当确定模块确定调度资源的数量(比如处于MAC层的处理模块将调度资源的数量通知给确定模块)后，可以实时地根据这个调度资源的数量决定发送多少数据给处理模块，例如第一个RLC PDU大小为200字节，第二个RLCPDU大小为300字节，第三个RLC PDU大小为500字节，调度资源的数量为800字节，则将第一个和第二个RLC PDU(共计500字节)完整的发送到处理模块，并将第三个RLC PDU的前面300字节做成分段的RLC PDU，同时发往处理模块。
也就是说，若所述确定模块根据调度资源的数量确定需要进行分段处理，则根据调度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU(可以称为RLC PDU分段)。
可选的，所述确定模块根据分段信息以及分段后的数据生成新的RLC PDU；
其中，所述分段信息包括下列信息中的部分或全部：
目标RLC PDU的RLC SN；
分段后的数据在目标RLC PDU中的起始位置信息；
分段后的数据的长度信息；
用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
比如，RLC PDU分段的格式如下：
可选的，需要携带RLC SN，针对同一个RLC PDU，其不同分段携带的SN一定是同一个SN，即对应原始RLC PDU；
可选的，需要携带该RLC PDU分段在原始RLC PDU中的起始位置SO(Segment offset)，例如如果是第一个分段则起始位置为0，如果是RLC PDU的第300-500字节，则起始位置为300；
可选的，RLC分段中需要携带分段的长度，例如这个原始RLC PDU的0-200字节的一个分段，则长度为200字节，之所以长度域在RLC分段头部域中可选，是因为该长度有可能在MAC组包时候体现；
可选的，需要携带是否最后一个分段的标识LSF(Last segment flag，最后分段标识)，比如显式的1bit指示，例如0代表非最后一个分段，1代表最后一个分段。
其中，本发明实施例的RLC PDU可以是初始传输的RLC PDU和/或重传的RLC PDU。
在实施中，不管重传还是初始传输，如果调度资源的数量不够容纳整个RLC PDU时，可以对RLC PDU进行分段，以适应调度资源的数量，这样可以提高传输效率，不浪费传输资源。
其中，对于重传分段分为两种：
请求重传RLC PDU，但传输资源不够，不足以容纳整个RLC PDU，需要根据资源大小对RLC PDU进行分段；
请求重传RLC PDU分段，但传输资源不够，不足以容纳要求的全部RLC PDU分段，需要根据资源大小对RLC PDU进行再次分段；
无论是上述哪种情况，针对重传来说，对RLC PDU的重传分段都是与初传的分段是类似的，即以RLC SN指示该分段归属哪个RLC PDU，以SO，LI，LSF来指示分段在原始RLC PDU中所处的位置、长度和是否最后一个分段。
举例说明：当需要重传的RLC PDU分段在RLC PDU的SN＝10中处于[500，1500]字节的位置，且该RLC PDU一共长度为1500字节。第一次传输机会资源大小为700字节，则根据传输资源大小组织RLC PDU分段，其中RLC PDU的SN＝10，SO＝500，LI＝700，LSF＝0(不是最后分段)，第二次传输机会资源大小为300字节，则根据传输资源大小组织RLC PDU分段，其中RLC PDU的SN＝10，SO＝1200，LI＝300，LSF＝1(是最后分段)。
对于接收端来说，由于RLC PDU的SN＝10的前面[0-500)已经确认接收，NACK后面的部分，则在接收到上述两次重传之后，认为RLC PDU的SN＝10全部收到，因为按顺序收到了全部字节，直至最后一个分段。则该PDU正确接收。
可选的，所述处理模块将所述调度资源对应的数据组成MAC PDU时，将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；将排序后的RLC PDU组成MAC PDU。
其中，MAC PDU的组织原则如下：
将来自于相同逻辑信道的RLC PDU和RLC PDU分段尽量按照SN顺序或者优先级顺序组织在一起；
对于不同逻辑信道之间的数据，尽量将高优先级的逻辑信道的数据放在MAC PDU的前部，低优先级的逻辑信道的数据放在MAC PDU的后部，即按 照逻辑信道优先级的顺序放置不同逻辑信道的数据。
一种典型的组包过程如图3A所示，其中，P-SN代表PDCP SN，R-SN代表RLC SN，LCID(Logical Channel ID)为逻辑信道标识，LI为长度指示域。LCID1的数据由于具有比LCID2更高的优先级，因此可以放置在MAC PDU前部，并且尽量一个逻辑信道的RLC PDU集中放置。对于LCID2的数据由于是一个分段，而且是第一个分段，则分段指示SO为0。这里还有另一种简化的方案是用1bit指示这是一个分段且第一个分段；对于第二次传输的LCID2的第二个分段，需要携带显示的SO指示。
例如在时刻1，LCID2中传输第一个分段，这个分段由于是从原始RLC PDU其SN＝n的初始位置开始，因此可以携带SO＝0来指示这是第一个分段，也可以以一个特殊的比特域(FS：First segment)，比如1比特信息，FS取值为1代表第一分段，FS取值为0代表非第一分段。当第一分段时，由于已经携带的FS＝1明确指示了这是第一分段，因此SO＝0此时可以省略。
对于下一传输时刻2，需要传输此LCID2的相同RLC PDU其SN＝n的第二个分段，此时因为不是第一个分段，因此需要显示携带SO来指示第二分段在原始RLC PDU中的起始位置。
在实施中，所述处理模块根据排序后的RLC PDU的LCID组成MAC PDU；
其中，所述MAC PDU包括每个RLC PDU分别的LCID。
还有一种可行的实施方式是所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。具体如图3B所示，该例中，将相同LCID的数据包集中在一起，并且携带统一的LCID。
上面的两个例子中分配模块和确定模块位于RLC层，处理模块位于MAC层。为进一步简化，可以将分配模块、确定模块和处理模块都置于MAC层，具体如图3C所示。
在实施中，确定模块和处理模块可以接续的并行处理，从而节省处理的时间，比如确定模块将处理好的MAC PDU可以先发送给处理模块进行后续处理，同时确定模块继续处理后续的MAC PDU。
需要说明的是上面的描述中，每一层的头格式中仅是示意出了一些域，例如SN，LI，LCID等，但具体实施中，头部中还可能有其他域，例如类型指示D/C用于指示数据或控制，E域为扩展指示域，LS用于指示最后一个分段等，在此不再一一列举。
二、所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中或位于不同实体中或所述分配模块、所述确定模块和所述处理模块之间是非理想回程连接的方式在后续进行介绍。
这里假设所述分配模块位于CU中，所述确定模块和所述处理模块位于DU中。
图4A给出了一种典型的下行数据的CU/DU实体的处理过程。
其中CU为集中处理实体，DU为分布式处理实体。
RLC-H是所述分配模块，RLC-L是所述确定模块，分别位于CU和DU两个物理实体。
下行数据发送过程如下：
1：PDCP将高层数据分配的PDCP SN，安全操作，头压缩，增加头部之后，形成PDCP PDU，并将其发送到对应的RLC-H实体；
2：RLC-H实体对接收到的PDCP PDU给其顺序分配RLC SN，RLC PDU和PDCP PDU为一一对应的关系，并将数据和对应的RLC SN分发到一个或者多个RLC-L实体。
其中，选择的方式为根据流控和反馈，选择链路条件较好和负荷较轻的路径，或者为了满足传输时延低可靠性高的要求，可以给多条RLC-L实体发送相同的数据，同时传输；
3：位于DU的RLC-L实体，根据MAC层实时调度的传输资源尺寸，将合适大小的RLC PDU和RLC PDU分段组合发送到MAC层，进行后续传输，其中RLC PDU分段以原始的PDCP PDU为对象，携带RLC-H分配的RLC SN，并SO，LI和LSF等域进行分段指示。
本发明实施例通过MAC/PHY的处理后进行空口传输，再经过对端 PHY/MAC处理，交给接收端RLC-L，并汇聚到RLC-H，由RLC-H完成接收状态的更新，反馈，数据包重组，并提交给PDCP。PDCP支持乱序的解安全和解头压缩等操作。
可选的，此处可以由RLC-L先完成RLC PDU的重组，再递交给RLC-H，或者直接支持RLC-L将RLC PDU分段递交给RLC-H，由RLC-H完成最终重组和排序。一般来说，当各个路径传输相同RLC PDU时，可以由RLC-H将来自不同路径的RLC PDU分段进行重组，加快重组的进度和降低时延。因此在多路径重复数据发送时，可以将RLC PDU分段的重组功能位于RLC-H，否则可以位于RLC-L，即根据情况可配置。
另外，在本发明实施例中，仅是给出了一种典型的CU/DU之间用户面协议栈的分布例子，事实上，本案所支持的数据处理方法，也可以支持仅PDCP协议位于CU，而RLC和MAC均位于DU，或者可以支持PDCP和多个RLC-H协议位于CU，而多个RLC-L和MAC均位于DU，数据处理方式是类似的，在此不再赘述。
如图5所示，本发明实施例进行数据接收的方法包括：
步骤500、接收模块将收到的MAC PDU分成多个RLC PDU；
步骤501、传输模块将收到的RLC PDU发送给解析模块；
步骤502、解析模块在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU。
本发明实施例所述接收模块、所述传输模块和所述解析模块位于同一个实体中；或，
所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中；或，
所述接收模块、所述传输模块和所述解析模块位于不同实体中。
若所述接收模块、所述传输模块和所述解析模块位于同一个实体中，则所述实体为基站或终端或DU；
若所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中，则所述解析模块位于CU中，所述所述接收模块和所述传输模块位于DU中。
一、为了便于描述，下面以整个用户平面UP(User Plane)的全部三层实体，所述接收模块、所述传输模块和所述解析模块均位于同一个物理实体或者之间是理想回程连接(即传输时延远远小于毫秒量级)为例进行描述。
所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中或位于不同实体中或所述接收模块、所述传输模块和所述解析模块之间是非理想回程连接的方式在后续进行介绍。
接收端是发送端的反向过程。当数据由物理层从空口接收到之后，进行物理层处理之后，恢复成MAC PDU的格式。
接收到数据，根据其中携带的LCID和LI等信息，解出不同的数据块，根据LCID的指示确定归属于不同的逻辑信道的RLC PDU(其中也可以包括进行分段处理的RLC PDU)。
传输模块在收到RLC PDU后有两种处理方式：
方式1、所述传输模块直接将收到的RLC PDU发送给解析模块。
这种方式所述传输模块在接收到RLC PDU后，将RLC PDU递交给解析模块，对于进行过分段处理的RLC PDU也直接递交给解析模块。
方式1实际上是一种类似于透传的方式，即直接将收到的数据全部发送到RLC Higher(即解析模块)去处理，例如Gap(间隔)检测，重排序Treordering定时器，状态反馈NACK/ACK等。
方式2、所述传输模块根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
所述传输模块对收到的RLC PDU进行重排序，对于进行分段处理的RLC PDU进行重组后再进行重排序，从而消除了MAC HARQ引起的乱序，并递交给解析模块。
如果出现非连续接收的RLC PDU，则启动Treordering_timer，在Treordering_timer超时后，如果仍然没有接收完整的RLC PDU，此时可以将 经过Treordering_timer检测的RLC PDU递交给解析模块，也可以不递交给解析模块，等待接收完整后在递交。
这里的排序是指按照RLC SN的顺序，进行接收状态的更新，例如：
如果当前按序接收数据的最高SN为3，则最高SN的下一个SN为4，若此次新接收到的SN为4，则认为按序接收，将按序接收数据的最高SN的下一个更新为5(当然，这里也可以只记录最高的SN，而不记录最高SN的下一个SN)；
如果中间出现了SN的缺口(比如接收到的RLC PDU的SN为3，下一个变成5，则确认出现SN的缺口)，则可以启动T-reordering定时器对底层传输导致的乱序进行检测，如果在T-reordering定时器超时后未收到的PDU，则放弃等待(针对UM(Unacknowledged Mode，非确认模式))或者由所述解析模块反馈NACK状态报告请求重传(针对AM(Acknowledged Mode，确认模式))。
其中，所述传输模块将收到的RLC PDU发送给解析模块之后，所述解析模块根据收到的RLC PDU的RLC SN生成反馈信息。之后可以按照本发明实施例发送的方法将反馈信息进行发送。
针对不同的接收情况，反馈信息的内容也不相同，下面分别进行介绍。
情况1、若未出现SN的缺口，即接收成功，则反馈信息中包括ACK(ACKnowledge，正确应答指令)信息。
情况2、若出现SN的缺口，即有RLC PDU丢失，则反馈信息中包括NACK(Negative ACKnowledge，错误应答指令)信息。
对于针对出现SN的缺口的反馈信息，由于允许根据传输资源的大小对RLC PDU数据进行分段，因此缺口可能是整个的RLC PDU丢失，也可能是RLC PDU分段丢失，还可能是连续的一串RLC PDU连续丢失。
在NACK状态报告中，需要考虑高效及节省开销，对单个出现的RLC PDU丢失，以单独的NACK_SN来显式指示；对RLC PDU分段丢失，以NACK_SN携带SO和LI来显式指示；对连续出现的多个连续SN的RLC PDU丢失，以 第一个NACK_SN携带连续丢失的PDU个数来显式指示。只有NACK的信息需要逐一指示，ACK_SN仅需要一个，指示该ACK_SN以下的所有PDU除了显示指示为NACK的PDU或者PDU分段之外的所有PDU均正确接收。
下面对出现SN的缺口的反馈信息进行说明。
1、若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN。
比如接收到的RLC PDU的SN为3，下一个接收到RLC PDU的SN为5，则确认SN为4的RLC PDU丢失，可以将4加入到反馈信息中。
2、若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息。
比如接收到的RLC PDU分段的SN为3，下一个接收到的RLC PDU的SN为4，根据收到的SN为3的RLC PDU确定是分段的RLC PDU，并且可以确定具体哪段未收到，假设第一分段未收到，丢失的RLC PDU的长度为200字节，则反馈信息中包括SN＝3，长度＝200，还包括用于表示丢失分段在原始RLC PDU中的起始位置SO＝0或者第一分段指示FS＝1。可选的，在表示长度的时候，可以以长度指示来显示，也可以以该分段在原始RLC PDU中的结束位置来表示。
3、若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量。
比如接收到RLC PDU的SN为3，下一个接收到的RLC PDU的SN为7，则确定SN为4、5和6的RLC PDU丢失，则反馈信息中包括4(即第一个RLC PDU的RLC SN)和3(丢失的RLC PDU的数量)。
4、若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU 是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
比如接收到SN为4的原始的RLC PDU中的一部分，下一个接收到的RLC PDU的SN为7，则确定SN为4、5和6的RLC PDU丢失。若SN为4、5和6的RLC PDU中N为4的RLC PDU是分段的RLC PDU，则反馈信息中包括4(即第一个RLC PDU的RLC SN)、3(丢失的RLC PDU的数量)和用于指示分段的RLC PDU的信息(比如00表示第一个RLC PDU分段，01表示最后一个RLC PDU分段，11表示第一个和最后一个RLC PDU分段)。
对于接收端只根据接收状态来反馈，如果整个RLC PDU都没有收到(即使该RLC PDU是分段的)，则SN即可表征丢失的整个RLC PDU，如果接收到RLC PDU的部分分段，则丢失RLC PDU分段的分段信息需要在状态报告中携带。
这里如果需要反馈连续的RLC PDU丢失的相关信息，则连续丢失的RLC PDU中没有分段的RLC PDU，或者第一个RLC PDU和/或最后一个RLC PDU是分段的PDU，如果连续丢失的RLC PDU的中间有分段的RLC PDU，可以采用上述第1种和第2种方式，即单独反馈未分段的RLC PDU和分段的RLC PDU；也可以符合要求的采用连续的方式反馈，不符合的采用单独的方式反馈。
比如丢失的RLC PDU为3～8，其中7是的分段的RLC PDU，可以3～6采用连续方式，7和8采用单独方式；也可以3～6采用连续方式，7和8采用连续方式。
在实施中，当RLC PDU整个被接收到，并且处于接收窗口内部，即便不是按序接收到的RLC PDU，解析模块也可以解出里面的PDCP PDU发送至PDCP层进行提前的解密，解完整性保护和解头压缩等处理。
对于PDCP层，当接收到RLC层发送来的PDCP PDU，则对其进行接收判断，判断是否是接收窗口之内的正常数据包，是否重复等，对符合接收条件的包进行解密，解完整性保护和解头压缩等操作，之后对该数据包进行重排序，如果符合按序递交的要求，则可以递交给高层，否则，需要进行重排 序等待，以便后续缺口数据补足之后，统一按序递交高层。
二、所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中或位于不同实体中或所述接收模块、所述传输模块和所述解析模块之间是非理想回程连接的方式在后续进行介绍。
图4B给出了一种典型的上行数据的CU/DU实体的处理过程
这里假设所述解析模块位于CU中，所述传输模块和所述接收模块位于DU中。
1、DU的MAC层(即接收模块)在接收到MAC PDU数据之后，解析出不同逻辑信道的RLC PDU或者RLC PDU分段，将其发送给DU的RLC Lower模块(即传输模块)；
2、RLC Lower模块可以不做任何处理，直接递交给CU中的RLC Higher模块(即解析模块)，或者RLC Lower模块进行重排序和重组之后，再递交给RLC Higher模块；
3、RLC Higher模块对RLC PDU或者RLC PDU的分段进行重排序和必要的重组等操作，并且按照规定反馈状态报告；RLC Higher模块将解析出的PDCP PDU发送给PDCP层；
4、PDCP层进行解密，解完整性保护，解头压缩等操作，然后AM模式下进行重排序，按序递交给高层。
从上述内容可以看出，本发明实施例可以使层二的数据在各层之间实时快速的接续并行处理，提升了处理的实时性效率，并且针对初传分段和重传分段具有统一的格式和处理过程，简化了处理的复杂度，提升了层二对大量数据包的处理效率，将更适用于未来5G各种应用场景。
基于同一发明构思，本发明实施例中还提供了一种进行数据发送的系统，由于该系统解决问题的原理与本发明实施例进行数据发送的方法相似，因此该设备的实施可以参见系统的实施，重复之处不再赘述。
如图6所示，本发明实施例进行数据发送的系统包括：
分配模块600，用于将收到的PDCP PDU组成RLC PDU，并分配对应的 RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
确定模块601，用于根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；
处理模块602，用于将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
可选的，所述分配模块600具体用于：
按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN。
可选的，所述分配模块600具体用于：
为优先级高的PDCP PDU优先分配。
可选的，生成的所述RLC PDU包括至少一个所述PDCP PDU和分配的RLC SN；或，
若收到的每个PDCP PDU的PDCP SN的顺序与分配的RLC SN顺序相同，则生成的所述RLC PDU包括至少一个所述PDCP PDU。
可选的，所述分配模块600具体用于：
在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU；或，
在确定调度资源的数量之后将收到的PDCP PDU组成RLC PDU。
可选的，所述确定模块601具体用于：
若根据调度资源的数量确定需要进行分段处理，则根据调度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU。
可选的，所述确定模块601具体用于：
根据分段信息以及分段后的数据生成新的RLC PDU；
其中，所述分段信息包括下列信息中的部分或全部：
目标RLC PDU的RLC SN；
分段后的数据在目标RLC PDU中的起始位置信息；
分段后的数据的长度信息；
用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
可选的，所述处理模块602具体用于：
将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；
将排序后的RLC PDU组成MAC PDU。
可选的，所述处理模块602具体用于：
根据排序后的RLC PDU的LCID组成MAC PDU；
其中，所述MAC PDU包括每个RLC PDU分别的LCID；或所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。
可选的，所述RLC PDU为初始传输的RLC PDU和/或重传的RLC PDU。
可选的，所述分配模块600、所述确定模块601和所述处理模块602位于同一个实体中；或，
所述分配模块600、所述确定模块601和所述处理模块602部分位于同一个实体中；或，
所述分配模块600、所述确定模块601和所述处理模块602位于不同实体中。
可选的，若所述分配模块600、所述确定模块601和所述处理模块602位于同一个实体中，则所述实体为基站或终端或DU；
若所述分配模块600、所述确定模块601和所述处理模块602部分位于同一个实体中，则所述分配模块600位于CU中，所述确定模块601和所述处理模块602位于DU中。
基于同一发明构思，本发明实施例中还提供了一种进行数据接收的系统，由于该系统解决问题的原理与本发明实施例进行数据接收的方法相似，因此该设备的实施可以参见系统的实施，重复之处不再赘述。
如图7所示，本发明实施例进行数据接收的系统包括：
接收模块700，用于将收到的MAC PDU分成多个RLC PDU；
传输模块701，用于将收到的RLC PDU发送给解析模块；
解析模块702，用于在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU。
可选的，所述解析模块702还用于：
根据收到的RLC PDU的RLC SN生成反馈信息；
其中，若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN；或，
若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息；或，
若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量；或，
若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
可选的，所述传输模块701具体用于：
直接将收到的RLC PDU发送给解析模块；或，
根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
可选的，所述接收模块700、所述传输模块701和所述解析模块702位于同一个实体中；或，
所述接收模块700、所述传输模块701和所述解析模块702部分位于同一个实体中；或，
所述接收模块700、所述传输模块701和所述解析模块702位于不同实体中。
可选的，若所述接收模块700、所述传输模块701和所述解析模块702位于同一个实体中，则所述实体为基站或终端或DU；
若所述接收模块700、所述传输模块701和所述解析模块702部分位于同一个实体中，则所述解析模块702位于CU中，所述所述接收模块700和所述传输模块701位于DU中。
图8下面给出一种分配模块600、确定模块601和处理模块602在同一个实体的例子，分配模块600、确定模块601和处理模块602部分在同一个实体或都在不同实体与图8结构类似，区别在于处理器处理哪个模块(或哪些模块)的功能，在此不再赘述。
基于同一发明构思，本发明实施例中还提供了一种发送设备，由于该设备解决问题的原理与本发明实施例进行数据发送的方法相似，因此该设备的实施可以参见系统的实施，重复之处不再赘述。
如图8所示，本发明实施例的发送设备包括：
处理器801，用于读取存储器804中的程序，执行下列过程：
将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
收发机802，用于在处理器801的控制下接收和发送数据。
可选的，所述处理器801具体用于：
按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN。
可选的，所述处理器801具体用于：
为优先级高的PDCP PDU优先分配。
可选的，生成的所述RLC PDU包括至少一个所述PDCP PDU和分配的RLC SN；或，
若收到的每个PDCP PDU的PDCP SN的顺序与分配的RLC SN顺序相同， 则生成的所述RLC PDU包括至少一个所述PDCP PDU。
可选的，所述处理器801具体用于：
在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU；或，
在确定调度资源的数量之后将收到的PDCP PDU组成RLC PDU。
可选的，所述处理器801具体用于：
若根据调度资源的数量确定需要进行分段处理，则根据调度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU。
可选的，所述处理器801具体用于：
根据分段信息以及分段后的数据生成新的RLC PDU；
其中，所述分段信息包括下列信息中的部分或全部：
目标RLC PDU的RLC SN；
分段后的数据在目标RLC PDU中的起始位置信息；
分段后的数据的长度信息；
用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
可选的，所述处理器801具体用于：
将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；
将排序后的RLC PDU组成MAC PDU。
可选的，所述处理器801具体用于：
根据排序后的RLC PDU的LCID组成MAC PDU；
其中，所述MAC PDU包括每个RLC PDU分别的LCID；或所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。
可选的，所述RLC PDU为初始传输的RLC PDU和/或重传的RLC PDU。
在图8中，总线架构(用总线800来代表)，总线800可以包括任意数量的互联的总线和桥，总线800将包括由处理器801代表的一个或多个处理器和存储器804代表的存储器的各种电路链接在一起。总线800还可以将诸如 外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口803在总线800和收发机802之间提供接口。收发机802可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器801处理的数据通过天线805在无线介质上进行传输，进一步，天线805还接收数据并将数据传送给处理器801。
处理器801负责管理总线800和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器804可以被用于存储处理器801在执行操作时所使用的数据。
可选的，处理器801可以是CPU(中央处埋器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
基于同一发明构思，本发明实施例中还提供了一种接收设备，由于该设备解决问题的原理与本发明实施例进行数据接收的方法相似，因此该设备的实施可以参见系统的实施，重复之处不再赘述。
图9下面给出一种接收模块700、传输模块701和解析模块702在同一个实体的例子，接收模块700、传输模块701和解析模块702部分在同一个实体或都在不同实体与图9结构类似，区别在于处理器处理哪个模块(或哪些模块)的功能，在此不再赘述。
如图9所示，本发明实施例的接收设备包括：
处理器901，用于读取存储器904中的程序，执行下列过程：
将收到的MAC PDU分成多个RLC PDU；将收到的RLC PDU发送给解析模块；在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU。
收发机902，用于在处理器901的控制下接收和发送数据。
可选的，所述处理器901还用于：
根据收到的RLC PDU的RLC SN生成反馈信息；
其中，若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN；或，
若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息；或，
若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量；或，
若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
可选的，所述处理器901具体用于：
直接将收到的RLC PDU发送给解析模块；或，
根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
在图9中，总线架构(用总线900来代表)，总线900可以包括任意数量的互联的总线和桥，总线900将包括由处理器901代表的一个或多个处理器和存储器904代表的存储器的各种电路链接在一起。总线900还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口903在总线900和收发机902之间提供接口。收发机902可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器901处理的数据通过天线905在无线介质上进行传输，进一步，天线905还接收数据并将数据传送给处理器901。
处理器901负责管理总线900和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器904可以被用于存储处理器901在执行操作时所使用的数据。
可选的，处理器901可以是CPU、ASIC、FPGA或CPLD。
以上参照示出根据本申请实施例的方法、装置(系统)和/或计算机程序产品的框图和/或流程图描述本申请。应理解，可以通过计算机程序指令来实现框图和/或流程图示图的一个块以及框图和/或流程图示图的块的组合。可以将这些计算机程序指令提供给通用计算机、专用计算机的处理器和/或其它可编程数据处理装置，以产生机器，使得经由计算机处理器和/或其它可编程数据处理装置执行的指令创建用于实现框图和/或流程图块中所指定的功能/动作的方法。
相应地，还可以用硬件和/或软件(包括固件、驻留软件、微码等)来实施本申请。更进一步地，本申请可以采取计算机可使用或计算机可读存储介质上的计算机程序产品的形式，其具有在介质中实现的计算机可使用或计算机可读程序代码，以由指令执行系统来使用或结合指令执行系统而使用。在本申请上下文中，计算机可使用或计算机可读介质可以是任意介质，其可以包含、存储、通信、传输、或传送程序，以由指令执行系统、装置或设备使用，或结合指令执行系统、装置或设备使用。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (36)

  1. 一种进行数据发送的方法，其特征在于，该方法包括：
    分配模块将收到的分组数据聚合协议协议数据单元PDCP PDU组成无线链路控制协议数据单元RLC PDU，并分配对应的RLC序列号SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
    确定模块根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；
    处理模块将所述调度资源对应的数据组成媒体接入控制协议数据单元MAC PDU，并根据所述MAC PDU进行数据发送处理。
  2. 如权利要求1所述的方法，其特征在于，所述分配模块分配对应的RLC SN，包括：
    所述分配模块按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN；或，
    所述分配模块按照同一优先级每个PDCP PDU集合的接收顺序分配对应的RLC SN，其中所述PDCP PDU组合中包括至少一个PDCP PDU。
  3. 如权利要求2所述的方法，其特征在于，所述分配模块为优先级高的PDCP PDU优先分配。
  4. 如权利要求1所述的方法，其特征在于，生成的所述RLC PDU包括至少一个所述PDCP PDU和分配的RLC SN；或，
    若收到的每个PDCP PDU的PDCP SN的顺序与分配的RLC SN顺序相同，则生成的所述RLC PDU包括至少一个所述PDCP PDU。
  5. 如权利要求1所述的方法，其特征在于，所述分配模块分配对应的RLC SN，包括：
    所述分配模块在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU；或，
    所述分配模块在确定调度资源的数量之后将收到的PDCP PDU组成RLC  PDU。
  6. 如权利要求1所述的方法，其特征在于，所述确定模块根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据，包括：
    若所述确定模块根据调度资源的数量确定需要进行分段处理，则根据调度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU。
  7. 如权利要求6所述的方法，其特征在于，所述确定模块对所述目标RLC PDU进行分段处理生成新的RLC PDU，包括：
    所述确定模块根据分段信息以及分段后的数据生成新的RLC PDU；
    其中，所述分段信息包括下列信息中的部分或全部：
    目标RLC PDU的RLC SN；
    分段后的数据在目标RLC PDU中的起始位置信息；
    分段后的数据的长度信息；
    用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
  8. 如权利要求1所述的方法，其特征在于，所述处理模块将所述调度资源对应的数据组成MAC PDU，包括：
    所述处理模块将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；
    所述处理模块将排序后的RLC PDU组成MAC PDU。
  9. 如权利要求8所述的方法，其特征在于，所述处理模块将排序后的RLC PDU组成MAC PDU，包括：
    所述处理模块根据排序后的RLC PDU的LCID组成MAC PDU；
    其中，所述MAC PDU包括每个RLC PDU分别的LCID；或所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。
  10. 如权利要求1～9任一所述的方法，其特征在于，所述RLC PDU为初始传输的RLC PDU和/或重传的RLC PDU。
  11. 如权利要求1～9任一所述的方法，其特征在于，所述分配模块、所 述确定模块和所述处理模块位于同一个实体中；或，
    所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中；或，
    所述分配模块、所述确定模块和所述处理模块位于不同实体中。
  12. 如权利要求11所述的方法，其特征在于，若所述分配模块、所述确定模块和所述处理模块位于同一个实体中，则所述实体为基站或终端或分布式处理实体DU；
    若所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中，则所述分配模块位于集中处理实体CU中，所述确定模块和所述处理模块位于DU中。
  13. 一种进行数据接收的方法，其特征在于，该方法包括：
    接收模块将收到的MAC PDU分成多个RLC PDU；
    传输模块将收到的RLC PDU发送给解析模块；
    解析模块在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU。
  14. 如权利要求13所述的方法，其特征在于，所述传输模块将收到的RLC PDU发送给解析模块之后，还包括：
    所述解析模块根据收到的RLC PDU的RLC SN生成反馈信息；
    其中，若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN；或，
    若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息；或，
    若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量；或，
    若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
  15. 如权利要求13所述的方法，其特征在于，所述传输模块将收到的RLC PDU发送给解析模块，包括：
    所述传输模块直接将收到的RLC PDU发送给解析模块；或，
    所述传输模块根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
  16. 如权利要求13～15任一所述的方法，其特征在于，所述接收模块、所述传输模块和所述解析模块位于同一个实体中；或，
    所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中；或，
    所述接收模块、所述传输模块和所述解析模块位于不同实体中。
  17. 如权利要求16所述的方法，其特征在于，若所述接收模块、所述传输模块和所述解析模块位于同一个实体中，则所述实体为基站或终端或DU；
    若所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中，则所述解析模块位于CU中，所述所述接收模块和所述传输模块位于DU中。
  18. 一种进行数据发送的系统，其特征在于，该系统包括：
    分配模块，用于将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
    确定模块，用于根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；
    处理模块，用于将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
  19. 如权利要求18所述的系统，其特征在于，所述分配模块具体用于：
    按照同一优先级每个PDCP PDU的接收顺序分配对应的RLC SN；或，
    按照同一优先级每个PDCP PDU集合的接收顺序分配对应的RLC SN，其中所述PDCP PDU组合中包括至少一个PDCP PDU。
  20. 如权利要求19所述的系统，其特征在于，所述分配模块具体用于：
    为优先级高的PDCP PDU优先分配。
  21. 如权利要求18所述的系统，其特征在于，生成的所述RLC PDU包括至少一个所述PDCP PDU和分配的RLC SN；或，
    若收到的每个PDCP PDU的PDCP SN的顺序与分配的RLC SN顺序相同，则生成的所述RLC PDU包括至少一个所述PDCP PDU。
  22. 如权利要求18所述的系统，其特征在于，所述分配模块具体用于：
    在确定调度资源的数量之前将收到的PDCP PDU组成RLC PDU；或，
    在确定调度资源的数量之后将收到的PDCP PDU组成RLC PDU。
  23. 如权利要求18所述的系统，其特征在于，所述确定模块具体用于：
    若根据调度资源的数量确定需要进行分段处理，则根据调度资源的数量确定需要进行分段的目标RLC PDU，并对所述目标RLC PDU进行分段处理生成新的RLC PDU。
  24. 如权利要求23所述的系统，其特征在于，所述确定模块具体用于：
    根据分段信息以及分段后的数据生成新的RLC PDU；
    其中，所述分段信息包括下列信息中的部分或全部：
    目标RLC PDU的RLC SN；
    分段后的数据在目标RLC PDU中的起始位置信息；
    分段后的数据的长度信息；
    用于表示分段后的数据是否是目标RLC PDU中最后的分段数据。
  25. 如权利要求18所述的系统，其特征在于，所述处理模块具体用于：
    将相同逻辑信道的RLC PDU按照RLC SN进行排序，以及将不同逻辑信道的RLC PDU按照优先级进行排序；
    将排序后的RLC PDU组成MAC PDU。
  26. 如权利要求25所述的系统，其特征在于，所述处理模块具体用于：
    根据排序后的RLC PDU的LCID组成MAC PDU；
    其中，所述MAC PDU包括每个RLC PDU分别的LCID；或所述MAC PDU包括不同的LCID，对应同一个LCID的RLC PDU共用一个LCID。
  27. 如权利要求18～26任一所述的系统，其特征在于，所述RLC PDU为初始传输的RLC PDU和/或重传的RLC PDU。
  28. 如权利要求18～26任一所述的系统，其特征在于，所述分配模块、所述确定模块和所述处理模块位于同一个实体中；或，
    所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中；或，
    所述分配模块、所述确定模块和所述处理模块位于不同实体中。
  29. 如权利要求28所述的系统，其特征在于，若所述分配模块、所述确定模块和所述处理模块位于同一个实体中，则所述实体为基站或终端或DU；
    若所述分配模块、所述确定模块和所述处理模块部分位于同一个实体中，则所述分配模块位于CU中，所述确定模块和所述处理模块位于DU中。
  30. 一种进行数据接收的系统，其特征在于，该系统包括：
    接收模块，用于将收到的MAC PDU分成多个RLC PDU；
    传输模块，用于将收到的RLC PDU发送给解析模块；
    解析模块，用于在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN。
  31. 如权利要求30所述的系统，其特征在于，所述解析模块还用于：
    根据收到的RLC PDU的RLC SN生成反馈信息；
    其中，若有未分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU的RLC SN；或，
    若有分段的RLC PDU丢失，则反馈信息中包括丢失的RLC PDU所属的原始RLC PDU的RLC SN、用于表示丢失的RLC PDU在原始RLC PDU中的起始位置的信息以及丢失的RLC PDU的长度信息；或，
    若有连续的RLC PDU丢失，且连续的RLC PDU中没有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN和丢失的RLC PDU的数量；或，
    若有连续的RLC PDU丢失，且连续的RLC PDU中有分段的RLC PDU，则反馈信息中包括连续的RLC PDU中第一个RLC PDU的RLC SN、用于指示分段的RLC PDU的信息和丢失的RLC PDU的数量，其中分段的RLC PDU是连续的RLC PDU中第一个RLC PDU和/或最后一个RLC PDU。
  32. 如权利要求30所述的系统，其特征在于，所述传输模块具体用于：
    直接将收到的RLC PDU发送给解析模块；或，
    根据收到的RLC PDU的RLC SN，对收到的RLC PDU进行排序和/或重组后发送给解析模块。
  33. 如权利要求30～32任一所述的系统，其特征在于，所述接收模块、所述传输模块和所述解析模块位于同一个实体中；或，
    所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中；或，
    所述接收模块、所述传输模块和所述解析模块位于不同实体中。
  34. 如权利要求33所述的系统，其特征在于，若所述接收模块、所述传输模块和所述解析模块位于同一个实体中，则所述实体为基站或终端或DU；
    若所述接收模块、所述传输模块和所述解析模块部分位于同一个实体中，则所述解析模块位于CU中，所述所述接收模块和所述传输模块位于DU中。
  35. 一种发送设备，其特征在于，包括：
    处理器，用于读取存储器中的程序，执行下列过程：
    将收到的PDCP PDU组成RLC PDU，并分配对应的RLC SN，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；根据调度资源的数量从生成的RLC PDU中确定所述调度资源对应的数据；将所述调度资源对应的数据组成MAC PDU，并根据所述MAC PDU进行数据发送处理。
    收发机，用于在处理器的控制下接收和发送数据。
  36. 一种接收设备，其特征在于，包括：
    处理器，用于读取存储器中的程序，执行下列过程：
    将收到的MAC PDU分成多个RLC PDU；将收到的RLC PDU发送给解析模块；在确定能够解析后，对排序和/或重组后的RLC PDU进行解析得到PDCP PDU，其中每个RLC PDU对应一个RLC SN，每个RLC PDU中包括至少一个PDCP PDU；
    收发机，用于在处理器的控制下接收和发送数据。
PCT/CN2017/105729 2016-11-03 2017-10-11 一种进行数据发送和接收的方法及系统 WO2018082433A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17867792.8A EP3537827A4 (en) 2016-11-03 2017-10-11 METHOD AND SYSTEM FOR SENDING AND RECEIVING DATA
JP2019523796A JP2019533395A (ja) 2016-11-03 2017-10-11 データを送受信するための方法およびシステム
KR1020197015912A KR20190075119A (ko) 2016-11-03 2017-10-11 데이터를 송수신하기 위한 방법 및 시스템
US16/346,462 US10986653B2 (en) 2016-11-03 2017-11-10 Method and system for sending and receiving data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610959950.6 2016-11-03
CN201610959950.6A CN108024374A (zh) 2016-11-03 2016-11-03 一种进行数据发送和接收的方法及系统

Publications (1)

Publication Number Publication Date
WO2018082433A1 true WO2018082433A1 (zh) 2018-05-11

Family

ID=62075776

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105729 WO2018082433A1 (zh) 2016-11-03 2017-10-11 一种进行数据发送和接收的方法及系统

Country Status (6)

Country Link
US (1) US10986653B2 (zh)
EP (1) EP3537827A4 (zh)
JP (1) JP2019533395A (zh)
KR (1) KR20190075119A (zh)
CN (1) CN108024374A (zh)
WO (1) WO2018082433A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3319252A1 (en) * 2016-11-04 2018-05-09 Panasonic Intellectual Property Corporation of America Efficient multiplexing of control information in transport block
US11050721B2 (en) * 2016-12-26 2021-06-29 Htc Corporation Device and method of handling mobile data transmissions in a wireless communication system
CN108282273B (zh) * 2017-01-05 2024-03-08 华为技术有限公司 分段重传的方法和装置
WO2018203305A1 (en) * 2017-05-05 2018-11-08 Nokia Technologies Oy Radio link control status reporting
US10721650B2 (en) 2017-06-09 2020-07-21 Samsung Electronics Co., Ltd. Method and apparatus for accelerating data processing in wireless communication system
CN110099448B (zh) * 2018-01-31 2023-01-13 华为技术有限公司 通信的方法和装置
US11546798B2 (en) * 2018-05-17 2023-01-03 Ntt Docomo, Inc. Network node
CN115088300A (zh) * 2020-01-23 2022-09-20 哲库科技有限公司 用于在介质访问控制层对分组数据单元进行排队的技术
CN114846890A (zh) * 2020-03-18 2022-08-02 Oppo广东移动通信有限公司 一种数据包重组方法、电子设备及存储介质
CN113875284A (zh) * 2020-04-30 2021-12-31 华为技术有限公司 处理数据包的方法和通信装置
EP4185031A4 (en) * 2020-07-17 2023-08-02 Huawei Technologies Co., Ltd. DATA TRANSMISSION METHOD AND APPARATUS
CN114500671A (zh) * 2020-10-27 2022-05-13 中国移动通信有限公司研究院 数据处理方法及设备
US20220085916A1 (en) * 2020-12-26 2022-03-17 Intel Corporation Scalable protocol-agnostic reliable transport
US11758460B1 (en) * 2021-02-02 2023-09-12 T-Mobile Usa, Inc. Managing local application connectivity in a multi-network environment
CN113507346A (zh) * 2021-06-03 2021-10-15 北京中联国成科技有限公司 一种基于5g的远程通信方法及装置
WO2023193269A1 (zh) * 2022-04-08 2023-10-12 Oppo广东移动通信有限公司 数据处理方法、装置、通信设备及存储介质
WO2024029423A1 (ja) * 2022-08-03 2024-02-08 三菱電機株式会社 通信システム
WO2024065296A1 (zh) * 2022-09-28 2024-04-04 华为技术有限公司 数据传输方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101369879A (zh) * 2007-08-14 2009-02-18 华为技术有限公司 一种请求数据重传的方法及装置
CN101388900A (zh) * 2007-09-12 2009-03-18 大唐移动通信设备有限公司 一种协议数据单元填充的处理方法、装置及系统
US20160286402A1 (en) * 2015-03-23 2016-09-29 Realtek Semiconductor Corp. Control circuit of wireless user equipment

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080310452A1 (en) 2007-06-14 2008-12-18 Texas Instruments Incorporated Data link layer headers
US9554417B2 (en) 2008-12-24 2017-01-24 Qualcomm Incorporated Optimized header for efficient processing of data packets
CN101848489B (zh) * 2009-03-25 2014-02-05 中兴通讯股份有限公司 Pdu的发送/接收方法和装置
CN101932004B (zh) * 2009-06-25 2012-07-04 电信科学技术研究院 一种数据链路层的数据发送处理方法及设备
KR101707271B1 (ko) 2010-10-01 2017-02-15 인터디지탈 패튼 홀딩스, 인크 복수의 송신 포인트로부터의 수신을 가능케 하는 ｍａｃ 및 ｒｌｃ 아키텍쳐 및 프로시져
WO2014089833A1 (zh) 2012-12-14 2014-06-19 华为技术有限公司 子母基站簇、集中单元、拉远单元及信息处理方法
US10142847B2 (en) 2014-05-23 2018-11-27 Qualcomm Incorporated Secure relay of discovery information in wireless networks
WO2017049647A1 (zh) * 2015-09-25 2017-03-30 华为技术有限公司 一种数据发送方法、数据接收方法和相关设备
CN106465183B (zh) * 2016-09-20 2020-06-02 北京小米移动软件有限公司 数据传输方法、装置及系统
WO2018053852A1 (zh) * 2016-09-26 2018-03-29 北京小米移动软件有限公司 无线承载的配置方法、装置及系统
US20180097918A1 (en) * 2016-09-30 2018-04-05 Mediatek Inc. Segmentation and Concatenation for New Radio Systems
EP3301842A1 (en) * 2016-09-30 2018-04-04 Panasonic Intellectual Property Corporation of America Efficient user plane architecture for new rat
US20180124843A1 (en) * 2016-11-01 2018-05-03 Sharp Laboratories Of America, Inc. Configurable radio link controller frame structure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101369879A (zh) * 2007-08-14 2009-02-18 华为技术有限公司 一种请求数据重传的方法及装置
CN101388900A (zh) * 2007-09-12 2009-03-18 大唐移动通信设备有限公司 一种协议数据单元填充的处理方法、装置及系统
US20160286402A1 (en) * 2015-03-23 2016-09-29 Realtek Semiconductor Corp. Control circuit of wireless user equipment

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO; INC: "Discussion on L2 protocol for NR", 3GPP DRAFT; R2-166544_DISCUSSION ON L2 PROTOCOL FOR NR, 1 October 2016 (2016-10-01), XP051162173 *
See also references of EP3537827A4
ZTE; ZTE MICROELECTRONICS: "Consideration on the pre-concatenation in RLC for NR", 3GPP DRAFT; R2-166347 CONSIDERATION ON THE PRE-CONCATENATION IN RLC FOR NR, 30 September 2016 (2016-09-30), XP051161667 *

Also Published As

Publication number Publication date
JP2019533395A (ja) 2019-11-14
US20190306871A1 (en) 2019-10-03
EP3537827A1 (en) 2019-09-11
CN108024374A (zh) 2018-05-11
EP3537827A4 (en) 2019-10-09
KR20190075119A (ko) 2019-06-28
US10986653B2 (en) 2021-04-20

Similar Documents

Publication Publication Date Title
WO2018082433A1 (zh) 一种进行数据发送和接收的方法及系统
US11122152B2 (en) Data processing method and apparatus to reduce an overhead in a layer two protocol
WO2018127225A1 (zh) 数据传输方法、网络侧设备及用户设备
CN105684501B (zh) 在移动通信系统中使用多个载波传送/接收数据的方法和装置
TWI220832B (en) A scheme to prevent HFN un-synchronization for UM RLC in a high speed wireless communication system
CN107359968B (zh) 一种单层序列号的数据传输方法及装置
CN104935413B (zh) 分组数据汇聚协议pdcp实体及其执行的方法
US8817806B2 (en) Method and apparatus for flow control between RLC and PDCP in a communication
WO2018130034A1 (zh) 数据处理方法、装置和系统
TWI390912B (zh) 無線傳輸／接受器單元之有效記憶分配
CN103782569B (zh) 数据处理装置和方法
WO2017185941A1 (zh) 一种数据传输方法及相关设备
US20180368166A1 (en) User equipment and method to support data preprocessing
US20190200273A1 (en) Flushing PDCP Packets To Reduce Network Load In Multi-Connectivity Scenarios
KR102141389B1 (ko) 다중 무선 접속 기술 기반 통신 시스템에서의 무선 링크 제어 상태 보고 전송 방법 및 장치
WO2018201960A1 (zh) 一种进行反馈的方法和设备
CN109923845A (zh) 无线电接入中的无线电承载切换
WO2009117961A1 (zh) 一种发送数据的方法、系统和设备
WO2018127220A1 (zh) 一种数据转发方法及装置
CN103944880B (zh) 一种ZigBee数据传输的方法
WO2022073487A1 (zh) 数据传输方法、装置及存储介质
WO2022227998A1 (zh) 一种数据传输方法及装置
WO2019015487A1 (zh) 一种数据重传处理方法、rlc实体和mac实体
WO2012155419A1 (zh) 一种处理重传数据的方法及基站
WO2012155441A1 (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: 17867792

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019523796

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20197015912

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017867792

Country of ref document: EP

Effective date: 20190603