[go: up one dir, main page]

WO2025213076A1 - Caractéristiques associées à des informations d'ensembles de pdu pour flux de données multiplexées - Google Patents

Caractéristiques associées à des informations d'ensembles de pdu pour flux de données multiplexées

Info

Publication number
WO2025213076A1
WO2025213076A1 PCT/US2025/023236 US2025023236W WO2025213076A1 WO 2025213076 A1 WO2025213076 A1 WO 2025213076A1 US 2025023236 W US2025023236 W US 2025023236W WO 2025213076 A1 WO2025213076 A1 WO 2025213076A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
data stream
pdu set
stream
indication
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
PCT/US2025/023236
Other languages
English (en)
Inventor
Rocco Di Girolamo
Achref METHENNI
Michel Roy
Srinivas GUDUMASU
Xavier De Foy
Michael Starsinic
Magurawalage Chathura Madhusanka Sarathchandra
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.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
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 InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025213076A1 publication Critical patent/WO2025213076A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • 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/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • 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]

Definitions

  • a fifth generation may be referred to as 5G.
  • a previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).
  • 4G fourth generation
  • LTE long term evolution
  • a device may generate a multiplexed data stream comprising a first packet data unit (PDU) set, a second PDU set, and an indication of non-sequential PDU set sequence numbers.
  • the first PDU set may be associated with a first data stream.
  • the second PDU set may be associated with a second data stream.
  • the device may determine a first mapping between a first subset of the nonsequential PDU set sequence numbers and a first set of sequential PDU set sequence numbers associated with the first data stream.
  • the device may determine a second mapping between a second subset of the non-sequential PDU set sequence numbers and a second set of sequential PDU set sequence numbers associated with the second data stream.
  • the device may send the multiplexed data stream, an indication of the first mapping, and an indication of the second mapping.
  • a device may receive a first multiplexed data stream comprising a first packet data unit (PDU) set, a second PDU set, and an indication of non-sequential PDU set sequence numbers.
  • the first PDU set may be associated with a first data stream.
  • the second PDU set may be associated with a second data stream.
  • the device may determine a first mapping associated with the first data stream, based on the non-sequential PDU set sequence numbers.
  • the device may determine a second mapping associated with the second data stream, based on the non-sequential PDU set sequence numbers.
  • the device may send a second multiplexed data stream, an indication of the first mapping, and an indication of the second mapping.
  • a device may receive configuration information that indicates information associated with multiplexing data streams and information associated with splitting a data stream.
  • the device may receive data from an application server.
  • the device may identify a first stream and a second stream in the received data.
  • the device may determine a first mapping between the first stream and a first quality of service (QoS) flow, and a second mapping between the second stream and a second QoS flow.
  • QoS quality of service
  • the device may determine metadata associated with the received data.
  • the device may send the received data and the metadata to a second network node.
  • the information associated with multiplexing streams may indicate a number of multiplexed streams.
  • the information associated with splitting a data stream may indicate one or more QoS flows carrying a split stream.
  • the metadata may indicate at least one of: information to help the second network node identify multiplexed streams in the received data, information regarding where to find PDU sets of split streams, or a sequence number offset.
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • WTRU wireless transmit/receive unit
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • FIG. 2 illustrates an example quality of service (QoS) management system.
  • QoS quality of service
  • FIG. 4 illustrates an example technique for creating multiplexed streams.
  • FIG. 5 illustrates an example of traffic over QoS flows with multiplexing.
  • FIG. 6 illustrates an example of PDU set information carried in QoS flows.
  • FIGs. 7A and 7B illustrate example downlink extended reality streams multiplexed over one or more QoS flows.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (WTRU), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the I nternet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e. , one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • NR New Radio
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and I EEE 802.11 , for example.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service set (BSS) mode may have an Access Point (AP) for the AP.
  • AP Access Point
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • the AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode- B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a- b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be testing equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • a device may generate a multiplexed data stream comprising a first packet data unit (PDU) set, a second PDU set, and an indication of non-sequential PDU set sequence numbers.
  • the first PDU set may be associated with a first data stream.
  • the second PDU set may be associated with a second data stream.
  • the device may determine a first mapping between a first subset of the nonsequential PDU set sequence numbers and a first set of sequential PDU set sequence numbers associated with the first data stream.
  • the device may determine a second mapping between a second subset of the non-sequential PDU set sequence numbers and a second set of sequential PDU set sequence numbers associated with the second data stream.
  • the device may send the multiplexed data stream, an indication of the first mapping, and an indication of the second mapping.
  • a device may receive a first multiplexed data stream comprising a first packet data unit (PDU) set, a second PDU set, and an indication of non-sequential PDU set sequence numbers.
  • the first PDU set may be associated with a first data stream.
  • the second PDU set may be associated with a second data stream.
  • the device may determine a first mapping associated with the first data stream, based on the non-sequential PDU set sequence numbers.
  • the device may determine a second mapping associated with the second data stream, based on the non-sequential PDU set sequence numbers.
  • the device may send a second multiplexed data stream, an indication of the first mapping, and an indication of the second mapping.
  • a UPF may receive rules (e.g., N4 rules) from an SMF.
  • the rules may include multiplexing information and splitting information.
  • the UPF may receive XR data from an application server.
  • the UPF may identify the streams in the received XR data.
  • the UPF may map the streams to the QoS flows based on the received rules.
  • the UPF may determine the PDU set metadata and stream metadata to include with the received XR data.
  • the UPF may send the XR data and metadata to the RAN node.
  • the multiplexing information and splitting information may include information related to restrictions on multiplexing or splitting a stream (e.g., number of streams, other QoS flow carrying a split stream, and/or the like).
  • the PDU set metadata may include information to help a RAN node identify multiplexed streams, information regarding where to find PDU sets of split streams, an offset (e.g., SN_offset), etc.
  • the RAN node may perform similar actions.
  • the QoS specifications may include 5QI (e.g., resource type, priority level, PDB, PER, an averaging window, a maximum data burst volume, etc.), ARP, RQA, notification control, flow bit rates (e.g., MFBR, GBR), aggregate bit rates, maximum packet loss rates, and/or the like.
  • 5QI e.g., resource type, priority level, PDB, PER, an averaging window, a maximum data burst volume, etc.
  • ARP resource type
  • RQA e.g., notification control
  • flow bit rates e.g., MFBR, GBR
  • aggregate bit rates e.g., maximum packet loss rates, and/or the like.
  • QoS management may be enabled in a system, such as the 5G system (5GS), as shown in FIG. 2.
  • 5GS 5G system
  • a PDU may arrive at the UPF over the N6 interface.
  • the UPF may use the configured PDRs to map the traffic to a QoS flow.
  • the UPF may create a tunnel to the RAN node.
  • the UPF may send the arriving PDU to the RAN node in a GTP-U packet.
  • the RAN node may use the configured QoS profile to determine how to manage the GTP-U packet. This management may include how to schedule the packet to the WTRU and whether the packet should be discarded. If scheduled, the packet may be transmitted to the WTRU (e.g., on a configured data radio bearer (DRB)).
  • DRB configured data radio bearer
  • Processing may be defined for XR media traffic.
  • the XR traffic may be transmitted as PDU sets.
  • the QoS profile may have specifications (e.g., requirements) that target PDU sets.
  • the header of the GTP-U PDU may carry PDU set information.
  • the PDU set information may include: a PDU set sequence number; an indication of the end/last PDU of the PDU set; a PDU sequence number within a PDU set; a PDU set size (e.g., in bytes); PDU set importance (e.g., identifying the relative importance of a PDU set compared to other PDU sets within a QoS flow); and/or the like.
  • the PSA UPF may rely on information carried in the received packets and/or on implementation. For example, if the XRM traffic is carried over RTP, the RTP header may include one or more of the following.
  • the RTP header may include an indication of the end/last PDU of the PDU set (e.g., a 1 -bit indication). This field may be a flag that is set to 1 for the last PDU of the PDU set and set to 0 for all other PDUs of the PDU set.
  • the RTP header may include an indication of the end of a data burst (e.g., a 3-bit indication referred to as an EDB field).
  • the EDB field may be 3 bits in length.
  • the EDB field may indicate the end of a data burst.
  • the 3 bits may encode the end of the data burst indication (e.g., following encoding guidelines).
  • the RTP header may include an indication of a PDU set importance (e.g., a 4-bit indication referred to as a PSI field).
  • the PDU set importance field may indicate the importance of the PDU set compared to other PDU sets within the same QoS flow. Lower values may indicate a higher importance PDU set. For example, the highest-importance PDU set may be indicated by 0 and the lowest-importance PDU set may be indicated by 15.
  • the RTP header may include an indication of a PDU set sequence number (e.g., a 10-bit indication referred to as a PSSN field).
  • the PSSN field may encode the sequence number of the PDU set to which the current PDU belongs.
  • the PSSN field may act as a 10-bit numerical identifier for the PDU set.
  • the RTP header may include an indication of a PDU sequence number within a PDU set (e.g., a 6-bit indication referred to as a PSN field).
  • the PSN field may indicate the sequence number of the current PDU within the PDU set.
  • the PSN field may be set to 0 for the first PDU in the PDU set and incremented by one (e.g., monotonically) for every PDU in the PDU set in order of transmission from the sender.
  • the RTP header may include an indication of a PDU set size (e.g., a 24-bit indication referred to as a PSSize field).
  • the PDU set size may indicate the total size of all PDUs of the PDU set to which this PDU belongs.
  • the PSSize field may be optional and/or subject to an SDP signaling offer/answer negotiation (e.g., in which the application server may indicate whether it will be able to provide the size of the PDU set for that RTP stream). If not enabled, the PSSize field may not be present.
  • the PSSize field may indicate a value of 0 (e.g., in all PDUs of that PDU set).
  • the PSSize field may indicate the size of a PDU set, including RTP/UDP/IP header encapsulation overhead of its corresponding PDUs.
  • the PSSize may be expressed in bytes.
  • the network may be configured with PDU set QoS specifications (e.g., requirements) or information (e.g., in addition to the PDU set information carried in the GTP-U header).
  • the information may be defined per QoS flow.
  • the PDU set QoS specifications may be the same for PDU sets (e.g., all PDU sets) carried in a QoS flow.
  • the following PDU set QoS specifications may be defined for XRM traffic flows.
  • a PDU set delay budget may define an upper bound for the delay that a PDU set may experience for the transfer between the WTRU and the N6 termination point at the UPF (e.g., the duration between the reception time of the first PDU (at the N6 termination point for DL or the WTRU for UL) and the time when all PDUs of a PDU set have been successfully received (at the WTRU for DL or N6 termination point for UL)).
  • a PDU set error rate may define an upper bound for the rate of PDU sets that have been processed by the sender of a link layer protocol (e.g., RLC in RAN of a 3GPP access) and not successfully delivered by the corresponding receiver to the upper layer (e.g., PDCP in RAN of a 3GPP access).
  • a link layer protocol e.g., RLC in RAN of a 3GPP access
  • PDCP in RAN of a 3GPP access
  • PDU set integrated handling information may indicate whether the PDUs (e.g., all PDUs) of the PDU set are to be used (e.g., needed for the usage of the PDU set) by the application layer on the receiver side.
  • PDU set QoS specification e.g., additional requirement(s)
  • a PDU set FEC success ratio may be a percentage of PDUs that are to be delivered (e.g., that need to be successfully delivered) to the WTRU to allow the WTRU to recover the entire PDU set.
  • PDU set traffic characteristic(s) may be provided by the core network to the NG-RAN.
  • the NG- RAN may configure a WTRU power-saving management scheme for connected mode DRX.
  • the PDU set traffic characteristic(s) may include: an UL and/or DL periodicity; N6 jitter information associated with the DL periodicity; an indication of the end of a data burst; and/or the like.
  • the UL and/or DL periodicity and/or N6 jitter information associated with the DL periodicity may be provided by the core network to the NG RAN (e.g., via TSCAI).
  • the core network may receive this information from the AF.
  • the core network may derive this information at the UPF.
  • the information may be transferred to the NG RAN via the SMF and AMF.
  • FIG. 3 illustrates an example of multiplexed streams.
  • XR Media services may include multiple types of flows (e.g., video stream, audio stream, haptic, other metadata, or sensor data for a more immersive experience). To enable these immersive services, different media types may be multiplexed into a (e.g., single) data flow (e.g., before arriving at the 5GS ingress).
  • a stream e.g., each stream
  • the QoS flow may carry multiplexed streams, as illustrated in FIG. 3.
  • FIG. 4 illustrates an example of creating multiplexed streams.
  • the multiplexing of the XR streams may occur: at the application layer (e.g., RTP, for example, as shown at d) in FIG.4); at the transport layer (e.g., QUIC, for example, as shown at c) in FIG. 4); based on PCC rules provided to the UPF (e.g., as shown at a) and b) in FIG. 4); and/or the like.
  • a framework may not support differentiated QoS for the multiplexed traffic flows (e.g., if the flows share the same IP 5 tuple).
  • a framework e.g., an enhanced framework
  • the framework may involve a device performing one or more of the following actions.
  • a device may identify multiplexed traffic flows with different QoS specifications (e.g., requirements) within a (e.g., single) transport connection.
  • a device may perform QoS flow mapping for traffic flows with different QoS specifications (e.g., requirements).
  • An AF may provide information to help a device perform traffic detection (e.g., the device may determine whether and what information to request from the AF for traffic detection).
  • An AF may provide information related to QoS specifications (e.g., requirements) of different traffic flows to the system, which may be a 5GS (e.g., the device may determine whether and how the AF provides the QoS specifications of different traffic flows to the system).
  • QoS specifications e.g., requirements
  • One or more multiplexing options may be available to map SDFs to QoS flows.
  • a first multiplexing option may involve mapping an SDF stream per QoS flow.
  • a second multiplexing option may involve mapping M SDF streams per QoS flow (e.g., in which all M streams may have the same QoS parameters and PDU set QoS parameters and similar PDU set traffic characteristics).
  • a third multiplexing option may involve mapping M SDF streams per QoS flow (e.g., in which all M streams may have the same QoS parameters and PDU set QoS parameters, and different PDU set traffic characteristics).
  • a further multiplexing option may involve mapping M SDF streams per QoS flow (e.g., in which all M streams have the same QoS parameters and different PDU set QoS parameters and different PDU set traffic characteristics, or have some PDU set QoS parameters that are the same and some that are different).
  • a fifth multiplexing option may involve mapping parts of N SDF streams to a QoS flow. In this case, the N streams may have the same QoS parameters and one or more PDU set QoS parameters (e.g., the same PSI). The N streams may have the same or different PDU set characteristics.
  • FIG. 5 illustrates an example of multiplexing traffic over QoS flows (e.g., based on the fourth or fifth multiplexing options).
  • QoS flow 1 may multiplex traffic from multiple (e.g., four) traffic streams (e.g., stream 1 , stream 2, stream 3, and stream 4).
  • QoS flow 2 may carry traffic from a stream (e.g., stream 3). Traffic from stream 3 may be split across QoS flow 1 and QoS flow 2.
  • the traffic over one QoS flow may be a mix of traffic from possibly different streams. If the RAN node gets the PDU set information from the PDUs present in a QoS flow, the RAN node may know (e.g., need to know) which PDU set information applies to which PDU sets.
  • a data flow may represent traffic from an application source (e.g., application server or WTRU).
  • the data flow may be a video data flow, an audio data flow, or a haptic data flow.
  • the data flows may have a relationship in time.
  • an audio data flow may be (e.g., need to be) time synchronized with a video data flow.
  • stream may refer to a service sub-flow (e.g., a media service sub-flow) multiplexed in a service flow (e.g., multiplexed in an application connection).
  • Stream and “XR stream” may be used interchangeably.
  • the term “end-to-end connection” may be used to refer to a connection between a WTRU and an application server (e.g., that is used to transfer one or multiple data flows).
  • the end-to-end connection may be an RTP session.
  • the end-to-end connection may be a QUIC connection (e.g., where multiple streams are multiplexed).
  • the different streams may be audio and video, or different video layers (e.g., each on its own stream).
  • a PDU set may refer to one or more PDUs carrying the payload of a (e.g., one) unit of information generated at the application level (e.g., frame(s), video slice(s), etc.) for extended reality (XR) services.
  • a PDU set may have one or more PDUs.
  • the PDUs of the PDU set may carry PDU set information.
  • PDU set information may be used to refer to information carried with the PDUs of the PDU set.
  • the PDU set information may help to characterize the PDU set.
  • Example PDU set information may include the PDU set size, the PDU set sequence number, the end PDU indication, etc.
  • multi-modal data may refer to data from different kinds of devices/sensors or data output to different kinds of destinations (e.g., one or more WTRUs) that is used (e.g., required) for the same task or application.
  • Multi-modal data may include more than one single-modal data. There may be a (e.g., strong) dependency among the (e.g., each) single-modal data.
  • Single-modal data may refer to a (e.g., one) type of data.
  • stream-based QoS or “stream-based QoS parameter(s)” may refer to QoS parameter(s) that apply to an entire stream.
  • a stream-based QoS parameter(s) may include the PDU set delay budget, the PDU set error rate, the AL FEC success ratio, and/or the like.
  • the term “PDU set-based QoS” or “PDU set-based QoS parameter(s)” may refer to QoS parameter(s) that apply to a PDU set.
  • the PDU set-based QoS parameters may include the PDU set delay budget, the PDU set error rate, and/or the like.
  • the term “QoS flow-based QoS” or “QoS flow-based QoS parameter(s)” may refer to QoS parameter(s) that apply to a QoS flow.
  • the QoS flow-based QoS parameter(s) may include the packet error rate, the packet delay budget, and/or the like.
  • a FEC success ratio may refer to the ratio of PDUs in a PDU set that are (e.g., need to be) received correctly to allow the receiver to decode the (e.g., entire) PDU set.
  • Feature(s) described herein may be used to manage multiplexed PDU sets and split PDU sets.
  • the network may (e.g., be configured to) multiplex PDU sets of different streams on a QoS flow.
  • the network may (e.g., be configured to) split PDU sets of a (e.g., single) stream across two or more QoS flows.
  • the UPF may identify PDU sets to be multiplexed and/or PDU sets to be split.
  • the UPF may include (e.g., new) stream metadata in the GTP-U packet header sent to the RAN.
  • the UPF may renumber the PDU set SN to compensate for the multiplexing and splitting.
  • FIGs. 7A and 7B illustrates DL XR streams that are multiplexed over a (e.g., single) QoS flow or split over two or more QoS flows.
  • the N4 rules may include multiplexing information related to how to multiplex streams over a QoS flow, and/or splitting information related to how to split a stream across one or more QoS flows.
  • the QoS profile may include multiplexing information related to how streams are multiplexed over a QoS flow, and/or splitting information related to how a stream is split across two or more QoS flows.
  • the QoS profile may include an indication of how to handle out-of-order delivery of PDU sets and/or an indication of how to map split streams to DRBs.
  • the stream multiplexing operation may take place before the traffic flow to QoS flow mapping operation.
  • the QoS parameters and configuration of the QoS flow may (e.g., may need to) satisfy the (e.g., both) stream ID1 and stream ID3 related specifications.
  • the AF may have provided QoS related parameter(s) (e.g., a PDB specification related to stream ID1 (PDB 1) and a PDB specification related to stream ID3 (PDB 3), which may have similar values).
  • the PCF may have determined that the PDB requirement related to the QoS flow that may carry these two streams is a PDB value that is similar to PDB 1 or PDB 3 or a function of the two values.
  • the system which may be a 5GS (e.g., including the AF and PCF), may be able to provide coherent multiplexing information and QoS specifications. If the network cannot provide such information, the PCF may reject the AF request (e.g., because there are no QoS parameters that satisfy both streams).
  • the PCF may determine QoS flow parameters (e.g., based on local configuration) that may or may not meet (e.g., all of) the specifications of the traffic flow and streams.
  • the PCF or other NFs may perform one or more actions to allow for the resolution of the multiplexing specifications/indication/information and the QoS parameters related to the different streams of the traffic flow.
  • a PDU from the XR streams may arrive at the UPF.
  • the UPF may identify the XR stream of the arriving PDU based on the configured PDRs.
  • the UPF may map the PDU to a QoS flow.
  • the UPF may prepare the GTP-U packet that carries the PDU to the RAN node.
  • the UPF may determine the GTP-U header information. This information may include PDU set metadata and/or stream metadata.
  • the UPF may determine the PDU set SN to include in the GTP-U header information (e.g., to guarantee sequential PDU set SNs).
  • the GTP-U PDU may be sent to the RAN node.
  • the traffic of a stream may be split across two or more QoS flows.
  • the RAN node may identify the streams in a QoS flow.
  • the RAN node may map the streams to DRBs (e.g., based on the configuration received at 2).
  • the RAN node may make scheduling decisions based on the PDU sets received over the split stream.
  • the RAN node may send the PDU to the WTRU over one or more data radio bearers.
  • the identification, mapping, and processing shown in the UPF may apply to DL traffic.
  • the same identification, mapping, and processing may apply at the WTRU for UL traffic.
  • a device and/or network may manage non-sequential PDU set SNs over a QoS flow.
  • Nonsequential PDU set SNs over a Qos flow may occur in one or more (e.g., two) scenarios.
  • the UPF may receive a first multiplexed traffic stream from the Application Server.
  • PDU sets from a (e.g., each) stream may be multiplexed.
  • the PDU set sequence numbers on the received multiplexed traffic stream may be non-sequential.
  • the UPF may generate a second multiplexed traffic stream (e.g., based on the first multiplexed traffic stream).
  • the UPF may receive multiple traffic streams (e.g., from one or more Application Servers).
  • the N4 rules may indicate for the UPF to multiplex the traffic streams over a third multiplexed stream.
  • the N4 rules may indicate for the UPF to send the third multiplexed traffic stream to the RAN node.
  • the UPF may encapsulate the PDU sets of the multiple traffic streams into GTP-U PDUs and send the GTP-U PDUs over the third multiplexed stream.
  • the network may handle (e.g., deal with) non-sequential PDU set SNs over a (e.g., single) QoS flow.
  • the RAN node may handle (e.g., deal with) non-sequential PDU set SNs for a QoS flow carrying multiplexed streams.
  • the RAN node may apply stream-based QoS to the QoS flow.
  • the RAN node may receive PDU sets on a QoS flow with non-sequential PDU set SNs (e.g., because of the multiplexing and splitting of streams at the UPF).
  • the RAN node may receive PDU sets from two or more (e.g., three) multiplexed streams (e.g., stream 1 , stream 2, stream 3).
  • the PDU sets from these (e.g., each of these) streams may have sequential PDU set SNs.
  • the multiplexed stream may have non-sequential PDU set SNs.
  • the RAN node may receive information (e.g., may need additional information) to help resolve the non-sequential PDU set SNs.
  • the UPF may provide this information to the RAN node.
  • the UPF may perform a mapping of the non-sequential PDU set SNs.
  • the mapping may involve one or more of the following.
  • the UPF may identify the individual streams (e.g., based on stream ID information carried in the RTP header).
  • the UPF may include the stream ID in a (e.g., each) PDU multiplexed in a QoS flow (e.g., QoS flow stream ID (QFSID)).
  • QFSID QoS flow stream ID
  • the UPF may identify the individual streams (e.g., based on information carried in the RTP header).
  • the UPF may generate a QFSID to include (e.g., in each PDU multiplexed in a QoS flow).
  • the QFSID may be provided as part of the N4 rules.
  • the UPF may set the PDU set SN equal to the PSSN carried in the RTP header.
  • the UPF may include the PDU set SN and/or the QFSID in the GTP-U packet header.
  • the RAN node may use the QFSID to identify which PDU sets are from the same stream.
  • the PDU set SNs may be sequential for an (e.g., each) identified stream.
  • the RAN node may use the QFSID to identify the PDU sets to apply to a (e.g., any) stream based QoS.
  • the mapping may involve one or more of the following.
  • the UPF may renumber the PDU set SN to compensate for the multiplexing and/or splitting of stream traffic. For example, the UPF may not use the PSSN as the PDU set SN. For example, the UPF may determine (e.g., make sure) that the PDU set SN is ordered sequentially across streams. The UPF may increase the PDU set SN for a (e.g., each) PDU set multiplexed on a QoS flow. For example, the UPF may increment the PDU set SN by 1 (e.g., for each PDU set transmitted to the RAN node). In this case, the RAN node may expect sequential PDU set SN for a (e.g., every) QoS flow.
  • the RAN node may not be able to determine the streams to which PDU sets arriving over the QoS flow belong.
  • the RAN node may not be able to provide stream-level QoS (e.g., any stream-level QoS).
  • the UPF may include stream level QoS parameter(s) with a (e.g., each) PDU set transmission.
  • the UPF may include the PSDB applied to the stream, the PSER applied to the stream, the FEC success ratio applied to the stream, and/or the like.
  • the RAN node may not be aware of the original PSSN of the PDU set.
  • the UPF may include an offset (e.g., SN_offset) with a (e.g., each) PDU set transmission.
  • the SN_offset may be used by the RAN node to recover the (e.g., original) PSSN associated with the PDU set.
  • the multiplexed stream may have a set of PDU sets (e.g., PDU set SN 1 of stream 1 , PDU set SN 1 of stream 2, PDU set SN 2 of stream 2, PDU set SN 3 of stream 2, PDU set SN of stream 1 , and/or PDU set SN 1 of stream 3).
  • the PDU set SNs may be mapped to a set of sequential PDU set sequence numbers (e.g., sequential PDU set SN 100 through sequential PDU set SN 105).
  • a (e.g., each) PDU set may be associated with (e.g., have) an SN offset.
  • the SN offset may be determined by subtracting the sequential PDU set SN (e.g., associated with the PDU set) from the PDU set SN.
  • the SN offset for sequential PDU set SN 100 through sequential PDU set SN 105 of the multiplexed stream may be 99, 100, 100, 100, 102, and 104, respectively. If the SN is modulo a maximum SN (e.g., max_SN), the subtraction may be considered a (modulo max_SN) subtraction.
  • the AF may assist the network in managing multiplexed XR streams or split XR streams (e.g., by providing information).
  • the AF may provision parameters related to how the UPF maps a stream to one or more QoS flows.
  • the parameters may enable/allow the AF to control how streams are transported over the core network and the radio access network.
  • the AF may prefer that the network send the PDU sets in order (e.g., guarantee in-order delivery of the PDU sets), provide similar QoS treatment for the PDU sets (e.g., all PDU sets) within a stream, or split the traffic (e.g., if deemed necessary or beneficial to meet a QoS specification).
  • the AF may configure the network, which may be a 5G network, with the XR stream-related information (e.g., using an API enhanced for multiplexed and/or split streams).
  • a NEF service API e.g., “Nnef_AFsessionWithQoS_Create”
  • stream information e.g., PDU set QoS specification/requirement per stream
  • indication of whether the network should provide similar treatment to all PDU sets of a stream e.g., which may be used by the AF to tell the network that it should try to map all PDU sets of the stream to the same QoS flow and/or DRB
  • an indication of whether the network should guarantee in-order delivery of PDU sets within a stream e.g., which may be used by the AF to tell the network that it expects PDU sets to arrive in order at the WTRU
  • an indication of whether the stream may be split e.g., which may be used by the AF to tell
  • the NEF service API may include multiplexing criteria.
  • the multiplexing criteria may provide one or more conditions that allow the multiplexing of certain streams (e.g., without including the stream IDs).
  • a multiplexing criterion may be multiplexing based on the types of PDU set QoS parameters provided for a (e.g., a) stream.
  • the criterion may indicate to include streams that have a PSIHI provided as PDU set QoS parameter multiplexed in the same QoS flow, and/or streams that have PSDB provided as a PDU set QoS parameter multiplexed together.
  • the N4 rules may include an indication of whether a stream (e.g., identified by a PDF) may be split.
  • the splitting may be done per PDU or per PDU set. If the stream can be split, the N4 rules may include how the split may be achieved.
  • the split may be based on PDU set importance (e.g., where a UPF may split a stream so that PDU sets of high importance are transported on one QoS flow, and PDU sets of lower importance are transported on another QoS flow).
  • the split may be based on PDU set size (e.g., where a UPF may split a stream so that large PDU sets are transported on one QoS flow, and smaller PDU sets are transported on another QoS flow).
  • the GBR may be split into a GBR allocation of 90Mbs for a QoS flow ID 1 and a GBR allocation of 10Mbps for QoS flow ID 2.
  • a first stream metadata may be the QoS flow stream ID (QFSID).
  • the 5GS may determine to renumber the stream IDs to resolvable values (e.g., because the RAN may not be able to differentiate PDUs from App1 and PDUs from App2 if they have the same stream ID A and are carried onto the same QoS flow 1).
  • the SMF may determine a renumbering rule and provide the renumbering rule to the UPF (e.g., use original stream ID and App ID to generate a stream ID).
  • the SMF may provide the renumbering rule to the WTRU (e.g., for the UL traffic). If the UPF determines the stream IDs mapping, the UPF may inform the SMF about the updated stream ID renumbering, and the SMF may send the updated mapping to the WTRU.
  • a second stream metadata may be an indication that a PDU is the last PDU of a stream.
  • the metadata may be used by the RAN node to determine that the next PDU set that will be received is from a different stream.
  • a third stream metadata may be an indication that a PDU is the first PDU of a stream.
  • the metadata may be used by the RAN node to determine that the PDU set being received is from a different stream than the last PDU set received.
  • a fourth stream metadata may be associated with PDUs of streams that are split across QoS flows. This may include one or more of the following: an indication that the preceding (e.g., prior) PDU set(s) for this stream was (were) sent on another QoS flow; the number of PDU sets that were transported over the other QoS flow; an indication that the proceeding (e.g., next) PDU set for this stream will be sent on another QoS flow; the number of PDU sets that will be transported over the other QoS flow; a list of one or more PDU set SNs that are sent on another QoS flow; a list of one or more (PDU set SN, QFSID) pairs (e.g., that identifies the PDU set SNs of stream (QFSID) that are sent on another QoS flow, which may allow the UPF to send information about stream ‘j’ over PDUs of stream ‘k’); the QoS flow ID that transports the split stream (e.g., the
  • a fifth stream metadata may be an SNJDffset. This may be used in option 2 to manage nonsequential PDU set SNs.
  • the RAN node may add the SN_offset to the received PDU set SN to recover the original PSSN of the PDU set.
  • a sixth stream metadata may be related to stream-based QoS.
  • the metadata may include the PSER to apply to this PDU set, the PSDB to apply to this PDU set, the PSIHI to apply to the PDU set, the AL FEC success ratio to apply to the PDU set, and/or the like.
  • the sixth stream metadata may be sent as values or as an index to a table of values.
  • the table of values may have been provided a priori to the RAN node, for example, in the QoS profile.
  • the index may point to a specific value in the table of values.
  • the configuration information may include stream-based QoS parameters.
  • the stream-based QoS parameters may include PSER to apply to a PDU set of this stream, the PSDB to apply to a PDU set of this stream, the PSIHI to apply to a PDU set of this stream, the AL FEC success ratio to apply to a PDU set of this stream, and/or the like.
  • the RAN node may make scheduling decisions based on awareness that PDU sets arriving over different QoS flows belong to the same stream.
  • An example application of the fourth RAN node action may be in the case of video l-frames and video P-frames.
  • a video P-frame sent over a QoS flow 2 with PSSN 10 may arrive at the RAN node before a PDU set with PSSN 9, which is sent over QoS flow 1 and is a video l-frame.
  • the RAN node may wait for the video l-frame to arrive before deciding to send the video P-frame (e.g., because loss of the video l-frame may render sending the video P-frame to the WTRU not useful).
  • the entities performing the processes described herein may be logical entities that may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of, and executing on a processor of, a mobile device, network node or computer system. That is, the processes may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of a mobile device and/or network node, such as the node or computer system, which computer executable instructions, when executed by a processor of the node, perform the processes discussed. It is also understood that any transmitting and receiving processes illustrated in figures may be performed by communication circuitry of the node under control of the processor of the node and the computer-executable instructions (e.g., software) that it executes.
  • software e.g., computer-executable instructions
  • the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.

Landscapes

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

Abstract

L'invention concerne des systèmes, des procédés et des instruments de traitement d'informations d'ensembles d'unités de données par paquets (PDU) pour des flux de données multiplexées. Un nœud de réseau peut générer un flux de données multiplexées comprenant un premier ensemble de PDU, un second ensemble de PDU et une indication de numéros de séquence d'ensembles de PDU non séquentiels. Le premier ensemble de PDU peut être associé à un premier flux de données. Le second ensemble de PDU peut être associé à un second flux de données. Le dispositif peut déterminer un premier mappage entre un premier sous-ensemble des numéros de séquence d'ensembles de PDU non séquentiels et des premiers numéros de séquence d'ensembles de PDU séquentiels associés au premier flux de données. Le dispositif peut déterminer un second mappage entre un second sous-ensemble des numéros de séquence d'ensembles de PDU non séquentiels et des numéros de séquence d'ensembles de PDU séquentiels associés au second flux de données. Le dispositif peut envoyer le flux de données multiplexées, une indication du premier mappage et une indication du second mappage.
PCT/US2025/023236 2024-04-04 2025-04-04 Caractéristiques associées à des informations d'ensembles de pdu pour flux de données multiplexées Pending WO2025213076A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463574359P 2024-04-04 2024-04-04
US63/574,359 2024-04-04

Publications (1)

Publication Number Publication Date
WO2025213076A1 true WO2025213076A1 (fr) 2025-10-09

Family

ID=95560628

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/023236 Pending WO2025213076A1 (fr) 2024-04-04 2025-04-04 Caractéristiques associées à des informations d'ensembles de pdu pour flux de données multiplexées

Country Status (1)

Country Link
WO (1) WO2025213076A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023211049A1 (fr) * 2022-04-28 2023-11-02 주식회사 케이티 Procédé et dispositif pour contrôler un traitement de données par paquets
WO2023220938A1 (fr) * 2022-05-17 2023-11-23 Zte Corporation Procédé, dispositif et produit-programme d'ordinateur destinés aux communications sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023211049A1 (fr) * 2022-04-28 2023-11-02 주식회사 케이티 Procédé et dispositif pour contrôler un traitement de données par paquets
EP4518283A1 (fr) * 2022-04-28 2025-03-05 KT Corporation Procédé et dispositif pour contrôler un traitement de données par paquets
WO2023220938A1 (fr) * 2022-05-17 2023-11-23 Zte Corporation Procédé, dispositif et produit-programme d'ordinateur destinés aux communications sans fil
US20250024317A1 (en) * 2022-05-17 2025-01-16 Zte Corporation Method, device and computer-readable storage medium for wireless communication

Similar Documents

Publication Publication Date Title
US20200053835A1 (en) Uu interface enhancement for nr v2x
EP3451787A1 (fr) Procédés et appareils permettant de partager une couche physique entre de multiples entités de communication sans fil
WO2020167914A1 (fr) Adaptation de livre de codes harq-ack
WO2020223453A2 (fr) Harq en boucle ouverte dans des systèmes sans fil
WO2025019413A1 (fr) Prise en charge de conflits d'accès relatifs au contrôle d'accès au support entre une unité de transmission/réception sans fil et une wtru relais
US20240196265A1 (en) Pdu-based priority level determination within a downlink qos flow
WO2019005712A1 (fr) Transmission en liaison montante sans autorisation de liaison montante
WO2024163898A1 (fr) Communications associées à une importance relative
WO2025019405A1 (fr) Unité d'émission/réception sans fil (wtru) à un support de conflit d'accès de commande d'accès au support (mac) de relais de wtru
EP4613013A1 (fr) Sélection de support radio dynamique associée à des opérations ai/ml
WO2024124020A1 (fr) Transmissions en liaison montante utilisant une priorité basée sur un ensemble de pdu dans un flux qos
EP4646872A1 (fr) Gestion de liaison de bout en bout par l'intermédiaire d'un relais wtru-à-wtru
WO2025213076A1 (fr) Caractéristiques associées à des informations d'ensembles de pdu pour flux de données multiplexées
US20250358676A1 (en) Active discarding based on pdu set correlation
WO2025096988A1 (fr) Flux de qos avec flux de xr multiplexés
EP4612954A1 (fr) Modification de règles de flux de qos
WO2024163887A1 (fr) Utilisation d'une importance relative en association avec une session de pdu
WO2024163877A1 (fr) Importance relative et facteur de rejet associés à la détermination de l'éligibilité de rejet de paquets
WO2024163869A1 (fr) Détermination de l'importance relative d'un ensemble de pdu associée à un flux de qos
WO2025024100A1 (fr) Procédé et nœud réseau pour planification sensible au retard pour flux d'ensembles d'unités de données de protocole (pdu)
WO2024233978A1 (fr) Procédés, architectures, appareils et systèmes pour permettre un accès à trajets multiples sensible à la réalité étendue
WO2025024381A1 (fr) Procédés, architectures, appareils et systèmes de multiplexage et de différenciation de flux d'ensembles de pdu
WO2025097013A1 (fr) Procédés et appareil de prise en charge de débit binaire adaptatif pour trafic xr dans des réseaux de communication
WO2025034750A1 (fr) Sélection ou resélection de ressources pour une opération de réception discontinue de liaison latérale sur une wtru à sauts multiples vers des relais wtru
WO2025117772A1 (fr) Procédés, architectures, appareils et systèmes de formation et d'assertion de groupes d'unités de données dans des réseaux 3gpp activés par 3gpp et mise en réseau sensible au temps (tsn)

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

Country of ref document: EP

Kind code of ref document: A1