EP4226596A1 - Temporisateur de rejet de pdcp de groupe pour des services à faible latence - Google Patents

Temporisateur de rejet de pdcp de groupe pour des services à faible latence

Info

Publication number
EP4226596A1
EP4226596A1 EP21794662.3A EP21794662A EP4226596A1 EP 4226596 A1 EP4226596 A1 EP 4226596A1 EP 21794662 A EP21794662 A EP 21794662A EP 4226596 A1 EP4226596 A1 EP 4226596A1
Authority
EP
European Patent Office
Prior art keywords
layer
sdus
discard timer
discard
group
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP21794662.3A
Other languages
German (de)
English (en)
Inventor
Du Ho Kang
Jose Luis Pradas
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4226596A1 publication Critical patent/EP4226596A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • 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

Definitions

  • the present disclosure generally relates to wireless communication networks, and particularly relates to techniques for ensuring timely deliver by a wireless network of data packets generated by latency-sensitive applications such as extended reality (XR) and cloud gaming.
  • XR extended reality
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • eMBB enhanced mobile broadband
  • MTC machine type communications
  • URLLC ultra-reliable low latency communications
  • D2D side-link device-to-device
  • FIG. 1 illustrates an exemplary high-level view of the 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198.
  • NG-RAN 199 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively.
  • the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150.
  • each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • NG-RAN 199 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • NG, Xn, Fl the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signaling transport.
  • the NG RAN logical nodes shown in Figure 1 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU).
  • gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130.
  • CUs e.g., gNB-CU 110
  • CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs.
  • Each DU is a logical node that hosts lower-layer protocols and can include, depending on the functional split, various subsets of the gNB functions.
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry.
  • central unit and “centralized unit” are used interchangeably herein, as are the terms “distributed unit” and “decentralized unit.”
  • a gNB-CU connects to gNB-DUs over respective Fl logical interfaces, such as interfaces 122 and 132 shown in Figure 1.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.
  • FIG. 2 shows a high-level view of an exemplary 5G network architecture, including a Next Generation Radio Access Network (NG-RAN) 299 and a 5G Core (5GC) 298.
  • NG-RAN 299 can include gNBs 210 e.g., 210a, b) and ng-eNBs 220 (e.g., 220a, b) that are interconnected with each other via respective Xn interfaces.
  • gNBs 210 e.g., 210a, b
  • ng-eNBs 220 e.g., 220a, b
  • the gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 298, more specifically to the AMF (Access and Mobility Management Function) 230 (e.g., AMFs 230a, b) via respective NG-C interfaces and to the UPF (User Plane Function) 240 (e.g., UPFs 240a, b) via respective NG-U interfaces.
  • the AMFs 230a, b can communicate with one or more policy control functions (PCFs, e.g., PCFs 250a, b) and network exposure functions (NEFs, e.g., NEFs 260a, b).
  • PCFs policy control functions
  • NEFs network exposure functions
  • Each of the gNBs 210 can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • Each of ng-eNBs 220 can support the fourth-generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs 220 connect to the 5GC via the NG interface.
  • Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, such as cells 21 la-b and 221a-b shown in Figure 2.
  • a UE 205 can communicate with the gNB or ng-eNB serving that particular cell via the NR or LTE radio interface, respectively.
  • Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.
  • NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the UL.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S-OFDM DFT-spread OFDM
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell.
  • SCS 15-kHz OFDM sub-carrier spacing
  • NR SCS can range from 15 to 240 kHz, with even greater SCS considered for future NR releases.
  • NR networks In addition to providing coverage via cells as in LTE, NR networks also provide coverage via “beams.”
  • a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
  • RS network-transmitted reference signal
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (310), a gNB (320), and an AMF (320), such as those shown in Figures 1-2.
  • the Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP.
  • the PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP.
  • PDCP provides header compression and retransmission for UP data.
  • IP Internet protocol
  • SDU service data units
  • PDU protocol data units
  • the RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH).
  • LCH logical channels
  • RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. If RLC receives a discard indication from associated with a PDCP PDU, it will discard the corresponding RLC SDU (or any segment thereof) if it has not been sent to lower layers.
  • the MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side).
  • the PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
  • the Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS). This includes mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets.
  • QoS quality-of-service
  • DRBs Data Radio Bearers
  • QFI QoS flow identifiers
  • the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control.
  • the RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF.
  • RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN.
  • RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs.
  • SI system information
  • SRBs Signaling Radio Bearers
  • RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs.
  • CA carrier aggregation
  • DC dual -connectivity
  • RRC also performs various security functions such as key management.
  • RRC IDLE state After a UE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE after the connection with the network is released.
  • RRC IDLE state the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX active periods also referred to as “DRX On durations”
  • an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB.
  • NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB.
  • RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.
  • XR Extended Reality
  • Cloud Gaming are some of the most important 5G media applications under consideration in the industry.
  • XR is an umbrella term that refers to all real- and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes exemplary forms such as Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR), as well as various other types that span or sit between these examples.
  • AR Augmented Reality
  • MR Mixed Reality
  • VR Virtual Reality
  • the term “XR” also refers to cloud gaming and related applications.
  • Edge Computing is generally viewed as an important network architecture enabler for XR.
  • EC facilitates deployment of cloud computing capabilities and service environments close to the cellular radio access network (RAN). It can provide benefits such as lower latency and higher bandwidth for user-plane (UP, e.g., data) traffic, as well as reduced backhaul traffic to the 5G core network (5GC).
  • UP user-plane
  • 5GC 5G core network
  • 3GPP is also studying prospects for several new services on application architecture for enabling Edge Applications, as described further in 3 GPP TR 23.758. Edge Applications are expected to take advantage of the low latencies enabled by 5G and EC network architecture to reduce the end-to-end application-level latencies.
  • the 5G NR radio interface is designed to support applications demanding high throughput and low latency in line with the requirements of XR and Edge Applications in NR networks.
  • XR applications generate periodic traffic with variable size.
  • the packet may be transmitted as a single PDU or may be segmented several PDUs before transmission.
  • One application packet could, for instance, correspond to one or several IP packets.
  • XR application PDUs may have time constraints, such that one or a set of application PDUs (referred to generically as “application PDUs”) may need to reach the receiver within a certain period of time, e.g., a maximum allowed latency. If not received by this time, the application PDUs are useless and can be discarded.
  • application PDUs referred to generically as “application PDUs”
  • the NR PDCP layer currently uses a discard timer
  • PDCP has no knowledge about how PDCP SDUs (or IP PDUs) map to the application PDUs that need to be delivered within the maximum allowed latency. This can cause various problems such as late delivery of XR application PDUs and waste of network resources delivering application PDUs that ultimately will be discarded by the receiver.
  • Embodiments of the present disclosure provide specific improvements to communication between UEs and network nodes in a wireless network, such as by providing, enabling, and/or facilitating solutions to overcome exemplary problems summarized above and described in more detail below.
  • Embodiments include methods (e.g., procedures) for communicating data using a protocol stack that includes a first layer comprising at least one group discard timer.
  • these exemplary methods can be performed by a UE (e.g., wireless device) or a network node (e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof) in a wireless network (e.g., E-UTRAN, NG-RAN).
  • a UE e.g., wireless device
  • a network node e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof
  • a wireless network e.g., E-UTRAN, NG-RAN.
  • These exemplary methods can include receiving, at the first layer from a higher layer of the protocol stack, a first plurality of SDUs associated with a common maximum latency requirement. These exemplary methods can also include, based on the common maximum latency requirement, initiating at least one group discard timer associated with the first plurality of SDUs. These exemplary methods can also include, upon expiration of the at least one discard timer, discarding the first plurality of SDUs associated with common latency requirement.
  • the first plurality of SDUs is associated with one or more of the following: one or more higher-layer PDUs that have a common maximum latency requirement; a common group discard time; and a single data flow (e.g., an XR data flow).
  • the first plurality of SDUs comprises a first SDU and a second SDU received a duration after the first SDU.
  • the initiating operations can include initiating a first discard timer with a first value upon receipt of the first SDU.
  • an indication of the first value can be received from the higher layer in association with the first SDU.
  • the first discard timer is associated with the first and second SDUs.
  • the initiating operations can also include initiating a second discard timers with a second value upon receipt of the second SDU.
  • the second value can be the first value minus the duration.
  • the discarding operations can include discarding the first SDU upon expiration of the first discard timer and discarding the second SDU upon expiration of the second discard timer.
  • the initiating operations can also include refraining from initiating a second discard timer upon receipt of the second SDU.
  • the discarding operations can include discarding the first plurality of SDUs upon expiration of the first discard timer.
  • the first plurality of SDUs can be associated with a data flow comprising a plurality of higher-layer PDUs.
  • the initiating operations can also include refraining from initiating further discard timers upon receipt, after the second SDU, of further SDUs associated with the data flow.
  • these exemplary methods can also include forming the first plurality of SDUs into a second plurality of first-layer PDUs; sending the second plurality of first- layer PDUs to a lower layer of the protocol stack; and, upon expiration of the at least one group discard timer, sending to the lower layer respective discard indications associated with the second plurality of first-layer PDUs.
  • these exemplary methods can also include determining that the first plurality of SDU are associated with a common maximum latency requirement based on one of the following:
  • the first layer can be a PDCP layer and the higher layer can be an application layer, an IP layer, or an SDAP layer.
  • the lower layer can be an RLC layer.
  • the node can be a UE.
  • these exemplary methods can also include receiving, from a network node in the wireless network, a discard timer configuration including one or more of the following:
  • initiating the at least one group discard timer and discarding the first plurality of SDUs can be based on the received discard timer configuration.
  • the node can be a network node in a wireless network.
  • these exemplary methods can also include sending, to a UE, a discard timer configuration including one or more of the above-mentioned items.
  • these exemplary methods can also include determining remaining durations of validity for the respective first plurality of SDUs based on the following for one or more higher-layer PDUs associated with the first plurality of SDUs: a maximum latency requirement, and a time of arrival in the wireless network. Additionally, initiating the at least one group discard timer can be based on the remaining durations of validity.
  • determining remaining durations of validity for the respective first plurality of SDUs can be based on one of the following:
  • UEs e.g., wireless devices
  • network nodes e.g., base stations, eNBs, gNBs, ng-eNBs, etc., or components thereof
  • Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such UEs or network nodes to perform operations corresponding to any of the exemplary methods described herein.
  • Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.
  • Figure 3 shows an exemplary configuration of NR UP and CP protocol stacks.
  • Figure 4 illustrates a comparison of various characteristics or requirements between XR and other 5G applications.
  • Figure 5 illustrates some exemplary traffic characteristics for XR.
  • Figure 6 illustrates some problems that application-layer PDUs can encounter between a source and a destination.
  • Figures 7A-B show a flow diagram of an exemplary method for a node (e.g., UE, wireless device, base station, eNB, gNB, ng-eNB, etc.) in a wireless network (e.g., NG-RAN, E-UTRAN), according to various embodiments of the present disclosure.
  • a node e.g., UE, wireless device, base station, eNB, gNB, ng-eNB, etc.
  • a wireless network e.g., NG-RAN, E-UTRAN
  • Figure 8 shows a block diagram of an exemplary wireless device or UE, according to various embodiments of the present disclosure.
  • Figure 9 shows a block diagram of an exemplary network node, according to various embodiments of the present disclosure.
  • FIG. 10 shows a block diagram of an exemplary network configured to provide over- the-top (OTT) data services between a host computer and a UE, according to various embodiments of the present disclosure.
  • OTT over-the-top
  • Radio Node can be either a radio access node or a wireless device.”
  • a “node” can be a network node or a wireless device.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g, a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point, a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g, a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network
  • base station distributed components e.g., CU and DU
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW Packet Data Network Gateway
  • AMF access and mobility management function
  • AMF access and mobility management function
  • AMF AMF
  • UPF user plane function
  • SCEF Service Capability Exposure Function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (z.e., is served by) a cellular communications network by communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • wireless device examples include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, etc.
  • the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short).
  • Network Node is any node that is either part of the radio access network (e.g, a radio access node or equivalent name discussed above) or of the core network (e.g, a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
  • PDCP has no knowledge about how PDCP SDUs (or IP PDUs) map to the application PDUs that need to be delivered within the maximum allowed latency. This can cause various problems such as late delivery of XR application PDUs and waste of network resources delivering such PDUs that will be ultimately be discarded. This is discussed in more detail below.
  • Figure 4 illustrates a comparison of various characteristics requirements for XR and other 5G applications.
  • Figure 4 shows a comparison of latency, reliability, and bitrate requirements for URLLC, streaming, and EC-based XR.
  • URLLC services have extreme requirements of 1-ms latency and of 10' 5
  • EC-based XR can have relaxed requirements 5-10 ms and 10' 4 reliability.
  • XR services can require a much higher bite rate than either URLLC or streaming, (e.g., due to codec inefficiency).
  • EC -based XR traffic can also be very dynamic, e.g., due to eye/viewport tracking. In general, the traffic can appear to be periodic but with variable file sizes, as illustrated in Figure 5.
  • the packet When an XR application-layer packet enters the Internet, the packet may be transmitted as a single PDU or may be segmented several PDUs before transmission.
  • One application packet could, for instance, correspond to one or several IP packets.
  • XR application PDUs may have a maximum allowed latency of 5-10 ms. If the application PDU(s) is/are not received by this time, the application PDU(s) is/are not of any use and can be discarded.
  • IP packets reach the PDCP layer with a certain jitter that comes from traversing the Internet and the 5GC.
  • the PDCP layer starts a discard timer each time a PDCP SDU is received by higher layers.
  • the NR PDCP layer currently uses a discard timer, PDCP has no knowledge about how PDCP SDUs (or IP PDUs) map to the application PDUs that need to be delivered within the maximum allowed latency.
  • one XR application PDU can be segmented into 5 IP packets.
  • Each IP packet arrives in- or out-of-sequence to the PDCP layer (as a PDCP SDU) at times X+deltal, X+delta2, etc.
  • Each packet will have a discard timer running with a certain time.
  • all 5 PDCP SDUs must be delivered within a defined time budget. If the delay budget for the application packet is consumed, the 5 PDCP SDUs corresponding to the application packet can be discarded regardless of whether the PDCP discard timer is still running.
  • the value of the current PDCP discard timer cannot depend on the number of PDCP SDUs that may correspond to a single application PDU. This is because the number of PDCP SDUs that correspond to a single application PDU may vary among application PDUs. Setting the PDCP discard timer to a fraction of the maximum latency of the application PDU may also impose a fictitious restriction and possibly lead to unnecessary discards. For example, if the maximum latency is 10 ms and PDCP discard timer is set to 2 ms (i.e., 10 ms/5 PDUs), any single PDCP PDU will be discarded 2 ms after it reaches PDCP.
  • all 5 PDCP PDUs are transmitted at the same time after 7 ms from the reception of the first PDCP SDU.
  • all 5 PDPC PDUs could be delivered within the 10-ms latency budget but the 2-ms time would cause unnecessary discard.
  • Figure 6 illustrates certain problems that application-layer PDUs can encounter between a source and a destination.
  • the application (illustrated as a “cloud”) generates one or more first application PDUs at time tO, all of which need to be delivered within the same maximum latency.
  • the application may generate second application PDUs at time tl with a common maximum latency that may be different than the first application PDUs, and/or at a later time than the first application PDUs.
  • These first and second application PDUs may traverse one or more intermediate networks or may be directly connected to a 3GPP network (e.g., 5GC).
  • 3GPP network e.g., 5GC
  • these application PDUs may be adapted (e.g. segmented) by lower-layer protocols to better fit the transmission conditions and/or constraints.
  • Challenges for the gNB PDCP layer include identifying which PDUs are associated with application PDUs (e.g., first or second) having the same maximum latency and which ones need to be delivered first. For example, the first set generated at tO may need to be delivered before the second set generated at tl (or vice versa).
  • the UE needs to receive UL grants to transmit these PDCP SDUs. If the UE does not receive the UL grants in time or the UL grants are not large enough to meet the maximum latency requirement, there may be PDCP SDUs related to the application PDU still pending for transmission. PDCP would attempt to transmit those pending PDCP SDUs even though they are no longer useful to the receiver. Moreover, transmitting those “late” PDCP SDUs may actually delay other PDCP SDUs related to a second application PDU coming after the first application PDU.
  • the current PDCP timer is not suitable for handling XR services.
  • An XR application may produce one or more application PDUs that must be delivered within a maximum latency (or delay budget).
  • the application and/or lower layers may segment and/or concatenate these application PDUs.
  • PDCP receives IP PDUs (or other protocol, if used) from upper layers, but has no information about how these IP PDUs (PDCP SDUs) map to the application PDUs having the maximum latency. As such, the PDCP layer cannot properly configure the single discard timer for each PDCP SDU.
  • PDCP SDUs subsequent application PDUs
  • subsequent PDCP SDUs should not be transmitted either, because doing so wastes network and UE resources.
  • SDU discard timer independent of other SDUs allows these subsequent SDUs to stay in the PDCP buffer even though they are unnecessary from an application perspective.
  • embodiments of the present disclosure provide flexible and efficient techniques that provide information to the PDCP layer about which PDCP SDUs are associated with a single application PDU that needs to be delivered according to a maximum latency requirement. Such techniques also provide different conditions for a transmitting PDCP entity to trigger a group discard timer for a set of PDCP SDUs associated with one or more applicationlayer PDUs having a common maximum latency requirement. Furthermore, when the group discard timer expires, the transmitting PDCP entity discards the set of PDCP SDUs and corresponding PDCP PDUs associated with the application PDU and provides a discard indication to lower layers with respect to all corresponding PDCP PDUs.
  • Embodiments of the present disclosure can provide various benefits and/or advantages. For example, by allowing the network (or UE) to discard a set of packets that are no longer valid for an application, network resources are used more efficiently thereby increasing capacity. Moreover, embodiments can facilitate more efficient resource management (e.g., scheduling) and/or better planning of for delivery of PDCP PDUs within a maximum latency associated with their corresponding application PDUs. This can provide better fulfillment of committed QoS and improvements to quality of experience (QoE) by avoiding unnecessary resource usage and interference caused by unwanted application PDU data.
  • QoE quality of experience
  • different conditions can be used to trigger a group discard timer for a set of PDCP SDUs associated with one or more application-layer PDUs having a common maximum latency requirement. For example, this could be trigger upon reception of a first PDCP SDU identified as being associated with: 1) a set of PDCP SDUs that share a group discard time, and/or 2) one or more application PDUs having a common maximum latency requirement.
  • a UE can be configured by the network (e.g., via RRC) to use a group PDCP discard timer and, when configured, the UE uses the triggering condition above.
  • the network configuration can be responsive to a UE indication of support of PDCP group discard timer.
  • legacy (i.e., non-supporting) UEs would not be configured as such but would continue to use the existing SDU-independent PDCP timer arrangement discussed above. If multiple group discard timer triggering conditions are available, the network can also configure the UE to use a particular one (or more) of the available conditions.
  • the transmitting PDCP entity starts one or more discard timer(s) according to various embodiments.
  • a transmitting PDCP entity can start multiple discard timers (i.e., one for each PDCP SDU) with each timer having a different initial value corresponding to the arrival time of the associated PDCP SDU.
  • a second PDCP SDU may have a shorter discard timer value than a first PDCP SDU that arrived previously, in accordance with the overall latency requirement of the associated application PDU.
  • a transmitting PDCP entity can start one discard timer that will be associated with all PDCP SDUs with a common group discard time or that are associated with one or more application PDUs having a common maximum latency requirement.
  • a transmitting PDCP entity can start one discard timer for the first received PDCP SDU associated with an XR flow comprising multiple application PDUs, and refrain from starting a discard timer for subsequently received PDCP SDUs associated with the same XR flow.
  • These embodiments can be beneficial when subsequently-received application PDUs are dependent on an initial application PDU.
  • a specific example is a P-frame in the context of compressed video.
  • the duration for the timer(s) can be configured by the network, e.g., via RRC.
  • multiple timer durations may be used/configured to differentiate PDCP SDUs in terms of latency requirement. This can be particularly beneficial in the case where multiple discard timers are started using different values, such as in the first option discussed above.
  • the particular duration for a discard timer may be set in various ways, such as the maximum latency requirement for the corresponding packet, an amount of remaining latency budget, etc.
  • the transmitting PDCP entity discards the set of PDCP SDUs and PDCP data PDUs corresponding to the application PDU.
  • each PDCP SDU will be discarded based on expiration of its associated discard timer without affecting or being affected by discard timers associated with other PDCP SDUs.
  • all PDCP SDUs associated with a common group will be discarded upon expiration of the discard timer started upon receipt of the first PDCP SDU.
  • all PDCP SDUs associated with the same XR flow will be discarded upon expiration of the discard timer started upon receipt of the first PDCP SDU.
  • the PDCP layer can provide discard indications to RLC for all PDCP PDUs corresponding to PDCP SDUs discarded based on timer expiration.
  • the network can configure (e.g., via RRC) discarding behavior in the UE, preferably compatible with the discard timer configuration that may also be network- configured, as discussed above.
  • the network may need to comply with specific QoS requirements for a flow.
  • the NG-RAN may obtain certain QoS parameters indicating performance for the flow, such as maximum latency.
  • the NG-RAN may need assistance to identify which PDCP SDUs are associated with which application PDUs. This information can facilitate delivery of all PDCP SDUs within a given delay budget for the application PDU(s) associated with a service.
  • the core network e.g., 5GC
  • the core network can provide a sequence number for each IP PDU (or packet) delivered to the PDCP layer.
  • the sequence number can be the same for all packets associated with a one application PDU or for all packets that have the same maximum latency requirement.
  • the PDCP layer can perform a packet inspection of the incoming packet headers to identify a relevant sequence number. For example, if PDCP SDUs are known to be IP packets, the Sequence Number (SN) and segmentation information can be extracted from each packet to identify if a packet is a segment and, when all the packets are received, the order of that reconstructed packet.
  • SN Sequence Number
  • segmentation information can be extracted from each packet to identify if a packet is a segment and, when all the packets are received, the order of that reconstructed packet.
  • the PDCP layer may be informed of the remaining time left for each incoming IP PDU/PDCP SDU.
  • the remaining time T for PDCP SDU j referred as TrJ, can be estimated as:
  • TrJ Tc - TeJ
  • TeJ Ton - TdJ - Tpc, where Tc is a common frame level latency requirement, TeJ is an elapsed time for each IP packet, Taj is an arrival time of PDCP SDU j (generally known in NG-RAN), TdJ is a departure time of the IP PDU (or transport layer PDU, depending on XR application server configuration), and Tpc is a per-SDU processing time in SDAP layer.
  • the information about TdJ can be provided occasionally by an XR Edge application server to the 5GC and forwarded to the NG-RAN. It is expected that TdJ will be approximately the frame interval over time, or its variance will be very small.
  • the NG-RAN can also estimate TeJ indirectly, such as by checking the arrival timing of the first SDAP SDU in every SDAP burst and comparing it with a typical frame refresh rate.
  • FIGS 7A-B show an exemplary method (e.g., procedures) for communicating data using a protocol stack that includes a first layer comprising at least one group discard timer, according to various embodiments of the present disclosure.
  • various features of the operations described below correspond to various embodiments described above.
  • the exemplary method shown in Figure 7 can be performed by a node in a wireless network (e.g., E-UTRAN, NG-RAN), such as a UE (e.g., wireless device) or a network node (e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof).
  • a wireless network e.g., E-UTRAN, NG-RAN
  • UE e.g., wireless device
  • a network node e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof.
  • Figure 7 shows specific blocks in a particular order, the operations of the exemplary method can be performed in a different order than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.
  • the exemplary method can include the operations of block 720, where the node can receive, at the first layer from a higher layer of the protocol stack, a first plurality of SDUs associated with a common maximum latency requirement.
  • the exemplary method can also include the operations of block 750, where the node can, based on the common maximum latency requirement, initiate at least one group discard timer associated with the first plurality of SDUs.
  • the exemplary method can also include the operations of block 770, where the node can, upon expiration of the at least one discard timer, discard the first plurality of SDUs associated with common latency requirement.
  • the first plurality of SDUs is associated with one or more of the following: one or more higher-layer PDUs that have a common maximum latency requirement; a common group discard time; and a single data flow (e.g., an XR data flow).
  • the first plurality of SDUs comprises a first SDU and a second SDU received a duration after the first SDU.
  • the initiating operations of block 740 can include the operations of sub-block 741, where the node can initiate a first discard timer with a first value upon receipt of the first SDU.
  • an indication of the first value can be received from the higher layer in association with the first SDU.
  • the first discard timer is associated with the first and second SDUs. Examples of these embodiments include the “second option” discussed above.
  • the initiating operations of block 740 can include the operations of sub-block 742, where the node can initiate a second discard timer with a second value upon receipt of the second SDU.
  • the second value can be the first value minus the duration.
  • the discarding operations of block 760 can include the operations of subblocks 761-762, where the node can discard the first SDU upon expiration of the first discard timer and discard the second SDU upon expiration of the second discard timer. Examples of these embodiments include the “first option” discussed above.
  • the initiating operations of block 740 can also include the operations of sub-block 743, where the node can refrain from initiating a second discard timer upon receipt of the second SDU.
  • the discarding operations of block 760 can include the operations of sub-block 763, where the node can discard the first plurality of SDUs upon expiration of the first discard timer. Examples of these embodiments include the “third option” discussed above.
  • the first plurality of SDUs can be associated with a data flow comprising a plurality of higher-layer PDUs.
  • the initiating operations of block 740 can also include the operations of sub-block 744, where the node can refrain from initiating further discard timers upon receipt, after the second SDU, of further SDUs associated with the data flow.
  • the exemplary method can also include the operations of blocks 760 and 780.
  • the node can form the first plurality of SDUs into a second plurality of first-layer PDUs and send the second plurality of first-layer PDUs to a lower layer of the protocol stack.
  • the node can, upon expiration of the at least one group discard timer, send to the lower layer respective discard indications associated with the second plurality of first-layer PDUs.
  • the exemplary method can also include the operations of block 730, where the node can determine that the first plurality of SDU are associated with a common maximum latency requirement based on one of the following:
  • the first layer can be a PDCP layer and the higher layer can be an application layer, an IP layer, or an SDAP layer.
  • the lower layer mentioned above can be an RLC layer.
  • the node can be a UE.
  • the exemplary method can also include the operations of block 710a, where the UE can receive, from a network node in the wireless network, a discard timer configuration including one or more of the following:
  • initiating the at least one group discard timer (e.g., in block 750) and discarding the first plurality of SDUs (e.g., in block 770) can be based on the received discard timer configuration.
  • the node can be a network node in a wireless network.
  • the exemplary method can also include the operations of block 710b, where the network node can send, to a UE, a discard timer configuration including one or more of the above- mentioned items.
  • the network node can use the same or similar discard timer configuration as provided to the UE, thereby facilitating communication interoperability and/or compatibility between the two nodes.
  • the exemplary method can also include the operations of block 740, where the node can determine remaining durations of validity for the respective first plurality of SDUs based on the following for one or more higher-layer PDUs associated with the first plurality of SDUs: a maximum latency requirement, and a time of arrival in the wireless network. Additionally, initiating the at least one group discard timer (e.g., in block 750) is based on the remaining durations of validity.
  • determining remaining durations of validity for the respective first plurality of SDUs can be based on one of the following:
  • embodiments can include a UE configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer.
  • the UE can include radio transceiver circuitry configured to communicate with a network node, in a wireless network, that has a compatible protocol stack.
  • the UE can also include processing circuitry operatively coupled to the radio transceiver circuitry.
  • the processing circuitry and the radio transceiver circuitry can be configured to perform operations corresponding to any of the relevant embodiments discussed above in relation to Figure 7.
  • embodiments can include a UE configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer.
  • the UE can include various modules with functionality that corresponds to respective operations discussed above in relation to Figure 7. As a specific example, the UE can include:
  • a discarding module with functionality that corresponds to the operations of block 770.
  • the functionality of these and other modules of the UE can be implemented by any appropriate combination of hardware and software, such as by processing circuitry, radio transceiver circuitry, and/or executable program instructions stored a computer-readable medium (e.g., a memory).
  • embodiments can include a network node, of a wireless network, that is configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer.
  • the network node can include radio network interface circuitry configured to communicate with a UE that has a compatible protocol stack.
  • the network node can also include processing circuitry operatively coupled to the radio network interface circuitry. The processing circuitry and the radio network interface circuitry can be configured to perform operations corresponding to any of the relevant embodiments discussed above in relation to Figure 7.
  • embodiments can include a network node, of a wireless network, that is configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer.
  • the network node can include various modules with functionality that corresponds to respective operations discussed above in relation to Figure 7. As a specific example, the network node can include:
  • a discarding module with functionality that corresponds to the operations of block 770.
  • the functionality of these and other modules of the network node can be implemented by any appropriate combination of hardware and software, such as by processing circuitry, radio network interface circuitry, and/or executable program instructions stored a computer-readable medium (e.g., a memory).
  • FIG 8 shows a block diagram of an exemplary wireless device or UE 800 (hereinafter referred to as “UE 800”) according to various embodiments of the present disclosure, including those described above with reference to other figures.
  • UE 800 can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.
  • UE 800 can include a processor 810 (also referred to as “processing circuitry”) that can be operably connected to a program memory 820 and/or a data memory 830 via a bus 870 that can comprise parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • Program memory 820 can store software code, programs, and/or instructions (collectively shown as computer program product (CPP) 821 in Figure 8) that, when executed by processor 810, can configure and/or facilitate UE 800 to perform various operations, including operations corresponding to various exemplary methods described herein.
  • CPP computer program product
  • execution of such instructions can configure and/or facilitate UE 800 to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as those commonly known as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, IxRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver 840, user interface 850, and/or control interface 860.
  • 3GPP 3GPP2
  • IEEE such as those commonly known as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, IxRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver 840, user interface 850, and/or control interface 860.
  • processor 810 can execute program code stored in program memory 820 that corresponds to MAC, RLC, PDCP, SDAP, RRC, and NAS layer protocols standardized by 3GPP (e.g., for NR and/or LTE).
  • processor 810 can execute program code stored in program memory 820 that, together with radio transceiver 840, implements corresponding PHY layer protocols, such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single-Carrier Frequency Division Multiple Access (SC-FDMA).
  • processor 810 can execute program code stored in program memory 820 that, together with radio transceiver 840, implements device-to-device (D2D) communications with other compatible devices and/or UEs.
  • D2D device-to-device
  • Program memory 820 can also include software code executed by processor 810 to control the functions of UE 800, including configuring and controlling various components such as radio transceiver 840, user interface 850, and/or control interface 860.
  • Program memory 820 can also comprise one or more application programs and/or modules comprising computer-executable instructions embodying any of the exemplary methods described herein.
  • Such software code can be specified or written using any known or future developed programming language, such as e.g., Java, C++, C, Objective C, HTML, XHTML, machine code, and Assembler, as long as the desired functionality, e.g., as defined by the implemented method steps, is preserved.
  • program memory 820 can comprise an external storage arrangement (not shown) remote from UE 800, from which the instructions can be downloaded into program memory 820 located within or removably coupled to UE 800, so as to enable execution of such instructions.
  • Data memory 830 can include memory area for processor 810 to store variables used in protocols, configuration, control, and other functions of UE 800, including operations corresponding to, or comprising, any of the exemplary methods described herein.
  • program memory 820 and/or data memory 830 can include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof.
  • data memory 830 can comprise a memory slot by which removable memory cards in one or more formats (e.g., SD Card, Memory Stick, Compact Flash, etc.) can be inserted and removed.
  • processor 810 can include multiple individual processors (including, e.g., multi-core processors), each of which implements a portion of the functionality described above. In such cases, multiple individual processors can be commonly connected to program memory 820 and data memory 830 or individually connected to multiple individual program memories and or data memories. More generally, persons of ordinary skill in the art will recognize that various protocols and other functions of UE 800 can be implemented in many different computer arrangements comprising different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and/or programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.
  • Radio transceiver 840 can include radio-frequency transmitter and/or receiver functionality that facilitates the UE 800 to communicate with other equipment supporting like wireless communication standards and/or protocols.
  • the radio transceiver 840 includes one or more transmitters and one or more receivers that enable UE 800 to communicate according to various protocols and/or methods proposed for standardization by 3GPP and/or other standards bodies.
  • such functionality can operate cooperatively with processor 810 to implement a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies, such as described herein with respect to other figures.
  • radio transceiver 840 includes one or more transmitters and one or more receivers that can facilitate the UE 800 to communicate with various LTE, LTE-Advanced (LTE-A), and/or NR networks according to standards promulgated by 3GPP.
  • the radio transceiver 840 includes circuitry, firmware, etc. necessary for the UE 800 to communicate with various NR, NR-U, LTE, LTE-A, LTE-LAA, UMTS, and/or GSMZEDGE networks, also according to 3GPP standards.
  • radio transceiver 840 can include circuitry supporting D2D communications between UE 800 and other compatible devices.
  • radio transceiver 840 includes circuitry, firmware, etc. necessary for the UE 800 to communicate with various CDMA2000 networks, according to 3GPP2 standards.
  • the radio transceiver 840 can be capable of communicating using radio technologies that operate in unlicensed frequency bands, such as IEEE 802.11 WiFi that operates using frequencies in the regions of 2.4, 5.6, and/or 60 GHz.
  • radio transceiver 840 can include a transceiver that is capable of wired communication, such as by using IEEE 802.3 Ethernet technology.
  • the functionality particular to each of these embodiments can be coupled with and/or controlled by other circuitry in the UE 800, such as the processor 810 executing program code stored in program memory 820 in conjunction with, and/or supported by, data memory 830.
  • User interface 850 can take various forms depending on the particular embodiment of UE 800, or can be absent from UE 800 entirely.
  • user interface 850 can comprise a microphone, a loudspeaker, slidable buttons, depressible buttons, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and/or any other user-interface features commonly found on mobile phones.
  • the UE 800 can comprise a tablet computing device including a larger touchscreen display.
  • one or more of the mechanical features of the user interface 850 can be replaced by comparable or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using the touchscreen display, as familiar to persons of ordinary skill in the art.
  • the UE 800 can be a digital computing device, such as a laptop computer, desktop computer, workstation, etc. that comprises a mechanical keyboard that can be integrated, detached, or detachable depending on the particular exemplary embodiment.
  • a digital computing device can also comprise a touch screen display.
  • Many exemplary embodiments of the UE 800 having a touch screen display are capable of receiving user inputs, such as inputs related to exemplary methods described herein or otherwise known to persons of ordinary skill.
  • UE 800 can include an orientation sensor, which can be used in various ways by features and functions of UE 800.
  • the UE 800 can use outputs of the orientation sensor to determine when a user has changed the physical orientation of the UE 800’ s touch screen display.
  • An indication signal from the orientation sensor can be available to any application program executing on the UE 800, such that an application program can change the orientation of a screen display (e.g., from portrait to landscape) automatically when the indication signal indicates an approximate 90-degree change in physical orientation of the device.
  • the application program can maintain the screen display in a manner that is readable by the user, regardless of the physical orientation of the device.
  • the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.
  • a control interface 860 of the UE 800 can take various forms depending on the particular exemplary embodiment of UE 800 and of the particular interface requirements of other devices that the UE 800 is intended to communicate with and/or control.
  • the control interface 860 can comprise an RS-232 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE (“Firewire”) interface, an I 2 C interface, a PCMCIA interface, or the like.
  • control interface 860 can comprise an IEEE 802.3 Ethernet interface such as described above.
  • the control interface 860 can comprise analog interface circuitry including, for example, one or more digital-to-analog converters (DACs) and/or analog-to-digital converters (ADCs).
  • DACs digital-to-analog converters
  • ADCs analog-to-digital converters
  • the UE 800 can comprise more functionality than is shown in Figure 8 including, for example, a video and/or still-image camera, microphone, media player and/or recorder, etc.
  • radio transceiver 840 can include circuitry necessary to communicate using additional radio-frequency communication standards including Bluetooth, GPS, and/or others.
  • the processor 810 can execute software code stored in the program memory 820 to control such additional functionality. For example, directional velocity and/or position estimates output from a GPS receiver can be available to any application program executing on the UE 800, including any program code corresponding to and/or embodying any exemplary embodiments (e.g., of methods) described herein.
  • FIG. 9 shows a block diagram of an exemplary network node 900 according to various embodiments of the present disclosure, including those described above with reference to other figures.
  • exemplary network node 900 can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.
  • network node 900 can comprise a base station, eNB, gNB, or one or more components thereof.
  • network node 900 can be configured as a central unit (CU) and one or more distributed units (DUs) according to NR gNB architectures specified by 3GPP. More generally, the functionally of network node 900 can be distributed across various physical devices and/or functional units, modules, etc.
  • CU central unit
  • DUs distributed units
  • Network node 900 can include processor 910 (also referred to as “processing circuitry”) that is operably connected to program memory 920 and data memory 930 via bus 970, which can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • processor 910 also referred to as “processing circuitry”
  • bus 970 can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • Program memory 920 can store software code, programs, and/or instructions (collectively shown as computer program product (CPP) 921 in Figure 9) that, when executed by processor 910, can configure and/or facilitate network node 900 to perform various operations, including operations corresponding to various exemplary methods described herein.
  • CPP computer program product
  • program memory 920 can also include software code executed by processor 910 that can configure and/or facilitate network node 900 to communicate with one or more other UEs or network nodes using other protocols or protocol layers, such as one or more of the PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS layer protocols standardized by 3GPP for LTE, LTE-A, and/or NR, or any other higher-layer protocols utilized in conjunction with radio network interface 940 and/or core network interface 950.
  • core network interface 950 can comprise the SI or NG interface and radio network interface 940 can comprise the Uu interface, as standardized by 3GPP.
  • Program memory 920 can also comprise software code executed by processor 910 to control the functions of network node 900, including configuring and controlling various components such as radio network interface 940 and core network interface 950.
  • Data memory 930 can comprise memory area for processor 910 to store variables used in protocols, configuration, control, and other functions of network node 900.
  • program memory 920 and data memory 930 can comprise non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., “cloud”) storage, or a combination thereof.
  • processor 910 can include multiple individual processors (not shown), each of which implements a portion of the functionality described above. In such case, multiple individual processors may be commonly connected to program memory 920 and data memory 930 or individually connected to multiple individual program memories and/or data memories.
  • network node 900 may be implemented in many different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuitry, programmable digital circuitry, analog baseband circuitry, radiofrequency circuitry, software, firmware, and middleware.
  • Radio network interface 940 can comprise transmitters, receivers, signal processors, ASICs, antennas, beamforming units, and other circuitry that enables network node 900 to communicate with other equipment such as, in some embodiments, a plurality of compatible user equipment (UE). In some embodiments, interface 940 can also enable network node 900 to communicate with compatible satellites of a satellite communication network. In some exemplary embodiments, radio network interface 940 can comprise various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and/or RRC layer protocols standardized by 3GPP for LTE, LTE- A, LTE-LAA, NR, NR-U, etc.
  • the radio network interface 940 can comprise a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies.
  • the functionality of such a PHY layer can be provided cooperatively by radio network interface 940 and processor 910 (including program code in memory 920).
  • Core network interface 950 can comprise transmitters, receivers, and other circuitry that enables network node 900 to communicate with other equipment in a core network such as, in some embodiments, circuit-switched (CS) and/or packet-switched Core (PS) networks.
  • core network interface 950 can comprise the SI interface standardized by 3GPP.
  • core network interface 950 can comprise the NG interface standardized by 3GPP.
  • core network interface 950 can comprise one or more interfaces to one or more AMFs, SMFs, SGWs, MMEs, SGSNs, GGSNs, and other physical devices that comprise functionality found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks that are known to persons of ordinary skill in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface.
  • lower layers of core network interface 950 can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethemet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • ATM asynchronous transfer mode
  • IP Internet Protocol
  • SDH over optical fiber
  • T1/E1/PDH over a copper wire
  • microwave radio or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • network node 900 can include hardware and/or software that configures and/or facilitates network node 900 to communicate with other network nodes in a RAN, such as with other eNBs, gNBs, ng-eNBs, en-gNBs, IAB nodes, etc.
  • Such hardware and/or software can be part of radio network interface 940 and/or core network interface 950, or it can be a separate functional unit (not shown).
  • such hardware and/or software can configure and/or facilitate network node 900 to communicate with other RAN nodes via the X2 or Xn interfaces, as standardized by 3 GPP.
  • OA&M interface 960 can comprise transmitters, receivers, and other circuitry that enables network node 900 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of network node 900 or other network equipment operably connected thereto.
  • Lower layers of OA&M interface 960 can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethernet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • ATM asynchronous transfer mode
  • IP Internet Protocol
  • SDH over optical fiber
  • T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • radio network interface 940, core network interface 950, and OA&M interface 960 may be multiplexed together on a single physical interface, such as the examples listed above.
  • FIG 10 is a block diagram of an exemplary communication network configured to provide over-the-top (OTT) data services between a host computer and a user equipment (UE), according to one or more exemplary embodiments of the present disclosure.
  • UE 1010 can communicate with radio access network (RAN) 1030 over radio interface 1020, which can be based on protocols described above including, e.g., LTE, LTE-A, and 5G/NR.
  • RAN radio access network
  • UE 1010 can be configured and/or arranged as shown in other figures discussed above.
  • RAN 1030 can include one or more network nodes (e.g., base stations, eNBs, gNBs, controllers, etc.) operable in licensed spectrum bands, as well one or more network nodes operable in unlicensed spectrum (using, e.g., LAA or NR-U technology), such as a 2.4-GHz band and/or a 5-GHz band.
  • network nodes comprising RAN 1030 can cooperatively operate using licensed and unlicensed spectrum.
  • RAN 1030 can include, or be capable of communication with, one or more satellites comprising a satellite access network.
  • RAN 1030 can further communicate with core network 1040 according to various protocols and interfaces described above.
  • one or more apparatus e.g., base stations, eNBs, gNBs, etc.
  • RAN 1030 and core network 1040 can be configured and/or arranged as shown in other figures discussed above.
  • eNBs comprising an evolved UTRAN (E-UTRAN) 1030 can communicate with an evolved packet core (EPC) network 1040 via an SI interface.
  • EPC evolved packet core
  • gNBs and ng-eNBs comprising an NG-RAN 1030 can communicate with a 5GC network 1030 via an NG interface.
  • Core network 1040 can further communicate with an external packet data network, illustrated in Figure 10 as Internet 1050, according to various protocols and interfaces known to persons of ordinary skill in the art. Many other devices and/or networks can also connect to and communicate via Internet 1050, such as exemplary host computer 1060.
  • host computer 1060 can communicate with UE 1010 using Internet 1050, core network 1040, and RAN 1030 as intermediaries.
  • Host computer 1060 can be a server (e.g., an application server) under ownership and/or control of a service provider.
  • Host computer 1060 can be operated by the OTT service provider or by another entity on the service provider’s behalf.
  • host computer 1060 can provide an over-the-top (OTT) packet data service to UE 1010 using facilities of core network 1040 and RAN 1030, which can be unaware of the routing of an outgoing/incoming communication to/from host computer 1060.
  • host computer 1060 can be unaware of routing of a transmission from the host computer to the UE, e.g., the routing of the transmission through RAN 1030.
  • OTT services can be provided using the exemplary configuration shown in Figure 10 including, e.g., streaming (unidirectional) audio and/or video from host computer to UE, interactive (bidirectional) audio and/or video between host computer and UE, interactive messaging or social communication, interactive virtual or augmented reality, cloud gaming, etc.
  • the exemplary network shown in Figure 10 can also include measurement procedures and/or sensors that monitor network performance metrics including data rate, latency and other factors that are improved by exemplary embodiments disclosed herein.
  • the exemplary network can also include functionality for reconfiguring the link between the endpoints (e.g., host computer and UE) in response to variations in the measurement results.
  • Such procedures and functionalities are known and practiced; if the network hides or abstracts the radio interface from the OTT service provider, measurements can be facilitated by proprietary signaling between the UE and the host computer.
  • the exemplary embodiments described herein provide flexible and efficient techniques to inform a PDCP layer about which PDCP SDUs are associated with a single application PDU that needs to be delivered according to a maximum latency requirement.
  • a network or UE
  • network resources are used more efficiently, thereby increasing capacity.
  • these techniques facilitate more efficient resource scheduling for delivery of PDCP PDUs. This can better fulfill QoS requirements and improve QoE by avoiding unnecessary resource usage and interference caused by unwanted application data.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
  • SDU associated with a common maximum latency requirement
  • A2 The method of embodiment Al, wherein the first plurality of SDUs is associated with one or more of the following: one or more higher-layer PDUs that have a common maximum latency requirement; a group discard time; and an extended reality (XR) application.
  • XR extended reality
  • A3 The method of any of embodiments A1-A2, wherein: the first plurality comprises a first SDU and a second SDU received a duration after the first SDU; and initiating the at least one group discard timer comprises initiating a first discard timer with a first value upon receipt of the first SDU.
  • initiating the at least one group discard timer further comprises initiating a second discard timers with a second value upon receipt of the second SDU; and the second value is the first value minus the duration.
  • discarding comprises: discarding the first SDU upon expiration of the first discard timer; and discarding the second SDU upon expiration of the second discard timer.
  • initiating the at least one group discard timer further comprises refraining from initiating a second discard timer upon receipt of the second SDU; and discarding comprises discarding the first plurality of SDUs upon expiration of the first discard timer.
  • A7 The method of embodiment A6, wherein: the first plurality of SDUs are associated with an extended reality (XR) data flow comprising a plurality of higher-layer PDUs; and initiating the at least one group discard timer further comprises refraining from initiating further discard timers upon receipt, after the second SDU, of further SDUs associated with the XR data flow.
  • XR extended reality
  • A8 The method of any of embodiments A1-A6, further comprising: forming the first plurality of SDUs into a second plurality of first-layer PDUs; sending the second plurality of first-layer PDUs to a lower layer; and upon expiration of the at least one group discard timer, sending, to the lower layer, respective discard indications associated with the second plurality of first-layer PDUs.
  • A9 The method of any of embodiments A1-A8, further comprising determining that the first plurality of SDU are associated with a common maximum latency requirement based on a common sequence number identified by one of the following: inspecting packet headers of the first plurality of SDUs; or receiving from the higher layer in association with each of the first plurality of SDUs.
  • the first layer is a Packet Data Convergence Protocol (PDCP) layer
  • the higher layer is an Internet Protocol ((IP) layer or a Service Data Adaptation Protocol (SDAP) layer.
  • PDCP Packet Data Convergence Protocol
  • IP Internet Protocol
  • SDAP Service Data Adaptation Protocol
  • the method further comprises receiving, from a network node in the wireless network, a discard timer configuration including one or more of the following: a number of group discard timers to be used; relationship between received SDUs and group discard timers; a duration for a first group discard timer; and relationship between expiration of group discard timers and discarding of SDUs.
  • a discard timer configuration including one or more of the following: a number of group discard timers to be used; relationship between received SDUs and group discard timers; a duration for a first group discard timer; and relationship between expiration of group discard timers and discarding of SDUs.
  • the node is a network node in the wireless network; and the method further comprises sending, to a user equipment (UE), a discard timer configuration including one or more of the following: a number of group discard timers to be used; relationship between received SDUs and group discard timers; a duration for a first group discard timer; and relationship between expiration of group discard timers and discarding of SDUs.
  • UE user equipment
  • a user equipment configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, the UE comprising: radio transceiver circuitry configured to communicate with a network node, in a wireless network, that has a compatible protocol stack; and processing circuitry operatively coupled to the radio transceiver circuitry, whereby the processing circuitry and the radio transceiver circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A12.
  • a user equipment configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, the UE being further arranged to perform operations corresponding to any of the methods of embodiments A1-A12.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A12.
  • UE user equipment
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A12.
  • UE user equipment
  • a network node of a wireless network, configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, the network node comprising: radio network interface circuitry configured to communicate with a user equipment (UE) that has a compatible protocol stack; and processing circuitry operatively coupled to the radio network interface circuitry, whereby the processing circuitry and the radio network interface circuitry are configured to perform operations corresponding to any of the methods of embodiments Al- A12.
  • UE user equipment
  • a network node, of a wireless network configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, the network node being further arranged to perform operations corresponding to any of the methods of embodiments A1-A12.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a network node configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, configure the network node to perform operations corresponding to any of the methods of embodiments A1-A12.
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node configured to communicate data using a protocol stack that includes a first layer comprising at least one group discard timer, configure the network node to perform operations corresponding to any of the methods of embodiments A1-A12.

Landscapes

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

Abstract

Des modes de réalisation comprennent des procédés pour un nœud dans un réseau sans fil pour communiquer des données à l'aide d'une pile de protocoles qui comprend une première couche comprenant au moins un temporisateur de rejet de groupe. De tels procédés consistent à recevoir (720), au niveau de la première couche à partir d'une couche supérieure de la pile de protocoles, une première pluralité d'unités de données de service, SDU, associées à une exigence de latence maximale commune. De tels procédés consistent, sur la base de l'exigence de latence maximale commune, à lancer (750) au moins un temporisateur de rejet de groupe associé à la première pluralité de SDU et, à l'expiration dudit temporisateur de rejet, à rejeter (770) la première pluralité de SDU associées à une exigence de latence commune. Le nœud peut être un équipement utilisateur, UE, ou un nœud réseau. D'autres modes de réalisation comprennent des UE et des nœuds de réseau configurés pour mettre en œuvre de tels procédés.
EP21794662.3A 2020-10-08 2021-10-06 Temporisateur de rejet de pdcp de groupe pour des services à faible latence Pending EP4226596A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063089180P 2020-10-08 2020-10-08
PCT/SE2021/050981 WO2022075912A1 (fr) 2020-10-08 2021-10-06 Temporisateur de rejet de pdcp de groupe pour des services à faible latence

Publications (1)

Publication Number Publication Date
EP4226596A1 true EP4226596A1 (fr) 2023-08-16

Family

ID=78294044

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21794662.3A Pending EP4226596A1 (fr) 2020-10-08 2021-10-06 Temporisateur de rejet de pdcp de groupe pour des services à faible latence

Country Status (3)

Country Link
EP (1) EP4226596A1 (fr)
AR (1) AR123720A1 (fr)
WO (1) WO2022075912A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023211941A1 (fr) * 2022-04-27 2023-11-02 Interdigital Patent Holdings, Inc. Procédés de gestion de performance de liaison robuste pour xr
CN117097435A (zh) * 2022-05-09 2023-11-21 维沃移动通信有限公司 数据处理方法、装置、通信设备、系统及存储介质
CN117202255A (zh) * 2022-05-31 2023-12-08 大唐移动通信设备有限公司 数据单元处理方法、装置及通信设备
CN117478971A (zh) * 2022-07-22 2024-01-30 中国移动通信有限公司研究院 数据处理方法、装置及通信设备
WO2024073967A1 (fr) * 2023-01-06 2024-04-11 Lenovo (Beijing) Limited Procédés et appareils pour un mécanisme d'activation de gestion de congestion

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101513033B1 (ko) * 2007-09-18 2015-04-17 엘지전자 주식회사 다중 계층 구조에서 ＱｏＳ를 보장하기 위한 방법
WO2018085209A1 (fr) * 2016-11-01 2018-05-11 Intel IP Corporation Évitement d'une désynchronisation d'un hfn dans une liaison montante sur un wlan dans une agrégation lte-wlan
US10237197B2 (en) * 2017-01-31 2019-03-19 Wipro Limited System and method for processing data packets for transmission in a wireless communication network
US11064059B2 (en) * 2017-04-25 2021-07-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method and communication device

Also Published As

Publication number Publication date
WO2022075912A1 (fr) 2022-04-14
AR123720A1 (es) 2023-01-04

Similar Documents

Publication Publication Date Title
US20220182943A1 (en) Discovery of and Recovery From Missed Wake-Up Signal (WUS) Reception
EP4226596A1 (fr) Temporisateur de rejet de pdcp de groupe pour des services à faible latence
US20240098532A1 (en) Methods for RAN-Visible (Lightweight) QoE Configuration and Measurement Coordination Among RAN Notes
EP3949623B1 (fr) Noeud de réseau, équipement utilisateur (ue), et procédés associés destinés à la planification de l'ue par le noeud de réseau
US20220104122A1 (en) Selective Cross-Slot Scheduling for NR User Equipment
WO2022081063A1 (fr) Procédés de mesure et de rapport de qualité d'expérience (qoe) légers dans un réseau sans fil
US20240015550A1 (en) Linked Radio-Layer and Application-Layer Measurements in a Wireless Network
US20230413178A1 (en) Methods for Discontinuous Reception (DRX) in Conjunction with Guaranteed Low-Latency Services
WO2022005379A1 (fr) Contrôle réseau amélioré de rapports de mesure de qualité d'expérience (qoe) par un équipement utilisateur
WO2022086409A1 (fr) Rapport de localisation de courant continu (dc) pour agrégation de porteuses (ca) de liaison montante intra-bande
US20230163893A1 (en) Methods and Apparatus for Disabled HARQ Processes
US20230319606A1 (en) User Equipment (UE) Reporting of Non-Cellular Receiver Status
US20230354453A1 (en) Beam Failure Recovery in Multi-Cell Configuration
US20230319607A1 (en) Inter-Cell Group Messages for User Equipment Operating in Multi-Connectivity
US20220286899A1 (en) Interface between a radio access network and an application
US20230156817A1 (en) Handling of Uplink Listen-Before-Talk Failures for Handover
EP4115653A1 (fr) Émission ou réception sélective pour réduire la consommation d'énergie d'un ue
US20240114367A1 (en) Mobility Measurement Reporting for XR Services
US20240187143A1 (en) Logical Channel Prioritization within Configured Grants
US20220271866A1 (en) Controlling Packet Data Convergence Protocol (PDCP) Duplication with Different Medium Access Control (MAC) Control Elements (CES)
WO2022129390A1 (fr) Procédés de mise à jour automatique d'autorisation configurée et de synchronisation de planification semi-persistante pour des services xr
WO2022207903A1 (fr) Priorisation de canal logique dans des autorisations configurées
WO2023148335A1 (fr) Configurabilité améliorée pour planification semi-persistante et autorisations configurées

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230313

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)