Methods, architectures, apparatuses and systems for informing changed quality of service information in network elements in IoT networks

Abstract

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products for informing changed quality of service information in network elements in IoT networks are described. A gateway device receives information comprising a first set of Quality of Service, QoS, requirements, the information originating from a first network, determines 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, transmits, to the client device, information indicative of the first set of QoS requirements, receives, from the client device, information indicative of whether the first set of QoS requirements is accepted or rejected by the client device, and transmits, to the first network, the information indicative of whether the first set of QoS requirements are accepted or rejected by the client device.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR INFORMING CHANGED QUALITY OF SERVICE INFORMATION IN NETWORK ELEMENTS IN loT NETWORKSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 528,118, filed 21 July 2023 and of U.S. Provisional Application No. 63 / 528,120, filed 21 July 2023, which are incorporated herein by reference in their entirety.BACKGROUND

[0002] 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.SUMMARY

[0003] In a first aspect, 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.

[0004] In a second aspect, 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.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like thedetailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein:

[0006] FIG. 1 A is a system diagram illustrating an example communications system;

[0007] 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;

[0008] 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;

[0009] 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;

[0010] FIG. 2 illustrates an example Personal loT Network, PIN architecture;

[0011] FIG. 3 illustrates an example of the PIN Application Framework in 5G Systems;

[0012] FIG. 4 illustrates a scenario in which a PINE requests communication via the 5GS;

[0013] 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;

[0014] 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;

[0015] 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;

[0016] 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; and

[0017] 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.DETAILED DESCRIPTION

[0018] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description.Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or any portion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.

[0019] Example Communications System

[0020] 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.

[0021] 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. For example, 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.

[0022] As shown in FIG. 1A, 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. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and / or a "STA", 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 mobilesubscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0023] 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. By way of example, 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.

[0024] 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. 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. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, 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. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0025] 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).

[0026] More specifically, as noted above, 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. For example, 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).

[0027] In an embodiment, 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).

[0028] In an embodiment, 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).

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, 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. Thus, 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).

[0030] In an embodiment, 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.

[0031] 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. In anembodiment, 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). In an embodiment, 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). In an embodiment, 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. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0032] 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. 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. Although not shown in FIG. 1 A, it will be appreciated that 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. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing an NR radio technology, 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.

[0033] 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). 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. For example, 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.

[0034] 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 includemultiple transceivers for communicating with different wireless networks over different wireless links). For example, 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.

[0035] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, 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. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0036] 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.

[0037] 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. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In an embodiment, 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.

[0038] Although the transmit / receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include twoor more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0039] 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. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, 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.

[0040] 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. In addition, 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. In other embodiments, 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).

[0041] 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. For example, 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.

[0042] 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. In addition to, or in lieu of, the information from the GPS chipset 136, 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.

[0043] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features,functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. 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.

[0044] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, 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)).

[0045] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, 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.

[0046] 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. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0047] 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, handoverdecisions, 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.

[0048] 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.

[0049] 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. For example, 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.

[0050] 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.

[0051] 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.

[0052] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, 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. In addition, 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.

[0053] Although 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.

[0054] In representative embodiments, the other network 112 may be a WLAN.

[0055] 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. 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). In certain representative embodiments, 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.

[0056] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, 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. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, 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.

[0057] 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.

[0058] Very high throughput (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. For the 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 fouriertransform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving 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.

[0059] 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 in802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 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,802.1 lah may support meter type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0060] WLAN systems, which may support multiple channels, and channel bandwidths, such as802.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. In the example of 802.1 lah, 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.

[0061] In the United States, 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.

[0062] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicatewith the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0063] 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. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, 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. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0064] 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).

[0065] 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. In the 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). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non- standalone configuration 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. For example, 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 substantiallysimultaneously. In the non- standalone configuration, 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.

[0066] 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.

[0067] 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.

[0068] 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. For example, 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. 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. For example, 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. 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.

[0069] 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 policyenforcement 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.

[0070] 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.

[0071] The CN 115 may facilitate communications with other networks. For example, 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. In addition, 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. In an embodiment, 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.

[0072] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, 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.

[0073] 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. For example, 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.

[0074] 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. For example, 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.

[0075] Introduction

[0076] In the description, among others, the following expressions are used.

