Edge service configuration

Abstract

To provide a method for notifying monitoring reports from an access and mobility management function (AMF) or other network functions (NFs) in a centralized core network by an application function (AF) from user equipment (EP), without waiting for AF actions or commands, such as monitoring of quality of service.SOLUTION: UE includes a processor, communication circuitry connected to a network, and a memory. The processor performs such that the UE receives a monitoring report from an AMF, sends an UP message indicating that the monitoring report can be sent to an AF to user plane functions (UPFs), receives, from the AMF, a non-access layer (NAS) message including the monitoring report and information to send the monitoring report to the AF, and sends, to the AF, information including the monitoring report using a protocol data unit (PDU) session.SELECTED DRAWING: Figure 12

Description

Technical Field

[0001] (Cross - reference to related applications) This application claims the benefit of U.S. Patent Application No. 62 / 955,506, filed on December 31, 2019, and U.S. Patent Application No. 63 / 018,582, filed on May 1, 2020, both entitled "Edge Services Configuration", the contents of which are hereby incorporated by reference in their entirety.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities, including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced standards, and New Radio (NR), also known as "5G." Development of 3GPP NR standards is expected to continue and include the definition of next-generation radio access technology (New RAT), which is expected to include the provision of new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to consist of new non-backward compatible radio access in the new spectrum below 7 GHz and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with branching requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra, for example, providing opportunities for ultra-mobile broadband access for indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with flexible wireless access below 7 GHz, utilizing centimeter-wave and millimeter-wave specific design optimizations.

[0003] 3GPP identifies the various use cases that NR is expected to support, resulting in a wide range of user experience requirements for data transfer speed, latency, and mobility. Use cases include the following common categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communications (mMTC), network operations (e.g., network slicing, routing, migration, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications, which may include any of the following: vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and vehicle-to-everything communication with other entities. Specific services and applications within these categories include, to name a few, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first-person connectivity, automotive e-calls, disaster alerts, real-time gaming, multi-person video conferencing, autonomous driving, augmented reality, haptic internet, virtual reality, home automation, robotics, and aerial drones. All of these use cases are contemplated herein. [Overview of the Initiative]

[0004] The embodiments disclosed herein describe a method that enables an external AF / AS to provide information to the 5GC regarding edge data network configuration. Further embodiments disclosed herein describe mechanisms for UE provisioning to enable edge services, such as 1) a mechanism that enables a UE that does not host an EEC to request provisioning of EDN information in order to enable application clients that are not aware of the edge to use edge services, and such a mechanism may be based on a UE registration procedure, as well as provisioning and using URSP rules; 2) a mechanism that enables an EEC hosted by a UE to obtain edge configuration information by using URSP rules to establish IP connectivity with a configuration server; and 3) a mechanism that enables an EEC hosted by a UE to obtain edge data network configuration information during registration.

[0005] Additional aspects disclosed herein describe methods for enabling low-latency network information exposure at the edge, such as 1) a mechanism that enables an AF to subscribe to event monitoring exposure via an NEF and request a preference for reporting optimized (e.g., low latency) or delivery via a UE; 2) a mechanism that enables subscriptions and policies from a centralized NF to be delivered via a UE to edge or local deployments along the UE's path; and 3) a mechanism that enables low-latency event monitoring exposure from a centralized NF to edge servers via a UE. [Brief explanation of the drawing]

[0006] A more detailed understanding can be obtained from the following explanation, along with the attached diagrams as examples. [Figure 1A] An example communication system is provided. [Figure 1B] This is an exemplary system diagram of the RAN and core network. [Figure 1C]This is an exemplary system diagram of the RAN and core network. [Figure 1D] This is an exemplary system diagram of the RAN and core network. [Figure 1E] Let's look at another example of a communication system. [Figure 1F] This is a block diagram of an exemplary device or apparatus, such as a WTRU. [Figure 1G] This is a block diagram of an exemplary computing system. [Figure 2] This example illustrates the use of edge and cloud V2X application servers via V2X AC on the Unreal Engine (UE). [Figure 3] This document provides an example of a 3GPP-defined architecture for enabling edge applications. (See 3GPP TR 23.758, a study on application architectures for enabling edge applications v1.0.0 (2019-09)). [Figure 4A] This shows an example call flow for an enhanced registration procedure (no EEC examples). [Figure 4B] This shows an example call flow for an enhanced registration procedure (no EEC examples). [Figure 4C] This shows an example call flow for an enhanced registration procedure (no EEC examples). [Figure 5A] This shows an exemplary call flow for establishing a PDU session for an enhanced UE request. [Figure 5B] This shows an exemplary call flow for establishing a PDU session for an enhanced UE request. [Figure 6A] This shows an example call flow for an enhanced registration procedure (EEC-based example). [Figure 6B] This shows an example call flow for an enhanced registration procedure (EEC-based example). [Figure 7] This is a system diagram of an exemplary core network architecture with networking capabilities. [Figure 8] This is an exemplary example of an unoptimized network exposure reporting path for edge deployment. [Figure 9] This is an example of an optimized reporting path from a centralized network function. [Figure 10] This is an example call flow for forwarding edge reporting joins from a centralized network exposure function. [Figure 11] This is an example of a routing / delivery call flow for an edge monitoring policy via UE. [Figure 12] This is an example call flow for reporting routing from a centralized NF via a UE. [Figure 13A] This illustrates an exemplary call flow for an enhanced registration procedure that allows the UE to communicate its support for routing monitoring reports. [Figure 13B] This illustrates an exemplary call flow for an enhanced registration procedure that allows the UE to communicate its support for routing monitoring reports. [Figure 13C] This illustrates an exemplary call flow for an enhanced registration procedure that allows the UE to communicate its support for routing monitoring reports. [Figure 13D] This illustrates an exemplary call flow for an enhanced registration procedure that allows the UE to communicate its support for routing monitoring reports. [Figure 13E] This illustrates an exemplary call flow for an enhanced registration procedure that allows the UE to communicate its support for routing monitoring reports. [Figure 14] This illustrates an example of an optimized reporting path from a locally deployed NF. [Modes for carrying out the invention]

[0007] FIG. 1A illustrates an exemplary communication system 100 in which the systems, methods, and apparatuses described and claimed herein may be used. The communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g, which may be referred to generally or collectively as WTRU 102 or multiple WTRUs 102. The communication system 100 may include radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. The network services 113 may include, for example, V2X servers, V2X functions, ProSe servers, ProSe functions, IoT services, video streaming, and / or edge computing, among others.

[0008] It will be understood that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, and / or network elements. Each WTRU 102 may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. In the example in Figure 1A, each WTRU 102 is illustrated in Figures 1A to 1E as a handheld wireless communication device. In the wide variety of use cases intended for wireless communication, each WTRU may include, or may include, any type of device or apparatus configured to transmit and / or receive wireless signals, including, but are not limited to, user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptop computers, tablets, netbooks, notebooks, personal computers, wireless sensors, household electrical appliances, wearable devices such as smartwatches or smart clothing, medical or e-health devices, robots, industrial equipment, drones, vehicles such as automobiles, buses or trucks, or airplanes.

[0009] The communication system 100 may also include base stations 114a and 114b. In the example of FIG. 1A, each of the base stations 114a and 114b is illustrated as a single element. In reality, the base stations 114a and 114b may include any number of interconnected base stations and / or network elements. The base station 114a is any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks such as the core network 106 / 107 / 109, the Internet 110, the network service 113, and / or other networks 112. Similarly, the base station 114b is any type of device configured to interface, either wired and / or wirelessly, with at least one of the remote radio heads (RRHs) 118a, 118b, the transmission and reception points (TRPs) 119a, 119b, and / or the roadside units (RSUs) 120a and 120b to facilitate access to one or more communication networks such as the core network 106 / 107 / 109, the Internet 110, other networks 112, and / or the network server 113. The RRHs 118a, 118b are any type of device configured to wirelessly interface with at least one of the WTRUs 102, e.g., the WTRU 102c, to facilitate access to one or more communication networks such as the core network 106 / 107 / 109, the Internet 110, the network service 113, and / or other networks 112.

[0010] TRP119a, 119b may be any type of device configured to wirelessly interface with at least one of WTRU102d to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, network services 113, and / or other networks 112. RSU120a, 120b may be any type of device configured to wirelessly interface with at least one of WTRU102e or 102f to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or network services 113. For example, base stations 114a, 114b may be base transceiver stations (BTS), Node B, eNode B, home Node B, home eNode B, Next Generation Node-B (gNode B), satellites, site controllers, access points (AP), wireless routers, etc.

[0011] Base station 114a may be part of RAN 103 / 104 / 105, 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), and relay nodes. Similarly, base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as a BSC, RNC, and relay nodes. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographic area, which may be referred to as a cell (not shown). Similarly, base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographic area, which may also be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, for example, base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. The base station 114a may use Multiple-Input Multiple Output (MIMO) technology, and therefore, for example, may utilize multiple transceivers for each sector of a cell.

[0012] Base station 114a may communicate with one or more WTRUs 102a, 102b, 102c, and 102g via air interfaces 115 / 116 / 117, which may be any suitable radio communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Air interfaces 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0013] Base station 114b may communicate with one or more of the RRH 118a and 118b, TRP 119a and 119b, and / or RSU 120a and 120b via wired or air interfaces 115b / 116b / 117b, which may be any suitable wired (e.g., cable, optical fiber, etc.) or radio communication link (e.g., RF, microwave, IR, UV, visible light, centimeter wave, millimeter wave, etc.). Air interfaces 115b / 116b / 117b may be established using any suitable RAT.

[0014] RRH118a, 118b, TRP119a, 119b, and / or RSU120a, 120b may communicate with one or more WTRU102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which may be any suitable radio communication link (e.g., RF, microwave, IR, ultraviolet UV, visible light, centimeter wave, millimeter wave, etc.). Air interface 115c / 116c / 117c may be established using any suitable RAT.

[0015] The WTRU102s can communicate with each other via direct air interfaces 115d / 116d / 117d, such as sidelink communication, which may be any suitable wireless communication link (e.g., RF, microwave, IR, ultraviolet UV, visible light, centimeter wave, millimeter wave, etc.). The air interfaces 115d / 116d / 117d may be established using any suitable RAT.

[0016] The communication system 100 may be a multi-access system and may use one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA. For example, base stations 114a in RAN103 / 104 / 105, and WTRU102a, 102b, 102c, or RRH118a, 118b, TRP119a, 119b, and / or RSU120a, 120b, and WTRU102c, 102d, 102e, and 102f in RAN103b / 104b / 105b may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) and Terrestrial Radio Access (UTRA), which may establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Advanced HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0017] Base stations 114a in RAN103 / 104 / 105, and WTRU102a, 102b, 102c, and 102g, or RRH118a and 118b, TRP119a and 119b, and / or RSU120b and 120b, and WTRU102c and 102d in RAN103b / 104b / 105b, may implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively, using, for example, Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A). Air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technology may include LTE D2D and / or V2X technology, as well as interfaces (such as sidelink communication). Similarly, 3GPP NR technology may include NR V2X technology, as well as interfaces (such as sidelink communication).

