WO2019184703A1 - 接收方法、发送方法及通信设备 - Google Patents

接收方法、发送方法及通信设备 Download PDF

Info

Publication number
WO2019184703A1
WO2019184703A1 PCT/CN2019/077799 CN2019077799W WO2019184703A1 WO 2019184703 A1 WO2019184703 A1 WO 2019184703A1 CN 2019077799 W CN2019077799 W CN 2019077799W WO 2019184703 A1 WO2019184703 A1 WO 2019184703A1
Authority
WO
WIPO (PCT)
Prior art keywords
parameter
pdcp pdu
pdcp
received
repetitive detection
Prior art date
Application number
PCT/CN2019/077799
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 EP19776827.8A priority Critical patent/EP3780503A4/en
Publication of WO2019184703A1 publication Critical patent/WO2019184703A1/zh
Priority to US17/039,257 priority patent/US20210021496A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • 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/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H04L1/1841—Resequencing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]

Definitions

  • Embodiments of the present disclosure relate to the field of secondary link data replication technologies, and in particular, to a receiving method, a transmitting method, and a communication device capable of performing secondary link data repeatability detection.
  • R15V2X Vehicle to Everything
  • PDCP Packet Data Convergence Protocol
  • PDU Protocol Data Unit
  • RLC Radio Link Control
  • Different RLC entities correspond to different logical channels, and different logical channels have different LCIDs (Logical Channel Identifyes).
  • the MAC Medium Access Control
  • HARQ Hybrid Automatic Repeat reQuest
  • the current PDCP layer needs to perform repetitive detection to discard duplicate data packets, but there is no clear description of how to perform repetitive detection.
  • An object of the embodiments of the present disclosure is to provide a receiving method, a transmitting method, and a communication device capable of performing sub-link data repeatability detection.
  • an embodiment of the present disclosure provides a receiving method, for a receiving end, including:
  • the received secondary link PDCP PDU is repeatedly detected using the repeatability detection parameter.
  • an embodiment of the present disclosure provides a sending method, where the sending end includes:
  • the repetitive detection parameter is used by the receiving end to perform repetitive detection on the received sub-link packet data convergence protocol PDCP protocol data unit PDU.
  • an embodiment of the present disclosure further provides a communications device, including:
  • a parameter acquisition module configured to obtain a repetitive detection parameter
  • the repetitive detection module is configured to perform repetitive detection on the received sub-link packet data convergence protocol PDCP protocol data unit PDU by using the repetitive detection parameter.
  • an embodiment of the present disclosure further provides a communications device, including:
  • a sending module configured to send, by the receiving end, information for acquiring a repetitive detection parameter to the receiving end
  • the repetitive detection parameter is used by the receiving end to perform repetitive detection on the received sub-link packet data convergence protocol PDCP protocol data unit PDU.
  • an embodiment of the present disclosure further provides a communication device, including a memory, a processor, and a program stored on the memory and executable on the processor, wherein the program is used by the processor.
  • an embodiment of the present disclosure further provides a network device, including a memory, a processor, and a program stored on the memory and executable on the processor, wherein the program is used by the processor.
  • the receiving end when receiving the PDCP PDU generated by the sub-link data replication, performs repetitive detection by using the determined repetitive detection parameter, and implements repetitive detection based on the sub-link PDCP PDU.
  • FIG. 1 is a flowchart of a receiving method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a PDCP PDU involved in a specific embodiment of the present disclosure
  • 3a to 3c are schematic diagrams of management of an out-of-sequence management timer in a second embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of sequentially delivering a PDCP SDU according to a third embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of the pull receiving window X involved in the fourth embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of the push receiving window Y involved in the fifth embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a sending method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 9 is a second schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 10 is a third schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 11 is a fourth schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • An embodiment of the present disclosure provides a receiving method, which is used by a receiving end.
  • the receiving method is as shown in FIG. 1 and includes the following steps:
  • Step 101 Obtain a repeatability detection parameter.
  • Step 102 Perform repetitive detection on the received secondary link PDCP PDU by using the repetitive detection parameter.
  • the receiving method may be implemented in a protocol layer PDCP entity in the receiving end, and the received secondary link PDCP PDU is sent by the RLC entity.
  • the receiving end when receiving the PDCP PDU generated by the sub-link data replication, performs repetitive detection by using the determined repetitive detection parameter, and implements repetitive detection based on the sub-link PDCP PDU. .
  • the repetitive detection parameter may include at least one of the following parameters: a timer duration parameter, a reception window length parameter, and a sequence number (SN) length parameter.
  • the repetitive detection parameter includes an SN length parameter.
  • step 102 is specifically:
  • the received secondary link PDCP PDU is discarded, otherwise the PDCP SDU corresponding to the received secondary link PDCP PDU is delivered. (Service Data Unit) to the upper layer entity and add the first SN to the SN record information.
  • Service Data Unit Service Data Unit
  • the receiving end such as the PDCP entity of the terminal device UE, can record the SN of the received PDCP PDU by using the SN record information.
  • the SN of the received PDCP PDU exists in the SN record information, it indicates that the received PDCP PDU has been received before, and the received PDCP PDU is discarded at this time.
  • the SN of the received PDCP PDU is not recorded in the SN record information, it indicates that the received PDCP PDU has not been received before, and the PDCP SDU corresponding to the received PDCP PDU can be delivered to the upper layer. entity.
  • the reception status of the PDCP PDU is recorded by the SN record information, and the repeatability detection of the PDCP PDU is performed based on the reception condition, which is simple to implement.
  • the repetitive detection parameter includes an SN length parameter.
  • step 102 is specifically:
  • the received secondary link is discarded.
  • PDCP PDU otherwise the PDCP SDU corresponding to the secondary link PDCP PDU is buffered;
  • the first SN is the SN of the received secondary link PDCP PDU
  • the second SN is the minimum value of the SN of the PDCP PDU that has not been received before receiving the PDCP PDU
  • the third SN is received.
  • the maximum value of the SN of the PDCP PDU that has been received is equal to the sum of 1.
  • the method may further include:
  • the second SN is updated, and the first PDCP SDU in the buffered PDCP SDU is delivered in sequence; wherein the SN of the PDCP PDU corresponding to the first PDCP SDU is smaller than the updated second SN,
  • the updated second SN is the minimum value of the SN of the PDCP PDU that has not been received yet;
  • the third SN is updated to be the sum of the first SN and 1.
  • the method may further include:
  • the second SN is updated, and the second PDCP SDU in the buffered PDCP SDU is delivered in order;
  • the SN of the PDCP PDU corresponding to the second PDCP SDU is smaller than the updated second SN, and the updated second SN is the second smallest value of the SN of the PDCP PDU that has not been received yet, and the out-of-order management timer is detected. Start when the package is out of order.
  • the method may further include:
  • the out-of-sequence management timer is restarted, and the fourth SN is updated to be the third SN, where the fourth SN is the SN of the PDCP PDU that causes the packet to be out of order.
  • the out-of-sequence management timer stopped when the updated second SN is greater than or equal to the fourth SN is restarted, and the fourth SN is updated to be the third SN.
  • a PDCP PDU with SN equal to n1 ie, the first SN
  • the corresponding PDCP SDU is buffered, and RX_Deliv (ie, the second SN) is updated.
  • the SN corresponding to the next PDCP PDU that has not been received is updated to n2.
  • all the PDCP SDUs of the corresponding PDCP PDU in the cache are less than the updated RX_Deliv(n2), such as the PDCP with the SN being n1+1, n1+2, ..., n2-1.
  • PDCP SDU corresponding to the PDU when a PDCP PDU with SN equal to n1 (ie, the first SN) is received, the corresponding PDCP SDU is buffered, and RX_Deliv (ie, the second SN) is updated.
  • the SN corresponding to the next PDCP PDU that has not been received is updated to n2.
  • the corresponding PDCP SDU is buffered, and the RX_Deliv (ie, the second SN) is updated to point to the SN corresponding to the next PDCP PDU that has not been received yet. , which is updated to n3.
  • the SNs of the corresponding PDCP PDUs in the cache are delivered in sequence to all the PDCP SDUs of the updated RX_Deliv(n3), that is, the PDCPs with the SNs n2+1, n2+2, ..., n3-1 are delivered.
  • PDCP SDU corresponding to the PDU are delivered.
  • the blank box in FIG. 2 represents the SN of the received PDCP PDU
  • the slanted box represents the SN of the received PDCP PDU
  • the RX_Deliv update triggers the delivery of the PDCP SDU.
  • the RX_Deliv cannot be updated and the PDCP SDU cannot be triggered.
  • the second embodiment of the present disclosure may be solved by multiple means, such as a timer triggering RX_Deliv update, a buffered PDCP SDU exceeding a preset number, triggering an RX_Deliv update, and an SN maximum according to the received PDCP PDU.
  • the difference between the value and the SN minimum exceeds a preset value to trigger a scheme such as RX_Deliv update.
  • the following uses the timer to trigger the RX_Deliv update as an example.
  • RX_Deliv may be actively updated and updated to the second smallest value of the SN of the PDCP PDU that has not been received yet, that is, updated to n2. . If a PDCP PDU with SN equal to n2 has been received, RX_Deliv may be updated equal to n3.
  • the SNs of the corresponding PDCP PDUs in the cache are delivered in sequence to all the PDCP SDUs of the updated RX_Deliv.
  • the RX_Deliv update is triggered by the timer, and the delivery of the PDCP SDU is triggered by the update of the RX_Deliv, so that the problem that the PDCP SDU cannot be delivered due to the failure of the RX_Deliv update can be avoided, and the normal operation of the service is ensured.
  • the out-of-sequence management timer is started when the packet out-of-sequence is detected for the first time.
  • the out-of-sequence management timer is not restarted due to the discovery of a new out-of-order PDCP PDU until it times out or is actively stopped.
  • FIG. 2 it is assumed that the out-of-sequence management timer is started when a packet out-of-sequence is detected when receiving a PDCP PDU with SN equal to n2-1, and will not be restarted when a PDCP PDU with an SN greater than n2 is subsequently received.
  • Out of order management timer is assumed that the out-of-sequence management timer is started when a packet out-of-sequence is detected when receiving a PDCP PDU with SN equal to n2-1, and will not be restarted when a PDCP PDU with an SN greater than n2 is subsequently received.
  • the RX_timer ie, the fourth SN
  • p-1+1 that is, set to p
  • start the out-of-order management timer this timer will not restart due to the discovery of a new out-of-order PDCP PDU until it times out or is actively stopped.
  • RX_Deliv ie, the second SN
  • the PDCP SDU corresponding to the PDCP PDU is first cached. After the PDCP SDU is cached, the following is an update analysis of RX_Deliv according to various situations.
  • the update RX_Deliv is m. If the updated RX_Deliv is smaller than the current RX_timer, it indicates that the PDCP PDU is out of order before the PDCP PDU with the SN equal to p-1, so the state of the out-of-order management timer is maintained.
  • the updated RX_Deliv will be greater than or equal to RX_timer (Fig. 3b)
  • the updated RX_Deliv is p.
  • the out-of-order management timer started when receiving the PDCP PDU with SN equal to p-1 can be turned off until a new out-of-sequence problem is found.
  • the RX_Deliv When the RX_Deliv is updated to be greater than or equal to p at a certain time, it indicates that the out-of-sequence problem caused by receiving the PDCP PDU with the SN equal to p-1 has been resolved. At this time, the PDCP PDU with the SN equal to p-1 is closed. The out-of-order management timer that is started.
  • RX_timer RX_Next, that is, the RX_timer is updated to the sum of the maximum value of the SN of the PDCP PDU that has been received so far and the sum of 1.
  • the repetitive detection parameter includes an SN length parameter and a timer duration parameter of the repetitive detection timer corresponding to the SN.
  • step 102 is specifically:
  • the repeated detection timer corresponding to the first SN When the repeated detection timer corresponding to the first SN is in the active state, the received secondary link PDCP PDU is discarded, otherwise the PDCP SDU corresponding to the received secondary link PDCP PDU is buffered, and the repeated detection timing corresponding to the first SN is started. Device.
  • the method further includes:
  • the updated second SN is a minimum value of the SN of the PDCP PDU that has not been received yet;
  • the third PDCP SDU in the buffered PDCP SDU is delivered in sequence when the first SN is smaller than the second SN, and the PDCP SDU corresponding to the received PDCP PDU is deleted.
  • the second SN is the minimum value of the SN of the PDCP PDU that has not been received yet, and the SN of the PDCP PDU corresponding to the third PDCP SDU is less than or equal to the first SN.
  • the method further includes:
  • the second SN is updated; wherein the second SN before the update is the minimum value of the SN of the PDCP PDU that has not been received before receiving the PDCP PDU delivered by the RLC entity, and the updated The second SN is the second smallest value of the SN of the PDCP PDU that has not been received yet, and the out-of-sequence management timer is started when the packet out-of-sequence is detected.
  • the method may further include:
  • the SN corresponding to the repeated detection timer in the active state includes the SN that is greater than the updated second SN, restarting the stopped out-of-sequence management timer, and updating the fourth SN to be in a valid state
  • the updated second SN is smaller than the second SN.
  • the timeout out-of-sequence management timer is restarted, and the fourth SN is updated to the sum of the maximum value of the SN corresponding to the repeated detection timer in the active state and 1; wherein the fourth SN before the update is the resulting packet The sum of the SN and 1 of the out-of-order PDCP PDU.
  • the third embodiment of the present disclosure may set a repetitive detection timer for each received and buffered PDCP SDU.
  • the repetitive detection timer has two functions: For the repetitive detection, this has been explained in the previous information, and the description will not be repeated here; 2.
  • the PDCP SDU is triggered in combination with other conditions.
  • the RX_Deliv (the minimum value of the SN indicating the PDCP PDU that has not been received yet, that is, the second SN) and the RX_Timer are also set in the third embodiment of the present disclosure (the PDCP PDU that causes the out of order is received).
  • the sum of SN and 1 is the fourth SN).
  • the corresponding PDCP SDU is buffered, and RX_Deliv is updated to point to the SN corresponding to the next PDCP PDU that has not been received, that is, updated to n2.
  • the corresponding repetitive detection timer is started. After the repetitive detection timer expires, if the corresponding SN is smaller than the current RX_Deliv, the corresponding SN is less than or equal to n1.
  • the PDCP SDUs corresponding to all PDCP PDUs are delivered in order.
  • the corresponding PDCP SDU is also cached, but RX_Deliv is not updated, and the value of RX_Deliv is still n1.
  • the corresponding repeatability detection timer is started. After the repetitive detection timer expires, if the corresponding SN is greater than or equal to the current RX_Deliv, that is, the PDCP PDU with the SN less than n2 is not received, at this time, in order to ensure the in-order delivery, the SN is deleted.
  • the delivery of the PDCP SDU needs to satisfy a condition that the SN of the corresponding PDCP PDU is smaller than the current RX_Deliv.
  • the RX_Deliv cannot be updated and the PDCP SDU cannot be triggered.
  • the PDCP PDU with the SN equal to n1 cannot be received, the PDCP SDU corresponding to the received PDCP PDU with the SN greater than n1 cannot be delivered.
  • multiple methods may be used to solve the problem, such as the timer triggering the RX_Deliv update, the buffered PDCP SDU exceeding the preset number, triggering the RX_Deliv update, and according to the received PDCP PDU.
  • the difference between the SN maximum and minimum values exceeds the preset value to trigger the RX_Deliv update and other schemes.
  • the RX_Deliv may be updated to be updated to the second smallest value of the SN of the PDCP PDU that has not been received yet, that is, updated to n2. .
  • the PDCP SDU corresponding to the RX_Deliv of the SN and the PDCP PDU of the updated RX_Deliv of the SN may satisfy the delivery condition and trigger the delivery.
  • the RX_Deliv update scheme is triggered by the timer, which avoids the problem that the PDCP SDU cannot be delivered due to the failure of RX_Deliv to update, and ensures the normal operation of the service.
  • the management criteria are basically the same as the specific embodiment 2, namely:
  • the updated RX_Deliv is greater than or equal to the current RX_timer, it indicates that the out-of-order problem caused by receiving a PDCP PDU has been resolved, and the out-of-sequence management timer can be turned off at this time.
  • the out-of-sequence management timer after the timeout update RX_Deliv, if there is a PDCP SDU with the SN greater than the updated RX_Deliv in the received PDCP PDU (according to whether to start the repeated detection timer), it indicates that the out-of-sequence problem still exists.
  • the repeatability detection parameter includes an SN length parameter and a receive window length parameter of the first receive window.
  • step 102 is specifically:
  • the second SN is a minimum value of a SN of a PDCP PDU that has not been received before receiving the PDCP PDU
  • the third SN is a PDCP that has been received before receiving the PDCP PDU.
  • the method may further include:
  • the second SN is updated, and the fourth PDCP SDU in the buffered PDCP SDU is delivered in sequence; wherein the SN of the PDCP PDU corresponding to the fourth PDCP SDU is smaller than the updated second SN,
  • the updated second SN is the minimum value of the SN of the PDCP PDU that has not been received yet;
  • the third SN is updated to be the sum of the first SN and 1, the second SN is updated, and the updated first receiving window is delivered in order.
  • the third SN is updated to be the sum of the first SN and 1, and the fifth PDCP SDU in the buffered PDCP SDU is delivered in sequence; wherein the PDCP corresponding to the fifth PDCP SDU
  • the SN of the PDU is smaller than the difference between the updated third SN and the size of the first receiving window;
  • the second SN When the second SN is smaller than the difference between the updated third SN and the first receiving window size, the second SN is updated, and the sixth PDCP SDU in the buffered PDCP SDU is delivered in order; wherein the sixth PDCP SDU corresponds to The SN of the PDCP PDU is smaller than the updated second SN, and the updated second SN is the minimum value of the SN of the PDCP PDU that has fallen into the updated first receiving window but has not been received;
  • the updated first receiving window is determined according to the difference between the updated third SN and the updated third SN and the first receiving window size.
  • an RX_Deliv (the minimum value of the SN indicating the PDCP PDU that has not been received yet, that is, the second SN) and a receiving window X are set, wherein the receiving window X
  • the size is Win_Size
  • RX_Next indicates the maximum value of the SN of the PDCP PDU that has been received and the sum value of 1 (ie, the third SN)
  • the receiving window X is determined according to the difference between RX_Next and RX_Next and Win_Size (ie, RX_Next-Win_Size).
  • RX_Deliv is in the receive window X.
  • the PDCP PDU when the SN of the PDCP PDU is greater than or equal to RX_Next ⁇ Win_Size and less than RX_Next, the PDCP PDU is considered to fall into the receiving window, otherwise falls outside the window.
  • the PDCP PDU corresponding to the SN is discarded; when receiving the PDCP PDU whose SN is smaller than n1 and greater than n', It is considered that the corresponding PDCP SDU has been cached, and the PDCP SDU is also discarded.
  • the PDCP PDU with the SN equal to n1 is received, the corresponding PDCP SDU is cached.
  • the RX_Deliv may be updated to point to the SN corresponding to the next PDCP PDU that has not been received, that is, updated to n2, and submitted in the cache in order.
  • RX_Next When receiving a PDCP PDU whose SN is less than n' (ie, less than RX_Next-Win_Size), RX_Next may be updated to the sum of n' and 1 and RX_Deliv is updated, and the PDCP PDU corresponding to the updated RX_Deliv falls into the updated receiving window.
  • the updated RX_Deliv is the minimum value in the SN of the PDCP PDU that falls within the receive window X but has not yet been received.
  • the cached PDCP SDUs which are outside the updated reception window X ie, the left side of the reception window X shown in FIG. 5 are sequentially delivered; this updated reception window X is based on the updated RX_Next and the update.
  • the difference between RX_Next and Win_Size is determined.
  • the RX_Next may be updated to be the maximum value of the SN of the currently received PDCP PDU, and the SN in the cache is less than the updated RX_Next and Win_Size.
  • RX_Deliv After the RX_Next update, it may cause RX_Deliv to be updated.
  • RX_Deliv When RX_Deliv is smaller than the difference between the updated RX_Next and Win_Size, RX_Deliv may be updated, and the updated PDCP PDU corresponding to RX_Deliv falls into the updated receiving window X, and the updated RX_Deliv falls into the receiving window X, but The minimum value in the SN of the PDCP PDU that has not been received.
  • the PDCP SDU corresponding to all PDCP PDUs in the cache whose SN is smaller than the updated RX_Deliv is delivered in order.
  • the updated receiving window X is determined based on the updated RX_Next and the updated difference between RX_Next and Win_Size.
  • the repeatability detection parameter includes an SN length parameter and a receive window length parameter of the second receive window.
  • step 102 is specifically:
  • the received secondary link PDCP PDU is cached, or when When the first SN is smaller than the second SN, or when the first SN is greater than or equal to a sum of the size of the second SN and the second receiving window, the received secondary link PDCP PDU is discarded, otherwise the buffer is cached. a PDCP SDU corresponding to the received secondary link PDCP PDU;
  • the second SN is a minimum value of the SN of the PDCP PDU that has not been received before receiving the PDCP PDU.
  • the method further includes:
  • the SN of the PDCP PDU corresponding to the seventh PDCP SDU is smaller than the updated second SN, and the updated second SN is the minimum value of the SN of the PDCP PDU that has not been received yet.
  • the method may further include:
  • the second SN is updated, and the eighth PDCP SDU in the buffered PDCP SDU is delivered in order;
  • the SN of the PDCP PDU corresponding to the eighth PDCP SDU is smaller than the updated second SN, and the updated second SN is the second smallest value of the SN of the PDCP PDU that has not been received yet, and the out-of-order management timer is detected. Start when the package is out of order.
  • an RX_Deliv (a minimum value indicating a SN of a PDCP PDU that has not been received yet, that is, a second SN) and a receiving window Y are set, wherein the receiving window Y
  • the size of Win_Size is determined by the RX_Deliv and the sum of RX_Deliv and Win_Size (ie RX_Deliv+Win_Size).
  • the PDCP PDU when the SN of the PDCP PDU is greater than or equal to RX_Deliv and less than RX_Deliv+Win_Size, the PDCP PDU is considered to fall into the receiving window Y, otherwise falls outside the window Y.
  • the PDCP PDU When receiving a PDCP PDU whose SN is greater than or equal to n1 and less than n3, since the PDCP PDU falls within the receiving window Y, if the PDCP SDU corresponding to the PDCP PDU has been buffered, the PDCP PDU is discarded; when the SN is received When the PDCP PDU is smaller than n1, the PDCP PDU falls outside the receiving window, and the PDCP PDU corresponding to n1-1 is discarded. When the PDCP PDU with the SN greater than or equal to n3 is received, the PDCP PDU falls outside the receiving window. The PDCP PDU is also discarded; when a PDCP PDU with SN equal to n1 is received, the corresponding PDCP SDU is cached.
  • the RX_Deliv may be updated to point to the SN corresponding to the next PDCP PDU that has not been received, that is, updated to n2, and submitted in the cache in order.
  • the RX_Deliv update triggers the delivery of the PDCP SDU.
  • the RX_Deliv cannot be updated and the PDCP SDU cannot be triggered.
  • the fifth embodiment of the present disclosure may be solved by various means, such as a timer triggering RX_Deliv update, a buffered PDCP SDU exceeding a preset number, triggering an RX_Deliv update, and an SN maximum according to the received PDCP PDU.
  • the difference between the value and the SN minimum exceeds a preset value to trigger a scheme such as RX_Deliv update.
  • the following uses the timer to trigger the RX_Deliv update as an example.
  • RX_Deliv may be updated to be updated to the second smallest value of the SN of the PDCP PDU that has not been received yet, that is, updated to n2. . If a PDCP PDU with SN equal to n2 has been received, RX_Deliv may be updated equal to n3.
  • the out-of-order management timer is restarted, and the SN of the corresponding PDCP PDU in the cache is sequentially delivered to be smaller than all the PDCP SDUs of the updated RX_Deliv.
  • the RX_Deliv update is triggered by the timer, and the delivery of the PDCP SDU is triggered by the update of the RX_Deliv, so that the problem that the PDCP SDU cannot be delivered due to the failure of the RX_Deliv update can be avoided, and the normal operation of the service is ensured.
  • the receiving end may perform the above-described repeatability detection by using the above-mentioned repeatability detecting parameter.
  • the repetitive detection parameters can be obtained in a plurality of ways, directly or indirectly, as described below.
  • the receiving end can directly obtain the repetitive detection parameter according to the protocol agreement.
  • the related protocol has pre-defined the above-mentioned repetitive detection parameters, such as the timer duration parameter, the receiving window length parameter, and the serial number length parameter, and the receiving end directly reads the relevant parameter when performing related services. can.
  • the first correspondence between the service attribute parameter and the repetitive detection parameter may be used to obtain a repetitive detection parameter corresponding to the service attribute of the target service, where the target service is a service carried by the PDCP PDU.
  • mapping table The above correspondence can be embodied in the form of a mapping table.
  • the secondary link can be used for services with different requirements, such as services with higher latency requirements and services with higher reliability requirements.
  • the correspondence between different service attribute parameters and repetitive detection parameters is established according to different service requirements.
  • the receiving end may determine the repetitive detection parameter corresponding to the service based on the service carried by the PDCP PDU, and perform repetitive detection by using the repetitive detection parameter.
  • the service attribute parameter may include at least one of the following parameters: PPPP (ProSe Per-Packet Priority) parameter, PPPR (ProSe Per-Packet Reliability) Parameters and SLRB ID (SideLink Radio Bear ID) parameters.
  • PPPP ProSe Per-Packet Priority
  • PPPR ProSe Per-Packet Reliability
  • SLRB ID Seg Radio Bear ID
  • the corresponding timer can be set to a longer timing, and for a service with a higher delay, the corresponding timer can be set to a shorter timing.
  • the corresponding receiving window length parameter can be set larger, and for the service with higher delay requirement, the corresponding receiving window length parameter can be set smaller.
  • the corresponding timer can be set to a longer timing, and for a service with a lower delay requirement, the corresponding timer can be set to a shorter timing.
  • the corresponding receiving window length parameter can be set larger, and for services with lower delay requirements, the corresponding receiving window length parameter can be set smaller.
  • the foregoing first correspondence may be configured at the same time on the sending end and the receiving end at the same time, such as by agreement, or pre-configured (such as configured at the factory, or configured by the user). Both the sender and the receiver can obtain the first correspondence described above by themselves.
  • the specific embodiment of the present disclosure may also be configured only on the transmitting end, and is sent by the sending end to the receiving end when needed, that is, the method in the specific embodiment of the present disclosure further includes:
  • the second correspondence between the logical channel parameter and the repetitive detection parameter may be used to obtain a repetitive detection parameter corresponding to the logical channel parameter of the target logical channel; the target logical channel is the PDCP PDU. Logical channel.
  • the duplicated sub-link PDCP PDUs are respectively delivered to two different RLC entities, and different RLC entities correspond to different logical channels, and different logical channels have different LCIDs.
  • the above logical channel parameters may be logical channel priority parameters.
  • the corresponding timer can set a longer timing, and for a service with a higher priority of the logical channel, the corresponding timer can set a shorter timing.
  • the corresponding receive window length parameter can be set larger, and for a service with a lower logical channel priority, the corresponding receive window length parameter can be set to a shorter timing.
  • the foregoing second correspondence may be configured at the same time on the sending end and the receiving end at the same time, such as by agreement, or pre-configured (such as configured at the factory or configured by the user). Both the sender and the receiver can obtain the second correspondence described above by themselves.
  • the specific embodiment of the present disclosure may also be configured only on the transmitting end, and is sent by the sending end to the receiving end when needed, that is, the method in the specific embodiment of the present disclosure further includes:
  • the message carrying the repetitive detection parameter may be directly sent by the transmitting end.
  • the receiving end can directly parse and obtain the repetitive detection parameter carried therein, and perform the above repetitive detection by using the repetitive detection parameter described above.
  • the transmitting end can determine the repetitive detection parameter according to the various correspondences described above.
  • the repetitive detection parameter, the first correspondence, and the second correspondence may all be transmitted to the receiving end in advance by the transmitting end through a sub-link channel, such as a sub-link broadcast channel.
  • an embodiment of the present disclosure further provides a sending method, used by a sending end, including the following steps:
  • Step 701 Send information for the receiving end to obtain the repetitive detection parameter to the receiving end.
  • the repetitive detection parameter is used by the receiving end to perform repetitive detection on the received sub-link packet data convergence protocol PDCP protocol data unit PDU.
  • the receiving end when receiving the PDCP PDU generated by the sub-link data replication, performs repetitive detection by using the determined repetitive detection parameter, and implements repetitive detection based on the sub-link PDCP PDU.
  • the repetitive detection parameter includes at least one of the following parameters: a timer duration parameter, a reception window length parameter, and a sequence number length parameter.
  • the information carries the repetitive detection parameter, or a first correspondence between the service attribute parameter and the repetitive detection parameter, or a logical channel parameter and a second of the repetitive detection parameter. Correspondence relationship.
  • the service attribute parameter includes at least one of the following parameters: a PPPP parameter, a PPPR parameter, and a SLRB identifier parameter;
  • the logical channel parameter is a logical channel priority parameter.
  • an embodiment of the present disclosure further provides a communications device, including:
  • a parameter obtaining module 81 configured to acquire a repetitive detection parameter
  • the repetitive detection mode 82 is configured to perform repetitive detection on the received sub-link packet data convergence protocol PDCP protocol data unit PDU by using the repetitive detection parameter.
  • the receiving end when receiving the PDCP PDU generated by the sub-link data replication, performs repetitive detection by using the determined repetitive detection parameter, and implements repetitive detection based on the sub-link PDCP PDU.
  • the repetitive detection parameter includes at least one of the following parameters: a timer duration parameter, a reception window length parameter, and a sequence number length parameter.
  • the parameter obtaining module 81 specifically includes:
  • a first acquiring unit configured to acquire the repetitive detection parameter according to a protocol agreement
  • a second acquiring unit configured to acquire, by using a first correspondence between the service attribute parameter and the repetitive detection parameter, a repetitive detection parameter corresponding to the service attribute of the target service, where the target service is the received sub-link PDCP The service carried by the PDU;
  • a third acquiring unit configured to acquire, by using a second correspondence between the logical channel parameter and the repetitive detection parameter, a repetitive detection parameter corresponding to a logical channel parameter of the target logical channel, where the target logical channel is to transmit the received Logical channel of the secondary link PDCP PDU;
  • the fourth acquiring unit is configured to obtain the repetitive detection parameter carried in the message sent by the sending end.
  • the service attribute parameter includes at least one of the following parameters: a PPPP parameter, a PPPR parameter, and a SLRB identifier parameter;
  • the logical channel parameter is a logical channel priority parameter.
  • the communications device further includes:
  • the receiving module is configured to receive the first correspondence and/or the second correspondence sent by the sending end.
  • the fourth acquiring unit is specifically configured to:
  • the repetitive detection parameter carried in the message sent by the sending end through the sub-link broadcast channel is obtained.
  • the repetitive detection parameter includes a sequence number length parameter
  • the repetitive detection module 82 is specifically configured to: when the SN record information maintained by the communication device includes the first SN, discard the receiving The sub-link PDCP PDU is sent, otherwise the PDCP SDU corresponding to the received sub-link PDCP PDU is delivered to the upper layer entity, and the first SN is added to the SN record information.
  • the repetitive detection parameter includes a sequence number length parameter
  • the repetitive detection module 82 is specifically configured to: when the first SN is greater than the second SN, and is smaller than the third SN, and the received When the PDCP SDU corresponding to the secondary link PDCP PDU is already buffered, or when the first SN is smaller than the second SN, the received secondary link PDCP PDU is discarded, otherwise the received secondary link is buffered.
  • the second SN is a minimum value of a SN of a PDCP PDU that has not been received before receiving the PDCP PDU
  • the third SN is a PDCP that has been received before receiving the PDCP PDU.
  • the maximum value of the SN of the PDU is the sum of 1 and 1.
  • the repetitive detection parameter includes a sequence number length parameter and a timer duration parameter of the repetitive detection timer corresponding to the SN, where the repetitive detection module 82 is specifically configured to: when the first SN corresponds to a repetition When the detection timer is in the active state, the received secondary link PDCP PDU is discarded, otherwise the PDCP SDU corresponding to the received secondary link PDCP PDU is buffered, and the repeated detection timer corresponding to the first SN is started. .
  • the repetitive detection parameter includes a sequence number length parameter and a receiving window length parameter of the first receiving window, where the repetitive detecting module 82 is specifically configured to: when the first SN is greater than the second SN, and is smaller than a third SN, and the PDCP SDU corresponding to the received secondary link PDCP PDU is already buffered, or when the first SN is smaller than the second SN and greater than or equal to the size of the third SN and the first receiving window When the difference is, the received secondary link PDCP PDU is discarded, otherwise the PDCP SDU corresponding to the received secondary link PDCP PDU is buffered;
  • the second SN is a minimum value of a SN of a PDCP PDU that has not been received before receiving the PDCP PDU
  • the third SN is a PDCP that has been received before receiving the PDCP PDU.
  • the maximum value of the SN of the PDU is the sum of 1 and 1.
  • the repetitive detection parameter includes a sequence number length parameter and a receiving window length parameter of the second receiving window, where the repetitive detecting module 82 is specifically configured to: when the first SN is greater than or equal to the second SN, And less than the sum of the size of the second SN and the second receiving window, and the PDCP SDU corresponding to the received secondary link PDCP PDU is already buffered, or when the first SN is smaller than the second SN, or And discarding the received secondary link PDCP PDU when the first SN is greater than or equal to a sum of the second SN and the second receiving window size, and otherwise buffering the PDCP corresponding to the received secondary link PDCP PDU SDU;
  • the second SN is a minimum value of the SN of the PDCP PDU that has not been received before receiving the PDCP PDU.
  • an embodiment of the present disclosure further provides a communications device, including:
  • the sending module 91 is configured to send, by the receiving end, information for acquiring a repetitive detection parameter to the receiving end;
  • the repetitive detection parameter is used by the receiving end to perform repetitive detection on the received sub-link packet data convergence protocol PDCP protocol data unit PDU.
  • the repetitive detection parameter includes at least one of the following parameters: a timer duration parameter, a reception window length parameter, and a sequence number length parameter.
  • the information carries the repetitive detection parameter, or a first correspondence between the service attribute parameter and the repetitive detection parameter, or a logical channel parameter and a second of the repetitive detection parameter. Correspondence relationship.
  • the service attribute parameter includes at least one of the following parameters: a PPPP parameter, a PPPR parameter, and a SLRB identifier parameter;
  • the logical channel parameter is a logical channel priority parameter.
  • Embodiments of the present disclosure also provide a communication device including a processor, a memory, a computer program stored on the memory and executable on the processor, wherein the computer program is implemented by the processor.
  • FIG. 10 is a schematic diagram of a hardware structure of a communication device that implements various embodiments of the present disclosure.
  • the communication device 1000 includes, but is not limited to, a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, and a sensor 1005.
  • the structure shown in FIG. 10 does not constitute a limitation to the terminal, and the communication device may include more or less components than those illustrated, or may combine some components, or different component arrangements.
  • the communication device includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.
  • the processor 1010 is configured to:
  • the processor 1010 is configured to: control the radio frequency unit 1001 to send information for the receiving end to obtain the repetitive detection parameter to the receiving end;
  • the repetitive detection parameter is used by the receiving end to perform repetitive detection on the received sub-link PDCP PDU.
  • the receiving end when the receiving end receives the PDCP PDU generated based on the secondary link data replication, the receiving end performs the repetitive detection by using the determined repetitive detection parameter, and implements the repetitive detection based on the sub-link PDCP PDU.
  • the radio frequency unit 1001 can be used for receiving and transmitting signals during and after receiving or transmitting information or a call, and specifically, after receiving downlink data from the base station, processing the processor 1010; The uplink data is sent to the base station.
  • radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio unit 1001 can also communicate with the network and other devices through a wireless communication system.
  • the communication device provides the user with wireless broadband Internet access through the network module 1002, such as helping the user to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 1003 can convert the audio data received by the radio frequency unit 1001 or the network module 1002 or stored in the memory 1009 into an audio signal and output as a sound. Moreover, the audio output unit 1003 can also provide audio output (eg, call signal reception sound, message reception sound, etc.) related to a particular function performed by the communication device 1000.
  • the audio output unit 1003 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 1004 is for receiving an audio or video signal.
  • the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 images an still picture or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode.
  • the data is processed.
  • the processed image frame can be displayed on the display unit 1006.
  • the image frames processed by the graphics processor 10041 may be stored in the memory 1009 (or other storage medium) or transmitted via the radio frequency unit 1001 or the network module 1002.
  • the microphone 10042 can receive sound and can process such sound as audio data.
  • the processed audio data can be converted to a format output that can be transmitted to the mobile communication base station via the radio unit 1001 in the case of a telephone call mode.
  • Communication device 1000 also includes at least one type of sensor 1005, such as a light sensor, motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 10061 according to the brightness of the ambient light, and the proximity sensor can close the display panel 10061 when the communication device 1000 moves to the ear / or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity.
  • sensor 1005 may also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be described here.
  • the display unit 1006 is for displaying information input by the user or information provided to the user.
  • the display unit 1006 can include a display panel 10061.
  • the display panel 10061 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the user input unit 1007 can be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal.
  • the user input unit 1007 includes a touch panel 10071 and other input devices 10072.
  • the touch panel 10071 also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 10071 or near the touch panel 10071. operating).
  • the touch panel 10071 may include two parts of a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 1010 receives the commands from the processor 1010 and executes them.
  • the touch panel 10071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the user input unit 1007 may also include other input devices 10072.
  • the other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which are not described herein.
  • the touch panel 10071 can be overlaid on the display panel 10061. After the touch panel 10071 detects a touch operation thereon or nearby, the touch panel 10071 transmits to the processor 1010 to determine the type of the touch event, and then the processor 1010 according to the touch. The type of event provides a corresponding visual output on display panel 10061.
  • the touch panel 10071 and the display panel 10061 are used as two independent components to implement the input and output functions of the terminal in FIG. 10, in some embodiments, the touch panel 10071 and the display panel 10061 may be integrated. The input and output functions of the terminal are implemented, and are not limited herein.
  • the interface unit 1008 is an interface in which an external device is connected to the communication device 1000.
  • the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, and an audio input/output. (I/O) port, video I/O port, headphone port, and more.
  • the interface unit 1008 can be configured to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more components within the communication device 1000 or can be used at the communication device 1000 and externally Data is transferred between devices.
  • the memory 1009 can be used to store software programs as well as various data.
  • the memory 1009 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.).
  • the memory 1009 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
  • the processor 1010 is a control center of the communication device that connects various portions of the entire terminal using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 1009, and recalling data stored in the memory 1009, Perform various functions and processing data of the terminal to monitor the terminal as a whole.
  • the processor 1010 may include one or more processing units; optionally, the processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, an application, etc., and a modulation solution
  • the processor mainly handles wireless communication. It will be appreciated that the above described modem processor may also not be integrated into the processor 1010.
  • the communication device 1000 can also include a power source 1011 (such as a battery) for powering various components.
  • a power source 1011 such as a battery
  • the power source 1011 can be logically coupled to the processor 1010 through a power management system to manage charging, discharging, and power consumption through the power management system. Management and other functions.
  • the communication device 1000 may further include some functional modules not shown, which are not described herein again.
  • FIG. 11 is a schematic diagram showing the hardware structure of a communication device that implements various embodiments of the present disclosure.
  • the communication device 110 includes, but is not limited to, a bus 111, a transceiver 112, an antenna 113, a bus interface 114, a processor 115, and a memory 116.
  • communication device 110 further includes a computer program stored on memory 116 and executable on processor 115.
  • the computer program is executed by the processor 115 to implement the following steps:
  • the computer program is executed by the processor 115 to implement the following steps:
  • the control transceiver 112 sends information for the receiving end to obtain the repetitive detection parameter to the receiving end; wherein the repetitive detecting parameter is used by the receiving end to perform repetitive detection on the received sub-link PDCP PDU.
  • the transceiver 112 is configured to receive and transmit data under the control of the processor 115.
  • a bus architecture (represented by bus 111), which may include any number of interconnected buses and bridges, will include one or more processors represented by processor 115 and memory represented by memory 116.
  • the various circuits are linked together.
  • the bus 111 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 114 provides an interface between bus 111 and transceiver 112.
  • Transceiver 112 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.
  • Data processed by the processor 115 is transmitted over the wireless medium via the antenna 113. Further, the antenna 113 also receives the data and transmits the data to the processor 115.
  • the processor 115 is responsible for managing the bus 111 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 116 can be used to store data used by the processor 115 when performing operations.
  • the processor 115 can be a CPU, an ASIC, an FPGA, or a CPLD.
  • the embodiment of the present disclosure further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, implements the foregoing receiving method or each of the foregoing sending method embodiments, and can reach The same technical effect, in order to avoid repetition, will not be described here.
  • the computer readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本公开提供一种接收方法、发送方法及通信设备，其中，所述接收方法包括：获取重复性检测参数；利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议协议数据单元进行重复性检测。