[0077] Personal loT Network (PIN): A configured and managed group of PIN Elements managed by at least one PIN Element with Management Capability (PEMC) and that are able to communicate with each other directly or via PIN Elements with Gateway Capability (PEGC), communicate with 5G network via at least one PEGC.

[0078] PIN Element (PINE): 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.

[0079] PIN Element with Gateway Capability (PEGC) : 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.

[0080] PIN Element with Management Capability (PEMC): A PIN Element with capability to manage the PIN.

[0081] PINE-to-PINE communication: communication between two PINEs which may use PINE-to-PINE direct communication or PINE-to-PINE indirect communication.

[0082] PINE-to-PINE direct communication: communication between two PIN Elements without PEGC, any 3 GPP RAN or core network entity in the middle.

[0083] PINE-to-PINE indirect communication: communication between two PIN Elements via PEGC or via UPF.

[0084] 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.

[0085] 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.

[0086] N3QAI: Non 3GPP QoS Assistance Information

[0087] Personal Internet of Things networks

[0088] 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.

[0089] When multiple loT devices are deployed in a private environment, UEs with loT capabilities can be organized in a Personal loT Network (PIN). For example, in the home environment, security sensors, smart lights, smart plugs, printers, cellphones, etc. are managed by a residential gateway and can communicate. In this case, all devices in the home constitute a Personal loT Network (PIN). Each device is called a PIN element and different PIN elements have different capabilities. For example, 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. A PIN Element with Management Capability (PEMC) 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).

[0090] 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).

[0091] Personal Internet of Things networks Architecture

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] QOS management in PIN network

[0097] A UE consists of a Terminal Equipment (TE) part and a Mobile Termination (MT) part. Simply speaking, 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.

[0098] Being UEs, 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).

[0099] 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.

[0100] 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.

[0101] QoS experienced by PINEs connected behind a PEGC depends on the end-to-end path between a PINE and the application server. 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. Based on the N3QAI together with QoS rule information, the PEGC may reserve resources in the non-3GPP network.

[0102] However, how to enforce QoS based on the N3QAI in the non-3GPP network is considered outside the scope of 3GPP.

[0103] TS 23.542, Section 8.6.2.2, describes PINE requesting communication to 5GS. FIG. 4 describes the scenario in which a PINE requests communication via the 5GS. In step S402, PINE 412 sends a request for 5G communication to PEGC 416. The request includes QoS (e.g., packet delay, AMBR) for a packet flow. In step S404, 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. In step S406, the PEGC 416 informs the PINE 412 about the N3QAI.

[0104] The PDU Session Modification Command can be triggered by the network at any time. As per the definition of the PDU session modification command, the PEGC (MT) can receive modified N3QAI for the non-3GPP connection between PEGC and PINEs. As described in herein, the PINE is informed about the QoS information after having requested 5G communication. However, there is no mechanism to inform the PINEs about QOS information changes, for example when the network changes, modifies, or updates QoS information.

[0105] One resulting problem is how do members of the PIN become aware of the changes in QoS indicated by network so that they can adjust their application layer behavior to account for the modified QoS information, i.e., N3QAI?

[0106] Further, the N3QAI that is received by the PEGC (MT), via the PDU Session Modification Command, might indicate that notification control is enabled. 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.

[0107] 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.

[0108] 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?

[0109] Introduction

[0110] 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.[OHl] 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.

[0112] 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.

[0114] A PIN client can subscribe to a PEGC or PEMC client to receive notification about QOS / N3QAI changes.

[0115] Various embodiments of the present principles will now be briefly described before a more detailed description.

[0116] PEGC Client handles the N3QAI changes

[0117] 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.

[0118] 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.

[0120] 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.

[0121] 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.

[0122] PEMC Client handles the N3QAI changes

[0123] 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.

[0124] 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.

[0125] 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. Optionally, the message can include if the QOS requirement cannot be met. The response may include the identity of the PIN Clients.

[0126] 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 identifythe 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.

[0127] PEGC Client handles notification control

[0128] 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.

[0129] The PEGC Client determines the identity of a PIN Client that is associated with the at least one data flow.

[0130] 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.

[0131] The PEGC Client receives a message from the PIN Client. The message indicates that the QoS Requirement is rejected or cannot be met.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] PEMC Client handles notification control

[0136] 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.

[0137] 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.

[0138] 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.

[0140] 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.

[0141] Detailed description

[0142] 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.