[0018] Base stations 114a in RAN103 / 104 / 105, and WTRU102a, 102b, 102c, and 102g, or RRH118a and 118b, TRP119a and 119b, and / or RSU120a and 120b, and WTRU102c, 102d, 102e, and 102f in RAN103b / 104b / 105b, are IEEE 802.16 (e.g., WiMAX (Worldwide Interoperability for Microwave Access), CDMA2000, CDMA2000 1x, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Telephone). Wireless technologies such as GSM communications, Enhanced Data rates for GSM Evolution (EDGE), and GSM EDGE (GERAN) can be implemented.

[0019] The base station 114c in Figure 1A may be, for example, a wireless router, home node B, home eNode B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in local areas such as offices, homes, vehicles, trains, airborne, satellite, factories, and campuses. The base station 114c and WTRU102, for example WTRU102e, can implement wireless technologies such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). Similarly, the base station 114c and WTRU102, for example WTRU102d, can implement wireless technologies such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). The base station 114c and WTRU102, for example WTRU102e, can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish picocells or femtocells. As shown in Figure 1A, base station 114c may have a direct connection to the internet 110. Therefore, base station 114c may not need to access the internet 110 via the core network 106 / 107 / 109.

[0020] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b may communicate with core networks 106 / 107 / 109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, and / or Voice Over Internet Protocol (VoIP) services to one or more of WTRU102. For example, core networks 106 / 107 / 109 may provide call control, billing services, mobile location-based services, prepaid calling, internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication.

[0021] Although not shown in Figure 1A, it will be understood that RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b and / or core networks 106 / 107 / 109 may communicate directly or indirectly with other RANs employing the same RAT as RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b, or different RATs. For example, in addition to connecting to RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b, which may utilize E-UTRA radio technology, core networks 106 / 107 / 109 may also communicate with other RANs (not shown) using GSM or NR radio technology.

[0022] Core networks 106 / 107 / 109 may also function as gateways for WTRU 102 to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include circuit-switched telephone networks providing Plain Old Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP / IP Internet Protocol suite. Other networks 112 may include wired and / or wireless networks owned and / or operated by other service providers. For example, network 112 may include any type of packet data network (e.g., an IEEE 802.3 Ethernet network) or another core network connected to one or more RANs, which may employ the same RAT as RAN 103 / 104 / 105 and / or a different RAT than RAN 103b / 104b / 105b.

[0023] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multimode capability, for example, WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different radio networks over different radio links. For example, WTRU 102g shown in Figure 1A may be configured to communicate with base station 114a which may use cellular-based radio technology and base station 114c which may use IEEE 802 radio technology.

[0024] Although not shown in Figure 1A, it will be understood that user equipment may have a wired connection to the gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. It will be understood that many of the ideas contained herein can be equally applied to UEs, which are WTRUs and UEs that use wired connections to connect to the network. For example, ideas that apply to wireless interfaces 115, 116, 117, and 115c / 116c / 117c can be equally applied to wired connections.

[0025] Figure 1B is a system diagram of an exemplary RAN103 and core network 106. As described above, RAN103 can communicate with WTRU102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN103 can also communicate with core network 106. As shown in Figure 1B, RAN103 may include nodes B140a, 140b, and 140c, each of which may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via air interface 115. Nodes B140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN103. RAN103 may also include RNC142a, 142b. It will be understood that RAN103 may include any number of node B and radio network controllers (RNCs).

[0026] As shown in Figure 1B, nodes B140a and B140b can communicate with RNC142a. Furthermore, node B140c can communicate with RNC142b. Nodes B140a, B140b, and B140c can communicate with their respective RNC142a and B142b via the Iub interface. RNC142a and B142b can communicate with each other via the Iur interface. Each of RNC142a and B142b may be configured to control their respective nodes B140a, B140b, and B140c to which it is connected. In addition, each of RNC142a and B142b may be configured to perform or support other functions such as external loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, and data encryption.

[0027] The core network 106 shown in Figure 1B may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the aforementioned elements is illustrated as part of the core network 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0028] RNC142a in RAN103 may be connected to MSC146 in core network 106 via IuCS interface. MSC146 may be connected to MGW144. MSC146 and MGW144 may provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as PSTN108 to facilitate communication between WTRU102a, 102b, and 102c and conventional terrestrial line communication devices.

[0029] RNC142a within RAN103 may also be connected to SGSN148 in core network 106 via an IuPS interface. SGSN148 may be connected to GGSN150. SGSN148 and GGSN150 may provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0030] The core network 106 may also be connected to other networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0031] Figure 1C is a system diagram of an exemplary RAN 104 and core network 107. As described above, RAN 104 can communicate with WTRU 102a, 102b, and 102c via the air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0032] RAN104 may include eNode-B160a, 160b, and 160c, but it will be understood that RAN104 may include any number of eNode-B. Each of eNode-B160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. For example, eNode-B160a, 160b, and 160c may implement MIMO technology. Thus, eNode-B160a can, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU102a.

[0033] Each of the eNode-B160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling, etc., on the uplink and / or downlink. As shown in Figure 1C, the eNode-B160a, 160b, and 160c may communicate with each other via the X2 interface.

[0034] The core network 107 shown in Figure 1C may include a Mobility Management Gateway (MME) 162, a Serving Gateway 164, and a Packet Data Network (PDN) Gateway 166. Although each of the aforementioned elements is illustrated as part of the core network 107, it will be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0035] The MME162 can be connected to each of the eNode-B160a, 160b, and 160c within RAN104 via the S1 interface and can function as a control node. For example, the MME162 may perform roles such as authenticating users for WTRU102a, 102b, and 102c, bearer activation / deactivation, and selecting a specific serving gateway during the initial attachment of WTRU102a, 102b, and 102c. The MME162 may also provide control plane functionality for exchanges between RAN104 and other RANs (not shown) using other radio technologies such as GSM or WCDMA.

[0036] The serving gateway 164 may be connected to each of the eNode-B 160a, 160b, and 160c in RAN 104 via the S1 interface. The serving gateway 164 can generally route and forward user data packets to and from WTRU 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during eNode B handover, triggering paging when downlink data is available to WTRU 102a, 102b, and 102c, and managing and remembering the context of WTRU 102a, 102b, and 102c.

[0037] The serving gateway 164 may also be connected to a PDN gateway 166, which can provide WTRUs 102a, 102b, and 102c with access to a packet-switched network, such as the Internet 110, thereby facilitating communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0038] The core network 107 can facilitate communication with other networks. For example, the core network 107 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108, thereby facilitating communication between WTRU 102a, 102b, and 102c and conventional fixed-line communication devices. For example, the core network 107 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and PSTN 108. In addition, the core network 107 may provide WTRU 102a, 102b, and 102c with access to network 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0039] Figure 1D is a system diagram of an exemplary RAN 105 and core network 109. RAN 105 can communicate with WTRU 102a and 102b via air interface 117 using NR radio technology. RAN 105 can also communicate with core network 109. Non-3GPP Interworking Function (N3IWF) 199 can communicate with WTRU 102c via air interface 198 using non-3GPP radio technology. N3IWF 199 can also communicate with core network 109.

[0040] RAN105 may include gNode-B180a and 180b. It will be understood that RAN105 may include any number of gNode-B. Each of gNode-B180a and 180b may include one or more transceivers for communicating with WTRU102a and 102b via air interface 117. When integrated access and backhaul connectivity is used, the same air interface may be used between the WTRU and the gNode-B, and this air interface may be a core network 109 via one or more gNBs. gNode-B180a and 180b may implement MIMO, MU-MIMO, and / or digital beamforming technologies. Thus, gNode-B180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU102a. It should be understood that RAN105 may use other types of base stations, such as eNode-B. It should also be understood that RAN105 may employ two or more types of base stations. For example, RAN may use eNode-B and gNode-B.

[0041] N3IWF199 may include non-3GPP access points 180c. It will be understood that N3IWF199 may include any number of non-3GPP access points. Non-3GPP access points 180c may include one or more transceivers for communicating with WTRU102c via air interface 198. Non-3GPP access points 180c may communicate with WTRU102c via air interface 198 using the 802.11 protocol.

[0042] Each of the eNode-B180a and 180b may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling, etc., on the uplink and / or downlink. As shown in Figure 1D, the gNode-B180a and 180b may communicate with each other, for example, via the Xn interface.

[0043] The core network 109 shown in Figure 1D may be a 5G core network (5GC). The core network 109 may provide numerous communication services to customers interconnected by a radio access network. The core network 109 includes several entities that perform the functionality of the core network. As used herein, the terms “core network entity” or “network function” refer to any entity that performs one or more functions of the core network. Such core network entities may be devices configured for radio and / or network communications, or logical entities implemented in the form of computer executable instructions (software) stored in the memory of a computer system such as system 90 illustrated in Figure 1G and executed on its processors.

[0044] In the example in Figure 1D, the 5G core network 109 may include an access and mobility management function (AMF) 172, a session management function (SMF) 174, user plane functions (UPF) 176a and 176b, a user data management function (UDM) 197, an authentication server function (AUSF) 190, a network exposure function (NEF) 196, a policy control function (PCF) 184, a non-3GPP interworking function (N3IWF) 199, and a user data repository (UDR) 178. Although each of the aforementioned elements is illustrated as part of the 5G core network 109, it should be understood that any of these elements may be owned and / or operated by entities other than the core network operator. Furthermore, it should be understood that a 5G core network may not consist of all of these elements, but may consist of additional elements, and may consist of multiple examples of each of these elements. Figure 1D shows network functions directly connected to each other, but it should be understood that they may communicate via routing agents such as a diameter routing agent or a message bus.

[0045] In the example in Figure 1D, connectivity between network functions is achieved through a set of interfaces or reference points. It will be understood that network functions can be modeled, described, or implemented as a set of services that are invoked or called by other network functions or services. Invocation of network function services can be achieved through direct connections between network functions, messaging exchanges on a message bus, software function invocations, and so on.

[0046] AMF172 can be connected to RAN105 via the N2 interface and can function as a control node. For example, AMF172 can perform registration management, connection management, reachability management, access authentication, and access authorization roles. AMF can forward user plane tunnel configuration information to RAN105 via the N2 interface. AMF172 can receive user plane tunnel configuration information from SMF via the N11 interface. Generally, AMF172 can route and forward NAS packets to and from WTRU102a, 102b, and 102c via the N1 interface. The N1 interface is not shown in Figure 1D.

