Routing in wireless communication system
The WTRU processor in wireless communication systems optimizes PDU sessions for AI applications by modifying connections based on routing policy information and location, addressing routing challenges and enhancing performance metrics.
Patent Information
- Application Number
- CN202380034463.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-28
- Filing Date
- 2023-03-27
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems face challenges in efficiently routing data and control information, particularly for artificial intelligence machine learning applications, due to architectural constraints and limitations in existing traffic routing mechanisms.
A wireless transmit/receive unit (WTRU) processor is configured to receive routing policy information, determine an existing protocol data unit (PDU) session, and modify it to connect to a second data network based on location and criteria, performing AI operations before and after the modification, using mappings between AI operations and data networks.
Enhances the routing of data and control information for AI applications by optimizing network connections based on location and network criteria, improving latency, congestion, and quality of service levels.
Smart Images

Figure CN119072958A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 324,330, filed on March 28, 2022, the contents of which are incorporated herein by reference. Background Art
[0003] Data and control information, such as data and control information associated with artificial intelligence machine learning (AIML) applications or tasks, may be carried in wireless communication systems, such as fifth generation (5G) new radio (NR) systems. To facilitate the transmission or reception of such information, constraints (e.g., architectural assumptions) may be imposed on the communication system, and existing traffic routing mechanisms may be reused, repurposed, and / or enhanced to support AIML applications or tasks. Summary of the invention
[0004] Systems, methods, and means associated with routing in a wireless communication network are disclosed herein. A wireless transmit / receive unit (WTRU) according to an embodiment of the present disclosure may include a processor configured to receive routing policy information from a network device, wherein the routing policy information may indicate at least a first data network, a second data network, a network slice for the WTRU to connect to the first data network or the second data network, and criteria associated with routing. The processor may be further configured to: determine an existing protocol data unit (PDU) session associated with the first data network, which can be established using the network slice indicated by the routing policy information; determine that the second data network can meet the criteria associated with routing based at least on the location of the WTRU and the routing policy information; and send (e.g., to the network device) a PDU session modification request indicating that the existing PDU session will be associated with the second data network (e.g., using the same network slice indicated by the routing policy information and / or by changing the destination of the existing PDU session to a device associated with the second data network).
[0005] In an example, the processor of the WTRU may be configured to perform a first artificial intelligence machine learning (AIML) operation using the existing PDU session before the sending of the PDU session modification request. After the sending of the PDU session modification request, the processor may be configured to receive a response indicating that the existing PDU session has been modified (e.g., connected to a device in the second data network), and perform a second AIML operation using the modified PDU session.
[0006] In an example, the criterion provided in the routing policy information may be a mapping between AIML operations and data networks, a mapping between locations and data networks, and / or at least one of a latency level, a network congestion level, or a quality of service level. In an example, the processor of the WTRU may be further configured to receive an analysis associated with the WTRU from the network device, and further determine, based on the received analysis, that the second data network satisfies the criterion indicated in the routing policy information.
[0007] In an example, at least one of the first AIML operation or the second AIML operation may be associated with federated learning, and the routing policy information may include a first routing descriptor (RSD) indicating a data network name (DNN) of the first data network and a second RSD indicating the DNN of the second data network. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.
[0009] Figure 1B is an example of a method that can be used according to an embodiment of the present invention. Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system.
[0010] Figure 1C is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of an example Radio Access Network (RAN) and an example Core Network (CN) for use within the illustrated communication system.
[0011] Figure 1D is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of yet another example RAN and yet another example CN for use within the illustrated communication system.
[0012] Figure 2 is a diagram illustrating an example of modifying a PDU session to support WTRU operations such as AIML operations.
[0013] Figure 3 is a diagram illustrating an example of information exchange between a WTRU and one or more network devices or entities. DETAILED DESCRIPTION
[0014] Figure 1A1 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 DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.
[0015] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, 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” and / or “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.
[0016] 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 that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or 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 (gNB), an 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 should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0017] 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), 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 cells (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.
[0018] 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).
[0019] 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 / 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 use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0020] 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).
[0021] 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).
[0022] 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).
[0023] 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.
[0024] Figure 1A The 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, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.
[0025] 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 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 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 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. 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 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Figure 1AAlthough not shown in the figure, 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 utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0026] 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 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 / 113 or a different RAT.
[0027] 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.
[0028] 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.
[0029] 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) circuit, 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.
[0030] 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 via 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.
[0031] 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.
[0032] 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.
[0033] The processor 118 of the WTRU 102 may be coupled to 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) and may receive user input data therefrom. 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).
[0034] 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.
[0035] 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.
[0036] 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, which 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 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.
[0037] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed via 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 WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.
[0038] 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.
[0039] 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.
[0040] 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.
[0041] 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 (or PGW) 166. While each of the foregoing elements is 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 a CN operator.
[0042] The MME 162 may be connected to each of the evolved Node-Bs 160a, 160b, 160c 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.
[0043] 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 handover, 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.
[0044] 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.
[0045] 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.
[0046] 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 communication interface with a communication network.
[0047] In a representative embodiment, the other network 112 may be a WLAN.
[0048] 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. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link establishment (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.
[0049] 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 width dynamically set via signaling. 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. If the primary channel is listened / 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.
[0050] 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.
[0051] 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).
[0052] 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 instrument type control / machine type communications, 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).
[0053] 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. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.
[0054] 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.
[0055] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 in accordance with an embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.
[0056] 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 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, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and the gNB 180b (and / or the gNB 180c).
[0057] 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 transmit time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths over time).
[0058] 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 WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.
[0059] 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 UL and / or DL, support of network slicing, dual connectivity, interworking between 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.
[0060] Figure 1DThe illustrated CN 115 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 each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0061] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 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 PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of 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 mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. 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.
[0062] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 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 enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0063] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 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 downlink packets, providing mobility anchoring, etc.
[0064] 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 acts 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 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 local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
[0065] 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 may be performed by one or more simulation devices (not shown): WTRU102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-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.
[0066] 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 testing purposes and / or may use over-the-air wireless communications to perform testing.
[0067] 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.
[0068] The functionality and / or features of the wireless communication system as described herein may be enhanced, repurposed, or reused to support additional service types such as AIML application (e.g., federated learning) services. For example, an application function (AF) may be configured to provide guidance (e.g., regarding geographic location or region, AF identifier, latency requirements, quality of service (QoS) criteria, etc.) to a device (e.g., WTRU) in a wireless communication system to enable the device to establish and implement user equipment routing policy (URSP) rules. Such URSP rules may include, for example, rules for determining network slices (e.g., represented by single network slice selection assistance information (S-NSSAI)), data networks (e.g., represented by data network names (DNNs)), AF instances, protocol data unit (PDU) sessions, edge application servers (EASs), etc. that may be used by the device to perform its functions (e.g., AIML operations) under various conditions.
[0069] Examples may be described herein in the context of AIML operations, but those skilled in the art will appreciate that the techniques disclosed in these examples may also be employed to perform other types of operations.
[0070] AIML operations and / or their associated AFs may be served by a network slice (e.g., a single network slice). If the AF is available in multiple locations (e.g., via edge computing), an instance of the AF (e.g., implemented on the EAS) may be suitable for (e.g., more suitable than other AF instances) one or more specific AIML operations and / or one or more specific locations. For example, if an AF instance (e.g., running on the EAS) can provide reduced latency for federated learning operations (e.g., the example of the AIML operation described herein), the WTRU may select the AF instance and move (e.g., redirect) the AIML traffic toward the AF instance (e.g., to a data network or EAS associated with the AF instance). The AF and / or a network device (e.g., a core network device or function) may provide guidance to the WTRU to facilitate the transition to the AF instance. For example, when the WTRU moves into the vicinity of the AF instance (e.g., when the WTRU moves from a first geographic location to a second geographic location, from an area covered by a public network to an area covered by a private network, etc.), the guidance may notify the WTRU of the AF instance. The guidance may convey information about S-NSSAI and / or DNN (e.g., near a particular location) that the WTRU may use to establish a PDU session (e.g., for performing AIML operations). Such guidance may be provided to the WTRU at different times, including, for example, during an initial configuration process (e.g., during WTRU registration), via periodic configuration updates (e.g., in non-access stratum (NAS) and / or radio resource control (RRC) messages), when the WTRU transitions from a current AF to a different AF (e.g., because the AF may no longer support the WTRU's AIML operations), etc.
[0071] URSP mechanisms and / or rules may be implemented to facilitate the operation of a wireless communication network (e.g., AIML operation) (e.g., to direct AIML operation traffic to a specific network slice and / or data network that may provide better support for AIML operation). Guidance may be provided to enable association or mapping of AIML context (e.g., characterized by location, time, DNN, and / or S-NSSA) with traffic characteristics of AIML operation (e.g., as indicated by an application descriptor that may indicate the type of operation, latency requirements, QoS requirements, etc. of the AIML operation). The guidance may be provided to a policy control function (PCF) of the wireless communication network and / or used to set URSP rules. These URSP rules may include information (e.g., filtering information) that may associate a data network (e.g., represented by a DNN), a network slice (e.g., represented by an S-NSSAI), a fully qualified domain name (FQDN), a geographic location, a time of day (e.g., a time when one or more other applications are also running), etc. with certain AIML operations of a WTRU or a WTRU group. For example, the association may limit traffic related to a specific AIML operation of the WTRU to the S-NSSAI, DNN, geographic location, and / or time of day indicated by the URSP rule. This association may serve as a criterion (e.g., a routing criterion) for the WTRU to determine which DNN and / or network slice to use for AIML operations at a location and / or time of day (e.g., if the WTRU moves to a location near a second DNN, the WTRU may switch from performing AIML operations on a first DNN or PDU session to performing AIML operations on a second DNN or PDU session).
[0072] The group of WTRUs for which guidance or USRP rules may be provided may include a group of WTRUs that may be part of a federated learning operation or a distributed AIML operation (such as an image recognition operation). The AIML operations described herein may be associated with corresponding AIML operation types and / or business or service descriptors (e.g., a combination of an operating system ID (OSid), an application ID, and a DNN). Thus, the guidance or USRP rule may indicate an AF service identifier (e.g., using an information element such as AF-Service_Identifier), an AIML operation type, and / or a business or service descriptor associated with the guidance or USRP rule, and the WTRU may determine which specific AIML operations may be subject to the guidance or USRP rule based on the indication. In an example, the AIML operation type may be mapped (e.g., by a PCF or a network exposure function (NEF)) to a business or service descriptor, and one or more combinations of a service descriptor and an AIML operation type may be associated with a set of routing parameters. The PCF may determine the priority of the descriptor (e.g., the order in which the WTRU may apply routing rules) based on the AIML operation associated with a particular service descriptor. The WTRU may use the priority information when applying routing rules.
[0073] Figure 2 An example of modifying an existing PDU session (e.g., an existing PDU session associated with an AIML operation) according to an embodiment of the present disclosure is illustrated. Figure 2 As shown, the WTRU may register with the network (e.g., the core network) at 0a and 0b. At 1 and 2, the AF may generate an AF request (e.g., a service parameter request), wherein the AF may provide guidance for one or more operations (e.g., AIML operations) of the WTRU (or WTRU group). The guidance may include information about one or more operations (e.g., operation type, application or service descriptor, etc.), information about network slices and / or data networks associated with the operations, and / or information about the association of network slices (e.g., represented by S-NSSAI), data networks (e.g., represented by DNN), FQDNs, locations, time of day, etc. with AIML operations or operation types. The guidance may also include service parameters that enable the core network to update policies (e.g., URSP rules) for the WTRU.
[0074] At 3 to 5, a network function such as an NEF may request service authorization for one or more operations of the WTRU (e.g., by sending a Nudm_ServiceSpecificAuthrization_Request to the UDM) (e.g., from a unified data manager (UDM)), and the NEF may receive a response (e.g., a Nudm_ServiceSpecificAuthrization_Response from the UDM) after granting the authorization. For example, at 3, the NEF may transmit a request to the UDM to authorize the guidance provided by the AF (e.g., if the AF has not yet been authorized). In response to such a request, the UDM may verify at 4 that the guidance provided by the AF can be converted into one or more URSP rules in a manner consistent with the WTRU's subscription (e.g., based on the WTRU's subscription information, the DNN and S-NSAAI combination for the AIML operation or operation type is valid). The UDM may perform the verification, for example, by considering the relevant AIML operation, application traffic descriptors, routing parameters (e.g., DNN, S-NSSAI, session and service continuity (SSC) mode, etc.) and spatial validity conditions for the subscriber record of the WTRU.
[0075] If the UDM authorizes the request at 4 (e.g., some requests related to the AIML operation may be accepted, while other requests may be rejected), the UDM may indicate the authorization decision to the NEF at 5, and in response, the NEF may formulate one or more URSP rules related to the AIML operation of the WTRU based on the guidance provided by the AF. Such USRP rules may include, for example, one or more routing descriptors (RSDs) (e.g., a first RSD and a second RSD), which may indicate the corresponding data networks associated with the AIML operation of the WTRU (e.g., the first data network and the second data network). The USRP rules (e.g., the RSDs included in the rules) may also indicate the network slices that the WTRU may use to connect to the data network (e.g., to the first data network and / or the second data network) and / or the criteria that the WTRU may use to make routing selections (e.g., the conditions or triggers for the WTRU to switch from the first data network to the second data network). For example, the criterion may indicate one or more of an expected latency level associated with the WTRU's AIML operation, an expected congestion level associated with the WTRU's AIML operation, an expected QoS level associated with the WTRU's AIML operation, a mapping between locations and data networks, a mapping between AIML operations and data networks, and the like.
[0076] Still refer to Figure 2, service or operation specific information (such as the URSP rules described herein) may be exchanged between a WTRU (or group of WTRUs), one or more network functions or devices, and / or an AF at 6 (e.g., based on the following reference Figure 3 operations described). At 7, the WTRU may determine, based at least on URSP rules received by the WTRU (e.g., which may include information about spatial conditions, such as locations where the URSP rules may be effective) and / or conditions at the WTRU (e.g., the location of the WTRU), that the WTRU's operations may be served (e.g., better served) by a particular AF instance, network slice, and / or data network. For example, the WTRU may have been performing a first set of one or more AIML operations by an existing PDU session (e.g., a first PDU session), which may have been established with a first data network (e.g., associated with a first AF instance and represented by a first DNN) over a particular network slice, and when the WTRU moves to a different location, the WTRU may determine, based on the URSP rules provided by the network and the WTRU's location, that a second data network (e.g., for a second AF instance operating on an EAS close to the WTRU's new location) may satisfy routing criteria indicated by the URSP rules (e.g., the criteria may indicate a mapping between the WTRU's location and the second data network, or a mapping between a second set of AIML operations and the second data network). Based on such a determination, the WTRU may send a PDU session modification request at 8 (e.g., sent to the core network function via an access network such as a base station) to associate an existing PDU session (e.g., a first PDU session) with a second data network (e.g., represented by a second DNN). The WTRU may do this, for example, by indicating in the PDU session modification request that the destination of the existing PDU session is to be changed to a device associated with the second data network (e.g., an edge server). The WTRU may include information about the second data network in the PDU session modification request. For example, the WTRU may indicate a DNN / S-NSSI combination in the PDU session modification request so that the existing PDU session may be modified to use the second DNN and the same network slice used to establish the existing PDU session (e.g., the DNN used for AIML operation may change, but the network slice used for AIML operation may remain unchanged).
[0077] In an example, the WTRU may establish a new PDU session with the second data network at 8 (e.g., instead of modifying an existing PDU session toward the second data network). As described herein, the WTRU may obtain information about the second AF instance, the second data network associated with the second AF instance, and / or the network slice that can be used to connect to the second data network based on URSP rules provided by the network (e.g., delivered by the PCF). As described herein, although the WTRU may switch to a different data network for AIML operation, the WTRU may continue to use the same network slice (e.g., S-NSSAI) for the AIML operation. In an example, the WTRU may maintain an existing PDU session (e.g., currently with a new PDU session).
[0078] In an example, the WTRU may also subscribe to analysis (e.g., mobility analysis) that may be provided by the core network, and may use the analysis received from the network (e.g., in conjunction with URSP rules) to determine which AF instance or data network to use and / or when to switch to that AF instance or data network. The WTRU may make these determinations, for example, based on congestion information that may be derived from slice load analysis and / or user data analysis.
[0079] In any of the scenarios described herein (e.g., modifying an existing PDU session for AIML operations or creating a new PDU session for AIML operations), the WTRU may receive an acknowledgment at 9 of granting or denying a PDU session modification request or a PDU session establishment request sent by the WTRU. For example, a modification of a DNN / S-NSSAI combination indicated by the WTRU may trigger the network to provide a new DNS server address (e.g., if the network decides to grant the modification request), and the WTRU may locate an edge application server (EAS) through the DNS server and connect to the EAS to perform the second set of AIML operations described herein.
[0080] Figure 3 It is illustrated that it can be used, for example, as Figure 2An example of service specific parameter provisioning performed as part of 6 of . As shown in the example, the AF may create an AF request at 1, for example, by involving a Nnef_ServiceParameter_Create service operation, a Nnef_ServiceParameter_Update operation, or a Nnef_ServiceParameter_Delete service operation. At 2, the AF may transmit its request to the NEF. If the NEF authorizes the AF request, the NEF may store the AF request information in a unified data repository (UDR) at 3. In the case of Nnef_ServiceParameter_Delete, the NEF may remove the AF request information from the UDR. At 4, the NEF may respond to the AF with the status of the AF request and / or the transaction ID associated with the AF request. At 5, the PCF may receive a Nudr_DM_Notify notification of the data change from the UDR, and the PCF may initiate policy delivery to the WTRU at 6 at 6.
[0081] Although the above features and elements are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without the other features and elements.
[0082] Although the implementations described herein may consider 3GPP specific protocols, it should be understood that the implementations described herein are not limited to such scenarios and are applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to such scenarios and are also applicable to other wireless systems.
[0083] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (sent via wired and / or wireless connections) and / or 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, but not limited to, built-in hard disks and removable disks), magneto-optical media, and / or optical media (such as compact disk (CD)-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, terminal, base station, RNC, and / or any host computer.
Claims
1. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit (WTRU) comprising: A processor, the processor being configured to: receiving routing policy information from a network device, wherein the routing policy information indicates at least a first data network, a second data network, a network slice for the WTRU to connect to the first data network or the second data network, and criteria associated with routing selection; determining an existing protocol data unit (PDU) session associated with the first data network, wherein the existing PDU is established using the network slice indicated by the routing policy information; determining, based at least on the location of the WTRU and the routing policy information, that the second data network satisfies the criteria associated with routing; as well as A PDU session modification request is sent, wherein the PDU session modification request indicates that the existing PDU session is to be associated with the second data network.
2. A WTRU according to claim 1, wherein the PDU session modification request further indicates that the connection with the second data network will be established using the network slice indicated by the routing policy information.
3. The WTRU of claim 1 or claim 2, wherein the PDU session modification request indicates that a destination of the existing PDU session is to be changed to a device associated with the second data network.
4. The WTRU of any one of claims 1 to 3, wherein: Prior to said sending of said PDU session modification request, said processor is further configured to perform a first artificial intelligence machine learning (AIML) operation via said existing PDU session.
5. The WTRU of any one of claims 1 to 4, wherein: After the sending of the PDU session modification request, the processor is further configured to receive a response indicating that the existing PDU session has been modified and to perform a second AIML operation via the modified PDU session.
6. The WTRU of claim 5, wherein the criteria associated with routing selection indicates a mapping between the second AIML operation and the second data network.
7. The WTRU according to any one of claims 4 to 6, wherein at least one of the first AIML operation or the second AIML operation is associated with federated learning.
8. The WTRU of any one of claims 1 to 7, wherein the criteria associated with routing selection indicates a mapping between the location of the WTRU and the second data network.
9. The WTRU according to any one of claims 1 to 7, wherein the criteria associated with route selection indicates a latency level, a network congestion level, or a quality of service level.
10. The WTRU of any one of claims 1 to 9, wherein the processor is further configured to receive analysis associated with the WTRU from the network device, and further determine that the second data network satisfies the criteria associated with routing selection based on the received analysis.
11. A WTRU according to any one of claims 1 to 10, wherein the routing policy information includes a first routing descriptor (RSD) indicating a data network name (DNN) of the first data network, and the routing policy information further includes a second RSD indicating the DNN of the second data network.
12. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving routing policy information from a network device, wherein the routing policy information indicates at least a first data network, a second data network, a network slice for the WTRU to connect to the first data network or the second data network, and criteria associated with routing selection; determining an existing protocol data unit (PDU) session associated with the first data network, wherein the existing PDU is established using the network slice indicated by the routing policy information; determining, based at least on the location of the WTRU and the routing policy information, that the second data network satisfies the criteria associated with routing; as well as A PDU session modification request is sent, wherein the PDU session modification request indicates that the existing PDU session is to be associated with the second data network.
13. A method according to claim 12, wherein the PDU session modification request further indicates that the connection with the second data network is to be established using the network slice indicated by the routing policy information.
14. A method according to claim 12 or claim 13, wherein the PDU session modification request indicates that a destination of the existing PDU session is to be changed to a device associated with the second data network.
15. The method according to any one of claims 12 to 14, further comprising performing a first artificial intelligence machine learning (AIML) operation via the existing PDU session before sending the PDU session modification request.
16. The method according to any one of claims 12 to 15, further comprising, after sending the PDU session modification request, receiving a response indicating that the existing PDU session has been modified and performing a second AIML operation via the modified PDU session.
17. The method of claim 16, wherein the criteria associated with routing indicates a mapping between the second AIML operation and the second data network.
18. The method of any one of claims 12 to 17, wherein the criteria associated with routing indicates a mapping between the location of the WTRU and the second data network.
19. The method according to any one of claims 12 to 17, wherein the criteria associated with route selection indicates a latency level, a network congestion level or a quality of service level.
20. The method of any one of claims 12 to 19, further comprising receiving an analysis associated with the WTRU from the network device, and determining that the second data network satisfies the criteria associated with routing selection further based on the received analysis.
21. A method according to any one of claims 12 to 20, wherein the routing policy information includes a first routing descriptor (RSD) indicating a data network name (DNN) of the first data network, and the routing policy information further includes a second RSD indicating the DNN of the second data network.
22. A network device, comprising: A processor, the processor being configured to: sending routing policy information to a wireless transmit / receive unit (WTRU), wherein the routing policy information indicates at least a first data network, a second data network, a network slice for the WTRU to connect to the first data network or the second data network, and criteria associated with routing for the WTRU; receiving a protocol data unit (PDU) session modification request from the WTRU, wherein the PDU session modification request is associated with an existing PDU session of the WTRU established with the first data network via the network slice indicated by the routing policy information, and wherein the PDU session modification request includes information about the network slice and an indication that the existing PDU session is to be associated with the second data network; as well as A PDU session modification response is sent to the WTRU, wherein the PDU session modification response indicates whether the PDU session modification request has been granted or denied.
23. The network device of claim 22, wherein the processor is further configured to determine the routing policy information based on guidance received from an application function associated with an artificial intelligence machine learning (AIML) operation of the WTRU.
24. The network device of claim 22 or claim 23, wherein the PDU session modification request indicates that a destination of the existing PDU session of the WTRU is to be changed to a device associated with the second data network.
25. A network device according to any one of claims 22 to 24, wherein the PDU session modification request further indicates that the connection with the second data network will be established using the network slice indicated by the routing policy information.
26. A network device according to any one of claims 22 to 25, wherein the criteria associated with the routing selection of the WTRU indicates a mapping between an artificial intelligence machine learning (AIML) operation of the WTRU and the second data network.
27. A network device according to any one of claims 22 to 26, wherein the standard associated with the routing selection of the WTRU indicates at least one of a mapping between a location and the second data network, a latency level, a network congestion level, or a quality of service level.