[0143] In the description of FIGs. 5-9 and, as the case may be, elsewhere herein, the following terms may be used:

[0144] New N3QAI: First option for N3QAI provided by network.

[0145] Alternate N3QAI: Second option for N3QAI provided by network.

[0146] Accepted N3QAI: The new N3QAI or alternate N3QAI accepted by PINE.

[0147] Accepted QoS: Same as accepted N3QAI, used to inform PIN server and AS.

[0148] Rejected QoS: New N3QAI, alternate N3QAI or both, rejected by PINE.

[0149] According to the present principles, 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.

[0150] 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.

[0151] As illustrated in FIG. 5A, having determined to change or update the QOS information, including N3QAI, provided to PEGC for the PIN, in step S502, the 5GS 509 sends a PDU Session Modification Command with the new N3QAI and alternate N3QAI to the PEGC (MT) 507.

[0152] In 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.

[0153] In 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 theidentities 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.

[0154] In 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.

[0155] In 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. For example, 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.

[0156] In 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. For example, 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.

[0157] In step S514, 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.

[0158] Turning to FIG. 5B, in step S516, 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.

[0159] In step S518, 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.

[0160] In 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.

[0161] In case the PIN server 511 received a message about QoS change in step S514 or step S518, 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 thatcapability. After reception of the update, the AS can take action, such as increase or decrease data rate, as per the QOS notification.

[0162] 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.

[0164] In 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.

[0165] In 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.

[0166] In step S612, 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. For example, 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.

[0167] In 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.

[0168] In step S616, 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.

[0169] Turning to FIG. 6B, in 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.

[0170] In step S620, 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.

[0171] In 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 theaccepted N3QAI (new or alternate) or rejected QOS by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID

[0172] In 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. As described with reference to step S520, 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.

[0173] In case the PIN server 611 received a message about QoS change in step S616 or step S620, in 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.

[0174] 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.

[0175] In embodiments, 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.

[0176] In embodiments, 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. Alternatively, the PEMCclient informs the PEGC client and the PEGC MT, which can update the network by triggering PDU session modification procedure.

[0177] 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.

[0178] 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. As illustrated in FIG. 7A, in step S702, the 5GS sends a PDU Session Modification Command with new N3QAI, alternate N3QAI and notification control enabled to the PEGC (MT) 707.

[0179] In 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.

[0180] In 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)

[0181] In 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.

[0182] In step S710, 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. For example, 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.

[0183] In 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. For example, the message may indicate the alternate N3QAI that the PINClient will use. The rejected QOS includes both new and alternate N3QAI with notification control enabled and indicates both are not accepted by the PINE.

[0184] In embodiments, the PIN Client 701 processes the response from application client. In case the application client rejects the new or alternate N3QAI, 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.

[0185] Turning to FIG. 7B, in other embodiments, after receiving a message that no N3QAI is accepted, the PEGC Client 705 determines that the AS should be informed (because notification control was enabled). In step S714b, 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. In step S716, 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. In step S718, 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. As described with reference to step S520, 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. In step S720, the 5GS 709 informs the PIN Server / AS 711 that the N3QAI with notification control cannot be met.

[0186] In yet other embodiments, in step S714c, 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.

[0187] 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.

[0188] According to the first embodiment, 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.

[0190] In 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.

[0191] In 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.

[0192] In 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.

[0193] 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.

[0194] 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.

[0195] In 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. As described with reference to step S520,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.

[0196] In step S820, the 5GS 809 informs the PIN Server / AS 811 that the N3QAI with notification control cannot be met.

[0197] In 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.

[0198] In step S824, the PIN client 801 informs the application client and starts PEGC discovery.

[0199] 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.

[0200] According to the second embodiment, 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.

[0201] As illustrated in FIG. 9A, 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.

[0202] In step S908, the PEGC Client 905 sends N3QAI change request message to the PEMC client 903 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 903 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 903 has subscribed to PEGC client.

[0203] In step S910, the PEMC client 903 determines that new and alternate N3QAI information with GFBR and notification control enabled, is available for the PINE. The PEMC client 903 cannot determine if the PINE can support the new N3QAI. The PEMC client 903 determines to inform the PINE about the QOS information along with a list of PEGC information. If the PINE cannot support the N3QAI, then it can discover a new PEGC.