[0047] SMF174 can be connected to AMF172 via the N11 interface. Similarly, SMF can be connected to PCF184 via the N7 interface and to UPF176a and 176b via the N4 interface. SMF174 can function as a control node. For example, SMF174 may be responsible for session management, IP address assignment for WTRU102a, 102b, and 102c, management and configuration of traffic steering rules in UPF176a and UPF176b, and generation of downlink data notifications to AMF172.

[0048] UPF176a and UPF176b may provide WTRU102a, 102b, and 102c with access to a packet data network (PDN), such as the Internet 110, to facilitate communication between WTRU102a, 102b, and 102c and other devices. UPF176a and UPF176b may also provide WTRU102a, 102b, and 102c with access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or any type of network that exchanges data packets. UPF176a and UPF176b may receive traffic steering rules from SMF174 via the N4 interface. UPF176a and UPF176b may provide access to a packet data network by connecting it to the N6 interface or by connecting it to each other or to other UPFs via the N9 interface. In addition to providing access to the packet data network, UPF176 can play a role in packet routing and forwarding, enforcement of policy rules, quality of service for user plane traffic, and downlink packet buffering.

[0049] AMF172 can also be connected to N3IWF199, for example, via the N2 interface. N3IWF facilitates connectivity between WTRU102c and the 5G core network 170, for example, via radio interface technology not defined by 3GPP. AMF can interact with N3IWF199 in the same or similar manner as it interacts with RAN105.

[0050] PCF184 may be connected to SMF174 via the N7 interface, to AMF172 via the N15 interface, and to Application Function (AF) 188 via the N5 interface. The N15 and N5 interfaces are not shown in Figure 1D. PCF184 may also provide policy rules to control plane nodes such as AMF172 and SMF174, enabling the control plane nodes to enforce these rules. PCF184 may send policies to AMF172 for WTRU102a, 102b, and 102c so that AMF can deliver the policies to WTRU102a, 102b, and 102c via the N1 interface. The policies can then be enforced or applied in WTRU102a, 102b, and 102c.

[0051] UDR178 can function as a repository for authentication certificates and membership information. UDR may connect to network functions, which can then append to, read, and modify data in the repository. For example, UDR178 may connect to PCF184 via the N36 interface. Similarly, UDR178 may connect to NEF196 via the N37 interface, and UDR178 may connect to UDM197 via the N35 interface.

[0052] UDM197 can function as an interface between UDR178 and other network functions. UDM197 can authorize network functions for access to UDR178. For example, UDM197 may connect to AMF172 via the N8 interface, or to SMF174 via the N10 interface. Similarly, UDM197 may connect to AUSF190 via the N13 interface. UDR178 and UDM197 may be tightly integrated.

[0053] The AUSF190 performs authentication-related operations and connects to the UDM178 via the N13 interface and to the AMF172 via the N12 interface.

[0054] NEF196 exposes the capabilities and services of the 5G core network 109 to the application function (AF) 188. Exposure may occur via the N33 API interface. The NEF may connect to AF188 via the N33 interface, or it may connect to other network functions to expose the capabilities and services of the 5G core network 109.

[0055] The application function 188 may interact with network functions within the 5G core network 109. The interaction between the application function 188 and the network functions may occur via a direct interface or via the NEF 196. The application function 188 may be considered part of the 5G core network 109, or it may be outside the 5G core network 109 and deployed by a company that has a business relationship with a mobile network operator.

[0056] Network slicing is a mechanism that mobile network operators can use to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types running across a single RAN. Network slicing allows operators to create customized networks that provide optimized solutions for different market scenarios requiring diverse requirements, for example, in the areas of functionality, performance, and isolation.

[0057] 3GPP is designing the 5G core network to support network slicing. Network slicing is a good tool that network operators can use to support a diverse set of 5G use cases (e.g., large-scale IoT, critical communications, V2X, and enhanced mobile broadband) that require highly varied and sometimes extreme requirements. Without using network slicing technology, the network architecture is likely to lack sufficient flexibility and scalability to efficiently support a wider range of use cases, as each use case has its own specific set of performance, scalability, and availability requirements. Furthermore, it should make the deployment of new network services more efficient.

[0058] Referring again to Figure 1D, in the network slicing scenario, WTRU102a, 102b, or 102c may be connected to AMF172 via the N1 interface. The AMF may be logically part of one or more slices. The AMF may coordinate the connection or communication of WTRU102a, 102b, or 102c to one or more UPF176a and 176b, SMF174, and other network functions. Each of the UPF176a and 176b, SMF174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may have different computing resources, security certificates, etc.

[0059] The core network 109 may facilitate communication with other networks. For example, the core network 109 may include, or communicate with, an IP gateway such as an IP Multimedia Subsystem (IMS) server that functions as an interface between the 5G core network 109 and the PSTN 108. For example, the core network 109 may include, or communicate with, a Short Message Service (SMS) service center that facilitates communication via the Short Message Service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between WTRUs 102a, 102b, and 102c and the server or application function 188. In addition, the core network 170 may provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0060] The core network entities described herein and illustrated in Figures 1A, 1C, 1D, and 1E are identified by the names given to them in certain existing 3GPP specifications, but future entities and functions may be identified by other names, and it is understood that certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Accordingly, it is understood that the specific network entities and functions described and illustrated in Figures 1A, 1B, 1C, 1D, and 1E are provided as examples only, and the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or hereafter defined.

[0061] Figure 1E illustrates an exemplary communication system 111 in which the systems, methods, and apparatus described herein may be used. The communication system 111 may include radio transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein may apply to any number of WTRUs, base station gNBs, V2X networks, and / or other network elements. One or more, or all, WTRUs A, B, C, D, E, and F may be outside the scope of access network coverage 131. WTRUs A, B, and C form a V2X group, where WTRU A is the group lead and WTRUs B and C are group members.

[0062] WTRUs A, B, C, D, E, and F can communicate with each other via the Uu interface 129 through the gNB 121 if they are within access network coverage 131. In the example in Figure 1E, WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may also communicate directly with each other via sidelink interfaces such as interfaces 125a, 125b, or 128 (e.g., PC5 or NR PC5), regardless of whether they are under or outside access network coverage 131. For example, in the example in Figure 1E, WTRU D, which is outside access network coverage 131, communicates with WTRU F, which is within coverage 131.

[0063] WTRUs A, B, C, D, E, and F may communicate with RSU 123a or 123b via vehicle-to-network communication (V2N) 133 or side-link interface 125b. WTRUs A, B, C, D, E, and F may communicate with V2X server 124 via vehicle-to-infrastructure communication (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate with another UE via vehicle-to-human communication (V2P) interface 128.

[0064] Figure 1F is a block diagram of an exemplary apparatus or device WTRU102 that may be configured for wireless communication and operation by the systems, methods, and apparatus described herein, such as WTRU102 in Figures 1A, 1B, 1C, 1D, or 1E. As shown in Figure 1F, the exemplary WTRU102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be understood that WTRU102 may include any quadratic combination of the aforementioned elements. Furthermore, base stations 114a and 114b, and / or base stations 114a and 114b, may also represent, but are not limited to, transceiver stations (BTS), nodes B, site controllers, access points (APs), home nodes B, evolved home nodes B (eNodeB), home evolved nodes B (HeNB), home evolved node B gateways, next-generation nodes B (gNode-B), and proxy nodes, and may include some or all of the elements shown in Figure 1F and described herein.

[0065] The processor 118 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal 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 a transceiver 120 which can be coupled to a transmit / receive element 122. Although Figure 1F illustrates the processor 118 and transceiver 120 as separate components, it will be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0066] The UE's transmit / receive element 122 may be configured to transmit a signal to or receive a signal from a base station (e.g., base station 114a in Figure 1A) via air interfaces 115 / 116 / 117, or to transmit a signal to or receive a signal from another UE via air interfaces 115d / 116d / 117d. For example, 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 optical signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of radio or wired signals.

[0067] In addition, although the transmit / receive element 122 is illustrated as a single element in Figure 1F, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may utilize MIMO technology. Therefore, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiplex antennas) for transmitting and receiving radio signals via the air interfaces 115 / 116 / 117.

[0068] The transceiver 120 may be configured to modulate the signal transmitted by the transmit / receive element 122 and demodulate the signal received by the transmit / receive element 122. As described above, the WTRU 102 may have multimode capability. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate over multiple RATs, e.g., NR and IEEE 802.11 or NR and E-UTRA, or to communicate with the same RAT over multiple beams to different RRHs, TRPs, RSUs, or nodes.

[0069] The processor 118 of the WTRU102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (for example, a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit) and may receive user input data from them. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicator 128. Furthermore, the processor 118 may access information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132, and store data in such memory. Non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, or a secure digital This may include digital (SD) memory cards, etc. The processor 118 may access information from memory that is not physically located on the WTRU 102, such as on a server hosted on a cloud or edge computing platform or a home computer (not shown), and store data in that memory.

[0070] The processor 118 may be configured to receive power from the power supply 134 and distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for supplying power to the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0071] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may determine its location by receiving location information from base stations (e.g., base stations 114a, 114b) via air interfaces 115 / 116 / 117 and / or based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by any preferred location determination method.

[0072] The processor 118 may be further 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 various sensors such as an accelerometer, a biometric (e.g., fingerprint) sensor, an electronic compass, a satellite transceiver, a digital camera (for photography or video), a universal serial bus (USB) port, or other interconnection interface, 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, or a video game player module.

[0073] WTRU102 may be included in sensors, household electrical appliances, wearable devices such as smartwatches or smart clothing, medical or e-health devices, robots, industrial equipment, drones, automobiles, trucks, trains or other vehicles, or other devices such as airplanes. WTRU102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as an interconnect interface which may include one of the peripheral devices 138.

[0074] Figure 1G is a block diagram of an exemplary computing system 90 in which one or more devices from the communication networks illustrated in Figures 1A, 1C, 1D, and 1E may be embodied, such as specific nodes or functional entities in RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, the Internet 110, other networks 112, or network services 113. The computing system 90 may include a computer or server and may be controlled primarily by computer-readable instructions, which may be in the form of software or by any means of storing or accessing such software. Such computer-readable instructions may be executed within a processor 91 to make the computing system 90 work. The processor 91 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to operate on a communication network. The coprocessor 81 is an optional processor distinct from the main processor 91, which may perform additional functions or assist the processor 91. The processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatus disclosed herein.

[0075] During operation, the processor 91 fetches, decodes, and executes instructions, and transmits information to other resources via the main data transfer path of the computing system, the system bus 80. Such a system bus connects the components within the computing system 90 and defines the medium for data exchange. The system bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0076] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. Such memory includes circuitry that enables information to be stored and retrieved. ROM 93 generally contains stored data that cannot be easily modified. Data stored in RAM 82 can be read or modified by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by the memory controller 92. The memory controller 92 can provide address translation functionality that translates virtual addresses to physical addresses when an instruction is executed. The memory controller 92 can also provide memory protection functionality that isolates processes within the system and separates system processes from user processes. Thus, a program running in the first mode can only access memory mapped by its own process virtual address space and cannot access memory in another process's virtual address space unless inter-process memory sharing is configured.