Description

接收方法、发送方法及通信设备
相关申请的交叉引用
本申请主张在2018年3月30日在中国提交的中国专利申请No.201810276861.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开实施例涉及副链路数据复制技术领域，特别是一种能够执行副链路数据重复性检测的接收方法、发送方法及通信设备。
背景技术
目前，R15V2X(Vehicle to Everything)通信引入了副链路数据复制(Sidelink Packet Duplication)，以提高副链路V2X消息传输的可靠性。其中，副链路终端在PDCP(Packet Data Convergence Protocol，分组数据汇聚协议)层执行数据复制功能，经过复制的副链路PDCP PDU(Protocol Data Unit，协议数据单元)分别递交给两个不同的RLC(Radio Link Control，无线链路控制)实体。不同RLC实体对应不同的逻辑信道，不同的逻辑信道具有不同的LCID(Logical Channel Identify，逻辑信道标识)。此外，由于当前不支持在同一个载波(Carrier)上传输两个复制的数据包，因此MAC(Medium Access Control，媒体接入控制)层在处理来自不同逻辑信道的复制数据时，需经由不同的HARQ(Hybrid Automatic Repeat reQuest，混合自动重传请求)实体传输。
在引入副链路数据复制后，当前的PDCP层需要执行重复性检测以丢弃重复的数据包，但是对于如何执行重复性检测却没有明确记载。
发明内容
本公开实施例的目的在于提供一种能够执行副链路数据重复性检测的接收方法、发送方法及通信设备。
第一方面，本公开实施例提供了一种接收方法，用于接收端，包括：
获取重复性检测参数；
利用所述重复性检测参数，对接收到的副链路PDCP PDU进行重复性检测。
第二方面，本公开实施例提供了一种发送方法，用于发送端，包括：
发送用于接收端获取重复性检测参数的信息到所述接收端；
其中，所述重复性检测参数用于所述接收端对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
第三方面，本公开实施例还提供了一种通信设备，包括：
参数获取模块,用于获取重复性检测参数；
重复性检测模块，用于利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
第四方面，本公开实施例还提供了一种通信设备，包括：
发送模块，用于发送用于接收端获取重复性检测参数的信息到所述接收端；
其中，所述重复性检测参数用于所述接收端对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
第五方面，本公开实施例还提供了一种通信设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序，其中，所述程序被所述处理器执行时实现上述应用于接收端的接收方法的步骤，或实现上述应用于发送端的发送方法的步骤。
第六方面，本公开实施例还提供了一种网络设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序，其中，所述程序被所述处理器执行时实现上述应用于接收端的接收方法的步骤，或实现上述应用于发送端的发送方法的步骤。
在本公开实施例中，接收端在接收到基于副链路数据复制生成的PDCP PDU时，利用确定的重复性检测参数进行重复性检测，实现了基于副链路PDCP PDU的重复性检测。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本公开实施例提供的接收方法的流程图；
图2为本公开具体实施例中涉及的PDCP PDU的示意图；
图3a至图3c为本公开具体实施例二中对失序管理定时器管理的示意图；
图4为本公开具体实施例三中涉及的按序递交PDCP SDU的示意图；
图5为本公开具体实施例四中涉及的拉动接收窗口X的示意图；
图6为本公开具体实施例五中涉及的推动接收窗口Y的示意图；
图7为本公开实施例提供的发送方法的流程图；
图8为本公开实施例的通讯设备的结构示意图之一；
图9为本公开实施例的通讯设备的结构示意图之二；
图10为本公开实施例的通讯设备的结构示意图之三；
图11为本公开实施例的通讯设备的结构示意图之四。
具体实施方式
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
本公开实施例提供一种接收方法，用于接收端，所述接收方法如图1所示，包括如下步骤：
步骤101：获取重复性检测参数；
步骤102：利用所述重复性检测参数，对接收到的副链路PDCP PDU进行重复性检测。
其中，该接收方法可以是接收端中的协议层PDCP实体中实现，该接收到的副链路PDCP PDU为RLC实体发送。
本公开实施例的接收方法中，接收端在接收到基于副链路数据复制生成 的PDCP PDU时，利用确定的重复性检测参数进行重复性检测，实现了基于副链路PDCP PDU的重复性检测。
在本公开具体实施例中，该重复性检测参数可包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号(Sequence Number，SN)长度参数。
以下对如何结合上述的重复性检测参数进行重复性检测详细说明如下。
方式一
在方式一中，该重复性检测参数包括SN长度参数。对应的，步骤102具体为：
当接收端维护的SN记录信息中包括接收到的副链路PDCP PDU的第一SN时，丢弃接收到的副链路PDCP PDU，否则递交所述接收到的副链路PDCP PDU对应的PDCP SDU(Service Data Unit，服务数据单元)到上层实体，并在SN记录信息中增加第一SN。
对此详细说明如下。
本公开具体实施例一中，接收端，比如终端设备UE的PDCP实体可通过SN记录信息来记录已经接收到的PDCP PDU的SN。当接收到的PDCP PDU的SN存在于SN记录信息中，则表明该接收到的PDCP PDU之前已经接收到过，此时丢弃该接收到的PDCP PDU。而如果SN记录信息中没有记录该接收到的PDCP PDU的SN，则表明该接收到的PDCP PDU之前没有接收到过，此时可递交(Deliver)该接收到的PDCP PDU对应的PDCP SDU到上层实体。
这样，通过SN记录信息来记录PDCP PDU的接收情况，并基于该接收情况来进行PDCP PDU的重复性检测，实现简单。
方式二
在方式二中，该重复性检测参数包括SN长度参数。对应的，步骤102具体为：
当第一SN大于第二SN，且小于第三SN，且接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当第一SN小于第二SN时，丢弃接收到的副链路PDCP PDU，否则缓存副链路PDCP PDU对应的PDCP SDU；
其中，第一SN为接收到的副链路PDCP PDU的SN，第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，第三SN为在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值。
进一步的，在缓存PDCP SDU之后，所述方法还可包括：
当第一SN等于第二SN时，更新第二SN，并按序递交缓存的PDCP SDU中的第一PDCP SDU；其中，第一PDCP SDU对应的PDCP PDU的SN小于更新后的第二SN，更新后的第二SN为当前还未接收到的PDCP PDU的SN的最小值；
当第一SN大于或等于第三SN时，更新第三SN为第一SN与1的和值。
进一步的，所述方法还可包括：
当失序管理定时器超时后，更新第二SN，并按序递交缓存的PDCP SDU中的第二PDCP SDU；
其中，第二PDCP SDU对应的PDCP PDU的SN小于更新后的第二SN，更新后的第二SN为当前还未接收到的PDCP PDU的SN的次小值，失序管理定时器是在检测到包失序时启动。
进一步的，在更新第二SN之后，所述方法还可包括：
当失序管理定时器超时后更新的第二SN小于第三SN时，重新启动失序管理定时器，并更新第四SN为第三SN；其中，第四SN为导致包失序的PDCP PDU的SN与1的和值；
或者，
当第一SN等于第二SN时更新的第二SN大于或等于第四SN，停止失序管理定时器；其中，第四SN为导致包失序的PDCP PDU的SN与1的和值；
当更新后的第二SN小于第三SN值时，重新启动在更新的第二SN大于或等于第四SN时停止的失序管理定时器，并更新第四SN为第三SN。
下面结合图2至图3c对本公开具体实施例二的详细过程进行说明。
例如，为了保证按序递交，如图2所示，当接收到SN等于n1(即第一SN)的PDCP PDU时，则会缓存对应的PDCP SDU，并更新RX_Deliv(即 第二SN)使其指向下一个还没有接收到的PDCP PDU对应的SN，即更新为n2。在更新RX_Deliv之后，则会按序递交缓存中对应的PDCP PDU的SN小于更新后的RX_Deliv(n2)的所有PDCP SDU，比如递交SN为n1+1、n1+2、…、n2-1的PDCP PDU对应的PDCP SDU。
而在接收到SN等于n2(即第一SN)的PDCP PDU时，则会缓存对应的PDCP SDU，并更新RX_Deliv(即第二SN)使其指向下一个还没有接收到的PDCP PDU对应的SN，即更新为n3。在更新RX_Deliv之后，则会按序递交缓存中对应的PDCP PDU的SN小于更新后的RX_Deliv(n3)的所有PDCP SDU，即递交SN为n2+1、n2+2、…、n3-1的PDCP PDU对应的PDCP SDU。
需指出的是，图2中的空白框代表没有接收到的PDCP PDU的SN，斜线框代表接收到的PDCP PDU的SN。
上述的方式中，RX_Deliv更新之后触发PDCP SDU的递交。然而在某些情况下，PDCP PDU丢失而发送端并没有重发时，将导致RX_Deliv无法更新，也就无法触发PDCP SDU的递交。
为避免上述情况的出现，本公开具体实施例二可以采用多种手段来解决，如定时器触发RX_Deliv更新、缓存的PDCP SDU超过预设数量触发RX_Deliv更新以及根据已接收到的PDCP PDU的SN最大值和SN最小值之间的差超过预设值触发RX_Deliv更新等方案。
以下以定时器触发RX_Deliv更新为例进行说明。
例如，参见图2所示，假定在接收到SN＝n3-1的PDCP PDU时检测到包失序，则会启动失序管理定时器。当失序管理定时器超时后，若发现还未接收到SN＝n1的PDCP PDU，则可主动更新RX_Deliv，将其更新为当前还未接收到的PDCP PDU的SN的次小值，即更新为n2。若SN等于n2的PDCP PDU已经收到，则可更新RX_Deliv等于n3。
在更新RX_Deliv之后，则会按序递交缓存中对应的PDCP PDU的SN小于更新后的RX_Deliv的所有PDCP SDU。
这样，通过定时器触发RX_Deliv更新，并通过RX_Deliv的更新触发PDCP SDU的递交，可避免由于RX_Deliv无法更新导致的PDCP SDU无法 递交的问题，保证了业务的正常进行。
而在设置了上述失序管理定时器之后，就涉及到失序管理定时器的管理问题，详细说明如下。
首先，失序管理定时器在首次检测到包失序时启动，该失序管理定时器在超时或者被主动停止之前，不会由于发现新的失序PDCP PDU而重新启动。如参见图2所示，假定在接收到SN等于n2-1的PDCP PDU时检测到包失序，则会启动失序管理定时器，而在后续接收到SN大于n2的PDCP PDU时，不会重新启动失序管理定时器。
以下进一步对失序管理定时器的管理及控制进行详细说明。
例如，如图3a-图3c所示，假定在接收到SN＝p-1的PDCP PDU时检测到包失序，则会将RX_timer(即第四SN)设置为p-1+1，即设置为p，并启动失序管理定时器(该定时器在超时或被主动停止之前，不会由于发现新的失序PDCP PDU而重新启动)。而在SN小于p的PDCP PDU中，还未接收到的PDCP PDU的最小值为n，则RX_Deliv(即第二SN)为n。
当前接收到SN等于n(n小于m)的PDCP PDU时，首先会缓存该PDCP PDU对应的PDCP SDU。在缓存PDCP SDU之后，以下根据各种情况进行RX_Deliv的更新分析。
情况一
在接收到SN等于n(n小于m)的PDCP PDU之后，如图3a所示，SN等于p-1的PDCP PDU之前还存在未接收到的PDCP PDU。假定未接收到的PDCP PDU的SN的最小值为m，则更新RX_Deliv为m。更新后的RX_Deliv小于当前的RX_timer，则表明SN等于p-1的PDCP PDU之前还存在PDCP PDU失序的情况，所以维持失序管理定时器的状态不变。
情况二
在接收到SN等于n的PDCP PDU之后，如图3b所示，当SN等于p-1的PDCP PDU之前不存在未接收到的PDCP PDU时，则更新后的RX_Deliv会大于或等于RX_timer(图3b中更新后的RX_Deliv为p，当然如果SN＝p的PDCP PDU已经在之前接收到，则更新后的RX_Deliv会大于p)，此时表明由于接收到SN等于p-1的PDCP PDU所导致的失序问题已经解决，此时 可以关闭在接收到SN等于p-1的PDCP PDU时启动的失序管理定时器，直至发现新的失序问题。
情况三
情况二中，在接收到SN等于p-1的PDCP PDU所导致的失序问题已经解决。但由于PDCP PDU的接收是一个持续的过程，如图3c所示，假定在解决由于接收到SN等于p-1的PDCP PDU所导致的失序问题之前，还接收到了SN等于q-1的PDCP PDU，此时RX_Next(即第三SN)更新为q，其中，q-1大于p。
当某一时刻RX_Deliv更新后大于或等于p时，则表明由于接收到SN等于p-1的PDCP PDU所导致的失序问题已经解决，此时会关闭在接收到SN等于p-1的PDCP PDU时启动的失序管理定时器。
然后，由于已经接收到SN等于q-1的PDCP PDU，如果更新后的RX_Deliv小于q(RX_Next)，则表明还有至少一个SN小于q的PDCP PDU还未接收到，此时，虽然由于接收到SN等于p-1的PDCP PDU所导致的失序问题已经解决，但失序情况依然存在，此时应该重新启动失序管理定时器，并更新RX_timer＝RX_Next，开始新一轮的失序管理。
另外，失序管理定时器在超时更新RX_Deliv后，如果已经接收到的PDCP PDU中，存在SN大于更新后的RX_Deliv的PDCP SDU，则表明失序问题依旧存在，此时需要重启失序管理定时器，并将RX_timer＝RX_Next，即将RX_timer更新为当前已经收到的PDCP PDU的SN的最大值与1的和值。
方式三
在方式三中，该重复性检测参数包括SN长度参数和与SN对应的重复检测定时器的定时器时长参数。对应的，步骤102具体为：
当第一SN对应的重复检测定时器处于有效状态时，丢弃接收到的副链路PDCP PDU，否则缓存接收到的副链路PDCP PDU对应的PDCP SDU，并启动第一SN对应的重复检测定时器。
进一步的，在缓存所述PDCP SDU之后，所述方法还包括：
当第一SN等于第二SN时，更新第二SN；其中，更新后的第二SN为当前还未接收到的PDCP PDU的SN的最小值；
当第一SN对应的重复检测定时器超时后，第一SN小于第二SN时，按序递交缓存的PDCP SDU中的第三PDCP SDU，否则删除接收到的PDCP PDU对应的PDCP SDU；其中，第二SN为当前还未接收到的PDCP PDU的SN的最小值，第三PDCP SDU对应的PDCP PDU的SN小于或等于第一SN。
进一步的，所述方法还包括：
当失序管理定时器超时后，更新第二SN；其中，更新前的第二SN为在接收到RLC实体递交的PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，更新后的第二SN为当前还未接收到的PDCP PDU的SN的次小值，失序管理定时器是在检测到包失序时启动。
进一步的，在更新第二SN之后，所述方法还可包括：
当第一SN等于第二SN时更新的第二SN大于或等于第四SN时，停止失序管理定时器；其中，第四SN为导致包失序的PDCP PDU的SN与1的和值；
当处于有效状态的重复检测定时器对应的SN中，包括大于更新后的第二SN的SN时，重新启动停止的失序管理定时器，并更新第四SN为处于有效状态的重复检测定时器对应的SN的最大值与1的和值；
或者，
当处于有效状态的重复检测定时器对应的SN中，包括大于在失序管理定时器超时后更新后的第二SN的SN时，或者，当失序管理定时器超时后更新后的第二SN小于第四SN时，重新启动超时的失序管理定时器，并更新第四SN为处于有效状态的重复检测定时器对应的SN的最大值与1的和值；其中，更新前的第四SN为导致包失序的PDCP PDU的SN与1的和值。
下面结合图2和图4对本公开具体实施例三的详细过程进行说明。
具体的，为了保证按序递交，本公开具体实施例三可为每个接收到并缓存下来的PDCP SDU设置了一个重复性检测定时器，该重复性检测定时器有两个作用：1、用于重复性检测，这已经在前面进行信息说明，在此不再重复描述；2、结合其他条件触发PDCP SDU的递交。
和上述具体实施例一样，本公开具体实施例三中也设置了一个RX_Deliv(指示当前还未收到的PDCP PDU的SN的最小值，即第二SN)和 RX_Timer(接收到导致失序的PDCP PDU的SN与1的和值，即第四SN)。
如图2所示，当接收到SN等于n1的PDCP PDU时，则会缓存对应的PDCP SDU，并更新RX_Deliv使其指向下一个还没有接收到的PDCP PDU对应的SN，即更新为n2。同时在接收到SN＝n1的PDCP PDU后会启动对应的重复性检测定时器，该重复性检测定时器到时之后，如果对应的SN小于当前的RX_Deliv，则会将对应的SN小于或等于n1的所有PDCP PDU对应的PDCP SDU按序递交。
进一步如图2所示，假定先接收到SN等于n2的PDCP PDU时，也会缓存对应的PDCP SDU，但不会更新RX_Deliv，此时RX_Deliv的值还是n1。同时在接收到SN等于n2的PDCP PDU后会启动对应的重复性检测定时器。该重复性检测定时器到时之后，如果对应的SN大于或等于当前的RX_Deliv，也就是说，还有SN小于n2的PDCP PDU未接收到，此时，为了保证按序递交，则会删除SN等于n2的PDCP PDU对应的PDCP SDU。
对于如何按序递交PDCP SDU可参见图4所示。如图4所示，假定当前RX_Deliv等于n3+1，如果Timer_n2先到期，则会按序递交SN小于或等于n2的所有PDCP PDU对应的PDCP SDU，并删除对应的重复检测定时器。然后Timer_n3到期，则会按序递交SN小于或等于n3，且大于n2的所有PDCP PDU对应的PDCP SDU，并删除对应的重复检测定时器。而如果Timer_n3先到期，则会按序递交SN小于或等于n3的所有PDCP PDU对应的PDCP SDU，并删除对应的重复检测定时器。
本公开具体实施例三中，PDCP SDU的递交需要满足一个条件，即对应的PDCP PDU的SN要小于当前的RX_Deliv。然而在某些情况下，PDCP PDU丢失而发送端并没有重发时，将导致RX_Deliv无法更新，也就无法触发PDCP SDU的递交。如图2所示，若SN等于n1的PDCP PDU一直无法收到，此时接收到的SN大于n1的PDCP PDU对应的PDCP SDU都无法递交。
本公开具体实施例三中，为了避免上述情况的出现，可以采用多种手段来解决，如定时器触发RX_Deliv更新、缓存的PDCP SDU超过预设数量触发RX_Deliv更新、以及根据已接收到的PDCP PDU的SN最大值和最小值之间的差超过预设值触发RX_Deliv更新等方案。
以下以定时器触发RX_Deliv更新为例进行说明如下。
例如，参见图2所示，假定在接收到SN＝n3-1的PDCP PDU时检测到包失序，则会启动失序管理定时器。当失序管理定时器超时后，若发现还未接收到SN＝n1的PDCP PDU，则可强制更新RX_Deliv，将其更新为当前还未接收到的PDCP PDU的SN的次小值，即更新为n2。而在更新RX_Deliv之后，SN在更新前的RX_Deliv和更新后的RX_Deliv的PDCP PDU对应的PDCP SDU则可能满足递交条件，触发递交。
这样，通过定时器触发RX_Deliv更新的方案，可避免由于RX_Deliv无法更新导致的PDCP SDU无法递交的问题，保证业务的正常进行。
而在设置了上述失序管理定时器之后，就涉及到失序管理定时器的管理问题，详细说明如下。
其管理准则和具体实施例二基本相同，即：
当更新后的RX_Deliv小于当前的RX_timer时，维持失序管理定时器的状态不变；
当更新后的RX_Deliv大于或等于当前的RX_timer时，则表明由于接收到某PDCP PDU所导致的失序问题已经解决，此时可关闭该失序管理定时器。
而失序管理定时器在超时更新RX_Deliv后，如果已经接收到的PDCP PDU中，存在SN大于更新后的RX_Deliv的PDCP SDU(依据是否启动重复检测定时器判断)，则表明失序问题依旧存在，此时需要重启失序管理定时器，并更新RX_timer＝RX_Next，即将RX_timer更新为当前已经收到的PDCP PDU的SN的最大值与1的和值。
方式四
在方式四中，该重复性检测参数包括SN长度参数和第一接收窗口的接收窗口长度参数。对应的，步骤102具体为：
当第一SN大于第二SN，且小于第三SN，且接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN，且大于或等于第三SN与第一接收窗口大小的差值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP  PDU的SN的最小值，所述第三SN为在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值；
进一步的，在缓存接收到的PDCP PDU对应的PDCP SDU之后，所述方法还可包括：
当第一SN等于第二SN时，更新第二SN，并按序递交缓存的PDCP SDU中的第四PDCP SDU；其中，第四PDCP SDU对应的PDCP PDU的SN小于更新后的第二SN，更新后的第二SN为当前还未接收到的PDCP PDU的SN的最小值；
当第一SN小于第三SN与第一接收窗口大小的差值时，更新第三SN为第一SN与1的和值，更新第二SN，并按序递交处于更新后的第一接收窗口外的缓存的PDCP SDU；其中，更新后的第二SN为落入更新后的第一接收窗口内，但还未接收到的PDCP PDU的SN中的最小值；
当第一SN大于或等于第三SN时，更新第三SN为第一SN与1的和值，并按序递交缓存的PDCP SDU中的第五PDCP SDU；其中，第五PDCP SDU对应的PDCP PDU的SN小于更新后的第三SN与第一接收窗口大小的差值；
当第二SN小于更新后的第三SN与第一接收窗口大小的差值时，更新第二SN，并按序递交缓存的PDCP SDU中的第六PDCP SDU；其中，第六PDCP SDU对应的PDCP PDU的SN小于更新后的第二SN，更新后的第二SN为落入更新后的第一接收窗口内，但还未接收到的PDCP PDU的SN中的最小值；
其中，更新后的第一接收窗口是根据更新后的第三SN和更新后的第三SN与第一接收窗口大小的差值确定的。
下面结合图5对本公开具体实施例四的详细过程进行说明。
例如，参见图5所示，本公开具体实施例四中设置了一个RX_Deliv(指示当前还未收到的PDCP PDU的SN的最小值，即第二SN)和一个接收窗口X，其中接收窗口X的大小为Win_Size，RX_Next指示已经接收到的PDCP PDU的SN的最大值与1的和值(即第三SN)，接收窗口X是根据RX_Next和RX_Next与Win_Size的差值(即RX_Next-Win_Size)确定的，RX_Deliv处于接收窗口X内。
在本公开具体实施例中，当PDCP PDU的SN大于或等于RX_Next– Win_Size，且小于RX_Next时，则认为该PDCP PDU落入接收窗口内，否则落在窗口外。
当接收到SN大于n1，且小于n3，且对应的PDCP SDU已缓存的PDCP PDU时，则会丢弃SN对应的PDCP PDU；当接收到SN小于n1，且大于n'的PDCP PDU时，则直接认为对应的PDCP SDU已经被缓存，也会丢弃该PDCP SDU；当接收到SN等于n1的PDCP PDU时，则会缓存对应的PDCP SDU。
进一步的，当接收到SN等于n1(即等于RX_Deliv)的PDCP PDU时，可更新RX_Deliv使其指向下一个还没有接收到的PDCP PDU对应的SN，即更新为n2，并按序递交缓存中的SN小于n2的所有PDCP PDU对应的PDCP SDU。
当接收到SN小于n'(即小于RX_Next-Win_Size)的PDCP PDU时，可更新RX_Next为n'与1的和值，并更新RX_Deliv，更新后的RX_Deliv对应的PDCP PDU落入更新后的接收窗口内，且更新后的RX_Deliv为落入接收窗口X内，但还未接收到的PDCP PDU的SN中的最小值。更新完成后，按序递交处于更新后的接收窗口X外(即图5所示的接收窗口X的左侧)的缓存的PDCP SDU；此更新后的接收窗口X是根据更新后的RX_Next和更新后的RX_Next与Win_Size的差值确定的。
当接收到SN大于或等于n3(即大于或等于RX_Next)的PDCP PDU时，可更新RX_Next为当前接收到的PDCP PDU的SN的最大值，并按序递交缓存中SN小于更新后的RX_Next与Win_Size的差值的所有PDCP PDU对应的PDCP SDU。
在RX_Next更新后，可能会导致RX_Deliv更新。当RX_Deliv小于更新后的RX_Next与Win_Size的差值时，可更新RX_Deliv，更新后的RX_Deliv对应的PDCP PDU落入更新后的接收窗口X内，且更新后的RX_Deliv为落入接收窗口X内，但还未接收到的PDCP PDU的SN中的最小值。更新完成后，按序递交缓存中SN小于更新的RX_Deliv的所有PDCP PDU对应的PDCP SDU。此更新后的接收窗口X是根据更新后的RX_Next和更新后的RX_Next与Win_Size的差值确定的。
方式五
在方式五中，该重复性检测参数包括SN长度参数和第二接收窗口的接收窗口长度参数。对应的，步骤102具体为：
当所述第一SN大于或等于第二SN，且小于第二SN与第二接收窗口大小的和值，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN时，或者，当所述第一SN大于或等于第二SN与第二接收窗口大小的和值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值。
进一步的，在缓存接收到的PDCP PDU之后，所述方法还包括：
当第一SN等于第二SN时，更新第二SN，并按序递交缓存的PDCP SDU中的第七PDCP SDU；
其中，第七PDCP SDU对应的PDCP PDU的SN小于更新后的第二SN，更新后的第二SN为当前还未接收到的PDCP PDU的SN的最小值。
进一步的，所述方法还可包括：
当失序管理定时器超时后，更新第二SN，并按序递交缓存的PDCP SDU中的第八PDCP SDU；
其中，第八PDCP SDU对应的PDCP PDU的SN小于更新后的第二SN，更新后的第二SN为当前还未接收到的PDCP PDU的SN的次小值，失序管理定时器是在检测到包失序时启动。
下面结合图6对本公开具体实施例五的详细过程进行说明。
例如，参见图6所示，本公开具体实施例五中设置了一个RX_Deliv(指示当前还未收到的PDCP PDU的SN的最小值，即第二SN)和一个接收窗口Y，其中接收窗口Y的大小为Win_Size，接收窗口Y是根据RX_Deliv和RX_Deliv与Win_Size的和值(即RX_Deliv+Win_Size)确定的。
参见图6所示，在本公开具体实施例中，当PDCP PDU的SN大于或等于RX_Deliv，且小于RX_Deliv+Win_Size时，则认为该PDCP PDU落入接收窗口Y内，否则落在窗口Y外。
当接收到SN大于或等于n1且小于n3的PDCP PDU时，由于该PDCP PDU落入接收窗口Y内，如果该PDCP PDU对应的PDCP SDU已被缓存，则会丢弃该PDCP PDU；当接收到SN小于n1的PDCP PDU时，该PDCP PDU落在接收窗外，则会丢弃SN等于n1-1对应的PDCP PDU；当接收到SN大于或等于n3的PDCP PDU时，由于该PDCP PDU落在接收窗外，也会丢弃该PDCP PDU；当接收到SN等于n1的PDCP PDU时，则会缓存对应的PDCP SDU。
进一步的，当接收到SN等于n1(即等于RX_Deliv)的PDCP PDU时，可更新RX_Deliv使其指向下一个还没有接收到的PDCP PDU对应的SN，即更新为n2，并按序递交缓存中的SN小于n2的所有PDCP PDU对应的PDCP SDU。
上述的方式中，RX_Deliv更新之后触发PDCP SDU的递交。然而在某些情况下，PDCP PDU丢失而发送端并没有重发时，将导致RX_Deliv无法更新，也就无法触发PDCP SDU的递交。
为避免上述情况的出现，本公开具体实施例五可以采用多种手段来解决，如定时器触发RX_Deliv更新、缓存的PDCP SDU超过预设数量触发RX_Deliv更新以及根据已接收到的PDCP PDU的SN最大值和SN最小值之间的差超过预设值触发RX_Deliv更新等方案。
以下以定时器触发RX_Deliv更新为例进行说明。
例如，参见图6所示，假定在接收到SN＝n3-1的PDCP PDU时检测到包失序，则会启动失序管理定时器。当失序管理定时器超时后，若发现还未接收到SN＝n1的PDCP PDU，则可强制更新RX_Deliv，将其更新为当前还未接收到的PDCP PDU的SN的次小值，即更新为n2。若SN等于n2的PDCP PDU已经收到，则可更新RX_Deliv等于n3。
在更新RX_Deliv之后，会重新启动失序管理定时器，并按序递交缓存中对应的PDCP PDU的SN小于更新后的RX_Deliv的所有PDCP SDU。
这样，通过定时器触发RX_Deliv更新，并通过RX_Deliv的更新触发PDCP SDU的递交，可避免由于RX_Deliv无法更新导致的PDCP SDU无法递交的问题，保证了业务的正常进行。
本公开具体实施例中，接收端可以通过上述的重复性检测参数来进行上述的重复性检测。
而该重复性检测参数可以通过直接或间接的多种方式获取，下面分别描述如下。
一种方式下，接收端可以依据协议约定来直接获取该重复性检测参数。
这种方式下，相关协议已经预先定义好了上述的重复性检测参数，如定时器时长参数、接收窗口长度参数和序列号长度参数，而接收端在进行相关业务时直接读取相关的参数即可。
另一种方式下，可以利用业务属性参数与重复性检测参数的第一对应关系，获取与目标业务的业务属性对应的重复性检测参数，所述目标业务为所述PDCP PDU承载的业务。
上述的对应关系可以以映射表的方式体现。
对此详细说明如下。
副链路可以用于各种不同需求的业务，如对时延要求比较高的业务，又如对可靠性要求比较高的业务。
本公开具体实施例中，根据不同的业务需求，建立不同业务属性参数和重复性检测参数的对应关系。而接收端在接收到副链路复制的PDCP PDU时，可以基于所述PDCP PDU承载的业务来确定，与该业务对应的重复性检测参数，并利用该重复性检测参数进行重复性检测。
所述业务属性参数可包括如下参数中的至少一个：PPPP(ProSe Per-Packet Priority，近距离通信数据分组包优先级)参数、PPPR(ProSe Per-Packet Reliability，近距离通信数据分组包可靠性)参数以及SLRB ID(SideLink Radio Bear ID，副链路无线承载标识)参数。
如对于时延(PPPR参数相关)要求比较低的业务，则相应的定时器可以设置较长的定时，而对于时延要求比较高的业务，则相应的定时器可以设置较短的定时。
如对于时延(PPPR参数相关)要求比较低的业务，则相应的接收窗口长度参数可以设置大一些，而对于时延要求比较高的业务，则相应的接收窗口长度参数可以设置小一些。
如对于可靠性(PPPP参数相关)要求比较高的业务，则相应的定时器可以设置较长的定时，而对于时延要求比较低的业务，则相应的定时器可以设置较短的定时。
如对于可靠性(PPPP参数相关)要求比较高的业务，则相应的接收窗口长度参数可以设置大一些，而对于时延要求比较低的业务，则相应的接收窗口长度参数可以设置小一些。
具体如何设置上述的对应关系，可以根据需求进行不同的设置，在此不作进一步详细描述。
本公开的具体实施例中，上述的第一对应关系可以同时在发送端和接收端同时配置，如通过协议约定，或进行预配置(如出厂时候配置好，或者由用户进行自主配置)，此时发送端和接收端都可以自行从自身得到上述的第一对应关系。
但本公开具体实施例中也可以仅在发送端配置，在需要使用时，由发送端发送给接收端，即本公开具体实施例的方法还包括：
接收发送端发送的所述第一对应关系。
再一种方式下，可以利用逻辑信道参数与重复性检测参数的第二对应关系，获取与目标逻辑信道的逻辑信道参数对应的重复性检测参数；所述目标逻辑信道为传输所述PDCP PDU的逻辑信道。
之前已经提到，经过复制的副链路PDCP PDU分别递交给两个不同的RLC实体，不同RLC实体对应不同的逻辑信道，不同的逻辑信道具有不同的LCID。
因此，本公开具体实施例中可以针对不同的逻辑信道设置不同的重复性检测策略。
上述的逻辑信道参数可以是逻辑信道优先级参数。
如对于逻辑信道优先级较低的业务，则相应的定时器可以设置较长的定时，而对于逻辑信道优先级较高的业务，则相应的定时器可以设置较短的定时。
如对于逻辑信道优先级较高的业务，则相应的接收窗口长度参数可以设置大一些，而对于逻辑信道优先级较低的业务，则相应的接收窗口长度参数 可以设置较短的定时。
具体如何设置上述的对应关系，可以根据需求进行不同的设置，在此不作进一步详细描述。
本公开的具体实施例中，上述的第二对应关系可以同时在发送端和接收端同时配置，如通过协议约定，或进行预配置(如出厂时候配置好，或者由用户进行自主配置)，此时发送端和接收端都可以自行从自身得到上述的第二对应关系。
但本公开具体实施例中也可以仅在发送端配置，在需要使用时，由发送端发送给接收端，即本公开具体实施例的方法还包括：
接收发送端发送的所述第二对应关系。
最后一种方式下，可以直接由发送端发送携带所述重复性检测参数的消息。接收端接收到该消息之后，即可直接解析并获取其中携带的重复性检测参数，并通过上述的重复性检测参数来进行上述的重复性检测。
而发送端可以根据上述的各种对应关系来确定重复性检测参数。
本公开具体实施例中，上述的重复性检测参数、第一对应关系、第二对应关系都可以通过副链路信道，如副链路广播信道由发送端提前传输给接收端。
参见图7所示，本公开实施例还提供了一种发送方法，用于发送端，包括如下步骤：
步骤701：发送用于接收端获取重复性检测参数的信息到所述接收端。
其中，所述重复性检测参数用于所述接收端对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
在本公开实施例中，接收端在接收到基于副链路数据复制生成的PDCP PDU时，利用确定的重复性检测参数进行重复性检测，实现了基于副链路PDCP PDU的重复性检测。
可选的，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
可选的，所述信息中携带有所述重复性检测参数，或，业务属性参数与所述重复性检测参数的第一对应关系，或，逻辑信道参数与所述重复性检测 参数的第二对应关系。
可选的，所述业务属性参数包括如下参数中的至少一个：PPPP参数、PPPR参数以及SLRB标识参数；
所述逻辑信道参数为逻辑信道优先级参数。
上述实施例对本公开的接收方法进行了说明，下面将结合实施例和附图对本公开的通信设备进行说明。
参见图8所示，本公开实施例还提供一种通信设备，包括：
参数获取模块81，用于获取重复性检测参数；
重复性检测模82，用于利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
在本公开实施例中，接收端在接收到基于副链路数据复制生成的PDCP PDU时，利用确定的重复性检测参数进行重复性检测，实现了基于副链路PDCP PDU的重复性检测。
可选的，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
可选的，所述参数获取模块81具体包括：
第一获取单元，用于根据协议约定获取所述重复性检测参数；
或者，
第二获取单元，用于利用业务属性参数与重复性检测参数的第一对应关系，获取与目标业务的业务属性对应的重复性检测参数，所述目标业务为所述接收到的副链路PDCP PDU承载的业务；
或者，
第三获取单元，用于利用逻辑信道参数与重复性检测参数的第二对应关系，获取与目标逻辑信道的逻辑信道参数对应的重复性检测参数，所述目标逻辑信道为传输所述接收到的副链路PDCP PDU的逻辑信道；
或者，
第四获取单元，用于获取发送端发送的消息中携带的所述重复性检测参数。
可选的，所述业务属性参数包括如下参数中的至少一个：PPPP参数、PPPR 参数以及SLRB标识参数；
所述逻辑信道参数为逻辑信道优先级参数。
可选的，所述通信设备还包括：
接收模块，用于接收发送端发送的所述第一对应关系和/或所述第二对应关系。
可选的，所述第四获取单元具体用于：
获取发送端通过副链路信道发送的消息中携带的所述重复性检测参数；
或，获取发送端通过副链路广播信道发送的消息中携带的所述重复性检测参数。
可选的，所述重复性检测参数包括序列号长度参数，所述重复性检测模块82具体用于：当所述通信设备维护的SN记录信息中包括所述第一SN时，丢弃所述接收到的副链路PDCP PDU，否则递交所述接收到的副链路PDCP PDU对应的PDCP SDU到上层实体，并在所述SN记录信息中增加所述第一SN。
可选的，所述重复性检测参数包括序列号长度参数，所述重复性检测模块82具体用于：当所述第一SN大于第二SN，且小于第三SN，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于所述第二SN时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，所述第三SN为在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值。
可选的，所述重复性检测参数包括序列号长度参数和与SN对应的重复检测定时器的定时器时长参数，所述重复性检测模块82具体用于：当所述第一SN对应的重复检测定时器处于有效状态时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU，并启动所述第一SN对应的重复检测定时器。
可选的，所述重复性检测参数包括序列号长度参数和第一接收窗口的接收窗口长度参数，所述重复性检测模块82具体用于：当所述第一SN大于第 二SN，且小于第三SN，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN，且大于或等于第三SN与第一接收窗口大小的差值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，所述第三SN为在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值。
可选的，所述重复性检测参数包括序列号长度参数和第二接收窗口的接收窗口长度参数，所述重复性检测模块82具体用于：当所述第一SN大于或等于第二SN，且小于第二SN与第二接收窗口大小的和值，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN时，或者，当所述第一SN大于或等于第二SN与第二接收窗口大小的和值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值。
参见图9所示，本公开实施例还提供一种通信设备，包括：
发送模块91，用于发送用于接收端获取重复性检测参数的信息到所述接收端；
其中，所述重复性检测参数用于所述接收端对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
可选的，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
可选的，所述信息中携带有所述重复性检测参数，或，业务属性参数与所述重复性检测参数的第一对应关系，或，逻辑信道参数与所述重复性检测参数的第二对应关系。
可选的，所述业务属性参数包括如下参数中的至少一个：PPPP参数、PPPR参数以及SLRB标识参数；
所述逻辑信道参数为逻辑信道优先级参数。
本公开实施例还提供一种通信设备，包括处理器，存储器，存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述计算机程序被所述处理器执行时实现上述接收方法实施例的各个过程，或上述发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
具体的，图10为实现本公开各个实施例的一种通信设备的硬件结构示意图，通信设备1000包括但不限于：射频单元1001、网络模块1002、音频输出单元1003、输入单元1004、传感器1005、显示单元1006、用户输入单元1007、接口单元1008、存储器1009、处理器1010、以及电源1011等部件。本领域技术人员可以理解，图10中示出的结构并不构成对终端的限定，通信设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开实施例中，通信设备包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
其中，当通信设备1000为接收端时，处理器1010用于：
获取重复性检测参数，利用所述重复性检测参数，对接收到的副链路PDCP PDU进行重复性检测。
当通信设备1000为发送端时，处理器1010用于：控制射频单元1001发送用于接收端获取重复性检测参数的信息到所述接收端；
其中，所述重复性检测参数用于所述接收端对接收到的副链路PDCP PDU进行重复性检测。
本公开实施例中，能够使得接收端在接收到基于副链路数据复制生成的PDCP PDU时，利用确定的重复性检测参数进行重复性检测，实现了基于副链路PDCP PDU的重复性检测。
应理解的是，本公开实施例中，射频单元1001可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器1010处理；另外，将上行的数据发送给基站。通常，射频单元1001包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元1001还可以通过无线通信系统与网络和其他设备通信。
通信设备通过网络模块1002为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元1003可以将射频单元1001或网络模块1002接收的或者在存储器1009中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元1003还可以提供与通信设备1000执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元1003包括扬声器、蜂鸣器以及受话器等。
输入单元1004用于接收音频或视频信号。输入单元1004可以包括图形处理器(Graphics Processing Unit，GPU)10041和麦克风10042，图形处理器10041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元1006上。经图形处理器10041处理后的图像帧可以存储在存储器1009(或其它存储介质)中或者经由射频单元1001或网络模块1002进行发送。麦克风10042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元1001发送到移动通信基站的格式输出。
通信设备1000还包括至少一种传感器1005，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板10061的亮度，接近传感器可在通信设备1000移动到耳边时，关闭显示面板10061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器1005还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元1006用于显示由用户输入的信息或提供给用户的信息。显示单元1006可包括显示面板10061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板10061。
用户输入单元1007可用于接收输入的数字或字符信息，以及产生与终端 的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元1007包括触控面板10071以及其他输入设备10072。触控面板10071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板10071上或在触控面板10071附近的操作)。触控面板10071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器1010，接收处理器1010发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板10071。除了触控面板10071，用户输入单元1007还可以包括其他输入设备10072。具体地，其他输入设备10072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板10071可覆盖在显示面板10061上，当触控面板10071检测到在其上或附近的触摸操作后，传送给处理器1010以确定触摸事件的类型，随后处理器1010根据触摸事件的类型在显示面板10061上提供相应的视觉输出。虽然在图10中，触控面板10071与显示面板10061是作为两个独立的部件来实现终端的输入和输出功能，但是在某些实施例中，可以将触控面板10071与显示面板10061集成而实现终端的输入和输出功能，具体此处不做限定。
接口单元1008为外部装置与通信设备1000连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元1008可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到通信设备1000内的一个或多个元件或者可以用于在通信设备1000和外部装置之间传输数据。
存储器1009可用于存储软件程序以及各种数据。存储器1009可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据 区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器1009可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器1010是通信设备的控制中心，利用各种接口和线路连接整个终端的各个部分，通过运行或执行存储在存储器1009内的软件程序和/或模块，以及调用存储在存储器1009内的数据，执行终端的各种功能和处理数据，从而对终端进行整体监控。处理器1010可包括一个或多个处理单元；可选的，处理器1010可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
通信设备1000还可以包括给各个部件供电的电源1011(比如电池)，可选的，电源1011可以通过电源管理系统与处理器1010逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，通信设备1000还可包括一些未示出的功能模块，在此不再赘述。
此外，图11为实现本公开各个实施例的一种通信设备的硬件结构示意图，通信设备110包括但不限于：总线111、收发机112、天线113、总线接口114、处理器115和存储器116。
在本公开实施例中，通信设备110还包括：存储在存储器116上并可在处理器115上运行的计算机程序。当通信设备110为接收端时，计算机程序被处理器115执行时实现以下步骤：
获取重复性检测参数，利用所述重复性检测参数，对接收到的副链路PDCP PDU进行重复性检测。
当通信设备110为发送端时，计算机程序被处理器115执行时实现以下步骤：
控制收发机112发送用于接收端获取重复性检测参数的信息到所述接收端；其中，所述重复性检测参数用于所述接收端对接收到的副链路PDCP PDU进行重复性检测。
收发机112，用于在处理器115的控制下接收和发送数据。
在图11中，总线架构(用总线111来代表)，总线111可以包括任意数 量的互联的总线和桥，总线111将包括由处理器115代表的一个或多个处理器和存储器116代表的存储器的各种电路链接在一起。总线111还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口114在总线111和收发机112之间提供接口。收发机112可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器115处理的数据通过天线113在无线介质上进行传输，进一步，天线113还接收数据并将数据传送给处理器115。
处理器115负责管理总线111和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器116可以被用于存储处理器115在执行操作时所使用的数据。
可选的，处理器115可以是CPU、ASIC、FPGA或CPLD。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述接收方法或者上述发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，该计算机可读存储介质，例如为只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光 盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本公开各个实施例所述的方法。
上面结合附图对本公开的实施例进行了描述，但是本公开并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本公开的启示下，在不脱离本公开宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本公开的保护之内。

