WO2021092441A1 - Address change notification associated with edge computing networks - Google Patents

Address change notification associated with edge computing networks Download PDF

Info

Publication number
WO2021092441A1
WO2021092441A1 PCT/US2020/059484 US2020059484W WO2021092441A1 WO 2021092441 A1 WO2021092441 A1 WO 2021092441A1 US 2020059484 W US2020059484 W US 2020059484W WO 2021092441 A1 WO2021092441 A1 WO 2021092441A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
wtru
network
registration
application server
Prior art date
Application number
PCT/US2020/059484
Other languages
French (fr)
Inventor
Ulises Olvera-Hernandez
Robert Gazda
Michelle Perras
Debashish Purkayastha
Saad Ahmad
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2021092441A1 publication Critical patent/WO2021092441A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5076—Update or notification mechanisms, e.g. DynDNS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • An apparatus associated with a network may receive a notification for a change of a first address for an application server (e.g., an edge application server (EAS)).
  • the application server may be located outside the network.
  • the apparatus may obtain a second address of the application server based on a procedure for configuring a parameter associated with the network.
  • the configured parameter associated with the network may indicate the change of the first address.
  • the apparatus may send the second address.
  • the second address may be forwarded to a wireless transmit/receive unit (WTRU), for example, by the apparatus or by another apparatus.
  • WTRU wireless transmit/receive unit
  • the apparatus may include a policy control function (PCF) or a session management function (SMF).
  • PCF policy control function
  • SMF session management function
  • the apparatus may subscribe to the notification for the change of the first address of the application server, and the notification may be received based on the subscription.
  • the apparatus may obtain an application identifier (ID) associated with the second address and a data network access ID, based on the procedure for configuring the parameter associated with the network.
  • ID application identifier
  • the apparatus may receive a request for a first registration from the WTRU and determine that a configuration update for the WTRU is to occur without a second registration based on at least one of: a characteristic of an application associated with the application server or a context associated with the WTRU.
  • the second address may be forwarded to the WTRU without the second registration.
  • the apparatus may receive a request for a first registration from the WTRU and determine that a configuration update for the WTRU is to occur via a second registration based on at least one of: a characteristic of an application associated with the application server or a context associated with the WTRU.
  • the apparatus may receive a request for the second registration that is subsequent to the first registration.
  • the second address may be forwarded to the WTRU via the second registration.
  • the notification for the change of the first address may be associated with an application migration or an address re-location.
  • the first address and/or the second address may be an end-point address.
  • the procedure may include a service parameter provisioning procedure.
  • a wireless transmit/receive unit (WTRU) configured to communicate with a network may obtain a first address of an application server (e.g., an EAS).
  • the WTRU may receive a second address of the application server and an application ID associated with the second address.
  • the WTRU may determine an application associated with the second address based on the application ID.
  • the WTRU may perform an update of the first address of the application server based on the second address and the application associated with the second address.
  • the WTRU may request the second address of the application server during an establishment of a package data unit (PDU) session.
  • the WTRU may receive a timer for triggering a mobility registration to the network.
  • the WTRU may send a request for a first registration to the network and receive the second address without a second registration.
  • the WTRU may send a request for a first registration to the network, send a request for the second registration to the network, and receive the second address via the second registration.
  • FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;
  • FIG.1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG.1A according to an embodiment;
  • FIG.1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG.1A according to an embodiment;
  • FIG.1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG.1A according to an embodiment;
  • FIG.2 illustrates an example of an edge computing reference model in 5GS;
  • FIG.3 illustrates an example of application function influence on user traffic;
  • FIG.4 illustrates an example of an application layer architecture (e.g., a SA)
  • FIG.1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), 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 multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • a netbook a personal computer
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the other networks 112.
  • 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, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • NR New Radio
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA20001X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG.1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG.1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG.1B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • a base station e.g., the base station 114a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the transmit/receive element 122 is depicted in FIG.1B 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.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), 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.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • an accelerometer an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity track
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the 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 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG.1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-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 the UL and/or DL, and the like.
  • the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG.1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the 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 user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • 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.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS.1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • DS Distribution System
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA e.g., only one station
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • 802.11af and 802.11ah The 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 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 802.11ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • FIG.1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG.1D may include at least one AMF 182a, 182b, at least one UPF 184a,184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0068]
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • 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.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet- based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, 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, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment.
  • An edge computing network(s) may use a local access (e.g., the concept of a local access) to a data network.
  • FIG.2 illustrates an example of an edge computing reference model in 5GS.
  • an edge application server EAS
  • EAS edge application server
  • AN may stand for access network in FIG.2.
  • the EAS may be within a data network (DN) located at the edge, for example, on a user plane.
  • a detection rule(s) may be used to identify traffic that is to be (e.g., needs to be) routed selectively.
  • User traffic (e.g., user traffic supporting specific applications) may be treated differently under different conditions including one or more of a geographical location, a time of day, or traffic content. Conditions may vary, for example, over time.
  • Treatment of user data traffic may include (e.g., require) dynamic handling of policies and/or rules, for example, depending on a characteristic of the application (e.g., the need of the application). The characteristic of the application may be determined by an Application Function (AF). User traffic may be handled dynamically.
  • AF Application Function
  • Data network access identifiers may relate to edge computing.
  • Edge computing support may be provided.
  • a network system e.g., 5G system (5GS)
  • 5GS 5G system
  • a network system may be able to route user traffic to a local data network, for example, by using traffic filters (e.g., in the form of routing profiles and/or traffic routing information associated to an access to a specific data network location).
  • FIG.3 illustrates an example of application function influence on user traffic.
  • the data network location may be identified by a Data Network Access Identifier (DNAI) (e.g., DNAI-1, DNAI-2, or DNAI-3, as shown in FIG.3).
  • DNAI identifying data network locations may be illustrated in FIG.3.
  • An application function may request an action through (e.g., directly through) a policy control function (PCF) or a network exposure function (NEF).
  • PCF policy control function
  • NEF network exposure function
  • SMF and UPF may be located in (e.g., within a scope of) a first network (e.g., 3GPP network).
  • EAS may be located in a second network (e.g., an edge data network) and outside the first network, for example, on the user plane.
  • an AF may be connected to the network.
  • An AF may send a request(s) to 5G core (5GC) (e.g., a PCF or a NEF), for example, to influence one or more SMF routing decisions for user plane (UP) traffic.
  • the UP traffic may be for a PDU sessions(s) destined to a data Network(s) that supports a specific application.
  • the AF may use a service based application programming interface (API) to access the PCF (e.g., if the AF has a trusted relationship with the Network Operator).
  • API application programming interface
  • the AF may send the request using the NEF (e.g., if the AF does not have a trusted relationship with the Network Operator).
  • the PCF may determine if a current PDU sessions(s) is potentially impacted by the request that the AF sent.
  • the PCF may use the application traffic and one or more of the following information (e.g., one or more of the following information related to the subscriber session) as input for selecting a traffic steering policy: network operator's policies, a user subscription, the user's current radio access technology (RAT), a network load status, an application identifier, a time of day, a WTRU location, and/or a data network name (DNN).
  • RAT current radio access technology
  • the PCF may update the SMF based on a corresponding updated (e.g., new) policy and charging control (PCC) rule(s), for example, by invoking a SM policy control service operation as illustrated in FIG.3.
  • PCC policy and charging control
  • the PCF may update one or more policies (e.g., the relevant policies) in the SMF that apply to one or more of the following: a particular PDU session, a WTRU, or a collection of WTRUs.
  • a request that is sent by a third-party provider may influence the UPF selection (e.g., reselection) and/or allow routing of user traffic to a local access identified by a DNAI, for example, as described herein.
  • the request (e.g., the request sent by the AF) may include traffic filters that may be installed in the selected UPF (e.g., the UPF handling the PDU session, for example, the UPF shown in FIG.3).
  • the selected UPF may act upon the traffic filters installed in the UPF, for example, by routing user traffic to the DNAI associated with one or more of the following: a DNN, subscribed network slice selection assistance information (S-NSSAI), and/or a PDU session.
  • FIG.3 illustrates that the DNAI may represent the access to a second network (e.g., a data network) where applications relevant to the traffic being routed are located.
  • the UPF may mark packets (e.g., to indicate a certain type of traffic to the data network (DN) side of the N6 reference point). UPF packet marking may enable those packets to be steered in the DN.
  • the UPF may forward (e.g., offload) traffic identified by a traffic descriptor to a local tunnel.
  • An application layer solution may be used to enhance edge computing services, for example, edge application server discovery.
  • Application layer mechanism(s) may be used to enhance edge computing services.
  • An application layer approach may enhance edge computing services (e.g., one or more of edge application server discovery, edge application server selection, and/or edge application server reselection).
  • FIG.4 illustrates an application layer architecture supporting edge computing services.
  • FIG.4 shows a first network (e.g., a 3GPP network) and a second network (e.g., an edge data network).
  • One or more of the edge application servers may be in (e.g., located in) the second network.
  • the one or more of the edge application servers may be outside (e.g., located outside) the first network, for example, on a user plane.
  • the WTRU may be associated with one or more application clients.
  • FIG.4 shows that “Application Data Traffic”, “EDGE 1” reference point, and “EDGE 4” reference point may be carried as user plane traffic (e.g., carried over a PDU session(s) supported through a UPF).
  • one or more components of the EAS may act as an AF connected to the first network, for example, via the EDGE-7 interface.
  • EDGE 2 may be an API for retrieval of network capability information and/or may be a control plane interface (e.g., EDGE 2 may use a service based operation(s) using relevant APIs).
  • EASs may be discovered.
  • An application client in a WTRU may use operating system (OS) services to determine an IP Address based on a fully qualified domain name (FQDN) (e.g., resolve a FQDN into an IP Address).
  • OS operating system
  • FQDN fully qualified domain name
  • a name-based approach may be used, for example, to reach the EAS supporting a certain application.
  • the WTRU may resolve (e.g., be required to resolve) the FQDN to reach the EAS supporting a particular application, for example, if a name-based approach is not used.
  • the client may not have a configured FQDN to reach the local EAS.
  • domain name server DNS
  • the issues may include a cache that is not supported, time to live (TTL) zero that is not supported, and/or the like).
  • TTL time to live
  • Constantly re-configuring the DNS servers or invalidating cache may introduce delays that are in contradiction to the low latency nature of the edge, as the gains provided by the close proximity that the edge provides, are offset by the delays introduced by the DNS resolution.
  • the application server (AS) address that was obtained by the application client may no longer be valid, for example, after an address resolution has taken place (e.g., if the application running at the server side has been relocated and/or if the application instance has crashed).
  • the AS address may not meet performance requirements of the application client (e.g., the AS address may be valid but not meet performance requirements).
  • the AS server may be located far from the application client, for example, to an extent where an application relocation may be warranted.
  • a WTRU may determine a suitable AS address. Mechanisms may enable the WTRU to determine a suitable AS address, for example, in cases where the WTRU does not have a configured FQDN and/or the WTRU has a stale AS address.
  • the suitable AS address may include, for example, an AS address that causes the AS to satisfy (e.g., leading to AS capable of satisfying) the needs of applications running in the WTRU. These mechanisms may not require application layer solutions (e.g., the solutions may or may not always apply).
  • Service continuity may be maintained upon an application relocation (e.g., at the AS), a PDU session anchor (PSA) change or both. Service continuity may be affected, and/or the user’s experience (e.g., QoE or QoS) may be impacted.
  • Service continuity may be affected (and/or the user’s experience may be impacted) when an application running in an EAS is relocated (e.g., due to one or more of the following: an EAS crash, a load balancing, a server maintenance, a performance change, WTRU mobility warranting an EAS change, and/or the migration towards aa different EAS causing a different application address assignment).
  • Service continuity may be affected (and/or the user’s experience may be impacted) if the PSA changes due to WTRU mobility.
  • the change of AS address and/or client address at the WTRU may cause a packet loss and end-point addresses to be re- synchronized.
  • Mechanisms may be used to preserve service continuity when an application running in EAS relocates, the PSA changes, or both occur. Service continuity, session continuity, or both may be used (e.g., required based on the needs of the application).
  • An address e.g., an end-point address
  • An EAS may be indicated in a registration request, for example, by a WTRU.
  • a WTRU may obtain (e.g., read) system information, for example, upon or after powering on, and, the WTRU may determine one or more of the following: tracking area code(s) (TACs), public land mobile network ID(s) (PLMN IDs), network identifier(s) (NIDs), and/or closed access group (CAG) identifier(s).
  • TACs tracking area code(s)
  • PLMN IDs public land mobile network ID(s)
  • NIDs network identifier(s)
  • CAG closed access group
  • An application ID may map to a NID/PLMN pair and/or map to a TAC.
  • a WTRU may be configured with a mapping of application IDs to NID/PLMN pairs or TACs (e.g., representing a location).
  • the WTRU may select a NID/PLMN pair (e.g., a combination of NID and PLMN) and/or a TAC to satisfy its application needs (based on the application ID), for example, when the WTRU reads the system information (e.g., SIB).
  • a NID/PLMN pair e.g., a combination of NID and PLMN
  • a TAC to satisfy its application needs (based on the application ID)
  • SIB system information
  • the WTRU may use one or more of the following: a reserved NID, a reserved CAG ID, a reserved application name, or a reserved application ID, if the WTRU is not configured with an FQDN or AS end-point address, to indicate (e.g., signal) the network that an EAS end-point address is to be provided to the WTRU, for example, when the WTRU does not have the EAS end-point address or is to renew the EAS end-point address (e.g., an old EAS end-point address).
  • a WTRU may include one or more of a reserved NID, a reserved CGS ID, a reserved application name or a reserved application ID in a registration request to indicate to the network to which network/CGS/application a change of address applies.
  • the network e.g., the AMF, UDM, PCF or SMF
  • the WTRU may use a reserved S-NSSAI, DNN, 5G virtual network (VN) group ID, application name or application ID, and/or a value (e.g., a value for an information element (IE) associated with the indicating the EAS end-point address) to indicate the network that an EAS end-point address is to be provided to the WTRU.
  • a value e.g., a value for an information element (IE) associated with the indicating the EAS end-point address
  • IE information element
  • one or more FQDNs/URIs may be provided to the WTRU, for example, if the client wants to contact multiple application addresses through different FQDNs/URIs.
  • An IE which may be a separate IE (e.g., “EAS End-Point-address-required”), may be included in the registration request, for example, for a first registration (e.g., an initial registration) and/or a second registration (e.g., a mobility registrations), for example, if the WTRU has a PDU session(s) to be activated.
  • the WTRU may include (e.g., explicitly include) a FQDN, a uniform resource identifier (URI), and/or a list of URIs or FQDNs of the AS end-point address(es) that the WTRU wants to reach.
  • URI uniform resource identifier
  • An address (e.g., an end-point address) of an EAS may be handled (e.g., stored) at the unified data management (UDM) and/or PCF.
  • a function associated with the network e.g., the AMF
  • may request another function associated with the network e.g., the PCF
  • to include the address of an EAS or a list of addresses associated with the EAS, for example, during registration (e.g., during a registration procedure).
  • the address of the EAS or the list of the address may be associated with a combination of one or more of a DNN, a S-NSSAI, or a NID or may be associated with a certain (e.g., specified) FQDN or a uniform resource identifier (URI).
  • the address of the EAS or the list of the addresses may be associated with a list (e.g., a container) including: a combination of one or more of a DNN, a S-NSSAI, or a NID; a certain FQDN; and a URI.
  • a parameter associated with the network may include one or more of: a DNN, a S-NSSAI, a NID, a FQDN, or a URI.
  • the address of the EAS may be stored at the PCF or at the UDM.
  • a function associated with the network e.g., an AMF
  • may determine whether an address resolution service e.g., the end-point address resolution service
  • an application requirement for example, whether an application requirement warrants the end-point address resolution service.
  • Another function associated with the network e.g., a PCF
  • the determination of whether an application requirement warrants a support of an address resolution service by the 5GS may be performed at the PCF based on operator policies or policies (e.g., policies pushed from the AF for certain applications or application set(s)) and/or based on a certain WTRU context, (e.g., one or more of a time of the day, a geographical proximity to the EAS, a topographical proximity to the EAS, a subscriber category, a computing capability, a storage capability, security requirements, and/or load balancing).
  • operator policies or policies e.g., policies pushed from the AF for certain applications or application set(s)
  • a certain WTRU context e.g., one or more of a time of the day, a geographical proximity to the EAS, a topographical proximity to the EAS, a subscriber category, a computing capability, a storage capability, security requirements, and/or load balancing.
  • One or more of a computing capability, a storage capability, security requirements, load balancing requirements, and/or the like, for EAS may be considered, for example, by the PCF to determine whether an application requirement warrants a support of an address resolution service by the 5GS. This may avoid unnecessary signaling. If an address (e.g., an end-point address) resolution is not to be performed (e.g., not permitted), the function associated with the network may indicate to the WTRU (e.g., via the registration accept message or using a new IE) that an address resolution for the EAS is to take place by other approaches (e.g., a regular DNS resolution or an application layer-based resolution).
  • An address (e.g., an end-point address) of an EAS may be handled at a network repository function (NRF).
  • An AF e.g., an AF associated with an EAS
  • An AF may publish an address of an EAS (e.g., the AF EAS end-point address), for example, based on (e.g., directly using) the NRF API or through the NEF.
  • a function associated with the network e.g., an AMF may use the NRF to resolve the address(es) of the EAS, for example, when the WTRU requests the 5GC to determine the address(s) for EAS(s) associated with certain applications.
  • the function associated with the network may use techniques described herein (e.g., techniques associated with EAS end-point address being handled at the UDM and/or PCF) to determine whether the address resolution (e.g., an EAS end-point resolution) is to be performed or not.
  • a function associated with the network e.g., an AMF
  • FIG.5 illustrates an example of EAS end-point address resolution during registration.
  • an AMF may receive a request for a registration (e.g., registration request) from a WTRU.
  • the registration request may include one or more of the following: a S-NSSAI, a DNN, a 5G VN group ID, an application name, an application ID, a FQDR, or a URI.
  • the AMF may send an address resolution request (e.g., an EAS end-point resolution request) to a UDM or a PCF.
  • an AF associated with an EAS may notify the NEF an address of the EAS or a change of the address, and the NEF may send the address of the EAS or the change of the address to the UDM or PCF via a procedure for configuring a parameter associated with the network (e.g., AF(EAS) Nnef parameter provision).
  • a procedure for configuring a parameter associated with the network e.g., AF(EAS) Nnef parameter provision.
  • one or more components of the EAS may act as an AF (e.g., AF(EAS)).
  • the AF may be connected to a network (e.g., part of a network).
  • the AF associated with an EAS may send the address of the EAS or the change of the address to the UDM or PCF via the procedure for configuring a parameter associated with the network (e.g., AF(EAS) Nnef parameter provision).
  • the UDM or the PCF may send an address resolution response (e.g., including the address of the EAS or the change of the address) to the AMF.
  • the AMF may send an address resolution request (e.g., an EAS end-point resolution request) to a NRF.
  • the AF associated with an EAS may publish the address of the EAS or the change of the address to a NRF (e.g., via AF(EAS) Publish End-point address).
  • the NRF may send an address resolution response (e.g., including the address of the EAS or the change of the address) to the AMF.
  • the function associated with the network e.g., the AMF
  • the AMF may determine whether an address resolution (e.g., an EAS end-point resolution) is warranted, for example, based on a WTRU context and/or policies.
  • the AMF may send a acceptance for the registration (e.g., registration accept) to the WTRU.
  • the registration accept may include an EAS address (e.g., end-point address) or a changed address for an EAS(s) associated with a relevant application(s).
  • EAS address e.g., end-point address
  • a first EAS address e.g., an end-point address(s) of a relevant application associated with the WTRU (e.g., installed in the WTRU) may be provided during a first registration (e.g., the initial registration).
  • the first EAS address may become stale (e.g., because the WTRU may be moving and/or may not trigger an application that requires EAS services).
  • a function associated with the network e.g., an AMF
  • the WTRU may trigger a mobility registration to update the first address to a second address or to request an address resolution (e.g., during the establishment of a PDU session), for example, using the timer.
  • the address resolution may include an EAS end-point address resolution.
  • Another function associated with the network e.g., a SMF
  • a function associated with the network e.g., the AMF and/or SMF may determine the value of the timer, for example, using network analytics.
  • An address (e.g., an end-point address) of an application function (e.g., an EAS acting as an AF) or an application server (e.g., EAS) may be updated through provisioning.
  • the provisioning may be based on a procedure for configuring a parameter associated with a network (e.g., a 3GPP network).
  • the parameter e.g., a NEF service parameter and/or a PCF service parameter
  • a network function may obtain a notification for a change of a first address of an application server (e.g., updated EAS end-point address information) from an AF, for example, when applications are migrated or end-point addresses are re-allocated.
  • the network function may be included in a network device.
  • the network function may obtain a second address (e.g., updated EAS end-point address information) based on a procedure for configuring or reconfiguring a parameter (e.g., a service parameter) associated with the network.
  • the AF may communicate updated EAS end-point address information to the network function via a NEF specific parameter provisioning service.
  • the AF may communicate the second address to the PCF directly (e.g., by enabling the AF to use the current specific parameter provisioning service directly toward the PCF).
  • the AF may push the second address (e.g., updated EAS End-point address) to the UDM or directly to the PCF.
  • An address (e.g., an end-point address) of an EAS may be updated via a procedure for configuring a parameter (e.g., an external parameter provisioning or a service parameter provisioning).
  • a function associated with the network may determine whether the address (e.g., updated EAS end-point address) should be sent (e.g., pushed) to the WTRU or whether it can wait, for example for the address to be sent to the WTRU later.
  • the function associated with the network may take into account whether the application and the particular WTRU context warrants an update (e.g., immediate update) or the update can be delayed until the WTRU contacts the 5GC again (e.g., through a mobility registration).
  • FIG.6 illustrates an example of an address update of an application server (e.g., an EAS) via a procedure for configuring a parameter (e.g., an external parameter provisioning).
  • the NF may subscribe to being notified an change of an address of an application server (e.g., EAS end-point address change).
  • the NF may send a UDM a request (e.g., Nudm_SDM_Subscribe request).
  • an AF associated with EAS e.g., an EAS acting as AF
  • NWDAF network data analytics function
  • WTRU mobility analytics and/or WTRU communication analytics may subscribe and/or WTRU communication analytics.
  • the AF may validate the received data and/or obtain (e.g., derive) a parameter associated with the WTRU (e.g., an expected WTRU behavior parameter).
  • the AF may determine that an address update (e.g., an EAS end-point address update) is to be performed.
  • the address update may be performed using a procedure for configuring a parameter (e.g., a NEF parameter) associated with the network.
  • the procedure for configuring a parameter (e.g., a NEF parameter) associated with the network may include one or more steps in FIG.6.
  • the AF may send a request for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete request), for example, to a NEF.
  • the NEF may send (e.g., forward) the request to the UDM.
  • the UDM may send a query (e.g., a Nudr_DM_Query) to the UDR, and the UDR may respond to the query.
  • the UDM may send an update (e.g., Nudr_DM_Update) to the UDR, and the UDR may respond to the update.
  • the UDM may send a response for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete response) to the NEF.
  • a parameter associated with the network e.g., Nnef_ParameterProvision_Create/Update/Delete response
  • the configured parameter (e.g., created, updated or deleted parameter) may indicate a change of the address.
  • the configured parameter may be used to determine the updated address.
  • the configured parameter may indicate the updated address.
  • the NEF may send (e.g., forward) the response to the AF.
  • the UDM may send a notification (e.g., Nudm_SDM_Notification Notify) to the NF, for example, based on the subscription.
  • a function associated with the network may use a WTRU configuration update mechanism to send (e.g., push) the EAS end-point address (e.g., if the AMF decides the EAS end-point address should be pushed) to a WTRU.
  • the WTRU configuration update may occur via a service request.
  • FIG.7 illustrates an example of a WTRU configuration update (e.g., for access and mobility management related parameters).
  • the example of a WTRU configuration update mechanism as illustrated in FIG.7 may be used, for example, to send the address of the EAS if the address of the EAS should be sent (e.g., as decided by the AMF).
  • the WTRU configuration update in FIG.7 may be for access and mobility management related parameters.
  • a function associated with the network e.g., AMF or SMF
  • may determine whether to update a WTRU configuration e.g., updating a first address of an EAS to a second address of an EAS
  • a second registration e.g., a re-registration subsequent to a first registration
  • a determination of whether the address update is performed without a second registration e.g., an immediate update without a second registration subsequent to the first registration
  • the WTRU re-registers e.g., via a second registration
  • the second address may be sent to the WTRU via a message (e.g., a WTRU configuration update command).
  • the second address may be sent to the WTRU via the second registration, for example, after the WTRU sends a request for the second registration (e.g., as shown in FIG.5).
  • the WTRU may send a response (e.g., a WTRU configuration update complete) after the first address is updated to the second address, for example, to the AMF.
  • the WTRU may inform higher layers the second address (e.g., by sending the second address from a first layer to a second layer such as an application layer that is higher than the first layer), for example, based on an application ID (e.g., the application ID as shown in FIG.9).
  • the WTRU may determine an application based on the application ID.
  • the application ID may be sent to the WTRU with the second address, for example, in the message.
  • the AMF may send (R)AN a message indicating an update (e.g., Update RAN).
  • the AMF may send Nudm_SDM_Info Service.
  • FIG.9 illustrates an example of an application relocation (e.g., a NW driven application relocation notification). Nnef_ParameterProvision_Delete request/response operations may be shown in the example of FIG.9.
  • the NF may subscribe an change of an address of an application server (e.g., EAS end-point address change triggered by application relocation).
  • the NF may send a UDM a request (e.g., Nudm_SDM_Subscribe request).
  • an AF associated with EAS e.g., an EAS acting as an AF
  • NWDAF network data analytics function
  • the AF may validate the received data and/or obtain (e.g., derive) a parameter associated with the WTRU (e.g., an expected WTRU behavior parameter).
  • a parameter associated with the WTRU e.g., an expected WTRU behavior parameter.
  • the AF may determine that an address update (e.g., an EAS end-point address update) is to be performed, for example, based on (e.g., upon) an application migration.
  • the address update may be performed using a procedure for configuring a parameter (e.g., a NEF parameter) associated with the network.
  • the AF may send a request for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete request), for example, to a NEF.
  • a request for creating, updating, or deleting a parameter associated with the network e.g., Nnef_ParameterProvision_Create/Update/Delete request
  • the AF may provide the DNAI and/or the application ID that are associated with the application that is migrated, for example, with the request.
  • the DNAI and/or the application ID may be sent to the WTRU, which may determine the application that is migrated based on the DNAI and/or the application ID.
  • the NEF may send (e.g., forward) the request to the UDM.
  • the UDM may send a query (e.g., a Nudr_DM_Query) to the UDR, and the UDR may respond to the query.
  • the UDM may send an update (e.g., Nudr_DM_Update) to the UDR, and the UDR may respond to the update.
  • the UDM may send a response for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete response) to the NEF.
  • the NEF may send (e.g., forward) the response to the AF.
  • the UDM may send a notification (e.g., Nudm_SDM_Notification Notify) to the NF, for example, based on the subscription.
  • a network (NW) driven local data network relocation may be performed based on (e.g., on a condition of) an edge application migration.
  • FIG.8 illustrates an example of an application relocation (e.g., a WTRU driven application relocation). A scenario where a WTRU is moving from a gNB (e.g., a first gNB) to another gNB (e.g., a second gNB) may be illustrated in FIG.8.
  • the WTRU may have access to a local data network (e.g., through DNAI-2 as shown in FIG.8), and the WTRU may be connected to a remote data network (e.g., cloud services), for example, depicted as DNAI-1 in FIG.8.
  • the 5GS may direct traffic to a local data network using DNAI-1 and DNAI-2, for example, to reach specific edge applications (e.g., Edge App1).
  • Edge App1 is to be relocated to DNAI-3 and no application layer procedures are in place to inform the WTRU that it no longer has access to Edge App1 using the current (e.g., known) Edge App1 end-point address, then data destined to Edge App1 may not be delivered.
  • One or more techniques described herein may be used to inform the 5GC that an edge application migration has occurred.
  • the application Id and/or the DNAI associated with the application that is being migrated may be provided, for example, using such technique(s).
  • the AF may choose a certain (e.g., an optimal) DNAI based on 5GC information, for example, using WTRU location monitoring information provided by the 5GC.
  • the example in FIG.8 may illustrate a WTRU driven application relocation.
  • the example in FIG.9 may illustrate a NW driven application relocation notification.
  • the NF may subscribe to UDM, or directly to the AF, for notifications of information updates, for example, as shown in 0d in FIG.9. If the NF (e.g., SMF) is subscribed to UDM, or directly to the AF, the update may be the result of an application relocation.
  • the AF may provide a notification (e.g., using the parameter provision notification to signal the change due to the application relocation), for example, as shown in 1 in FIG.9.
  • the AF may use a function associated with a network (e.g., the NEF) for these implementation(s); the AF may alternatively or additionally provide these information to the SMF (e.g., if the SMF has the possibility of subscribing to notifications directly from the AF).
  • the SMF may subscribe to receiving a notification and receive the notification base on the subscription.
  • a WTRU may drive a DNAI change.
  • FIG.10 illustrates an example of a data network access identifier (DNAI) change (e.g., a WTRU driven DNAI change on a condition of discovering a more suitable local area data network (LADN)).
  • DNAI data network access identifier
  • a WTRU may be moving from one gNB to another or finding an overlapping local area data network (LADN) or standalone non-public network (SNPN) network.
  • the WTRU may determine that access to a DNAI (e.g., a new DNAI), for example DNAI- 3, is warranted (e.g., based on policies and mapping from a combination of one or more of a DNN, a S- NSSAI, a DNI, a CAG ID).
  • the WTRU may determine that access to a DNAI is warranted (e.g., 1 in FIG.10).
  • the WTRU may decide to request the establishment of a PDU session (e.g., a new PDU Session).
  • the WTRU may provide the NW with one or more of the following: the relevant DNN, S-NSSAI, DNI, and/or CAG ID, and/or indicate that a DNN, a S-NSSAI, and/or the like is supported.
  • the WTRU may be preconfigured with mapping from the relevant DNN, S-NSSAI, DNI, CAG ID, and/or S-NSSAI to a specific DNAI. If the WTRU is preconfigured with mapping from these values to a specific DNAI, the WTRU may provide the relevant DNAI to the SMF.
  • the WTRU may request the establishment of a PDU session (e.g., 2 in FIG.10).
  • the SMF e.g., using a notification of a user plane management event procedure(s)
  • the procedure may be used upon PSA relocation, where the WTRU may trigger this PSA change (e.g., 3 in FIG.10).
  • the AF may reply (e.g., immediately) by using the service operation (e.g., defined by Nsmf_EventExposure_AppRelocationInfo) to provide the EAS end-point address, (e.g., the updated EAS End-Point-Address).
  • the establishment or continuation of the data communication between the WTRU and the Edge App1 may be enabled.
  • the AF may reply, for example, enabling the establishment or continuation of the data communication between the WTRU and the Edge App1 (e.g., 4 in FIG.10).
  • a WTRU driven DNAI change based on (e.g., upon) a discovery of a more suitable LADN may occur, for example, as illustrated in the example of FIG.10.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in devices described herein.