[0077] In addition, the computing system 90 may include a peripheral device controller 83 that plays a role in communicating commands from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0078] The display 86, controlled by the display controller 96, is used to display visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented as a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components necessary to generate the video signal transmitted to the display 86.

[0079] Furthermore, the computing system 90 may include communication circuits, such as a wireless or wired network adapter 97, which can be used to connect the computing system 90 to external communication networks or devices such as RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, the Internet 110, WTRU 102, or other networks 112 in Figures 1A, 1B, 1C, 1D, and 1E, enabling the computing system 90 to communicate with other nodes or functional entities in those networks. The communication circuits may be used alone or in combination with the processor 91 to perform the transmission and reception steps of specific devices, nodes, or functional entities described herein.

[0080] Any or all of the apparatus, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, and it is understood that when such instructions are executed by a processor, such as processor 118 or 91, the processor will cause the processor to execute and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer-executable instructions that are executed on a processor of an apparatus or computing system configured for wireless and / or wired network communication. Computer-readable storage mediums include volatile and non-volatile, removable and non-removable media for storing information, which are implemented by any non-temporary (e.g., tangible or physical) method or technique, but such computer-readable storage mediums do not contain signals. Computer-readable storage media include RAM, ROM, EEPROM, flash memory, or other memory technologies; CD-ROM, digital versatile disks (DVDs), or other optical disk storage; magnetic cassettes, magnetic tapes, magnetic disk storage devices, or other magnetic storage devices; or any other tangible or physical media that can be used to store desired information and can be accessed by a computing system.

[0081] The following is a list of acronyms that may appear in the following description. Unless otherwise specified, the acronyms used herein refer to the corresponding terms listed below.

[0082] 5GC 5G Core Network AF Application Function AMF Access Management Function API Application Programming Interface AS Application Server AC Application Client BS combination function CN Core Network DNN Data Network Name DNS Domain Name Server EAS Edge Application Server EDN (Edge Data Network) ECSP Edge Computing Service Provider EDNCS Edge Data Network Configuration Server EES Edge Enabler Server EEC Edge Enabler Client EHE Edge Hosting Environment EMRP Edge Monitoring Routing Policy FQDN (Fully Qualified Domain Name) GMLC Gateway Mobile Location Center GUI (Graphical User Interface) LADN Local Area Data Network NEF Network Exposure Function NF Network Function PDU Protocol Data Unit SMF session management function UDM (Unified Data Management) UE User Equipment UP User Plane Application Server - An entity deployed on a network node that provides services to application clients.

[0083] Application client - An entity that accesses the services of an application server.

[0084] Edge application server - A server that provides application services hosted on an edge node or edge hosting environment.

[0085] Edge node - A virtual or physical entity deployed within an edge network that hosts edge-based applications and services.

[0086] Edge data network – A local data network that supports the delivery deployment of an edge hosting environment. In this disclosure, the term edge data network may be used interchangeably with the term edge hosting environment. For example, a server described herein that resides within an edge data network runs in the corresponding edge hosting environment.

[0087] An edge enabler server is an entity deployed within an edge network that provides edge network-centric services to edge enabler clients and edge application servers. In some 3GPP specifications, edge enabler servers are not functionally distinguished from edge application servers, and the term "edge application server" can apply to both.

[0088] Edge Enabler Clients are deployed on devices that provide edge network-centric services to application clients hosted on those devices.

[0089] An edge data network configuration server is an entity within the network that constitutes edge enabler clients and edge enabler servers to enable services provided by the edge data network. An edge data network configuration server is sometimes also called an edge configuration server.

[0090] Edge hosting environment - An environment that provides the necessary support for running edge application servers.

[0091] Deploying edge applications.

[0092] The advantages of deploying Application Servers (AS) at the edge of the 3GPP system rather than in the cloud can include reduced access latency and increased reliability for Application Clients (ACs) accessing services provided by these ASs. In addition, network operators can also benefit from deploying ASs at the network edge because this deployment model can distribute the load and reduce network congestion levels (for example, by enabling local communication between ACs and ASs).

[0093] For example, Figure 2 illustrates a use case for an autonomous vehicle. The vehicle hosts a UE, and hosted on the UE is a V2X AC used by the vehicle's autonomous driving control system. The V2X AC communicates with V2X services deployed in a 3GPP system (e.g., platooning services, cooperative driving services, or collision avoidance services). V2X services can be deployed in a way that they are delivered throughout the system, as a combination of V2X AS deployed on edge nodes (e.g., roadside units or cell towers) and in the cloud.

[0094] For enhanced performance (e.g., reduced access latency and higher reliability), a preferred method for accessing V2X services via V2X AC may be via a V2X AS deployed in an edge network within the system, typically closer to the vehicle, rather than accessing a V2X AS via the cloud. When accessing a V2X AS at the edge, the V2X AC hosted on the UE in the vehicle may have access to more timely and reliable information about other vehicles, as well as road and traffic conditions. As a result, the vehicle can travel faster and closer to other vehicles. The vehicle may also be able to change lanes more frequently and effectively without sacrificing safety. In contrast, when accessing a V2X AS in the cloud, the vehicle may have to revert to a more conservative mode of operation due to the reduced availability of timely information. This can typically result in reduced vehicle speed, increased distance between the vehicle and other vehicles, and / or less-than-optimal lane changes.

[0095] When a vehicle travels along a roadway, V2X AC handovers between V2X ASs hosted on different edge nodes closest to the vehicle may need to be coordinated. Similarly, V2X AC handovers between V2X ASs hosted on edge nodes and V2X ASs hosted in the cloud may also need to be coordinated in case edge network coverage fades in and out during the vehicle's journey. In such scenarios, seamless (low-latency, reliable) V2X AC handovers between ASs hosted on both edge nodes and the cloud may be critical to the successful deployment of this type of V2X use case, as well as other types of use cases with similar requirements to V2X.

[0096] A 3GPP architecture to enable edge applications. Error! Reference not found. This shows a 3GPP-defined architecture for enabling edge applications. The framework for enabling edge applications may include edge enabler clients and application clients hosted on the UE, and edge enabler servers hosted on the edge data network. Edge enabler clients and edge enabler servers may be configured using an edge data network configuration server. Edge enabler clients and servers may provide edge-centric capabilities to application clients and servers, respectively. Edge enabler servers and edge data network configuration servers may also interact with 3GPP networks.

[0097] 3GPP architecture for network exposure. Figure 7 is a system diagram of the core network architecture with network functionality, as described below. The current network exposure mechanism in 5GS can be designed based on the NEF and other control planes NF, e.g., AMF, SMF, or PCF. The NEF (as described in 3GPP TS 23.501, System Architecture of 5G Systems, Stage 2, V16.3.0 (2019-12)) may include the following functionalities: • Secure exposure of capabilities and events for third parties, application functions, etc. NEF uses a standardized interface (Nudr) to store and retrieve information as structured data in a Unified Data Repository (UDR). • Secure provisioning of information from external applications to the 3GPP network. This provides a means for application functions to securely provide information to the 3GPP network, such as expected UE behavior, 5GLAN group information, or service-specific information. In this case, the NEF may authenticate, authorize, and assist in throttling the application functions. • Conversion of internal and external information. Conversion occurs between information exchanged with AF and information exchanged with internal network functions. For example, conversion may occur between AF service identifiers and internal 5G core information such as DNN or S-NSSAI. Specifically, the NEF processes network masking and user protection information to an external AF in accordance with network policies. The network exposure function receives information from other network functions (based on the exposure capabilities of those other network functions). The NEF stores the received information as structured data in the Unified Data Repository (UDR) using a standardized interface. The stored information can be accessed and "re-exposed" by the NEF to other network functions and application functions and used for other purposes such as analysis. The NEF can support packet flow description functionality by storing and retrieving PFDs within the UDR and providing the PFDs to the SMF in response to a request from the SMF (pull mode) or a request for PFD management from the NEF (push mode). • NEF may also support 5G LAN group management functionality. • Exposure to analysis. NWDAF analysis may be safely exposed by an external party's NEF as specified in TS 23.288. • Data retrieval from external parties by the NWDAF. Data provided by external parties may be collected by the NWDAF via the NEF for analytical generation purposes. The NEF processes and transfers requests and notifications between the NWDAF and the AF as specified in TS 23.288.

[0098] A particular NEF instance may support one or more of the functionalities described above, and as a result, an individual NEF may support a subset of the APIs designated for capability exposure. An NEF may have access to a UDR, which may be located in the same PLMN as the NEF. In the case of external exposure of a service related to a particular UE, the NEF may reside in an HPLMN. Depending on the operator's agreement, an NEF in an HPLMN may have an interface with an NF in a VPLMN.

[0099] Description of the problem. SA6 designs an edge computing application layer architecture. In this architecture, application clients on the UE can access services of edge enabler clients on the UE. Application clients on the UE can also communicate with edge application servers. Edge application servers may reside in the edge data network. Edge servers may interact with 5GS to access functionality and network-exposed information. Currently, exposure may be provided via a control plane NF, e.g., NEF or PCF, which is likely to be centrally deployed to avoid relocation. When an application client on the UE accesses an edge enabler client using SA6-defined procedures and APIs, it is said to be "edge-aware".

[0100] In the SA6 architecture, edge enabler clients can communicate with EDN configuration servers that may be hosted on the N6-LAN (i.e., the EDN configuration servers may not be deployed at the edge). Edge enabler clients can communicate with EDN configuration servers to obtain information such as which edge data networks or edge application servers are available at a given location. Therefore, edge enabler clients may need to obtain configuration information before they can establish communication with the EDN configuration servers and provide services to application clients. 3GPP does not define means for edge enabler clients to discover EDN configuration servers.

[0101] In other scenarios, application clients on the UE may not be "edge-aware." Therefore, for example, they may not communicate with edge enabler clients and may not adhere to the 3GPP application layer protocol.

[0102] In scenarios where an application client is not "edge-aware," but an application on the UE can use edge services, 3GPP does not define how the UE protocol stack can know where to send application data when edge computing becomes available. In other words, there is no way for the UE to independently (without application assistance) decide when to route data to the edge. For example, consider a case where a smartphone hosts an application that is not edge-aware. The smartphone may display a GUI that allows the user to indicate which application they want to enable edge computing for. If the application is not "edge-aware," there is no way for the UE protocol stack to enable edge computing for the indicated application.

[0103] When edge services rely on network exposure information (e.g., reports) from the NEF, long delays in reports traveling from the network to the edge server can cause the information to become outdated by the time it reaches the edge server. This, in turn, can lead to changes in application behavior (e.g., adjusting video stream resolution or switching the level of driving automation) based on the old network information. Therefore, one of the issues that needs to be addressed is how network exposure information (e.g., reports) can be delivered to the edge server in a more timely or optimized manner. If new and more efficient exposure mechanisms are defined, they should also include methods for 5G systems to determine which exposure mechanism to use, so that multiple mechanisms can coexist in the system. This issue is further discussed below and is shown in Figure 8.