[0204] In step S912, the PEMC Client 903 sends N3QAI change request message to the PIN client 901 in a PINE to inform about the new N3QAI, alternate N3QAI, GFBR with notificationcontrol enabled and the impacted flow id identified by Flow ID. The message can be a notification if PIN client has subscribed to PEMC client.

[0205] In step S914, the PIN Client 901 can inform an application client about the new N3QAI, alternate N3QAI and notification control enabled. 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. For example, 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.

[0206] In step S916, the PIN Client 901 sends a N3QAI change response message to PEMC client, indicating either that it accepts the new or alternate N3QAI with notification control or that it cannot support the suggested N3QAI by including rejected QOS information.

[0207] Upon determination that notification control is enabled, the PIN client 901 may determine to inform, in step S918, the PIN server 911. If so, the PIN Client 901 can directly inform the PIN server 911 about the accepted QOS or rejected QOS with notification control enabled, by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID, by sending a QoS change indication message.

[0208] Turning to FIG. 9B, in step S920, the PEMC client 903 determines if 5GS / AS needs to be informed as notification control is enabled. If the PINE cannot support the requested QOS and indicated by sending rejected QOS, PEMC client determines that AS needs to be informed.

[0209] In step S922, in response to the request received in step S908 from PEGC Client 905, the PEMC client 903 sends a N3QAI change response message to the PEGC client 905, indicating if the PIN client accepted N3QAI (new or alternate) or rejected the changed / updated QOS with notification control enabled, including the PINE ID to indicate the PINE and impacted flow by indicating Flow ID.

[0210] After receiving the QOS Reject message, the PEGC Client 905 determines that the AS should be informed (because notification control was enabled). In step S924, the PEGC Client 905 sends a N3QAI change response message to respond to the PEGC MT’s request in step S906. The message can include information about the rejected QoS (new or alternate N3Q Al with notification control enabled) by the PINE, indicated by PINE ID, and the impacted flow, indicated by Flow ID

[0211] In step S926, the PEGC MT 907 sends at least one PDU Session Modification Request to the network 909. The PDU Session Modification Request indicates a N3QAI that was rejected for use within the PIN. As described with reference to step S520, the PDU Session ModificationRequest can be per PINE and indicate a N3QAI that was accepted or rejected for use by the respective PINE within the PIN.

[0212] In step S928, the 5GS 909 informs the PIN Server / AS 911 that the N3QAI with notification control cannot be met.

[0213] In step S930, the PEMC client 903 may inform the PIN server 911 about the accepted QOS or rejected QOS with notification control enabled, by the PINE identified by PINE ID and the flow identified by Flow ID.

[0214] In step S932, the PIN server 911 informs the AS about the QOS rejected by the PINE by indicating the rejected QOS by a PINE identified by PINE ID and the impacted flow identified by Flow ID. The AS can take action, such as decrease data rate, as per the QOS notification.

[0215] Summing up, the present disclosure describes different solutions.

[0216] A Wireless Transfer / Receive Unit, WTRU, can receive, from a first network, information comprising a first set of Quality of Service, QoS, parameters and a second set of QoS parameters, determine devices in a second network, for which the device acts as a gateway to the first network, involved in traffic flows impacted by the first and second set of QoS parameters, transmit to the determined devices information indicative of the first and second set of QoS parameters, receive, from at least one determined device, information indicative of an accepted set of QoS parameters among the first and second set of QoS parameters or of a rejection of both the first and second set of QoS parameters, and transmit, to the first network, information indicative of at least one of a set of QoS parameters accepted or a rejection of the first and second set of QoS parameters by a determined device in the second network.

[0217] A Wireless Transfer / Receive Unit, WTRU, can receive, from a first gateway device in a first network in which the WTRU is a managing device, information comprising a first set of Quality of Service, QoS, parameters and a second set of QoS parameters, upon determination that further devices in the first network cannot support the first or the second set of QoS parameters, transmitting to the gateway device information indicative of rejection of the first and second set of QoS parameters, and transmit, to the further devices, a message indicative of a request to change gateway device from the first gateway device to a second gateway device.

