SYSTEM AND METHOD FOR SUPPORTING ADAPTIVE QoS FLOW AND PROFILE
By using data characteristic tags and policy control functions in WTRU, the QoS flow is dynamically adjusted, which solves the problem of difficulty in adapting to changes in application data flow characteristics in the prior art, and achieves flexible adjustment and adaptation to service quality.
Patent Information
- Application Number
- CN202380033613.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-28
- Filing Date
- 2023-03-28
- Publication Date
- 2024-11-29
AI Technical Summary
The prior art is difficult to effectively adapt and adjust quality of service (QoS) flows to cope with changes in application data flow characteristics, making it difficult for the network to dynamically modify QoS flows to meet changing data characteristics requirements.
Dynamically map service data flow (SDF) to appropriately use the introduction of data characteristic tag information in the wireless sending/receiving unit (WTRU), combining policy control function (PCF) and session management function (SMF). QoS stream to adapt to data characteristics changes.
Real-time perception and dynamic adjustment of application data flow characteristics is realized, ensuring that the network can automatically adjust QoS flow according to changes in data characteristics, thereby improving the flexibility and adaptability of the network.
Smart Images

Figure CN119054331A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 324,386, filed on March 28, 2022, the contents of which are hereby incorporated by reference into this document. Background Art
[0003] In the 5G Core (5GC), a Quality of Service (QoS) flow is associated with a QoS profile, which may include QoS parameters such as 5G QoS Class Identifier (5QI), Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), etc. The standard 5QI in the profile is associated with a set of more detailed QoS characteristics such as resource type, packet delay budget, etc. For non-standard 5QI, these detailed QoS characteristics need to be signaled in the QoS profile. Summary of the invention
[0004] A wireless transmit / receive unit (WTRU) may receive a plurality of quality of service (QoS) rules, wherein each of the QoS rules includes data characteristic tag information; receive data traffic, wherein the data traffic includes a service data flow (SDF). The WTRU may select a QoS rule based on a determined traffic characteristic of the SDF and the data characteristic tag information; map the SDF to a QoS flow based on the selected QoS rule; and transmit the QoS flow. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:
[0006] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;
[0007] Figure 1B is an example of an embodiment in which Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;
[0008] Figure 1C is an example of an embodiment in which Figure 1A a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;
[0009] Figure 1D is an example of an embodiment in which Figure 1AA system diagram of another example RAN and another example CN used within the illustrated communication system;
[0010] Figure 2 is an example of a specific implementation of an enhanced QoS rule with data characteristic mapping;
[0011] Figure 3 is an example of establishing an alternative QoS profile associated with data characteristics; and
[0012] Figure 4 is an example of a process for selecting QoS rules based on data characteristics. DETAILED DESCRIPTION
[0013] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.
[0014] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood 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 (STA)) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0015] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B such as a gNode B (gNB), a new radio (NR) Node B, 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.
[0016] The base station 114a may be part of the RAN 104, 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), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send 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 a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver 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 sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.
[0017] 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).
[0018] More specifically, as noted above, the communication 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, etc. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), that may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols, such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed Uplink (UL) Packet Access (HSUPA).
[0019] 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) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).
[0020] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology (such as NR radio access) that may establish the air interface 116 using NR.
[0021] 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 together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).
[0022] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, 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), etc.
[0023] Figure 1AThe base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, 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 yet another 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 a picocell or a femtocell. As Figure 1A As shown, the base station 114 b may have a direct connection to the Internet 110. Therefore, the base station 114 b may not need to access the Internet 110 via the CN 106.
[0024] The RAN 104 may be in communication with the CN 106, 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 may be 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. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0025] The CN 106 may also act 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 a circuit-switched telephone network that provides 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication 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 or a different RAT.
[0026] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c 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.
[0027] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0028] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, 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. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0029] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station by an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, IR, UV or visible light signals. In another embodiment, the send / receive element 122 may be configured to send and / or receive both RF signals and optical signals. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.
[0030] Although the transmit / receive element 122 Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0031] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0032] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an 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 a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0033] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to 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, etc.
[0034] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0035] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, etc. The peripheral device 138 may include one or more sensors. The sensor may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geographic location sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, etc.
[0036] 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 specific subframes for both UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the 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 specific subframes for both UL (e.g., for transmission) or DL (e.g., for reception)) may be concurrent and / or simultaneous.
[0037] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0038] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0039] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0040] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0041] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 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, etc. 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.
[0042] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0043] 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.
[0044] 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 be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.
[0045] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.
[0046] In a representative embodiment, the other network 112 may be a WLAN.
[0047] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Services originating from outside the BSS and directed to the STA may be reached by the AP and may be delivered to the STA. Services originating from the STA and directed to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Services between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit services to the AP, and the AP may deliver services to the destination STA. Services between STAs within the BSS may be considered and / or referred to as point-to-point services. Point-to-point services may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.
[0048] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. In the case where the primary channel is listened / detected and / or determined to be busy by a specific STA, the specific STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.
[0049] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0050] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).
[0051] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).
[0052] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum 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 (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. In the case where the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is transmitting to the AP, all available bands may be considered busy even if most of the available bands remain idle.
[0053] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.
[0054] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0055] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 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 one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send 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, gNB 180a may transmit multiple component carriers to 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, 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).
[0056] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. 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 the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).
[0057] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0058] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR, and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.
[0059] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0060] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 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, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 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.
[0061] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy implementation and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0062] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.
[0063] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.
[0064] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following items may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.
[0065] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions 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. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for the purpose of testing and / or performing tests using over-the-air wireless communications.
[0066] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) can be used by the simulation device to send and / or receive data.
[0067] The acronyms and abbreviations used in the preceding and following paragraphs may be defined as follows:
[0068] The terms further defined herein may be referred to using a variety of different symbols. Hereinafter, "a", "an" and similar phrases may be interpreted as "one or more" and "at least one". Similarly, any term ending with the suffix "(s)" may be interpreted as "one or more" and "at least one". For example, the term "may" may be interpreted as "can".
[0069] AF Application Function
[0070] AI
[0071] DCL Data Characteristic Label
[0072] ML Machine Learning
[0073] NEF Network Exposure Function
[0074] NG-RAN Next Generation Radio Access Node
[0075] PCC Strategy and Charging Control
[0076] PCF Policy Control Function
[0077] PDU Packet Data Unit
[0078] SDF Service Data Flow
[0079] SMF session management functions
[0080] QFI QoS Flow Identifier
[0081] QoS Quality of Service
[0082] TCP Transmission Control Protocol
[0083] UPF User Plane Function
[0084] In an embodiment, the WTRU may be configured with QoS rules that map application data flows to QoS flows. The QoS rules may use packet filters (e.g., IP addresses, port ranges, etc.) to identify data flows associated with QoS flows. Data flows that match the packet filters may be transmitted / received on the same QoS flow.
[0085] The network, which may include a session management function (SMF) in an embodiment, may provide an alternative QoS profile for a guaranteed bit rate (GBR) QoS flow to a next generation radio access node (NG-RAN). The alternative QoS profile may include a combination of QoS parameters to which the application service may be able to adapt. When the NG-RAN cannot meet the configured QoS profile but can meet the alternative QoS profile, it may report a reference to the satisfied alternative QoS profile to the network.
[0086] Some application data flows may sometimes require different characteristics. For example, an artificial intelligence (AI) / machine learning (ML) application client may exchange signaling (e.g., configuration data) with a server, and may pass a training model to / receive a training model from the server. The former data exchange may be low bit rate, non-delay sensitive, while the latter model transfer may be bursty, high bit rate, and delay sensitive. However, these different data transfers may use the same data connection (e.g., a Transmit Control Protocol (TCP) connection) and may not be distinguished by various packet filters, and the network / WTRU may not use QoS rule configuration to map them to different QoS flows with different QoS profiles. In addition, the data service may vary depending on the AI / ML application operation used over the data connection. For example, in the case where the AI / ML application operation corresponds to a federated learning operation, the service on the packet data unit (PDU) session may suddenly increase when the inference window is about to close.
[0087] The network may not know when the application data may change its characteristics drastically, so it is difficult for the network to modify the QoS flow to adapt to the data flow. Therefore, methods are needed to solve the following problems: (i) how the WTRU and the network notice the changing data characteristics of the application data flow, and (ii) how the WTRU and the network modify the QoS flow / QoS profile to adapt to the changing data flow.
[0088] Figure 2 An example implementation of an enhanced QoS rule with data characteristic mapping is shown. In an embodiment, it may be assumed that a policy control function (PCF) 10 is aware of the various data characteristics of an application. Some examples of data characteristics may be: "low bit rate", "high bit rate", "delay sensitive", "delay tolerant", "burst", and "loss tolerant". The PCF may create different policy and charging control (PCC) rules 12 that may be associated with the same service data flow (SDF). The PCF 10 may include a "data characteristic label" (DCL) as part of the SDF template in the PCC rule. The "data characteristic label" may represent one or a combination of data characteristics. For example, the PCF 10 may create two PCC rules for the SDF, wherein one of the PCC rules may have a "burst and delay tolerant" data characteristic as a "data characteristic label" in the SDF template, while the other PCC rule may have a "non-burst and delay sensitive" data characteristic as a "data characteristic label" in the SDF template. The packet filters of these two PCC rules may be the same. Introducing "data characteristic tags" in PCC rules may enable the network and WTRU 40 to transmit application data flows through different QoS flows when the data characteristics vary drastically and may require different QoS treatments.
[0089] In an embodiment, the AF may provide the PCF (possibly through the NEF) with a list of AI / ML operations associated with a single network slice selection assistance information (S-NSSAI) and a data network name (DNN) and an associated fully qualified domain name (FQDN). These operations may be mapped to specific "data characteristics" by the PCF. When the WTRU 40 receives the "data characteristics" information in the PCC rules, the WTRU 40 may remap the "data characteristics" to specific AI / ML operation types.
[0090] Based on the PCC rules with the data characteristic tags received from the PCF, the SMF 20 may be able to create QoS rules associated with the "data characteristic tags" in the PCC rules. In the case where there are multiple PCC rules associated with the SDF, the SMF 20 may also create multiple QoS rules 21, 22 for the same SDF, which may allow the WTRU to transmit application services through different QoS flows according to the current data characteristics.
[0091] The AI / ML engine in the WTRU or CN can use a data set that has been successfully used and has PCC rules as a labeled data set for training and subsequent PCC rule recommendations. In this way, the AI / ML engine can enable dynamic creation of PCC rules.
[0092] The application layer 42 in the WTRU 40 may be able to indicate the current characteristics of the SDF. The application layer may indicate to the lower layers one or a combination of characteristics of the data to be transmitted. The indication may be sent on a per-packet basis (i.e., accompanying each packet to be transmitted) or may be transmitted when the data characteristics change. For example, when the AI / ML application client in the WTRU starts to deliver training model data, it may indicate to the communication module (which may be a cellular wireless communication module in an embodiment) that the future data characteristics have changed to, for example, bursty, high bit rate, and loss intolerant. In the case where such data characteristic indications are available from the upper layers, in addition to matching the packet filters, the WTRU 40 may also attempt to match it with a data characteristic tag that is associated with the QoS rules 41, 42. In the case where a match can be found, the WTRU may transmit the data via the QoS flow associated with the matched QoS rule. In the case where no match can be found (which may mean an exact match in an embodiment), the WTRU may find a close match (which may be the closest match in an embodiment) and use that QoS rule.
[0093] When the corresponding QoS flow is identified, the SDF packet is delivered to the lower layer (i.e., access layer) along with the QoS flow identifier (i.e., UL packet of SDF tagged with QFI) for UL transmission. The WTRU access layer may have a QoS flow to data radio bearer (DRB) mapping rule configured by the NG-RAN, and further maps the UL packet to the corresponding DRB using the rule. The data of the DRB is then multiplexed with other DRBs to form a transport block (e.g., at the media access layer), and the data is delivered to the NG-RAN and the network over the air interface.
[0094] In an embodiment, the WTRU may be able to sense traffic pattern changes and generate data characteristic tags for the current traffic.
[0095] In an embodiment, the SMF may create multiple alternative QoS profiles associated with various data characteristics based on PCC rules. The SMF may provide the alternative QoS profiles to relevant nodes (e.g., NG-RAN). In an embodiment, when the WTRU detects a drastic change in application data characteristics (which in an embodiment may include receiving a data characteristic indication from an upper layer), the WTRU may initiate a session management (SM) procedure (which in an embodiment may be a PDU session modification request) to notify the SMF of such changes. The WTRU may indicate the affected QoS flows and the new data characteristics to the SMF. The SMF may identify the alternative QoS profile associated with the new data characteristics and notify the relevant nodes (e.g., NG-RAN) to apply the new alternative QoS profile to the affected QoS flows.
[0096] The application client or WTRU may have a configuration that enables it to anticipate potential traffic pattern changes. For example, the configuration for an AI / ML client may indicate a specific time period during which federated learning training may be performed, which may result in significant changes in data characteristics. The WTRU may notify the network of potential changes in advance.
[0097] The network entity (which may be UPF or AF in the implementation) may detect or predict changes in the traffic pattern of the application. For example, the UPF may sense the traffic pattern change and trigger an event notification to the SMF, or the AF may predict the change and notify the SMF. The SMF may notify the QoS enforcement point (which may be NG-RAN) to apply the new QoS profile accordingly.
[0098] Figure 3 An example of generating an alternative QoS profile associated with a data characteristic is shown. At 310, the WTRU 310 may initiate a PDU session establishment procedure. The WTRU 310 may indicate to the network that it is capable of detecting changes in data characteristics. As part of the PDU session establishment procedure, the SMF 314 may receive one or more PCC rules 322 from the PCF 316. The PCC rules 322 may be associated with data characteristics (DCL) with corresponding QoS requirements (associated QoS). The SMF 314 may configure the QoS rules 322 and transmit the QoS rules to the WTRU 310. In the case where the QoS flow may experience potential changes in data characteristics according to the PCC rules, the SMF 314 may configure one or more alternative QoS profiles 326 corresponding to various data characteristics and transmit the one or more alternative QoS profiles to a relevant node, which may be a NG-RAN, where QoS processing may be performed. At 328, when the WTRU 310 detects or predicts a change in the data characteristics, the WTRU 310 may initiate a PDU session modification request 330 to notify the SMF 314 of the affected QoS flows (e.g., using a QoS flow identifier (QFI)) and the new data characteristics. The WTRU 310 may detect the change in data characteristics, for example, by an indication received from upper layers. The WTRU may suggest an alternative QoS profile for the new data characteristics. At 332, the SMF may identify an alternative QoS profile corresponding to the new data characteristics, or use the WTRU-proposed QoS profile. At 334, the SMF 314 may transmit a new QoS profile corresponding to the new data characteristics or a reference / reference to an existing alternative QoS profile to the NG-RAN, so that the NG-RAN applies the new alternative QoS profile.
[0099] Figure 44 is a flow chart of an exemplary method implemented in a WTRU. At 410, the WTRU receives a plurality of quality of service (QoS) rules, wherein each of the QoS rules may include data characteristic tag information. At 412, the WTRU receives data traffic, wherein the data traffic may include a service data flow (SDF). At 414, the WTRU selects a QoS rule based on determined traffic characteristics and data characteristic tag information of the SDF. At 416, the WTRU maps the SDF to a QoS flow based on the selected QoS rule. At 418, the WTRU sends the QoS flow.
[0100] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described 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 (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving a plurality of quality of service (QoS) rules, wherein each of the QoS rules includes data characteristic tag information; receiving a data service, wherein the data service comprises a service data flow (SDF); Determining the service characteristics of the SDF; Selecting QoS rules based on the determined service characteristics of the SDF and the data characteristic tag information; Mapping the SDF to a QoS flow based on the selected QoS rule; as well as Send the data service QoS flow. 2 . The method according to claim 1 , wherein the data characteristic tag information comprises at least one of the following: low bit rate, high bit rate, delay sensitive, delay tolerant, poor tolerance, and burst.
3. A method according to any preceding claim, wherein the received QoS rules are for the same application.
4. The method according to any preceding claim, further comprising: The service characteristics of the SDF are determined based on a service pattern or information from a higher layer.
5. The method according to any preceding claim, further comprising: An indication is transmitted by the WTRU to a network node that the WTRU is capable of detecting a change in a characteristic of data.
6. The method according to any preceding claim, further comprising: In the case where the WTRU detects a change in data characteristics, the WTRU initiates a PDU session modification request to the (Session Management Function) SMF.
7. A method according to any preceding claim, wherein the PDU session modification request comprises a QoS Flow Identifier (QFI) and new data characteristics.
8. The method according to any preceding claim, further comprising: A data characteristic indication is received by the WTRU.
9. A WTRU configured to perform the method according to any one of the preceding claims.