[0104] Provisioning for enabling edge services The following assumptions or conventions may be used when describing provisioning for enabling edge services.

[0105] The UE may or may not be aware of the edge service.

[0106] An edge-aware UE can trigger explicit requests for services provided at the edge. Two methods may be available for implementing an edge-aware UE. The first form of implementing an edge-aware UE is by provisioning an edge enabler client hosted on the UE, which enables edge services to be combined with network entities such as edge enabler servers and edge enabler configuration servers, as described in the SA6 architecture. This disclosure uses SA6 scientific names for these entities, but it should be noted that non-SA6-based implementations with equivalent entities may be assumed. For example, the edge enabler client may be called a service layer or common service entity. The second form of implementing an edge-aware UE is one in which the edge enabler client is not hosted on the UE, but has a special protocol stack and configuration edge functionality. For example, the UE may provide a GUI that allows a user to indicate that a particular application should be allowed access to edge services. In this case, the UE protocol stack needs to enable the UE to know how to send application data when edge computing is possible.

[0107] A UE that is unaware of the edge does not have the ability to trigger explicit requests for services provided at the edge. A UE that is unaware of the edge may have traffic routed to edge services by the network, but the UE is generally unaware of this.

[0108] Application clients in a UE that are aware of the edge (with or without EEC) may or may not be aware of the edge service.

[0109] Edge-aware application clients are pre-provisioned using configuration information that can be explicitly provided to the UE or an EEC hosted by the UE that has information about edge-related capabilities and requirements. Edge-aware application clients can also trigger explicit requests for services provided at the edge. These requests are processed by the UE or an EEC hosted by the UE before they are requested from the network.

[0110] An application client that is not aware of the edge may not have the ability to trigger an explicit request for edge services, but information about the capabilities and requirements of the application client that is not aware of the edge may be pre-provisioned, which can be used by the UE or an EEC hosted on the UE to configure or trigger such services. For example, the UE may provide a GUI that allows the user to indicate that the application enables edge computing. The functionality enabled by the GUI may use configuration information pre-provisioned by the application client, but the application client itself may not be aware of the edge.

[0111] An edge data network is a local data network that supports the delivery deployment of edge hosting environments.

[0112] Services in the edge data network are provided by edge computing service providers (ECSPs), which may or may not be the same as the mobile network operators (MNOs).

[0113] An edge data network can be configured as an LADN (for example, when the MNO is also an ECSP), in which case its service area can be discovered as an LADN service area based on existing 5GC procedures. However, these procedures do not enable the discovery of edge data network service areas in the more general case where the EDN is not configured as an LADN. The following explanation addresses the more general case, with specific references to the LADN case.

[0114] Edge data network configuration servers are deployed and managed by either ECSP or MNO and can provide configuration services to one or more edge data networks. Configuration servers are generally not located at the edge, but rather are part of the MNO's N6-LAN.

[0115] 5GC EDN information. 5GS specifies network capabilities for interworking with external application servers. This includes exposure capabilities via NEF, such as provisioning capabilities to external functions. It also includes the capabilities of application servers belonging to third parties with which PLMN has a match that influences routing decisions. These capabilities, with enhancements, can be used to provide a means for ECSP to provide externally managed EDN information to the EDN.

[0116] The application server may provide configuration for edge data networks that may not be managed by the PLMN providing services to the UE to: 1) the AMF, where information about the EDN service area is used to assist in EDN and EDNCS discovery; and 2) the SMF, where traffic information is used to influence routing, where that routing influence can be used to access EDNCS or to provide connectivity for edge services.

[0117] It should be noted that PCF can provide both AMF and SMF through the corresponding policies. The AMF and SMF configurations are described in detail below. However, AF can also provide a single set of provisioning information to PCF, and as a result, that information is provided to both AMF and SMF via the corresponding policies.

[0118] The AMF may consist of any EDN-related information for all EDNs available in any tracking area of ​​the AMF's service area, and may also consist of information about additional EDNs within the PLMN.

[0119] There may be different approaches to how edge data network information can be configured in the AMF, for example, as a set of tracking areas. In one example, the information is configured per DNN, i.e., for different UEs that access edge services using the same DNN, and the configured edge service area is the same regardless of the UE enrollment information. In a second example, the information is configured per EDNCS, i.e., for different UEs that access edge services of the same type or from the same ECSP, and the configured edge service area is the same regardless of the UE enrollment area. The UE enrollment information is used to derive the type of enrolled edge service, which is then used to derive the corresponding EDN-CS. Different DNNs provided by the UE may be mapped to the same EDN-CS.

[0120] In both of the above examples, the EDN information configured in the AMF may depend on factors that determine whether a UE is in a registration area (e.g., mobility patterns and permitted / non-permitted areas). For example, UEs that are in the same EDN service area and subscribed to the same service (or use the same DNN) but have different mobility patterns may be mapped to different EDNCS (or EDNs). For each EDN, the information may include an EDN identifier, a service area (e.g., a list of corresponding TAIs), a DNN or multiple DNNs, an indicator specifying whether the EDN is configured as an LADN and discoverable, an ID associated with the ECSP, the FQDN of the EDN-CS associated with each or multiple DNNs, and conditional parameters for determining the EDNCS association to the DNN (e.g., per service type). How this information may be used by the AMF is described in the following procedures.

[0121] The SMF receives traffic routing impact information from the AF via the PCF. When provisioning edge configuration information with 5GC, application server requests may target, for example, a group of UEs. In such cases, the information may be stored in the UDR, and the PCF receives a corresponding notification of the application server request. The traffic routing impact information provided to the SMF may include 1) traffic descriptors (IP filters or application IDs), 2) DNAI, 3) N6 routing information (which may include IP addresses and ports), and 4) EDNCS FQDN. The way in which this information can be used by the SMF will be described in the procedures described later.

[0122] Processing of edge-aware UE applications without an EEC. The embodiments disclosed herein include procedures that may be well suited when a UE that does not host an EEC needs to provide edge services to edge-aware UE applications. For example, the UE may provide a GUI that allows the user to indicate that a particular application should be allowed access to edge services. The UE protocol stack may use this indication to determine that traffic from the indicated application should be routed to the edge data network.

[0123] Handling edge-aware UE applications without an EEC - registration-based UE provisioning. UEs may need to register with the network to be authorized to receive services in order to enable mobility tracking and reachability. When registering a UE with the network, it is proposed that the UE indicates to the network that it wishes to access the network's edge computing resources. This mechanism can be used in scenarios where a UE hosts an application that does not host an EEC, is edge-aware, and provides a GUI that allows the user to indicate the application enabling edge computing.

[0124] Figures 4A–4C illustrate an enhanced registration procedure (without EEC examples) according to one aspect of the present disclosure. The procedure shown in Figures 4A–4C is an enhanced version of the general registration procedure described in Section 4.2.2.2.2 of 23.502 (3GPP TS 23.502, Procedures for 5G Systems, Stage 2, V16.1.1 (2019-09)). The enhancements to the general registration procedure are as follows: In step 1 of Figure 4A, the UE can initiate the registration procedure using registration type “Initial Registration” or “Mobility Registration Renewal” and request the retrieval of edge data network information by providing an EDN information directive, which is flags and additional information that may indicate that the UE wishes to access the network’s edge computing resources. The EDN information directive may also include an application descriptor (OSId and / or OSAppId) to indicate to the network that a particular application on the UE should have access to the edge computing services. The EDN information instruction may be forwarded to the AMF in step 3 of Figure 4A and to the PCF in step 16 of Figure 4B. The PCF may use this information to determine which URSP rules to forward to the UE. The PCF may respond to the AMF with an instruction on whether the UE can be configured with URSP rules that enable edge computing. This instruction may be provided by the PCF per application descriptor. In step 21 of Figure 4C, the instruction from the PCF may be provided to the UE by the AMF. The PCF may further subscribe to the AMF to receive notifications when the UE's location changes so that it can update the UE's URSP rules related to edge computing.

[0125] Handling UE applications that are not aware of edges without an EEC - Using URSP rules. URSPs are policies provided to UEs by PCF. These can be used by UEs to determine how outgoing traffic from the UE is routed. Traffic may be routed to an established PDU session, offloaded to non-3GPP access outside the PDU session, or trigger the establishment of a new PDU session.

[0126] Using the enhancements to the registration procedure described above, the UE may provide the PCF with instructions that it hosts applications that may benefit from traffic being routed to edge services. This information (e.g., application descriptors) may be used by the PCF to determine if a URSP rule may be required to access the edge services. As a result, an EDN-specific URSP rule may be returned to the UE in the registration acceptance response. The URSP rule may also be provided to the UE in the configuration update procedure. To support this feature, the route selection component of the URSP rule may be modified to include a new edge-aware instruction. A route with this instruction may only be considered valid if the UE is configured (e.g., via a GUI) so that the associated application descriptor enables edge services. The RSD may further indicate locations where the route can be considered valid (e.g., where edge computing services are available).

[0127] URSP policies with route descriptors containing edge-aware directives can only be used if edge computing is possible on the UE. Route selection validation criteria may provide location (and time) conditions associated with the specific edge service required. Edge-aware directives can be used in URSP rules that route PDU session establishments for edge configuration purposes to edge services. Other URSP rules with edge-aware directives may cause PDU session establishments for edge configuration purposes to be sent to the configuration server.

[0128] EEC discovery on edge-configured servers (URSP-based approach). The PDU session establishment procedure is used by the UE in 5GS to establish a new PDU session in several handovers from the EPS, or between 3GPP and non-3GPP instances, or following a network-triggered PDU session establishment procedure. This procedure may assume that the UE has registered and the AMF has retrieved user enrollment data from the UDM.

[0129] In some scenarios, an edge enabler client may attempt to establish IP connectivity to an edge configuration server after it has been pre-provisioned with the FQDN of the edge configuration server or after it has been acquired during registration. For example, a UE discovers an EDN service area, and one of its application clients has been pre-provisioned with a well-known FQDN to access the configuration server. A UE URSP rule may cause the UE to attempt to establish a new PDU session when the FQDN is first accessed. The URSP rule may indicate to the UE that it will use the PDU session to acquire edge configuration data, or more generally, operator configuration data. This mechanism may also be used for purposes other than acquiring operator or edge configuration data, for example, to acquire the edge service itself. The mechanism may also be used by an edge-aware UE or application when the FQDN is pre-configured, rather than being provided via a URSP rule.