Abstract

A network device may receive a notification for a change of a first address for an application server {e.g., an edge application server (EAS)), The network device may obtain a second address of the application server based on a procedure for configuring a parameter associated with a network. The configured parameter associated with the network may indicate the change of the first address. The network device may send the second address, for example, such that the second address is forwarded to a wireless transmit/receive unit (VVTRU), The network device may subscribe to the notification for the change of the first address of the application server, and the notification may be received based on the subscription. The network device may obtain an application identifier (ID) associated with the second address and a data network access ID, based on the procedure for configuring the parameter associated with the network.

Description

DISCOVERY, SELECTION, AND ACCESS ASSOCIATED WITH EDGE COMPUTING NETWORKS CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of U.S. Provisional Application No.62/932,193, filed November 7, 2019, the content of which is incorporated by reference herein. BACKGROUND [0002] Mobile communications are in continuous evolution and are already at the doorstep of their fifth incarnation – 5G. SUMMARY [0003] An apparatus associated with a network (e.g., a network device) may receive a notification for a change of a first address for an application server (e.g., an edge application server (EAS)). The application server may be located outside the network. The apparatus may obtain a second address of the application server based on a procedure for configuring a parameter associated with the network. The configured parameter associated with the network may indicate the change of the first address. The apparatus may send the second address. The second address may be forwarded to a wireless transmit/receive unit (WTRU), for example, by the apparatus or by another apparatus. The apparatus may include a policy control function (PCF) or a session management function (SMF). The apparatus may subscribe to the notification for the change of the first address of the application server, and the notification may be received based on the subscription. The apparatus may obtain an application identifier (ID) associated with the second address and a data network access ID, based on the procedure for configuring the parameter associated with the network. [0004] The apparatus may receive a request for a first registration from the WTRU and determine that a configuration update for the WTRU is to occur without a second registration based on at least one of: a characteristic of an application associated with the application server or a context associated with the WTRU. The second address may be forwarded to the WTRU without the second registration. [0005] The apparatus may receive a request for a first registration from the WTRU and determine that a configuration update for the WTRU is to occur via a second registration based on at least one of: a characteristic of an application associated with the application server or a context associated with the WTRU. The apparatus may receive a request for the second registration that is subsequent to the first registration. The second address may be forwarded to the WTRU via the second registration. [0006] The notification for the change of the first address may be associated with an application migration or an address re-location. The first address and/or the second address may be an end-point address. The procedure may include a service parameter provisioning procedure. [0007] A wireless transmit/receive unit (WTRU) configured to communicate with a network may obtain a first address of an application server (e.g., an EAS). The WTRU may receive a second address of the application server and an application ID associated with the second address. The WTRU may determine an application associated with the second address based on the application ID. The WTRU may perform an update of the first address of the application server based on the second address and the application associated with the second address. The WTRU may request the second address of the application server during an establishment of a package data unit (PDU) session. The WTRU may receive a timer for triggering a mobility registration to the network. The WTRU may send a request for a first registration to the network and receive the second address without a second registration. In some examples, the WTRU may send a request for a first registration to the network, send a request for the second registration to the network, and receive the second address via the second registration. BRIEF DESCRIPTION OF THE DRAWINGS [0008] FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented; [0009] FIG.1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0010] FIG.1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0011] FIG.1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0012] FIG.2 illustrates an example of an edge computing reference model in 5GS; [0013] FIG.3 illustrates an example of application function influence on user traffic; [0014] FIG.4 illustrates an example of an application layer architecture (e.g., a SA WG6 or SA6 application layer architecture for enabling edge applications); [0015] FIG.5 illustrates an example of EAS end-point address resolution, e.g., during registration; [0016] FIG.6 illustrates an example of an address update of an application server (e.g., an EAS) via a procedure for configuring a parameter (e.g., an external parameter provisioning); [0017] FIG.7 illustrates an example of a WTRU configuration update (e.g., for access and mobility management related parameters); [0018] FIG.8 illustrates an example of an application relocation (e.g., a WTRU driven application relocation); [0019] FIG.9 illustrates an example of an application relocation (e.g., a NW driven application relocation notification); and [0020] FIG.10 illustrates an example of a data network access identifier (DNAI) change (e.g., a WTRU driven DNAI change on a condition of discovering a more suitable local area data network (LADN)). DETAILED DESCRIPTION [0021] FIG.1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), 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 multicarrier (FBMC), and the like. [0022] As shown in FIG.1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and/or a “STA”, may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE. [0023] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the 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, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements. [0024] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. [0025] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT). [0026] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA). [0027] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro). [0028] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR). [0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB). [0030] 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, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. [0031] The base station 114b in FIG.1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In 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 femtocell. As shown in FIG.1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115. [0032] The RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG.1A, it will be appreciated that the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT. For example, in addition to being connected to the RAN 104/113, which may be utilizing a NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. [0033] The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT. [0034] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG.1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology. [0035] FIG.1B is a system diagram illustrating an example WTRU 102. As shown in FIG.1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. [0036] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG.1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip. [0037] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals. [0038] Although the transmit/receive element 122 is depicted in FIG.1B 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. [0039] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example. [0040] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), 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, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown). [0041] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like. [0042] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment. [0043] The processor 118 may further be coupled to other peripherals 138, which may include one or more software 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 e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor. [0044] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the 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 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)). [0045] FIG.1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106. [0046] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. [0047] Each of the eNode-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 the UL and/or DL, and the like. As shown in FIG.1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0048] The CN 106 shown in FIG.1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0049] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA. [0050] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the 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 user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like. [0051] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. [0052] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. [0053] Although the WTRU is described in FIGS.1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [0054] In representative embodiments, the other network 112 may be a WLAN. [0055] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication. [0056] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS. [0057] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel. [0058] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC). [0059] Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The 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 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life). [0060] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available. [0061] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code. [0062] FIG.1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115. [0063] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c). [0064] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time). [0065] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c. [0066] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface. [0067] The CN 115 shown in FIG.1D may include at least one AMF 182a, 182b, at least one UPF 184a,184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0068] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi. [0069] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet- based, and the like. [0070] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, 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, and the like. [0071] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b. [0072] In view of Figures 1A-1D, and the corresponding description of Figures 1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions. [0073] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications. [0074] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data. [0075] An edge computing network(s) may use a local access (e.g., the concept of a local access) to a data network. FIG.2 illustrates an example of an edge computing reference model in 5GS. As illustrated in FIG.2, an edge application server (EAS) may be located in (e.g., within the scope of) a local data network which may be accessed (e.g., employing an uplink classifier or branching point to divert user traffic according to packet detection rules installed in the UPF by its controlling SMF). AN may stand for access network in FIG.2. As shown in FIG.2, the EAS may be within a data network (DN) located at the edge, for example, on a user plane. [0076] A detection rule(s) may be used to identify traffic that is to be (e.g., needs to be) routed selectively. User traffic, (e.g., user traffic supporting specific applications) may be treated differently under different conditions including one or more of a geographical location, a time of day, or traffic content. Conditions may vary, for example, over time. Treatment of user data traffic may include (e.g., require) dynamic handling of policies and/or rules, for example, depending on a characteristic of the application (e.g., the need of the application). The characteristic of the application may be determined by an Application Function (AF). User traffic may be handled dynamically. [0077] Data network access identifiers (DNAI) may relate to edge computing. Edge computing support may be provided. A network system (e.g., 5G system (5GS)) may be able to route user traffic to a local data network, for example, by using traffic filters (e.g., in the form of routing profiles and/or traffic routing information associated to an access to a specific data network location). FIG.3 illustrates an example of application function influence on user traffic. The data network location may be identified by a Data Network Access Identifier (DNAI) (e.g., DNAI-1, DNAI-2, or DNAI-3, as shown in FIG.3). As an example, DNAI identifying data network locations may be illustrated in FIG.3. An application function (AF) may request an action through (e.g., directly through) a policy control function (PCF) or a network exposure function (NEF). As shown in FIG.3, PCF, a SMF and a UPF may be located in (e.g., within a scope of) a first network (e.g., 3GPP network). As shown in FIG.3, an EAS may be located in a second network (e.g., an edge data network) and outside the first network, for example, on the user plane. As shown in FIG.3, an AF may be connected to the network. [0078] An AF may send a request(s) to 5G core (5GC) (e.g., a PCF or a NEF), for example, to influence one or more SMF routing decisions for user plane (UP) traffic. The UP traffic may be for a PDU sessions(s) destined to a data Network(s) that supports a specific application. The AF may use a service based application programming interface (API) to access the PCF (e.g., if the AF has a trusted relationship with the Network Operator). The AF may send the request using the NEF (e.g., if the AF does not have a trusted relationship with the Network Operator). [0079] The PCF may determine if a current PDU sessions(s) is potentially impacted by the request that the AF sent. The PCF may use the application traffic and one or more of the following information (e.g., one or more of the following information related to the subscriber session) as input for selecting a traffic steering policy: network operator's policies, a user subscription, the user's current radio access technology (RAT), a network load status, an application identifier, a time of day, a WTRU location, and/or a data network name (DNN). [0080] For a PDU session (e.g., each of the current PDU sessions) that is potentially impacted by the AF request, the PCF may update the SMF based on a corresponding updated (e.g., new) policy and charging control (PCC) rule(s), for example, by invoking a SM policy control service operation as illustrated in FIG.3. [0081] The PCF may update one or more policies (e.g., the relevant policies) in the SMF that apply to one or more of the following: a particular PDU session, a WTRU, or a collection of WTRUs. [0082] A request that is sent by a third-party provider (e.g., an AF as shown in FIG.3) may influence the UPF selection (e.g., reselection) and/or allow routing of user traffic to a local access identified by a DNAI, for example, as described herein. The request (e.g., the request sent by the AF) may include traffic filters that may be installed in the selected UPF (e.g., the UPF handling the PDU session, for example, the UPF shown in FIG.3). The selected UPF may act upon the traffic filters installed in the UPF, for example, by routing user traffic to the DNAI associated with one or more of the following: a DNN, subscribed network slice selection assistance information (S-NSSAI), and/or a PDU session. FIG.3 illustrates that the DNAI may represent the access to a second network (e.g., a data network) where applications relevant to the traffic being routed are located. [0083] In examples, the UPF may mark packets (e.g., to indicate a certain type of traffic to the data network (DN) side of the N6 reference point). UPF packet marking may enable those packets to be steered in the DN. The UPF may forward (e.g., offload) traffic identified by a traffic descriptor to a local tunnel. [0084] There may be application layer considerations when supporting edge computing services. An application layer solution may be used to enhance edge computing services, for example, edge application server discovery. Application layer mechanism(s) may be used to enhance edge computing services. [0085] An application layer approach may enhance edge computing services (e.g., one or more of edge application server discovery, edge application server selection, and/or edge application server reselection). FIG.4 illustrates an application layer architecture supporting edge computing services. [0086] FIG.4 shows a first network (e.g., a 3GPP network) and a second network (e.g., an edge data network). One or more of the edge application servers may be in (e.g., located in) the second network. The one or more of the edge application servers may be outside (e.g., located outside) the first network, for example, on a user plane. The WTRU may be associated with one or more application clients. FIG.4 shows that “Application Data Traffic”, “EDGE 1” reference point, and “EDGE 4” reference point may be carried as user plane traffic (e.g., carried over a PDU session(s) supported through a UPF). As shown in FIG.4, one or more components of the EAS may act as an AF connected to the first network, for example, via the EDGE-7 interface. [0087] EDGE 2 may be an API for retrieval of network capability information and/or may be a control plane interface (e.g., EDGE 2 may use a service based operation(s) using relevant APIs). [0088] EASs may be discovered. An application client in a WTRU may use operating system (OS) services to determine an IP Address based on a fully qualified domain name (FQDN) (e.g., resolve a FQDN into an IP Address). A name-based approach may be used, for example, to reach the EAS supporting a certain application. The WTRU may resolve (e.g., be required to resolve) the FQDN to reach the EAS supporting a particular application, for example, if a name-based approach is not used. In some examples, the client may not have a configured FQDN to reach the local EAS. In an edge environment, domain name server (DNS) may present issues that may prevent a FQDN from being resolved to a proper EAS instance (e.g., the issues may include a cache that is not supported, time to live (TTL) zero that is not supported, and/or the like). Constantly re-configuring the DNS servers or invalidating cache may introduce delays that are in contradiction to the low latency nature of the edge, as the gains provided by the close proximity that the edge provides, are offset by the delays introduced by the DNS resolution. [0089] The application server (AS) address that was obtained by the application client may no longer be valid, for example, after an address resolution has taken place (e.g., if the application running at the server side has been relocated and/or if the application instance has crashed). The AS address may not meet performance requirements of the application client (e.g., the AS address may be valid but not meet performance requirements). The AS server may be located far from the application client, for example, to an extent where an application relocation may be warranted. [0090] A WTRU may determine a suitable AS address. Mechanisms may enable the WTRU to determine a suitable AS address, for example, in cases where the WTRU does not have a configured FQDN and/or the WTRU has a stale AS address. The suitable AS address may include, for example, an AS address that causes the AS to satisfy (e.g., leading to AS capable of satisfying) the needs of applications running in the WTRU. These mechanisms may not require application layer solutions (e.g., the solutions may or may not always apply). [0091] Service continuity may be maintained upon an application relocation (e.g., at the AS), a PDU session anchor (PSA) change or both. Service continuity may be affected, and/or the user’s experience (e.g., QoE or QoS) may be impacted. Service continuity may be affected (and/or the user’s experience may be impacted) when an application running in an EAS is relocated (e.g., due to one or more of the following: an EAS crash, a load balancing, a server maintenance, a performance change, WTRU mobility warranting an EAS change, and/or the migration towards aa different EAS causing a different application address assignment). Service continuity may be affected (and/or the user’s experience may be impacted) if the PSA changes due to WTRU mobility. [0092] When an application running in EAS is to be relocated or the PSA changes, the change of AS address and/or client address at the WTRU may cause a packet loss and end-point addresses to be re- synchronized. [0093] Mechanisms may be used to preserve service continuity when an application running in EAS relocates, the PSA changes, or both occur. Service continuity, session continuity, or both may be used (e.g., required based on the needs of the application). [0094] An address (e.g., an end-point address) of an EAS may be indicated in a registration request, for example, by a WTRU. A WTRU may obtain (e.g., read) system information, for example, upon or after powering on, and, the WTRU may determine one or more of the following: tracking area code(s) (TACs), public land mobile network ID(s) (PLMN IDs), network identifier(s) (NIDs), and/or closed access group (CAG) identifier(s). [0095] An application ID may map to a NID/PLMN pair and/or map to a TAC. A WTRU may be configured with a mapping of application IDs to NID/PLMN pairs or TACs (e.g., representing a location). In an example, the WTRU may select a NID/PLMN pair (e.g., a combination of NID and PLMN) and/or a TAC to satisfy its application needs (based on the application ID), for example, when the WTRU reads the system information (e.g., SIB). [0096] The WTRU may use one or more of the following: a reserved NID, a reserved CAG ID, a reserved application name, or a reserved application ID, if the WTRU is not configured with an FQDN or AS end-point address, to indicate (e.g., signal) the network that an EAS end-point address is to be provided to the WTRU, for example, when the WTRU does not have the EAS end-point address or is to renew the EAS end-point address (e.g., an old EAS end-point address). In an example, a WTRU may include one or more of a reserved NID, a reserved CGS ID, a reserved application name or a reserved application ID in a registration request to indicate to the network to which network/CGS/application a change of address applies. The network (e.g., the AMF, UDM, PCF or SMF) may use a reserved name(s)/ID(s) to indicate that these identifiers can be used by the when WTRU does not have the correct EAS end-point address to select an EAS and its end-point address. [0097] The WTRU may use a reserved S-NSSAI, DNN, 5G virtual network (VN) group ID, application name or application ID, and/or a value (e.g., a value for an information element (IE) associated with the indicating the EAS end-point address) to indicate the network that an EAS end-point address is to be provided to the WTRU. In an example, one or more FQDNs/URIs may be provided to the WTRU, for example, if the client wants to contact multiple application addresses through different FQDNs/URIs. An IE, which may be a separate IE (e.g., “EAS End-Point-address-required”), may be included in the registration request, for example, for a first registration (e.g., an initial registration) and/or a second registration (e.g., a mobility registrations), for example, if the WTRU has a PDU session(s) to be activated. The WTRU may include (e.g., explicitly include) a FQDN, a uniform resource identifier (URI), and/or a list of URIs or FQDNs of the AS end-point address(es) that the WTRU wants to reach. [0098] An address (e.g., an end-point address) of an EAS may be handled (e.g., stored) at the unified data management (UDM) and/or PCF. A function associated with the network (e.g., the AMF) may request another function associated with the network (e.g., the PCF) to include the address of an EAS, or a list of addresses associated with the EAS, for example, during registration (e.g., during a registration procedure). The address of the EAS or the list of the address may be associated with a combination of one or more of a DNN, a S-NSSAI, or a NID or may be associated with a certain (e.g., specified) FQDN or a uniform resource identifier (URI). The address of the EAS or the list of the addresses may be associated with a list (e.g., a container) including: a combination of one or more of a DNN, a S-NSSAI, or a NID; a certain FQDN; and a URI. A parameter associated with the network may include one or more of: a DNN, a S-NSSAI, a NID, a FQDN, or a URI. [0099] The address of the EAS may be stored at the PCF or at the UDM. When the AMF reads the subscriber records in the UDM (e.g., during the registration procedure), a function associated with the network (e.g., an AMF) may determine whether an address resolution service (e.g., the end-point address resolution service) is to be performed based on an application requirement, for example, whether an application requirement warrants the end-point address resolution service. Another function associated with the network (e.g., a PCF) may determine whether an address resolution service is to be performed based on an application requirement, for example, based on one or more policies and/or a WTRU context. In an example, the determination of whether an application requirement warrants a support of an address resolution service by the 5GS may be performed at the PCF based on operator policies or policies (e.g., policies pushed from the AF for certain applications or application set(s)) and/or based on a certain WTRU context, (e.g., one or more of a time of the day, a geographical proximity to the EAS, a topographical proximity to the EAS, a subscriber category, a computing capability, a storage capability, security requirements, and/or load balancing). One or more of a computing capability, a storage capability, security requirements, load balancing requirements, and/or the like, for EAS, may be considered, for example, by the PCF to determine whether an application requirement warrants a support of an address resolution service by the 5GS. This may avoid unnecessary signaling. If an address (e.g., an end-point address) resolution is not to be performed (e.g., not permitted), the function associated with the network may indicate to the WTRU (e.g., via the registration accept message or using a new IE) that an address resolution for the EAS is to take place by other approaches (e.g., a regular DNS resolution or an application layer-based resolution). [0100] An address (e.g., an end-point address) of an EAS may be handled at a network repository function (NRF). An AF (e.g., an AF associated with an EAS) may publish an address of an EAS (e.g., the AF EAS end-point address), for example, based on (e.g., directly using) the NRF API or through the NEF. A function associated with the network (e.g., an AMF) may use the NRF to resolve the address(es) of the EAS, for example, when the WTRU requests the 5GC to determine the address(s) for EAS(s) associated with certain applications. The function associated with the network may use techniques described herein (e.g., techniques associated with EAS end-point address being handled at the UDM and/or PCF) to determine whether the address resolution (e.g., an EAS end-point resolution) is to be performed or not. [0101] A function associated with the network (e.g., an AMF) may provide an address (e.g., an end-point address) of an EAS, for example, to a WTRU during registration. If the function determines the address of the EAS (e.g., using mechanism(s) described herein), the function may provide the address to the WTRU (e.g., using a registration accept message. FIG.5 illustrates an example of EAS end-point address resolution during registration. As shown in FIG.5, an AMF may receive a request for a registration (e.g., registration request) from a WTRU. As shown in FIG.5, the registration request may include one or more of the following: a S-NSSAI, a DNN, a 5G VN group ID, an application name, an application ID, a FQDR, or a URI. As shown in FIG.5, the AMF may send an address resolution request (e.g., an EAS end-point resolution request) to a UDM or a PCF. As shown in FIG.5, an AF associated with an EAS may notify the NEF an address of the EAS or a change of the address, and the NEF may send the address of the EAS or the change of the address to the UDM or PCF via a procedure for configuring a parameter associated with the network (e.g., AF(EAS) Nnef parameter provision). As shown in FIG.5, one or more components of the EAS may act as an AF (e.g., AF(EAS)). As shown in FIG.5, the AF may be connected to a network (e.g., part of a network). As shown in FIG.5, the AF associated with an EAS may send the address of the EAS or the change of the address to the UDM or PCF via the procedure for configuring a parameter associated with the network (e.g., AF(EAS) Nnef parameter provision). As shown in FIG.5, the UDM or the PCF may send an address resolution response (e.g., including the address of the EAS or the change of the address) to the AMF. As shown in FIG.5, the AMF may send an address resolution request (e.g., an EAS end-point resolution request) to a NRF. As shown in FIG.5, the AF associated with an EAS may publish the address of the EAS or the change of the address to a NRF (e.g., via AF(EAS) Publish End-point address). As shown in FIG.5, the NRF may send an address resolution response (e.g., including the address of the EAS or the change of the address) to the AMF. As shown in FIG.5, the function associated with the network (e.g., the AMF) may determine whether an address resolution (e.g., an EAS end-point resolution) is warranted, for example, based on a WTRU context and/or policies. As shown in FIG.5, the AMF may send a acceptance for the registration (e.g., registration accept) to the WTRU. As shown in FIG.5, the registration accept may include an EAS address (e.g., end-point address) or a changed address for an EAS(s) associated with a relevant application(s). [0102] A first EAS address (e.g., an end-point address(s)) of a relevant application associated with the WTRU (e.g., installed in the WTRU) may be provided during a first registration (e.g., the initial registration). The first EAS address may become stale (e.g., because the WTRU may be moving and/or may not trigger an application that requires EAS services). A function associated with the network (e.g., an AMF) may provide a timer for the WTRU. The WTRU may trigger a mobility registration to update the first address to a second address or to request an address resolution (e.g., during the establishment of a PDU session), for example, using the timer. The address resolution may include an EAS end-point address resolution. Another function associated with the network (e.g., a SMF) may provide the timer for the WTRU (e.g., by fetching the timer from the UDM/PCF or from the NRF), for example, if the WTRU requests an address resolution during the establishment of a PDU session. A function associated with the network (e.g., the AMF and/or SMF) may determine the value of the timer, for example, using network analytics. [0103] An address (e.g., an end-point address) of an application function (e.g., an EAS acting as an AF) or an application server (e.g., EAS) may be updated through provisioning. The provisioning may be based on a procedure for configuring a parameter associated with a network (e.g., a 3GPP network). The parameter (e.g., a NEF service parameter and/or a PCF service parameter) may be associated with the network. A network function (e.g., the PCF associated with the network or the SMF associated with the network) may obtain a notification for a change of a first address of an application server (e.g., updated EAS end-point address information) from an AF, for example, when applications are migrated or end-point addresses are re-allocated. The network function may be included in a network device. The network function may obtain a second address (e.g., updated EAS end-point address information) based on a procedure for configuring or reconfiguring a parameter (e.g., a service parameter) associated with the network. In an example, the AF may communicate updated EAS end-point address information to the network function via a NEF specific parameter provisioning service. The AF may communicate the second address to the PCF directly (e.g., by enabling the AF to use the current specific parameter provisioning service directly toward the PCF). The AF may push the second address (e.g., updated EAS End-point address) to the UDM or directly to the PCF. [0104] An address (e.g., an end-point address) of an EAS may be updated via a procedure for configuring a parameter (e.g., an external parameter provisioning or a service parameter provisioning). A function associated with the network (e.g., an AMF) may determine whether the address (e.g., updated EAS end-point address) should be sent (e.g., pushed) to the WTRU or whether it can wait, for example for the address to be sent to the WTRU later. The function associated with the network may take into account whether the application and the particular WTRU context warrants an update (e.g., immediate update) or the update can be delayed until the WTRU contacts the 5GC again (e.g., through a mobility registration). [0105] FIG.6 illustrates an example of an address update of an application server (e.g., an EAS) via a procedure for configuring a parameter (e.g., an external parameter provisioning). As shown in FIG.6, the NF (e.g., the PCF) may subscribe to being notified an change of an address of an application server (e.g., EAS end-point address change). As shown in FIG.6, the NF may send a UDM a request (e.g., Nudm_SDM_Subscribe request). As shown in FIG.6, an AF associated with EAS (e.g., an EAS acting as AF) may subscribe and/or receive from network data analytics function (NWDAF) WTRU mobility analytics and/or WTRU communication analytics. As shown in FIG.6, the AF may validate the received data and/or obtain (e.g., derive) a parameter associated with the WTRU (e.g., an expected WTRU behavior parameter). As shown in FIG.6, the AF may determine that an address update (e.g., an EAS end-point address update) is to be performed. As shown in FIG.6, the address update may be performed using a procedure for configuring a parameter (e.g., a NEF parameter) associated with the network. The procedure for configuring a parameter (e.g., a NEF parameter) associated with the network may include one or more steps in FIG.6. As shown in FIG.6, the AF may send a request for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete request), for example, to a NEF. As shown in FIG.6, the NEF may send (e.g., forward) the request to the UDM. As shown in FIG.6, the UDM may send a query (e.g., a Nudr_DM_Query) to the UDR, and the UDR may respond to the query. As shown in FIG.6, the UDM may send an update (e.g., Nudr_DM_Update) to the UDR, and the UDR may respond to the update. As shown in FIG.6, the UDM may send a response for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete response) to the NEF. The configured parameter (e.g., created, updated or deleted parameter) may indicate a change of the address. The configured parameter may be used to determine the updated address. The configured parameter may indicate the updated address. As shown in FIG.6, the NEF may send (e.g., forward) the response to the AF. As shown in FIG. 6, the UDM may send a notification (e.g., Nudm_SDM_Notification Notify) to the NF, for example, based on the subscription. [0106] A function associated with the network (e.g., an AMF) may use a WTRU configuration update mechanism to send (e.g., push) the EAS end-point address (e.g., if the AMF decides the EAS end-point address should be pushed) to a WTRU. The WTRU configuration update may occur via a service request. FIG.7 illustrates an example of a WTRU configuration update (e.g., for access and mobility management related parameters). The example of a WTRU configuration update mechanism as illustrated in FIG.7 may be used, for example, to send the address of the EAS if the address of the EAS should be sent (e.g., as decided by the AMF). The WTRU configuration update in FIG.7 may be for access and mobility management related parameters. As shown in FIG.7, a function associated with the network (e.g., AMF or SMF) may determine whether to update a WTRU configuration (e.g., updating a first address of an EAS to a second address of an EAS) or trigger a second registration (e.g., a re-registration subsequent to a first registration). As shown in FIG.7, a determination of whether the address update is performed without a second registration (e.g., an immediate update without a second registration subsequent to the first registration) or is to be performed until the WTRU re-registers (e.g., via a second registration), for example, based on one or more application characteristics and a WTRU context. As shown in FIG.7, if a determination is made that the address update is to be performed without a second registration, the second address may be sent to the WTRU via a message (e.g., a WTRU configuration update command). If a determination is made that the address update is to be performed via the second registration, the second address may be sent to the WTRU via the second registration, for example, after the WTRU sends a request for the second registration (e.g., as shown in FIG.5). As shown in FIG.7, the WTRU may send a response (e.g., a WTRU configuration update complete) after the first address is updated to the second address, for example, to the AMF. As shown in FIG.7, the WTRU may inform higher layers the second address (e.g., by sending the second address from a first layer to a second layer such as an application layer that is higher than the first layer), for example, based on an application ID (e.g., the application ID as shown in FIG.9). The WTRU may determine an application based on the application ID. The application ID may be sent to the WTRU with the second address, for example, in the message. As shown in FIG.7, the AMF may send (R)AN a message indicating an update (e.g., Update RAN). As shown in FIG.7, the AMF may send Nudm_SDM_Info Service. [0107] FIG.9 illustrates an example of an application relocation (e.g., a NW driven application relocation notification). Nnef_ParameterProvision_Delete request/response operations may be shown in the example of FIG.9. As shown in FIG.9, the NF (e.g., the SMF) may subscribe an change of an address of an application server (e.g., EAS end-point address change triggered by application relocation). As shown in FIG.9, the NF may send a UDM a request (e.g., Nudm_SDM_Subscribe request). As shown in FIG.9, an AF associated with EAS (e.g., an EAS acting as an AF) may subscribe and/or receive from network data analytics function (NWDAF) WTRU mobility analytics and/or WTRU communication analytics. As shown in FIG.9, the AF may validate the received data and/or obtain (e.g., derive) a parameter associated with the WTRU (e.g., an expected WTRU behavior parameter). As shown in FIG.9, the AF may determine that an address update (e.g., an EAS end-point address update) is to be performed, for example, based on (e.g., upon) an application migration. As shown in FIG.9, the address update may be performed using a procedure for configuring a parameter (e.g., a NEF parameter) associated with the network. As shown in FIG.9, the AF may send a request for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete request), for example, to a NEF. As shown in FIG.9, the AF may provide the DNAI and/or the application ID that are associated with the application that is migrated, for example, with the request. The DNAI and/or the application ID may be sent to the WTRU, which may determine the application that is migrated based on the DNAI and/or the application ID. As shown in FIG.9, the NEF may send (e.g., forward) the request to the UDM. As shown in FIG.9, the UDM may send a query (e.g., a Nudr_DM_Query) to the UDR, and the UDR may respond to the query. As shown in FIG.9, the UDM may send an update (e.g., Nudr_DM_Update) to the UDR, and the UDR may respond to the update. As shown in FIG.9, the UDM may send a response for creating, updating, or deleting a parameter associated with the network (e.g., Nnef_ParameterProvision_Create/Update/Delete response) to the NEF. As shown in FIG.9, the NEF may send (e.g., forward) the response to the AF. As shown in FIG.9, the UDM may send a notification (e.g., Nudm_SDM_Notification Notify) to the NF, for example, based on the subscription. [0108] A network (NW) driven local data network relocation may be performed based on (e.g., on a condition of) an edge application migration. FIG.8 illustrates an example of an application relocation (e.g., a WTRU driven application relocation). A scenario where a WTRU is moving from a gNB (e.g., a first gNB) to another gNB (e.g., a second gNB) may be illustrated in FIG.8. The WTRU may have access to a local data network (e.g., through DNAI-2 as shown in FIG.8), and the WTRU may be connected to a remote data network (e.g., cloud services), for example, depicted as DNAI-1 in FIG.8. [0109] The 5GS may direct traffic to a local data network using DNAI-1 and DNAI-2, for example, to reach specific edge applications (e.g., Edge App1). In an example, if Edge App1 is to be relocated to DNAI-3 and no application layer procedures are in place to inform the WTRU that it no longer has access to Edge App1 using the current (e.g., known) Edge App1 end-point address, then data destined to Edge App1 may not be delivered. [0110] One or more techniques described herein (e.g., EAS end-point update through NEF/PCF service parameter provisioning) may be used to inform the 5GC that an edge application migration has occurred. The application Id and/or the DNAI associated with the application that is being migrated may be provided, for example, using such technique(s). The AF may choose a certain (e.g., an optimal) DNAI based on 5GC information, for example, using WTRU location monitoring information provided by the 5GC. The example in FIG.8 may illustrate a WTRU driven application relocation. The example in FIG.9 may illustrate a NW driven application relocation notification. [0111] There may be request and/or response operations associated with Nnef_ParameterProvision_Delete. The NF (e.g., SMF) may subscribe to UDM, or directly to the AF, for notifications of information updates, for example, as shown in 0d in FIG.9. If the NF (e.g., SMF) is subscribed to UDM, or directly to the AF, the update may be the result of an application relocation. The AF may provide a notification (e.g., using the parameter provision notification to signal the change due to the application relocation), for example, as shown in 1 in FIG.9. The AF may use a function associated with a network (e.g., the NEF) for these implementation(s); the AF may alternatively or additionally provide these information to the SMF (e.g., if the SMF has the possibility of subscribing to notifications directly from the AF). The SMF may subscribe to receiving a notification and receive the notification base on the subscription. [0112] A WTRU may drive a DNAI change. FIG.10 illustrates an example of a data network access identifier (DNAI) change (e.g., a WTRU driven DNAI change on a condition of discovering a more suitable local area data network (LADN)). As shown in the example of FIG.10, a WTRU may be moving from one gNB to another or finding an overlapping local area data network (LADN) or standalone non-public network (SNPN) network. The WTRU may determine that access to a DNAI (e.g., a new DNAI), for example DNAI- 3, is warranted (e.g., based on policies and mapping from a combination of one or more of a DNN, a S- NSSAI, a DNI, a CAG ID). In the example of FIG.10, the WTRU may determine that access to a DNAI is warranted (e.g., 1 in FIG.10). [0113] The WTRU may decide to request the establishment of a PDU session (e.g., a new PDU Session). The WTRU may provide the NW with one or more of the following: the relevant DNN, S-NSSAI, DNI, and/or CAG ID, and/or indicate that a DNN, a S-NSSAI, and/or the like is supported. The WTRU may be preconfigured with mapping from the relevant DNN, S-NSSAI, DNI, CAG ID, and/or S-NSSAI to a specific DNAI. If the WTRU is preconfigured with mapping from these values to a specific DNAI, the WTRU may provide the relevant DNAI to the SMF. As illustrated in the example of FIG.10, the WTRU may request the establishment of a PDU session (e.g., 2 in FIG.10). [0114] The SMF (e.g., using a notification of a user plane management event procedure(s)) may notify the AF that the WTRU has established a connection to a data network referenced through a DNAI. The procedure may be used upon PSA relocation, where the WTRU may trigger this PSA change (e.g., 3 in FIG.10). [0115] The AF may reply (e.g., immediately) by using the service operation (e.g., defined by Nsmf_EventExposure_AppRelocationInfo) to provide the EAS end-point address, (e.g., the updated EAS End-Point-Address). The establishment or continuation of the data communication between the WTRU and the Edge App1 may be enabled. As illustrated in the example of FIG.10, the AF may reply, for example, enabling the establishment or continuation of the data communication between the WTRU and the Edge App1 (e.g., 4 in FIG.10). A WTRU driven DNAI change based on (e.g., upon) a discovery of a more suitable LADN may occur, for example, as illustrated in the example of FIG.10. [0116] Although the features and elements of the present disclosure may consider New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well. [0117] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in devices described herein.

