WO2018127842A1 - Changement de numéro de séquence de protocole de convergence de données de paquets sans perte - Google Patents

Changement de numéro de séquence de protocole de convergence de données de paquets sans perte Download PDF

Info

Publication number
WO2018127842A1
WO2018127842A1 PCT/IB2018/050088 IB2018050088W WO2018127842A1 WO 2018127842 A1 WO2018127842 A1 WO 2018127842A1 IB 2018050088 W IB2018050088 W IB 2018050088W WO 2018127842 A1 WO2018127842 A1 WO 2018127842A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
cell
pdus
handover
state variables
Prior art date
Application number
PCT/IB2018/050088
Other languages
English (en)
Inventor
Jose Luis Pradas
Mikael WITTBERG
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2018127842A1 publication Critical patent/WO2018127842A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/037—Protecting confidentiality, e.g. by encryption of the control plane, e.g. signalling traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/142—Reselecting a network or an air interface over the same radio air interface technology

Definitions

  • Particular embodiments are directed to wireless communications and, more particularly, to preventing packet loss when changing the length of a Packet Data Convergence Protocol (PDCP) Sequence Number (SN).
  • PDCP Packet Data Convergence Protocol
  • SN Sequence Number
  • 3 GPP Third Generation Partnership Project
  • PDCP Packet Data Convergence Protocol
  • the network e.g., target node
  • SN PDCP sequence number
  • the PDCP transmitter can ensure lossless reconfigurations. Reducing the PDCP SN length, however, may result in data losses.
  • a network attempts to use the same size PDCP SN for all connected base stations.
  • a different SN length may be assigned for the same type of traffic.
  • UE user equipment
  • a handover normally triggers a PDCP re-establishment procedure to be performed both by the PDCP transmitter and the PDCP receiver.
  • the purpose of this procedure is to ensure that the PDCP layer can continue to handle traffic and avoid packet losses.
  • sequence numbers can be mapped from the PDCP window used in the source base station to the PDCP window used in the target base station, because the target window is longer than the source window.
  • the conversion is more complicated.
  • the window used in the source base station is larger than the window used in the target base station.
  • RLC radio link control
  • AM acknowledged mode
  • the network triggers a full radio resource control (RRC) reconfiguration.
  • RRC radio resource control
  • FIGURE 1 is a block diagram illustrating PDCP SN of different lengths. As explained in more detail below, the PDCP SN is part of a larger 32-bit value referred to as COUNT. FIGURE 1 illustrates how the structure of the COUNT value changes when the PDCP SN is shortened from length M to length N.
  • the PDCP protocol specification (3GPP TS 36.323) specifies different procedures, both for the receiver and the transmitter, where the usage of PDCP SN is required.
  • the PDCP SN is used in the PDCP protocol to keep different PDCP service data units (SDUs) in order, to identify packets, and as input into the ciphering algorithm.
  • SDUs PDCP service data units
  • the PDCP SN is included in the header of a PDCP protocol data unit (PDU). Thus, the length of the PDCP SN should be as short as possible.
  • the PDCP protocol uses the PDCP SN in certain procedures. For example, a PDCP transmitter may need to keep track of PDCP PDUs that have been submitted to lower layers and for which confirmation of successful delivery has not yet been received. As another example, the PDCP receiver may use the PDCP SN to ensure in-order delivery of any PDCP PDUs that are received from a lower layer. If packets are received out-of-order, PDCP may temporarily store these PDCP PDUs until the missing PDUs are received and the resulting set of PDUs can be disassembled into PDCP SDUs that can be forwarded in-order to higher layers.
  • a PDCP implementation normally keeps track of the status of PDCP PDUs.
  • the receiver uses a receiver window, and the sender uses a transmitter window. In these windows the status of each PDCP SN can be indicated.
  • the size of the transmitter and receiver windows determines how many PDCP PDUs the PDCP protocol can keep in flight at the same time.
  • in flight refers to the number of PDCP PDUs that can be transmitted without having received an acknowledgement (ACK) for successful delivery.
  • ACK acknowledgement
  • in flight refers to the number of PDCP PDUs that it can keep buffered to wait for any missing PDCP PDUs so that delivery towards higher layers is in-order.
  • Different services using different radio bearers may use different sizes of the PDCP
  • VoIP Voice over LTE
  • a high data rate service may use a relatively long PDCP SN because high data rates there may keep many PDCP PDUs in flight at the same time.
  • the size of the PDCP window (receiver and transmit) is half of the value range provided by the PDCP SN size. The reason is that the receiver needs to distinguish between PDCP PDUs that are older or newer than the most recent PDCP PDU received. Thus, using the complete window could result in the following situation.
  • the PDCP SN is one part of a larger value that is used to keep track of all PDCP PDUs.
  • the PDCP is combined with a Hyper Frame Number (HFN) to form a 32-bit value referred to as COUNT.
  • the COUNT value is formed as follows: (1) the PDCP SN is the least significant part of the COUNT (i.e., if the length of the PDCP SN is X bits, then the X least significant bits of COUNT is the PDCP SN); and (2) the HFN is the remaining most significant part of the COUNT that is not part of the PDCP SN (i.e., if the length of the PDCP SN is X bits, then the length of the HFN is 32 - X bits, which are the most significant bits of the COUNT).
  • COUNT is used as input when ciphering a PDCP PDU. It is not possible to use only the PDCP SN as input in the ciphering algorithm because then the same PDCP SN would be used for more than one PDCP PDU because of the wrap-around to 0 of the PDCP SN that happens frequently. Using the same number as input to the ciphering algorithm for different packets is considered unsafe.
  • the PDCP SN Only the PDCP SN is sent as part of the PDCP PDUs. Thus, the current value of the HFN is kept up to date by both the network and the UE. Both the network and the UE need to understand when the PDCP SN wraps around to zero and then the HFN is incremented by one.
  • the PDCP receiver may create status reports.
  • the first missing PDCP SN (FMS) is one of the elements used to create the status report.
  • the FMS has a length equal to the SN length.
  • the embodiments include methods to decrement the PDCP SN size.
  • the PDCP bearer is re-established as follows: (1) the receiver processes all PDCP protocol data units (PDUs) already received from the source node/cell and which are waiting in the receiver PDCP window, and it forwards these PDUs to higher layers; (2) the receiver sends, if requested, a status report back to the transmitter indicating the missing PDCP PDUs; (3) the PDCP state variables are reset to their initial values; and (4) the transmitter retransmits the payload of all PDCP PDUs for which it has not got a confirmation from lower layers of successful reception and for which it has not got confirmation of successful reception in a PDCP status report.
  • PDUs PDCP protocol data units
  • a method for use in a radio network element capable of operating as a PDCP transmitting entity comprises: performing a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; resetting PDCP state variables to initial values; for all PDCP PDUs for which the radio network element has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generating new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmitting the new PDCP PDUs.
  • resetting PDCP state variables to their initial values comprises setting Next PDCP TX SN to 0 and TX HFN to 0.
  • Generating new PDCP PDUs for all unconfirmed PDCP PDUs may comprise: performing ciphering of a PDCP payload using the reset Next_PDCP_TX_SN and TX HFN; assigning the reset Next_PDCP_TX_SN to PDCP payload; submitting the PDCP payload to a lower protocol layer for transmission; and incrementing Next_PDCP_TX_SN and TX HFN.
  • the PDCP transmitter comprises a network node or a wireless device.
  • a PDCP transmitter comprises processing circuitry operable to perform a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; reset PDCP state variables to initial values; for all PDCP PDUs for which the PDCP transmitter has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generate new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmit the new PDCP PDUs.
  • the processing circuitry is operable to reset PDCP state variables to their initial values by setting Next PDCP TX SN to 0 and TX HFN to 0.
  • the processing circuitry operable to generate new PDCP PDUs for all unconfirmed PDCP PDUs may be operable to: perform ciphering of a PDCP payload using the reset Next PDCP TX SN and TX HFN; assign the reset Next PDCP TX SN to PDCP payload; submit the PDCP payload to a lower protocol layer (e.g., RLC) for transmission; and increment Next_PDCP_TX_SN and TX HFN.
  • a lower protocol layer e.g., RLC
  • the PDCP transmitter comprises a network node or a wireless device.
  • a method in a radio network element capable of operating as a PDCP receiving entity comprises: performing a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; submitting to a higher protocol layer (e.g., RRC) all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and resetting PDCP state variables to initial values.
  • Resetting PDCP state variables to initial values may comprise setting Next PDCP RX SN to 0, RX HFN to 0, and Last submitted PDCP RX SN to Maximum PDCP SN.
  • the method further comprises identifying PDCP PDUs which were not received from the first cell using an updated first missing PDCP SN (FMS) format with a length greater than the PDCP SN length of the second cell.
  • the updated FMS format may have a length equivalent to the PDCP SN length of the first cell, or equivalent to the number of bits as a COUNT value of one of the identified PDCP PDUs not received from the first cell.
  • the method further comprises: receiving a handover reconfiguration message from one of the first or second cell; upon receiving the handover reconfiguration message, identifying PDCP PDUs which were not received from the first cell using the updated FMS; and sending a status report to the second cell.
  • the status report includes the updated FMS.
  • the radio network element comprises a wireless device or a network node.
  • a PDCP receiver comprises processing circuitry operable to: perform a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; submit to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and reset PDCP state variables to initial values.
  • the processing circuitry may be operable to reset PDCP state variables to initial values by setting Next PDCP RX SN to 0, RX HFN to 0, and Last submitted PDCP RX SN to Maximum PDCP SN.
  • the processing circuitry is further operable to identify PDCP PDUs which were not received from the first cell using an updated FMS format with a length greater than the PDCP SN length of the second cell.
  • the updated FMS format may have a length equivalent to the PDCP SN length of the first cell, or a length equivalent to the number of bits as a COUNT value of one of the identified PDCP PDUs not received from the first cell.
  • a wireless device comprises a PDCP transmitting module and a PDCP receiving module.
  • the PDCP transmitting module is operable to: perform a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; reset PDCP state variables to initial values; for all PDCP PDUs for which the wireless device has not received confirmation of receipt from a PDCP receiver (110, 120) (unconfirmed PDCP PDUs), generate new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmit the new PDCP PDUs.
  • the PDCP receiving module is operable to: perform a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; submit to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and reset PDCP state variables to initial values.
  • a network node comprises a PDCP transmitting module and a PDCP receiving module.
  • the PDCP transmitting module is operable to: perform a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; reset PDCP state variables to initial values; for all PDCP protocol data units (PDUs) for which the network node has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generate new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmit the new PDCP PDUs.
  • PDUs PDCP protocol data units
  • the PDCP receiving module is operable to: perform a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; submit to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and reset PDCP state variables to initial values.
  • the computer program product comprises instructions stored on non-transient computer-readable media which, when executed by a processor, perform the steps of: performing a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; resetting PDCP state variables to initial values; for all PDCP PDUs for which the processor has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generating new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmitting the new PDCP PDUs.
  • Another computer program product comprises instructions stored on non-transient computer-readable media which, when executed by a processor, perform the steps of: performing a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell; submitting to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and resetting PDCP state variables to initial values.
  • An advantage of particular embodiments is that there will not be any losses of PDCP PDUs in the radio interface, because the PDCP transmitter will ensure that all PDCP PDUs not yet confirmed to be received are retransmitted to the PDCP receiver. Because the PDCP receiver will receive any retransmitted PDCP PDUs after it has already forwarded all its received PDCP PDUs to higher layers, the PDCP PDUs that are received as new transmissions, but which are really re-transmissions, may be received out-of-order by higher layers.
  • Packet losses may be avoided when the length of the PDCP SN is decreased at handover.
  • Particular embodiments also ensure that the PDCP re-establishment procedure performed at handover can be done in a reliable way which avoids the risk of the Hyper Frame Number (HFN) values becoming out-of-sync between the transmitter and the receiver, which would otherwise lead to radio link failure (RLF).
  • HFN Hyper Frame Number
  • RLF radio link failure
  • FIGURE 1 is a block diagram illustrating PDCP SN of different length
  • FIGURE 2 is a block diagram illustrating an example mapping of a PDCP reception window to a smaller PDCP reception window
  • FIGURE 3 illustrates an example wireless network, according to a particular embodiment
  • FIGURE 4 is a flow diagram of an example method in a PDCP transmitter, according to some embodiments
  • FIGURE 5 is a flow diagram of an example method in a PDCP receiver, according to some embodiments
  • FIGURE 6 is another flow diagram of an example method in a PDCP transmitter, according to some embodiments.
  • FIGURE 7 is another flow diagram of an example method in a PDCP receiver, according to some embodiments.
  • FIGURE 8A is a block diagram illustrating an example embodiment of a wireless device
  • FIGURE 8B is a block diagram illustrating example components of a wireless device
  • FIGURE 9A is a block diagram illustrating an example embodiment of a network node
  • FIGURE 9B is a block diagram illustrating example components of a network node.
  • the network may change the Packet Date Convergence Protocol (PDCP) sequence number (SN) length.
  • PDCP Packet Date Convergence Protocol
  • SN Packet Number
  • RRC radio resource control
  • a problem with the first missing PDCP SN is that, after the reconfiguration, the UE will use the number of bits indicated for the PDCP SN length.
  • the FMS can only indicate a subset of the missing PDCP PDUs because the new receiving window in the target cell is shorter than at the source cell.
  • An alternative solution proposes decreasing the PDCP SN size at handover without the need for doing a full RRC reconfiguration by mapping parts of the PDCP windows with the long SN to the PDCP windows with the short SN.
  • An example is illustrated in FIGURE 2.
  • FIGURE 2 is a block diagram illustrating an example mapping of a PDCP reception window to a smaller PDCP reception window.
  • a PDCP SN in the middle of the larger reception window is chosen to become the low end of the smaller reception window.
  • the next expected PDCP SN for a new PDCP PDU is chosen to become the high end of the smaller reception window.
  • a problem with the illustrated example is that the PDCP PDUs that are stored in the receiver window between the Last Submitted PDCP RX SN and the "SN to become the Low End in the smaller window" do not fit in the smaller window and must either be discarded or forwarded to higher layers even though there are missing PDCP PDUs that have not yet been received. Thus, PDCP PDUs are lost because those PDCP PDUs that have not been received and which do not fit in the new small window will not be retransmitted by the transmitter.
  • Another disadvantage is that the state variables that the transmitter and receiver are using for keeping track of the current HFN (e.g., RX HFN and TX HFN in conventional LTE) may have a small risk of becoming out-of-sync between each other after the handover. This can happen if the PDCP receiver has failed to receive a certain number of PDCP PDUs in sequence which has caused the RX HFN not to be updated, while the transmitter has updated the TX HFN for the same SN used in the smaller window. The only way to recover from this failure is to trigger a radio link failure (RLF) and setup a new RRC connection.
  • RLF radio link failure
  • a user equipment When a user equipment (UE) performs handover from a source base station using SN length M to a target base station using SN length N (that is different from M), the UE and the network may ensure that the PDCP SN size can be updated to the correct length.
  • UE user equipment
  • the embodiments described herein include methods of decrementing the PDCP SN size.
  • the PDCP bearer may be re-established as follows: (1) the receiver processes all PDCP PDUs already received from the source node/cell and which are waiting in the receiver PDCP window, and it forwards these PDUs to higher layers; (2) the receiver sends, if requested, a status report back to the transmitter indicating the missing PDCP PDUs; (3) the PDCP state variables are reset to their initial values; and (4) the transmitter retransmits the payload of all PDCP PDUs for which it has not got a confirmation from lower layers of successful reception and for which it has not got confirmation of successful reception in a PDCP status report.
  • An advantage of particular embodiments is that packet losses may be avoided when the length of the PDCP SN is decreased at handover. Particular embodiments also ensure that the PDCP re-establishment procedure performed at handover can be done without the risk of the Hyper Frame Number (HFN) values becoming out-of-sync between the transmitter and the receiver, which would otherwise lead to radio link failure (RLF).
  • HFN Hyper Frame Number
  • RLF radio link failure
  • a non-limiting term "UE” is used.
  • the UE herein can be any type of wireless device capable of communicating with network node or another UE over radio signals.
  • the UE may also be radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), a sensor equipped with UE, iPAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE) etc.
  • the UE may also be referred to as a wireless device.
  • network node can be any kind of network node which may comprise of a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., MME, SON node, a coordinating node, positioning node (e.g. SMLC, E-SMLC, etc.), MDT node, etc.), or even an external node (e.g., 3rd party node, a node external to the current network), etc.
  • a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (R
  • LTE and NR are used throughout this disclosure as an example cellular system, but the ideas presented herein may apply to other wireless communication systems as well.
  • FIGURE 3 is a block diagram illustrating an example wireless network, according to a particular embodiment.
  • Wireless network 100 includes one or more wireless devices 110 (such as mobile phones, smart phones, laptop computers, tablet computers, MTC devices, or any other devices that can provide wireless communication) and a plurality of network nodes 120 (such as base stations, eNodeBs, gNBs, etc.).
  • Network node 120 serves coverage area 115 (also referred to as cell 115).
  • wireless devices 110 that are within coverage of radio network node 120 (e.g., within cell 115 served by network node 120) communicate with radio network node 120 by transmitting and receiving wireless signals 130.
  • wireless devices 110 and network node 120 may communicate wireless signals 130 containing voice traffic, data traffic, and/or control signals.
  • a network node 120 communicating voice traffic, data traffic, and/or control signals to wireless device 110 may be referred to as a serving network node 120 for the wireless device 110.
  • Wireless signals 130 may include both downlink transmissions (from radio network node 120 to wireless devices 110) and uplink transmissions (from wireless devices 110 to radio network node 120).
  • Wireless signals 130 may include data encapsulated in one or more protocols.
  • wireless signals 130 may include data encapsulated using PDCP 135.
  • Each radio network element e.g., wireless device 110, network node 120, etc.
  • PDCP parameters such as the PDCP SN
  • the PDCP transmitter and PDCP receiver may perform a re-establishment procedure to account for a decreased SN length. More detailed examples are described with respect to FIGURES 4 and 7.
  • wireless device 110 may be referred to by the non-limiting term "UE.”
  • a UE may include any type of wireless device capable of communicating with a network node or another UE over radio signals.
  • the UE may comprise radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), a sensor equipped with UE, iPAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc.
  • D2D device to device
  • M2M machine to machine communication
  • iPAD machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc.
  • LEE laptop embedded equipped
  • LME laptop mounted equipment
  • CPE Customer Premises Equipment
  • network node 120 may include any type of network node such as a base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNB, multi-RAT base station, Multi- cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., MME, SON node, a coordinating node, etc.), or even an external node (e.g., 3rd party node, a node external to the current network), etc.
  • a core network node e.g., MME, SON node, a coordinating node, etc.
  • an external node e.g., 3rd party node, a node external to the current network
  • Each network node 120 may have a single transmitter or multiple transmitters for transmitting wireless signals 130 to wireless devices 110.
  • network node 120 may comprise a multi-input multi-output (MIMO) system.
  • each wireless device 110 may have a single receiver or multiple receivers for receiving signals 130 from network nodes 120.
  • MIMO multi-input multi-output
  • each network node 120 may use any suitable radio access technology, such as long term evolution (LTE), LTE-Advanced, NR, UMTS, HSPA, GSM, cdma2000, WiMax, WiFi, and/or other suitable radio access technology.
  • Wireless network 100 may include any suitable combination of one or more radio access technologies. For purposes of example, various embodiments may be described within the context of certain radio access technologies. However, the scope of the disclosure is not limited to the examples and other embodiments could use different radio access technologies.
  • a wireless network may include one or more wireless devices and one or more different types of network nodes capable of communicating with the wireless devices.
  • the network may also include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (such as a landline telephone).
  • a wireless device may include any suitable combination of hardware and/or software.
  • a wireless device such as wireless device 110
  • a network node may include any suitable combination of hardware and/or software.
  • a network node, such as network node 120 may include the components described below with respect to FIGURE 9A.
  • the source cell or network node When a handover of a wireless device from one network node to another network node is triggered, the source cell or network node transmits to the target cell or network node all PDCP SDUs for which acknowledgements were not yet received.
  • the PDCP SN length used in the target cell is less than the PDCP SN length used in the source cell, the PDCP transmitter and receiver perform additional steps. Examples methods are illustrated in FIGURES 4-7.
  • FIGURE 4 is a flow diagram of an example method in a PDCP transmitter, according to some embodiments.
  • one or more steps may be performed by components of wireless network 100 described with reference to FIGURE 3.
  • FIGURE 3 Although particular examples may be described with respect to a network node or a wireless device, the embodiments described herein may be performed by a network node, a wireless device, or any other suitable radio network node.
  • the method begins at step 1, where at PDCP re-establishment the PDCP transmitter resets all PDCP state variables to their initial values and applies the new ciphering key. For example, after handover of wireless device 110 from network node 120a to network node 120b, network node 120b may set Next_PDCP_TX_SN to 0, TX HFN to 0, and set the new smaller size of the PDCP transmission window.
  • the PDCP transmitter applies the ciphering algorithm and key provided by upper layers during the re-establishment procedure. For example, network node 120b may apply ciphering using a newly received algorithm and/or key.
  • the PDCP transmitter re-transmits the payload of all PDCP PDUs (PDCP SDUs) for which it has not received confirmation that they have not been received by the receiver. The retransmission is done as if these PDCP PDUs are new PDUs (i.e., the transmitter adds new/updated PDCP headers, and as a payload, it puts the PDCP SDUs which the transmitter decided to re-transmit).
  • network node 120b may at step 3.1 perform ciphering of the PDCP SDU using the new Next_PDCP_TX_SN and TX HFN, at step 3.2 assign the new SN to the PDCP PDU and submit the resulting PDCP data PDU to lower layer, and at step 3.3 increment the Next_PDCP_TX_SN and TX HFN to the next subsequent SN.
  • the PDCP transmitter continues transmission of any new PDCP PDUs in the normal manner.
  • network node 120b transmits an new PDCP PDUs to wireless device 110 using the new PDCP parameters.
  • FIGURE 5 is a flow diagram of an example method in a PDCP receiver, according to some embodiments.
  • one or more steps may be performed by components of wireless network 100 described with reference to FIGURE 3.
  • FIGURE 3 Although particular examples may be described with respect to a network node or a wireless device, the embodiments described herein may be performed by a network node, a wireless device, or any other suitable radio network node.
  • the method begins at step 1, where at PDCP re-establishment the PDCP receiver submits to higher layers all PDCP SDUs that it has already received, but that are waiting in the reception window because there are missing PDCP PDUs that have not yet been received and that come before the PDUs stored in the reception window.
  • network node 120b may, if not done already, perform deciphering of the associated PDCP SDU using the currently assigned COUNT value and submit the resulting PDCP data SDU to higher layers in current sequence number order.
  • the PDCP receiver resets all PDCP state variables to their initial values. For example, network node 120b may set Next_PDCP_RX_SN to 0, RX HFN to 0, Last submitted PDCP RX SN to Maximum PDCP SN, and set the new smaller size of the PDCP transmission window.
  • the PDCP receiver applies the new ciphering key.
  • network node 120b may apply a new ciphering algorithm and/or key.
  • the PDCP receiver continues to receive new PDCP PDUs as in normal reception.
  • the PDCP receiver may modify the FMS.
  • the FMS length is the same as the PDCP SN length.
  • the receiver is not able to indicate the same range of PDCP PDUs SN.
  • the FMS format is updated in some embodiments.
  • the updated FMS format may be used (if indicated by the network) to provide a status report of those PDCP PDUs which were not received from the source node/cell.
  • the network may send a reconfiguration request to the wireless device, triggering the wireless device to send a status report using the updated FMS format.
  • the reconfiguration request may comprise an explicit reconfiguration message.
  • the explicit reconfiguration message may be a handover reconfiguration message that includes, for example, the PDCP SN length or other parameters that are reconfigured for the target node/cell.
  • the reconfiguration message may comprise an existing message normally exchanged during the handover process that triggers the reconfiguration.
  • the updated FMS format is such that it facilitates uniquely identifying the PDCP PDUs that are missing.
  • the FMS contains the COUNT value of the first missing PDU SN which was not received from the source cell/node.
  • Another embodiment uses the same number of bits as the PDCP SN length prior to the reconfiguration.
  • the UE may continue using the FMS as specified with the same number of bits as the new (reduced) PDCP SN length. In other embodiments it may use the complete COUNT.
  • the transmitter may use the status report which would include the new FMS format to identify missing PDUs.
  • FIGURE 6 is another flow diagram of an example method in a PDCP transmitter, according to some embodiments.
  • one or more steps of method 600 may be performed by components (e.g., network node 120, wireless device 110) of wireless network 100 described with reference to FIGURE 3.
  • components e.g., network node 120, wireless device 110
  • FIGURE 3 may be described with respect to a network node or a wireless device, the embodiments described herein may be performed by a network node, a wireless device, or any other suitable radio network node.
  • a PDCP transmitter performs a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell.
  • network node 120a may handover wireless device 110 from cell 115a served by network node 120a to cell 115b served by network node 120b.
  • Cell 115b may have a smaller PDCP SN than cell 115a.
  • network node 120a Before the handover, network node 120a has a PDCP connection with wireless device 110.
  • Network node 120a includes a PDCP transmitter for transmitting PDCP PDUs to wireless device 110 and a PDCP receiver for receiving PDCP PDUs from wireless device 110.
  • Wireless device 110 includes a PDCP transmitter for transmitting PDCP PDUs to network node 120a and a PDCP receiver for receiving PDCP PDUs from network node 120a.
  • network node 120b has a PDCP connection with wireless device 110.
  • Network node 120b includes a PDCP transmitter for transmitting PDCP PDUs to wireless device 110 and a PDCP receiver for receiving PDCP PDUs from wireless device 110.
  • Wireless device 110 includes a PDCP transmitter for transmitting PDCP PDUs to network node 120b and a PDCP receiver for receiving PDCP PDUs from network node 120b.
  • An example of step 612 with respect to network node 120b includes network node 120b performing a handover of wireless device 110 from network node 120a.
  • network node 120b may receive instructions and data from network node 120a.
  • Part of the data may include unacknowledged PDCP PDUs and PDCP state variables (e.g., Next_PDCP_TX_SN, TX_HFN, etc.) from network node 120a.
  • step 612 with respect to wireless device 110 includes wireless device 110 determining or being instructed to switch to cell 115b.
  • the PDCP transmitter resets PDCP state variables to initial values.
  • the PDCP transmitter of network node 120b may initialize its PDCP state variables (e.g., set Next PDCP TX SN to 0, TX HFN to 0, etc.).
  • the PDCP transmitter of wireless device 110 may initialize its PDCP state variables (e.g., set Next PDCP TX SN to 0, TX HFN to 0, etc.).
  • the PDCP transmitter for all PDCP PDUs for which it has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generates new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs.
  • network node 120b may have one or more PDCP PDUs for which is has not received receipt confirmation (acknowledgement) from wireless device 110. Instead of waiting for confirmation, or re-transmitting the existing unconfirmed PDUs, network node 120b generates new PDCP PDUs using the existing PDU payloads but attaching headers based on the newly reset PDCP variables (e.g., starting with the reset variables and incrementing the values for each of the one or more unconfirmed PDUs).
  • wireless device 110 may have one more PDCP PDUs for which is has not received receipt confirmation (acknowledgement) from network node 120a. Instead of waiting for confirmation, or re-transmitting the existing unconfirmed PDUs to network node 120b, wireless device generates new PDCP PDUs using the existing PDU payloads but attaching headers based on the newly reset PDCP variables.
  • the PDCP transmitter transmits the new PDCP PDUs.
  • the PDCP transmitter of network node 120b may transmit the new PDCP PDUs generated at step 616 to wireless device 110.
  • the PDCP transmitter of wireless device 110 may transmit the new PDCP PDUs generated at step 616 to network node 120b.
  • FIGURE 6 Additionally, one or more steps in method 300 may be performed in parallel or in any suitable order.
  • FIGURE 7 is another flow diagram of an example method in a PDCP receiver, according to some embodiments.
  • one or more steps of method 700 may be performed by components (e.g., network node 120, wireless device 110) of wireless network 100 described with reference to FIGURE 3.
  • components e.g., network node 120, wireless device 110
  • FIGURE 7 is another flow diagram of an example method in a PDCP receiver, according to some embodiments.
  • one or more steps of method 700 may be performed by components (e.g., network node 120, wireless device 110) of wireless network 100 described with reference to FIGURE 3.
  • components e.g., network node 120, wireless device 110
  • the embodiments described herein may be performed by a network node, a wireless device, or any other suitable radio network node.
  • a PDCP receiver performs a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell.
  • network node 120a may handover wireless device 110 from cell 115a served by network node 120a to cell 115b served by network node 120b.
  • Cell 115b may have a smaller PDCP SN than cell 115a.
  • network node 120a has a PDCP connection with wireless device 110.
  • Network node 120a includes a PDCP transmitter for transmitting PDCP PDUs to wireless device 110 and a PDCP receiver for receiving PDCP PDUs from wireless device 110.
  • Wireless device 110 includes a PDCP transmitter for transmitting PDCP PDUs to network node 120a and a PDCP receiver for receiving PDCP PDUs from network node 120a.
  • network node 120b has a PDCP connection with wireless device 110.
  • Network node 120b includes a PDCP transmitter for transmitting PDCP PDUs to wireless device 110 and a PDCP receiver for receiving PDCP PDUs from wireless device 110.
  • Wireless device 110 includes a PDCP transmitter for transmitting PDCP PDUs to network node 120b and a PDCP receiver for receiving PDCP PDUs from network node 120b.
  • step 712 with respect to network node 120b includes network node 120b performing a handover of wireless device 110 from network node 120a.
  • network node 120b may receive instructions and data from network node 120a.
  • Part of the data may include PDCP PDUs and PDCP state variables (e.g., Next PDCP RX SN, RX HFN, Last submitted PDCP RX SN, etc.) from network node 120a.
  • step 712 with respect to wireless device 110 includes wireless device 110 determining or being instructed to switch to cell 115b.
  • the PDCP transmitter submits to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer.
  • network node 120b may have one or more PDCP PDUs which it has not yet submitted to a higher protocol layer (e.g., RRC).
  • Network node 120b may submit these PDCP PDUs to the higher protocol layer without further waiting (e.g., even if the PDUs are out of order because of a missing SN).
  • wireless device 110 may have one or more PDCP PDUs which it has not yet submitted to a higher protocol layer (e.g., RRC). Wireless device 110 may submit these PDCP PDUs to the higher protocol layer at step 714.
  • a higher protocol layer e.g., RRC
  • the PDCP receiver resets its PDCP state variables to initial values. For example the PDCP receiver of network node 120 and/or wireless device 110 may reset Next PDCP RX SN to 0, RX HFN to 0, and Last submitted PDCP RX SN to Maximum PDCP SN.
  • FIGURE 8A is a block diagram illustrating an example embodiment of a wireless device.
  • the wireless device is an example of the wireless devices 110 illustrated in FIGURE 3.
  • the wireless device is capable of performing a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell.
  • the wireless device is capable of: resetting PDCP state variables to initial values; for all PDCP PDUs for which the wireless device has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generating new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmitting the new PDCP PDUs.
  • the wireless device is capable of: submitting to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and resetting PDCP state variables to initial values.
  • a mobile phone a smart phone, a PDA (Personal Digital Assistant), a portable computer (e.g., laptop, tablet), a sensor, a modem, a machine type (MTC) device / machine to machine (M2M) device, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, a device-to-device capable device, a B- IoT device, or any other device that can provide wireless communication.
  • the wireless device includes transceiver 810, processing circuitry 820, memory 830, and power source 840.
  • transceiver 810 facilitates transmitting wireless signals to and receiving wireless signals from wireless network node 120 (e.g., via an antenna), processing circuitry 820 executes instructions to provide some or all of the functionality described herein as provided by the wireless device, and memory 830 stores the instructions executed by processing circuitry 820.
  • Power source 840 supplies electrical power to one or more of the components of wireless device 110, such as transceiver 810, processing circuitry 820, and/or memory 830.
  • Processing circuitry 820 includes any suitable combination of hardware and software implemented in one or more integrated circuits or modules to execute instructions and manipulate data to perform some or all of the described functions of the wireless device.
  • processing circuitry 820 may include, for example, one or more computers, one more programmable logic devices, one or more central processing units (CPUs), one or more microprocessors, one or more applications, and/or other logic, and/or any suitable combination of the preceding.
  • Processing circuitry 820 may include analog and/or digital circuitry configured to perform some or all of the described functions of wireless device 110.
  • processing circuitry 820 may include resistors, capacitors, inductors, transistors, diodes, and/or any other suitable circuit components.
  • Memory 830 is generally operable to store computer executable code and data.
  • Examples of memory 830 include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readable and/or computer-executable memory devices that store information.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • mass storage media e.g., a hard disk
  • removable storage media e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)
  • CD Compact Disk
  • DVD Digital Video Disk
  • Power source 840 is generally operable to supply electrical power to the components of wireless device 110.
  • Power source 840 may include any suitable type of battery, such as lithium-ion, lithium-air, lithium polymer, nickel cadmium, nickel metal hydride, or any other suitable type of battery for supplying power to a wireless device.
  • processing circuitry 820 in communication with transceiver 810 communicates PDCP encapsulated data with network node 120.
  • processing circuitry 820 in communication with transceiver 810 may perform any of the steps described with respect to FIGURES 4-7.
  • Other embodiments of the wireless device may include additional components (beyond those shown in FIGURE 8A) responsible for providing certain aspects of the wireless device's functionality, including any of the functionality described above and/or any additional functionality (including any functionality necessary to support the solution described above).
  • FIGURE 8B is a block diagram illustrating example components of a wireless device 110.
  • the components may include PDCP transmitting module 850 and PDCP receiving module 852.
  • PDCP transmitting module 850 may perform the PDCP transmitting functions of wireless device 110.
  • PDCP transmitting module 850 may perform the steps described with respect to FIGURES 4 and/or 6.
  • PDCP transmitting module 850 may include or be included in processing circuitry 820.
  • PDCP receiving module 852 may perform the PDCP receiving functions of wireless device 110. For example, PDCP receiving module 852 may perform the steps described with respect to FIGURES 5 and/or 7. In certain embodiments, PDCP receiving module 852 may include or be included in processing circuitry 820.
  • FIGURE 9A is a block diagram illustrating an example embodiment of a network node.
  • the network node is capable of performing a handover from a first cell to a second cell where a PDCP SN for the second cell is smaller than a PDCP SN for the first cell.
  • the network node is capable of: resetting PDCP state variables to initial values; for all PDCP PDUs for which the network node has not received confirmation of receipt from a PDCP receiver (unconfirmed PDCP PDUs), generating new PDCP PDUs by applying new PDCP headers based on the reset PDCP state variables to the payload of the unconfirmed PDCP PDUs; and transmitting the new PDCP PDUs.
  • the network node is capable of: submitting to a higher protocol layer all PDCP PDUs that were received before the handover but not yet submitted to the higher protocol layer; and resetting PDCP state variables to initial values.
  • Network node 120 can be an eNodeB, a nodeB, a base station, a wireless access point (e.g., a Wi-Fi access point), a low power node, a base transceiver station (BTS), a transmission point or node, a remote RF unit (RRU), a remote radio head (RRH), or other radio access node.
  • Network node 120 includes processing circuitry 920 (e.g., CPUs, ASICs, FPGAs, etc.), at least one memory 930, at least one network interface 940, and one or more radio units that each include on or more transceivers 910 coupled to one or more antennas.
  • Transceiver 910 facilitates transmitting wireless signals to and receiving wireless signals from a wireless device, such as wireless devices 110 (e.g., via an antenna); processing circuitry 920 executes instructions to provide some or all of the functionality described above as being provided by a network node 120; memory 930 stores the instructions executed by processing circuitry 920; and network interface 940 communicates signals to backend network components, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), controller, and/or other network nodes 120.
  • PSTN Public Switched Telephone Network
  • Processing circuitry 920 and memory 930 can be of the same types as described with respect to processing circuitry 820 and memory 830 of FIGURE 8 A above.
  • network interface 940 is communicatively coupled to processing circuitry 920 and refers to any suitable device operable to receive input for network node 120, send output from network node 120, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding.
  • Network interface 940 includes appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate through a network.
  • processing circuitry 920 in communication with transceiver 910 communicates PDCP encapsulated data with wireless device 110.
  • a portion of the network node 120 may be implemented as virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • some or all of the functions executed by processing circuitry 920 of network node 120 are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by processing circuitry 920.
  • network node 120 include additional components (beyond those shown in FIGURE 9 A) responsible for providing certain aspects of the network node's functionality, including any of the functionality described above and/or any additional functionality (including any functionality necessary to support the solution described above).
  • the various different types of network nodes may include components having the same physical hardware but configured (e.g., via programming) to support different radio access technologies, or may represent partly or entirely different physical components.
  • FIGURE 9B is a block diagram illustrating example components of a network node 120.
  • the components may include PDCP transmitting module 950 and PDCP receiving module 952.
  • PDCP transmitting module 950 may perform the PDCP transmitting functions of network node 120. For example, PDCP transmitting module 950 may perform the steps described with respect to FIGURES 4 and/or 6. In certain embodiments, PDCP transmitting module 950 may include or be included in processing circuitry 920.
  • PDCP receiving module 952 may perform the PDCP receiving functions of network node 120. For example, PDCP receiving module 952 may perform the steps described with respect to FIGURES 5 and/or 7. In certain embodiments, PDCP receiving module 952 may include or be included in processing circuitry 920.
  • Some embodiments of the disclosure may provide one or more technical advantages. Some embodiments may benefit from some, none, or all of these advantages. Other technical advantages may be readily ascertained by one of ordinary skill in the art.

