[go: up one dir, main page]

WO2025024278A1 - Procédés, architectures, appareils et systèmes d'information sur les changements de qualité de service dans des éléments de réseau dans des réseaux ido - Google Patents

Procédés, architectures, appareils et systèmes d'information sur les changements de qualité de service dans des éléments de réseau dans des réseaux ido Download PDF

Info

Publication number
WO2025024278A1
WO2025024278A1 PCT/US2024/038750 US2024038750W WO2025024278A1 WO 2025024278 A1 WO2025024278 A1 WO 2025024278A1 US 2024038750 W US2024038750 W US 2024038750W WO 2025024278 A1 WO2025024278 A1 WO 2025024278A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
client
network
n3qai
client device
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/038750
Other languages
English (en)
Inventor
Debashish Purkayastha
Anuj Sethi
Michael Starsinic
Michel Roy
Saad Ahmad
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 WO2025024278A1 publication Critical patent/WO2025024278A1/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/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • 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/0823—Errors, e.g. transmission errors
    • 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
    • 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/0876—Network utilisation, e.g. volume of load or congestion level
    • 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/50—Testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Definitions

  • the present disclosure is generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, systems directed to informing network elements in loT networks of changes to Quality of Service information, in particular loT networks connected to external wireless networks.
  • the present principles are directed to a method in a gateway device, the method comprising receiving information comprising a first set of Quality of Service, QoS, requirements, the information originating from a first network, determining a client device, in a second network and for which the gateway device acts as a gateway to the first network, involved in at least one traffic flow impacted by the first set of QoS requirements, transmitting, to the client device, information indicative of the first set of QoS requirements, receiving, from the client device, information indicative of whether the first set of QoS requirements is accepted or rejected by the client device, and transmitting, to the first network, the information indicative of whether the first set of QoS requirements are accepted or rejected by the client device.
  • QoS Quality of Service
  • the present principles are directed to a device comprising at least one processor configured to receive information comprising a first set of Quality of Service, QoS, requirements, the information originating from a first network, determine a client device, in a second network and for which the device acts as a gateway to the first network, involved in at least one traffic flow impacted by the first set of QoS requirements, transmit, to the client device, information indicative of the first set of QoS requirements, receive, from the client device, information indicative of whether the first set of QoS requirements is accepted or rejected by the client device, and transmit, to the first network, the information indicative of whether the first set of QoS requirements are accepted or rejected by the client device.
  • QoS Quality of Service
  • FIG. 1 A is a system diagram illustrating an example communications system
  • FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;
  • 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;
  • RAN radio access network
  • CN core network
  • FIG. ID 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. 1 A;
  • FIG. 2 illustrates an example Personal loT Network, PIN architecture
  • FIG. 3 illustrates an example of the PIN Application Framework in 5G Systems
  • FIG. 4 illustrates a scenario in which a PINE requests communication via the 5GS
  • FIG. 5 (made up of FIGs. 5 A and 5B) illustrates an example method according to the present principles, in which where a PEGC Client handles the N3QAI changes that are received from the network;
  • FIG. 6 (made up of FIGs. 6A and 6B) illustrates an example method according to the present principles in which a PEMC Client handles the N3QAI changes received from the network;
  • FIG. 7 (made up of FIGs. 7A and 7B) illustrates an example method according to the present principles in which a PEGC Client initiates a notification when QoS Requirements cannot be met;
  • FIG. 8 (made up of FIGs. 8A and 8B) illustrates a first embodiment of an example method according to the present principles in which an example procedure where a PEMC Client initiates a notification when QoS Requirements cannot be met;
  • FIG. 9 (made up of FIGs. 9A and 9B) illustrates a second embodiment of an example method according to the present principles in which an example procedure where a PEMC Client initiates a notification when QoS Requirements cannot be met.
  • the methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks.
  • An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.
  • FIG. 1A is a system 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), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (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 singlecarrier FDMA
  • ZT zero-tail
  • ZT UW unique-word
  • DFT discreet Fourier transform
  • OFDM ZT UW DTS-s 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 radio access network (RAN) 104/113, a core network (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.
  • Each of the 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 (or be) 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 (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
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • 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, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112.
  • the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), 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 or any 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 116 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 Packet Access (HSDPA) and/or High-Speed Uplink 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).
  • a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • 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 (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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 (Wi-Fi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global
  • 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 any of a small cell, picocell or femtocell.
  • a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.
  • 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 any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi 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 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/114 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. IB 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 elements/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. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.
  • 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 WTRU 102 may include any number of transmit/receive elements 122.
  • the WTRU 102 may employ MIMO technology.
  • 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), readonly 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.
  • location information e.g., longitude and latitude
  • 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 elements/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 half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (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 uplink (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, and 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 receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, 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 (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one 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, and 160c in the RAN 104 via an SI 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 SI 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.
  • 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 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 into 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. l ie DLS or an 802.1 Iz 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 (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. 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) may transmit at any given time in a given BSS.
  • 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 nonadj acent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20 MHz, 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 a medium access control (MAC) layer, entity, etc.
  • MAC medium access control
  • Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in
  • 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum
  • 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,
  • MTC meter type control/machine-type communications
  • 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.1 In, 802.1 lac, 802.1 laf, and 802.1 lah 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.
  • the available frequency bands which may be used by 802.1 lah, 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.1 lah is 6 MHz to 26 MHz depending on the country code.
  • FIG. ID 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, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c.
  • 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, 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., including a 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 functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPFs user plane functions
  • AMFs access and mobility management functions
  • the CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one 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.
  • AMF 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 protocol data unit (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.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • 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.
  • 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 UE 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, e.g., 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 multihomed 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 any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/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. For example, 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 (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
  • PIN Personal loT Network
  • PEMC PIN Element with Management Capability
  • PEGC PIN Elements with Gateway Capability
  • PIN Element A device that can communicate within a PIN (via PIN direct connection, via PEGC, or via PEGC and 5G Core Network, 5GC), or outside the PIN via a PEGC and 5GC.
  • PIN Element with Gateway Capability A PIN Element with the ability to provide connectivity to and from the 5G network for other PIN Elements, or to provide relay for the communication between PIN Elements.
  • PIN Element with Management Capability A PIN Element with capability to manage the PIN.
  • PINE-to-PINE communication communication between two PINEs which may use PINE-to-PINE direct communication or PINE-to-PINE indirect communication.
  • PINE-to-PINE indirect communication communication between two PIN Elements via PEGC or via UPF.
  • PINE-to-PINE routing the traffic is routed by a PEGC between two PINEs, the two PINEs connect directly with the PEGC via non-3GPP access.
  • PINE-to-Network routing the traffic is routed by a PEGC between PINE and 5GS, the PINE connects directly with the PEGC via non-3GPP access separately.
  • N3QAI Non 3GPP QoS Assistance Information
  • the Internet of Things (loT) feature has been designed for devices that communicate using the traditional cellular network. Devices with loT capabilities require better power consuming performance and increased network efficiency for bulk operations.
  • UEs with loT capabilities can be organized in a Personal loT Network (PIN).
  • PIN Personal loT Network
  • security sensors, smart lights, smart plugs, printers, cellphones, etc. are managed by a residential gateway and can communicate.
  • all devices in the home constitute a Personal loT Network (PIN).
  • PIN element Each device is called a PIN element and different PIN elements have different capabilities.
  • a residential gateway can be a PIN Element with Gateway Capability (PEGC) and provide connections between PIN elements and connections between 5G network and PIN Elements.
  • PEGC Gateway Capability
  • a PIN Element with Management Capability is a PIN Element that provides a means for an authorized administrator to configure and manage a PIN.
  • the residential gateway which acts as a PEGC could support PIN management function as well and be a PIN element with management capability (PEMC).
  • Wearable devices constitute another kind of PIN, in which a smartphone may act as a PIN Element with Gateway Capability (PEGC) as well as a PIN element with management capability (PEMC) and a smartwatch, VR/AR glasses, and airpods communicate in the PIN (or with other UEs via 5G network).
  • PEGC PIN Element with Gateway Capability
  • PEMC PIN element with management capability
  • smartwatch VR/AR glasses
  • airpods communicate in the PIN (or with other UEs via 5G network).
  • FIG. 2 illustrates an example Personal loT Network, PIN, architecture.
  • the PIN 210 includes two PIN elements, PINEs, 212, 214, a PIN Element with Management Capability, PEMC, 216 and a PIN Element with Gateway Capability, PEGC, 218.
  • the PEGC 218 can establish a connection with a RAN 222 of a 5GC 220 that further includes an AMF 224, a SMF 226 and a UPF 228 connected to a data network 230.
  • the 5G System design assumes that only a 3GPP UE can act as PEGC and/or PEMC, there are one or more PEGCs in a PIN, there are one or more PEMCs in a PIN and only one of these is able to control the PIN, the PIN Elements use non-3GPP access (e.g., WIFI, Bluetooth) for direct communication, the PEMC can use 5G ProSe Direct Communication for direct communication with PEGC, the PEGC and PEMC subscribe to the same PLMN or (S)NPN, and a single PEGC may support more than one PIN at a time.
  • non-3GPP access e.g., WIFI, Bluetooth
  • FIG. 3 illustrates an example of the PIN Application (PINAPP) Framework in 5G Systems.
  • Application entities such as PIN Client in a PINE, PIN Gateway Client in PEGC, PIN Management Client in PEMC, and PIN Server in data network are part of the PINAPP architecture and enable desired feature in a PIN.
  • QOS management in PIN network is part of the PINAPP architecture and enable desired feature in a PIN.
  • a UE consists of a Terminal Equipment (TE) part and a Mobile Termination (MT) part.
  • TE Terminal Equipment
  • MT Mobile Termination
  • the TE part hosts applications and the MT is the receiver / transmitter that provides network services to the TE.
  • the interface between the MT part and TE part is so-called AT commands or APIs.
  • both a PEGC and a PEMC have a TE and an MT part.
  • the PEGC Client and PEMC Client are “applications” that are hosted in the TE part. Messages like PDU Session Modification Requests and PDU Session Modification Command are sent and received by the MT part of the PEGC (UE).
  • TS 23.501 Section 5.44.3.3, explains that “Non-3GPP QoS Assistance Information, N3QAI” may be included as part of an PDU Session Modification Command.
  • the PDU Session Modification Command provided by SMF to a UE.
  • a PEGC is an example of a UE.
  • N3QAI can include 5G QoS Identifier (5QI), Guaranteed Flow Bit Rate (GFBR) uplink, GFBR downlink, Maximum Flow Bit Rate (MFBR) uplink, MFBR downlink, Averaging window, Resource type, Priority level, Packet delay budget (PDB), Packet error rate, Maximum data burst volume, Maximum packet loss rate downlink, Maximum packet loss rate uplink, ARP, and Periodicity, all of which are known in the art.
  • 5QI 5G QoS Identifier
  • GFBR Guaranteed Flow Bit Rate
  • MFBR Maximum Flow Bit Rate
  • Averaging window Resource type
  • Priority level Packet delay budget
  • Packet error rate Packet error rate
  • Maximum data burst volume Maximum packet loss rate downlink
  • Maximum packet loss rate uplink ARP
  • Periodicity all of which are known in the art.
  • Non-3GPP QoS Assistance Information (N3QAI) enables the PEGC to perform QoS differentiation for the PINEs in the non-3GPP network behind the PEGC.
  • SMF provides the PEGC with QoS flow descriptions, including N3QAI for each QoS flow to the PEGC based on the (DNN, S-NSSAI) combination of the PDU Session.
  • the PEGC may reserve resources in the non-3GPP network.
  • FIG. 4 describes the scenario in which a PINE requests communication via the 5GS.
  • PINE 412 sends a request for 5G communication to PEGC 416.
  • the request includes QoS (e.g., packet delay, AMBR) for a packet flow.
  • QoS e.g., packet delay, AMBR
  • the PEGC 416 initiates a PDU session modification procedure with 5GS 418.
  • Non-3GPP QoS Assistance Information, N3QAI is signaled by the 5GS 418 to the PEGC 416 in step S404.
  • the PEGC 416 informs the PINE 412 about the N3QAI.
  • the PDU Session Modification Command can be triggered by the network at any time.
  • the PEGC MT
  • the PEGC can receive modified N3QAI for the non-3GPP connection between PEGC and PINEs.
  • the PINE is informed about the QoS information after having requested 5G communication.
  • there is no mechanism to inform the PINEs about QOS information changes for example when the network changes, modifies, or updates QoS information.
  • the N3QAI that is received by the PEGC (MT), via the PDU Session Modification Command might indicate that notification control is enabled.
  • notification control When notification control is enabled, an Application Server (AS) may expect a notification that certain QoS settings cannot be maintained. For example, if GFBR for a QOS flow cannot be met, then it may be necessary to notify an Application Server.
  • AS Application Server
  • the 5G core network might have no information about the condition of the PIN network. Thus, the 5GC will not know if the QoS cannot be met for the PIN network. Therefore, the 5GC cannot notify the AS about the condition that the QoS cannot be met and the 5GC cannot adjust network settings based on conditions in the PIN network.
  • a further resulting problem is how can the Application Server be notified and how can 5GC can be triggered to adjust QoS Settings when conditions in the PIN prevent the QoS being met?
  • At least an embodiment of the present principles proposes mechanisms to inform PIN elements about the changed or updated N3QAI information for the non-3GPP part of the PIN through application layer messaging mechanisms.
  • the PEGC client or the PEMC client may receive the new N3QAI and inform PINEs and a PIN server.
  • At least an embodiment of the present principles proposes a mechanism to inform an application server and PIN elements about changes in QOS/N3QAI indicated by network and includes notification control.
  • the PEGC client or the PEMC client handles the new N3QAI with notification control.
  • Embodiments of the present principles provide application-level mechanisms to inform a PIN Client in a PINE, which informs the Application Client in the PINE, about changes in QOS information as per the N3QAI. [0113] Embodiments of the present principles also provide solutions to inform AS about the inability of a PINE to support a requested N3QAI, when notification control is enabled.
  • a PIN client can subscribe to a PEGC or PEMC client to receive notification about QOS/N3QAI changes.
  • PEGC Client handles the N3QAI changes
  • a PEGC Client in the UE and the MT part of the UE receives information from the MT part of the UE.
  • the information from the MT part of the UE indicates a QoS Requirements for at least one PIN data flow.
  • the MT part of the UE is triggered to send to information to the PEGC Client by the reception of a PDU Session Modification Command that includes N3QAI information.
  • the MT part of the UE determines which PIN data flows are associated with the N3QAI information.
  • the PEGC Client determines the identity of a PIN Client that is associated with at least one data flow, sends a message to the PIN Client, the message including the QoS Requirements, [0119]
  • the PEGC Client may receive a response message from the PIN Client. The response message indicates which of the QoS Requirements are accepted by the PIN Client.
  • the PEGC Client may send information to the MT part of the UE.
  • the information sent to the MT part of the UE indicates the QoS Requirements that are accepted for the at least one data flow.
  • the PEGC Client may send a message to PIN server.
  • the information sent to the PIN server can indicate that the QoS Requirement can be met for at least one data flow.
  • the message can also indicate QoS Requirements that cannot be met.
  • PEMC Client handles the N3QAI changes
  • a PEMC Client in the UE receives information from a PEGC Client about changed QoS Requirements for at least one data flow in a PIN.
  • the PEMC Client determines a PIN Client that is associated with the data flow and sends a message includes the QoS Requirements to the PIN Client.
  • the PEMC Client responds to the PEGC Client to inform if the QoS Requirements were sent to at least one PIN Client.
  • the message includes information if the QOS requirement can be met for at least one data flow.
  • the message can include if the QOS requirement cannot be met.
  • the response may include the identity of the PIN Clients.
  • the PEMC Client may send a message to PIN Server to inform if the QOS requirement can be met for at least one data flow.
  • the message identifies the data flow and may also identify the PIN Client.
  • the message may include QoS information, which cannot be met.
  • the message may cause the PIN server to inform Application Server, so that the Application server can change to a different data rate.
  • PEGC Client handles notification control
  • a PEGC Client in the UE and the MT part of the UE receives information from the MT part of the UE.
  • the information indicates a QoS Requirement for a data flow and includes an indication that notification control is enabled for the at least one data flow.
  • the MT part of the UE was triggered to send to information to the PEGC Client by the reception of a PDU Session Modification Command that includes N3QAI information.
  • the MT part of the UE determined which PIN data flows are associated with the N3QAI information.
  • the PEGC Client determines the identity of a PIN Client that is associated with the at least one data flow.
  • the PEGC Client sends a message to the PIN Client.
  • the message includes the QoS Requirement and an indication that notification control enabled for the at least one data flow.
  • the PEGC Client receives a message from the PIN Client.
  • the message indicates that the QoS Requirement is rejected or cannot be met.
  • the PEGC Client sends information to the MT part of the UE.
  • the information sent to the MT part of the UE indicating that the QoS Requirement can not be met for at least one data flow.
  • the message may indicate QoS Requirements that can be met.
  • the message triggers the MT part of the UE to send a PDU Session Modification command to the network that indicates that the QoS Requirement can not be met for at least one data flow and may indicates QoS Requirements that can be met.
  • the PEGC Client may send a message to PIN server.
  • the information sent to the PIN server indicates that the QoS Requirement cannot be met for at least one data flow.
  • the message may indicate QoS Requirements that can be met.
  • PEMC Client handles notification control
  • a PEMC Client in the UE receives information from PEGC Client about changed QoS Requirements and an indication that notification control is enabled for at least one data flow in a PIN.
  • the PEMC Client determines that the changed QoS requirements cannot be met and that a PINE that is associated with a first PEGC should instead associate with a second PEGC in order to meet the requirements.
  • the PEMC Client sends a message to the PIN Client, the message indicating the QoS requirements and identities of PEGC(s) that the PIN Client may associate with. [0139] The PEMC Client sends a message to the PEGC Client, the message indicating if the QoS Requirements can be met.
  • the PEMC Client may send a message to PIN server, the message indicating that the QoS Requirement cannot be met for at least one data flow.
  • the message may indicate QoS Requirements that can be met.
  • the PEGC client or the PEMC client can handle the N3QAI changes indicated by the network. Handling the N3QAI changes means that either PEGC or PEMC client informs PIN clients about the N3QAI change, collects responses from PIN clients and informs network or the application server if the QOS change is accepted or rejected by PINE. PIN clients inform the application client about the QOS changes and the application client can take actions such as reducing data rate, reserving resources etc.
  • New N3QAI First option for N3QAI provided by network.
  • Alternate N3QAI Second option for N3QAI provided by network.
  • Accepted N3QAI The new N3QAI or alternate N3QAI accepted by PINE.
  • Accepted QoS Same as accepted N3QAI, used to inform PIN server and AS.
  • Rejected QoS New N3QAI, alternate N3QAI or both, rejected by PINE.
  • traffic flows in a PIN may need to be identified by a Flow ID.
  • a Flow ID can be combination of one or more PINE ID(s), PINE IP address(es), and DSCP code.
  • a UE may map Flow IDs to QoS Flows which are identified by a QFI.
  • FIG. 5 (made up of FIGs. 5 A and 5B) illustrates an example method according to the present principles in which a PEGC Client handles the N3QAI changes that are received from the network.
  • the 5GS 509 sends a PDU Session Modification Command with the new N3QAI and alternate N3QAI to the PEGC (MT) 507.
  • step S504 the PEGC (MT) 507 determines which flows are impacted by the new N3QAI.
  • the PEGC (MT) can determine this by checking which traffic flows map to the QoS Flows that are indicated in the N3QAI.
  • step S506 the PEGC (MT) 507 sends a N3QAI change request message to the PEGC Client 505 to indicate the new N3QAI and alternate N3QAI received for the flows.
  • the message also includes information about the impacted flows.
  • the PEGC Client 505 determines the identities of the PINEs that are associated with the impacted flows. This message can be a notification if the PEGC Client 505 has subscribed to PEGC (MT) 507.
  • step S508 the PEGC Client 505 sends a N3QAI change request message to the PIN client(s) 501 to inform about the new N3QAI, alternate N3QAI and the impacted flow by indicating Flow ID.
  • the message can be a notification if PIN client has subscribed to PEGC client.
  • step S510 the PIN Client 501 can inform an Application Client about the new N3QAI and alternate N3QAI.
  • the Application Client can accept the new N3QAI or alternate N3QAI, take specific actions such as decreasing or increasing video quality.
  • the Application Client may adjust application layer settings such that different bit rates or information encoding techniques are used. The different bit rates or information encoding techniques may be better suited, or more compatible with, the current QoS settings. It can also reject the suggested N3QAI in case it cannot adapt to the new N3QAI.
  • step S512 the PIN Client 501 sends a N3QAI change response to PEGC client 505, indicating either that it accepts the new or alternate N3QAI or that it cannot support the suggested N3QAI.
  • the accepted N3QAI indicates either the accepted new N3QAI or the alternate N3QAI.
  • the message may indicate the alternate N3QAI that the PIN Client 501 will use.
  • the rejected QOS includes both new N3QAI and alternate N3QAI and indicates that both are rejected by the PINE.
  • the PIN Client 501 may further inform the PIN server 511 about the accepted QOS, i.e., the accepted N3QAI (new or alternate) or rejected QOS by sending a QoS change indication message.
  • the accepted QOS i.e., the accepted N3QAI (new or alternate) or rejected QOS by sending a QoS change indication message.
  • the PEGC client 505 responds to PEGC MT’s request in step S506 by sending it a N3QAI change response message.
  • the message can include information about the accepted N3QAI (new or alternate) or rejected QOS by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID.
  • the PEGC client 505 may further inform the PIN server 511 about the accepted QOS or rejected QOS by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID, by sending a QoS change indication message.
  • step S520 the PEGC MT 507 sends at least one PDU Session Modification Request to the 5GS network 509.
  • the PDU Session Modification Request can be per PINE and indicate a N3QAI that was accepted or rejected for use by the respective PINE within the PIN.
  • the PIN server 511 may, in step S522, update the AS about the QOS accepted or rejected by PINE identified by PINE ID and the impacted flow indicated with Flow ID, in case it has that capability. After reception of the update, the AS can take action, such as increase or decrease data rate, as per the QOS notification.
  • FIG. 6 (made up of FIGs. 6A and 6B) illustrates an example method according to the present principles in which a PEMC Client handles the N3QAI changes received from the network. [0163] As illustrated in FIG. 6A, steps S602-S606 correspond to steps S502-S506 of FIG. 5.
  • step S608 the PEGC Client 605 sends a N3QAI change request message to the PEMC client 603 to inform about the new N3QAI, alternate N3QAI and the impacted PINE.
  • the impacted PINE is identified by a PINE ID
  • the impacted flow is identified by Flow ID along with the PEGC ID.
  • the PEMC client 603 uses the PEGC ID to exclude it from the suggested list of PEGCs, sent by the PEMC client 603 to the PINE 601 for PEGC discovery.
  • the message can be a notification if PEMC client has subscribed to PEGC client.
  • step S610 the PEMC Client 603 sends a N3QAI change request message to the PIN client 601 in the PINE to inform about the new N3QAI, alternate N3QAI and the impacted Flow ID.
  • the message can be a notification if the PIN client 601 has subscribed to PEMC client 603.
  • the PIN Client 601 can inform an application client about the new N3QAI and alternate N3QAI.
  • the application client can accept the new or alternate N3QAI, take specific actions such as decreasing or increasing video quality. It can also reject the suggested N3QAI.
  • the Application Client may adjust application layer settings such that different bit rates or information encoding techniques are used. The different bit rates or information encoding techniques may be better suited, or more compatible with, the current QoS settings.
  • step S614 the PIN Client 601 sends a N3QAI change response message to the PEMC client 603, indicating either it the N3QAI (new or alternate) or it cannot support the suggested N3QAI.
  • the PIN Client 603 may send a QoS change indication message to the PIN server 611 to inform it about the accepted QOS or rejected QOS by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID.
  • step S618 the PEMC Client 603 sends a N3QAI change response message to PEGC client 605, in response to the request received in step S608, indicating if the PIN client accepted N3QAI (new or alternate) or rejected the changed/updated QOS, including the PINE ID to indicate the PINE and impacted flow by indicating Flow ID.
  • the PEMC client 605 may inform the PIN server 611 about the accepted QOS or rejected QOS by the PINE identified by PINE ID and the flow identified by Flow ID.
  • step S622 the PEGC client 605 sends a N3QAI change response message to the PEGC MT 607 to respond to its request in step S606.
  • the message can include information about the accepted N3QAI (new or alternate) or rejected QOS by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID
  • step S624 the PEGC MT 607 sends at least one PDU Session Modification Request to the network, 5GS, 609.
  • the PDU Session Modification Request indicates a N3QAI that was accepted or rejected for use within the PIN.
  • the PDU Session Modification Request can be per PINE and indicate aN3QAI that was accepted or rejected for use by the respective PINE within the PIN.
  • step S626 the PIN server 611 may update the AS about the QOS accepted or rejected by PINE identified by PINE ID and the impacted flow indicated with Flow ID, if it has that capability.
  • the AS can take action, such as increase or decrease data rate, as per the QOS notification.
  • the PEGC client or the PEMC client can handle the N3QAI changes with notification control, indicated by the network. Handling the N3QAI changes means that either the PEGC or PEMC client informs PIN clients about the N3QAI change with notification control enabled, collects the responses from PIN clients. If a PIN client rejects the QoS, then informing the PIN server is mandatory; if the QoS is accepted, the PIN server may be informed.
  • the PIN client informs the application client about the changes in QOS requirements and the application client can take actions such as reducing data rate, reserving resources etc.
  • the PEGC client obtains the information about N3QAI change with notification control enabled, informs the PIN client about the change in N3QAI including notification control enabled. After receiving indication from the PIN client that the N3QAI cannot be supported, the PEGC client informs the AS directly.
  • the PEGC Client can send an indication that the N3QAI cannot be supported to the PEGC MT.
  • the indication may trigger the PEGC MT to send a PDU session modification message to the network.
  • the PDU session modification message may include an indication that the N3QAI cannot be supported and may trigger the SMF to notify an Application Server about the inability of the PINE to support the N3QAI.
  • the PEMC client is notified about the new N3QAI with notification control enabled by PEGC client.
  • the PEMC client can either inform the PIN client about the new N3QAI with notification control enabled, or can abstain from informing the PIN client and decide on its own whether the new N3QAI can be supported by the PINE.
  • the PEMC client can receive an indication from the PIN Client that it cannot support the new N3QAI.
  • the PEMC decides whether the AS should be notified.
  • PEMC client informs AS directly.
  • the PEMC client informs the PEGC client and the PEGC MT, which can update the network by triggering PDU session modification procedure.
  • FIG. 7 (made up of FIGs. 7A and 7B) illustrates an example method according to the present principles in which a PEGC Client initiates a notification when QoS Requirements cannot be met.
  • the 5GS 709 can determine to change or update the QOS information provided to the PEGC, including N3QAI and notification control.
  • the QoS Information can include the QOS information (e.g., new N3QAI, alternate N3QAI with GFBR) and notification control enabled.
  • the 5GS sends a PDU Session Modification Command with new N3QAI, alternate N3QAI and notification control enabled to the PEGC (MT) 707.
  • step S704 the PEGC (MT) 707 determines which flows/PINEs are impacted by the new QOS information, i.e., new N3QAI, alternate N3QAI.
  • the PEGC (MT) 707 can determine this by checking which flows map to the QoS Flows that are indicated in the N3QAI.
  • step S706 the PEGC (MT) 707 sends N3QAI change request message to the PEGC Client 705 to indicate the new N3QAI and alternate N3QAI with GFBR and notification control enabled received for the flows.
  • the message also includes information about the impacted flows.
  • the PEGC Client 705 determines the identities of the PINEs that are associated with the impacted flows.
  • the message can be a notification if PEGC client has subscribed to PEGC (MT)
  • step S708 the PEGC Client 705 sends a N3QAI change request message to the PIN client(s) 701 to inform about the new N3QAI, alternate N3QAI with GFBR, notification control enabled, and the impacted flow identified by Flow ID.
  • the message can be a notification if PIN client has subscribed to PEGC client.
  • the PIN Client 701 can inform application client about the new N3QAI, alternate N3QAI and notification control enabled.
  • An application client can accept the new or alternate N3QAI, take specific actions such as decreasing or increasing video quality. It can also reject the suggested N3QAI.
  • the Application Client may adjust application layer settings such that different bit rates or information encoding techniques are used. The different bit rates or information encoding techniques may be better suited, or more compatible with, the current QoS settings. It can also reject the suggested N3QAI, as it cannot adapt to the new N3QAI.
  • step S712 the PIN Client 701 sends a N3QAI change response to the PEGC client 705, indicating either that it accepted the new or alternate N3QAI or that it cannot support the suggested N3QAI as GFBR cannot be met.
  • the accepted N3QAI indicates either the accepted new N3QAI or the alternate N3QAI.
  • the message may indicate the alternate N3QAI that the PIN Client will use.
  • the rejected QOS includes both new and alternate N3QAI with notification control enabled and indicates both are not accepted by the PINE.
  • the PIN Client 701 processes the response from application client.
  • the PIN Client can decide that the PIN server needs to be informed because notification control is enabled. If so, in step S714a, the PIN client 701 informs the PIN server 711 about the accepted QOS or rejected QOS by sending QoS change indication message.
  • the PIN server can update the AS about the QOS accepted or rejected by PINE identified by PINE ID and the flow identified by Flow ID.
  • the AS can take action, such as increase or decrease data rate, as per the QOS notification.
  • the PEGC Client 705 determines that the AS should be informed (because notification control was enabled).
  • the PEGC Client 705 informs PEGC MT 707 about the QOS information either accepted or rejected by a PINE by sending a N3QAI change response message, possibly per PINE. It indicates the Flow ID and accepted QOS or rejected QOS information.
  • the PEGC MT 707 in response to receiving QOS reject information, determines that the AS 711 needs to be informed as notification control was enabled.
  • the PEGC MT 707 sends at least one PDU Session Modification Request to the network 709.
  • the PDU Session Modification Request indicates a N3QAI that was accepted or rejected with notification control, for use within the PIN.
  • the PDU Session Modification Request can be per PINE and indicate a N3QAI that was accepted or rejected for use by the respective PINE within the PIN.
  • the 5GS 709 informs the PIN Server/AS 711 that the N3QAI with notification control cannot be met.
  • the PEGC client 705 sends a QoS change indication message to the PIN server 711 to inform about the accepted QOS or rejected QOS, like GFBR cannot be met and notification control enabled.
  • the message includes the impacted PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID.
  • the PIN server 711 can trigger notification control towards AS.
  • FIG. 8 (made up of FIGs. 8A and 8B) illustrates a first embodiment of an example method according to the present principles in which an example procedure where a PEMC Client initiates a notification when QoS Requirements cannot be met.
  • the PEMC client receives the new QOS information and notification control from the PEGC client. In case the PINE cannot support the requested QOS, the PEMC client determines this and initiates the process to inform the application server. [0189] As illustrated in FIG. 8A, steps S802-S806 correspond to steps S702-S706 of FIG. 7: the PEGC client receives the new N3QAI information with notification control enabled from network/5GS.
  • the QoS Information can include the QOS information (e.g., new N3QAI, altN3QAI with GFBR) and notification control enabled.
  • step S808 the PEGC Client 805 sends a N3QAI change request message to the PEMC client 803 to inform about the new N3QAI, alternate N3QAI with notification control enabled and the impacted PINE.
  • the impacted PINE is identified by a PINE ID
  • the impacted flow is identified by Flow ID along with the PEGC ID.
  • the PEMC client 803 uses the PEGC ID, to exclude it from the suggested list of PEGCs, sent by PEMC client to PINE for PEGC discovery.
  • the message can be a notification if PEMC client has subscribed to PEGC client.
  • step S810 the PEMC client 803 determines that the PINE cannot support the new N3QAI with GFBR.
  • the PEMC client 803 can make the determination based on the PINE profile, its location, connectivity etc. It can determine that the PINE should find a different PEGC.
  • the PEMC client 803 initiates a procedure so that the PINE will become associated with a different PEGC, as will be described in step S822. Since notification control is enabled, the PEMC client 803 also determines that the AS 811 should be notified.
  • step S812 the PEMC client 803 sends N3QAI change response (to the message in step S808) to the PEGC Client 805, indicating that the PIN client cannot support the requested N3QAI by indicating the rejected N3QAI with GFBR in the rejected QOS, and notification enabled for the Flow ID.
  • the PEMC Client 803 Since the PEMC Client 803 is aware that notification control is enabled, it can, in step S814, send a QoS change indication message to the PIN server 811 to inform that the N3QAI with GFBR cannot be met.
  • the message can also include the impacted PINE identified by PINE ID, impacted flow identified by Flow ID, connected to a PEGC identified by PEGC ID.
  • PIN server can provide the information to AS, so that AS can take action such as reduce data rate.
  • the PEGC Client 805 After receiving the notification response in step S812, the PEGC Client 805 determines that the AS should be informed (because notification control was enabled). Turning to FIG. 8B, in step S816, the PEGC Client 805, sends a N3QAI change response message to the PEGC MT 807.
  • the message includes information about the rejected QOS for the PINE, and indicates the impacted PINE by PINE ID, and the impacted flow by Flow ID.
  • step S818 the PEGC MT 807 sends at least one PDU Session Modification Request to the network 809.
  • the PDU Session Modification Request indicates a N3QAI that was rejected with notification control enabled, for use within the PIN.
  • the PDU Session Modification Request can be per PINE and indicate a N3QAI that was accepted or rejected for use by the respective PINE within the PIN.
  • step S820 the 5GS 809 informs the PIN Server/AS 811 that the N3QAI with notification control cannot be met.
  • step S822 the PEMC client 805 sends a message to the PIN Client 801 indicating that this should start looking for a new PEGC, as the desired QOS cannot be supported with the current PEGC.
  • the message includes a list of PEGC, to assist PINE in finding a new PEGC.
  • step S824 the PIN client 801 informs the application client and starts PEGC discovery.
  • FIG. 9 (made up of FIGs. 9A and 9B) illustrates a second embodiment of an example method according to the present principles in which an example procedure where a PEMC Client initiates a notification when QoS Requirements cannot be met.
  • the PEMC client receives the new QOS information and notification control from PEGC client.
  • PEMC client is not aware if the PINE can support the requested QOS.
  • PEMC client informs PIN client about the new N3QAI. After receiving response from PIN client, PEMC starts informing network or AS about the agreed or rejected QOS. The following diagram describes the procedure.
  • steps S902-S906 correspond to steps S702-S706 of FIG. 7: the PEGC client receives the new N3QAI information with notification control enabled from network/5GS.
  • the QoS Information can include the QOS information (e.g., newN3QAI, alternate N3QAI with GFBR) and notification control enabled.
  • the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor.
  • Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media.
  • 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 internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
  • processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit (“CPU”) and memory.
  • CPU Central Processing Unit
  • memory In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being “executed,” “computer executed” or “CPU executed.”
  • any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium.
  • the computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.
  • a signal bearing medium examples include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc.
  • a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
  • a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities).
  • a typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
  • any two components so associated may also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being “operably couplable” to each other to achieve the desired functionality.
  • operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
  • the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
  • the terms “any of' followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include “any of,” “any combination of,” “any multiple of,” and/or “any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items.
  • the term “set” is intended to include any number of items, including zero.
  • the term “number” is intended to include any number, including zero.
  • the term “multiple”, as used herein, is intended to be synonymous with “a plurality”.
  • a range includes each individual member.
  • a group having 1-3 cells refers to groups having 1, 2, or 3 cells.
  • a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

Landscapes

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

Abstract

L'invention concerne des procédures, des procédés, des architectures, des appareils, des systèmes, des dispositifs et des produits programmes d'ordinateur d'information sur les changements de qualité de service dans des éléments de réseau dans des réseaux IdO. Un dispositif de passerelle reçoit des informations comprenant un premier ensemble d'exigences de qualité de service, QoS, les informations provenant d'un premier réseau; détermine un dispositif client, dans un second réseau et pour lequel le dispositif de passerelle agit en tant que passerelle vers le premier réseau, impliqué dans au moins un flux de trafic impacté par le premier ensemble d'exigences de QoS; transmet, au dispositif client, des informations indiquant le premier ensemble d'exigences de QoS; reçoit, de la part du dispositif client, des informations indiquant si le premier ensemble d'exigences de QoS est accepté ou rejeté par le dispositif client; et transmet, au premier réseau, les informations indiquant si le premier ensemble d'exigences de QoS est accepté ou rejeté par le dispositif client.
PCT/US2024/038750 2023-07-21 2024-07-19 Procédés, architectures, appareils et systèmes d'information sur les changements de qualité de service dans des éléments de réseau dans des réseaux ido Pending WO2025024278A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363528120P 2023-07-21 2023-07-21
US202363528118P 2023-07-21 2023-07-21
US63/528,118 2023-07-21
US63/528,120 2023-07-21

Publications (1)

Publication Number Publication Date
WO2025024278A1 true WO2025024278A1 (fr) 2025-01-30

Family

ID=92295543

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/038750 Pending WO2025024278A1 (fr) 2023-07-21 2024-07-19 Procédés, architectures, appareils et systèmes d'information sur les changements de qualité de service dans des éléments de réseau dans des réseaux ido

Country Status (1)

Country Link
WO (1) WO2025024278A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200344769A1 (en) * 2019-04-23 2020-10-29 Lenovo (Singapore) Pte. Ltd. Establishing qos flows over non-3gpp access

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200344769A1 (en) * 2019-04-23 2020-10-29 Lenovo (Singapore) Pte. Ltd. Establishing qos flows over non-3gpp access

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Services and System Aspects; Application layer support for Personal IoT Network; (Release 18)", no. V18.0.0, 22 June 2023 (2023-06-22), pages 1 - 103, XP052408975, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/23_series/23.542/23542-i00.zip 23542-i00.docx> [retrieved on 20230622] *
MICHAEL STARSINIC ET AL: "Non-3GPP QoS and delay budget - 23.501", vol. 3GPP SA 2, no. Athens, GR; 20230220 - 20230224, 10 February 2023 (2023-02-10), XP052235762, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_155_Athens_2023-02/Docs/S2-2302460.zip S2-2302460 revision of approved 1368 N3GPP QoS and delay.docx> [retrieved on 20230210] *

Similar Documents

Publication Publication Date Title
WO2020168065A1 (fr) Procédures de contrôle de congestion pour des communications pc5
US20240129968A1 (en) Methods, architectures, apparatuses and systems for supporting multiple application ids using layer-3 relay
US20250113395A1 (en) Methods, architectures, apparatuses and systems for offloading data traffic flows from an edge network of a cellular network to a non-cellular network
WO2023146811A1 (fr) Procédés, architectures, appareils et systèmes pour prendre en charge une zone de desserte de découpage en tranches de réseau
WO2025168644A1 (fr) Procédés et appareils permettant un guidage du trafic sensible au calcul au moyen d&#39;un ancrage d&#39;adresse de protocole internet (ip)
WO2024211727A1 (fr) Procédés, architectures, appareils et systèmes de relocalisation de serveur d&#39;un noeud de consommateur dans un motif sans chevauchement
WO2024147984A1 (fr) Gestion de liaison de bout en bout par l&#39;intermédiaire d&#39;un relais wtru-à-wtru
WO2020036768A1 (fr) Procédés et appareil destinés à l&#39;acheminement de couche 2 des paquets de multidiffusion
EP4470246A1 (fr) Connectivité d&#39;un réseau personnel d&#39;internet des objets
WO2023192146A1 (fr) Sélection d&#39;une route dans un système de communication sans fil
EP4294724A1 (fr) Procédé et système permettant l&#39;interfonctionnement de 5g et eps dans le cadre de la communication de véhicule aérien sans pilote (uav)
WO2022098804A1 (fr) Procédés, architectures, appareils et systèmes de continuité de service pour réseaux locaux
WO2025024278A1 (fr) Procédés, architectures, appareils et systèmes d&#39;information sur les changements de qualité de service dans des éléments de réseau dans des réseaux ido
US20250358223A1 (en) Methods, architectures, apparatuses and systems for ip packet handling using multi-hop relaying
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
WO2025240687A1 (fr) Procédés, architectures, appareils et systèmes pour une communication un-à-plusieurs avec un relais de dispositif à dispositif à sauts multiples
WO2024233262A1 (fr) Procédés, architectures, appareils et systèmes de détermination de division de budget de retard de paquet pour des relais wtru à wtru
WO2025184461A1 (fr) Procédés, appareils et systèmes de direction de trafic sensible au calcul compatible avec la mobilité de service
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
WO2024211728A1 (fr) Procédés, architectures, appareils et systèmes de relocalisation de serveur d&#39;un nœud consommateur dans un schéma de connexion avant déconnexion
WO2025174638A1 (fr) Prise en charge d&#39;un traitement basé sur un ensemble d&#39;unités de données par paquets sur un accès non 3gpp
WO2024233897A1 (fr) Procédés, architectures, appareils et systèmes pour établir des règles de facturation et de contrôle de politique
WO2024233904A1 (fr) Procédés, architectures, appareils et systèmes de gestion de conflits de ressources
WO2025072897A1 (fr) Demande de resélection de relais indiquant un support de relais à sauts multiples
WO2025213024A1 (fr) Commande d&#39;admission de tranche de réseau basée sur la consommation d&#39;énergie

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

Country of ref document: EP

Kind code of ref document: A1