[0130] The PDU session establishment procedure in Section 4.3.2.2.1 of 23.502 (see 3GPP TS 23.502, Procedure for 5G Systems, Stage 2, V16.1.1 (2019-09)) may be enhanced as shown in Figures 5A and 5B. Note that only the changes to the procedure introduced by this disclosure are detailed, and all other steps are performed in accordance with this specification.

[0131] Figures 5A and 5B show an example call flow for an enhanced UE request PDU session establishment. Here, in step 1 of Figure 5A, the UE may send an AMF NAS message (S-NSSAI, DNN, PDU session ID, request type, old PDU session ID, N1 SM container (PDU session establishment request)) which includes an edge configuration request instruction. Including an edge configuration request instruction may indicate that the PDU session will be used to retrieve configuration information from an edge configuration server.

[0132] In step 2, the AMF may proceed to SMF selection and determine the EDNCS if an edge configuration request indicator is included. If the message includes a DNN corresponding to a known EDNCS, the AMF may forward that information to the SMF so that the FQDN is determined to be the IP address of the operator's ECS, so that the SMF may decide which DNS server addresses to provide to the UE. DNS server addresses can be provided in several ways, such as as a simple list or as a list mapping each DNS address to a location (e.g., cell ID). If the message does not include a DNN corresponding to a known EDNCS, for the provided S-NSSAI, the AMF may select / determine an EDNCS based on 1) an EDNCS corresponding to an available LADN, 2) an EDNCS based on priority established from UE enrollment information regarding the relative priority of the enrolled edge service or the default DNN used, or 3) an EDNCS based on the local OAM configuration. The AMF may create an implicit enrollment in “Presence of UE in EDN Area” so that presence notices are sent to the SMF.

[0133] In step 3, the AMF may send an Nsmf_PDUSession_CreateSMContext Request to a selected SMF with an edge configuration selection mode flag, which the SMF may use to determine which DNS server addresses should be sent to the UE in the PDU session establishment response. The DNS server addresses can be provided in several ways, such as as a simple list or as a list mapping each DNS address to a location (e.g., cell ID). The PDU session establishment response may also be used to send to the UE that the edge configuration server can be reached using the PDU session.

[0134] In step 5, the SMF may send an Nsmf_PDUSession_CreateSMContext response to the AMF. The response may include the FQDN of the EDNCS or provide the DNS server address of the EDNCS to be updated at the UE (i.e., during the PDU session, as described in 3GPP TS 23.501, System Architecture of 5G Systems, Stage 2, V16.3.0 (2019-12)). In step 8, the SMF may select an appropriate UPF using the FQDN of the EDNCS. In step 10a, the SMF may send an N4 session establishment request to the selected UPF, which may include appropriate CN tunnel information. Then, continuing from step 6, various optional steps such as secondary authentication / authorization may be taken into consideration that the PDU session is used for configuration purposes. Steps 12 and 13 in Figure 5B are used to forward the response information to the UE.

[0135] Edge configuration server EEC discovery (registration-based approach). The UE may be provided with edge configuration server information during registration. Enhancements to the general registration procedure are shown in Figures 6A and 6B and are described below. In step 1 of Figure 6A, the UE can initiate the registration procedure using registration type “Initial Registration” or “Mobility Registration Update” and request discovery of edge configuration servers by providing an EDNCS discovery request instruction, which is a flag and additional information indicating that the UE wishes to access edge computing resources in the network. The EDNCS discovery request instruction may also include an application descriptor (OSId and / or OSAppId) to indicate to the network that a particular application on the UE should have access to edge computing services. The EDNCS discovery request instruction may be forwarded to the AMF in step 3. The AMF may use this information to determine which EDNCS discovery information to forward to the UE.

[0136] When a UE requests EDN discovery information via an EDN discovery request instruction, the AMF may identify the EDN discovery information provided in response to the registration procedure. The AMF may use subscription information (existing or obtained via step 14 in Figure 6B) to determine which services the UE has edge service subscriptions for. The AMF may prepare a list of available EDNs and EDNCS for the UE in the registration area to be provided to the UE in registration acceptance (step 21 in Figure 6B). The information provided to the UE may include, for each EDN that meets the criteria to be discovered by the UE, 1) an EDN identifier, 2) the UE's authorization scope on the EDN (e.g., on services or storage), 3) the corresponding EDN service area (e.g., a list of corresponding TAIs), 4) one or more DNNs used to acquire edge services, 5) an optional indicator specifying whether the EDN is configured as an LADN and discoverable, 6) the FQDNs of the EDNCS associated with each or more DNNs, determined based on conditional parameters (e.g., per service type or mobility pattern), or 7) EDN discovery information. EDNCS discovery information may include the following: 1) the EDNCS's FQDN or IP address, 2) a list of services (e.g., application descriptors) indicating which edge services can be provided, or 3) one or more DNNs associated with the ECD for the UE to access. Note that the “EDN information” in step 21 of Figure 6B includes this “EDNCS discovery information” described above.

[0137] Please note that not all information in the list above may be available to AMF. For example, an EDN service area may be configured, but EDNCS information may not be available. Also, if the UE includes an indicator requesting LADN DNN or LADN information, AMF may only provide information for EDNs that are configured as LADNs and discoverable. Alternatively, the UE may be able to extract this information using an optional indicator that specifies whether an EDN is configured as an LADN and discoverable.

[0138] Based on the available EDN service areas at the UE, the UE may later decide whether it can request a PDU session for edge services. Alternatively, this information may be requested and provided in a UE service request or configuration update procedure. If the AMF determines, based on the process described above, that two or more applicable EDNCS are available, the AMF may select / determine for the provided S-NSSAI: 1) EDNCS corresponding to available LADNs, 2) EDNCS based on priority established from UE enrollment information regarding the relative priority of the enrolled edge services or the default DNN used, or 3) EDNCS based on the local OAM configuration. The AMF may create an implicit enrollment for “UE presence in EDN area” so that a presence notification is sent to the SMF. The AMF may determine the SMF corresponding to the selected EDNCS, or, if it cannot determine the EDNCS, may reject the session establishment request.

[0139] Enables efficient network exposure and alternative routes via UE. Monitoring events may be exposed to Application Functions (AFs) (as described in 3GPP TS 23.502, Section 4.15.3, Procedures for 5G Systems, Stage 2, V16.1.1 (2019-09)). When monitoring events are exposed to AFs via NEFs, reports may be sent from the NF (AMF, GMLC, UDM, or SMF) that detected the event to the NEF and onto the AF. Prior to detecting the event and sending the report, the NF that detected the event may be configured to monitor one of the procedures in TS 23.502, Section 4.15.3.2 for the AMF. The configuration typically consists of calling a join operation.

[0140] Figure 8 shows an example of an unoptimized network exposure reporting path for edge deployment. “Local deployment” as described herein refers to core network functions (e.g., UPF or SMF) that may be dedicated to enabling functionality in LADN and / or edge deployment when local deployment functions are generally deployed geographically closer to the UE. Local deployment functions may be illustrated independently of “centralized” core network functions that are deployed independently of the location of the serviced UE.

[0141] An edge hosting environment may be geographically close to a local deployment and UE, but functionally it is not part of a CN deployment. Therefore, in one aspect of this disclosure, considering a local deployment isolated from an edge hosting environment, for example, a local deployment may serve multiple EHEs and be managed by different providers. However, this is merely a logical configuration, and a local deployment may, or may be considered part of a 5GC, or include EHEs, etc. Also note that in some 3GPP specifications (e.g., from 3GPP SA2), this concept of a local deployment may be referred to as an "edge" or "edge deployment."

[0142] Figure 8 illustrates two possibilities for AF deployment: in an Edge Hosting Environment (EHE) with an edge application server, or in a centralized cloud. The dotted lines illustrate the reporting pathway to AF for reports that may be generated by either AMF or local SMF.

[0143] Figure 8 illustrates why the current exposure architecture may cause problems in some edge deployments. The fact that surveillance reports must traverse through a centralized NEF can cause unacceptable delays between the occurrence of events at the AF and the reception of event reports, particularly towards edge AFs. Note that AMFs and NEFs may be in a “centralized” core network, i.e., not at the “edge,” but they may not be close to each other. For example, AMFs, SMFs, and NEFs may each be in different / separate cities.

[0144] Aspects of this disclosure propose a novel reporting method that may be used to send event reports when a UE is connected to an edge hosting environment (EHE) via a local deployment. In one aspect, a novel CN ​​function, a "Local Enablement Function" (LEF), is proposed. The LEF may be a type of NEF that can be used to route monitoring reports to an AF. Monitoring report configuration requests from a non-latency-sensitive AF may still be sent to an NEF residing within a centralized core network.

[0145] Figure 9 shows an example of an optimized reporting path from a centralized network function. Figure 9 illustrates the LEF of a local deployment used to expose the AF in an EHE connected to a local deployment. The dotted line illustrates the reporting path from either the AMF or the local SMF to the edge AF. The illustrated reporting path corresponds to the method introduced herein. Optimization occurs by minimizing (or eliminating) the number of times messages cross geographical boundaries between the centralized NF and geographically close entities at the edge.

[0146] Methods for Edge Reporting Enrollment via Centralized NEF - Using Enrollment Retargeting. The following describes how an AF may enroll in monitoring events via a centralized NEF. When a UE moves and connects to different local deployments and EHEs, the enrollment may be forwarded to an LEF serving the corresponding deployment.

[0147] Figure 10 is an example call flow demonstrating the forwarding of edge reporting joins from a centralized network exposure function. The flow in Figure 10 illustrates events forwarded by the centralized NEF to the PCF, such as joins to downlink delivery data status. In the flow, the PCF may be replaced by a UDM for other types of events, such as availability after a DDN failure. Thus, the forwarding functionality and flow messages described for the PCF can be applied to other NFs such as UDMs.

[0148] To enable AF joins for event monitoring via a centralized NEF, it is proposed to enhance the reporting join procedure to include newly proposed reporting parameters, including reporting requirements, AF availability information, and UE routing preference indicators, while reporting exposure is provided by the NEF or LEF best suited to satisfy reporting requirements (e.g., delay). The reporting requirements (e.g., delay tolerance) may be for each join and may include a list of qualifiers so that the provided reporting requirements can be applied differently based on several conditions, e.g., UE location, UE reachability status, time, etc. AF availability information may be, for example, AF location parameters or availability time. UE routing preference indicators may be used as mandatory or optional requirements for including (or preferring to include) UEs in the reporting path. This feature may also be used when a UE can use reporting (e.g., QoS changes) for processing instead of waiting for AF processing based on reporting. Reporting parameters can be used to determine which entity (e.g., NEF or LEF) is best suited for reporting exposure to satisfy reporting requirements.

[0149] In step 1 of Figure 10, the AF may send an Nnef_EventExposure_Subscribe request to a centralized NEF requesting edge hosting environment discovery reports, such as data delivery status. The request may include IP traffic filters and monitoring events. In step 2, the NEF may send an Npcf_EventExposure_Subscribe request to a PCF. IP filter information, monitoring events received from step 1, and the requesting AF endpoint may be included in the message. The NEF may determine the address of the selected PCF for the PDU session, for example, by querying the BSF.