Landscapes

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

Abstract

Selon certains modes de réalisation, un procédé destiné à être utilisé dans une entité de transmission de protocole de convergence de données de paquets (PDCP) comprend : la réalisation d'un transfert d'une première cellule à une seconde cellule dans lequel un numéro de séquence (SN) PDCP pour la seconde cellule est plus petit que la première cellule; la réinitialisation des variables d'état PDCP; pour toutes les unités de données (PDU) de protocole PDCP pour lesquelles l'émetteur PDCP n'a pas reçu de confirmation de réception à partir d'un récepteur PDCP (PDU de PDCP non confirmées), la génération de nouvelles PDU de PDCP par l'application de nouveaux en-têtes de PDCP sur la base des variables d'état de PDCP de réinitialisation à la charge utile des PDU de PDCP non confirmées; et la transmission des nouvelles PDU de PDCP. Certains modes de réalisation comprennent des procédés destinés à être utilisés dans une entité de réception PDCP comprenant : la soumission à une couche de protocole supérieure de toutes les PDU de PDCP qui ont été reçues avant transfert mais pas encore soumises à la couche de protocole supérieure; la réinitialisation des variables d'état PDCP.
PCT/IB2018/050088 2017-01-06 2018-01-05 Changement de numéro de séquence de protocole de convergence de données de paquets sans perte WO2018127842A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762443438P 2017-01-06 2017-01-06
US62/443,438 2017-01-06

