[go: up one dir, main page]

WO2025029919A1 - Améliorations de système 5gs sensibles à la latence de bout en bout pour xrm - Google Patents

Améliorations de système 5gs sensibles à la latence de bout en bout pour xrm Download PDF

Info

Publication number
WO2025029919A1
WO2025029919A1 PCT/US2024/040390 US2024040390W WO2025029919A1 WO 2025029919 A1 WO2025029919 A1 WO 2025029919A1 US 2024040390 W US2024040390 W US 2024040390W WO 2025029919 A1 WO2025029919 A1 WO 2025029919A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
latency
pdb
message
value
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/US2024/040390
Other languages
English (en)
Inventor
Achref METHENNI
Michael Starsinic
Rocco Di Girolamo
Michel Roy
Magurawalage Chathura SARATHCHANDRA
Xavier De Foy
Samir Ferdi
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 WO2025029919A1 publication Critical patent/WO2025029919A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • a fifth generation of mobile communication radio access technology may be referred to as 5G new radio (NR).
  • a previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long term evolution (LTE).
  • a first network node may receive a first message from a second network node.
  • the first message may indicate end-to-end (E2E) latency information.
  • the first network node may determine a packet delay budget (PDB) value for a data flow based on the E2E latency information.
  • the first network node may generate a policy and charging control (PCC) rule based on the E2E information.
  • the first network node may send a second message to a third network node.
  • the second message may indicate the PCC rule, and the PCC rule may include a PDB value.
  • the first network node may receive a third message from the second network node.
  • the third message may indicate an E2E latency measurement and that the E2E latency measurement is below (or above) a threshold.
  • a measurement below the threshold may indicate that the E2E latency is satisfactory, reflecting that the latency is less than the maximum acceptable E2E latency.
  • a measurement above the threshold may indicate that the E2E latency is not satisfactory.
  • the second network node may send the E2E latency measurement, and the measurement may be either above or below the threshold.
  • the first network node may update the PCC rule based on the E2E latency measurement.
  • the first network node may send a fourth message to a third network node.
  • the fourth message may include the updated PCC rule.
  • the PDB value may be a first PDB value.
  • the updated PCC rule may include a second PDB value.
  • the first PDB value may be different from the second PDB value.
  • the first network node may send a fifth message to the second network node, and the fifth message may indicate an issue with a delay requirement.
  • the first network node may determine a Quality of Service (QoS) Identifier (QI) associated with the data flow.
  • QoS Quality of Service
  • QI Quality of Service
  • the PCC rule may include the QFI and may be associated with the data flow.
  • the PCC rule may include a Quality of Service (QoS) monitoring policy associated with the E2E latency information.
  • the first network node may include a policy control function (PCF), the second network node may include an application function (AF), and the third network node may include a session management function (SMF).
  • PCF policy control function
  • AF application function
  • SMF session management function
  • Systems, methods, and instrumentalities may be configured for end-to-end latency aware system enhancements for extended reality and multimodal interactions (XRM).
  • a first network node e.g., PCF
  • the first message may indicate an end-to-end latency requirement and/or a Quality of Service (QoS) parameter (e.g., requirement) for an XRM service.
  • QoS Quality of Service
  • the first network node may generate a QoS monitoring policy based on the QoS requirement.
  • the first network node may generate a Policy and Charging Control (PCC) rule based on the QoS monitoring policy.
  • the first network node may send a second message to a third network node (e.g., SMF).
  • the second message may indicate a PCC rule.
  • the first network node may receive a third message from the second network node.
  • the third message may indicate an end-to-end latency measurement.
  • the first network node may update the PCC rule based on the end-to-end latency measurement.
  • the first network node may send a fourth message to the third network node.
  • the fourth message may include the updated PCC rule.
  • the Quality of Service (QoS) parameter(s) may be associated with at least one of a source IP address, a destination IP address, or a source port number, a destination port number.
  • the first network node may send a first notification message to the second network node
  • the first notification message may indicate a QoS adjustment to be used to trigger an end-to-end latency measurement.
  • the first network node may send a second notification message to the second network node to prompt one or more application layer changes.
  • the end-to-end latency measurement may be a first end-to-end latency measurement.
  • FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG.1B 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.1C 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.1A according to an embodiment.
  • FIG.1D 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 of end-to-end latency detection and packet delay budget (PDB) adjustment.
  • PDB packet delay budget
  • 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 unique word OFDM
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 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 (UE), 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 (IoT) 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.
  • UE user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • a netbook a personal computer
  • 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 Internet 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 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA20001X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG.1A 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 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • 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.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG.1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG.1B 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 processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122.
  • 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.
  • a base station e.g., the base station 114a
  • 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 transmit/receive element 122 is depicted in FIG.1B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • 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 IEEE 802.11, for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • 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 power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
  • 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.
  • 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 track
  • 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.
  • 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)).
  • FIG.1C 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.
  • Each of the eNode-Bs 160a, 160b, 160c 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, and the like.
  • the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG.1C 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 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 each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • 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.
  • the CN 106 may facilitate communications with other networks. For example, 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.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • 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 WTRU is described in FIGS.1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • 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 BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • DS Distribution System
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic.
  • 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.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) 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 may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA e.g., only one station
  • 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.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • 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
  • 802.11af and 802.11ah The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac.802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 802.11ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • 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.11n, 802.11ac, 802.11af, and 802.11ah, 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
  • FIG.1D 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 gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • 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.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • 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.1D, 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.1D 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. [0060]
  • 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.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • the AMF 182 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.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • 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 test equipment.
  • Direct RF coupling and/or wireless communications via RF circuitry may be used by the emulation devices to transmit and/or receive data.
  • Reference to a timer herein may refer to a time, a time period, tracking the time, tracking the period of time, etc.
  • Reference to a timer expiration herein may refer to determining that the time may have occurred or that the period of time may have expired.
  • 5GS 5G System 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Function AN Access Network API Application Programming Interface AS Application Server CN Core Network DL Downlink DNN Data Network Name E2E End-to-End IP Internet Protocol NEF Network Exposure Function NG-RAN Next Generation Radio Access Network PCC Policy Charging and Control PCF Policy Control Function PDB Packet Delay Budget PDU Protocol Data Unit PSA PDU Session Anchor QoS Quality of Service RAN Radio Access Network SMF Session Management Function S-NSSAI Single Network Slice Selection Assistance Information TE Terminal Equipment UE User Equipment UL Uplink UPF User Plane Function VR Virtual Reality XR Extended Reality XRM Extended and Multimodal Reality [0069] A PCF may be provisioned for E2E latency information, may set up E2E aware policies, and may receive E2E latency measurement and adjust delays.
  • a PCF may perform the following actions.
  • the PCF may receive a request from the AF via the NEF.
  • the request may be a Npcf_PolicyAuthorization request from the NEF.
  • the request may include an address of the WTRU (e.g., IP address), traffic flow description, a requested delay (e.g., a 5GS requested delay) , and end-to-end latency information.
  • the E2E latency information may include one or more of the following: E2E latency adjustment requirement indication, E2E latency requirement value, E2E latency measurement value, N6 latency check frequency, E2E latency jitter value, E2E latency jitter duration, E2E latency out-of-range count, and/or target E2E latency value.
  • the PCF may use the received end-to-end latency information to determine a PDB value for the flow (e.g., the data flow).
  • the QoS Identifier may refer to a QoS Flow Identifier (QFI), which may be used to associate traffic with an appropriate QoS flow.
  • QFI QoS Flow Identifier
  • QI and/or QFI may be used interchangeably herein with a 5QI to reflect QoS parameters (e.g., 5G QoS parameters, such as a 5G QoS identifier (5QI)).
  • the PCF may use the PDB to determine a QoS Identifier (QI), such as a 5QI, to associate with the flow and create a PCC Rule, which may include information about the flow and the determined QI (e.g., 5QI).
  • QI QoS Identifier
  • the PCF may include a QoS monitoring policy in the PCC rule and may determine and set the reporting frequency of the QoS monitoring policy based on the N6 latency check frequency.
  • the PCF may include a maximum CN PDB in the PCC rule that is sent to the SMF.
  • the PCF may send PCC rules to SMF.
  • the PCF may receive a new end-to-end latency measurement value from the AF via the NEF.
  • the message from the AF may indicate to the NEF and PCF how much the E2E latency measurement is in or out of range.
  • the PCF may determine that the E2E latency measurement does not meet the threshold (e.g., exceed the threshold or is lower than a target E2E latency value).
  • the PCF may use the determination and the E2E latency measurement to update the PCC rule, e.g., to update and determine a PDB value (e.g., a new PDB value).
  • the PCF may choose to assign a PDB that is larger than a PDB that is associated with the flow, or larger than the requested delay (e.g., 5GS delay).
  • the PCF may choose to use/assign a PDB that is lower than the PDB that is associated with the flow, or lower than the requested delay (e.g., 5GS delay).
  • the PCF may send one or more PCC rules (e.g., new PCC rules) to the SMF.
  • the PCF may send a notification to the AS if an adjustment were made to tell the AS that QoS parameters that are associated with the flow have been adjusted to improve the end-to-end latency that is associated with the traffic.
  • the PCF may send a notification to the AS if the PCF determines that the PDB that is determined to accommodate the E2E latency parameter (e.g., requirement) provided by the AF cannot be met by the system (e.g., the 5GS).
  • the PCF may send a message to the AF via the NEF to notify the AF of the event.
  • an application function and application server may be used interchangeably.
  • WTRU hosted application may be used herein to refer to an application hosted on a WTRU, or an application hosted on a device tethered to the WTRU.
  • a user plane latency parameter e.g., requirement
  • An application function may provide a user plane latency parameter (e.g., requirement) to the 5GS.
  • the user plane latency parameter (e.g., requirement) may include information, such as a maximum allowed user plane latency.
  • the maximum allowed user plane latency may characterize the target user plane latency.
  • the maximum allowed user plane latency may represent a maximum value for a considered user plane latency to meet.
  • a user plane latency parameter (e.g., requirement) requested by an AF is authorized by a network node (e.g., a PCF)
  • the AF request including the parameter (e.g., requirement)
  • the SMF may take actions to meet the parameters (e.g., requirements), for example, by reconfiguring the user plane of the PDU Session.
  • the SMF may decide to perform an PSA UPF relocation if the target PSA UPF satisfies the maximum user plane latency.
  • the packet delay budget (PDB) may define an upper bound for the time a packet may be delayed between the WTRU and the N6 termination point at the UPF.
  • a packet delay budget may be considered to be the sum of a Core Network Packet Delay Budget (CN PDB) and an Access Network Packet Delay Budget (AN PDB), such as a 5G-AN PDB.
  • the CN PDB may be the portion of the overall PDB that is allocated to the time it takes traffic to move between the PSA UPF and the 5G Access Network.
  • the PSA UPF may be the N6 termination point.
  • the AN PDB (e.g., 5G-AN PDB) may be the portion of the overall PDB that is allocated to the time it takes traffic to move between the WTRU and the access network (e.g., 5G access network).
  • a WTRU may be able to connect to the system (e.g., 5GS).
  • the WTRU may be connected to devices via tethering.
  • the devices may be multi-modal display devices, such as VR glasses, haptic gloves, and the like.
  • the multi-modal traffic may be provided by an application server, which may be trusted or untrusted and may be a distant server or an edge server.
  • the AS may provide multimodal traffic to the WTRU.
  • the traffic may be sent to a PSA UPF, which may forward the traffic to the WTRU in the user plane dedicated to the traffic.
  • the traffic may be processed by the WTRU and forwarded to the tethered devices for an immersive experience (e.g., a full, immersive experience).
  • a type of XRM traffic may pose information, which may indicate that a change of pose of a VR headset may have occurred.
  • the pose information may be sent in the uplink from the tethered device to the WTRU and to the PSA UPF via the system (e.g., 5GS).
  • the PSA UPF may receive the traffic and send the traffic to the AS.
  • a PSA UPF may be a user data terminating point between the system and AS.
  • Downlink and uplink traffic may go by (e.g., to) a PSA UPF.
  • the PSA UPF may forward the traffic to the AS in the uplink direction (e.g. pose information).
  • the AS server may use the traffic to provide the corresponding XRM traffic (e.g., video) based on the pose information.
  • Parameters e.g., requirements
  • the motion to photon parameter e.g., requirement
  • the latency of the user plane may be considered between the WTRU and the anchor UPF.
  • the WTRU may establish a PDU session that may be used to carry traffic between the WTRU and the UPF.
  • Parameters e.g., such as a packet delay budget (PDB)
  • PDB packet delay budget
  • Parameters such as CN PDB for the RAN to PSA UPF delay and An PDB (e.g., 5G-AN PDB) may characterize the radio latency.
  • CN PDB for the RAN to PSA UPF delay
  • An PDB e.g., 5G-AN PDB
  • the latency between the WTRU and a tethered device may be considered.
  • the WTRU may be able to request a delay (e.g., a non-3GPP delay) for the link between the WTRU and a tethered device.
  • the system e.g., 5GS
  • the system e.g., 5GS
  • the E2E latency of XRM traffic may be used to refer to the latency between the application (e.g., hosted at the WTRU or in a device tethered to the WTRU) and the application server.
  • An E2E latency may exist for uplink traffic (e.g., between the application and AS) and for downlink traffic (e.g., between the AS and the application).
  • the uplink E2E latency and downlink E2E latency may not be the same.
  • the latency between the PSA UPF and the AS may impact the overall E2E latency of XRM traffic, and the system (e.g., 5G system) may not (e.g., may not be able to) dynamically adjust for changes in the latency between the PSA UPF and AS.
  • the delay between the PSA UPF and AS may be referred to as the N6 delay.
  • Mechanisms may allow the system (e.g., 5GS) to detect the E2E latency of XR traffic flows (e.g., including the N6 delay).
  • system modifications e.g., enhancements
  • the network may reduce the end-to-end latency.
  • the PCF may receive a request from the AF via the NEF which may include a WTRU address, traffic flow description, requested delay (e.g., 5GS requested delay); or end-to-end latency information such as an E2E latency adjustment parameter (e.g., parameter (e.g., requirement)) indication, E2E latency parameter (e.g., requirement) and/or measurement value, N6 latency check frequency; a combination thereof, and/or the like.
  • the PCF may use E2E latency information to determine a PDB value for the flow.
  • the PCF may create one or more corresponding PCC rules and send the one or more PCC rules to the SMF.
  • the one or more PCC rules may include a QoS monitoring policy with the reporting frequency of the QoS monitoring policy based on the N6 latency check frequency.
  • the one or more PCC rules may include a maximum CN PDB.
  • the PCF may receive an end-to-end latency measurement value (e.g., new end-to-end latency measurement value) from the AF via the NEF.
  • the PCF may use the end-to-end latency measurement value to determine that the E2E latency measurement does not meet the threshold (e.g., exceed the threshold or is lower than the target E2E latency value).
  • the PCF may use the determination and the E2E measurement to try to update the one or more PCC rules, e.g., by determining a PDB value (e.g., new PDB value).
  • the PCF may send the rules (e.g., new rules) to the SMF and send a notification to the AS to inform the SMF and the AS of the adjusted parameters (e.g., new adjusted parameter) that was determined, or that the PDB determined cannot be met by the 5GS.
  • the PCF may receive a request from the AF via the NEF, which may include at least one of a WTRU address; traffic flow description; requested delay (e.g., 5GS requested delay); or end-to-end latency information such as an E2E latency adjustment parameter (e.g., requirement) indication, E2E latency parameter (e.g., requirement), measurement value, N6 latency check frequency, a combination thereof, and/or the like.
  • the PCF may use E2E latency information to determine a PDB value for the flow and create a corresponding PCC rule and send them to the SMF.
  • the PCC rule may include a QoS monitoring policy with the reporting frequency of the QoS monitoring policy based on the N6 latency check frequency.
  • the PCC rule may include a maximum CN PDB.
  • the PCF may receive an end-to-end latency measurement value (e.g., a new end-to-end latency measurement value) from the AF via the NEF.
  • the PCF may use the information to determine that the E2E latency measurement does not meet the threshold, e.g., exceed the threshold, or is lower than target E2E latency value.
  • the PCF may use the determination and the E2E measurement to attempt to update the PCC rule, e.g., by determining a new PDB value.
  • the PCF may send the rules (e.g., new rules) to the SMF and send a notification to the AS to inform the SMF and the AS of the adjusted parameter (e.g., new adjusted parameter) that was determined, or that the PDB determined cannot be met by the system (e.g., 5GS).
  • An E2E latency parameter (e.g., requirement) may be satisfied by adjusting packet delay budgets.
  • FIG.2 illustrates an example of end-to-end latency detection and PDB adjustment. (e.g., where an application server may provide end-to-end latency measurements and end-to-end latency requirements to the PCF in the 5G core network).
  • the example procedure may explain how the PCF may use the measurement and parameter (e.g., requirement) information to determine core network and access network packet delay budgets.
  • the system e.g., 5G system
  • the application server/function may provide the 5GS with information regarding an XRM service.
  • the AF may invoke an Nnef_AFsessionWithQoS API operation of the NEF. The AF may use the API to provide QoS requirements for the XRM service.
  • the service invocation may identify the WTRU that the QoS requirements apply to and the flows of the WTRU that the QoS requirements apply to.
  • the flows may be identified by a combination of source and destination IP addresses and port numbers.
  • the AF may provide a DNN/S-NSSAI combination when invoking the API to indicate that the QoS parameters (e.g., requirements) apply to traffic in a PDU Session of the WTRU that is associated with the indicated DNN/S-NSSAI combination.
  • a QoS parameter (e.g., QoS requirement) that may be provided by the AF may be a delay value (e.g., 5GS delay value) that represents an upper delay bound that the AF requests for the traffic as it passes through the system (e.g., 5GS).
  • the delay value (e.g., 5GS delay value) may be a request to limit the delay that is incurred as the traffic passes between the WTRU and UPF.
  • the AF may provide a QoS reference value (e.g., in the E2E latency information) which the PCF may translate to a delay value (e.g., a PDB value). The translation may be based on information that may be provisioned in the PCF.
  • the Nnef_AFsessionWithQoS API may be used by the AF to provide the following end-to-end latency Information to the NEF.
  • the end-to-end latency information may include an end-to-end latency adjustment parameter (e.g., requirement) indication.
  • the indication may be used to indicate to the system (e.g., 5G System) that the system may account for the N6 delay.
  • the end-to-end latency information may include an end-to-end latency parameter (e.g., requirement) value.
  • the latency parameter (e.g., requirement) may represent the upper bound on the latency of traffic between the WTRU hosted application and the application server.
  • the end-to-end latency information may include an end-to-end latency measurement value.
  • the measurement may represent the measured latency between an application that is hosted on the WTRU and an application server.
  • the value may be expressed in seconds.
  • the application that is hosted on the WTRU may be hosted in the TE part of the WTRU or on a device that is tethered to the WTRU.
  • the end-to-end latency information may include an N6 latency check frequency.
  • the value may represent how often the AS requests that the network check the N6 latency.
  • the end-to-end latency information may include an end-to-end latency jitter value. The value may indicate an acceptable variation above the end-to-end latency measurement that may be acceptable without triggering packet delay adjustment.
  • the end-to-end latency information may include an end-to-end latency jitter duration.
  • the value may indicate a duration for w [0107] hich the end-to-end latency measurement may be above the maximum and within the end-to-end latency jitter variation without triggering packet delay adjustment. If the end-to-end latency jitter duration is not specified, a packet delay adjustment may not be triggered as long as the value remains within the end- to-end latency jitter variation.
  • the end-to-end latency information may include an end-to-end latency out-of-range count.
  • the value may indicate, based on the N6 measurement frequency, a number of measurement iterations that may be above the maximum latency and within the end-to-end jitter value (if specified) before triggering packet delay adjustment.
  • the end-to-end latency information may include a target end-to-end latency value.
  • the value may indicate a target latency for the E2E latency that the application server or the system (e.g., 5GS) attempts to maintain.
  • the value may be relevant, for example, in the context of collaborative gaming (e.g., where getting equivalent latencies for a player may be more important than getting the lowest latency).
  • the NEF may invoke an Npcf_PolicyAuthorization API operation of the PCF to provide the parameters that were received from the AF to the PCF.
  • the Npcf_PolicyAuthorization API may be enhanced so that the end-to-end latency information may be provided to the PCF.
  • the PCF may create a QoS monitoring policy for the flows that are associated with end-to-end latency information.
  • the PCF may generate PCC rules for the PDU session that carries the flows, and the QoS monitoring policy may be included in the PCC rules.
  • the PCF may use the delay value (e.g., 5GS delay value) to determine a PDB value for the flow.
  • the PDB value may be set to (approximately) the same value as the delay (e.g., 5GS delay).
  • the PCF may derive a packet delay budget value for the specific XR service data flow based on the end-to-end latency information (e.g., including the end-to-end latency parameter (e.g., requirement) and/or measurement value (e.g., delay measurement value), and may use local policies to determine what percentage of those values may account for the delay (e.g., 5GS delay).
  • the PCF may set the value determined by the PCF to be a PDB value for the flow.
  • the end-to-end latency requirement value and the end-to-end latency measurement value may be included in end-to-end (E2E) latency information.
  • the PCF may use the end-to-end latency parameter (e.g., requirement) value and an end-to-end latency measurement value to determine a PDB value for the flow.
  • an end-to-end latency parameter e.g., requirement
  • an end-to-end latency measurement value e.g., in the end-to-end latency information
  • the PCF may assign a PDB that is larger than a PDB that is (e.g., currently) associated with the flow or larger than the requested delay (e.g., 5GS delay).
  • the PCF may choose to assign a PDB that is lower than a PDB that is (e.g., currently) associated with the flow or lower than the requested delay (e.g., 5GS delay).
  • the PCF may use the PDB to determine a QI (e.g., 5QI) to associate with the flow.
  • the PCF may create a PCC rule that includes information about the flow (e.g., including the PDB (value) and the determined QI (e.g., 5QI).
  • the PCF may include a QoS monitoring policy in the PCC Rule.
  • the PCF may determine and set the reporting frequency of the QoS monitoring policy based on the N6 latency check frequency.
  • the PCF may include a maximum CN PDB in the PCC rule that is sent to the SMF.
  • the maximum CN PDB value may be used by the SMF to determine how to set the CN PDB and used to determine an appropriate AN PDB (e.g., 5G-AN PDB) to signal to the NG-RAN Node in the QoS profile.
  • the SMF may be configured to associate CN PDB values with UPF and RAN Node combinations.
  • the SMF may use the maximum CN PDB during UPF selection and re-selection procedures to determine that a selected UPF does not result in a path delay that may be larger (e.g., may be too large).
  • the SMF may be configured with information about the path delay between the RAN node that the WTRU is connected to and the UPFs that are available to be selected.
  • the SMF may select a UPF that is associated with a delay that is small (e.g., relatively small), so that the overall delay that is associated with the PDU Session does not exceed the delay parameters (e.g., requirements) that are indicated in the PCC rules and/or the parameters (e.g., requirements) of the application traffic.
  • the SMF may determine that a UPF is eligible to be selected/re-selected if the configured CN PDB value for the UPF is lower than the maximum CN PDB value provided by the PCF. [0119] If multiple UPFs include the parameters described herein, the SMF may choose to select among the UPFs, the UPF which may have the lowest CN PDB value.
  • the selection procedure may help reduce the total path delay, which may include the CN delay, the AN delay (e.g., 5G-AN delay), and the N6 delay.
  • the end-to-end latency jitter value, end-to-end latency jitter duration, and end-to-end latency out- of-range count may be used by the PCF to configure the PCC rule, so that the PCC rule indicates to the SMF that jitter measurements may be performed by the UPF, and the measurement values may be reported to the PCF.
  • the PCF may compare the measurements that are received from the UPF against the end-to-end latency jitter value, end-to-end latency jitter duration, and end-to-end latency out-of-range count (e.g., the end-to-end latency jitter value, end-to-end latency jitter duration, and end-to-end latency out-of-range count may be included in the end-to-end latency information).
  • end-to-end latency jitter value, end-to-end latency jitter duration, and end-to-end latency out-of-range count may be included in the end-to-end latency information.
  • the PCF may use the comparison to determine a PDB value or determine whether an additional delay may be injected at the UPF (e.g., the PCF may determine a packet delay budget (PDB) value for a data flow based on the end-to- end latency information, such as the end-to-end latency requirement and/or delay measurement, and generate a PCC rule(s) based on the end-to-end latency information). For example, a (e.g., additional) delay may be added to the PDB based on the end-to-end delay measurement exceeding the end-to-end latency requirement [0121]
  • the PCF may send PCC rules to the SMF.
  • the SMF may use the PCC rules to generate N4 rules and send them to the UPF.
  • the SMF may use the PCC rules to generate QoS profiles and send them to the NG-RAN Node.
  • the SMF may use the PCC rules to generate QoS rules and send them to the WTRU.
  • the PCC rules that are received by the SMF from the PCF may be affected (e.g., enhanced) to include a maximum CN PDB.
  • the maximum CN PDB value may be used by the SMF to determine how to set the CN PDB and used to determine an AN PDB (e.g., a 5G-AN PDB) to signal to the NG-RAN node in the QoS profile.
  • the SMF may use the maximum CN PDB during UPF selection and re-selection procedures.
  • QoS rules, QoS profiles, and N4 Rules may describe the QoS treatment that may be associated with traffic flows.
  • QoS rules may be sent from the SMF to the WTRU.
  • QoS profiles may be sent from the SMF to the RAN node.
  • N4 Rules may be sent from the SMF to the UPF.
  • Packet delay budget information may be considered by the SMF when determining what type of QoS treatment to associate with a flow. Packet delay budget information may be considered by the SMF when determining what QoS Flow a traffic flow may be associated with.
  • the PCF may use the end-to-end latency to derive a PDB for the 5GS.
  • the PCF may use the derived PDB value to determine a QI (e.g., 5QI) to associate with the flow.
  • the QI value (e.g., 5QI value) may be included in the generated PCC rules.
  • the PCC rules may include a maximum CN PDB.
  • the PCF may derive an N4 rule from the generated PCC rule.
  • the N4 rule may include the 5QI information that is derived by the PCF from the PDB (e.g., derived by the PCF from the PDB early on).
  • the N4 rule may include the maximum CN PDB.
  • the maximum CN PDB value may be used by the SMF to determine how to set the CN PDB and to determine a An PDB (e.g., 5G-AN PDB) to signal to the NG-RAN Node in the QoS profile.
  • the network e.g., the SMF or PCF
  • the PCF may send a message to the AF via the NEF to notify the AF of the event.
  • the message may trigger the AS/AF to perform application layer changes.
  • the application server may choose a (e.g., different) codec configuration for the video traffic which may lower the quality of the video traffic. By lowering the video quality, the E2E latency parameter (e.g., requirement) may be lowered.
  • the AF may perform an E2E latency measurement and provide the end-to-end latency measurement value to the NEF.
  • the AF may provide the end-to-end latency measurement value to the NEF by invoking the Nnef_AFsessionWithQoS API.
  • the NEF may provide the end-to-end latency measurement value to the PCF by invoking the Npcf_PolicyAuthorization API.
  • the message from the AF may indicate to the NEF and PCF how much the E2E latency measurement may be in or out of range.
  • the message may indicate that the E2E latency measurement was a number of seconds too large, and user experience may be poor.
  • the message may indicate that the E2E latency measurement was a number of seconds under the threshold, and user experience may be expected to be acceptable.
  • the system e.g., the PCF or the SMF
  • the system may determine that the E2E latency measurement may have exceeded the threshold by fcomparing the reported measurement value to the E2E latency parameter (e.g., requirement).
  • the system may measure the WTRU-PSA UPF delay, the system (e.g., 5GS) may deduce the N6 delay once the system receives the E2E latency measurement. In examples, the system may determine that the N6 delay is large (e.g., too large).
  • the PCF may use the N6 delay to calculate an E2E latency measurement by adding the N6 delay to the WTRU to PSA UPF delay.
  • the E2E latency measurement may be compared to the E2E latency parameter (e.g., requirement). If the E2E latency measurement is larger than the E2E latency measurement, the PCF may determine that the N6 delay may be too large. [0130] If the AF has provided a target E2E latency value, the 5GS, e.g., the PCF, may compare the reported E2E delay measurement.
  • the PCF may determine to adjust the PCC rules to add an additional delay to the PDB value or instruct the UPF via the SMF to inject a certain delay.
  • the PCF may determine how much delay may be injected based on the target end-to-end latency value and the delay measurements.
  • the PCF may determine to use the E2E latency measurement to update the PCC rules.
  • the PCF may update the PCC rules, as described at 2.
  • the PCF may send PCC rules to the SMF.
  • the SMF may use the PCC rules to generate the N4 rule and send the N4 rules to the UPF.
  • the SMF may use the PCC rules to generate QoS profiles and send QoS profiles to the NG-RAN node.
  • the SMF may use the PCC rules to generate QoS rules and send QoS rules to the WTRU.
  • the PCF may use the end-to-end latency measurement to derive a PDB (e.g., a new PDB) for the system (e.g., 5GS).
  • the PCF may use the derived PDB value to determine a QI (e.g., 5QI) to associate with the flow.
  • the QI value (e.g., 5QI value) may be included in the generated PCC rules.
  • the PCC rules may include a maximum CN PDB.
  • the PCF may derive an N4 rule from the generated PCC rule.
  • the N4 rule may include the QI information (e.g.,5QI information) that may be derived from the PDB early on.
  • the N4 rule may include the maximum CN PDB.
  • the maximum CN PDB value that may be used by the SMF to determine how to set the CN PDB may be used to determine an AN PDB (e.g., a 5G-AN PDB) to signal to the NG-RAN Node in the QoS profile.
  • AN PDB e.g., a 5G-AN PDB
  • the SMF may generate a QoS rule for the WTRU, and the QoS rule may include the QI value (e.g., 5QI value) that was derived by the PCF from the PDB, determined based on the E2E latency measurement.
  • the PCF may send a notification to the AS that QoS Parameters that are associated with the flow have been adjusted to improve the end-to-end latency that is associated with the traffic.
  • the notification may serve as a request, or trigger, for the AS to perform a new measurement of the end-to-end latency.4-7 may be repeated.
  • the PCF may send a message to the AF via the NEF to notify the AF of the event (e.g., that the system may not lower the PDB further to accommodate for the E2E latency issue).
  • the message may trigger the AS/AF to perform application layer changes.
  • the application server may choose a codec configuration (e.g., a different codec configuration) for the video traffic which may lower the quality of the video traffic to have a lower E2E latency value and meet the E2E latency parameter (e.g., requirement).
  • the SMF may request the WTRU to measure downlink E2E delay and report the measurement back to the network (e.g., to the SMF or PCF) or back to the AS.
  • the rules may include an indication of how often the WTRU may be to report the E2E delay (e.g., reporting frequency), which may be based on an N6 latency check frequency.
  • the N6 latency check frequency may indicate how often the WTRU may report the measurement.
  • the QoS rule provided to the WTRU may include the indication to perform an E2E delay measurement and include the N6 latency check frequency in the QoS rule.
  • the WTRU may inform the application function hosted on the WTRU that the application hosted on the WTRU may monitor the E2E latency.
  • the WTRU may provide the application with the reporting frequency that is included in the QoS rule. If the measurement is reported to the network (e.g., to the SMF or PCF), the network may use the E2E delay information to update the PCC rules. In examples, if the E2E delay measurement is larger than the E2E latency parameter (e.g., requirement) the PCF may determine a PDB value (e.g., new PDB value) for the system (e.g., 5GS) with a value that is lower than the previous PDB value used in the previous PCC rule.
  • a PDB value e.g., new PDB value
  • the PCF may provide a value (e.g., a new value) for the maximum CN PDB that is lower than the maximum CN PDB value used in the previous PCC rule.
  • the PCF may send the updated PCC rules to the SMF.
  • the SMF may generate and distribute QoS rules, QoS profiles, and N4 Rules.
  • the AS may forward the information to the PCF (e.g., through the NEF), which may use the E2E delay information to update the PCC rules.
  • the E2E latency measurement may not be determined at the UPF or WTRU.
  • the AF may provide the system (e.g., 5GS) with the E2E latency parameter (e.g., requirement), and the system may be measure the E2E latency measurement and to determine if the E2E parameter (e.g., requirement) is met.
  • the network may ask the UPF to measure the N6 delay for UL and DL transmissions and to report the measurements to the SMF or PCF.
  • the PCF may estimate the DL E2E delay and UL E2E delay by considering one or more of the following: reported N6 delay for UL, reported N6 delay for DL, measured UL delay between WTRU and UPF, measured DL delay between UPF and WTRU, and/or reported latency between the WTRU and a tethered device.
  • the PCF may update the PCC rules.
  • An E2E latency parameter (e.g., requirement) may be satisfied by triggering edge relocation.
  • FIG. 2 illustrates an example of how end-to-end latency may be improved by adjusting packet delay budgets. End-to-end latency may be improved by adjusting the maximum allowed user plane latency that is used to trigger edge relocation.
  • the actions at 1 may be triggered by the AF invoking an Nnef_TrafficInfluence API to provide the end-to-end latency Information to the NEF.
  • the NEF may invoke an Npcf_PolicyAuthorization API of the PCF to provide the end-to-end latency information to the PCF.
  • the action at 1 may involve the PCF receiving an end-to-end latency parameter (e.g., requirement) value and an end-to-end latency measurement value and using the end-to-end latency parameter (e.g., requirement) value and an end-to-end latency measurement value to determine a maximum allowed user plane latency for the flow.
  • the PCF may choose to assign a maximum allowed user plane latency that is larger than the maximum allowed user plane latency that is currently associated with the flow or larger than the requested 5GS delay.
  • the PCF may choose to increase the maximum allowed user plane latency this is associated with the flow.
  • the PCF may choose to assign a maximum allowed user plane latency that is lower than the maximum allowed user plane latency that is currently associated with the flow or lower than the requested 5GS delay.
  • the PCF may choose to decrease the maximum allowed user plane latency that may be associated with the flow.
  • the PCF may include the maximum allowed user plane latency for one or more flows in the PCC rules.
  • the PCC rule may be sent to the SMF, and the SMF may use the maximum allowed user plane latency to trigger an edge relocation procedure.
  • the result of the edge relocation procedure may be that a PSA UPF (e.g., new PSA UPF) is selected for the flow.
  • the PSA UPF may be located such that the traffic of the flow incurs less delay.
  • the PCF may be triggered to calculate a new maximum allowed user plane latency value for the flow.
  • Systems, methods, and instrumentalities may be configured for end-to-end latency aware system enhancements for extended reality and multimodal interactions (XRM).
  • a first network node may receive a first message from a second network node.
  • the first message may indicate end-to-end (E2E) latency information.
  • the first network node may determine a packet delay budget (PDB) value for a data flow based on the E2E latency information.
  • the first network node may generate a policy and charging control (PCC) rule based on the E2E information.
  • PDC policy and charging control
  • the first network node may send a second message to a third network node.
  • the second message may indicate the PCC rule, and the PCC rule may include a PDB value.
  • the first network node may receive a third message from the second network node.
  • the third message may indicate an E2E latency measurement that may satisfy or exceed a threshold.
  • the third message may indicate an E2E latency measurement and that the E2E latency measurement is below (or above) a threshold.
  • a measurement below the threshold may indicate that the E2E latency is satisfactory, reflecting that the latency is less than the maximum acceptable E2E latency.
  • a measurement above the threshold may indicate that the E2E latency is not satisfactory.
  • the second network node may send the E2E latency measurement, and the measurement may be either above or below the threshold.
  • the first network node may update the PCC rule based on the E2E latency measurement.
  • the first network node may send a fourth message to a third network node.
  • the fourth message may include the updated PCC rule.
  • the PDB value may be a first PDB value.
  • the updated PCC rule may include a second PDB value.
  • the first PDB value may be different from the second PDB value.
  • the first network node may send a fifth message to the second network node, and the fifth message may indicate an issue with a delay requirement.
  • the first network node may determine a Quality of Service (QoS) Identifier (QI) associated with the data flow.
  • QI Quality of Service
  • the PCC rule may include the QI and may be associated with the data flow.
  • the PCC rule may include a Quality of Service (QoS) monitoring policy associated with the E2E latency information.
  • the first network node may include a policy control function (PCF), the second network node may include an application function (AF), and the third network node may include a session management function (SMF).
  • PCF policy control function
  • AF application function
  • SMF session management function
  • a first network node may receive a first message from a second network node.
  • the first message may indicate an end-to-end latency requirement and/or a Quality of Service (QoS) parameter (e.g., requirement) for an XRM service.
  • QoS Quality of Service
  • the first network node may generate a QoS monitoring policy based on the QoS requirement.
  • the first network node may generate a Policy and Charging Control (PCC) rule based on the QoS monitoring policy.
  • the first network node may send a second message to a third network node (e.g., SMF).
  • the second message may indicate a PCC rule.
  • the first network node may receive a third message from the second network node.
  • the third message may indicate an end-to-end latency measurement.
  • the first network node may update the PCC rule based on the end-to-end latency measurement.
  • the first network node may send a fourth message to the third network node.
  • the fourth message may include the updated PCC rule.
  • the Quality of Service (QoS) parameter(s) e.g., a packet delay budget (PDB), packet error rate (PER)
  • PDB packet delay budget
  • PER packet error rate
  • the first network node may send a first notification message to the second network node.
  • the first notification message may indicate a QoS adjustment to be used to trigger an end-to-end latency measurement.
  • the first network node may send a second notification message to the second network node to prompt one or more application layer changes.
  • the end-to-end latency measurement may be a first end-to-end latency measurement.
  • the first notification message may indicate a trigger to perform a second end-to-end latency measurement.
  • the one or more application layer changes may include altering the codec configuration for video traffic to lower the quality and improve the end-to-end latency.
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as compact disc (CD)-ROM disks, and/or digital versatile disks (DVDs).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as compact disc (CD)-ROM disks, and/or digital versatile disks (DVDs).
  • CD compact disc
  • DVDs digital versatile disks
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes, des procédés et des instrumentalités pouvant être configurés pour améliorer des système sensibles à la latence de bout en bout pour des interactions en réalité étendue et multimodales (XRM). Un premier nœud de réseau peut recevoir un premier message provenant d'un second nœud de réseau. Le premier message peut indiquer des informations de latence de bout en bout (E2E). Le premier nœud de réseau peut déterminer une valeur de budget de retard de paquet (PDB) pour un flux de données sur la base des informations de latence E2E. Le premier nœud de réseau peut générer une règle de commande de politique et de facturation (PCC) sur la base des informations E2E. Le premier nœud de réseau peut envoyer un deuxième message à un troisième nœud de réseau. Le second message peut indiquer la règle PCC, et la règle PCC peut comprendre une valeur PDB. Le premier nœud de réseau peut recevoir un troisième message provenant du second nœud de réseau. Le troisième message peut indiquer une mesure de latence E2E et le fait que la mesure de latence E2E est inférieure à un seuil.
PCT/US2024/040390 2023-07-31 2024-07-31 Améliorations de système 5gs sensibles à la latence de bout en bout pour xrm Pending WO2025029919A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363529982P 2023-07-31 2023-07-31
US63/529,982 2023-07-31

Publications (1)

Publication Number Publication Date
WO2025029919A1 true WO2025029919A1 (fr) 2025-02-06

Family

ID=92459219

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/040390 Pending WO2025029919A1 (fr) 2023-07-31 2024-07-31 Améliorations de système 5gs sensibles à la latence de bout en bout pour xrm

Country Status (1)

Country Link
WO (1) WO2025029919A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MICHAEL STARSINIC ET AL: "LS on a new SST value for Extended Reality and Media Services", vol. 3GPP SA 2, no. Online; 20230116 - 20230120, 24 January 2023 (2023-01-24), XP052233878, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/Docs/S2-2301372.zip 23700-60-i00.zip 23700-60-i00.docx> [retrieved on 20230124] *
NOKIA ET AL: "KI#2, Sol#4: Updates for Deterministic QoS for UE-UE TSC communication", vol. SA WG2, no. Shanghai; 20200819 - 20200902, 13 August 2020 (2020-08-13), XP052463279, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_140e_Electronic/Docs/S2-2005735.zip S2-2005735-23.700-20_UpdateSol#4.docx> [retrieved on 20200813] *

Similar Documents

Publication Publication Date Title
US20230116626A1 (en) Network slice reselection
EP4075871B1 (fr) Relocalisation de plan d&#39;utilisateur
EP3620029A1 (fr) Mécanisme de reprise de faisceau
US20240389027A1 (en) Method of power saving for wtru to network relay
WO2025096568A1 (fr) Procédés, appareils et systèmes de surveillance et de prévention de performance anormale de réseau par collecte de données améliorée pour une fonction d&#39;analyse de données de réseau
US20250374111A1 (en) System and methods for supporting self-adaptive qos flow and profile
EP4555785A1 (fr) Politique de sélection de réseau local sans fil (wlan)
WO2025029919A1 (fr) Améliorations de système 5gs sensibles à la latence de bout en bout pour xrm
WO2025035098A1 (fr) Ensembles de pdu dl avec atsss
WO2024211581A1 (fr) Attribution de ressources de réseau sur la base d&#39;informations de retard
WO2025174890A1 (fr) Configuration et rapport de rejet d&#39;unité de données par paquets actifs pour des applications de réalité étendue
WO2024211582A1 (fr) Attribution de ressources de réseau sur la base d&#39;informations de budget de retard d&#39;ensemble d&#39;unités de données de protocole (pdu) (psdb)
WO2025208015A1 (fr) Attribution d&#39;identifiant d&#39;application attaché
WO2024211840A1 (fr) Surveillance de gigue basée sur des tampons de niveau d&#39;ensemble de pdu et des niveaux d&#39;importance
WO2024211839A1 (fr) Surveillance de gigue par une unité d&#39;émission/réception sans fil
WO2024211827A1 (fr) Systèmes et procédés associés à un mode de direction redondant et à une signalisation pmf
WO2024233272A1 (fr) Procédés, architectures, appareils et systèmes pour déterminer une configuration de gestion de liaison radio sur la base d&#39;un profil de qos reçu d&#39;une wtru source
WO2024233267A1 (fr) Procédés, architectures, appareils et systèmes pour déterminer un budget de retard de paquet et une configuration de support de commande de liaison radio
WO2025240695A1 (fr) Changement de périodicité de trafic dynamique et configuration de surveillance de paramètres n6
WO2024233264A1 (fr) Procédés, architectures, appareils et systèmes permettant de déterminer des première et seconde configurations sur la base d&#39;un profil de qos
WO2025235437A1 (fr) Sélection de ressources pour transmission de données de réalité étendue (xr)
WO2025175121A1 (fr) Procédés et appareil pour mettre en œuvre une activation de caractéristique de service sensible à l&#39;économie d&#39;énergie
WO2024233268A1 (fr) Procédés, architectures, appareils et systèmes permettant de déterminer de multiples valeurs de budget de retard de paquet pour des relais wtru à wtru
WO2025151435A1 (fr) Configuration de wtru pour réglages de rrt plus rapides
WO2024211895A1 (fr) Systèmes et procédés d&#39;établissement de sécurité entre une unité d&#39;émission-réception sans fil cible (wtru) et une wtru relais u2u

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

Country of ref document: EP

Kind code of ref document: A1