[0150] Using the enrolled reporting parameters proposed above, the NEF can determine the entity best suited to support the exposure of the enrolled report. To support this functionality in the BSF, it is proposed that the registered Nbsf Management Register operation (as described in 3GPP TS 23.502 5.2.13.2.2, Procedure for 5G Systems, Stage 2, V16.1.1 (2019-09)) be enhanced to include information about available NEFs and LEFs. This means that when the PCF calls Nbsf_Management_Register, in addition to the tuple for the PDU session and PCF id (UE address, SUPI, GPSI, DNN, DN information (e.g., S-NSSAI), PCF id), it may also provide preferred NEF / LEF information based on, for example, reporting requirements or endpoint (AF) information.

[0151] When a joined NEF meets these requirements, existing join / notification procedures may apply. The following explanation primarily focuses on cases where the LEF provides the most efficient reporting exposure in a local deployment.

[0152] In step 3, the PCF may send an Nsmf_EventExposure_Subscribe request message to the local SMF, which may be useful for PDU sessions related to IP filter information, the LEF, and the notification endpoint of the requesting AF. Next, in step 4, the local SMF may send an Nnef_EventExposure_Subscribe request to the corresponding LEF requesting exposure of the report. This request may include the endpoint of the requesting AF. Then, in step 5, the LEF responds to the local SMF with an Nsmf_EventExposure_Subscribe response, and in step 6, the local SMF may send an Npcf_EventExposure_Subscribe response message to the PCF, which may include the LEF information. Subsequently, in step 7, the PCF may send an Npcf_EventExposure_Subscribe response message to the NEF, which may include the LEF information. In step 8, the NEF may send an Nsmf_EventExposure_Subscribe response to the AF, which may include the LEF information. In step 9, the local SMF may detect an event, such as a change in downlink delivery status. Also, in step 10, the SMF may send Nsmf_EventExposure_Notify to the LEF along with the downlink delivery status event message.

[0153] To communicate with the LEF, the local SMF may use the N4 interface to the local UPF and from the local UPF, which is the Nx interface already proposed for the LEF. Alternatively, a new interface or API may be defined between the local SMF and the LEF. Alternatively, a new service-based interface may be defined between the local SMF and the LEF, and reports may be sent to the LEF using the API of the service-based interface. In step 11, the LEF may send Nnef_EventExposure_Notify to the AF along with the downlink delivery status event message.

[0154] It should be noted that the messages in steps 4, 5, 10, and 11 in the above description may use Nnef behavior, assuming that the LEF interface is implemented as an extension of the NEF behavior currently defined by 3GPP. However, LEF messaging can be implemented independently, although it may be implemented similarly to the Nnef behavior currently described by 3GPP.

[0155] In addition to the BSF functionality enhancements proposed herein, it should be noted that this method relies on the PCF determining the corresponding local SMF. This means that when the UE moves from local deployment A to local deployment B and changes its connection, the PCF needs to track the joins sent to the local SMF and LEF that serve local deployment A, forward them to local deployment B, and delete the old joins. The PCF may also send an update to the join response for the NEF (corresponding to step 7) which has the new LEF. The update to the join response is forwarded by the NEF to the AF (corresponding to step 8).

[0156] Method for Edge Reporting Enrollment via Centralized NEF - Using Policies to Forward via UE. Figure 11 is an example call flow demonstrating routing / delivery of an edge monitoring policy via a UE. The flow in Figure 11 describes how an AF may enroll via a centralized NEF to monitor events generated by an NF in a local deployment. To support this method, the AF enrollment procedure may be enhanced using previously proposed reporting parameters. Reporting parameters may include reporting requirements, AF availability information, and UE routing preference indicators. Reporting parameters may be used to determine whether this enrollment relates to event monitoring at the edge that needs to be delivered in an optimized format, for example, via an LEF in a local deployment. To enable the method of using policies to forward via a UE, one or more event enrollments of an AF may be used to create an Edge Monitoring Policy (EMP).

[0157] The AMF may encapsulate an EMP in a NAS message and send it to the UE. When the UE changes its connection from one local deployment to another, it may provide an EMP to each local SMF via user-plane messaging using a pre-configured FQDN (or provided in the policy itself). Alternatively, the UE may provide an EMP to each local SMF via NAS-SM messaging (e.g., PDU session establishment or PDU session modification messages). When a UPF receives a message addressed to a pre-configured FQDN, this UPF may deliver that message to the local SMF associated with the PDU session. To enable this functionality, it has been proposed that the UE indicate support for policy forwarding. This support indication may be provided during various procedures, for example, when registering with the core network. The network (i.e., the AMF) may use this indicator to determine whether it is permissible to send an EMP to the UE.

[0158] The SMF can be configured using policy information (EMP) that can be sent from the UE to the local SMF. This method of delivering policies to the SMF via the UE can also be used in other cases, such as when the SMF cannot communicate directly with the PCF or receive policy information from the AMF, or in local deployments to deliver other policies or configuration messages from a centralized NF to an NF.

[0159] In step 1 of Figure 11, the AF may send an Nnef_EventExposure_Subscribe request to a centralized NEF requesting edge hosting environment discovery reports, such as data delivery status. This request may include IP traffic filters and monitoring events. Then, in step 2, the NEF may send this request to the corresponding NF, for example, an Npcf_EventExposure_Subscribe request to a PCF. The PCF may be replaced by a UDM for several types of events, such as availability after a DDN failure. IP filter information, monitoring events received from step 1, messages, and the endpoint of the requesting AF may be included. The NEF may determine the address of the selected PCF for the PDU session by querying the BSF.

[0160] In step 3, the PCF or UDM may create a corresponding EMP, or modify an existing EMP to include a new join. The EMP may, for example, be created by the PCF and stored in the UDM. The EMP may also be forwarded to the AMF, where it is encapsulated in a NAS message for the UE to which the monitoring is related. The EMP may include information about one or more monitoring events and one or more received AFs. EMPs that can be delivered using this method include: • A policy identifier that provides a unique ID for the policy, This may include a UE identification filter that provides a method for identifying the UEs to which the monitoring policy applies. The filter may be, for example, an IP filter or a join correlation ID. • It can be represented as a notification endpoint associated with the endpoint information of a received AF. This can be two or more received AFs, • An identifier for the measurement or message type (e.g., Downlink Delivery Data Status Event ID) that determines which measurement or message type should be generated in the local deployment and sent to the AF to which the policy applies. For example, a notification parameter may include a time window in which event notifications should be forwarded to the AF. The notification criteria are used by the local SMF to configure event monitoring. The notification parameter may include LEF information, or the LEF information may be pre-configured in the local SMF. For example, policy applicability criteria may include specifying which local deployment should apply by indicating geographical area, specific LADN information, etc. Policy applicability criteria may be used by local SMFs when validating policies or configuring monitoring. The policy delivery criteria may include other criteria that define how the UE should deliver EMPs to its local deployment. For example, a policy delivery criterion might indicate to the UE that an AMF trigger is required to trigger delivery. In another example, the criterion might indicate that the UE should trigger EMP delivery for any new LADNs it discovers, such as periodically. These criteria may also indicate whether the UE should use a pre-configured FQDN for EMP delivery, or whether it may configure a different specific FQDN.

[0161] In step 4, the AMF may use a NAS message to send the EMP to the UE. The NAS message may contain instructions on how to send the report to the local SMF when connecting to the local deployment, along with the EMP. For example, the policy delivery criteria mentioned above may be included in the NAS message instead of being included in the policy itself.

[0162] When the UE connects to a new local deployment, the subsequent steps in Figure 11 are repeated for each new local deployment. In step 5, the UE may detect a new local deployment, for example, by detecting a new LADN. Alternatively, the UE may be triggered by the AMF after connecting to a local deployment. Then, in step 6, the UE may send an EMP encapsulated in a UP message to the local UPF, and then forward this message to the local SMF using the policy delivery criteria specified in the EMP or in the NAS message received from the AMF. The UE may consist of a DNN and / or S-NSSAI that can be used to send the EMP to the SMF. The UE may consist of URSP rules indicating that traffic carrying the EMP should be routed toward a specific DNN and / or S-NSSAI. In step 7, the local SMF may configure monitoring in the local deployment. The local SMF may configure other NFs implemented in the local deployment (e.g., NWDAF) to provide monitoring reports. Events may be detected by the local SMF in step 8. Alternatively, the event may be detected by other NFs implemented in the local deployment. In step 9, the local SMF may send Nsmf_EventExposure_Notify to the LEF along with the monitored event, and the LEF may send Nnef_EventExposure_Notify to the AF in step 10 along with the monitored event message.

[0163] The above method for distributing subscription information provided by the AF via a centralized NF (i.e., NEF) can be used to distribute any policy or configuration information provided to the NF via the centralized NF in a local deployment along the UE's path. This method can also be used to distribute policy or configuration information provided via the centralized NF to servers in an edge hosting environment connected to the local deployment.

[0164] Method for Reporting to Edge Servers - Method for Centralized NF Event Reporting via UE. When an event is detected within the central core network (e.g., by the AMF in Figure 8) and the AF is at the edge, sending the report via the NEF to the edge may not be efficient. As illustrated in Figure 8, sending the report via the NEF can cause significant delays. In one embodiment, it is proposed that the AMF may send the report via the UE using a NAS message, provided that the UE is connected to a local / edge deployment and the AF that should receive the report. The NAS message may include an event report and instructions (i.e., an address) on how to send the report to the AF. For example, the following information may be sent to the UE: • Event reports describing events such as location changes, changes in SUPI / PEI associations, changes in MICO mode settings, UE reachability reports, QoS targets that can no longer (or again) be met, or QoS monitoring parameters. • The IP address or FQDN of the LEF that should receive the report. • DNN or S-NSSAI to be used in association with the PDU session used to send reports to the UE, • An AF identifier that identifies the AF to which the LEF should forward the report, and • A transaction reference ID that can be used by AF to correlate early requests and reports in order to receive reports.

[0165] This method can be further used to forward monitoring reports from AMFs or other NFs within a centralized core network when the UE is reachable. This method can also support joins with precisely implemented reporting parameters, and UE routing preference indicators can command or indicate UE routing preferences. This is particularly useful when UEs that directly act on the report without waiting for AF operations or commands are beneficial, such as QoS monitoring. Simultaneously, the AF can also notify reports via optimized routes.

[0166] Figure 12 is an example call flow demonstrating report routing from a centralized NF via a UE. Figure 12 illustrates a high-level flow method for monitoring reports being routed from a centralized NF (e.g., AMF) to an AF located at an EHE via a UE.

