Roaming wireless transmit / receive unit authorization for edge applications

Abstract

Systems, methods, and tools may be described herein for a wireless transmit / receive unit (WTRU) to authorize roaming (e.g., to authorize an EEC (edge enabler client) in roaming a WTRLI through a V-ECS (Access Edge Configuration Server) token that may be generated by an H-ECS (Home Edge Configuration Server). A first message may be transmitted. The first message may indicate a request for an authorization token to be used in accessing the network. A second message may be transmitted. The second message may indicate authentication information. A third message may be transmitted. The third message may indicate an authorization token. The authorization token may be associated with the authentication information. A fourth message may be received. The fourth message may indicate verification of the authorization token and may indicate an identity of the accessed network.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 399,927, filed on August 22, 2022, the contents of which are hereby incorporated by reference into this document. Background Art

[0003] Mobile communications using wireless communications continue to evolve. The fifth generation of mobile communications radio access technology (RAT) may be referred to as 5G New Radio (NR). The previous generation (legacy) mobile communications RAT may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the invention

[0004] Systems, methods, and tools for authorized roaming, such as an edge enabler client (EEC) in an authorized roaming WTRU, may be described herein. A first network node may receive a first message from a wireless transmit receive unit (WTRU), the first message including temporary public land mobile network (T-PLMN) information, a first authorization token, a first edge enabler client (EEC identifier (ID), and a request to verify the first authorization token. The first network node may determine the home public land mobile network (HPLMN) information of the WTRU based on the T-PLMN information. The first network node may determine a second EEC ID based on the first EEC ID. The first network node may determine a second network node based on the HPLMN information and the second EEC ID. The first network node may transmit a second message to the second network node, the second message including the request to verify the first authorization token. The first network node may receive a third message including a verification response from the second network node. The first network node may generate a second authorization token if the verification response indicates that the first authorization token is valid, and the second authorization token may be associated with a visited network edge execution service (V-EES). The first network node may transmit a fourth message to the WTRU, the fourth message including the second authorization token and information about the V-EES information.

[0005] The first network node may include a visitor edge computing service (V-ECS), and wherein the second network node further includes a home network edge computing service (H-ECS). The first network node may verify the second authorization token by determining a digital signature of the first authorization token and / or contacting the second network node.

[0006] The first EEC ID may be different from the second EEC ID. The first EEC ID may obfuscate the identity of the WTRU. The first network node may determine the second EEC ID based on the first EEC ID by determining the identity of the WTRU based on the first EEC ID. The second EEC ID may be associated with the identity of the WTRU. The first network node may determine the second EEC ID by transmitting a request to the second network node to decrypt the second EEC ID. The first network node may determine the second EEC ID by performing decryption and / or reverse hashing.

[0007] The first message may include a universal public subscription identifier (GPSI). The first network node may determine a home network of the WTRU based on the GPSI. The home network of the WTRU may be associated with the second network node. 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 an 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 another example RAN and another example CN for use within the illustrated communication system.

[0012] Figure 2 An example of an architecture (eg, a System Aspect 6 (SA6) architecture) that can be used for one or more edge applications is illustrated.

[0013] Figure 3 An example message flow for authorization between a client hosted in a roaming WTRU (eg, an edge enabler client (EEC)) and a server in a visited network (eg, a visited edge application server (V-ECS)) is illustrated. 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, and 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 eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. Although 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] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSC), radio network controllers (RNC), relay nodes, etc. Base station 114a and / or 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 a licensed spectrum and an unlicensed spectrum. 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, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, 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, and SC-FDMA. 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-A Pro).

[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), and GSM EDGE (GERAN).

[0024] Figure 1A The base station 114b in 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 local areas such as commercial venues, homes, vehicles, campuses, industrial facilities, sky corridors (e.g., for use by drones), and roads. 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 high-level security functions, such as user authentication. Although not described in detail in the text and video, 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 high-level 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, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0026] The CN 106 / 115 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 / 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) and 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 a 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, an IR, UV, or visible light signal. In another embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. 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 Although depicted as a single element in the figure, 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 to enable 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 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, and a secure digital (SD) memory card, among others. 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, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device and activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; geolocation sensor; altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor and / or humidity sensor.