Claims

CLAIMS What is Claimed: 1. A network device, comprising: a processor configured to: receive a notification of a change of a first address of an edge application server; obtain a second address of the edge application server based on a procedure for configuring a parameter associated with a network, wherein the configured parameter associated with the network indicates the change of the first address; and send the second address of the edge application server.
2. A method, comprising: receiving a notification of a change of a first address of an edge application server; obtaining a second address of the edge application server based on a procedure for configuring a parameter associated with a network, wherein the configured parameter associated with the network indicates the change of the first address; and sending the second address of the edge application server.
3. The network device of claim 1 or the method of claim 2, wherein the second address is sent to a wireless transmit/receive unit (WTRU) or forwarded to the WTRU via another network device.
4. The network device of claim 1 or the method of claim 2, wherein the edge application server is located outside the network.
5.^ The network device of claim 1, wherein the processor is further configured to subscribe to the notification of the change of the first address of the edge application server, wherein the notification is received based on the subscription.
6. The network device of claim 1, wherein the processor is further configured to obtain an application identifier (ID) associated with the second address and a data network access ID, based on the procedure for configuring the parameter associated with the network.
7. The network device of claim 1, wherein the processor is further configured to: receive a request for a first registration from a wireless transmit/receive unit (WTRU); and determine that a configuration update for the WTRU is to occur without a second registration based on at least one of: a characteristic of an application associated with the edge application server or a context associated with the WTRU, wherein the second address is forwarded to the WTRU without the second registration.
8. The network device of claim 1, wherein the processor is further configured to: receive a request for a first registration from a wireless transmit/receive unit (WTRU); determine that a configuration update for the WTRU is to occur via a second registration based on at least one of: a characteristic of an application associated with the edge application server or a context associated with the WTRU; and receive a request for a second registration, wherein the second registration is subsequent to the first registration, and the second address is forwarded to the WTRU via the second registration.
9. The network device of claim 1, wherein the processor is further configured to: receive a request for a first registration from a wireless transmit/receive unit (WTRU); determine that a configuration update for the WTRU is to occur via a service request based on at least one of: a characteristic of an application associated with the edge application server or a context associated with the WTRU, wherein the second address is forwarded to the WTRU based on the service request from the WTRU.
10. The network device of claim 1 or the method of claim 2, wherein the notification is associated with an application migration or an address re-location.
11. The network device of claim 1 or the method of claim 2, wherein the second address comprises an end-point address, and the procedure comprises a service parameter provisioning procedure.
12. The network device of claim 1, wherein the network device comprises a policy control function or a session management function.
13. The method of claim 2, further comprising obtaining an application identifier (ID) associated with the second address and a data network access ID, based on the procedure for configuring the parameter associated with the network.
14. A wireless transmit/receive unit (WTRU) configured to communicate with a network, comprising: a processor configured to: obtain a first address of an edge application server; receive a second address of the edge application server and an application identifier (ID) associated with the second address; determine an application associated with the second address based on the application ID; and perform an update of the first address of the edge application server based on the second address and the application associated with the second address.
15. A method comprising: obtaining a first address of an edge application server; receiving a second address of the edge application server and an application identifier (ID) associated with the second address; determining an application associated with the second address based on the application ID; and performing an update of the first address of the edge application server based on the second address and the application associated with the second address.
16. The WTRU of claim 14, wherein the processor is further configured to request the second address of the application server during an establishment of a package data unit (PDU) session.
17. The WTRU of claim 14, wherein the processor is further configured to receive a timer for triggering a mobility registration to the network.
18. The WTRU of claim 14, wherein the processor is further configured to: send a request for a first registration to the network, wherein the second address is received without a second registration.
19. The WTRU of claim 14, wherein the processor is further configured to: send a request for a first registration to the network; and send a request for a second registration to the network, wherein the second registration is subsequent to the first registration, and the second address is received via the second registration.
20. The method of claim 15, further comprising requesting the second address of the application server during an establishment of a package data unit (PDU) session.
PCT/US2020/059484 2019-11-07 2020-11-06 Address change notification associated with edge computing networks WO2021092441A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962932193P 2019-11-07 2019-11-07
US62/932,193 2019-11-07