Publications (1)

Publication Number Publication Date
WO2018127842A1 true WO2018127842A1 (fr) 2018-07-12

Family

ID=61022394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2018/050088 WO2018127842A1 (fr) 2017-01-06 2018-01-05 Changement de numéro de séquence de protocole de convergence de données de paquets sans perte

Country Status (1)

Country Link
WO (1) WO2018127842A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020055209A1 (fr) * 2018-09-14 2020-03-19 Samsung Electronics Co., Ltd. Procédé et appareil pour une transmission de paquet dans un système de communication sans fil
US11765627B2 (en) 2019-05-29 2023-09-19 Google Llc Sequence number transfer for radio bearers

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL: "Limitation of PDCP SN and FMS-fields", 3GPP DRAFT; R2-122651 LIMITATION OF PDCP SN AND FMS-FIELDS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20120521 - 20120525, 15 May 2012 (2012-05-15), XP050607347 *
HUAWEI ET AL: "Handover related issue for the extended PDCP SN", vol. RAN WG2, no. Qingdao, China; 20120813 - 20120817, 7 August 2012 (2012-08-07), XP050665605, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_79/Docs/> [retrieved on 20120807] *
LG ELECTRONICS: "Correction to SN management for DRBs mapped on UM", 3GPP DRAFT; R2-081595 [REL-8] PROPOSED CR TO 25.323 ON CORRECTION TO SN MANAGEMENT FOR UM, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. ShenZhen, China; 20080404, 25 March 2008 (2008-03-25), XP050603674 *
MEDIATEK INC: "Impact on handover with PDCP SN change", vol. RAN WG2, no. Qingdao, China; 20120813 - 20120817, 7 August 2012 (2012-08-07), XP050665624, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_79/Docs/> [retrieved on 20120807] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020055209A1 (fr) * 2018-09-14 2020-03-19 Samsung Electronics Co., Ltd. Procédé et appareil pour une transmission de paquet dans un système de communication sans fil
US11765627B2 (en) 2019-05-29 2023-09-19 Google Llc Sequence number transfer for radio bearers