[0037] The WTRU 102 may include a full-duplex radio component for which transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio component 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 component for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (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, and scheduling of users in the UL and / or DL, among other things. 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 being 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.

[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, and selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c. 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 an inter-evolved Node-B handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

[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 a wireless terminal, it is contemplated that in certain representative embodiments, such a terminal may (eg, temporarily or permanently) use a wired communications interface with a communications 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 a BSS and one or more stations (STAs) 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 out of the BSS. Traffic originating from outside the BSS and going to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and going 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. Direct link establishment (DLS) may be utilized to transmit point-to-point traffic between the source STA and the destination STA (e.g., directly between them). 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 operation mode or a similar operation 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 sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0050] High throughput (HT) STAs may communicate using a 40 MHz wide channel (eg, 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 the data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 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 band may be considered busy even if most of the band remains 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 1D1 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, 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).

[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 anchor points. 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 eNodeB 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 eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeB 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.

[0059] 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, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b and 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 in order 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, and / or 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 traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU 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, and 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-d, base station 114a-b, evolved Node B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein. The simulation device may be one or more devices configured to emulate 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 can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0068] This article uses the following acronyms:

[0069] AC Application Client EAS Edge Application Server ECS Edge Configuration Server EDN Edge Data Network EEC Edge Enabler Client EEL Edge Enabler Layer EES Edge Enabler Server H-ECS Home ECS (i.e., ECS in the home network) HPLMN Home PLMN PLMN Public Land Mobile Network V-ECS Visited ECS (that is, the ECS in the visited network) VPLMN PLMNs interviewed UE User Equipment

[0070] Systems, methods, and tools for a wireless transmit / receive unit (WTRU) to authorize roaming (e.g., to authorize an EEC (edge ​​enabler client) in a roaming WTRU via a V-ECS (visit edge configuration server) token that may be generated by an H-ECS (home edge configuration server) may be described herein. A first message may be transmitted. The first message may indicate a request for an authorization token to be used in a visited network. A second message may be transmitted. The second message may indicate authentication information. A third message may be transmitted. The third message may indicate an authorization token. The authorization token may be associated with the authentication information. A fourth message may be received. The fourth message may indicate verification of the authorization token and may indicate the identity of the visited network.

[0071] A roaming authorization (e.g., WTRU authorization) may be provided. In an example, a token that may be generated by the H-ECS may be used by the V-ECS to authorize an EEC that may be in a roaming WTRU. In an example, the V-ECS may verify the token by checking a digital signature of the token, by contacting the H-ECS, a combination thereof, or the like. In an example, after authentication, the V-ECS may generate an authorization token to be used by the EEC towards the V-EES. In an example, the token may be privacy protected to prevent the EEC / WTRU from being tracked by the V-ECS while allowing authorization.

[0072] An application layer may be provided to support edge services. In an example, an application architecture for an application (e.g., an edge application) may include a client (e.g., an edge enabler client) that may be deployed in one or more of a WTRU, an edge configuration service (ECS), an edge enabler service (EES), and / or an edge application server (EAS).

[0073] Figure 2 An example of an architecture (e.g., a System Aspect 6 (SA6) architecture) that can be used for one or more edge applications is illustrated. The SA6 architecture can include an application client (AC), an edge enabler client (EEC), an edge configuration server (ECS), an edge enabler server (EES), and / or an edge application server (EAS).

[0074] An AC may be provided. In the AC, the WTRU may include an application (e.g., a user application). The AC may include an application that may communicate with the EAS. The AC may include a cardinality. In an example, for each WTRU, there may be one or more EECs. In an example, an AC (e.g., one AC) may use an EEC (e.g., one EEC).

[0075] An EEC may be provided. Support (e.g., edge support) may be provided by the EEC to an AC (e.g., an AC on a WTRU). The EEC may include a cardinality. In an example, one or more EECs may be included (e.g., for each WTRU). In an example, an AC (e.g., an AC) may use an EEC (e.g., an EEC).

[0076] An ECS may be provided. An ECS may provide support functions for an EEC and / or an EES. For example, an EEC and / or an EES may use support functions to discover an EES. An ESS may provide one or more EASs. An ECS may include a base. For example, a network may include one or more ECSs.

[0077] An EES may be provided. The EES may provide support functions for the EAS and / or EEC. The EES may include a cardinality. In an example, for each edge data network (EDN) that may be a DNN, one or more EESs may be included. In an example, multiple EDNs may be included in the network.

[0078] An EAS may be provided. An application server may reside in the EDN and may be included in the EAS. For example, the EAS may be a software server that may provide services to application clients. The EAS may include a cardinality. For example, for each EDN, one or more EASs (e.g., multiple EASs) may be included. An EDN (e.g., each EDN) may include a set of EASs (e.g., a different set of EASs). One or more EASs may serve a group of AC / WTRUs. In an example, one or more EASs may be dedicated to an AC / WTRU (e.g., a single AC / WTRU).

[0079] The terms "roaming network", "visited network" and "visited public land mobile network (VPLMN)" may be used interchangeably herein. The terms "home network" and "home public land mobile network (HPLMN)" may be used interchangeably herein.

[0080] In order to use edge applications (e.g., in edge infrastructure in a visited network), a roaming WTRU may request authentication and authorization (e.g., by an H-ECS) before the WTRU is configured and provisioned. For example, the WTRU may be authenticated and authorized before the WTRU contacts a visited edge enabler server (V-EES) and / or a visited edge application server (V-EAS).

[0081] In an example, the EEC in the WTRU may be in the home network. Authentication may occur between the EEC and the H-ECS. In an example, a transport layer security (TLS) authentication method may be used. When the authentication is a successful authentication, the EEC may be authorized by the H-ECS. For example, the H-ECS may use a local authorization policy to authorize the EEC.

[0082] In an example, configuration information may be used to determine (e.g., by the H-ECS after successful authentication and authorization) whether an access token may be requested for a candidate EES. A separate EES access token may be issued (e.g., by the H-ECS) for a candidate EES (e.g., a candidate EES using token-based authorization). The EES service token may include one or more of an ECS fully qualified domain name (ECSFQDN) (e.g., issuer), an EEC ID (e.g., principal), an expected EES service name (e.g., scope), an EES FQDN (e.g., audience), and / or an expiration time (e.g., a time at which the token may expire and / or a duration after which the token may expire). A service provisioning response may be transmitted (e.g., returned from the ECS to the EEC) that may include the EES access token.

[0083] As described herein, a mechanism may be provided for authorizing an EEC in a roaming WTRU by an ECS in a visited network (e.g., a V-ECS). Features described herein may include means for authorizing an EEC in a roaming WTRU by an ECS (e.g., an ECS associated with a visited network).

[0084] In an example, an attempt may be made by the WTRU to use an EDGE application associated with a visited network (e.g., the WTRU is roaming to a visited network). For example, the EEC in the WTRU may contact the H-ECS to obtain an authorization token to be used in the visited network. In an example, when the WTRU may be roaming to a visited network, the EEC may contact the H-ECS and may attempt to use an EDGE application associated with the visited network.

[0085] The V-ECS may be contacted with the authentication information (e.g., by an EEC in a roaming WTRU). An authorization token may be presented (e.g., by the EEC to the V-ECS). For example, the EEC in a roaming WTRU may contact the V-ECS with the authentication information and may present the authorization token to the V-ECS.

[0086] The token may be verified (e.g., by the V-ECS) by checking a digital signature (e.g., a digital signature of the token). The token may be verified by contacting the H-ECS or an authentication, authorization, and accounting server (AAA server) in the home network. The token may be verified by calling an API that may be provided by the home network.

[0087] An authorization token may be generated (eg, by the V-ECS after authentication and authorization) for use by the EEC towards the V-EES. The authorization token and the V-EES identity may be provided to the EEC (eg, in a service provisioning response).

[0088] The authorization token may be privacy protected. For example, the authorization token may be privacy protected to prevent the EEC / WTRU from being tracked by the V-ECS while allowing authorization.

[0089] Figure 3 An example message flow for authorization between a client hosted in a roaming WTRU (eg, an edge enabler client (EEC)) and a server in a visited network (eg, a visited edge application server (V-ECS)) is illustrated.

[0090] At 1, a WTRU may be registered in a home network. The WTRU may register to obtain an authorization token to be used with edge applications in a roaming network. The ECS service authorization token may include one or more of a home ECS FQDN (e.g., issuer), an EEC ID and GPSI (e.g., subject), an expected ECS service name (e.g., scope), an access ECS FQDN (e.g., audience), an expiration time (e.g., a time when the token may expire, or a duration after which the token may expire), or a digital signature (e.g., a digital signature generated by the home ECS). The authorization token may include an endpoint address (e.g., an endpoint address that can be used by the V-ECS to verify the token). The V-ECS (e.g., a first network node) may be provisioned with an endpoint address that may be valid for an operator (e.g., each operator). The authorization token may include an identifier. The identifier may be an identifier that the V-ECS can use to determine which provisioned endpoint address can be used to verify the EEC's token.

[0091] In an example, when a WTRU may be registered in a roaming network, the process shown at 1 may be performed. When a WTRU may be registered in a roaming network, an H-ECS (e.g., a second network node) may be contacted (e.g., contacted by the WTRU). A service provisioning request may be transmitted (e.g., by the WTRU) to the H-ECS. The VPLMN may be indicated (e.g., by the EEC) that it may be registered (e.g., registered into) the EEC, and the H-ECS may provide a T-HPLMN identifier (e.g., a temporary HPLMN identifier) ​​to the EEC. The T-HPLMN ID may include an identifier that may be pre-arranged between the HPLMN and the VPLMN (e.g., to temporarily identify the HPLMN).

[0092] In an example, the authorization token may be configured to enable authorization while preventing the V-ECS from tracking the EEC / WTRU. Tracking may be prevented by utilizing an EEC ID pseudonym instead of an EEC ID while ensuring that the EEC ID pseudonym may not be reused. The EEC ID may be confidentiality protected (e.g., encrypted and / or hashed with a one-time use freshness parameter).

[0093] At 2, the WTRU may access a roaming network (e.g., register in the roaming network). A service deployment request may be transmitted (e.g., by an EEC in the roaming WTRU) to an ECS in the visited network. The service deployment request may include an authorization token (e.g., a first authorization token), an EEC ID, an EEC ID pseudonym, a combination thereof, etc. The service deployment request may include a T-HPLMN ID. The service deployment request may include a request to verify the authorization token.

[0094] At 3, information about the WTRU's home network may be extracted (e.g., by the V-ECS upon receiving a provisioning request) based on the GPSI in the authorization token. In the case where the WTRU is roaming, the authorization token may be verified (e.g., by the ECS) by comparing the home network identifier with a PLMN identifier (e.g., a PLMN identifier associated with the ECS). A non-roaming authentication and authorization mechanism between the EEC and the ECS may be employed (e.g., in the case where the WTRU is not roaming). The T-HPLMN ID may include a service provisioning request. The T-HPLMN ID may be used to determine the HPLMN ID (e.g., the HPLMN information may be determined based on the T-PLMN information. Determining the HPLMN ID (e.g., using the T-HPLMN ID) may avoid transmitting (e.g., via the EEC) a domain identifier (e.g., transmitting the HPLMN ID to the ECS in an unencrypted manner).

[0095] At 4 (e.g., in a WTRU roaming scenario), the token may be verified (e.g., by the V-ECS) by checking one or more of a digital signature (e.g., of the token) or transmitting the token (e.g., to the home ECS). Information from the authorization token may be used (e.g., by the V-ECS) to determine an entity to contact (e.g., an entity to contact in the home network). For example, the token may include an endpoint address (e.g., an endpoint address of the H-ECS that the V-ECS may contact).

[0096] like Figure 3 As shown, the H-ECS may be contacted (e.g., by the V-ECS) to perform authorization (e.g., to verify an authorization token). An entity (e.g., a different entity (e.g., function)) may be contacted to perform authorization. In an example, an AAA server or a network open function (NEF) may be contacted. As described at 1, an endpoint address that may be valid for an operator (e.g., each operator) may be provisioned (e.g., provisioned within the ECS).

[0097] At 4, the authorization token may include an identifier. The identifier may be an identifier that the V-ECS can use to determine that the deployed endpoint address can be used to verify the token of the EEC. The examples described herein may provide EEC / WTRU privacy, and the EEC / WTRU privacy may be protected. For example, the EEC ID may be recovered (e.g., recovered / decrypted by the H-ECS) from a pseudonym, an encrypted value, and / or a hashed value (e.g., recovered before the verification token). In an example, the first EEC ID may include a pseudonym, an encrypted value, and / or a hashed value (e.g., recovered before the verification token). In an example, the second EEC ID may be decrypted based on the first EEC ID. In an example, the second EEC ID may be determined by performing a reverse hash operation based on the first EEC ID. The first EEC ID may be distinguished from the second EEC ID. The first EEC ID may confuse the identity of the WTRU, and the identity may be determined based on the first EEC ID. The second EEC ID may include the identity of the WTRU (e.g., may be associated with the identity).

[0098] At 5, the H-ECS may transmit a confirmation message. For example, in the event that the token verification is successful (eg, verification response), the H-ECS may transmit a confirmation message back to the V-ECS.

[0099] At 6, a configuration request (eg, a configuration request from an EEC in a roaming WTRU) may be processed (eg, processing may begin) by the V-ECS. A token validation confirmation may be received (eg, received by the V-ECS from the H-ECS).

[0100] At 7, a token (e.g., a second authorization token) may be generated. For example, one or more tokens may be generated by the V-ECS for use with the V-EES of the EEC. The token may be transmitted to the WTRU (e.g., over a secure TLS connection). The EEC and GPSI of the WTRU may be (e.g., successfully) authenticated (e.g., by the ECS). The EES service token may include an ECS FQDN (e.g., issuer), an EEC ID, a GPSI (e.g., subject), an expected EES service name (e.g., scope), an EES FQDN (e.g., audience), an expiration time (e.g., a time at which expiration may occur, and / or a duration before which expiration may occur), a digital signature (e.g., a digital signature generated by the V-ECS), combinations thereof, and the like.

[0101] Systems, methods, and tools for authorized roaming, such as an edge enabler client (EEC) in an authorized roaming WTRU, may be described herein. A first network node may receive a first message from a wireless transmit receive unit (WTRU), the first message including temporary public land mobile network (T-PLMN) information, a first authorization token, a first edge enabler client (EEC identifier (ID), and a request to verify the first authorization token. The first network node may determine the home public land mobile network (HPLMN) information of the WTRU based on the T-PLMN information. The first network node may determine a second EEC ID based on the first EEC ID. The first network node may determine a second network node based on the HPLMN information and the second EEC ID. The first network node may transmit a second message to the second network node, the second message including the request to verify the first authorization token. The first network node may receive a third message including a verification response from the second network node. The first network node may generate a second authorization token if the verification response indicates that the first authorization token is valid, and the second authorization token may be associated with a visited network edge execution service (V-EES). The first network node may transmit a fourth message to the WTRU, the fourth message including the second authorization token and information about the V-EES information.

[0102] The first network node may include a visitor edge computing service (V-ECS), and wherein the second network node further includes a home network edge computing service (H-ECS). The first network node may verify the second authorization token by determining a digital signature of the first authorization token and / or contacting the second network node.

[0103] The first EEC ID may be different from the second EEC ID. The first EEC ID may obfuscate the identity of the WTRU. The first network node may determine the second EEC ID based on the first EEC ID by determining the identity of the WTRU based on the first EEC ID. The second EEC ID may be associated with the identity of the WTRU. The first network node may determine the second EEC ID by transmitting a request to the second network node to decrypt the second EEC ID. The first network node may determine the second EEC ID by performing decryption and / or reverse hashing.

[0104] The first message may include a Universal Public Subscription Identifier (GPSI). The first network node may determine the home network of the WTRU based on the GPSI. The home network of the WTRU may be associated with the second network node.

[0105] Although the features and elements described above 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.

[0106] Although the implementation described herein may consider 3GPP specific protocols, it should be understood that the implementation described herein is not limited to such scenarios and may be applicable to other wireless systems. For example, although the solution described herein considers LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solution described herein is not limited to such scenarios and may be applicable to other wireless systems.

[0107] 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 first network node, the first network node comprising: A processor, the processor being configured to: receiving a first message from a wireless transmit receive unit (WTRU), the first message including temporary public land mobile network (T-PLMN) information, a first authorization token, a first edge enabler client (EEC identifier (ID), and a request to verify the first authorization token; determining a home public land mobile network (HPLMN) information of the WTRU based on the T-PLMN information; determining a second EEC ID based on the first EEC ID; determining a second network node based on the HPLMN information and the second EEC ID; transmitting a second message to the second network node, the second message comprising a request to verify the first authorization token; receiving, from the second network node, a third message comprising a verification response; generating a second authorization token if the validation response indicates that the first authorization token is valid, wherein the second authorization token is associated with a visited network edge execution service (V-EES); as well as A fourth message is transmitted to the WTRU, the fourth message including the second authorization token and information regarding the V-EES information.

2. The first network node of claim 1, wherein the first network node further comprises a visitor edge computing service (V-ECS), and wherein the second network node further comprises a home network edge computing service (H-ECS).

3. The first network node of claim 1, wherein the processor is further configured to verify the second authorization token by performing at least one of determining a digital signature of the first authorization token or contacting the second network node. The first network node of claim 1 , wherein the first EEC ID is different from the second EEC ID.

5. The first network node of claim 1 , wherein the first EEC ID obscures the identity of the WTRU, and wherein the processor is configured to determine the second EEC ID based on the first EECID comprises the processor being configured to: The identity of the WTRU is determined based on the first EEC ID, wherein the second EEC ID is associated with the identity of the WTRU. 6 . The first network node of claim 5 , wherein the processor is further configured to determine the second EEC ID by transmitting a request to decrypt the second EEC ID to the second network node.

7. The first network node of claim 5, wherein the processor is further configured to determine the second EEC ID by performing any one of decryption or reverse hashing.

8. The first network node of claim 1 , wherein the first message further comprises a General Public Subscription Identifier (GPSI), and wherein the processor is further configured to: A home network of the WTRU is determined based on the GPSI, and wherein the home network of the WTRU is associated with the second network node.

9. A method for a first network node, wherein the method comprises: receiving a first message from a wireless transmit receive unit (WTRU), the first message including temporary public land mobile network (T-PLMN) information, a first authorization token, a first edge enabler client (EEC identifier (ID), and a request to verify the first authorization token; determining a home public land mobile network (HPLMN) information of the WTRU based on the T-PLMN information; determining a second EEC ID based on the first EEC ID; determining a second network node based on the HPLMN information and the second EEC ID; transmitting a second message to the second network node, the second message comprising a request to verify the first authorization token; receiving, from the second network node, a third message comprising a verification response; generating a second authorization token if the validation response indicates that the first authorization token is valid, wherein the second authorization token is associated with a visited network edge execution service (V-EES); as well as A fourth message is transmitted to the WTRU, the fourth message including the second authorization token and information regarding the V-EES information.

10. The method of claim 9, wherein the first network node further comprises a visitor edge computing service (V-ECS), and wherein the second network node further comprises a home network edge computing service (H-ECS).

11. The method according to claim 9, wherein the method further comprises: The second authorization token is verified by performing at least one of determining a digital signature of the first authorization token or contacting the second network node.

12. The method of claim 9, wherein the first EEC ID is different from the second EEC ID.

13. The method of claim 9, wherein the first EEC ID obfuscates the identity of the WTRU, and wherein determining the second EEC ID based on the first EEC ID comprises determining the identity of the WTRU based on the first EEC ID, and wherein the second EEC ID is associated with the identity of the WTRU.

14. The method of claim 13, wherein the method further comprises determining the second EECID by transmitting a request to the second network node to decrypt the second EECID.

15. The method of claim 13, wherein the method further comprises determining the second EEC ID by performing any of decryption or reverse hashing.

16. The method of claim 9, wherein the first message further includes a General Public Subscription Identifier (GPSI), and wherein the method further includes: A home network of the WTRU is determined based on the GPSI, and wherein the home network of the WTRU is associated with the second network node.

Images