WO2017133595A1 - 数据处理的方法及装置 - Google Patents

数据处理的方法及装置 Download PDF

Info

Publication number
WO2017133595A1
WO2017133595A1 PCT/CN2017/072487 CN2017072487W WO2017133595A1 WO 2017133595 A1 WO2017133595 A1 WO 2017133595A1 CN 2017072487 W CN2017072487 W CN 2017072487W WO 2017133595 A1 WO2017133595 A1 WO 2017133595A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
entity
data
user plane
unit
Prior art date
Application number
PCT/CN2017/072487
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 中兴通讯股份有限公司
Publication of WO2017133595A1 publication Critical patent/WO2017133595A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for data processing.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • Enhancements in LPN deployment and capabilities have been identified by the Third Generation Partnership Project (3GPP) as one of the most interesting topics in future network development.
  • 3GPP Third Generation Partnership Project
  • UE User Equipment
  • Evolved-Universal Mobile telecommunications system Terrestrial Radio Access Network is currently deployed in the coverage of the macro base station or the boundary of the macro base station and the macro base station and the LPN.
  • the scenario of jointly providing data transmission services for the UE is more recognized and basically has a more common architecture mode.
  • FIG. 1 is a schematic diagram of a dual connectivity control plane in the related art, such as
  • a Mobility Management Entity (MME) in a core network Core Network, referred to as CN
  • CN Core Network
  • S1-MME interface is regarded by the CN as a mobile anchor point.
  • a master base station (Master eNB, abbreviated as MeNB); a node that provides additional radio resources for the UE, other than the MeNB, is called a secondary base station (Secondary eNB, SeNB for short).
  • the interface between the MeNB and the SeNB is temporarily referred to as an X2 interface, and can transmit control plane signaling and user plane data.
  • a wireless Uu interface is built between the MeNB and the SeNB and the UE. That is, the UE is in a dual connectivity state (Dual Connectivity, DC for short).
  • the specific user plane data transmission architecture can be as shown in Figure 2.
  • the data may be sent by the Serving GateWay (S-GW for short) to the MeNB through the S1-U interface, and then by the MeNB. It is sent to the UE through the wireless Uu port; it can also be sent to the MeNB through the S1-U interface by the S-GW.
  • the MeNB sends part of the data packet to the UE through the Uu interface, and the other part transmits to the SeNB through the X2 interface, and then passes the Uu through the SeNB.
  • the port is sent to the UE.
  • the data packet of the bearer of the Evolved Packet System (EPS) is transmitted by the radio resources of the two base stations, which greatly improves the throughput of the bearer and satisfies the data rate of the UE. demand.
  • EPS Evolved Packet System
  • the system architecture meets the UE data rate requirements, it does not provide a flexible link cooperation mechanism.
  • the data of the MeNB is offloaded in the Packet Data Convergence Protocol (PDCP) layer. Since the MeNB and the SeNB have independent Radio Link Controller (RLC) entities, once the data packet is sent by the PDCP entity to the RLC entity located in the MeNB or the SeNB, the subsequent data transmission must be completed in the MeNB or the SeNB. send. Since the current PDCP entity does not automatically request the retransmission function (the current PDCP entity architecture is as shown in FIG. 3), the cross-branch retransmission operation cannot be performed. Therefore, when there is a problem with one link, it is difficult to perform a packet retransmission operation from another link in time.
  • RLC Radio Link Controller
  • the present invention provides a data processing method and apparatus for solving at least the problem of data retransmission from other links when a link has a problem in the related art.
  • a data processing method comprising: determining a user plane entity for processing data, wherein the user plane entity has a function of retransmitting the data a retransmission function, a dynamic routing function for determining a transmission path of the data; processing the data with the determined user plane entity.
  • the user plane entity includes a sending end for transmitting data and/or a receiving end for receiving data, wherein the sending end has at least one of the following functions: for caching protocol data unit PDU and/or Or a transport buffer function of the service data unit SDU and processing the buffered PDU and/or SDU, the dynamic routing function, a header compression function for compressing a unit header of the PDU and/or the SDU, And an encryption function for encrypting the PDU and/or the SDU; the receiving end has at least one of the following functions: a receiving and buffering function for receiving and buffering the received protocol data unit PDU and/or the service data unit SDU, a reordering function for rearranging the received PDU and/or the SDU, a decompression function for decompressing the received PDU and/or a unit header of the SDU, for A decryption function that decrypts the received PDU and/or the SDU.
  • the sending end has at least one of the following functions: for caching protocol data
  • the dynamic routing function includes at least one of: routing a protocol data unit PDU to be sent by the user plane entity, and selecting a corresponding one according to the type of the PDU to be sent.
  • the function of the routing policy for directly transmitting the to-be-transmitted PDU to the lower layer entity or through the network element
  • the interface transmits the PDU to be sent to a function of a predetermined network element.
  • the type of the PDU to be sent includes at least one of the following: a first transmitted PDU, a retransmitted PDU, a PDU carrying control panel signaling, a PDU carrying user plane signaling, and the number of retransmissions reaches a predetermined threshold.
  • PDU wherein the predetermined threshold is stipulated by a first predetermined protocol or configured by first higher layer signaling.
  • selecting a corresponding routing policy according to the type of the PDU to be sent includes: selecting, according to the type of the PDU, a predetermined branch to send, if the PDU to be sent meets a predetermined condition,
  • the predetermined branch is configured by a second predetermined protocol or configured by the second higher layer signaling.
  • the predetermined branch comprises at least one of: a branch adopting a predetermined transmission technology, a transmission branch connected to a predetermined network element, and a logical channel and/or a transport channel configured with a predetermined quality of service QoS requirement.
  • the user plane entity is located in a core network, or an access network.
  • the user plane entity is an enhanced packet data convergence protocol PDCP entity or an enhanced radio link control RLC entity.
  • the lower layer entity of the user plane entity is an RLC entity or a medium access control MAC entity; and/or, when the user plane entity is When the enhanced RLC entity is described, the lower layer entity is a MAC entity; and the lower layer entity is configured to segment and/or cascade the received PDUs sent by the user plane entity.
  • the transmission buffer function includes at least one of: buffering header-compressed and/or encrypted PDUs; deleting or re-transmitting the cached PDU according to the feedback information; A timer deletes the cached PDU or replaces it with an empty packet.
  • the retransmitting the cached PDU according to the feedback information includes: retransmitting the complete cached PDU according to the feedback information; or receiving an acknowledgement indication according to the feedback information retransmission Part of the cached data in the PDU.
  • the method before the retransmitting part of the data in the cached PDU that does not receive the acknowledgement indication according to the feedback information, the method further includes: updating unit header information of the PDU to be retransmitted,
  • the updated unit header information includes at least one of the following: an original sequence number of the PDU, and location information of a part of the PDU to be retransmitted in the original PDU.
  • the method further includes: the first timer is started by: the user plane entity receiving the SDU, where the user plane entity maintains one of the first for each SDU received A timer, the SDU is a data unit received by the user plane entity from a higher layer.
  • the receiving buffer function includes the following functions: after detecting that the received PDU is lost, starting a second timer; when the second timer expires, and still not receiving the lost
  • the status report is sent to the sending end, where the status report is used to notify the sending end that the receiving end fails to receive the lost PDU; before the second timer expires, the status report is received.
  • the timing of the second timer is stopped.
  • the data unit buffered by the sending end is a data PDU, and/or, and the header compression work Corresponding control PDU.
  • an apparatus for data processing comprising: a determining module, configured to determine a user plane entity for processing data, wherein the user plane entity has the following module: a retransmission module And the dynamic routing module is configured to determine a transmission path of the data, and the processing module is configured to process the data by using the determined user plane entity.
  • the user plane entity includes a sending end for sending data and/or a receiving end for receiving data, wherein the sending end has at least one of the following modules: a transmission buffer module, configured to cache protocol data. a unit PDU and/or a service data unit SDU and processing the buffered PDU and/or SDU; the dynamic routing module; a header compression module, configured to compress a unit header of the PDU and/or SDU; and encrypt a module, configured to encrypt the PDU and/or the SDU; the receiving end is configured to: at least one of the following modules: a receiving buffer module, configured to receive and buffer the received protocol data unit PDU and/or the service data unit SDU; a rearrangement module, configured to perform reordering on the received PDU and/or the SDU; and a decompression compression module, configured to decompress the received unit header of the PDU and/or the SDU; And for decrypting the received PDU and/or the SDU.
  • a transmission buffer module configured to cache protocol
  • the dynamic routing module includes at least one of the following: a first selecting unit, configured to perform routing on a protocol data unit PDU to be sent by the user plane entity, and according to the type of the PDU to be sent. And selecting a corresponding routing policy; the transmitting unit is configured to directly transmit the to-be-transmitted PDU to the lower-layer entity, or deliver the to-be-transmitted PDU to the predetermined network element by using the inter-network element interface.
  • the type of the PDU to be sent includes at least one of the following: a first transmitted PDU, a retransmitted PDU, a PDU carrying control panel signaling, a PDU carrying user plane signaling, and the number of retransmissions reaches a predetermined threshold.
  • PDU wherein the predetermined threshold is stipulated by a first predetermined protocol or configured by first higher layer signaling.
  • the first selecting unit includes: a second selecting unit, configured to select, according to the type of the PDU, a predetermined branch to be sent if the PDU to be sent satisfies a predetermined condition, where The predetermined branch is stipulated by the second predetermined protocol or configured by the second higher layer signaling.
  • the predetermined branch comprises at least one of: a branch adopting a predetermined transmission technology, a transmission branch connected to a predetermined network element, and a logical channel and/or a transport channel configured with a predetermined quality of service QoS requirement.
  • the user plane entity is located in a core network, or an access network.
  • the user plane entity is an enhanced packet data convergence protocol PDCP entity or an enhanced radio link control RLC entity.
  • the lower layer entity of the user plane entity is an RLC entity or a medium access control MAC entity; and/or, when the user plane entity is When the enhanced RLC entity is described, the lower layer entity is a MAC entity; and the lower layer entity is configured to segment and/or cascade the received PDUs sent by the user plane entity.
  • the transmission buffer module includes at least one of the following units: a buffer unit, configured to cache the PDU after header compression and/or encryption processing, and a first processing unit, configured to cache the information according to the feedback information. PDU Performing deletion or retransmission; the second processing unit is configured to delete the cached PDU according to the first timer maintained locally or replace it with an empty packet.
  • the first processing unit includes: a first retransmission unit, configured to retransmit the complete buffered PDU according to the feedback information; or a second retransmission unit, configured to use, according to the feedback The information is retransmitted without partial data in the cached PDU that received the acknowledgment indication.
  • the transmission buffering module further includes: an updating unit, configured to: before the first retransmission unit retransmits part of the data in the cached PDU that does not receive the acknowledgement indication according to the feedback information, The unit header information of the PDU to be retransmitted, wherein the updated unit header information includes at least one of the following: an original sequence number of the PDU, and part of the data of the PDU to be retransmitted in an original location The location information in the PDU.
  • an updating unit configured to: before the first retransmission unit retransmits part of the data in the cached PDU that does not receive the acknowledgement indication according to the feedback information, The unit header information of the PDU to be retransmitted, wherein the updated unit header information includes at least one of the following: an original sequence number of the PDU, and part of the data of the PDU to be retransmitted in an original location The location information in the PDU.
  • the method further includes: the first timer is started by: the user plane entity receiving the SDU, where the user plane entity maintains one of the first for each SDU received A timer, the SDU is a data unit received by the user plane entity from a higher layer.
  • the receiving buffer module includes: a starting unit, configured to: after detecting that the received PDU is lost, start a second timer; and send, when the second timer expires After the PDU is still not received, the status report is sent to the sending end, where the status report is used to notify the sending end that the receiving end fails to receive the lost PDU; And a stopping unit, configured to stop timing of the second timer if the PDU of the lost packet is received before the second timer expires.
  • the data unit buffered by the sending end is a data PDU, and/or a control PDU corresponding to the header compression function.
  • a user plane entity for determining data processing wherein the user plane entity has at least one of the following functions: a retransmission function for retransmitting data, and a transmission path for determining data.
  • Dynamic routing function the method for processing data by using a certain user plane entity solves the problem that data cannot be retransmitted from other links when a link has a problem in the related art, thereby achieving cross-link branch weight Pass the effect.
  • FIG. 1 is a schematic diagram of a dual connection control plane in the related art
  • FIG. 2 is a schematic diagram of a dual-connection user plane data transmission architecture in the related art
  • FIG. 3 is a schematic diagram of a PDCP entity architecture in the related art
  • FIG. 4 is a flow chart of a method of data processing in accordance with an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of an apparatus for data processing according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram 1 of an enhanced PDCP entity architecture according to an embodiment of the present invention.
  • FIG. 7 is a second schematic diagram of an enhanced PDCP entity architecture according to an embodiment of the present invention.
  • FIG. 8 is a third schematic diagram of an enhanced PDCP entity architecture according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of an internal functional module of an enhanced PDCP entity according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an enhanced PDCP entity sending end architecture according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for data processing according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 determining a user plane entity for processing data, where the user plane entity has the following functions: a retransmission function for retransmitting data, and a dynamic routing function for determining a transmission path of data;
  • Step S404 processing the data by using the determined user plane entity.
  • a user plane entity for processing data is determined, wherein the user plane entity has a retransmission function and a dynamic routing function, and uses the determined user plane entity to process data, when a link has a problem.
  • the data transmission path can be updated to other links through the retransmission function and the dynamic routing function of the user plane entity, which solves the problem that the data cannot be retransmitted from other links when a link has a problem in the related art.
  • the effect of cross-link branch retransmission is achieved.
  • the user plane entity may include a sending end for transmitting data and/or a receiving end for receiving data, wherein the sending end has at least one of the following functions: for caching protocol data units ( Protocol Data Unit (referred to as PDU) and/or Service Data Unit (SDU) and the transmission buffer function for processing the buffered PDU and/or SDU, dynamic routing function, used for PDU and/or
  • PDU Protocol Data Unit
  • SDU Service Data Unit
  • the unit header of the SDU performs a compressed header compression function
  • an encryption function for encrypting the PDU and/or the SDU
  • the receiving end has at least one of the following functions: a receiving buffer for receiving and buffering the received PDU and/or the SDU.
  • the retransmission function may be included in the transport buffer function or as a separate function.
  • the functions of the above-mentioned sender and receiver can be configured or not configured according to service requirements, or can be configured by agreement.
  • the foregoing dynamic routing function may include at least one of the following: The PDU to be sent by the host entity is routed, and the function of the corresponding routing policy is selected according to the type of the PDU to be sent; the PDU to be sent is directly transmitted to the lower layer entity, or the interface between the network elements is to be used. The function of the transmitted PDU is passed to the predetermined network element.
  • the type of the PDU to be sent may include at least one of the following: a first transmitted PDU, a retransmitted PDU, a PDU carrying control panel signaling, a PDU carrying user plane signaling, and a retransmission.
  • the PDU whose number of times reaches a predetermined threshold, wherein the predetermined threshold is stipulated by the first predetermined protocol or configured by the first higher layer signaling.
  • the first predetermined protocol may be a 3GPP protocol
  • the first higher layer signaling may be a Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • selecting a corresponding routing policy may include: selecting, according to the type of the PDU, a predetermined branch to send if the PDU to be sent satisfies a predetermined condition, Wherein, the predetermined branch is agreed by the second predetermined protocol or configured by the second higher layer signaling.
  • the second predetermined protocol may be the same as or different from the first predetermined protocol.
  • the second higher layer signaling may be the same as or different from the first higher layer signaling.
  • the predetermined branch may include at least one of the following: a branch adopting a predetermined transmission technology, and a transmission branch connected to the predetermined network element, configured with a predetermined Quality of Service (QoS) requirement.
  • QoS Quality of Service
  • the user plane entity may be located in the core network, or the access network, and the user plane entity may be an enhanced PDCP entity, or an enhanced RLC entity, and when the user plane entity is an enhanced PDCP entity.
  • the lower layer entity of the user plane entity may be an RLC entity or a Media Access Control (MAC) entity; and/or, when the user plane entity is an enhanced RLC entity, the lower layer entity may be a MAC entity;
  • the lower layer entity is configured to split and/or cascade the PDUs sent in the received user plane entity.
  • a flat user plane design is introduced, and the existing PDCP, RLC, and MAC level 3 user plane architectures are simplified.
  • the user plane architecture of the access network is composed of enhanced PDCP and MAC. Or consisting of enhanced RLC and MAC, which reduces the functional overlap between user plane entities, reduces the complexity of the user plane, and improves the efficiency of the user plane.
  • the transmission buffer function may include at least one of: buffering the header compressed and/or encrypted PDU; deleting or retransmitting the buffered PDU according to the feedback information; The first timer deletes the cached PDU or replaces it with an empty packet.
  • the transport buffer function may be located under the header compression and/or encryption function. When the header compression and/or encryption function is configured, the buffer in the transmission buffer is processed by the header compression and/or encryption module. Protocol data unit.
  • retransmitting the buffered PDU according to the feedback information may include: retransmitting the complete cached PDU according to the feedback information; or retransmitting the cached PDU that does not receive the acknowledgement indication according to the feedback information. Part of the data.
  • the data processing method may further include: updating the unit header of the PDU to be retransmitted.
  • the updated unit header information includes at least one of the following: a sequence number of the original PDU, and location information of a part of the data of the PDU to be retransmitted in the original PDU.
  • the condition that the first timer is started may be: the user plane entity receives the SDU, where the user plane entity maintains a first timer for each received SDU, and the SDU is a user plane entity.
  • the data unit received from the upper layer and not processed by the user plane entity, wherein the relationship between the SDU and the PDU in the optional embodiment is: the SDU is a data unit that has not been processed by the user plane entity, and the PDU is a user plane entity to the SDU.
  • the data unit obtained by the processing includes data units that are submitted to the upper layer by all the processing of the user plane entity, and data units that have not been processed (ie, processed).
  • the receiving buffer function may include the following functions: after detecting that the received PDU is lost, starting the second timer; when the second timer expires, and still not receiving the lost PDU In the case, the status report is sent to the sending end, where the status report is used to notify the sending end that the receiving end fails to receive the lost PDU; if the PDU of the lost packet is received before the second timer expires, Stop the timing of the second timer.
  • the receiving end detects that the protocol data unit is lost (the protocol data unit serial number in the receiving buffer is discontinuous)
  • the timer is started, and when the timer expires, the timer is not received before the timer expires.
  • the enhanced user plane entity at the receiving end sends a status report to the transmitting end enhanced user plane entity. If the enhanced user plane receives all the lost data packets when the timer starts before the timer expires, the receiving entity stops the timer.
  • the SDU performs all processing for the user plane entity to submit the data unit of the upper layer
  • the PDU is the data unit processed by the user plane entity, or the data unit in the processing process of the user plane entity.
  • the data unit buffered by the transmitting end is a data PDU, and/or a control PDU corresponding to the header compression function.
  • the sender buffer function only caches data protocol data units (data PDUs), does not cache control protocol data units (control PDUs), or does not cache other control PDUs other than the header compression function related control PDUs.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a device for data processing is provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and the description thereof has been omitted.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram of an apparatus for data processing according to an embodiment of the present invention. As shown in FIG. The determination module 52 and the processing module 54 are described below, and the device will be described below.
  • a determining module 52 configured to determine a user plane entity for processing data, wherein the user plane entity has the following modules: a retransmission module for retransmitting data; and a dynamic routing module for determining data transmission The path; processing module 54, is coupled to the determining module 52 for processing the data with the determined user plane entity.
  • the user plane entity includes a transmitting end for transmitting data and/or a receiving end for receiving data
  • the sending end has at least one of the following modules: a transmission buffer module for a caching protocol a data unit PDU and/or a service data unit SDU and processing the buffered PDU and/or SDU; a dynamic routing module; a header compression module for compressing a unit header of the PDU and/or the SDU; and an encryption module for The PDU and/or the SDU are encrypted;
  • the receiving end has at least one of the following modules: a receiving buffer module for receiving and buffering the received PDU and/or the SDU; and a rearranging module for performing the received PDU and/or the SDU
  • the rearrangement module is configured to decompress the unit header of the received PDU and/or the SDU
  • the decryption module is configured to decrypt the received PDU and/or the SDU.
  • the dynamic routing module includes at least one of the following: a first selecting unit, configured to perform routing on the PDU to be sent by the user plane entity, and select corresponding according to the type of the PDU to be sent.
  • the routing unit is configured to directly transmit the PDU to be sent to the lower layer entity, or transmit the PDU to be sent to the predetermined network element through the interface between the network elements.
  • the type of the PDU to be sent includes at least one of the following: a first transmitted PDU, a retransmitted PDU, a PDU carrying control panel signaling, a PDU carrying user plane signaling, and a number of retransmissions.
  • the type of the PDU to be sent may be determined according to whether the PDU is first transmitted or retransmitted, whether the PDU carries control plane signaling or user plane data, whether the number of retransmissions of the protocol data reaches n times, and the like.
  • the first selecting unit includes: a second selecting unit, configured to select, according to the type of the PDU, a predetermined branch to transmit if the PDU to be sent satisfies a predetermined condition, where the predetermined The branch is configured by a second predetermined protocol or by a second higher layer signaling.
  • the predetermined branch comprises at least one of: a branch employing a predetermined transmission technique, a transmission branch connected to a predetermined network element, a logical channel and/or a transmission channel configured with a predetermined QoS requirement.
  • the user plane entity is located in the core network, or the access network.
  • the user plane entity is an enhanced packet data convergence protocol PDCP entity or an enhanced radio link control RLC entity.
  • the lower layer entity of the user plane entity is an RLC entity or a medium access control MAC entity; and/or, when the user plane entity is an enhanced RLC entity
  • the lower layer entity is a MAC entity; wherein the lower layer entity is configured to split and/or cascade the PDUs sent in the received user plane entity.
  • the transmission cache module includes at least one of the following units: a cache unit, The first processing unit is configured to delete or retransmit the buffered PDU according to the feedback information, and the second processing unit is configured to perform the first timer pair according to the local maintenance.
  • the cached PDU is deleted or replaced with an empty packet.
  • the first processing unit includes: a first retransmission unit, configured to retransmit the complete buffered PDU according to the feedback information; or a second retransmission unit, configured to retransmit according to the feedback information Some data in the cached PDU that did not receive the confirmation indication.
  • the transmission buffer module further includes: an updating unit, configured to update the to-be-retransmitted before the first retransmission unit retransmits part of the data in the buffered PDU that has not received the confirmation indication according to the feedback information.
  • the unit header information of the PDU wherein the updated unit header information includes at least one of the following: a sequence number of the original PDU, and location information of a part of the data of the PDU to be retransmitted in the original PDU.
  • the first timer is started by: the user plane entity receives the SDU, where the user plane entity maintains a first timer for each received SDU, and the SDU is the user plane entity.
  • the receiving buffer module includes: a starting unit, configured to: after detecting that the received PDU is lost, start a second timer; and send a unit, when the second After the timer expires, and the lost PDU is still not received, the status report is sent to the sending end, where the status report is used to notify the sending end that the receiving end receives the lost The PDU fails.
  • the stopping unit is configured to stop timing of the second timer if the PDU of the packet is received before the second timer expires.
  • the data unit buffered by the sender is a data PDU, and/or a control PDU corresponding to the header compression function.
  • Embodiments of the present invention provide a wireless network communication device (base station or user equipment), where the wireless network communication device includes an enhanced user plane entity.
  • the enhanced user plane entity is hereinafter referred to as an enhanced PDCP entity (which may also be referred to as an enhanced RLC entity), and the enhanced PDCP entity includes an acknowledge mode automatic request retransmission function.
  • FIG. 6 is a schematic diagram 1 of an enhanced PDCP entity architecture according to an embodiment of the present invention.
  • an enhanced PDCP entity is located on an access network side.
  • the data of the core network is sent to the enhanced PDCP entity, and then distributed to the LTE branch, the 5G (next generation communication technology) branch, and/or the WLAN branch by the dynamic routing function of the PDCP entity.
  • the automatic repeat-reQuest (ARQ) function is located in the PDCP entity, and the data packet during retransmission can be selected to be sent according to the actual situation.
  • the lower layer of the PDCP entity is connected to the RLC entity, and the RLC entity includes at least a splitting and/or cascading function.
  • the RLC entity is connected to the MAC entity, and the MAC entity is connected to the physical layer.
  • FIG. 7 is a second schematic diagram of an enhanced PDCP entity architecture according to an embodiment of the present invention, as shown in FIG.
  • the PDCP entity is located on the access network side, and is directly connected to the MAC layer below.
  • the MAC layer includes at least the ability to split and/or cascade PDCP PDUs.
  • the enhanced PDCP entity and the MAC entity may be located in the same or different network elements (for example, in different RATs). In this mode, enhanced PDCP can also be referred to as enhanced RLC.
  • header compression and encryption in the enhanced PDCP may be moved up to the core network (possibly only the header compression module may be considered, and the header compression and encryption modules may also be moved up simultaneously).
  • FIG. 8 is a third schematic diagram of an enhanced PDCP entity architecture according to an embodiment of the present invention. As shown in FIG. 8, an enhanced PDCP entity is located on a core network side. The dynamic routing module of the enhanced PDCP entity distributes the data sent downstream to different branches.
  • FIG. 6, FIG. 7, and FIG. 8 describe two access network bearers (Radio Access Bearers, RAB for short), wherein one access network bearer (for example, RAB1) is only limited to transmission in LTE, so no dynamic routing module is needed. .
  • the other RAB is allowed to transmit in LTE, 5G, and WLAN. Therefore, the PDCP entity corresponding to the RAB includes a dynamic routing module.
  • the security module may also be considered optional.
  • the associated ARQ module can also be set to optional if the associated RAB does not consider retransmission (ARQ) operations.
  • FIG. 9 is a schematic diagram of an internal function module of an enhanced PDCP entity according to an embodiment of the present invention.
  • FIG. 9 FIG. 9 (FIG. 6-8 focuses on an enhanced PDCP user plane entity in the entire user plane architecture. Location) Describes the internal structure of an enhanced PDCP entity in an embodiment of the present invention), further describing the user plane enhancement entity of the present invention (hereinafter referred to as an enhanced PDCP entity, which may be referred to as another name in actual operation, such as enhanced RLC) A functional architecture of an entity, etc., wherein the PDCP entity includes a transmitting portion and a receiving portion.
  • the sending part includes the following processing modules.
  • Head compression processing module (corresponding to the above header compression module)
  • Encryption processing module (corresponding to the above encryption module)
  • Routing module (corresponding to dynamic routing module)
  • the number processing module numbers adds an SN number for each PDCP Service Data Unit (PDCP SDU).
  • the numbered PDCP protocol data unit will enter the header compression processing module for header compression processing.
  • the header-compressed PDCP PDU will enter the encryption processing module for encryption processing.
  • the encrypted PDCP protocol data unit enters the PDCP header adding module to add PDCP header information.
  • the PDCP PDU added with the PDCP header information enters the transmission buffer module for caching.
  • the PDCP PDUs that have added the PDCP header information enter the routing module for routing and are sent to the selected lower layer module. (This step can be sent directly to the transmission buffer unit and the routing unit after the PDCP header is added; it can also be sent to the transmission buffer unit and then sent to the routing unit by the transmission buffer unit).
  • the transmission/transfer of data between modules can be based on the memory pointer (that is, the memory pointer is sent from one functional module to another, and the other functional module accesses the relevant data according to the received memory pointer), and does not necessarily have to be true.
  • Mobile data storage location that is, the memory pointer is sent from one functional module to another, and the other functional module accesses the relevant data according to the received memory pointer
  • the routing unit selects a relatively stable one.
  • the branch link sends the secondary data packet (LTE branch); if the current transmission is the first transmission, the branch with a large traffic but potentially dangerous packet loss can be selected for data transmission (WLAN branch or high-band carrier branch).
  • the branch link with a relatively stable routing sends a secondary data packet (LTE branch).
  • the module in the transmission buffer of the sender processes the PDCP PDU in the buffer according to the received feedback information.
  • the processing may be one of the following: when the transmission buffer module receives the transmission confirmation indication of the corresponding PDCP PDU, the PDCP entity deletes the PDCP PDU from the transmission buffer; when the transmission buffer module receives the non-acknowledgment indication of the corresponding PDCP PDU (NACK ), retransmit the PDCP PDU.
  • the module in the transmit buffer of the sender can also process the buffered PDCP PDU according to the timer maintained by itself.
  • the processing may be one of the following: when the corresponding PDCP PDU has not received the transmission confirmation indication when the transmission timer expires, the transmission buffer module deletes the PDCP PDU from the transmission buffer and sends a PDCP PDU discard indication to the lower layer.
  • the transmission buffer module replaces the secondary PDCP PDU with a null packet from the transmission buffer (the empty packet is PDCP data containing only the PDCP header but the data portion is empty) PDU), and send a PDCP PDU empty packet replacement indication to the lower layer.
  • the PDCP service data unit is a data unit that is received by the PDCP layer from the upper layer and has not been processed by the PDCP layer.
  • the PDCP protocol data unit is a data unit processed by the PDCP layer.
  • the data unit that enters the PDCP layer processing but has not completed the processing is also referred to as a protocol data unit.
  • the receiving part contains the following processing modules:
  • PDCP decryption module (equivalent to decryption module)
  • Receive buffer and sort module (equivalent to receive buffer module and rearrangement module)
  • the PDCP entity receiving part first performs a decryption operation after receiving the PDCP PDU.
  • the decrypted PDCP protocol data unit is placed in the receive buffer. If received in the cache All sequential PDCP PDUs are sent to the deheaded module in sequence.
  • the head module After the head module removes the PDCP PDU header, it submits it to the connector compression module for decompression.
  • the PDCP service data unit that completes the decompression is delivered to the upper layer.
  • the order of the header decoding module and the PDCP head module can be exchanged.
  • the receiving buffer module detects that the PDCP PDU data unit is lost (the PDCP data unit serial number in the receiving buffer is discontinuous), the timer is started, and when the timer expires, the lost data is not detected before the timer expires. Packet, the receiving end PDCP entity sends a status report to the transmitting PDCP entity. If the PDCP entity receives all lost packets at the start of the timer before the timer expires, the PDCP receiving entity stops the timer.
  • the PDCP service data unit performs all processing for the PDCP layer to deliver the data unit to the upper layer.
  • the PDCP protocol data unit is a data unit processed by the PDCP layer.
  • the data unit that enters the PDCP layer processing but has not completed the processing is also referred to as a protocol data unit.
  • FIG. 10 is a schematic diagram of an enhanced PDCP entity sending end architecture according to an embodiment of the present invention.
  • an enhanced PDCP entity includes a transmitting part and a receiving part.
  • the sending part includes the following processing modules:
  • the number processing module numbers adds an SN number for each PDCP Service Data Unit (PDCP SDU).
  • the numbered PDCP protocol data unit will enter the header compression processing module for header compression processing.
  • the header-compressed PDCP PDU will enter the encryption processing module for encryption processing.
  • the encrypted PDCP protocol data unit enters the PDCP header adding module to add PDCP header information.
  • the PDCP PDU added with the PDCP header information enters the transmission buffer module for caching.
  • the PDCP PDUs that have been added with the PDCP header information enter the routing module for routing and are sent to the selected lower-layer module. (This step can be sent directly to the transmission buffer unit and the routing unit after the PDCP header is added; it can also be sent to the transmission buffer unit and then sent to the routing unit by the transmission buffer unit).
  • the data transmission/transfer between modules can adopt the memory pointer based method (ie, the memory pointer) From one function module to another, another function module accesses the relevant data according to the received memory pointer), and does not necessarily have to move the data storage location.
  • the memory pointer based method ie, the memory pointer
  • the routing module may perform routing according to the characteristics of the data unit of the current transmission protocol: for example, if the PDCP protocol data unit of the current transmission is a PDCP PDU that is retransmitted for the first time or a PDCP PDU whose retransmission times exceeds n times. (n is a protocol agreement or can be configured by a higher layer), the routing unit selects a more stable branch link to send a secondary data packet (LTE branch); if the current transmission is the first transmission, the traffic may be selected to have a large traffic loss potential. Dangerous branches for data transmission (WLAN branch or high-band carrier branch). In addition, if the PDCP protocol data unit of the current transmission is a PDCP control PDU, the branch link with a relatively stable routing sends a secondary data packet (LTE branch).
  • the module in the transmission buffer of the sender processes the PDCP PDU in the buffer according to the received feedback information.
  • the processing may be one of the following: when the transmission buffer module receives the transmission confirmation indication of the corresponding PDCP PDU, the PDCP entity deletes the PDCP PDU from the transmission buffer.
  • the transmission buffer module receives a non-acknowledgment indication (NACK) of the corresponding PDCP PDU, the PDCP PDU is retransmitted.
  • NACK non-acknowledgment indication
  • the transmission buffer module receives a partial acknowledgment indication (or a partial non-acknowledgement indication NACK) of the corresponding PDCP PDU
  • the unacknowledged portion of the PDCP PDU is retransmitted.
  • you need to re-add the PDCP PDU header. This part of the operation can be done by a special re-segmentation module, or directly by the transmission buffer module.
  • the PDCP PDU that is once again divided needs to include at least the following information: the SN number of the PDCP PDU before the split, and the location information of the data part of the split PDCP PDU in the original PDCP PDU.
  • the foregoing location information may be jointly represented by the start bit information (representing the position of the first bit in the first PDU after the division in the original PDCP PDU) and the bit length; or by the start bit information (representing the first after the split) The position of the bit in the original PDCP PDU and the terminating bit information (representing the position of the last bit in the original PDU in the original PDCP PDU).
  • the module in the transmit buffer of the sender can also process the buffered PDCP PDU according to the timer maintained by itself.
  • the processing may be one of the following: when the corresponding PDCP PDU has not received the transmission confirmation indication when the transmission timer expires, the transmission buffer module deletes the PDCP PDU from the transmission buffer and sends a PDCP PDU discarding indication to the lower layer (this step) Optional).
  • the transmission buffer module When the corresponding PDCP PDU has not received the transmission confirmation indication when the transmission timer expires, the transmission buffer module replaces the secondary PDCP PDU with a null packet from the transmission buffer (the empty packet is PDCP data containing only the PDCP header but the data portion is empty) PDU), and optionally send a PDCP PDU empty packet replacement indication to the lower layer (this step is optional).
  • the deletion operation may be omitted or replaced with the empty packet operation. (You can also delete or replace it with an empty packet operation according to the above two processes.
  • the deletion operation may be omitted or replaced with the empty packet operation.
  • the PDCP service data unit is the PDCP layer received from the upper layer without PDCP.
  • the PDCP protocol data unit is a data unit processed by the PDCP layer. In order to simplify the description, the data unit that enters the PDCP layer processing but has not completed the processing is also referred to as a protocol data unit.
  • the receiving part contains the following processing modules:
  • the PDCP entity receiving part first performs a decryption operation after receiving the PDCP PDU.
  • the decrypted PDCP protocol data unit is placed in the receive buffer. If all the sequential PDCP PDUs are received in the buffer, the sequentially received PDCP PDUs are sent to the deheader module.
  • the head module After the head module removes the PDCP PDU header, it submits it to the connector compression module for decompression.
  • the PDCP service data unit that completes the decompression is delivered to the upper layer.
  • the order of the header decoding module and the PDCP head module can be exchanged.
  • the receiving buffer module detects that the PDCP PDU data unit is lost (the PDCP data unit serial number in the receiving buffer is discontinuous), the timer is started, and when the timer expires, the lost data is not detected before the timer expires. Packet, the receiving end PDCP entity sends a status report to the transmitting PDCP entity. If the PDCP entity receives all lost packets at the start of the timer before the timer expires, the PDCP receiving entity stops the timer.
  • the (receiver), the PDCP service data unit is the data unit that is delivered to the upper layer by the PDCP layer after all processing is completed.
  • the PDCP protocol data unit is a data unit processed by the PDCP layer. To simplify the description, data units that enter the PDCP layer processing but have not yet completed processing are also referred to as protocol data units in this patent.
  • the ARQ function is moved from the RLC entity to the PDCP entity to become an enhanced PDCP entity, which can solve the problem that it is difficult to implement cross-branch data retransmission under the current multi-link architecture.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • S1 Determine a user plane entity for processing data, where the user plane entity has the following functions: a retransmission function for retransmitting data, and a dynamic routing function for determining a transmission path of data;
  • the foregoing storage medium may include, but is not limited to, a U disk, a read only memory. (Read-Only Memory, referred to as ROM), Random Access Memory (RAM), mobile hard disk, disk or optical disk, and other media that can store program code.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • mobile hard disk disk or optical disk, and other media that can store program code.
  • the processor executes the above-mentioned S1-S2 according to the stored program code in the storage medium.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the present invention relates to the field of communications, and solves the problem that data cannot be retransmitted from other links when a link has a problem in the related art, thereby achieving the effect of retransmission across links.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

本发明提供了一种数据处理的方法及装置，其中，该方法包括：确定用于对数据进行处理的用户面实体，其中，该用户面实体具备以下功能：用于对数据进行重传的重传功能、用于确定数据的传输路径的动态路由功能；利用确定的用户面实体对数据进行处理。通过本发明，解决了相关技术中当一个链路出现问题时，不能从其他链路进行数据重传的问题，进而达到了跨链路分支重传的效果。 (图4)

Description

数据处理的方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种数据处理的方法及装置。
背景技术
随着无线通信技术和协议标准的不断演进，移动分组业务经历了巨大的发展，单个终端的数据吞吐能力不断提升。以长期演进(Long Term Evolution，简称为LTE)系统为例，在20M带宽内可以支持下行最大速率为100Mbps的数据传输；后续的增强LTE(LTE-Advanced，简称为LTE-A)系统中，数据的传输速率将进一步提升，甚至可以达到1Gbps。
终端数据业务量膨胀式的增长，使得移动网络的服务能力和部署策略都面临着巨大的压力与挑战。运营商一方面需要增强现有的网络部署和通讯技术，另一方面希望加快新技术的推广和网络拓展，从而达到快速提升网络性能的目的。而移动通信系统发展至今，仅通过对宏网络进行增强以提供经济、灵活、高能力的服务变得越来越困难，因此，部署低功率节点(Low Power Node，简称为LPN)以提供小小区(Small cell)覆盖的网络策略成为了极具吸引力的解决方案。
LPN部署及能力方面的增强已经被第三代伙伴组织计划(Third Generation Partnership Project，简称为3GPP)确认为未来网络发展中最令人感兴趣的课题之一。但是，在各类型基站独立为用户终端(User Equipment，简称为UE)提供服务的过程中，既存在诸多问题，又无法满足大数据量及高移动性的业务需求。因此，目前业界对在宏基站的覆盖范围内或边界部署LPN、由宏基站和LPN两者共同组成演进的通用移动通信系统陆地无线接入网(Evolved-Universal mobile telecommunications system Terrestrial Radio Access Network，简称为E-UTRAN)系统架构中的接入网，从而联合为UE提供数据传输服务的场景更为认同且基本有了较为普识的架构模式，图1为相关技术中双连接控制面示意图，如图1所示，与核心网(Core Network，简称为CN)中的移动性管理实体(Mobility Management Entity，简称为MME)设置有S1-MME接口、并被CN视作移动锚点的基站，称为主基站(Master eNB，简称为MeNB)；除MeNB外，为UE提供额外的无线资源的节点，称为次基站(Secondary eNB，简称为SeNB)。MeNB与SeNB间的接口暂称为X2接口，可传输控制面信令与用户面数据。MeNB与SeNB和UE间均建有无线Uu口，也就是说，UE处于双连接态(Dual Connectivity，简称为DC)。
在图1所示系统架构下，具体的用户面数据传输架构可如图2所示。数据可由服务网关(Serving GateWay，简称为S-GW)通过S1-U接口发送给MeNB、再由MeNB 通过无线Uu口发送给UE；也可由S-GW通过S1-U接口发送给MeNB，MeNB将部分数据包通过Uu口发送给UE，而另一部分则通过X2接口传输给SeNB、再由SeNB通过Uu口发送给UE。这样，同一演进分组承载(Evolved Packet System，简称为EPS)承载(bearer)的数据包借由两个基站的无线资源进行发送，极大地提高了所述承载的吞吐量，满足了UE的数据速率需求。
然而，在所述系统架构满足UE数据速率需求的同时，却不能提供灵活的链路协作机制。在当前协议中,当配置了Bearer分裂(split)时，MeNB的数据在分组数据汇聚协议(Packet Data Convergence Protocol，简称为PDCP)层进行分流。由于MeNB和SeNB拥有独立的无线链路控制(Radio Link Controller，简称为RLC)实体，数据包一旦由PDCP实体发送到了位于MeNB或SeNB的RLC实体，后续的数据传输就必须在MeNB或SeNB中完成发送。由于当前PDCP实体没有自动请求重传功能(当前PDCP实体架构如图3所示)，不能进行跨分支重传操作。因此，当一个链路出现问题时，难以及时从另一个链路进行数据包重传操作。
针对相关技术中当一个链路出现问题时，不能从其他链路进行数据重传的问题，目前尚未提出解决方案。
发明内容
本发明提供了一种数据处理的方法及装置，以至少解决相关技术中当一个链路出现问题时，不能从其他链路进行数据重传的问题。
根据本发明的一个方面，提供了一种数据处理的方法，包括：确定用于对数据进行处理的用户面实体，其中，所述用户面实体具备以下功能：用于对所述数据进行重传的重传功能、用于确定所述数据的传输路径的动态路由功能；利用确定的所述用户面实体对所述数据进行处理。
可选地，所述用户面实体包括用于发送数据的发送端和/或用于接收数据的接收端，其中，所述发送端具备以下功能至少之一：用于缓存协议数据单元PDU和/或业务数据单元SDU并对缓存的所述PDU和/或SDU进行处理的传输缓存功能、所述动态路由功能、用于对所述PDU和/或SDU的单元头进行压缩的头压缩功能、用于对所述PDU和/或SDU进行加密的加密功能；所述接收端具备以下功能至少之一：用于对接收的协议数据单元PDU和/或业务数据单元SDU进行接收缓存的接收缓存功能、用于对接收的所述PDU和/或所述SDU进行重排的重排功能、用于对接收的所述PDU和/或所述SDU的单元头进行解压缩的解头压缩功能、用于对接收的所述PDU和/或所述SDU进行解密的解密功能。
可选地，所述动态路由功能，包括以下至少之一：用于对所述用户面实体待发送的协议数据单元PDU进行路由选择，并根据所述待发送的PDU的类型，选择相对应的路由策略的功能；用于直接将所述待发送的PDU传输给下层实体、或通过网元间 接口将所述待发送的PDU传递给预定网元的功能。
可选地，所述待发送的PDU的类型包括以下至少之一：首次传输的PDU，重传的PDU，承载控制面板信令的PDU，承载用户面信令的PDU，重传次数达到预定阈值的PDU，其中，所述预定阈值由第一预定协议约定或由第一高层信令配置。
可选地，根据所述待发送的PDU的类型，选择相对应的路由策略包括：根据所述PDU的类型，在待发送的所述PDU满足预定条件的情况下，选择预定的分支进行发送，其中，所述预定的分支由第二预定协议约定或者由第二高层信令配置。
可选地，所述预定的分支包括以下至少之一：采用预定的传输技术的分支，连接到预定网元的传输分支，配置有预定服务质量QoS要求的逻辑信道和/或传输信道。
可选地，所述用户面实体位于核心网，或者接入网。
可选地，所述用户面实体为增强的分组数据汇聚协议PDCP实体，或者为增强的无线链路控制RLC实体。
可选地，当所述用户面实体为所述增强的PDCP实体时，所述用户面实体的下层实体为RLC实体或媒体接入控制MAC实体；和/或，当所述用户面实体为所述增强的RLC实体时，所述下层实体为MAC实体；其中，所述下层实体用于对接收到的所述用户面实体中发送的PDU进行分割和/或级联。
可选地，所述传输缓存功能，包括以下功能至少之一：缓存经头压缩和/或加密处理后的PDU；根据反馈信息对缓存的所述PDU进行删除或重传；根据本地维护的第一定时器对缓存的PDU进行删除或用空包替代。
可选地，所述根据反馈信息对缓存的所述PDU进行重传，包括：根据所述反馈信息重传完整的缓存的所述PDU；或者，根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据。
可选地，在所述根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据之前，所述方法还包括：更新待重传的所述PDU的单元头信息，其中，更新后的所述单元头信息包括以下至少之一：原始的所述PDU的序号，待重传的所述PDU的部分数据在原始的所述PDU中的位置信息。
可选地，还包括：所述第一定时器启动的条件为：所述用户面实体接收到所述SDU，其中，所述用户面实体为接收到的每一个所述SDU维护一个所述第一定时器，所述SDU为所述用户面实体从高层接收到的数据单元。
可选地，所述接收缓存功能，包括以下功能：检测到接收到的所述PDU丢失后，启动第二定时器；当所述第二定时器超时后，且仍没有收到丢失的所述PDU的情况下，向所述发送端发送状态报告，其中，所述状态报告用于告知所述发送端所述接收端接收丢失的所述PDU失败；在所述第二定时器超时前，收到丢包的所述PDU的情况下，停止所述第二定时器的计时。
可选地，所述发送端缓存的所述数据单元为数据PDU，和/或，与所述头压缩功 能对应的控制PDU。
根据本发明的另一方面，提供了一种数据处理的装置，包括：确定模块，用于确定用于对数据进行处理的用户面实体，其中，所述用户面实体具备以下模块：重传模块，用于对所述数据进行重传；动态路由模块，用于确定所述数据的传输路径；处理模块，用于利用确定的所述用户面实体对所述数据进行处理。
可选地，所述用户面实体包括用于发送数据的发送端和/或用于接收数据的接收端，其中，所述发送端具备以下模块至少之一：传输缓存模块，用于缓存协议数据单元PDU和/或业务数据单元SDU并对缓存的所述PDU和/或SDU进行处理；所述动态路由模块；头压缩模块，用于对所述PDU和/或SDU的单元头进行压缩；加密模块，用于对所述PDU和/或SDU进行加密；所述接收端具备以下模块至少之一：接收缓存模块，用于对接收的协议数据单元PDU和/或业务数据单元SDU进行接收缓存；重排模块，用于对接收的所述PDU和/或所述SDU进行重排；解头压缩模块，用于对接收的所述PDU和/或所述SDU的单元头进行解压缩；解密模块，用于对接收的所述PDU和/或所述SDU进行解密。
可选地，所述动态路由模块，包括以下至少之一：第一选择单元，用于对所述用户面实体待发送的协议数据单元PDU进行路由选择，并根据所述待发送的PDU的类型，选择相对应的路由策略；传输单元，用于直接将所述待发送的PDU传输给下层实体、或通过网元间接口将所述待发送的PDU传递给预定网元。
可选地，所述待发送的PDU的类型包括以下至少之一：首次传输的PDU，重传的PDU，承载控制面板信令的PDU，承载用户面信令的PDU，重传次数达到预定阈值的PDU，其中，所述预定阈值由第一预定协议约定或由第一高层信令配置。
可选地，所述第一选择单元包括：第二选择单元，用于根据所述PDU的类型，在待发送的所述PDU满足预定条件的情况下，选择预定的分支进行发送，其中，所述预定的分支由第二预定协议约定或者由第二高层信令配置。
可选地，所述预定的分支包括以下至少之一：采用预定的传输技术的分支，连接到预定网元的传输分支，配置有预定服务质量QoS要求的逻辑信道和/或传输信道。
可选地，所述用户面实体位于核心网，或者接入网。
可选地，所述用户面实体为增强的分组数据汇聚协议PDCP实体，或者为增强的无线链路控制RLC实体。
可选地，当所述用户面实体为所述增强的PDCP实体时，所述用户面实体的下层实体为RLC实体或媒体接入控制MAC实体；和/或，当所述用户面实体为所述增强的RLC实体时，所述下层实体为MAC实体；其中，所述下层实体用于对接收到的所述用户面实体中发送的PDU进行分割和/或级联。
可选地，所述传输缓存模块，包括以下单元至少之一：缓存单元，用于缓存经头压缩和/或加密处理后的PDU；第一处理单元，用于根据反馈信息对缓存的所述PDU 进行删除或重传；第二处理单元，用于根据本地维护的第一定时器对缓存的PDU进行删除或用空包替代。
可选地，所述第一处理单元，包括：第一重传单元，用于根据所述反馈信息重传完整的缓存的所述PDU；或者，第二重传单元，用于根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据。
可选地，所述传输缓存模块还包括：更新单元，用于在所述第一重传单元根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据之前，更新待重传的所述PDU的单元头信息，其中，更新后的所述单元头信息包括以下至少之一：原始的所述PDU的序号，待重传的所述PDU的部分数据在原始的所述PDU中的位置信息。
可选地，还包括：所述第一定时器启动的条件为：所述用户面实体接收到所述SDU，其中，所述用户面实体为接收到的每一个所述SDU维护一个所述第一定时器，所述SDU为所述用户面实体从高层接收到的数据单元。
可选地，所述接收缓存模块，包括以下单元：启动单元，用于在检测到接收到的所述PDU丢失后，启动第二定时器；发送单元，用于当所述第二定时器超时后，且仍没有收到丢失的所述PDU的情况下，向所述发送端发送状态报告，其中，所述状态报告用于告知所述发送端所述接收端接收丢失的所述PDU失败；停止单元，用于在所述第二定时器超时前，收到丢包的所述PDU的情况下，停止所述第二定时器的计时。
可选地，所述发送端缓存的所述数据单元为数据PDU，和/或，与所述头压缩功能对应的控制PDU。
通过本发明，采用确定用于对数据进行处理的用户面实体，其中，该用户面实体具备以下功能至少之一：用于对数据进行重传的重传功能、用于确定数据的传输路径的动态路由功能；利用确定的用户面实体对数据进行处理的方法，解决了相关技术中当一个链路出现问题时，不能从其他链路进行数据重传的问题，进而达到了跨链路分支重传的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为相关技术中双连接控制面示意图；
图2为相关技术中双连接用户面数据传输架构示意图；
图3为相关技术中PDCP实体架构图；
图4是根据本发明实施例的数据处理的方法的流程图；
图5是根据本发明实施例的数据处理的装置的结构框图；
图6是根据本发明实施例的增强的PDCP实体架构示意图一；
图7是根据本发明实施例的增强的PDCP实体架构示意图二；
图8是根据本发明实施例的增强的PDCP实体架构示意图三；
图9是根据本发明实施例的增强的PDCP实体内部功能模块示意图；
图10是根据本发明实施例的增强的PDCP实体发送端架构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种数据处理的方法，图4是根据本发明实施例的数据处理的方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，确定用于对数据进行处理的用户面实体，其中，该用户面实体具备以下功能：用于对数据进行重传的重传功能、用于确定数据的传输路径的动态路由功能；
步骤S404，利用确定的用户面实体对数据进行处理。
通过上述步骤，确定用于对数据进行处理的用户面实体，其中，该用户面实体具备重传功能和动态路由功能，利用确定的用户面实体对数据进行处理，当一个链路出现问题时，可以通过用户面实体的重传功能和动态路由功能，将数据的传输路径更新为其他链路，解决了相关技术中当一个链路出现问题时，不能从其他链路进行数据重传的问题，进而达到了跨链路分支重传的效果。
在一个可选的实施方式中，用户面实体可以包括用于发送数据的发送端和/或用于接收数据的接收端，其中，发送端具备以下功能至少之一：用于缓存协议数据单元(Protocol Data Unit，简称为PDU)和/或业务数据单元(Service Data Unit，简称为SDU)并对缓存的PDU和/或SDU进行处理的传输缓存功能、动态路由功能、用于对PDU和/或SDU的单元头进行压缩的头压缩功能、用于对PDU和/或SDU进行加密的加密功能；接收端具备以下功能至少之一：用于对接收的PDU和/或SDU进行接收缓存的接收缓存功能、用于对接收的PDU和/或SDU进行重排的重排功能、用于对接收的PDU和/或SDU的单元头进行解压缩的解头压缩功能、用于对接收的PDU和/或SDU进行解密的解密功能。在该可选实施例中，在用户面实体的发送端，重传功能可以包括在传输缓存功能中，也可以作为一个独立的功能而存在。上述发送端和接收端的各项功能，可根据业务需求选择配置或不配置，也可由协议约定强制配置。
在一个可选的实施例中，上述动态路由功能，可以包括以下至少之一：用于对用 户面实体待发送的PDU进行路由选择，并根据待发送的PDU的类型，选择相对应的路由策略的功能；用于直接将待发送的PDU传输给下层实体、或通过网元间接口将待发送的PDU传递给预定网元的功能。
在一个可选的实施例中，待发送的PDU的类型可以包括以下至少之一：首次传输的PDU，重传的PDU，承载控制面板信令的PDU，承载用户面信令的PDU，重传次数达到预定阈值的PDU，其中，该预定阈值由第一预定协议约定或由第一高层信令配置。例如，该第一预定协议可以为3GPP协议，该第一高层信令可以为无线资源控制(Radio Resource Control，简称为RRC)信令。
在一个可选的实施例中，根据待发送的PDU的类型，选择相对应的路由策略可以包括：根据PDU的类型，在待发送的PDU满足预定条件的情况下，选择预定的分支进行发送，其中，预定的分支由第二预定协议约定或者由第二高层信令配置。该第二预定协议可以与第一预定协议相同，也可以不同。同样，该第二高层信令可以和第一高层信令相同，也可以不同。
在一个可选的实施例中，预定的分支可以包括以下至少之一：采用预定的传输技术的分支，连接到预定网元的传输分支，配置有预定服务质量(Service Quality，简称为QoS)要求的逻辑信道和/或传输信道。
在上述各个实施例中，用户面实体可以位于核心网，或者接入网，该用户面实体可以为增强的PDCP实体，或者为增强的RLC实体，并且，当用户面实体为增强的PDCP实体时，用户面实体的下层实体可以为RLC实体或媒体接入控制(Media Access Control，简称为MAC)实体；和/或，当用户面实体为增强的RLC实体时，下层实体可以为MAC实体；其中，下层实体用于对接收到的用户面实体中发送的PDU进行分割和/或级联。同时，本实施例中引入了扁平化的用户面设计，将现有的PDCP、RLC、MAC 3级用户面架构进行了精简，重构后接入网的用户面架构由增强的PDCP和MAC组成，或者由增强的RLC和MAC组成，减少了用户面实体间的功能重叠，减少了用户面的复杂度，提高了用户面的效率。
在一个可选的实施例中，传输缓存功能，可以包括以下功能至少之一：缓存经头压缩和/或加密处理后的PDU；根据反馈信息对缓存的PDU进行删除或重传；根据本地维护的第一定时器对缓存的PDU进行删除或用空包替代。该可选实施例中，传输缓存功能可以位于头压缩和/或加密功能之下，在配置了头压缩和/或加密功能时，传输缓存中缓存的是经过头压缩和/或加密模块处理后的协议数据单元。
在一个可选的实施例中，根据反馈信息对缓存的PDU进行重传，可以包括：根据反馈信息重传完整的缓存的PDU；或者，根据反馈信息重传没有收到确认指示的缓存的PDU中的部分数据。
在一个可选的实施例中，在根据反馈信息重传没有收到确认指示的缓存的PDU中的部分数据之前，该数据处理的方法还可以包括：更新待重传的PDU的单元头信 息，其中，更新后的单元头信息包括以下至少之一：原始的PDU的序号，待重传的PDU的部分数据在原始的PDU中的位置信息。
在一个可选的实施例中，第一定时器启动的条件可以为：用户面实体接收到SDU，其中，用户面实体为接收到的每一个SDU维护一个第一定时器，SDU为用户面实体从高层接收到的、未经过用户面实体处理的数据单元，其中，该可选实施例中SDU与PDU的关系为：SDU为未经过用户面实体处理的数据单元，PDU为用户面实体对SDU进行处理得到的数据单元，包括用户面实体完成所有处理后递交给高层的数据单元，也包括没有完成处理(即处理过程中)的数据单元。
在一个可选的实施例中，接收缓存功能，可以包括以下功能：检测到接收到的PDU丢失后，启动第二定时器；当第二定时器超时后，且仍没有收到丢失的PDU的情况下，向发送端发送状态报告，其中，该状态报告用于告知发送端所述接收端接收丢失的所述PDU失败；在第二定时器超时前，收到丢包的PDU的情况下，停止第二定时器的计时。在该可选实施例中，接收端当察觉到协议数据单元丢失时(接收缓存中的协议数据单元序号不连续)，则启动定时器，当定时器超时后仍没有收到定时器超时前察觉到丢失的数据包，则接收端所述增强用户面实体向发送端增强用户面实体发送状态报告。如果定时器超时前增强用户面收到了定时器启动时所有丢失的数据包，则接收端实体停止所述定时器。该可选实施例中，SDU为用户面实体完成所有处理递交高层的数据单元，PDU为经过用户面实体处理后的数据单元，或者用户面实体处理过程中的数据单元。
在上述各个实施例中，发送端缓存的数据单元为数据PDU，和/或，与头压缩功能对应的控制PDU。例如，发送端缓存功能仅缓存数据协议数据单元(数据PDU)，不缓存控制协议数据单元(控制PDU)，或者不缓存除头压缩功能相关控制PDU外的其他控制PDU。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种数据处理的装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图5是根据本发明实施例的数据处理的装置的结构框图，如图5所示，该装置包 括确定模块52和处理模块54，下面对该装置进行说明。
确定模块52，用于确定用于对数据进行处理的用户面实体，其中，该用户面实体具备以下模块：重传模块，用于对数据进行重传；动态路由模块，用于确定数据的传输路径；处理模块54，连接至确定模块52，用于利用确定的用户面实体对数据进行处理。
在一个可选的实施例中，用户面实体包括用于发送数据的发送端和/或用于接收数据的接收端，其中，发送端具备以下模块至少之一：传输缓存模块，用于缓存协议数据单元PDU和/或业务数据单元SDU并对缓存的PDU和/或SDU进行处理；动态路由模块；头压缩模块，用于对PDU和/或SDU的单元头进行压缩；加密模块，用于对PDU和/或SDU进行加密；接收端具备以下模块至少之一：接收缓存模块，用于对接收的PDU和/或SDU进行接收缓存；重排模块，用于对接收的PDU和/或SDU进行重排；解头压缩模块，用于对接收的PDU和/或SDU的单元头进行解压缩；解密模块，用于对接收的PDU和/或SDU进行解密。
在一个可选的实施例中，动态路由模块，包括以下至少之一：第一选择单元，用于对用户面实体待发送的PDU进行路由选择，并根据待发送的PDU的类型，选择相对应的路由策略；传输单元，用于直接将待发送的PDU传输给下层实体、或通过网元间接口将待发送的PDU传递给预定网元。
在一个可选的实施例中，待发送的PDU的类型包括以下至少之一：首次传输的PDU，重传的PDU，承载控制面板信令的PDU，承载用户面信令的PDU，重传次数达到预定阈值的PDU，其中，预定阈值由第一预定协议约定或由第一高层信令配置。
例如，可以根据该PDU是首次传输还是重传、该PDU承载的是控制面信令还是用户面数据、该协议数据的重传次数是否达到n次等，来确定待发送的PDU的类型。
在一个可选的实施例中，第一选择单元包括：第二选择单元，用于根据PDU的类型，在待发送的PDU满足预定条件的情况下，选择预定的分支进行发送，其中，预定的分支由第二预定协议约定或者由第二高层信令配置。
在一个可选的实施例中，预定的分支包括以下至少之一：采用预定的传输技术的分支，连接到预定网元的传输分支，配置有预定QoS要求的逻辑信道和/或传输信道。
在一个可选的实施例中，用户面实体位于核心网，或者接入网。
在一个可选的实施例中，用户面实体为增强的分组数据汇聚协议PDCP实体，或者为增强的无线链路控制RLC实体。
在一个可选的实施例中，当用户面实体为增强的PDCP实体时，用户面实体的下层实体为RLC实体或媒体接入控制MAC实体；和/或，当用户面实体为增强的RLC实体时，下层实体为MAC实体；其中，下层实体用于对接收到的用户面实体中发送的PDU进行分割和/或级联。
在一个可选的实施例中，传输缓存模块，包括以下单元至少之一：缓存单元，用 于缓存经头压缩和/或加密处理后的PDU；第一处理单元，用于根据反馈信息对缓存的PDU进行删除或重传；第二处理单元，用于根据本地维护的第一定时器对缓存的PDU进行删除或用空包替代。
在一个可选的实施例中，第一处理单元，包括：第一重传单元，用于根据反馈信息重传完整的缓存的PDU；或者，第二重传单元，用于根据反馈信息重传没有收到确认指示的缓存的PDU中的部分数据。
在一个可选的实施例中，传输缓存模块还包括：更新单元，用于在第一重传单元根据反馈信息重传没有收到确认指示的缓存的PDU中的部分数据之前，更新待重传的PDU的单元头信息，其中，更新后的单元头信息包括以下至少之一：原始的PDU的序号，待重传的PDU的部分数据在原始的PDU中的位置信息。
在一个可选的实施例中，第一定时器启动的条件为：用户面实体接收到SDU，其中，用户面实体为接收到的每一个SDU维护一个第一定时器，SDU为用户面实体从高层接收到的、未经过用户面实体处理的数据单元，其中，PDU为用户面实体对SDU进行处理得到的数据单元。
在一个可选的实施例中，接收缓存模块，包括以下单元：启动单元，用于在检测到接收到的所述PDU丢失后，启动第二定时器；发送单元，用于当所述第二定时器超时后，且仍没有收到丢失的所述PDU的情况下，向所述发送端发送状态报告，其中，所述状态报告用于告知所述发送端所述接收端接收丢失的所述PDU失败；停止单元，用于在所述第二定时器超时前，收到丢包的所述PDU的情况下，停止所述第二定时器的计时。
在一个可选的实施例中，所述发送端缓存的所述数据单元为数据PDU，和/或，与所述头压缩功能对应的控制PDU。
下面结合具体实施环境，对本发明数据处理的方进行说明。
本发明实施例提供了一种无线网络通信装置(基站或用户设备)，该无线网络通信装置包括增强的用户面实体。为了描述方便，后续将该增强的用户面实体称为增强的PDCP实体(也可称为增强的RLC实体)，该增强的PDCP实体中包含确认模式自动请求重传功能。
图6是根据本发明实施例的增强的PDCP实体架构示意图一，如图6所示，增强的PDCP实体位于接入网侧。核心网的数据发送到增强的PDCP实体，再通过PDCP实体的动态路由功能分发到LTE分支、5G(下一代通信技术)分支，和/或WLAN分支中进行发送。其中，自动请求重传(Automatic Repeat-reQuest，简称为ARQ)功能位于PDCP实体内，重传时的数据包可以根据实际情况选择与首次传输不同的分支进行发送。PDCP实体下层与RLC实体相连，RLC实体中至少包括分割和/或级联功能。RLC实体下与MAC实体相连，而MAC实体则与物理层相衔接。
图7是根据本发明实施例的增强的PDCP实体架构示意图二，如图7所示，增强 的PDCP实体位于接入网侧，下面直接与MAC层相连。而MAC层则至少包括了分割和/或级联PDCP PDU的能力。其中，增强的PDCP实体与MAC实体可以位于相同或不同的网元中(例如，位于不同的RAT中)。此种模式下，增强的PDCP也可称为增强的RLC。
图6、图7中架构下，增强的PDCP中的头压缩、加密等功能可能上移到核心网中(可能只上移头压缩模块，也可考虑头压缩与加密模块同时上移)。
图8是根据本发明实施例的增强的PDCP实体架构示意图三，如图8所示，增强的PDCP实体位于核心网侧。增强的PDCP实体的动态路由模块将下行发送的数据分发到不同的分支上。
图6、图7、图8中描述了两个接入网承载(Radio Access Bearer，简称为RAB)，其中一个接入网承载(例如，RAB1)仅限定在LTE中传输，因此无需动态路由模块。而另一个RAB则允许在LTE、5G、WLAN中传输，因此此RAB对应的PDCP实体中包含了动态路由模块。
另外，如果相关RAB不要求加密，则安全模块也可考虑设置为可选。如果相关RAB不考虑重传(ARQ)操作，则相关ARQ模块也可设置为可选。
图9是根据本发明实施例的增强的PDCP实体内部功能模块示意图，如图9所示，在图9中(图6-8重点描述的是增强的PDCP用户面实体在整个用户面架构中的位置)描述本发明实施例中增强的PDCP实体的内部结构)，进一步描述了本发明的用户面增强实体(后续称为增强PDCP实体，在实际操作中可能被称为其他名字，例如增强的RLC实体等)的功能架构，其中该PDCP实体包含发送部分和接收部分。其中，发送部分包含以下处理模块。
编号处理模块
头压缩处理模块(对应于上述头压缩模块)
加密处理模块(对应于上述加密模块)
PDCP头添加处理模块
传输缓存模块
路由选择模块(对应于动态路由模块)
其中，编号处理模块为每一个PDCP服务数据单元(PDCP SDU)进行编号(添加SN号)。
如果配置了头压缩功能，则编号后的PDCP协议数据单元将进入头压缩处理模块进行头压缩处理。
如果配置了加密处理模块，则头压缩后的PDCP PDU将进入加密处理模块进行加密处理。
加密后的PDCP协议数据单元进入PDCP头添加模块添加PDCP头信息。
添加完PDCP头信息的PDCP PDU进入传输缓存模块进行缓存。
如果PDCP实体下配置了多条可选的传输路径(例如，配置了双连结)，添加完PDCP头信息的PDCP PDU进入路由选择模块进行路由选择，并发送到选择后的下层模块。(此步骤可由添加完PDCP头后直接发往传输缓存单元和路由选择单元；也可先发送到传输缓存单元，再由传输缓存单元发送到路由选择单元)。
其中，数据在模块间的发送/转移可以采用基于内存指针的方式(即将内存指针由一个功能模块发往另一个，另一个功能模块根据接收到的内存指针访问相关数据)，并不一定要真实移动数据存放位置。
其中，路由选择模块可以根据本次传输协议数据单元的特征进行路由选择：
例如，如果本次传输的PDCP协议数据单元是第一次重传的PDCP PDU或者是重传次数超过n次的PDCP PDU(n为协议约定或可由高层配置)，则路由选择单元选择较为稳定的分支链路发送次数据包(LTE分支)；如果本次传输是首次传输，则可以选择流量较大但有丢包潜在危险的分支进行数据发送(WLAN分支或高频段载波分支)。另外，如果本次传输的PDCP协议数据单元是PDCP控制PDU，则路由选择较为稳定的分支链路发送次数据包(LTE分支)。
发送端传输缓存中模块根据收到的反馈信息对缓存中的PDCP PDU进行处理。处理可以是以下之一：当传输缓存模块收到了相应PDCP PDU的传输确认指示时，PDCP实体从传输缓存中删除掉此PDCP PDU；当传输缓存模块收到了相应PDCP PDU的非确认指示时(NACK)，对此PDCP PDU进行重传操作。
发送端传输缓存中模块也可根据自身维护的定时器对缓存的PDCP PDU进行处理。处理可以是以下之一：当相应PDCP PDU在传输定时器超时时还没有收到传输确认指示，则传输缓存模块从传输缓存中删除掉此PDCP PDU，并向低层发送PDCP PDU丢弃指示。当相应PDCP PDU在传输定时器超时时还没有收到传输确认指示，则传输缓存模块从传输缓存中将次PDCP PDU替换为空包(空包为仅包含PDCP头但数据部分为空的PDCP数据PDU)，并向低层发送PDCP PDU空包替换指示。
其中(发送端)，PDCP业务数据单元为PDCP层从高层接收到的未经过PDCP层处理的数据单元。而PDCP协议数据单元为经过PDCP层处理后的数据单元。为了简化描述，进入PDCP层处理，但还没有完成处理的处理过程中的数据单元也称为协议数据单元。
对于PDCP实体，接收部分包含如下处理模块：
PDCP解密模块(相当于解密模块)
接收缓存及排序模块(相当于接收缓存模块和重排模块)
PDCP去头模块
解头压缩模块
其中，PDCP实体接收部分接收到PDCP PDU后先进行解密操作。
完成解密后将解密后的PDCP协议数据单元放入接收缓存中。若缓存中接收到了 所有顺序的PDCP PDU，则将顺序接收的PDCP PDU发送到去头模块。
去头模块去掉PDCP PDU头后，递交到接头压缩模块进行解头压缩操作。
将完成解头压缩的PDCP业务数据单元递交给高层。
其中解头压缩模块和PDCP去头模块的顺序可以交换。
其中，接收缓存模块当察觉到PDCP PDU数据单元丢失时(接收缓存中的PDCP数据单元序号不连续)，则启动定时器，当定时器超时后仍没有收到定时器超时前察觉到丢失的数据包，则接收端PDCP实体向发送端PDCP实体发送状态报告。如果定时器超时前PDCP实体收到了定时器启动时所有丢失的数据包，则PDCP接收端实体停止所述定时器。
其中(接收端)，PDCP业务数据单元为PDCP层完成所有处理递交给高层的数据单元。而PDCP协议数据单元为经过PDCP层处理后的数据单元。为了简化描述，进入PDCP层处理，但还没有完成处理的处理过程中的数据单元也称为协议数据单元。
图10是根据本发明实施例的增强的PDCP实体发送端架构示意图，如图10所示，本发明实施例中，增强的PDCP实体包含发送部分和接收部分。其中，发送部分包含以下处理模块：
编号处理模块
头压缩处理模块
加密处理模块
PDCP头添加处理模块
传输缓存模块
路由选择模块
其中，编号处理模块为每一个PDCP服务数据单元(PDCP SDU)进行编号(添加SN号)。
如果配置了头压缩功能，则编号后的PDCP协议数据单元将进入头压缩处理模块进行头压缩处理。
如果配置了加密处理模块，则头压缩后的PDCP PDU将进入加密处理模块进行加密处理。
加密后的PDCP协议数据单元进入PDCP头添加模块添加PDCP头信息。
添加完PDCP头信息的PDCP PDU进入传输缓存模块进行缓存。
如果PDCP实体下配置了多条可选的传输路径(例如，配置了双联结)，添加完PDCP头信息的PDCP PDU进入路由选择模块进行路由选择，并发送到选择后的下层模块。(此步骤可由添加完PDCP头后直接发往传输缓存单元和路由选择单元；也可先发送到传输缓存单元，再由传输缓存单元发送到路由选择单元)。
其中，数据在模块间的发送/转移可以采用基于内存指针的方式(即将内存指针 由一个功能模块发往另一个，另一个功能模块根据接收到的内存指针访问相关数据)，并不一定要真实移动数据存放位置。
其中，路由选择模块可以根据本次传输协议数据单元的特征进行路由选择：例如，如果本次传输的PDCP协议数据单元是第一次重传的PDCP PDU或者是重传次数超过n次的PDCP PDU(n为协议约定或可由高层配置)，则路由选择单元选择较为稳定的分支链路发送次数据包(LTE分支)；如果本次传输是首次传输，则可以选择流量较大但有丢包潜在危险的分支进行数据发送(WLAN分支或高频段载波分支)。另外，如果本次传输的PDCP协议数据单元是PDCP控制PDU，则路由选择较为稳定的分支链路发送次数据包(LTE分支)。
发送端传输缓存中模块根据收到的反馈信息对缓存中的PDCP PDU进行处理。处理可以是以下之一：当传输缓存模块收到了相应PDCP PDU的传输确认指示时，PDCP实体从传输缓存中删除掉此PDCP PDU。当传输缓存模块收到了相应PDCP PDU的非确认指示时(NACK)，对此PDCP PDU进行重传操作。当传输缓存模块收到了相应PDCP PDU的部分确认指示(或部分非确认指示NACK)，则对此PDCP PDU中非确认的部分进行重传操作。此时，需要重新进行PDCP PDU头的添加操作。此部分操作可以由专门的再次分割模块完成，也可由传输缓存模块直接完成。
对此再次分段的情况，再次分割后的PDCP PDU中至少需要包含以下信息：分割前的PDCP PDU的SN号，分割后的PDCP PDU中的数据部分在原始PDCP PDU中的位置信息。
上述位置信息可以由起始bit信息(表示分割后的第一个PDU中第一个bit在原始PDCP PDU中的位置)和bit长度共同表示；或者由起始bit信息(表示分割后的第一个bit在原始PDCP PDU中的位置)和终止bit信息(表示分割后的PDU中最后一个bit在原始PDCP PDU中的位置)共同表示。
发送端传输缓存中模块也可根据自身维护的定时器对缓存的PDCP PDU进行处理。处理可以是以下之一：当相应PDCP PDU在传输定时器超时时还没有收到传输确认指示，则传输缓存模块从传输缓存中删除掉此PDCP PDU，并向低层发送PDCP PDU丢弃指示(此步骤可选)。当相应PDCP PDU在传输定时器超时时还没有收到传输确认指示，则传输缓存模块从传输缓存中将次PDCP PDU替换为空包(空包为仅包含PDCP头但数据部分为空的PDCP数据PDU)，并可选地向低层发送PDCP PDU空包替换指示(此步骤可选)。
其中，在上述过程中，当相应PDCP PDU在传输定时器超时时还没有收到全部传输确认指示时(已经有部分成功传输的PDCP PDU)，可以不进行删除操作或替换为空包操作。(也可按照上述两种处理进行删除或替换为空包操作，这里只是提供了另外一种可选技术手段)
其中(发送端)，PDCP业务数据单元为PDCP层从高层接收到的未经过PDCP 层处理的数据单元。而PDCP协议数据单元为经过PDCP层处理后的数据单元。为了简化描述，进入PDCP层处理，但还没有完成处理的处理过程中的数据单元也称为协议数据单元。
对于PDCP实体，接收部分包含如下处理模块：
PDCP解密模块
接收缓存及排序模块
PDCP去头模块
解头压缩模块
其中，PDCP实体接收部分接收到PDCP PDU后先进行解密操作。
完成解密后将解密后的PDCP协议数据单元放入接收缓存中。若缓存中接收到了所有顺序的PDCP PDU，则将顺序接收的PDCP PDU发送到去头模块。
去头模块去掉PDCP PDU头后，递交到接头压缩模块进行解头压缩操作。
将完成解头压缩的PDCP业务数据单元递交给高层。
其中解头压缩模块和PDCP去头模块的顺序可以交换。
其中，接收缓存模块当察觉到PDCP PDU数据单元丢失时(接收缓存中的PDCP数据单元序号不连续)，则启动定时器，当定时器超时后仍没有收到定时器超时前察觉到丢失的数据包，则接收端PDCP实体向发送端PDCP实体发送状态报告。如果定时器超时前PDCP实体收到了定时器启动时所有丢失的数据包，则PDCP接收端实体停止所述定时器。
其中，当收到的数据包中有空包时，只要序号连续，仍然认为是连续的。
其中(接收端)，PDCP业务数据单元为PDCP层完成所有处理后递交给高层的数据单元。而PDCP协议数据单元为经过PDCP层处理后的数据单元。为了简化描述，进入PDCP层处理，但还没有完成处理的处理过程中的数据单元在本专利中也称为协议数据单元。
本发明实施例中，将ARQ功能由RLC实体上移到PDCP实体，成为增强的PDCP实体，可以解决目前多链接架构下难以实现跨分支数据重传的问题。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，确定用于对数据进行处理的用户面实体，其中，该用户面实体具备以下功能：用于对数据进行重传的重传功能、用于确定数据的传输路径的动态路由功能；
S2，利用确定的用户面实体对数据进行处理。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器 (Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述S1-S2。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
工业实用性
本发明涉及通信领域，解决了相关技术中当一个链路出现问题时，不能从其他链路进行数据重传的问题，进而达到了跨链路分支重传的效果。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (30)

  1. 一种数据处理的方法，包括：
    确定用于对数据进行处理的用户面实体，其中，所述用户面实体具备以下功能：用于对所述数据进行重传的重传功能、用于确定所述数据的传输路径的动态路由功能；
    利用确定的所述用户面实体对所述数据进行处理。
  2. 根据权利要求1所述的方法，其中，所述用户面实体包括用于发送数据的发送端和/或用于接收数据的接收端，其中，
    所述发送端具备以下功能至少之一：用于缓存协议数据单元PDU和/或业务数据单元SDU并对缓存的所述PDU和/或SDU进行处理的传输缓存功能、所述动态路由功能、用于对所述PDU和/或SDU的单元头进行压缩的头压缩功能、用于对所述PDU和/或SDU进行加密的加密功能；
    所述接收端具备以下功能至少之一：用于对接收的协议数据单元PDU和/或业务数据单元SDU进行接收缓存的接收缓存功能、用于对接收的所述PDU和/或所述SDU进行重排的重排功能、用于对接收的所述PDU和/或所述SDU的单元头进行解压缩的解头压缩功能、用于对接收的所述PDU和/或所述SDU进行解密的解密功能。
  3. 根据权利要求1或2所述的方法，其中，所述动态路由功能包括以下至少之一：
    用于对所述用户面实体待发送的协议数据单元PDU进行路由选择，并根据所述待发送的PDU的类型，选择相对应的路由策略的功能；
    用于直接将所述待发送的PDU传输给下层实体、或通过网元间接口将所述待发送的PDU传递给预定网元的功能。
  4. 根据权利要求3所述的方法，其中，所述待发送的PDU的类型包括以下至少之一：
    首次传输的PDU，重传的PDU，承载控制面板信令的PDU，承载用户面信令的PDU，重传次数达到预定阈值的PDU，其中，所述预定阈值由第一预定协议约定或由第一高层信令配置。
  5. 根据权利要求3所述的方法，其中，根据所述待发送的PDU的类型，选择相对应的路由策略包括：
    根据所述PDU的类型，在待发送的所述PDU满足预定条件的情况下，选择预定的分支进行发送，其中，所述预定的分支由第二预定协议约定或者由第二高层信令配置。
  6. 根据权利要求5所述的方法，其中，所述预定的分支包括以下至少之一：
    采用预定的传输技术的分支，连接到预定网元的传输分支，配置有预定服务质量QoS要求的逻辑信道和/或传输信道。
  7. 根据权利要求1所述的方法，其中，所述用户面实体位于核心网，或者接入网。
  8. 根据权利要求1所述的方法，其中，所述用户面实体为增强的分组数据汇聚协议PDCP实体，或者为增强的无线链路控制RLC实体。
  9. 根据权利要求8所述的方法，其中，
    当所述用户面实体为所述增强的PDCP实体时，所述用户面实体的下层实体为RLC实体或媒体接入控制MAC实体；和/或，
    当所述用户面实体为所述增强的RLC实体时，所述下层实体为MAC实体；
    其中，所述下层实体用于对接收到的所述用户面实体发送的PDU进行分割和/或级联。
  10. 根据权利要求2所述的方法，其中，所述传输缓存功能包括以下功能至少之一：
    缓存经头压缩和/或加密处理后的PDU；
    根据反馈信息对缓存的所述PDU进行删除或重传；
    根据本地维护的第一定时器对缓存的PDU进行删除或用空包替代。
  11. 根据权利要求10所述的方法，其中，所述根据反馈信息对缓存的所述PDU进行重传，包括：
    根据所述反馈信息重传完整的缓存的所述PDU；或者，
    根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据。
  12. 根据权利要求11所述的方法，其中，在所述根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据之前，所述方法还包括：
    更新待重传的所述PDU的单元头信息，其中，更新后的所述单元头信息包括以下至少之一：原始的所述PDU的序号，待重传的所述PDU的部分数据在原始的所述PDU中的位置信息。
  13. 根据权利要求10所述的方法，还包括：
    所述第一定时器启动的条件为：所述用户面实体接收到所述SDU，其中，所述用户面实体为接收到的每一个所述SDU维护一个所述第一定时器，所述SDU为所述用户面实体从高层接收到的数据单元。
  14. 根据权利要求2所述的方法，其中，所述接收缓存功能包括以下功能：
    检测到接收到的所述PDU丢失后，启动第二定时器；
    当所述第二定时器超时后，且仍没有收到丢失的所述PDU的情况下，向所述发送端发送状态报告，其中，所述状态报告用于告知所述发送端所述接收端接收丢失的所述PDU失败；
    在所述第二定时器超时前，收到丢包的所述PDU的情况下，停止所述第二定时器的计时。
  15. 根据权利要求2所述的方法，其中，所述发送端缓存的所述数据单元为数据PDU，和/或，与所述头压缩功能对应的控制PDU。
  16. 一种数据处理的装置，包括：
    确定模块，设置为确定用于对数据进行处理的用户面实体，其中，所述用户面实体具备以下模块：重传模块，设置为对所述数据进行重传；动态路由模块，设置为确定所述数据的传输路径；
    处理模块，设置为利用确定的所述用户面实体对所述数据进行处理。
  17. 根据权利要求16所述的装置，其中，所述用户面实体包括用于发送数据的发送端和/或用于接收数据的接收端，其中，
    所述发送端具备以下模块至少之一：
    传输缓存模块，设置为缓存协议数据单元PDU和/或业务数据单元SDU并对缓存的所述PDU和/或SDU进行处理；
    所述动态路由模块；
    头压缩模块，设置为对所述PDU和/或SDU的单元头进行压缩；
    加密模块，设置为对所述PDU和/或SDU进行加密；
    所述接收端具备以下模块至少之一：
    接收缓存模块，设置为对接收的协议数据单元PDU和/或业务数据单元SDU进行接收缓存；
    重排模块，设置为对接收的所述PDU和/或所述SDU进行重排；
    解头压缩模块，设置为对接收的所述PDU和/或所述SDU的单元头进行解压缩；
    解密模块，设置为对接收的所述PDU和/或所述SDU进行解密。
  18. 根据权利要求16或17所述的装置，其中，所述动态路由模块包括以下至少之一：
    第一选择单元，设置为对所述用户面实体待发送的协议数据单元PDU进行路由选择，并根据所述待发送的PDU的类型，选择相对应的路由策略；
    传输单元，设置为直接将所述待发送的PDU传输给下层实体、或通过网元间接口将所述待发送的PDU传递给预定网元。
  19. 根据权利要求18所述的装置，其中，所述待发送的PDU的类型包括以下至少之一：
    首次传输的PDU，重传的PDU，承载控制面板信令的PDU，承载用户面信令的PDU，重传次数达到预定阈值的PDU，其中，所述预定阈值由第一预定协议约定或由第一高层信令配置。
  20. 根据权利要求18所述的装置，其中，所述第一选择单元包括：
    第二选择单元，设置为根据所述PDU的类型，在待发送的所述PDU满足预定条件的情况下，选择预定的分支进行发送，其中，所述预定的分支由第二预定协议约定或者由第二高层信令配置。
  21. 根据权利要求20所述的装置，其中，所述预定的分支包括以下至少之一：
    采用预定的传输技术的分支，连接到预定网元的传输分支，配置有预定服务质量QoS要求的逻辑信道和/或传输信道。
  22. 根据权利要求16所述的装置，其中，所述用户面实体位于核心网，或者接入网。
  23. 根据权利要求16所述的装置，其中，所述用户面实体为增强的分组数据汇聚协议PDCP实体，或者为增强的无线链路控制RLC实体。
  24. 根据权利要求23所述的装置，其中，
    当所述用户面实体为所述增强的PDCP实体时，所述用户面实体的下层实体为RLC实体或媒体接入控制MAC实体；和/或，
    当所述用户面实体为所述增强的RLC实体时，所述下层实体为MAC实体；
    其中，所述下层实体用于对接收到的所述用户面实体中发送的PDU进行分割和/或级联。
  25. 根据权利要求17所述的装置，其中，所述传输缓存模块包括以下单元至少之一：
    缓存单元，设置为缓存经头压缩和/或加密处理后的PDU；
    第一处理单元，设置为根据反馈信息对缓存的所述PDU进行删除或重传；
    第二处理单元，设置为根据本地维护的第一定时器对缓存的PDU进行删除或用空包替代。
  26. 根据权利要求25所述的装置，其中，所述第一处理单元包括：
    第一重传单元，设置为根据所述反馈信息重传完整的缓存的所述PDU；或者，
    第二重传单元，设置为根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据。
  27. 根据权利要求26所述的装置，其中，所述传输缓存模块还包括：
    更新单元，设置为在所述第一重传单元根据所述反馈信息重传没有收到确认指示的缓存的所述PDU中的部分数据之前，更新待重传的所述PDU的单元头信息，其中，更新后的所述单元头信息包括以下至少之一：原始的所述PDU的序号，待重传的所述PDU的部分数据在原始的所述PDU中的位置信息。
  28. 根据权利要求25所述的装置，还包括：
    所述第一定时器启动的条件为：所述用户面实体接收到所述SDU，其中，所述用户面实体为接收到的每一个所述SDU维护一个所述第一定时器，所述SDU为所述用户面实体从高层接收到的数据单元。
  29. 根据权利要求17所述的装置，其中，所述接收缓存模块包括以下单元：
    启动单元，设置为在检测到接收到的所述PDU丢失后，启动第二定时器；
    发送单元，设置为当所述第二定时器超时后，且仍没有收到丢失的所述PDU的情况下，向所述发送端发送状态报告，其中，所述状态报告用于告知所述发送端所 述接收端接收丢失的所述PDU失败；
    停止单元，设置为在所述第二定时器超时前，收到丢包的所述PDU的情况下，停止所述第二定时器的计时。
  30. 根据权利要求17所述的装置，其中，所述发送端缓存的所述数据单元为数据PDU，和/或，与所述头压缩功能对应的控制PDU。
PCT/CN2017/072487 2016-02-01 2017-01-24 数据处理的方法及装置 WO2017133595A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610072280.6A CN107027136B (zh) 2016-02-01 2016-02-01 数据处理的方法及装置
CN201610072280.6 2016-02-01

Publications (1)

Publication Number Publication Date
WO2017133595A1 true WO2017133595A1 (zh) 2017-08-10

Family

ID=59500592

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/072487 WO2017133595A1 (zh) 2016-02-01 2017-01-24 数据处理的方法及装置

Country Status (2)

Country Link
CN (1) CN107027136B (zh)
WO (1) WO2017133595A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109392025B (zh) 2017-08-11 2023-09-29 华为技术有限公司 数据传输方法和数据传输装置
CN116709593A (zh) 2018-02-14 2023-09-05 华为技术有限公司 确定协议数据单元会话服务网元的方法和装置
CN112637909B (zh) * 2019-09-24 2023-04-07 中国移动通信集团重庆有限公司 锚点网络的智能配置方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137441A (zh) * 2010-12-22 2011-07-27 华为技术有限公司 数据传输方法、设备及系统
CN102395156A (zh) * 2011-09-28 2012-03-28 电信科学技术研究院 应用于pdcp实体和rlc实体间的数据传输方法及装置
CN102761921A (zh) * 2007-04-26 2012-10-31 富士通株式会社 无线通信系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102761921A (zh) * 2007-04-26 2012-10-31 富士通株式会社 无线通信系统
CN102137441A (zh) * 2010-12-22 2011-07-27 华为技术有限公司 数据传输方法、设备及系统
CN102395156A (zh) * 2011-09-28 2012-03-28 电信科学技术研究院 应用于pdcp实体和rlc实体间的数据传输方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification", 3GPP TS 36. 323, 27 January 2016 (2016-01-27), XP055406780 *
"LTE; Evolved Universal Terrestrial Radio Access(E-UTRA); Packet Data Convergence Protocol (PDCP) specification", 3GPP TS 36. 323, 27 January 2016 (2016-01-27), XP055406780 *

Also Published As

Publication number Publication date
CN107027136A (zh) 2017-08-08
CN107027136B (zh) 2020-11-20

Similar Documents

Publication Publication Date Title
US11751097B2 (en) Method and apparatus for reestablishing packet data convergence protocol (PDCP) entity in a wireless communication system
KR102545953B1 (ko) 무선 통신 시스템에서 데이터 처리 방법 및 장치
WO2018127238A1 (zh) 信息处理方法及装置
TWI466484B (zh) 在無線裝置與網路間傳輸資料單元之序列的無線通訊裝置及方法
JP5541469B2 (ja) ハンドオーバ処理
RU2461147C2 (ru) Способ обработки радиопротокола в системе подвижной связи и передатчик подвижной связи
KR100938090B1 (ko) 이동통신 시스템에서 핸드오버 수행 방법 및 장치
KR102341420B1 (ko) 스위칭 방법, 액세스 네트워크 장치 및 단말 장치
US8611304B2 (en) Method, system and base station for transmitting data during cell handover
KR101563008B1 (ko) 무선통신 시스템에서 무선 베어러 해제 방법 및 수신기
WO2018127225A1 (zh) 数据传输方法、网络侧设备及用户设备
TWI646814B (zh) Data transmission method and related equipment
US20040165554A1 (en) System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change
KR20090031239A (ko) 성공적으로 수신했으나 헤더 압축 복원에 실패한 패킷의 처리 방법
JP2022528843A (ja) 高信頼低遅延サービスをサポートするシステムでのｐｄｃｐ制御データを処理する方法及び装置
KR20190019000A (ko) 차세대 이동 통신 시스템에서 효율적인 패킷 중복 전송 및 수신 방법 및 장치
KR102465541B1 (ko) 무선 통신 시스템에서 데이터 처리 방법 및 장치
WO2017133595A1 (zh) 数据处理的方法及装置
KR102655629B1 (ko) 이동 통신 시스템에서 핸드오버를 수행하는 방법 및 장치
KR102656608B1 (ko) 무선 통신 시스템에서 무선 노드 통신 방법 및 장치
GB2462699A (en) Delivering PDCP SDUs to an upper layer within a receiving side entity of an E-UMTS
CN111955027B (zh) 控制移动通信系统中的数据接收速率的方法和装置
JPWO2020178918A1 (ja) 無線通信システム、送受信方法、プログラム、無線通信基地局装置、制御回路および制御方法
KR102597038B1 (ko) 무선 통신 시스템에서의 무선 노드 통신 방법 및 장치
US20240163673A1 (en) Method and device for applying integrity protection or verification procedure to enhance security in wireless communication system

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: 17746915

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17746915

Country of ref document: EP

Kind code of ref document: A1