[0167] After the UE receives the monitoring report from the AMF in step 2 of Figure 12, in step 3, it may send this monitoring report to the LEF via the local UPF. When the UE sends the monitoring report to the LEF, the UE may choose to use the DNN and an existing PDU session already associated with the S-NSSAI provided by the AMF when the monitoring report was sent to the UE. Alternatively, the UE may establish a new PDU session using the DNN and the S-NSSAI provided by the AMF and use the new PDU session to send the report. The UE may also transfer information to the LEF, such as an AF identifier, so that the LEF can decide which AF to forward the report to. The UE may also include other information, such as a timestamp indicating when the report was received from the AMF and the transaction reference ID received from the AMF.

[0168] In step 4, the UPF may use an interface or API to send reports to the LEF. For example, the Nx interface in Figure 9 could be an N6-based interface, and IP-based routing could be used to send reports to the LEF. Alternatively, a new service-based interface may be defined between the UPF and the LEF, and the API of the service-based interface may be used to send reports to the LEF.

[0169] Next, in step 5, the LEF may expose information to the edge AF using the same API used in the centralized NEF (Figure 9). The Ny interface supports the edge AF to the LEF interface and can be implemented as the N33 / Nnef interface defined in TS 29.122. This API can be enhanced so that reports arrive at the edge AF via the UE, since the UE is connected to the AF through the edge environment.

[0170] To enable this functionality, it has been proposed that the UE indicate support for routing monitoring reports to the edge. This support indication could be provided during various procedures, for example, as part of the PDU session establishment procedure when registering with the core network. The network (i.e., AMF) could then use this indicator to determine whether it is permissible to send monitoring reports to the UE.

[0171] To enable this functionality, it has also been proposed that the core network provide the UE with an Edge Monitoring Routing Policy (EMRP). The UE can use EMRP to receive monitoring reports, route them to the LEF, and then expose that information to the requesting edge AF.

[0172] Figures 13A–13E illustrate an example call flow of an enhanced registration procedure that enables the UE to communicate its support for routing monitoring reports. Figures 13A–13E illustrate a general registration procedure (as described in 3GPP TS 23.502, Procedures for 5G Systems, Stage 2, V16.1.1 (2019-09)) that has been enhanced to enable the UE to communicate its support for routing monitoring reports to the LEF.

[0173] The following enhancements are proposed in the procedure shown in Figures 13A to 13E to enable the UE to support routing monitoring reporting to the LEF.

[0174] In step 1 of Figure 13A, the UE includes an LEF reporting capability indicator in the registration request, notifying the core network that the UE can receive monitoring reports from the AMF and provide monitoring reports to the LEF. This registration request may be forwarded to the AMF in step 3.

[0175] In step 16 of Figure 13C, the AMF includes an LEF reporting capability indicator to the PCF when establishing the AM policy association for the UE. The PCF creates a new Edge Monitoring Routing Policy (EMRP) policy or updates an existing Edge Monitoring Routing Policy. The information used by the PCF to create / update the policy may include the UE location and the subscribed service area limits (from the AMF based on UDM information). The PCF also obtains information about the monitoring enabled for the UE by querying various NFs (e.g., AMF, GMLC, UDM). The PCF may provision information about available LEFs as part of the network configuration or policy. The EMRP policy is: a) A policy identifier that provides a unique ID for the policy, b) A DNN that identifies a data network, to which the UE is connected when routing monitoring reports to a given LEF, c) The IP address or FQDN of the LEF to which the policy applies, d) Notification endpoint associated with the received AF endpoint information, e) An identifier for the measurement or message type (e.g., Event ID) that determines which measurement or message type should be forwarded to the LEF to which the policy applies, f) An indicator of application layer-level exposure of LEF information may include. This is a binary indicator that allows the UE to send LEF information to the AF using application layer signaling. This is useful for supporting the AF at the edge to discover which LEFs to connect to. The AF can generally be pre-provisioned with information about centralized NEFs. However, with the surge in edge deployments, it may not be feasible to pre-provision information about all LEFs when the ECSP is different from the MNO. Instead, the UE can send this information to the AF at the application level based on the received EMRP.

[0176] In step 21 of Figure 13E, the EMRP is returned to the UE in a registration acceptance message. If the UE did not include an LEF reporting capability indicator in step 1, the AMF may ask the UE in the registration acceptance message whether they wish to provide LEF reporting.

[0177] In step 22, if the UE is requested by the AMF to provide its LEF reporting capability, the UE returns an indicator to the AMF in the registration completion message. Upon receiving the LEF reporting capability indicator, the AMF may trigger the execution of a UE configuration update procedure for transparent UE policy delivery in order to generate and send an EMRP. After receiving the EMRP, the UE routes the monitoring reports specified by the policy and sends them to the LEF.

[0178] The UE may also send an LEF reporting capability indicator as part of the PDU session establishment procedure. In this scenario, the UE includes the indicator in the PDU session establishment request or when modifying the PDU session. The SMF receives the indicator and forwards it to the PCF. The EMRP is generated by the PCF and returned to the UE in the PDU session establishment acceptance response. Examples of existing types of AMF monitoring reports using this method include UE reachability, location reporting, and availability after downlink data notification failures.

[0179] Examples of existing types of PCF monitoring reports using this method include changes in access type, signaling path status, QoS targets that can no longer (or again) be met, and QoS monitoring parameters.

[0180] Another event detected in the central core network in Figure 8 is a change in QoS for an ongoing PDU session (TS 23.503 section 6.1.3.22). This report can be transmitted via SMF and NAS signaling.

[0181] Methods for reporting to edge servers - Methods for edge-deployed NF event routing. Figure 14 shows an example of an optimized reporting path from a locally deployed NF. When an event (e.g., downlink delivery data state by SMF in Figure 14) is detected at the edge and the AF is at the edge, it is efficient to send the report to the AF via a path that does not leave the edge.

[0182] For reports generated by other NFs in a local deployment (e.g., NWDAF), the PCF is applicable to all (or a set of) UEs connected to the local deployment and may generate an Edge Monitoring Policy (EMP) to be provided to the local SMF. EMPs may be generated or stored by other NFs, e.g., UDMs, for availability after a DDN failure event. The Edge Monitoring Policy provided to the local SMF is: • A policy identifier that provides a unique ID for the policy, A UE identification filter that provides a method for identifying UEs to which a monitoring policy applies, wherein the filter may be expressed as, for example, an IP filter or a join correlation ID, • Notification endpoints associated with received AF endpoint information, which may include two or more received AFs, • An identifier for the measurement or message type that determines which measurement or message type should be forwarded to the LEF to which the policy applies (e.g., Downlink Delivery Data Status Event ID), A notification parameter that includes the address of the LEF to which the policy applies (e.g., an IP address), and the notification parameter may include other criteria for event notifications to be forwarded to the AF (e.g., a time window), and such notification criteria may be used by the local SMF to configure event monitoring and for notification routing. This may include policy applicability criteria that specify which local deployments should apply, for example, by indicating geographical area, specific LADN information, etc. Policy applicability criteria may be used by local SMFs to validate policies or configure monitoring.

[0183] A local SMF may use edge monitoring policies to determine how to configure monitoring and send monitoring reports. The local SMF may configure other NFs implemented in the local deployment (e.g., NWDAF) to provide monitoring reports. Based on this configuration, reports identified by UE identification filters and filtering based on metric or message type identifiers are generated and sent to the LEF as indicated by the policy. Messages sent by the local SMF to the LEF also include known endpoints provided by the policy, which are used by the LEF to determine where to forward the reports.

[0184] In many cases, existing interfaces can be reused to report events generated by local NFs. For example, a local SMF may use the N4 interface with a local UPF. From the local UPF, reporting can use the previously proposed interfaces, namely the Nx interface between the local UPF and the LEF, and the Ny interface between the LEF and the (E)AF. Alternatively, a new interface or API may be defined between the local SMF and the LEF. Another alternative is to define a new service-based interface between the local SMF and the LEF, and use the API of the service-based interface to send reports to the LEF. The new interface / API or service-based interface may also be defined between other locally deployed NFs (e.g., NWDAF) and the LEF.

Claims

1. A wireless transmit / receive unit (WTRU) that hosts an edge enabler client (EEC), the WTRU comprising a processor, a communication circuit connected to a network, and a memory, wherein the memory, when executed by the processor, provides the WTRU with The WTRU receives a monitoring report from the network and sends a message indicating that it can send the monitoring report to the application function (AF). Receiving a NAS message from the network that includes a monitoring report and information for transmitting the monitoring report to the AF, and The information, including the aforementioned monitoring report, is transmitted to the AF using a protocol data unit (PDU) session. A WTRU, which includes computer-executable instructions, that causes the computer to perform the following actions.

2. The WTRU according to claim 1, wherein the monitoring report includes information about an event, including one or more of the following: a change in location, a change in SUPI / PEI association, a change in MICO mode setting, a UE reachability report, or a change in the ability to satisfy one or more QoS targets.

3. The WTRU according to claim 1, wherein the monitoring report includes at least one of a UE researchable report or a QoS monitoring parameter.

4. The WTRU according to claim 1, wherein the information for transmitting the monitoring report to the AF includes at least one of the following: an IP address or FQDN to which the monitoring report is to be transmitted, a DNN or S-NSSAI used by the WTRU to select a PDU session and transmit the monitoring report, or a transaction reference ID that the WTRU transmits to the AF when transmitting the monitoring report.

5. The WTRU according to claim 1, wherein the information transmitted to the AF includes at least one of a bitstream indicating when the monitoring report was received from the network, or a transaction reference ID received from the network.

6. The WTRU according to claim 1, wherein the instruction causes the WTRU to select or establish the PDU session.

7. The WTRU according to claim 1, wherein the message includes a registration request or a PDU session establishment request.

8. A server that hosts network functions (NF), the server comprising a processor, a communication circuit connected to a network, and a memory, wherein the memory, when executed by the processor, provides the server with The wireless transmission / reception unit (WTRU) receives a message from the WTRU indicating that it has received a monitoring report from the network and can transmit the monitoring report to the application function (AF), and Sending a NAS message to the WTRU that includes a monitoring report and information for sending the monitoring report to the AF, A server containing computer-executable instructions that perform the following actions.

9. The server according to claim 8, wherein the monitoring report includes information about an event, which includes one or more of the following: a change in location, a change in SUPI / PEI association, a change in MICO mode settings, a UE reachability report, or a change in the ability to satisfy one or more QoS targets.

10. The server according to claim 8, wherein the monitoring report includes at least one of a UE researchable report or a QoS monitoring parameter.

11. The server according to claim 8, wherein the information for transmitting the monitoring report to the AF includes at least one of the following: an IP address or FQDN to which the monitoring report is to be transmitted, a DNN or S-NSSAI used by the WTRU to select a PDU session and transmit the monitoring report, or a transaction reference ID that the WTRU transmits to the AF when transmitting the monitoring report.

12. The server according to claim 8, wherein the message includes a registration request or a PDU session establishment request.

Images