Publications (1)

Publication Number Publication Date
WO2021092441A1 true WO2021092441A1 (en) 2021-05-14

Family

ID=73646566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2020/059484 WO2021092441A1 (en) 2019-11-07 2020-11-06 Address change notification associated with edge computing networks

Country Status (1)

Country Link
WO (1) WO2021092441A1 (en)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556727A (en) * 2021-07-19 2021-10-26 中国联合网络通信集团有限公司 Data transmission method and system of cloud equipment based on mobile container
CN113572835A (en) * 2021-07-21 2021-10-29 腾讯科技（深圳）有限公司 Data processing method, network element equipment and readable storage medium
CN114513509A (en) * 2022-01-04 2022-05-17 烽火通信科技股份有限公司 Wi-sun network data acquisition method and device based on MQTT
CN115396487A (en) * 2021-05-25 2022-11-25 维沃移动通信有限公司 Server address processing method and device
WO2023016280A1 (en) * 2021-08-09 2023-02-16 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for edge application service
US11652895B1 (en) * 2022-02-15 2023-05-16 Oracle International Corporation Methods, systems, and computer readable media for dynamic optimized network function discovery for consumer network functions
WO2023104070A1 (en) * 2021-12-10 2023-06-15 华为技术有限公司 Method and apparatus for selecting edge application server
CN113825172B (en) * 2021-07-30 2023-08-18 西安理工大学 Multi-unmanned aerial vehicle network load balancing method based on diffusion type deployment algorithm
WO2023192216A1 (en) * 2022-03-28 2023-10-05 Interdigital Patent Holdings, Inc. Personal internet of things network element identifier configuration
US11871309B2 (en) 2021-09-28 2024-01-09 Oracle International Corporation Methods, systems, and computer readable media for network function discovery using preferred-locality information
CN117395744A (en) * 2023-12-11 2024-01-12 广东海洋大学 Communication method and device, equipment and storage medium
US11888946B2 (en) 2021-06-02 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests
US11888957B2 (en) 2021-12-07 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing
US11930083B2 (en) 2021-08-09 2024-03-12 Oracle International Corporation Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019118964A1 (en) * 2017-12-15 2019-06-20 Idac Holdings, Inc. Enhanced nef function, mec and 5g integration
WO2019139903A1 (en) * 2018-01-12 2019-07-18 Idac Holdings, Inc. Methods for protocol enhancements in 5g nas
WO2019194954A1 (en) * 2018-04-06 2019-10-10 Convida Wireless, Llc Methods of managing connections to a local area data network (ladn) in a 5g network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019118964A1 (en) * 2017-12-15 2019-06-20 Idac Holdings, Inc. Enhanced nef function, mec and 5g integration
WO2019139903A1 (en) * 2018-01-12 2019-07-18 Idac Holdings, Inc. Methods for protocol enhancements in 5g nas
WO2019194954A1 (en) * 2018-04-06 2019-10-10 Convida Wireless, Llc Methods of managing connections to a local area data network (ladn) in a 5g network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Multi-access Edge Computing (MEC); Device application interface", vol. ISG MEC Multi-access Edge Computing, no. V2.1.2, 22 October 2019 (2019-10-22), pages 1 - 23, XP014352370, Retrieved from the Internet <URL:docbox.etsi.org/ISG/MEC/70-Draft/0016v221UEAppInterface/MEC-0016v221UEAppInterfacev212/gs_MEC016v212_clean.docx> [retrieved on 20191022] *

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115396487A (en) * 2021-05-25 2022-11-25 维沃移动通信有限公司 Server address processing method and device
US11888946B2 (en) 2021-06-02 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests
CN113556727B (en) * 2021-07-19 2022-08-23 中国联合网络通信集团有限公司 Data transmission method and system of cloud equipment based on mobile container
CN113556727A (en) * 2021-07-19 2021-10-26 中国联合网络通信集团有限公司 Data transmission method and system of cloud equipment based on mobile container
CN113572835A (en) * 2021-07-21 2021-10-29 腾讯科技（深圳）有限公司 Data processing method, network element equipment and readable storage medium
CN113572835B (en) * 2021-07-21 2024-02-27 腾讯科技（深圳）有限公司 Data processing method, network element equipment and readable storage medium
CN113825172B (en) * 2021-07-30 2023-08-18 西安理工大学 Multi-unmanned aerial vehicle network load balancing method based on diffusion type deployment algorithm
US11930083B2 (en) 2021-08-09 2024-03-12 Oracle International Corporation Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations
WO2023016280A1 (en) * 2021-08-09 2023-02-16 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for edge application service
US11871309B2 (en) 2021-09-28 2024-01-09 Oracle International Corporation Methods, systems, and computer readable media for network function discovery using preferred-locality information
US11888957B2 (en) 2021-12-07 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing
WO2023104070A1 (en) * 2021-12-10 2023-06-15 华为技术有限公司 Method and apparatus for selecting edge application server
CN114513509B (en) * 2022-01-04 2023-05-16 烽火通信科技股份有限公司 MQTT-based wi-sun network data acquisition method and device
CN114513509A (en) * 2022-01-04 2022-05-17 烽火通信科技股份有限公司 Wi-sun network data acquisition method and device based on MQTT
US11652895B1 (en) * 2022-02-15 2023-05-16 Oracle International Corporation Methods, systems, and computer readable media for dynamic optimized network function discovery for consumer network functions
WO2023192216A1 (en) * 2022-03-28 2023-10-05 Interdigital Patent Holdings, Inc. Personal internet of things network element identifier configuration
CN117395744A (en) * 2023-12-11 2024-01-12 广东海洋大学 Communication method and device, equipment and storage medium
CN117395744B (en) * 2023-12-11 2024-02-20 广东海洋大学 Communication method and device, equipment and storage medium