Claims (24)

  1. 一种接收方法，用于接收端，包括：
    获取重复性检测参数；
    利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
  2. 根据权利要求1所述的接收方法，其中，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
  3. 根据权利要求1或2所述的接收方法，其中，所述获取重复性检测参数具体包括：
    根据协议约定获取所述重复性检测参数；
    或者，
    利用业务属性参数与重复性检测参数的第一对应关系，获取与目标业务的业务属性对应的重复性检测参数，所述目标业务为所述接收到的副链路PDCP PDU承载的业务；
    或者，
    利用逻辑信道参数与重复性检测参数的第二对应关系，获取与目标逻辑信道的逻辑信道参数对应的重复性检测参数；所述目标逻辑信道为传输所述接收到的副链路PDCP PDU的逻辑信道；
    或者，
    获取发送端发送的消息中携带的所述重复性检测参数。
  4. 根据权利要求3所述的接收方法，其中，
    所述业务属性参数包括如下参数中的至少一个：近距离通信数据分组包优先级PPPP参数、近距离通信数据分组包可靠性PPPR参数以及副链路无线承载SLRB标识参数；
    所述逻辑信道参数为逻辑信道优先级参数。
  5. 根据权利要求3所述的接收方法，还包括：
    接收发送端发送的所述第一对应关系和/或所述第二对应关系。
  6. 根据权利要求3所述的接收方法，其中，所述获取发送端发送的消息中携带的所述重复性检测参数具体为：
    获取发送端通过副链路信道发送的消息中携带的所述重复性检测参数；
    或者，
    获取发送端通过副链路广播信道发送的消息中携带的所述重复性检测参数。
  7. 根据权利要求2所述的接收方法，其中：
    所述重复性检测参数包括序列号长度参数；
    所述利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测具体为：
    当所述接收端维护的SN记录信息中包括所述接收到的副链路PDCP PDU的第一SN时，丢弃所述接收到的副链路PDCP PDU，否则递交所述接收到的副链路PDCP PDU对应的PDCP服务数据单元SDU到上层实体，并在所述SN记录信息中增加所述第一SN；
    或者，
    所述重复性检测参数包括序列号长度参数；
    所述利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测具体为：
    当所述第一SN大于第二SN，且小于第三SN，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于所述第二SN时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
    其中，所述第二SN为：在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，所述第三SN为：在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值；
    或者，
    所述重复性检测参数包括序列号长度参数和与SN对应的重复检测定时器的定时器时长参数；
    所述利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议 PDCP协议数据单元PDU进行重复性检测具体为：
    当所述第一SN对应的重复检测定时器处于有效状态时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU，并启动所述第一SN对应的重复检测定时器；
    或者，
    所述重复性检测参数包括序列号长度参数和第一接收窗口的接收窗口长度参数；
    所述利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测具体为：
    当所述第一SN大于第二SN，且小于第三SN，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN，且大于或等于第三SN与第一接收窗口大小的差值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
    其中，所述第二SN为：在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，所述第三SN为：在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值；
    或者，
    所述重复性检测参数包括序列号长度参数和第二接收窗口的接收窗口长度参数；
    所述利用所述重复性检测参数，对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测具体为：
    当所述第一SN大于或等于第二SN，且小于第二SN与第二接收窗口大小的和值，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN时，或者，当所述第一SN大于或等于第二SN与第二接收窗口大小的和值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
    其中，所述第二SN为：在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值。
  8. 一种发送方法，用于发送端，包括：
    发送用于接收端获取重复性检测参数的信息到所述接收端；
    其中，所述重复性检测参数用于所述接收端对接收到的副链路PDCP PDU进行重复性检测。
  9. 根据权利要求8所述的发送方法，其中，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
  10. 根据权利要求8或9所述的发送方法，其中，所述信息中携带有所述重复性检测参数，或，业务属性参数与所述重复性检测参数的第一对应关系，或，逻辑信道参数与所述重复性检测参数的第二对应关系。
  11. 根据权利要求10所述的发送方法，其中：
    所述业务属性参数包括如下参数中的至少一个：近距离通信数据分组包优先级PPPP参数、近距离通信数据分组包可靠性PPPR参数以及副链路无线承载SLRB标识参数；
    所述逻辑信道参数为逻辑信道优先级参数。
  12. 一种通信设备，包括：
    参数获取模块，用于获取重复性检测参数；
    重复性检测模块，用于利用所述重复性检测参数，对接收到的副链路PDCP PDU进行重复性检测。
  13. 根据权利要求12所述的通信设备，其中，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
  14. 根据权利要求12或13所述的通信设备，其中，所述参数获取模块具体包括：
    第一获取单元，用于根据协议约定获取所述重复性检测参数；
    或者，
    第二获取单元，用于利用业务属性参数与重复性检测参数的第一对应关系，获取与目标业务的业务属性对应的重复性检测参数，所述目标业务为所述接收到的副链路PDCP PDU承载的业务；
    或者，
    第三获取单元，用于利用逻辑信道参数与重复性检测参数的第二对应关系，获取与目标逻辑信道的逻辑信道参数对应的重复性检测参数，所述目标逻辑信道为传输所述接收到的副链路PDCP PDU的逻辑信道；
    或者，
    第四获取单元，用于获取发送端发送的消息中携带的所述重复性检测参数。
  15. 根据权利要求14所述的通信设备，其中：
    所述业务属性参数包括如下参数中的至少一个：PPPP参数、PPPR参数以及SLRB标识参数；
    所述逻辑信道参数为逻辑信道优先级参数。
  16. 根据权利要求14所述的通信设备，还包括：
    接收模块，用于接收发送端发送的所述第一对应关系和/或所述第二对应关系。
  17. 根据权利要求14所述的通信设备，其中，所述第四获取单元具体用于：
    获取发送端通过副链路信道发送的消息中携带的所述重复性检测参数；
    或者，
    获取发送端通过副链路广播信道发送的消息中携带的所述重复性检测参数。
  18. 根据权利要求14所述的通信设备，其中：
    所述重复性检测参数包括序列号长度参数，所述重复性检测模块具体用于：当所述通信设备维护的SN记录信息中包括所述第一SN时，丢弃所述接收到的副链路PDCP PDU，否则递交所述接收到的副链路PDCP PDU对应的PDCP SDU到上层实体，并在所述SN记录信息中增加所述第一SN；
    或者，
    所述重复性检测参数包括序列号长度参数，所述重复性检测模块具体用于：当所述第一SN大于第二SN，且小于第三SN，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于所述第二SN时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副 链路PDCP PDU对应的PDCP SDU；
    其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，所述第三SN为在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值；
    或者，
    所述重复性检测参数包括序列号长度参数和与SN对应的重复检测定时器的定时器时长参数，所述重复性检测模块具体用于：当所述第一SN对应的重复检测定时器处于有效状态时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU，并启动所述第一SN对应的重复检测定时器；
    或者，
    所述重复性检测参数包括序列号长度参数和第一接收窗口的接收窗口长度参数，所述重复性检测模块具体用于：当所述第一SN大于第二SN，且小于第三SN，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN，且大于或等于第三SN与第一接收窗口大小的差值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
    其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP PDU的SN的最小值，所述第三SN为在接收到所述PDCP PDU之前，已经接收到的PDCP PDU的SN的最大值与1的和值；
    或者，
    所述重复性检测参数包括序列号长度参数和第二接收窗口的接收窗口长度参数，所述重复性检测模块具体用于：当所述第一SN大于或等于第二SN，且小于第二SN与第二接收窗口大小的和值，且所述接收到的副链路PDCP PDU对应的PDCP SDU已缓存时，或者，当所述第一SN小于第二SN时，或者，当所述第一SN大于或等于第二SN与第二接收窗口大小的和值时，丢弃所述接收到的副链路PDCP PDU，否则缓存所述接收到的副链路PDCP PDU对应的PDCP SDU；
    其中，所述第二SN为在接收到所述PDCP PDU之前，还未接收到的PDCP  PDU的SN的最小值。
  19. 一种通信设备，包括：
    发送模块，用于发送用于接收端获取重复性检测参数的信息到所述接收端；
    其中，所述重复性检测参数用于所述接收端对接收到的副链路分组数据汇聚协议PDCP协议数据单元PDU进行重复性检测。
  20. 根据权利要求19所述的通信设备，其中，所述重复性检测参数包含如下参数中的至少一个：定时器时长参数、接收窗口长度参数和序列号长度参数。
  21. 根据权利要求19或20所述的通信设备，其中，所述信息中携带有所述重复性检测参数，或，业务属性参数与所述重复性检测参数的第一对应关系，或，逻辑信道参数与所述重复性检测参数的第二对应关系。
  22. 根据权利要求21所述的通信设备，其中：
    所述业务属性参数包括如下参数中的至少一个：近距离通信数据分组包优先级PPPP参数、近距离通信数据分组包可靠性PPPR参数以及副链路无线承载SLRB标识参数；
    所述逻辑信道参数为逻辑信道优先级参数。
  23. 一种通信设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，其中，所述程序被所述处理器执行时实现如权利要求1至7中任一项所述的接收方法的步骤，或实现如权利要求8至11中任一项所述的发送方法的步骤。
  24. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储程序，所述程序被处理器执行时实现如权利要求1至7中任一项所述的接收方法的步骤，或实现如权利要求8至11中任一项所述的发送方法的步骤。