[0218] A Wireless Transfer / Receive Unit, WTRU, can receive, from a gateway device in a first network in which the WTRU is a managing device, information comprising a first set of Quality of Service, QoS, parameters and a second set of QoS parameters, transmit, to further devices in the first network, information indicative of the first and second set of QoS parameters, receive, from at least one further device, information indicative of an accepted set of QoS parameters among the first and second set of QoS parameters or of a rejection of both the first and second setof QoS parameters, transmit, to the gateway device, information indicative of at least one of a set of QoS parameters accepted or a rejection of the first and second set of QoS parameters by a further device in the second network, and transmit, to a server in a second network connected to the gateway device, information indicative of at least one of a set of QoS parameters accepted or a rejection of the first and second set of QoS parameters by a further device in the second network.

[0219] Conclusion

[0220] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0221] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0222] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and / or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and / or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and / or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and / or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may berepresentative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0223] In addition, 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.

[0224] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0225] Moreover, in the embodiments provided above, 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. 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."

[0226] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to therebyreconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0227] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0228] In an illustrative embodiment, 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.

[0229] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and / or systems and / or other technologies described herein may be effected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0230] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples may be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, severalportions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of 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., 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.).

[0231] Those skilled in the art will recognize that it is common within the art to describe devices and / or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that 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.

[0232] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depictedarchitectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, 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. Specific examples of 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.

[0233] With respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0234] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., thebare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, 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. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0235] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0236] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a rangeincludes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0237] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMSWhat is claimed is:

1. A method comprising in a gateway device: 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.

2. The method of claim 1, further comprising: receiving, from the first network, information comprising a second set of QoS parameters; wherein the client device is further involved in at least one traffic flow impacted by the second set of QoS parameters; transmitting, to the client device, information indicative of the second set of QoS parameters; receiving, from the client device, information indicative of whether the second set of QoS requirements is accepted or rejected by the client device; and transmitting, to the first network, information indicative of whether the second set of QoS requirements are accepted or rejected by the client device.

3. The method of claim 1 or 2, wherein: the received first set of QoS requirements are for the at least one traffic flow; the received information further comprises an indication that notification control is enabled; and the information transmitted to the client device further comprises an indication that notification control is enabled.

4. The method of claim 2, further comprising: transmitting, to the client device, the information indicative of the traffic flows impacted by at least one of the first set of QoS requirements and the second set of QoS requirements.

5. The method of claim 2, wherein: the information indicative of whether the second set of QoS requirements are accepted or rejected by the client device is transmitted to an application server.

6. The method of claim 2, wherein the received information indicative of whether the first set of QoS requirements is accepted or rejected by the client device and of whether the second set of QoS requirements is accepted or rejected by the client device either indicate that one of the first and the second set of QoS requirements is accepted or that both the first and the second set of QoS requirements are rejected.

7. The method of claim 2, further comprising: transmitting, to the first network, information indicative of the at least one traffic flow.

8. The method of claim 2, wherein: the information transmitted to the first network is transmitted in a request to modify a packet data unit session.

9. 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.

10. The device of claim 9, wherein the at least one processor is further configured to:receive, from the first network, information comprising a second set of QoS parameters; wherein the client device is further involved in at least one traffic flow impacted by the second set of QoS parameters; transmit, to the client device, information indicative of the second set of QoS parameters; receive, from the client device, information indicative of whether the second set of QoS requirements is accepted or rejected by the client device; and transmit, to the first network, information indicative of whether the second set of QoS requirements are accepted or rejected by the client device.

11. The device of claim 9 or 10, wherein: the received first set of QoS requirements are for the at least one traffic flow; the received information further comprises an indication that notification control is enabled; and the information transmitted to the client device further comprises an indication that notification control is enabled.

12. The device of claim 10, wherein the at least one processor is further configured to: transmit, to the client device, the information indicative of the traffic flows impacted by at least one of the first set of QoS requirements and the second set of QoS requirements.

13. The device of claim 10, wherein: the information indicative of whether the second set of QoS requirements are accepted or rejected by the client device is transmitted to an application server.

14. The device of claim 10, wherein the received information indicative of whether the first set of QoS requirements is accepted or rejected by the client device and of whether the second set of QoS requirements is accepted or rejected by the client device either indicate that one of the first and the second set of QoS requirements is accepted or that both the first and the second set of QoS requirements are rejected.

15. The device of claim 10, wherein the at least one processor is further configured to: transmit, to the first network, information indicative of the at least one traffic flow.

16. The device of claim 10, wherein: the information transmitted to the first network is transmitted in a request to modify a packet data unit session.

Images