WO2023130453A1 - Procédés et appareil de classification de paquets pour trafic xr - Google Patents

Procédés et appareil de classification de paquets pour trafic xr Download PDF

Info

Publication number
WO2023130453A1
WO2023130453A1 PCT/CN2022/071038 CN2022071038W WO2023130453A1 WO 2023130453 A1 WO2023130453 A1 WO 2023130453A1 CN 2022071038 W CN2022071038 W CN 2022071038W WO 2023130453 A1 WO2023130453 A1 WO 2023130453A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
packets
critical
packet
layer
Prior art date
Application number
PCT/CN2022/071038
Other languages
English (en)
Inventor
Xuelong Wang
Original Assignee
Mediatek Singapore Pte. Ltd.
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 Mediatek Singapore Pte. Ltd. filed Critical Mediatek Singapore Pte. Ltd.
Priority to PCT/CN2022/071038 priority Critical patent/WO2023130453A1/fr
Priority to CN202211639711.4A priority patent/CN116418894A/zh
Priority to US18/151,720 priority patent/US20230224383A1/en
Priority to TW112100849A priority patent/TW202345565A/zh
Publication of WO2023130453A1 publication Critical patent/WO2023130453A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]
    • 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/20—Traffic policing
    • 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/22—Traffic shaping
    • 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 relates generally to communication systems, and more particularly, the methods of enabling packet classification for XR traffic within the wireless commination network to support XR specific packet handling.
  • Various cellular systems may provide the transmission of different traffics, which allows a user equipment (UE) in the system to communicate with the cellular system.
  • UE user equipment
  • the radio access network has been typically designed to be service-agnostic, so the functions are usually not linked to a specific service, or application.
  • the service based on eXtended Reality i.e. XR service
  • the current service-agnostic design of RAN sets limitation to what the RAN can do to perform better.
  • XR eXtended Reality
  • Cloud Gaming are some of the most important 5G media applications under consideration in the industry.
  • XR is an umbrella term for different types of realities and refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes representative forms such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) and the areas interpolated among them.
  • AR Augmented Reality
  • MR Mixed Reality
  • VR Virtual Reality
  • XR services require high bit rate with bounded latency.
  • the high bit rates lead to that a large application data unit (ADU) will be transmitted in several IP packets.
  • ADU application data unit
  • RAN will treat all the packets as if they are uncorrelated from each other.
  • the end-user performance depends on if all the IP packets belonging to a single ADU are successfully delivered.
  • Application information in the RAN can assist the network to plan its resources to deliver the data according to the committed QoS.
  • radio resource management may benefit of having information about the traffic characteristic of the application.
  • a method, a computer-readable medium, and an apparatus are provided.
  • the apparatus may be a user equipment.
  • the PDCP protocol layer classifies the PDCP SDU when receiving the packets from upper layer and know the attributes of the PDCP SDU, for example, get the information if the PDCP SDU belongs to critical data or non-critical data. Based on the attributes of the PDCP SDU, the PDCP protocol layer can assign specific discard timer for the PDCP SDU. As a result, the PDCP SDU carrying critical data is not easier to be discarded during PDCP congestion and the chances for it to be transmitted is higher than non-critical data.
  • the PDCP protocol layer may set the same discard timer for all of these packets (i.e. the packets belongs to the a ADU or a XR frame) and then start the timer at the same timer, in order to achieve the coordinated PDCP packets dropping for these packets.
  • PDCP When PDCP receives the XR packets from upper layer, PDCP can prioritize critical PDCP packets over non-critical PDCP packets when placing the PDCP packets within its transmission buffer. Alternatively, when the PDCP protocol layer delivers the packets to RLC layer, the critical PDCP packets is prioritized over non-critical PDCP packets when they are placed at RLC layer buffer. In addition to packet prioritization, critical PDCP packets can also preempt the transmission of the existing buffered RLC data. In case of packet preemption, critical data will be always firstly assembled to MAC PDU at the same LCH.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 (a) is a schematic system diagram illustrating an exemplary Base Station (i.e. BS) , in accordance with certain aspects of the present disclosure.
  • BS Base Station
  • FIG. 1 (b) is a schematic system diagram illustrating an exemplary UE, in accordance with certain aspects of the present disclosure.
  • FIG. 2 illustrates an exemplary NR wireless communication system, in accordance with certain aspects of the present disclosure.
  • FIG. 3 illustrates an exemplary packet stack for XR traffic transmission, in accordance with certain aspects of the present disclosure.
  • FIG. 4 illustrates an exemplary IP packet classification at UPF, in accordance with certain aspects of the present disclosure.
  • FIG. 5 illustrates an exemplary SDAP based packet classification, in accordance with certain aspects of the present disclosure.
  • FIG. 6 illustrates an exemplary PDCP based packet classification, in accordance with certain aspects of the present disclosure.
  • FIG. 7 illustrates an exemplary PDCP packet discard for legacy system, in accordance with certain aspects of the present disclosure.
  • FIG. 8 illustrates an exemplary PDCP packet discard with long discard timer assigned for critical PDCP data, in accordance with certain aspects of the present disclosure.
  • FIG. 9 illustrates an exemplary PDCP packet prioritization for critical PDCP data, in accordance with certain aspects of the present disclosure.
  • FIG. 1 (a) is a schematic system diagram illustrating an exemplary Base Station (i.e. BS) .
  • the BS may also be referred to as an access point, an access terminal, a base station, a Node-B, an eNode-B, a gNB, or by other terminology used in the art.
  • base stations serve a number of mobile stations within a serving area, for example, a cell, or within a cell sector.
  • the Base Station has an antenna, which transmits and receives radio signals.
  • a RF transceiver coupled with the antenna, receives RF signals from antenna, converts them to baseband signals, and sends them to processor.
  • RF transceiver also converts received baseband signals from processor, converts them to RF signals, and sends out to antenna.
  • Processor processes the received baseband signals and invokes different functions.
  • Memory stores program instructions and data to control the operations of Base Station.
  • Figure 1 (b) is a schematic system diagram illustrating an exemplary UE.
  • the UE may also be referred to as a mobile station, a mobile terminal, a mobile phone, smart phone, wearable, an IoT device, a table let, a laptop, or other terminology used in the art.
  • UE has an antenna, which transmits and receives radio signals.
  • a RF transceiver coupled with the antenna, receives RF signals from antenna, converts them to baseband signal, and sends them to processor.
  • RF transceiver also converts received baseband signals from processor, converts them to RF signals, and sends out to antenna.
  • Processor processes the received baseband signals and invokes different functional modules to perform features in UE.
  • Memory stores program instructions and data to control the operations of mobile station.
  • Figure 2 illustrates an exemplary NR wireless communication system. Different protocol split options between Central Unit and Distributed Unit of gNB nodes may be possible.
  • SDAP and PDCP layer are located in the central unit, while RLC, MAC and PHY layers are located in the distributed unit.
  • XR application is initially supported by equipment in the industry.
  • the specific encoder for XR is subject to further work (e.g. by MPEG-I) .
  • Other technical components may be provided in existing MPEG specifications outside of MPEG-I (e.g., HEVC and AVC) in order to create interoperable immersive experiences for XR application.
  • the XR encoder is assumed to be based on H. 264 and/or H.265.
  • the encoded XR traffic can be transported by RTP and RTCP, which are quite popular real-time streaming transport protocols.
  • the media streaming transport protocol layer can be based on RTMP, WebRTC etc., as well. These streaming transport protocol layer have different performance about streaming latency.
  • Corresponding network transport layer for XR traffic can be based on UDP, TCP, or QUIC, etc.
  • RTP and UDP are used as the streaming transport protocol layer and network transport protocol layer.
  • IP protocol is used to as the routing protocol layer for the transmission of XR traffic within the network. Then from air interface perspective, the radio layer protocol layer only handles IP packets.
  • IP packet fragmentation is not encouraged for video stream, since NAL layer (i.e. network adaptation layer) of RTP/H. 264 can also perform packet fragmentation in order to match the MTU (maximum transmission unit) at lower layer.
  • RTP and the XR traffic encoder usually support large packet size.
  • the UDP can support up to around 65K packet size (with the exact number as 65118) .
  • IP can support up to 65K packet size.
  • various packet information may be included within the protocol header.
  • the lower layer e.g. IP, SDAP, PDCP, etc.
  • the said information to express the attribute of a particular data packet can be one or a plural of the following items: (1) the packet belongs to which media streaming slice; (2) the packet belongs to which application data unit; (3) the packet belongs to which encoding layer (e.g. base layer or enhanced layer for better quality viewing) ; (4) the packet belongs to which media streaming frame (5) the packet belongs to which type of media streaming frame (e.g.
  • the packet belongs to critical data or non-critical data; (7) the packet delay budget for the packet; (8) priority of the packet; (9) the packet is new transmission or retransmission at media streaming transport layer or application; (10) the packet is a redundant packet or a non-redundant transmission; (11) the packet is a control packet or a data streaming packet from media streaming transport layer; (12) the reliability requirement of the packet. (13) the packet belongs to which media traffic type (e.g. XR traffic) .
  • media traffic type e.g. XR traffic
  • critical packets means the packets are important and the reception of these packets is very important. Sometimes, this packet should be prioritized. It may have more stringent transmission requirement in terms of quality, reliability, packet error rate, packet delay budget, etc.
  • critical packets can be I-frame
  • the normal packets i.e., non-critical packets
  • the critical packets can be control related packets
  • the normal packets i.e., non-critical packets
  • the different frames, the different slices or different application data unit can be associated with a different RTP payload types at RTP layer.
  • the RTP header may provide the information that this packet belongs to a particular frame (e.g., a particular I-frame or P-frame for video stream) .
  • lower layer e.g., IP, SDAP, PDCP
  • RTP header may provide the information that this packet belongs to a particular ADU, which helps low layer to do coordinated dropping for a group of packets, to do packet prioritization and/or to do packet preemption.
  • 5GS exploits DiffServ and DSCP at IP layer to do packet marking and to associate a given packet to a given QoS flow.
  • 6 DSCP bits are used to map the traffic carried by IP to the traffic expressed by 5QI. These bits are only visible at network layer from service granularity perspective due to lack of DSCP bits. It is based on a fixed mapping table between DSCP and 5QI as defined by operators.
  • Figure 4 depicts a mechanism where the IP based packetization is performed at UPF for DL XR traffic.
  • the UPF entity is at a better position to differentiate the XR traffic in terms of different QoS flows since it interworks with the node at the data network.
  • the XR application i.e. application 3 are split into two QoS flows (QoS Flow 2 and 3) when the data are delivered to RAN.
  • QoS Flow 2 and 3 QoS flows
  • DRB 2 and DRB 3 data radio bearers
  • UPF can inspect the DSCP of IP layer and then map the different packet types to different QoS flows. This alternative is based on the similar mark as presented by Diffserv and DSCP.
  • the current DSCP only has 6-bit, where there is only one code-point (i.e., 32) used for AR traffic so far, as recommended by IETF.
  • DSCP bits should be extended in terms of the bit number (e.g., from 6 bits to 8 bits) , otherwise, more code-points within the 6-bit should be defined to match the number of XR traffic types, since apparently XR traffic includes a number of various applications with different QoS requirement.
  • the shortage of this operation is this may introduce the requirement to enable inter-flow synchronization at the SDAP->IP layer delivery at the UE side.
  • UPF may mark the packets (e.g., critical data or non-critical data) before transmitting them to the gNB, which helps the gNB to perform further packetization at RAN level.
  • Figure 5 depicts a mechanism where the packet classification is performed at SDAP for XR traffic.
  • the SDAP protocol layer inspects the transport packet header (e.g. IP/UDP/RTP) to know the packet characteristics.
  • SDAP maps one flow to multiple DRBs to classify critical packets and non-critical packets, or to classify different type of packets.
  • DRB 2 and DRB 3 represent different types of packets within one flow.
  • the PDCP entities of these DRBs serving one QoS flow are associated, which is subject to aggregation at Rx SDAP at receiving side. In this case, each DRB/PDCP entity handles the packets independently.
  • one XR application is split into two QoS flows.
  • One XR application can be mapped to one QoS flow or multiple QoS flows.
  • Figure 6 depicts a mechanism where the packet classification is performed at PDCP for XR traffic.
  • PDCP inspects the transport packet header (e.g., SDAP, IP, UDP and/or RTP) to know the packet characteristics.
  • PDCP maps one DRB to multiple RLC entities/LCHs to classify critical packets and non-critical packets, or to classify different type of packets.
  • Critical packets and non-critical packets, or different type of packets within one DRB can be carried by different logical channels.
  • the grey packets represent the critical packets (or one type of packets) for a particular XR application.
  • the RLC entities/logical channels of the DRB are associated, which is subjected to aggregation at the PDCP at receiver side.
  • the logical channel i.e., LCH
  • LCH logical channel carrying critical packets (or one type of packets) will be put with higher priority (comparing with non-critical packets, or other type of packets) for LCH prioritization at MAC layer.
  • Each RLC entity/LCH handles the packets independently.
  • the PDCP layer maps one DRB to one RLC entity and one LCH but classifies the critical packets and non-critical packets, or different types of packets within the RLC entity and the corresponding LCH.
  • the radio protocol layer (SDAP or PDCP layer) can inspect the DSCP code within the IP header to know if the packet is XR traffic before the radio protocol layer perform deep packet inspection on the protocol header of the media streaming transport layer (e.g., RTP) to examine the detailed attributes of the packets for a particular XR application.
  • SDAP Secure Digital Protocol
  • PDCP layer can inspect the DSCP code within the IP header to know if the packet is XR traffic before the radio protocol layer perform deep packet inspection on the protocol header of the media streaming transport layer (e.g., RTP) to examine the detailed attributes of the packets for a particular XR application.
  • RTP media streaming transport layer
  • the PDCP layer assigns a discard timer at reception of a PDCP SDU from upper layers. This timer is the same for all of the packets within a DRB and it is basically assigned based on the packet delay budget for the traffic carried by the DRB. As shown in Figure 7, discard timer (i.e., 60ms) is assigned to all of the packets regardless of critical packets or non-critical packets. Figure 7 describes the case, where the PDCP is congested and PDCP buffers the data until the PDCP SDU (with number of N+10) arrives, before an opportunity to do transmission. As shown in Figure 7, the critical packets are discarded as same as normal packets (i.e., non-critical packets) .
  • the critical packet PDCP SDU (N+3) is discarded as same as normal packets (i.e., packets numbered by N+1 and N+2) .
  • the critical packets numbered by N+4 and N+5 are also discarded because of the expiration of PDCP discard timer. Since the decoding of normal packets may be based on the previous critical packet, this legacy discard behavior will impact user experience.
  • Figure 8 depicts a mechanism for PDCP to assign different PDCP discard timers for XR critical data packets and non-critical data packets.
  • the intention is to assign a bit longer PDCP discard timer to the PDCP SDU carrying XR critical data when PDCP receives the PDCP SDU including XR critical data from upper layers for the same DRB.
  • the critical packets will be kept as long as possible during PDCP congestion.
  • PDCP is required to know the characteristic of the XR packet when a PDCP SDU is received from upper layer.
  • the upper layer e.g. SDAP layer
  • the critical packets are assigned with a long discard timer (which is 120ms)
  • the non-critical packets are assigned with a short discard timer (which is 60ms)
  • a short discard timer which is 60ms
  • the critical packets are delivered. In this way, the receiver side may achieve better decoding experience since more critical packets would be available during decoding.
  • Both short discard timer and long discard timer can be configured by RRC message from gNB to the UE during the establishment of the DRB for the XR traffic.
  • different discard timer values may be assigned to different types of the XR data packets with an aim to allow the more important packets to have more opportunity to be transmitted and to have less opportunity to be dropped.
  • different discard timer values may be assigned for the same type of XR data packets.
  • XR video frames may be independent or dependent on other previous and/or future frames. Therefore, if an IP packet belonging to a particular ADU is too late, it may negatively affect previous ADUs, upcoming ADUs, as well as the play-out time of the current ADU. Thus, dropping all relevant PDCP packets that carry the IP packets belonging to an ADU which may not be used for XR rendering, may be beneficial from a capacity point of view.
  • the media streaming transport layer e.g., RTP
  • Radio layer protocol e.g., PDCP
  • One alternative is to assign a set of coordinated PDCP discard timers to all of the relevant PDCP packets that carry the IP packets belonging to an ADU (or other XR data packet unit that is used at media stream transport layer) .
  • Another alternative is to assign a set of coordinated PDCP discard timers to all of the relevant PDCP packets that carry the IP packets belonging to a particular XR frame (or other unit that is used at XR encoder) . In this way, all of the PDCP packets for an XR ADU or a XR frame (or XR other unit) can be discarded together.
  • the PDCP may set the same discard timer for all of these packets (i.e.
  • the packets belongs to the an ADU or a XR frame) and then start the timer at the same timer.
  • the packets, received by PDCP layer from the upper layer not at the same time can be assigned with a set of coordinated discard timer values in order to trigger group based coordinated PDCP packet dropping. For example, at time point T, PDCP receives a PDCP SDU-1 for ADU-1 or XR frame-1, the discard timer can be set with 60ms. Then at time point T+10ms, when PDCP receives a PDCP SDU-2 for ADU-1 or XR frame-1, the discard timer can be set with 50ms.
  • PDCP records the XR ADU and XR frame that the PDCP SDU belongs to and then in case of PDCP SDU discarding, PDCP can discard all of the PDCP SDUs belongs to the same XR ADU and XR frame regardless of the discard timer expiration.
  • PDCP delivers the data packets to RLC layer
  • PDCP delivers firstly the PDCP packets that carry XR critical data (or the data with packet delay budget ahead of the normal data packets) even though the normal data packets may be buffered at the front of the critical packets.
  • the critical PDCP packets is always prioritized at RLC layer but will not preempt the transmission for the existing buffered RLC data, and normal data packets are deprioritized during data delivery from PDCP to RLC layer.
  • the critical PDCP packets is always prioritized at RLC layer and always preempt the transmission of the existing buffered RLC data.
  • critical data will be always firstly assembled to MAC PDU at the same LCH.
  • Finer granularity BSR i.e., buffer status report
  • BSR classifies how may critical data is in UE buffer, and how many non-critical data is in UE buffer.
  • BSR report can also indicate the remaining packet delay budget, frame information and/or ADU information for the packets at UE buffer to gNB, e.g., the UE can tell the gNB the buffered packets belong to a critical frame and the remaining packet delay budget is 5ms, which helps the gNB to allocate physical resources for such scheduling in an urgent manner.
  • MAC can indicate to physical layer if there is any critical data assembled within a particular MAC PDU (i.e., Transport Block) , which helps the physical layer to perform corresponding handling (e.g., disabling feedback based HARQ retransmission for delay sensitive packets) .
  • Transport Block i.e., Transport Block
  • the packet prioritization for XR at PDCP can also apply to ADU based packet handling, XR frame based packet handling or other unit based packet handling, which is not shown in Figure 9.
  • the PDCP SDUs that belong to the same XR ADU, or same XR fame may be buffered together within the PDCP buffer although they may be received not at the same time.
  • One late coming PDCP SDU that belongs to a XR ADU or XR frame (with lots of PDCP SDU transmitted) can be prioritized by PDCP when it delivers the PDCP SDU to RLC layer.
  • PDCP may ensure the PDCP packets that belong to the same XR ADU or XR frame be delivered to RLC layer in a consecutive manner in case of packet prioritization and packet preemption. For example, if a PDCP packet that carries part of a critical XR frame is prioritized over a normal PDCP packet, all PDCP packets that carry that critical XR frame should be prioritized over the normal PDCP packet.
  • the same principle can be applied to packet preemption.
  • the packet prioritization and packet preemption at PDCP layer may be inherited by RLC layer and this may impact the MAC PDU assembly.
  • MAC layer may further notify the priority of a packet and/or other information to Physical layer to perform corresponding handling (e.g., disabling feedback based HARQ retransmission for delay sensitive packets) .
  • PDCP when PDCP receives the XR packets from upper layer, PDCP can prioritize critical PDCP packets over non-critical PDCP packets when placing the PDCP packets within its transmission buffer. For example, the critical PDCP data can be put ahead of the non-critical PDCP packets. Another example is that PDCP can put the PDCP packets belonging to one XR ADU and/or XR frame together within the buffer in order for further aligned delivery to lower layer. When PDCP is aware of the attributers of the packet in terms of packet inspection or cross layer indication from upper layer, PDCP can perform non-order placement within the buffer and accordingly non-order delivery to RLC layer.
  • critical PDCP packets can also preempt the transmission of the existing buffered PDCP layer data.
  • packet preemption any critical PDCP data coming from upper layer will be always buffered ahead of the existing buffered PDCP layer data in PDCP buffer during PDCP congestion.
  • PDCP layer always delivers the buffered critical PDCP packets if any to RLC layer.
  • Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.

Landscapes

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

Abstract

La divulgation décrit des procédés et un appareil de prise en charge d'une classification de paquets pour un trafic XR à l'intérieur du réseau de diffusion sans fil pour prendre en charge une priorisation et une préemption de paquets spécifiques à XR au niveau d'une couche de protocole radio (par exemple, une couche PDCP). Lorsque le PDCP reçoit les paquets XR de la couche supérieure, le PDCP peut prioriser des paquets PDCP critiques par rapport à des paquets PDCP non critiques. En variante, lorsque la couche de protocole PDCP délivre les paquets à la couche RLC, les paquets PDCP critiques sont classés par ordre de priorité sur des paquets PDCP non critiques. En plus de la priorisation de paquets, des paquets PDCP critiques peuvent également préempter la transmission des données RLC mises en mémoire tampon existantes. En cas de préemption de paquet, des données critiques seront toujours tout d'abord assemblées à la PDU MAC au même canal logique.
PCT/CN2022/071038 2022-01-10 2022-01-10 Procédés et appareil de classification de paquets pour trafic xr WO2023130453A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2022/071038 WO2023130453A1 (fr) 2022-01-10 2022-01-10 Procédés et appareil de classification de paquets pour trafic xr
CN202211639711.4A CN116418894A (zh) 2022-01-10 2022-12-20 业务处理方法和设备
US18/151,720 US20230224383A1 (en) 2022-01-10 2023-01-09 Extended reality (xr) traffic handling
TW112100849A TW202345565A (zh) 2022-01-10 2023-01-09 業務處理方法和設備

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/071038 WO2023130453A1 (fr) 2022-01-10 2022-01-10 Procédés et appareil de classification de paquets pour trafic xr

Publications (1)

Publication Number Publication Date
WO2023130453A1 true WO2023130453A1 (fr) 2023-07-13

Family

ID=87072917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/071038 WO2023130453A1 (fr) 2022-01-10 2022-01-10 Procédés et appareil de classification de paquets pour trafic xr

Country Status (1)

Country Link
WO (1) WO2023130453A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240089795A1 (en) * 2022-01-21 2024-03-14 Ofinno, Llc Data Unit Processing

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102905310A (zh) * 2011-07-25 2013-01-30 中兴通讯股份有限公司 一种数据处理方法、装置及分组数据汇聚协议层模块
WO2017196380A1 (fr) * 2016-05-13 2017-11-16 Intel IP Corporation Évitement de rejet de données vidéo critiques dans une pile de modems d'évolution à long terme
CN108616925A (zh) * 2016-12-13 2018-10-02 中兴通讯股份有限公司 一种数据流的处理方法及装置
CN111277373A (zh) * 2020-01-14 2020-06-12 深圳震有科技股份有限公司 一种服务器切换的控制方法、终端及存储介质
CN113365066A (zh) * 2021-06-29 2021-09-07 北京二六三企业通信有限公司 一种视频数据的传输方法和装置
CN113411820A (zh) * 2021-06-17 2021-09-17 武汉理工大学 一种wifi环境下vr业务优化方法、系统及存储介质
CN113472683A (zh) * 2021-07-23 2021-10-01 Oppo广东移动通信有限公司 数据丢弃方法、装置、终端及存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102905310A (zh) * 2011-07-25 2013-01-30 中兴通讯股份有限公司 一种数据处理方法、装置及分组数据汇聚协议层模块
WO2017196380A1 (fr) * 2016-05-13 2017-11-16 Intel IP Corporation Évitement de rejet de données vidéo critiques dans une pile de modems d'évolution à long terme
CN108616925A (zh) * 2016-12-13 2018-10-02 中兴通讯股份有限公司 一种数据流的处理方法及装置
CN111277373A (zh) * 2020-01-14 2020-06-12 深圳震有科技股份有限公司 一种服务器切换的控制方法、终端及存储介质
CN113411820A (zh) * 2021-06-17 2021-09-17 武汉理工大学 一种wifi环境下vr业务优化方法、系统及存储介质
CN113365066A (zh) * 2021-06-29 2021-09-07 北京二六三企业通信有限公司 一种视频数据的传输方法和装置
CN113472683A (zh) * 2021-07-23 2021-10-01 Oppo广东移动通信有限公司 数据丢弃方法、装置、终端及存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240089795A1 (en) * 2022-01-21 2024-03-14 Ofinno, Llc Data Unit Processing

Similar Documents

Publication Publication Date Title
CN107426776B (zh) QoS控制方法及设备
CN109314710B (zh) 用于通信网络中的服务质量监测、策略执行和计费的系统和方法
JP6907444B2 (ja) データ伝送方法、通信デバイス、端末、および基地局
CN109155762B (zh) 数据传输的方法及装置
EP2745477B1 (fr) Procédés et systèmes de différenciation de paquets
EP2218294B1 (fr) Signalement d'état de tampons fondé sur la configuration de porteuse radio
US10616803B2 (en) Radio base station, packet transmission apparatus, wireless terminal, control method, and program
KR20140017662A (ko) 모바일 송수신기, 기지국 송수신기, 데이터 서버, 그리고 관련 장치, 방법 및 컴퓨터 프로그램
WO2018177432A1 (fr) Procédé et appareil de traitement de données et dispositif correspondant
US20230224383A1 (en) Extended reality (xr) traffic handling
CN112352449B (zh) 无线通信网络中的拥塞管理
WO2019101054A1 (fr) Procédé, dispositif et système de commande de taux d'agrégation
US9584441B2 (en) Method and apparatus for transmitting a multimedia data packet using cross-layer optimization
CN114727340A (zh) 传输报文的方法和装置
WO2023130453A1 (fr) Procédés et appareil de classification de paquets pour trafic xr
US11647419B2 (en) Adjusting window size based on quality of experience
WO2023060406A1 (fr) Prise en charge de qos améliorée destinée à la réalité étendue (xr)
WO2023023414A2 (fr) Classification de qualité de service (qos) basée sur une signature de paquet
US9826543B2 (en) Method and apparatus in a wireless communication system
WO2023130452A1 (fr) Procédés et appareil d'inspection et de classification de paquets xr basés sur sdap au niveau d'une couche d'accès radio
WO2024060991A1 (fr) Procédé et appareil de guidage de flux de données pour trajets multiples
WO2024113069A1 (fr) Systèmes et procédés de gestion de qualité de service pour un trafic de réalité étendue
WO2024087585A9 (fr) Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole
WO2023184552A1 (fr) Procédé et appareil de transmission de données et dispositif de communication
WO2023184537A1 (fr) Procédé et appareil de transmission de données, et dispositif de communication

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

Country of ref document: EP

Kind code of ref document: A1