PCT/CN2019/077799 2018-03-30 2019-03-12 接收方法、发送方法及通信设备 WO2019184703A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19776827.8A EP3780503A4 (en) 2018-03-30 2019-03-12 RECEPTION PROCEDURE, TRANSMISSION PROCESS AND COMMUNICATION DEVICE
US17/039,257 US20210021496A1 (en) 2018-03-30 2020-09-30 Receiving method, sending method, and communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810276861.0A CN110324195B (zh) 2018-03-30 2018-03-30 一种接收方法、发送方法及通信设备
CN201810276861.0 2018-03-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/039,257 Continuation US20210021496A1 (en) 2018-03-30 2020-09-30 Receiving method, sending method, and communications device

Publications (1)

Publication Number Publication Date
WO2019184703A1 true WO2019184703A1 (zh) 2019-10-03

Family

ID=68060933

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/077799 WO2019184703A1 (zh) 2018-03-30 2019-03-12 接收方法、发送方法及通信设备

Country Status (4)

Country Link
US (1) US20210021496A1 (zh)
EP (1) EP3780503A4 (zh)
CN (1) CN110324195B (zh)
WO (1) WO2019184703A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190119799A (ko) * 2018-04-13 2019-10-23 삼성전자주식회사 차세대 이동 통신 시스템에서 차량 통신을 지원하기 위한 자원할당 방법 및 장치
CN114830719A (zh) * 2019-12-31 2022-07-29 华为技术有限公司 一种通信方法和装置
CN111585841B (zh) * 2020-04-29 2022-01-07 深圳市元征科技股份有限公司 一种自动测试方法及相关装置
CN113840281A (zh) * 2020-06-23 2021-12-24 展讯通信（上海）有限公司 数据传输方法、设备、装置及存储介质
WO2022265465A1 (en) * 2021-06-18 2022-12-22 Lg Electronics Inc. Method and apparatus for transmitting data units based on time information by ue group in wireless communication system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104272796A (zh) * 2012-03-17 2015-01-07 黑莓有限公司 处理分组数据汇聚协议数据单元

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3113559B1 (en) * 2014-03-21 2023-07-26 Huawei Technologies Co., Ltd. Device and method for data transmission in direct communication
US10028311B2 (en) * 2014-04-22 2018-07-17 Lg Electronics Inc. Method for processing received PDCP PDUs for D2D communication system and device therefor
CN106797401B (zh) * 2014-10-31 2020-03-27 Lg电子株式会社 用于避免在d2d通信系统中发送仅具有填充的mac pdu的方法及其装置
US10212102B2 (en) * 2016-03-17 2019-02-19 Lg Electronics Inc. Method and apparatus for buffering V2X message for path switching in wireless communication system
CN107359968B (zh) * 2016-05-10 2020-05-26 电信科学技术研究院 一种单层序列号的数据传输方法及装置
EP3493586B1 (en) * 2017-05-19 2020-08-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for data reception and processing of radio link control layer
EP3582429B1 (en) * 2017-06-15 2021-08-04 Samsung Electronics Co., Ltd. Packet duplication control
KR102435428B1 (ko) * 2017-09-27 2022-08-24 삼성전자주식회사 무선 통신 시스템에서 패킷을 전송하기 위한 방법 및 장치

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104272796A (zh) * 2012-03-17 2015-01-07 黑莓有限公司 处理分组数据汇聚协议数据单元

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3780503A4 *
VIVO: "Packet Duplication Detection in Sidelink PDCP", 3GPP TSG-RAN WG2 MEETING #101BIS R2-1804697, 14 April 2018 (2018-04-14), XP051428411 *
VIVO: "Packet Duplication Indication for PC5", 3 GPP TSG-RAN WG2 MEETING#101 R2-1802005, 2 March 2018 (2018-03-02), XP051399080 *