Similar Documents

Publication Publication Date Title
RU2721331C1 (ru) Повторное отображение потока qos 5g в несущий радиоканал
EP3469830B1 (fr) Procédé de réalisation d&#39;un rétablissement d&#39;une entité pdcp associée à une entité rlc um dans un système de communication sans fil, et dispositif associé
AU2019252287B2 (en) Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer
US11838978B2 (en) NR PDCP preservation upon RRC resume/suspend
EP3614736B1 (fr) Procédé et appareil de gestion de transferts
CN111373809B (zh) 上行信号发送方法、上行信号接收方法、装置和系统
CN108282292B (zh) 用于处理数据的方法、发送端和接收端
US10448447B2 (en) Device and method for handling a bearer type change for a radio bearer
US10582556B2 (en) Device and method for handling a bearer type change
WO2022110168A1 (fr) Procédé de configuration de communication et appareil de communication
US20210297915A1 (en) Packet data convergence protocol (pdcp) protocol data unit (pdu) handling for mobility between new radio access technology and long term evolution
CN111713057A (zh) 用于处置通信的传送装置和其中执行的方法
WO2018127842A1 (fr) Changement de numéro de séquence de protocole de convergence de données de paquets sans perte
US20230362707A1 (en) Wireless communication method and device
CN113115360B (zh) 无线通信方法、通信设备、芯片和通信系统
US10455472B2 (en) Device and method of handling data transmissions in a wireless communication system
EP3442265A1 (fr) Dispositif et procédé pour gérer une opération de protocole de convergence de données par paquets
TW201911947A (zh) 處理一交遞的裝置及方法
CN111654360B (zh) 一种非激活态的切换处理方法及通信设备
CN113556792A (zh) 状态报告传输方法、终端设备和网络设备
WO2022052104A1 (fr) Procédés et appareils d&#39;optimisation d&#39;une interruption ho de liaison montante
JP2024519200A (ja) ５ｇｓからｅｐｃの再選択のセキュリティハンドリング
CN117322025A (zh) 5gs至epc重选的安全性处置
CN115701172A (zh) 分组数据汇聚协议状态报告发送方法、设备及装置
CN115315982A (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: 18701230

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18701230

Country of ref document: EP

Kind code of ref document: A1