Similar Documents

Publication Publication Date Title
WO2021092441A1 (en) Address change notification associated with edge computing networks
US11765126B2 (en) Methods, apparatus, and system for edge resolution function
US20240089727A1 (en) Terminal requesting network slice capabilities from non-3gpp access network
KR20220164073A (en) User plane relocation
US20230209621A1 (en) Methods, architectures, apparatuses and systems for discovery, selection and optimal access to edge computing networks
WO2021163507A1 (en) Security and privacy support for direct wireless communications
US20230413212A1 (en) User equipment/wireless transmit/receive unit-provided data networks on wtrus
EP4133790A1 (en) Methods, apparatuses and systems directed to a change of wtru to wtru relay
WO2022271957A1 (en) Discovery of internet of things network
EP4154594A1 (en) Method of wtru to network relay handover
US20230308985A1 (en) Methods and devices for handling virtual domains
US20230379985A1 (en) Methods, apparatuses and systems directed to provisioning domain support in 5g networks
KR20230048387A (en) Method and Apparatus for Discovery and Selection of Local NEFs
WO2024035879A1 (en) Service continuity associated with inter pine communication changes from direct mode to using intermediate pegc
WO2023219828A1 (en) Switching a service from a wtru to a pin and a pin to a wtru
WO2023192146A1 (en) Route selection in a wireless communication system
WO2023150371A1 (en) Ecs discovery associated with roaming
EP4335125A1 (en) Multicast and broadcast service transmission for a remote wtru via a relay wtru
WO2023147049A1 (en) Personal internet of things network connectivity
WO2024039843A1 (en) Wireless local area network (wlan) selection policy
WO2022216587A1 (en) Methods, architectures, apparatuses and systems for unifying edge configuration server provisioning
WO2023059612A1 (en) Customer premises network access control
WO2023014559A1 (en) Onboarding and remote provising for standalone non-public network (snpn)
WO2022125855A1 (en) Methods, architectures, apparatuses and systems for fqdn resolution and communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20816813

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20816813

Country of ref document: EP

Kind code of ref document: A1