Also Published As

Publication number Publication date
EP3780503A4 (en) 2021-04-28
US20210021496A1 (en) 2021-01-21
CN110324195B (zh) 2021-01-08
CN110324195A (zh) 2019-10-11
EP3780503A1 (en) 2021-02-17

Similar Documents

Publication Publication Date Title
WO2019184703A1 (zh) 接收方法、发送方法及通信设备
WO2019161741A1 (zh) 辅小区组添加方法、终端设备及主节点
WO2020088584A1 (zh) 副链路释放方法、终端及网络侧设备
WO2019096119A1 (zh) 业务处理方法及移动通信终端
WO2019218855A1 (zh) 数据包丢失率的测量方法、获取方法、终端及网络设备
WO2021037148A1 (zh) 数据传输方法及终端
CN112770350A (zh) 一种失败报告的上报方法及相关设备
WO2020063263A1 (zh) 旁链路的链路释放方法及终端
WO2019141132A1 (zh) 业务处理方法及移动通信终端
WO2020063240A1 (zh) 信道接入方法、配置方法、终端及网络侧设备
WO2020088178A1 (zh) 处理方法及终端
WO2019184763A1 (zh) 通信范围信息的处理方法及终端
WO2020169028A1 (zh) 副链路组播通信的配置方法和终端
CN110324851B (zh) 一种接收方法及通信设备
WO2021012871A1 (zh) 设置延时的方法及设备
WO2019056959A1 (zh) 完整性保护方法、终端和基站
WO2019137368A1 (zh) 系统信息的传输方法和用户终端
US11622296B2 (en) Data sending method and receiving method and user equipment
WO2021027714A1 (zh) 数据传输方法、接收设备及发送设备
JP7170119B2 (ja) ランダムアクセス方法、端末装置及びネットワーク装置
US20220201564A1 (en) Data transmission method, terminal, and network node
WO2019192514A1 (zh) 连接重建方法及相关设备
WO2019137425A1 (zh) 重配置方法、终端及基站
WO2019214472A1 (zh) 操作方法及终端
CN110943963B (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: 19776827

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019776827

Country of ref document: EP

Effective date: 20201030