Identification of an edge enabler client (EEC) in an edge application server (EAS) and an edge enabler server (EES) in an edge data network

Abstract

An apparatus for wireless communication is provided. The apparatus may be a user equipment (UE). The apparatus receives a symbol from a first server in an edge data network. For example, the first server may be an edge application server (EAS). The apparatus transmits identification information associated with the apparatus to a second server in the edge data network. For example, the second server may be an edge enabler server (EES). The identification information includes at least a symbol, an identifier for the apparatus, and an identifier for the first server, wherein the identifier for the apparatus is independent of the apparatus's Internet Protocol (IP) address.

Description

Technical Field

[0001] This patent application claims priority and benefits from the following applications: PCT patent application No. PCT / US2022 / 040134, filed with the U.S. Receiving Office on August 11, 2022, entitled "IDENTIFICATION OF AN EDGE ENABLER CLIENT (EEC) IN AN EDGE APPLICATION SERVER (EAS) AND AN EDGE ENABLER SERVER (EES) IN AN EDGE DATA NETWORK"; and Greek patent application No. 20210100550, filed with the Hellenic Patent and Trademark Office on August 13, 2021, entitled "IDENTIFICATION OF AN EDGE ENABLER CLIENT (EEC) IN AN EDGE APPLICATION SERVER (EAS) AND AN EDGE ENABLER SERVER (EES) IN AN EDGE DATA NETWORK".

[0002] In summary, this case concerns communication systems, and more specifically, the identification of edge enabler clients (EECs) in edge application servers (EAS) and edge enabler servers (EES) in edge data networks. Prior Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiplexing access technologies that support communication with multiple users by sharing available system resources. Examples of such multiplexing access technologies include Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and Time Division Synchronous Code Division Multiple Access (TD-SCDMA).

[0004] These multiplexing access technologies have been adopted in various telecommunications standards to provide shared protocols that enable different wireless devices to communicate at the city, country, region, and even global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMBE) released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., in the case of the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communications (mMTC), and Ultra-Reliable Low-Latency Communications (URLLC). Some forms of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiplexing access technologies and telecommunications standards that employ them. Summary of the Invention

[0005] The following provides a simplified overview of one or more patterns to offer a basic understanding of such patterns. This overview is not an exhaustive summary of all anticipated patterns, nor is it intended to identify key or essential elements of all patterns, nor to illustrate the categories of any or all patterns. Its sole purpose is to provide some concepts of one or more patterns in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In one embodiment of this invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives a symbol from a first server in an edge data network and transmits identification information associated with the apparatus to a second server in the edge data network, wherein the identification information includes at least the symbol, an identifier of the apparatus, and an identifier of the first server, wherein the identifier of the apparatus is independent of the apparatus's Internet Protocol (IP) address.

[0007] In one embodiment of this invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives identification information associated with a User Equipment (UE) from the UE, wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address. The apparatus receives a service request from the application server including at least the symbol and the identifier of the application server, wherein the apparatus includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE. The apparatus transmits a message responding to the service request to the application server, at least based on the mapping.

[0008] In one embodiment of this invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus performs the following operations: receiving a network address of a first server configured to provide public network address information associated with a user equipment (UE); transmitting a request to the first server for the public network address information associated with the UE based on the network address; receiving, from the first server, the public network address information associated with the UE in response to the request; and transmitting the public network address information associated with the UE and the private network address information associated with the UE to a second server in an edge data network when network address translation is applied to private network address information associated with the UE.

[0009] In one embodiment of this invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus performs the following operations: receiving at least public network address information associated with a user equipment (UE) from the UE; receiving a service request from an application server in an edge data network that includes at least the public network address information associated with the UE, wherein the apparatus includes a mapping between private network address information associated with the UE and the public network address information associated with the UE; and transmitting a message responding to the service request to the application server in the edge data network, at least based on the mapping.

[0010] In one embodiment of this invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus performs the following operations: receiving from a user equipment (UE) a message including at least one user plane data packet; determining public network address information of the UE based on the message; receiving private network address information associated with the UE from a network address translation (NAT) device; receiving a service request from an application server in an edge data network including at least the public network address information associated with the UE, wherein the apparatus includes a mapping between the private network address information associated with the UE and the public network address information associated with the UE; and transmitting a message responding to the service request to the application server in the edge data network, at least based on the mapping.

[0011] In one embodiment of this application, a method for wireless communication includes the steps of: receiving a symbol from a first server in an edge data network; and transmitting identification information associated with a user equipment (UE) to a second server in the edge data network, wherein the identification information includes at least the symbol, an identifier of the UE, and an identifier of the first server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address. In one embodiment of this application, the identifier of the UE is a General Public Subscription Identifier (GPSI). In one embodiment of this application, the first server is an Edge Application Server (EAS), and the second server is an Edge Enabler Server (EES). In one embodiment of this application, the identification information is associated with an identifier of an Edge Enabler Client (EEC) in the UE.

[0012] In one embodiment of this case, a method for wireless communication includes the following steps: receiving identification information associated with a user equipment (UE) from the user equipment (UE), wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address; receiving a service request from the application server including at least the symbol and the identifier of the application server, wherein the means includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE; and transmitting a message responding to the service request to the application server. In one embodiment of this application, the method also includes the steps of: responding to the service request, determining at least one of the EEC ID or the UE identifier based on the symbol, the application server identifier, and the mapping between the EEC ID, the symbol, the application server identifier, and the UE identifier; and executing the service request based on at least one of the EEC ID or the UE identifier. In another embodiment of this application, the method also includes the step of: generating a table including the mapping between the symbol, the application server identifier, and the UE identifier. In another embodiment of this application, the UE identifier is a General Public Subscription Identifier (GPSI) or the symbol. In one embodiment of this case, the method also includes the following steps: assigning a second identifier to the UE; and transmitting the second identifier of the UE to the application server; wherein the mapping between the Edge Enabler Client ID (EEC ID), the symbol, the application server's identifier, and the UE's identifier maps the second identifier of the UE to the Edge Enabler Client ID (EEC ID), the symbol, the application server's identifier, and the UE's identifier.

[0013] In one embodiment of this case, a method for wireless communication includes the following steps: receiving a network address of a first server configured to provide public network address information associated with a user equipment (UE); transmitting a request to the first server for the public network address information associated with the UE based on the network address; receiving the public network address information associated with the UE in response to the request from the first server; and transmitting the public network address information associated with the UE and the private network address information associated with the UE to a second server in an edge data network when network address translation is applied to private network address information associated with the UE. In one embodiment of this application, receiving the network address of a first server configured to provide public network address information associated with the UE includes performing at least one of the following operations: receiving the network address of the first server from an entity in the core network via parameters in a Protocol Configuration Option (PCO) Information Element (IE); receiving the network address of the first server from an Edge Configuration Server (ECS) in an Edge Data Network; or receiving the network address of the first server from an Edge Enabler Server (EES) in the Edge Data Network. In one embodiment of this application, the first server is a STUN (Stay-through Utility for NAT) server, and the second server is an Edge Enabler Server (EES). In one embodiment of this application, the method also includes the step of transmitting the UE's identifier to the second server. In one embodiment of this application, the UE's identifier is a General Public Subscription Identifier (GPSI). In one embodiment of this case, the method also includes the following steps: determining whether network address translation is applied to the private network address information associated with the UE.

[0014] In one embodiment of this application, a method for wireless communication of a device includes the following steps: receiving at least public network address information associated with the user equipment (UE) from the UE; receiving a service request from an application server in an edge data network that includes at least the public network address information associated with the UE, wherein the device includes a mapping between private network address information associated with the UE and the public network address information associated with the UE; and transmitting a message responding to the service request to the application server in the edge data network. In another embodiment of this application, the method also includes the following steps: in response to the service request, determining the private network address information associated with the UE based on the public network address information associated with the UE and the mapping between the private network address information associated with the UE and the public network address information associated with the UE; and executing the service request based on the private network address information associated with the UE. In one embodiment of this case, the method also includes the following steps: activating the Network Open Functions (NEF) Application Programming Interface (API) based on the private network address information associated with the UE.

[0015] In one embodiment of this application, the method also includes the step of: transmitting to the UE a network address of a server configured to provide public network address information associated with the UE. In another embodiment of this application, the method also includes the step of: receiving an identifier of the UE from the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to both the private network address information associated with the UE and the public network address information associated with the UE. In one embodiment of this application, the UE's identifier is a General Public Subscription Identifier (GPSI). In one embodiment of this application, the public network address information associated with the UE includes a first Internet Protocol (IP) address and a first port number, and wherein the private network address information associated with the UE includes a second IP address and a second port number. In one embodiment of this case, the method also includes the following steps: assigning an identifier to the UE; and transmitting the UE's identifier to the application server, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to the private network address information associated with the UE and the public network address information associated with the UE.

[0016] In one embodiment of this case, a method for wireless communication of a device includes the following steps: receiving a message from a user equipment (UE) including at least one user plane data packet; determining public network address information of the UE based on the message; receiving private network address information associated with the UE from a network address translation (NAT) device; receiving a service request from an application server in an edge data network including at least the public network address information associated with the UE, wherein the device includes a mapping between the private network address information associated with the UE and the public network address information associated with the UE; and transmitting a message responding to the service request to the application server in the edge data network. In one embodiment of this application, the method also includes the following steps: determining an identifier for the UE based on the public network address information associated with the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to both the private network address information associated with the UE and the public network address information associated with the UE. In one embodiment of this application, the UE's identifier is a General Public Subscription Identifier (GPSI). In another embodiment of this application, the method also includes the following steps: assigning an identifier to the UE; and transmitting the identifier to the application server; wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the identifier to both the private network address information associated with the UE and the public network address information associated with the UE.

[0017] In one embodiment of this application, an apparatus for wireless communication includes: a component for receiving a symbol from a first server in an edge data network; and a component for transmitting identification information associated with the apparatus to a second server in the edge data network, wherein the identification information includes at least the symbol, an identifier of the apparatus, and an identifier of the first server, wherein the identifier of the apparatus is independent of the apparatus's Internet Protocol (IP) address. In one embodiment of this application, the identifier of the apparatus is a General Public Subscription Identifier (GPSI). In one embodiment of this application, the first server is an Edge Application Server (EAS), and the second server is an Edge Enabler Server (EES). In one embodiment of this application, the identification information is associated with an identifier of an Edge Enabler Client (EEC) in the apparatus.

[0018] In one embodiment of this case, an apparatus for wireless communication includes: a component for receiving identification information associated with a user equipment (UE) from the user equipment (UE), wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address; a component for receiving a service request from the application server including at least the symbol and the identifier of the application server, wherein the apparatus includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE; and a component for transmitting a message responding to the service request to the application server. In one embodiment of this application, the apparatus for wireless communication also includes: a component for responding to the service request by determining at least one of the EEC ID or the UE identifier based on the symbol, the application server identifier, and the mapping between the EEC ID, the symbol, the application server identifier, and the UE identifier; and a component for executing the service request based on at least one of the EEC ID or the UE identifier. In another embodiment of this application, the apparatus for wireless communication also includes: a component for generating a table including the mapping between the symbol, the application server identifier, and the UE identifier. In another embodiment of this application, the UE identifier is a General Public Subscription Identifier (GPSI) or the symbol.

[0019] In one embodiment of this case, the device for wireless communication also includes: a component for assigning a second identifier to the UE; and a component for transmitting the second identifier of the UE to the application server; wherein the mapping between the Edge Enabler Client ID (EEC ID), the symbol, the application server's identifier, and the UE's identifier maps the second identifier of the UE to the Edge Enabler Client ID (EEC ID), the symbol, the application server's identifier, and the UE's identifier. In one embodiment of this case, the device for wireless communication also includes: a component for receiving a network address of a first server configured to provide public network address information associated with the device; a component for transmitting a request for the public network address information associated with the device to the first server based on the network address; a component for receiving, from the first server, the public network address information associated with the device in response to the request; and a component for transmitting, to a second server in an edge data network, the public network address information associated with the device and the private network address information associated with the device, when network address translation is applied to private network address information associated with the device. In one embodiment of this application, the component for receiving the network address of the first server, configured to provide public network address information associated with the device, is configured to perform at least one of the following operations: receiving the network address of the first server from an entity in the core network via parameters in a Protocol Configuration Option (PCO) Information Element (IE); receiving the network address of the first server from an Edge Configuration Server (ECS) in an Edge Data Network; or receiving the network address of the first server from an Edge Enabler Server (EES) in the Edge Data Network. In one embodiment of this application, the first server is a STUN (Stay-through Utility for NAT) server, and the second server is an Edge Enabler Server (EES). In one embodiment of this application, the device for wireless communication also includes a component for transmitting the device's identifier to the second server. In one embodiment of this application, the device's identifier is a General Public Subscription Identifier (GPSI). In one embodiment of the present invention, the device for wireless communication also includes a component for determining whether network address translation is applied to the private network address information associated with the UE.

[0020] In one embodiment of this application, an apparatus for wireless communication includes: components for receiving public network address information associated with a user equipment (UE) and private network address information associated with the UE from a user equipment (UE); components for receiving a service request from an application server in an edge data network, including at least the public network address information associated with the UE, wherein the apparatus includes a mapping between the private network address information associated with the UE and the public network address information associated with the UE; and components for transmitting a message responding to the service request to the application server in the edge data network. In another embodiment of this application, the apparatus for wireless communication also includes: components for determining the private network address information associated with the UE based on the public network address information associated with the UE and the mapping between the private network address information associated with the UE and the public network address information associated with the UE in response to the service request; and components for executing the service request based on the private network address information associated with the UE.

[0021] In one embodiment of this application, the device for wireless communication also includes: a component for activating a Network Open Functions (NEF) Application Programming Interface (API) based on the private network address information associated with the UE. In another embodiment of this application, the device for wireless communication also includes: a component for transmitting to the UE the network address of a server configured to provide the public network address information associated with the UE. In another embodiment of this application, the device for wireless communication also includes: a component for receiving an identifier of the UE from the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to both the private network address information associated with the UE and the public network address information associated with the UE. In another embodiment of this application, the UE's identifier is a General Public Subscription Identifier (GPSI). In one embodiment of this application, the public network address information associated with the UE includes a first Internet Protocol (IP) address and a first port number, and the private network address information associated with the UE includes a second IP address and a second port number. In another embodiment of this application, the device for wireless communication also includes: a component for assigning an identifier to the UE; and a component for transmitting the UE's identifier to the application server, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to both the private network address information associated with the UE and the public network address information associated with the UE.

[0022] In one embodiment of this case, an apparatus for wireless communication includes: a component for receiving a message from a user equipment (UE) comprising at least one user plane data packet; a component for determining public network address information of the UE based on the message; a component for receiving private network address information associated with the UE from a network address translation (NAT) device; a component for receiving a service request from an application server in an edge data network comprising at least the public network address information associated with the UE, wherein the apparatus includes a mapping between the private network address information associated with the UE and the public network address information associated with the UE; and a component for transmitting a message responding to the service request to the application server in the edge data network. In one embodiment of this application, the device for wireless communication also includes: a component for determining an identifier for the UE based on public network address information associated with the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to both the private network address information associated with the UE and the public network address information associated with the UE. In one embodiment of this application, the UE's identifier is a General Public Subscription Identifier (GPSI). In another embodiment of this application, the device for wireless communication also includes: a component for assigning an identifier to the UE; and a component for transmitting the identifier to the application server; wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the identifier to both the private network address information associated with the UE and the public network address information associated with the UE.

[0023] In one embodiment of this case, a computer-readable medium is provided for storing computer-executable code. When executed by a processor, the code causes the processor to: receive a symbol from a first server in an edge data network; and transmit device-associated identification information to a second server in the edge data network, wherein the identification information includes at least the symbol, a device identifier, and an identifier of the first server, wherein the device identifier is independent of the device's Internet Protocol (IP) address.

[0024] In one embodiment of this invention, a computer-readable medium is provided for storing computer-executable code. When executed by a processor, the code causes the processor to perform the following operations: receive identification information associated with a user equipment (UE) from the UE, wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address; receive a service request from the application server including at least the symbol and the identifier of the application server, wherein the means includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE; and transmit a message responding to the service request to the application server.

[0025] In one embodiment of this case, a computer-readable medium is provided for storing computer-executable code. When executed by a processor, the code causes the processor to: receive a network address of a first server configured to provide public network address information associated with a device; transmit a request to the first server for the public network address information associated with the device based on the network address; receive, from the first server, the public network address information associated with the device in response to the request; and, when network address translation is applied to private network address information associated with the device, transmit the public network address information associated with the device and the private network address information associated with the device to a second server in an edge data network.

[0026] In one embodiment of this invention, a computer-readable medium is provided for storing computer-executable code. When executed by a processor, the code causes the processor to perform the following operations: receive at least public network address information associated with the user equipment (UE) from the UE; receive a service request from an application server in an edge data network that includes at least the public network address information associated with the UE, wherein means include a mapping between private network address information associated with the UE and the public network address information associated with the UE; and transmit a message responding to the service request to the application server in the edge data network.

[0027] In one embodiment of this invention, a computer-readable medium storing computer-executable code is provided. When executed by a processor, the code causes the processor to perform the following operations: receive a message from a user equipment (UE) including at least one user plane data packet; determine public network address information of the UE based on the message; receive private network address information associated with the UE from a network address translation (NAT) device; receive a service request from an application server in an edge data network including at least the public network address information associated with the UE, wherein means include a mapping between the private network address information associated with the UE and the public network address information associated with the UE; and transmit a message responding to the service request to the application server in the edge data network.

[0028] To achieve the foregoing and related objectives, one or more forms include the features fully described below and specifically pointed out in the claims. The following description and figures illustrate certain illustrative features of one or more forms in detail. However, these features indicate only a few of the various ways in which the principles of the various forms may be employed, and the description is intended to include all such forms and their equivalents. Simple Explanation of the Diagram

[0029] Figure 1 is a schematic diagram illustrating an example of a wireless communication system and access network.

[0030] Figures 2A, 2B, 2C, and 2D are schematic diagrams illustrating examples of the DL channel within the first 5G / NR frame, the DL channel within the 5G / NR sub-frame, the UL channel within the second 5G / NR frame, and the UL channel within the 5G / NR sub-frame, respectively.

[0031] Figure 3 is a schematic diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0032] Figure 4 is a schematic diagram illustrating an exemplary network architecture including a UE, a radio access network, a core network, a network address translation (NAT) device, and an edge data network.

[0033] Figure 5 is a schematic diagram illustrating an exemplary network architecture including a UE, a radio access network, a core network, a network address translation (NAT) device, and an edge data network.

[0034] Figure 6 is a signal flow diagram of various states based on the content of this case.

[0035] Figure 7 is a schematic diagram illustrating an exemplary network architecture including a UE, a core network, a STUN (Standardization-through-Network) server for NAT, and an edge data network.

[0036] Figure 8 (including Figure 8A and Figure 8B) illustrates the signal flow diagrams for each state according to the content of this case.

[0037] Figure 9 is a schematic diagram illustrating an exemplary network architecture including a UE, core network, NAT server, and edge data network.

[0038] Figure 10 illustrates the signal flow diagrams for each state according to the content of this case.

[0039] Figure 11 is a flowchart of a wireless communication method.

[0040] Figure 12 is a flowchart of a wireless communication method.

[0041] Figure 13 is a conceptual data flow diagram illustrating the data flow between different components / elements in an exemplary device.

[0042] Figure 14 is a schematic diagram illustrating an example of the hardware implementation of a device employing a processing system.

[0043] Figure 15 is a flowchart of a wireless communication method.

[0044] Figure 16 is a flowchart of a wireless communication method.

[0045] Figure 17 is a flowchart of a wireless communication method.

[0046] Figure 18 is a conceptual data flow diagram illustrating the data flow between different components / elements in an exemplary device.

[0047] Figure 19 is a schematic diagram illustrating an example of hardware implementation for a device employing a processing system. Implementation

[0048] The detailed descriptions below, illustrated with reference to the accompanying drawings, are intended to describe various configurations, and not to represent the only configurations in which the concepts described herein can be implemented. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, it will be apparent to those skilled in the art that these concepts can be implemented without such specific details. In some instances, well-known structures and components are illustrated in block diagram form to avoid obscuring these concepts.

[0049] Various apparatuses and methods will now be used to present several prototypes of telecommunications systems. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings, using various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0050] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" that includes one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, individual hardware circuits, and other suitable hardware configured to perform the various functions described throughout this document. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted to mean instructions, instruction sets, code, code fragments, code, program, subprogram, software component, application, software application, software suite, convention, sub-convention, object, executable file, executable thread, program, function, etc.

[0051] Accordingly, in one or more exemplary embodiments, the described functions can be implemented using hardware, software, or any combination thereof. If implemented in software, such functions can be stored on a computer-readable medium or encoded as one or more instructions or codes on a computer-readable medium. A computer-readable medium includes computer storage media. Storage media can be any available media accessible by a computer. By way of example, and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electronically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other media capable of storing computer-executable code having an instruction or data structure accessible by a computer.

[0052] Figure 1 is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0053] Base station 102 configured for 4G LTE (collectively referred to as Evolutionary Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of NAS messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), user and device tracking, RAN Information Management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via backhaul link 134 (e.g., X2 interface). Backhaul link 134 can be wired or wireless.

[0054] Base station 102 can wirelessly communicate with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network may also include a home evolutionary node B (eNB) (HeNB), which can provide services to a restricted group called a closed user group (CSG). The communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth allocated to each carrier in carrier aggregation for transmission in each direction. Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. Primary component carriers may be referred to as primary cells (PCells), and secondary component carriers may be referred to as secondary cells (SCells).

[0055] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the physical sideline broadcast channel (PSBCH), physical sideline exploration channel (PSDCH), physical sideline shared channel (PSSCH), and physical sideline control channel (PSCCH). D2D communication can be via a variety of wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0056] The wireless communication system may also include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform an idle channel assessment (CCA) before communication to determine whether the channel is available.

[0057] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as the Wi-Fi AP 150. Employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0058] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum of RF. EHF has a range from 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communication using mmW / near mmW radio frequency bands (e.g., 3 GHz–300 GHz) has extremely high path loss and short range. mmW base station 180 can utilize beamforming 182 with UE 104 to compensate for the extremely high path loss and short range.

[0059] Base station 180 may transmit beamforming signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamforming signals from base station 180 in one or more reception directions 182''. UE 104 may also transmit beamforming signals to base station 180 in one or more transmission directions. Base station 180 may receive beamforming signals from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission and reception directions for base station 180 may be the same or different. The transmission and reception directions for UE 104 may be the same or different.

[0060] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a service gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted via service gateway 166, which itself is connected to PDN gateway 172. PDN gateway 172 provides UE IP address allocation and other functions. PDN gateway 172 and BM-SC 170 are connected to IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide service provisioning and delivery functions for MBMS users. BM-SC 170 can act as an entry point for MBMS transmission by content providers, can be used to authorize and initiate MBMS bearer services within the Public Land Mobile Network (PLMN), and can be used to schedule MBMS transmissions. MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 in a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for communication period management (start / stop) and collection of billing information related to eMBMS.

[0061] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Term Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS procedures and term management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0062] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, base station transceiver, radio base station, radio transceiver, transceiver functional unit, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, SIP phones, laptops, personal digital assistants (PDAs), satellite radio units, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile service client, client, or some other suitable term.

[0063] Referring again to Figure 1, in some configurations, UE 104 can be configured to transmit identification information associated with UE 104 to a server on the edge data network (e.g., an edge enabler server), wherein the identification information of UE 104 is independent of the IP address (198) of UE 104.

[0064] Figure 2A is a schematic diagram 200 illustrating an example of a first sub-frame within a 5G / NR frame structure. Figure 2B is a schematic diagram 230 illustrating an example of a DL channel within a 5G / NR sub-frame. Figure 2C is a schematic diagram 250 illustrating an example of a second sub-frame within a 5G / NR frame structure. Figure 2D is a schematic diagram 280 illustrating an example of a UL channel within a 5G / NR sub-frame. The 5G / NR frame structure can be FDD (where sub-frames within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or TDD (where sub-frames within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). In the examples provided in Figures 2A and 2C, the 5G / NR frame structure is assumed to be TDD, where sub-frame 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and X is flexibly usable between DL and UL, and sub-frame 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having time slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available time slot formats 0-61. Time slot formats 0 and 1 are full DL and full UL, respectively. Other time slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured to have a time slot format via the received Time Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G / NR frame structures as TDD.

[0065] Other wireless communication technologies can have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe can include one or more time slots. Subframes can also include micro-time slots, which can include 7, 4, or 2 symbols. Each time slot can include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot can include 14 symbols, while for time slot configuration 1, each time slot can include 7 symbols. Symbols on the DL can be cyclic prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe can be based on the time slot configuration and numerical scheme. For slot configuration 0, different numerical schemes µ 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerical schemes 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and numerical scheme µ, there are 14 symbols / slot and 2 µ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the numerical scheme. The subcarrier spacing can be equal to 2 µ * 15 kHz, where µ is the numerical scheme from 0 to 5. Therefore, numerical scheme µ=0 has a subcarrier spacing of 15 kHz, and numerical scheme µ=5 has a subcarrier spacing of 480 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A-2D provide examples of slot configuration 0 with 14 symbols per slot and numerical scheme µ=0 with 1 slot per subframe. The subcarrier spacing is 15 kHz, and the symbol duration is approximately 66.7 µs.

[0066] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0067] As shown in Figure 2A, some REs in the REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R x for a specific configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RSs may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0068] Figure 2B illustrates examples of various DL channels within a sub-frame of a frame. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs). Each CCE includes nine RE Groups (REGs), and each REG includes four consecutive REs within an OFDM symbol. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific sub-frame of the frame. The PSS is used by the UE 104 to determine sub-frame / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific sub-frame of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identification Group Number and radio frame timing. Based on the Physical Layer Identification and Physical Layer Cell Identification Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) (which carries the Main Information Block (MIB)) can logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (e.g., System Information Block (SIB)), and paging messages.

[0069] As shown in Figure 2C, some REs in the RE array carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. In different configurations, the PUCCH DM-RS can be transmitted depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. Although not illustrated, the UE can transmit a Sound Reference Signal (SRS). The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0070] Figure 2D illustrates examples of various UL channels within sub-frames of a frame. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0071] Figure 3 is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with: broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reports; PDCP layer functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and delivery support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), and MAC... SDU handles demultiplexing from TB, scheduling information reports, error correction via HARQ, priority processing, and logical channel prioritization.

[0072] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to signal clusters based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be separated into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot frequency) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimate can be derived based on a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0073] At UE 350, each receiver 354RX receives signals via its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can merge these multiple spatial streams into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal clustering point transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. This data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0074] The controller / processor 359 may be associated with memory 360, which stores code and data. Memory 360 may be referred to as computer-readable media. In UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transmission and logic channels to recover IP packets from EPC 160. The controller / processor 359 is also responsible for error detection to support HARQ operation using ACK and / or NACK protocols.

[0075] Similar to the functions described in the DL transmission combined with base station 310, controller / processor 359 provides: RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with: header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transmission channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0076] The TX processor 368 can use the channel estimate derived by the channel estimator 358 based on the reference signal or feedback transmitted from the base station 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0077] At base station 310, UL transmission is processed in a manner similar to that described for the receiver function at UE 350. Each receiver 318RX receives signals via its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0078] The controller / processor 375 may be associated with memory 376 storing code and data. Memory 376 may be referred to as computer-readable media. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logic channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection to support HARQ operation using ACK and / or NACK protocols.

[0079] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 can be configured to perform various states of 198 in conjunction with Figure 1.

[0080] When a mobile network service provider (CNF) does not have enough public Internet Protocol (IP) addresses (e.g., public IPv4 addresses) available for assignment to a UE, the CNF may assign a private IP address (e.g., a private IPv4 address) to the UE. For example, a unique private IPv4 address may be assigned to each UE's modem. Since the private IP address may not be known to networks outside the mobile network (e.g., the Internet), Network Address Translation (NAT) may be required to map the UE's private IP address to a public IP address. However, the mobile network's core network (CN) may not perform NAT and may not be aware of the UE's public IP address. Furthermore, entities within the UE (e.g., modem, Edge Enabler Client (EEC), Application Client (AC)) may not be aware of the UE's public IP address.

[0081] In edge computing, entities in an edge data network (such as Edge Application Servers (EAS) and Edge Enabler Servers (EES)) can communicate using one or more Application Programming Interfaces (APIs) (also known as EDGEAPP APIs). The EDGEAPP API defined between the EAS and EES typically uses the UE's IP address as the API key. For example, an entity in the edge data network can obtain the UE's IP address from the UE's Application Client (AC) or Edge Enabler Client (EEC). The EEC and EES can identify the EEC without using the UE's IP address.

[0082] Therefore, in some scenarios where Network Address Translation (NAT) is deployed between the mobile network (e.g., the 3GPP core network (CN)) and the edge data network, the EEC may provide the UE's private IP address to the EES, and the EAS may only know the UE's public IP address in the data packets received from the Access Client (AC) (e.g., due to NAT). In such scenarios, the mismatch between the UE's public and private IP addresses at the EAS and EES may hinder the functionality of the EDGEAPP API between the EAS and EES.

[0083] Application service providers typically do not identify a UE based on its IP address, as the UE's IP address can change at any time (e.g., Wi-Fi to cellular transition). In some instances, when a user initially accesses a service supported by the EAS, the EAS and the user (e.g., the UE) can exchange tokens. For example, a token can be a unique value (e.g., a unique literal value) based on login information such as a username and / or password created by the user. Subsequently, the edge data network can use the token to identify the user (e.g., the UE).

[0084] In some instances, if the EAS and EES at the edge data network can identify the UE's EEC using the tokens exchanged between the application client (AC) and the EAS, the problems associated with identifying the UE using the UE's public IP address at the edge data network can be overcome (e.g., when NAT is deployed between the core network (CN) and the edge data network).

[0085] Figure 4 is a schematic diagram illustrating an exemplary network architecture 400 including a user equipment (UE) 410, a radio access network 430, a core network 440, a network address translation (NAT) server 450, and an edge data network 460.

[0086] UE 410 includes an application processor 412 and a modem 420. The application processor 412 includes an application client (AC) 414, and the modem 420 includes an edge enabler client (EEC) 422, a non-access stratum (NAS) protocol layer 424, and an access stratum protocol layer 426. An EDGE-5 reference point 416 (also referred to as the EDGE-5 interface) enables interaction between the application client (AC) 414 and the edge enabler client (EEC) 422.

[0087] Application client (AC) 414 may be an application that executes in application processor 412 and performs client functions. Edge enabler client (EEC) 422 provides the support functions required by application client (AC) 414. For example, support functions may include obtaining and supplying configuration information to enable the exchange of application data traffic 472 with edge application server (EAS) 462 and exploring edge application servers (EAS) available in edge data network 460.

[0088] Radio access network 430 includes at least one base station, such as base station 432. UE 410 and base station 432 can transmit data via radio signal transmission 478.

[0089] The core network 440 includes a first network device 442 (also referred to as a first network node) and a second network device 444 (also referred to as a second network node). In some instances, the core network 440 may be a 3GPP core network. The first network device 442 implements User Plane Function (UPF) 443, and the second network device 444 implements Access and Mobility Management Function (AMF) 446 and Communication Period Management Function (SMF) 448. The UE 410 may transmit control information with AMF 446 and / or SMF 448 via NAS signaling 477.

[0090] Edge data network 460 may include an edge application server (EAS) 462, an edge enabler server (EES) 464, and an edge configuration server (ECS) 466. EAS 462 may be an application server within edge data network 460 configured to perform server functions. Application client (AC) 414 may connect to EAS 462 to access the features of edge computing. In some instances, EAS 462 may interact with core network 440 by directly invoking core network function APIs (e.g., if it is an entity trusted by core network 440) and / or by invoking core network capabilities via EES 464.

[0091] EES 464 provides support functions for EAS 462 and Edge Enabler Client (EEC) 422. For example, EES 464 can supply configuration information to Edge Enabler Client (EEC) 422 and can exchange application data traffic with EAS 462. EEC 422 and EES 464 can communicate via Edge Signal Transmission 476 on EDGE-1 reference point 474.

[0092] In some instances, EES 464 supports API driver functionality and API opening capabilities. In some instances, EES 464 supports external access to the core network 440 and service capabilities to EAS 462 at EDGE-3 reference point 468. In some instances, EES 464 supports functions associated with registration for Edge Enabler Client (EEC) 422 and EAS 462, such as registration procedures, registration updates, and / or deregistration operations.

[0093] The Edge Configuration Server (ECS) 466 provides support functionality for the Edge Enabler Client (EEC) 422 to connect to the EES 464. In some instances, the Edge Configuration Server (ECS) 466 supplies edge configuration information to the Edge Enabler Client (EEC) 422. For example, the edge configuration information may include information for the Edge Enabler Client (EEC) 422 to connect to the EES 464 and / or information for establishing a connection with the EES 464 (such as Uniform Resource Identifiers (URIs)). In some instances, the Edge Configuration Server (ECS) 466 supports functionality associated with registration for the EES 464, such as registration procedures, registration updates, and / or deregistration operations.

[0094] UE 410 may be assigned a private network address 428 (e.g., a private Internet Protocol (IP) address and port number), which may be a network address translated via a Network Address Translation (NAT) server 450. The translated network address may serve as UE 410's public network address 452 (e.g., a public Internet Protocol (IP) address and port number). In some instances, UE 410 may know its private network address but not its public network address 452. For example, entities within UE 410 (such as AC 414 and EEC 422) may know the private network address 428 but may not know the public network address 452.

[0095] Figure 5 is a schematic diagram of the exemplary network architecture (e.g., edge data network architecture 400) illustrated in Figure 4, which includes a UE 410, a radio access network 430, a core network 440, a network address translation (NAT) server 450, and an edge data network 460. In some instances, and as described in detail herein, EES 464 can generate an EEC identification table, which includes a mapping between at least private network addresses and public network addresses of the UE 410. For example, as shown in Figure 5, EES 464 can generate an EEC identification table 510.

[0096] Figure 6 is a signal flow diagram 600 for various states according to the content of this case. The signal flow diagram 600 includes UE 410, EES 464 and EAS 462. UE 410 includes AC 414 and EEC 422.

[0097] AC 414 transmits a message 602 to EAS 462 including a request for a token. In some instances, a network API for anonymous client reference management (e.g., NetAPI:ACR) can be used to initiate the request for a token. At 604, EAS 462 generates a token. In some instances, the token may be an Open Action Alliance (OMA) Anonymous Client Reference (ACR) (abbreviated herein as OACR). In such instances, EAS 462 may generate a token by assigning an OACR to AC 414. EAS 462 transmits a message 606 to AC 414 including a token (e.g., OACR).

[0098] AC 414 receives message 606 containing a token and transmits message 608, including the token and application identifier (ID), to EEC 422 via EDGE-5 API 416 (also known as EDGE-5 reference point). In some instances, message 608 may include information elements (IEs) containing the following: token, application identifier (ID), and EAS 462 identifier (ID) (also known as edge application server ID and EAS ID). EEC 422 receives message 608 and, at 610, determines the EAS 462 identifier (ID) based on the information elements (IEs) in message 608.

[0099] EEC 422 can transmit message 612, which includes a symbol, an identifier for UE 410 (also referred to as the UE identifier and UE ID), and an identifier for EAS 462. For example, EEC 422 can transmit message 612 to EES 464. In some instances, the identifier for UE 410 can be a Common Public Subscription Identifier (GPSI) associated with UE 410. A GPSI is a public identifier that can be used both inside and outside a 3GPP system (e.g., Radio Access Network 430 and Core Network (CN) 440 in Figure 5). For example, a GPSI can be used for subscriptions in different data networks addressed outside of Core Network (CN) 440. In some instances, a GPSI can be a Mobile Subscriber Integrated Services Digital Network (ISDN) number (MSISDN) or an external identifier. In some instances, EEC 422 can provide the GPSI via an edge application server (EAS) exploration API or a new API. In some scenarios, if the Edge Enabler Client (EEC) 422 does not provide the GPSI associated with the UE 410, the EES 464 may trigger an API for obtaining the GPSI (e.g., the IP addr-GPSI translation API).

[0100] At 614, EES 464 may assign an optional identifier (also referred to herein as an optional UE identifier, optional UE ID, and edge UE ID) to UE 410. EES 464 may transmit message 616 to EAS 462 including the optional identifier of UE 410. In some instances, when EAS 462 triggers an API defined between EES 464 and EAS 462 (such as an API for requesting the identity of UE 410 (e.g., the identifier of UE 410)), EES 464 may transmit message 616 including the optional identifier of UE 410. When other APIs defined between EES 464 and EAS 462 are triggered, EAS 462 may use the optional identifier of UE 410. Such APIs defined between EES 464 and EAS 462 may be referred to as EDGE-3 APIs. In some instances, the optional identifier for UE 410 may be the GPSI of UE 410 or a symbol in message 612.

[0101] At point 618, EES 464 generates an EEC identification table (e.g., EEC identification table 510 in Figure 5). In some instances, the EEC identification table may include one or more EEC IDs and a mapping between each EEC ID and its corresponding symbol, EAS identifier, and / or UE identifier. In some versions of this work, optional UE identifiers may be mapped to EEC IDs in the EEC identification table. In some instances, different symbols or different UE IDs (EEC ID, edge UE ID) may address the same UE. An exemplary EEC identification table generated at point 618 is shown in Table 1.

[0102] Table 1 EEC ID Symbols EAS ID UE ID Optional UE ID (e.g., edge UE ID) EEC ID1 OACR1 EAS ID1 918369110173 1 EEC ID2 OACR2 EAS ID2 123@berlin.de 2 EEC ID3 OACR3 EAS ID3 456@seoul.kr 3 EEC ID3 OACR4 EAS ID4 789@sandiego.us 3

[0103] In Table 1, each row indicates the mapping between the EEC identifier (EEC ID) and its corresponding symbol in the UE, the EAS identifier (EAS ID), and the UE identifier (UE ID). As shown in Table 1, optional identifiers of the UE (e.g., edge UE ID) can be mapped to EEC IDs.

[0104] In an exemplary scenario, referring to Table 1 and Figure 6, the identifier of EEC 422 in UE 410 can be represented as "EEC ID1", the symbol in message 612 can be represented as "OACR1", the identifier (EAS ID) of EAS 462 can be represented as "EAS ID1", the identifier of UE 410 can be represented as "918369110173", and the optional identifier of UE 410 (e.g., edge UE ID) can be represented as "1". As described herein, for example, EES 464 can receive the symbol (e.g., OACR1), the identifier of EAS 462 (e.g., EAS ID1), and the identifier of UE 410 (e.g., 918369110173) in message 612.

[0105] As shown in Figure 6, EAS 462 can transmit message 620, which includes a service request. In some instances, the service request can invoke an API (also known as the EDGE-3 API) defined between EAS 462 and EES 464. EAS 462 can include at least a symbol and an identifier of EAS 462 (EAS ID) in message 620 to enable the API to be executed at EES 464.

[0106] At 622, EES 464 can determine the identifier of EEC 422 and / or the identifier of UE 410 based on the EEC identification table (e.g., the exemplary EEC identification table shown in Table 1) and the identifier of EAS 462 (EAS ID) included in message 620. For example, EES 464 can match the identifier of EAS 462 (EAS ID) received in message 620 with the identifier of EAS 462 (EAS ID) in the EEC identification table. In one instance, referring to Table 1, if the identifier of EAS 462 (EAS ID) received in message 620 is "OACR1" and "EAS ID1" respectively, then EES 464 can find "OACR1" and "EAS ID1" in Table 1 and can determine that the EEC ID corresponding to "OACR1" and "EAS ID1" is "EEC ID1". In some instances, EES 464 can determine that the UE ID corresponding to "OACR1" and "EAS ID1" is "918369110173". In some instances, EES 464 can determine that the optional UE ID (e.g., edge UE ID) corresponding to "OACR1" and "EAS ID1" is "1". It should be noted that neither the public IP address nor the private IP address of UE 410 is used by EES 464 to identify UE 410.

[0107] At 624, EES 464 can execute a service request from EAS 462 based on the identifier of EEC 422 (e.g., the identifier of EEC 422 determined at 622). In other instances, EES 464 can execute a service request from EAS 462 based on the identifier of EEC 422 (e.g., the identifier of EEC 422 determined at 622) and / or the identifier of UE 410. EES 464 can respond to the service request in message 620 by transmitting message 626 to EAS 462.

[0108] An example of a service request from EAS 462 will now be described. In one example, the service request in message 620 could be an EDGE-3 API requesting the location of UE 410. In response to the service request, EES 464 can determine the identifier of EEC 422 (e.g., EEC ID1) and the identifier of UE 410 (e.g., GPSI value 918369110173) based on the EEC identification table (e.g., Table 1), and can execute a 3GPP network API to obtain the location of UE 410 using the identifier of UE 410 (e.g., GPSI value 918369110173). The 3GPP network can return information indicating the location of UE 410 and the identifier of UE 410. EES 464 can include the information indicating the location of UE 410 in response message 626.

[0109] In some instances, as long as the notation between the AC (e.g., AC 414) and EAS (e.g., EAS 462) remains valid, the mapping between the EEC ID and its corresponding notation, the EAS identifier, and / or the UE identifier in the EEC identification table (e.g., Table 1) can remain valid. In some instances, when the EES 464 triggers the Network Open Functions (NEF) Application Programming Interface (API) for the EEC 422, the EES 464 can use the GPSI corresponding to the EEC ID.

[0110] In some scenarios, if the communication period between AC 414 and EAS 462 is released, or if the tokens exchanged between AC 414 and EAS 462 (e.g., OACR) expire, the EEC identification table can be updated by repeating steps 602 to 618 in Figure 6.

[0111] In some scenarios, EEC 422 may not be able to provide GPSI to EES 464. In such scenarios, EES 464 can use APIs configured to provide GPSI for EEC 422 based on EEC 422 IP addresses (e.g., SA2 NEF GPSI-IP Address Translation API). However, if a Network Address Translation (NAT) server is implemented between the core network and the edge data network, such APIs may not provide GPSI because the API requires non-translated (e.g., non-NAT) IP addresses. The variants described herein overcome such problems arising from the implementation of Network Address Translation (NAT) between the core network and the edge data network.

[0112] Figure 7 is a schematic diagram illustrating an exemplary network architecture 700 including a user equipment (UE) 710, a core network 720, a communication time-travel utility (STUN) server 730 for NAT, and an edge data network 740.

[0113] UE 710 includes an Edge Enabler Client (EEC) 712 and a Non-Access Layer (NAS) protocol layer 714. UE 710 may include additional components that have been omitted for ease of description, such as an application processor and a modem device in which the EEC 712 may reside.

[0114] EEC 712 provides the support functions required by application clients in UE 710. For example, support functions may include obtaining and supplying configuration information to enable the exchange of application data traffic with EAS 742 and the exploration of EAS available in the edge data network 740.

[0115] The core network 720 includes network equipment 722 (also known as a network node). In some instances, the core network 720 may be a 3GPP core network. Network equipment 722 implements Access and Mobility Management Function (AMF) 723 and Communication Management Function (SMF) 725. The UE 710 can transmit control information with AMF 723 and / or SMF 725 via NAS signaling 764.

[0116] Edge data network 740 may include an edge application server (EAS) 742, an edge enabler server (EES) 744, and an edge configuration server (ECS) 750. EAS 742 may be an application server configured within edge data network 740 to perform server functions. Application clients in UE 710 may connect to EAS 742 to access edge computing features. In some instances, EAS 742 may interact with core network 720 by directly invoking core network function APIs (e.g., if it is an entity trusted by core network 720) and / or by invoking core network capabilities via EES 744.

[0117] EES 744 provides support functions for EAS 742 and EEC 712. For example, EES 744 can supply configuration information to EEC 712 and can exchange application data traffic with EAS 742. In some instances, EES 744 supports API driver functionality and API opening functionality. In some instances, EES 744 supports external access to the core network 720 and service capabilities to EAS 742 at EDGE-3 reference point 748. In some instances, EES 744 supports functions associated with registration for EEC 712 and EAS 742, such as registration procedures, registration updates, and / or deregistration operations.

[0118] The ECS 750 provides support for connectivity between the EEC 712 and EES 744. In some instances, the ECS 750 provides edge configuration information to the EEC 712. For example, edge configuration information may include information for the EEC 712 to connect to the EES 744 and / or information for establishing a connection with the EES 744 (such as Uniform Resource Identifiers (URIs)). In some instances, the ECS 750 supports functions associated with registration for the EES 744, such as registration procedures, registration updates, and / or deregistration operations. The ECS 750 can communicate with the EES 744 via EDGE-6 reference point 752.

[0119] UE 710 may be assigned a private network address (e.g., a private Internet Protocol (IP) address and port number), which may be a network address translated via a Network Address Translation (NAT) server 735. The translated network address can serve as the public network address (e.g., a public Internet Protocol (IP) address and port number) of UE 710. In some instances, UE 710 may know its private network address but not its public network address. For example, an entity in UE 710 (such as EEC 712) may know its private network address but may not know its public network address.

[0120] In some instances, and as described in detail herein, EES 744 can generate an EEC identification table that includes a mapping between at least private network addresses and public network addresses of the UE 710. For example, as shown in the Edge Data Network Architecture 700, EES 744 can generate an EEC identification table 746.

[0121] The EEC 712 can communicate with the STUN server 730 via the STUN interface 754. For example, the STUN interface 754 can use the STUN protocol, which allows a client (e.g., the EEC 712) to explore the presence and type of NAT between the client and an external network (e.g., the Internet). In some instances, the STUN server 730 can enable the client to explore the mapping between the client's private network address information (e.g., private IP address and port number) and the client's corresponding public network address information (e.g., public IP address and port).

[0122] Figure 8 (including Figures 8A and 8B) illustrates a signal flow diagram 800 for various states according to the content of this case. Signal flow diagram 800 includes UE 710, core network 722, STUN server 730, EAS 742, EES 744, and ECS 750. UE 710 includes NAS protocol layer 714 and EEC 712.

[0123] Signal flow diagram 800 includes optional communications 810, 820, and 830 for supplying the network address of STUN server 730 (also referred to as the STUN server address) to UE 710. Therefore, it should be understood that if one of the optional communications 810, 820, and 830 is performed and UE 710 is able to receive the network address of STUN server 730, the remaining optional communications may not be necessary. For example, if UE 710 is able to receive the network address of STUN server 730 using optional communication 810, optional communications 820 and 830 may be skipped.

[0124] In one example, referring to optional communication 810 in Figure 8A, the core network 720 can provide the network address of the STUN server 730 to the EEC 712 via NAS message 812 at the NAS protocol layer 714. The EEC 712 can then receive the network address of the STUN server 730 via NAS message 814. In some examples, entities in the core network 720 (e.g., AMF and / or SMF) can include the network address of the STUN server 730 in the NAS message 812 using new parameters in the Protocol Configuration Options (PCO) Information Element (IE). In some examples, the NAS message 814 including the network address of the STUN server 730 can be a NAS (upper layer) AT command (e.g., a modem command).

[0125] In another instance, referring to optional communication 820 in Figure 8A, the ECS 750 can provide the network address of the STUN server 730 to the EEC 712 in message 822 during service provisioning. In some instances, referring to Figure 7, the ECS 750 can use edge signaling 762 on EDGE-4 reference point 760 to transmit message 822.

[0126] In another example, referring to optional communication 830 in Figure 8A, EEC 712 can transmit message 832 to EES 744 including an indication of STUN server support (also referred to as STUN server support indication). In some instances, EES 744 can be pre-configured with the network address of STUN server 730, can be supplied with the network address of STUN server 730, or can be configured to obtain the network address of STUN server 730. EES 744 can respond to message 832 by transmitting message 834 including the network address of STUN server 730. In some instances, messages 832 and 834 can be exchanged between EEC 712 and EES 744 during the registration process between EEC 712 and EES 744. In some instances, referring to Figure 8A, EEC 712 and EES 744 can use edge signal transmission 758 on EDGE-1 reference point 756 to exchange messages 832, 834.

[0127] Referring to Figure 8B, the EEC 712 of UE 710 can transmit message 836, which includes private network address information associated with UE 710, to STUN server 730. For example, EEC 712 can use the network address of the STUN server received via one of optional communications 810, 820, or 830 to transmit message 836 to STUN server 730. STUN server 730 can use the private network address information associated with UE 710 to transmit message 838 to EEC 712, where message 838 includes public network address information associated with UE 710. In some instances, the public network address information associated with UE 710 includes a first Internet Protocol (IP) address and a first port number, and the private network address information associated with UE 710 includes a second IP address and a second port number.

[0128] At 840, EEC 712 determines whether Network Address Translation (NAT) is applied to the private network address information associated with UE 710. In some instances, EEC 712 may compare the private network address information associated with UE 710 with the public network address information in message 838. If the private network address information associated with UE 710 matches the public network address information in message 838, EEC 712 may determine that NAT is not applied. If the private network address information associated with UE 710 does not match the public network address information in message 838, EEC 712 may determine that NAT is applied.

[0129] UE 710 can transmit message 842 to EES 744. In some instances, when EEC 712 has determined (e.g., at 840) that Network Address Translation (NAT) is applied, EEC 712 may include both private network address information associated with UE 710 and public network address information associated with UE 710. In other instances, when EEC 712 has determined (e.g., at 840) that Network Address Translation (NAT) is not applied, EES 744 may include private network address information associated with UE 710.

[0130] In some instances, message 842 may also include the first identifier of UE 710 (also referred to as UE ID_1). In some instances, the first identifier of UE 710 may be the GPSI of UE 710. If EEC 712 does not include the first identifier of UE 710 (e.g., the GPSI of UE 710) in message 842, then EES 744 may use the private network address information associated with UE 710 as the key for triggering the GPSI translation API with core network 720.

[0131] In some instances, the EEC 712 may transmit message 842 during the EAS exploration process with the EES 744, during the registration process with the EES 744, and / or via one or more new EDGE-1 APIs. For example, one or more new EDGE-1 APIs may include an API for identifying the EEC 712 (also known as the EEC Identifier API).

[0132] At position 844, EES 744 generates an EEC identification table. In some instances, the EEC identification table may include one or more private network address information entries (e.g., private Internet Protocol (IP) addresses and port numbers) and a mapping between each private network address information entry and the corresponding public network address information entry (e.g., public Internet Protocol (IP) addresses and port numbers). In some instances, the EEC identification table may optionally include a first identifier of UE 710 (also referred to as UE ID_1) and / or a second identifier of UE 710 (also referred to as UE ID_2).

[0133] In some instances, the second identifier of UE 710 (e.g., UE ID_2) can be an edge UE ID assigned by EES 744. For example, EES 744 can assign an edge UE ID to UE 710 and can provide the edge UE ID to EAS 742. In some instances, when EAS 742 triggers an API defined between EES 744 and EAS 742 to request the identity of UE 710 (e.g., the identifier of UE 710), EES 744 can provide the edge UE ID to EAS 742. In some instances, EAS 742 can use the edge UE ID of UE 710 when other APIs defined between EES 744 and EAS 742 are triggered. Such APIs defined between EES 744 and EAS 742 can be referred to as EDGE-3 APIs. In some instances, the edge UE ID of UE 710 can be the GPSI of UE 710.

[0134] The first identifier and / or the second identifier of UE 710 can be mapped to private network address information entries in the EEC identification table. An example EEC identification table generated at 844 is shown in Table 2.

[0135] Table 2 UE private network address information UE Public Network Address Information UE ID_1 (Optional) UE ID_2 (Optional) 192.168.1.1:1111 190.1.1.1:1111 918369110173 1 192.168.1.2:1113 190.1.1.1:1114 123@berlin.de 2 192.168.1.3:1811 190.1.1.3:1811 456@seoul.kr 3 192.168.1.4:1711 190.1.1.4:1711 789@sandiego.us 4

[0136] In Table 2, each row indicates the mapping between the UE's private network address information and the UE's corresponding public network address information. As shown in Table 2, the UE's first optional identifier (e.g., UE ID_1) and the UE's second optional identifier (e.g., UE ID_2) can be mapped to the UE's private network address information.

[0137] In an exemplary scenario, referring to Table 2 and Figure 8, the private network address information of UE 710 may include a private Internet Protocol (IP) address and port number represented as "192.168.1.1:1111", a public Internet Protocol (IP) address and port number represented as "190.1.1.1:1111", a first identifier of UE 710 represented as "918369110173" (e.g., UE ID_1), and a second identifier of UE 710 represented as "1" (e.g., UE ID_2). As described herein, for example, EES 464 may receive the private and public network address information of UE 710 and optionally receive the first identifier of UE 710 (e.g., "918369110173") in message 842.

[0138] As shown in Figure 8B, EAS 742 can transmit message 846, which includes a service request. In some instances, the service request can trigger an API (also known as the EDGE-3 API) defined between EAS 742 and EES 744. EAS 742 can include at least the public network address information of UE 710 in message 846.

[0139] At 848, EES 744 can identify EEC 712 by determining the private network address information of UE 710 and / or the identifier of UE 710 (e.g., UE ID_1 and / or UE ID_2 associated with UE 710) based on an EEC identification table (e.g., an exemplary EEC identification table shown in Table 2). For example, EES 744 can match the public network address information of UE 710 received in message 846 with the public network address information entries in the EEC identification table. Subsequently, EES 744 can determine the private network address information corresponding to the public network address information of UE 710 that matches in the EEC identification table.

[0140] In one instance, referring to Table 2, if the public network address information of UE 710 received in message 846 is "190.1.1.1:1111", then EES 744 can find "190.1.1.1:1111" in Table 2 and determine that the private network address information of UE 710 corresponding to "190.1.1.1:1111" is "192.168.1.1:1111". In some instances, EES 744 can optionally determine that the first identifier (e.g., UE ID_1) of UE 710 corresponding to "190.1.1.1:1111" is "918369110173". In some instances, EES 744 may optionally determine that the second identifier (e.g., UE ID_2) of the UE 710 corresponding to "190.1.1.1:1111" is "1".

[0141] At 850, EES 744 can execute a service request from EAS 742 based on the private network address information of UE 710 (e.g., "192.168.1.1:1111"). For example, EES 744 can use the private network address information of UE 710 when activating the Network Open Functions (NEF) Application Programming Interface (API). In other instances, EES 744 can execute a service request from EAS 742 based on the UE's first and / or second identifiers (e.g., UE ID_2, UE ID_2). EES 744 can respond to the service request in message 846 by transmitting message 852 to EAS 742.

[0142] An example of a service request from EAS 742 will now be described. In one example, the service request in message 846 could be an EDGE-3 API requesting the location of UE 710, and the public network address information of UE 710 included in message 846 (e.g., "190.1.1.1:1111") could serve as the key for the service request (e.g., for the EDGE-3 API requesting the location of UE 710). In response to the service request, EES 744 can determine the private network address information of UE 710 based on the EEC identification table (e.g., Table 2), and can use the private network address information of UE 710 (e.g., "192.168.1.1:1111") as the key for the 3GPP network API to execute the 3GPP network API to obtain the location of UE 710. The 3GPP network can return information indicating the location of UE 710. EES 744 may include information indicating the location of UE 710 in response message 852.

[0143] Figure 9 is a schematic diagram illustrating an exemplary network architecture 900 including a user equipment (UE) 910, a core network 920, a NAT server 930, and an edge data network 940.

[0144] UE 910 includes an Edge Enabler Client (EEC) 912. UE 910 may include additional components that have been omitted for ease of description, such as an application processor and a modem device in which the EEC 912 may reside.

[0145] EEC 912 provides the support functions required by application clients in UE 910. For example, support functions may include obtaining and providing configuration information to enable the exchange of application data traffic with EAS 942, and exploring the EAS available in the edge data network 940. In some instances, the core network 920 may be a 3GPP core network.

[0146] Edge data network 940 may include EAS 942, EES 944, and ECS 950. EAS 942 may be an application server in edge data network 940 configured to perform server functions. EAS 942 may communicate with core network 920 over EDGE-7 reference point 954. Application clients in UE 710 may connect to EAS 942 to access edge computing features. In some instances, EAS 942 may interact with core network 920 by directly invoking core network function APIs (e.g., if it is an entity trusted by core network 920) and / or by invoking core network capabilities via EES 944.

[0147] The EES 944 provides support functions for the EAS 942 and EEC 912. For example, the EES 944 can supply configuration information to the EEC 912 and can exchange application data traffic with the EAS 942. The EES 944 can communicate with the EEC 912 via the edge signaling relay 958 on the EDGE-1 reference point 956. The EES 944 can communicate with the core network 920 via the external open signaling relay 962 on the EDGE-2 reference point 960. The EES 944 can communicate with the NAT server 930 via the interface 964.

[0148] In some instances, EES 944 supports API driver functionality and API opening capabilities. In some instances, EES 944 supports external access to the core network 920 and service capabilities to EAS 942 at EDGE-3 reference point 946. In some instances, EES 944 supports functions associated with registration for EEC 912 and EAS 942, such as registration procedures, registration updates, and / or deregistration operations.

[0149] The ECS 950 provides support for connectivity between the EEC 912 and EES 944. In some instances, the ECS 950 supplies edge configuration information to the EEC 912. For example, edge configuration information may include information for the EEC 912 to connect to the EES 944 and / or information for establishing a connection with the EES 944 (such as Uniform Resource Identifiers (URIs)). In some instances, the ECS 950 supports functions associated with registration with the EES 944, such as registration procedures, registration updates, and / or deregistration. The ECS 950 can communicate with the EES 944 via EDGE-6 reference point 952.

[0150] UE 910 may be assigned a private network address (e.g., a private Internet Protocol (IP) address and port number), which may be a network address translated via a Network Address Translation (NAT) server 930. The translated network address can serve as the public network address (e.g., a public Internet Protocol (IP) address and port number) of UE 910. In some instances, UE 910 may know its private network address but not its public network address. For example, an entity in UE 910 (such as EEC 912) may know its private network address but may not know its public network address.

[0151] In some instances, and as described in detail herein, EES 944 can generate an EEC identification table that includes a mapping between at least private network addresses and public network addresses of the UE 910. For example, as shown in the Edge Data Network Architecture 900, EES 944 can generate an EEC identification table 948.

[0152] Figure 10 illustrates the signal flow diagram 1000 for each state according to the content of this case. The signal flow diagram 1000 includes UE 910, NAT server 930, EES 944, and EAS 942. UE 710 includes EEC 912.

[0153] In some instances, the EEC 912 can perform a registration procedure with the EES 944. For example, during the registration procedure, the EEC 912 can transmit registration message 1002 to the EES 944. In some instances, registration message 1002 may include the first identifier of the UE 910 (also referred to as UE ID_1). In some instances, the first identifier of the UE 910 may be the GPSI of the UE 910. In some instances, the EEC 912 may include private network address information associated with the UE 910 in registration message 1002.

[0154] NAT server 930 can receive registration message 1002. In some instances, registration message 1002 may include one or more data packets (e.g., user plane (UP) data packets). The user plane (UP) protocol of the one or more data packets may include public network address information associated with UE 910. For example, the user plane (UP) protocol of the one or more data packets may define fields configured to carry public network address information associated with UE 910 (e.g., in one or more data packets). In some instances, the public network address information associated with UE 910 may be provided by NAT server 930. NAT server 930 may forward registration message 1002 to EES 944.

[0155] At 1006, EES 944 determines the public network address information of UE 910 based on registration message 1002. In some instances, EES 944 derives the public network address information associated with UE 910 (e.g., public IP address and port number of UE 910) based on the UP protocol used for registration message 1002.

[0156] At 1007, EES 944 determines whether Network Address Translation (NAT) has been applied to the public network address information of UE 910 determined at 1006. As mentioned above, in some instances, EEC 912 may include private network address information associated with UE 910 in registration message 1002. In such instances, at 1007, EES 944 may determine whether NAT has been applied to the public network address information determined at 1006 by comparing the public network address information determined at 1006 with the private network address information associated with UE 910.

[0157] If the public network address information determined at 1006 does not match the private network address information associated with UE 910, EES 944 may transmit message 1008 to NAT server 930 including a request (e.g., a query) for the private network address information of UE 910. In some instances, this request may be based on the public network address information of UE 910 (e.g., message 1008 may include the public network address information of UE 910). For example, EES 944 may transmit message 1008 to determine at NAT server 930 the private network address information of UE 910 associated with the public network address information of UE 910. NAT server 930 may transmit message 1010 including the private network address information associated with UE 910 (e.g., the private IP address and port number of UE 910).

[0158] It should be understood that if the public network address information determined at 1006 does not match the private network address information associated with UE 910, then EES 944 can determine that Network Address Translation (NAT) is applied. Furthermore, if the public network address information determined at 1006 matches the private network address information associated with UE 910, then EES 944 can determine that NAT is not applied. Therefore, if the public network address information determined at 1006 matches the private network address information associated with UE 910, then EES 944 may not transmit message 1008. This is because EES 944 can determine that NAT is not applied, and therefore, it is not necessary to query the NAT server 930 for the private network address information associated with UE 910.

[0159] At position 1012, EES 944 generates an EEC identification table. In some instances, the EEC identification table may include one or more private network address information entries (e.g., private Internet Protocol (IP) addresses and port numbers) and a mapping between each private network address information entry and a corresponding public network address information entry (e.g., public Internet Protocol (IP) addresses and port numbers). In some instances, the EEC identification table may optionally include a first identifier for UE 910 (also referred to as UE ID_1) and / or a second identifier for UE 910 (also referred to as UE ID_2). In some instances, the second identifier for UE 910 may be an edge UE ID assigned by EES 944. The first identifier for UE 910 and / or the second identifier for UE 910 may be mapped to private network address information entries in the EEC identification table. An exemplary EEC identification table generated at position 1012 is shown in Table 3.

[0160] Table 3 UE private network address information UE Public Network Address Information UE ID_1 (Optional) UE ID_2 (Optional) 192.168.1.5:1111 190.1.1.5:1111 718369249615 5 192.168.1.6:1113 190.1.1.6:1114 123@berlin.de 6 192.168.1.7:1811 190.1.1.7:1811 456@seoul.kr 7 192.168.1.8:1711 190.1.1.8:1711 789@sandiego.us 8

[0161] In Table 3, each row indicates the mapping between the UE's private network address information and the UE's corresponding public network address information. As shown in Table 3, the UE's first optional identifier (e.g., UE ID_1) and the UE's second optional identifier (e.g., UE ID_2) can be mapped to the UE's private network address information.

[0162] In an exemplary scenario, referring to Table 3 and Figure 10, the private network address information of UE 910 may include a private Internet Protocol (IP) address and port number represented as "192.168.1.5:1111", a public Internet Protocol (IP) address and port number represented as "190.1.1.5:1111", a first identifier of UE 910 represented as "718369249615" (e.g., UE ID_1), and a second identifier of UE 910 represented as "5" (e.g., UE ID_2).

[0163] As shown in Figure 10, EAS 942 can transmit message 1014, which includes a service request. In some instances, the service request may trigger an API (also known as the EDGE-3 API) defined between EAS 942 and EES 944. EAS 942 may include at least the public network address information of UE 910 in message 1014.

[0164] At 1016, EES 944 can determine the private network address information and / or the identifier of UE 910 based on an EEC identification table (e.g., the exemplary EEC identification table shown in Table 3). For example, EES 944 can match the public network address information of UE 910 received in message 1014 with the public network address information entries in the EEC identification table. Subsequently, EES 944 can determine the private network address information corresponding to the public network address information of UE 910 that matches in the EEC identification table.

[0165] In one instance, referring to Table 3, if the public network address information of UE 910 received in message 1014 is "190.1.1.5:1111", then EES 944 can find "190.1.1.5:1111" in Table 3 and determine that the private network address information of UE 910 corresponding to "190.1.1.5:1111" is "192.168.1.5:1111". In some instances, EES 944 can optionally determine that the first identifier (e.g., UE ID_1) of UE 910 corresponding to "190.1.1.5:1111" is "718369249615". In some instances, EES 744 may optionally determine that the second identifier (e.g., UE ID_2) of the UE 910 corresponding to "190.1.1.5:1111" is "5".

[0166] At 1018, EES 944 can execute a service request from EAS 942 based on the private network address information of UE 910 (e.g., "192.168.1.5:1111"). In other instances, EES 944 can execute a service request from EAS 942 based on the first and / or second identifier of UE 910 (e.g., UE ID_2, UE ID_2). EES 944 can respond to the service request in message 1014 by transmitting message 1020 to EAS 942.

[0167] An example of a service request from EES 942 will now be described. In one example, the service request in message 1014 could be an EDGE-3 API requesting the location of UE 910, and the public network address information of UE 910 included in message 1014 (e.g., "190.1.1.5:1111") could serve as the key for the service request (e.g., for the EDGE-3 API requesting the location of UE 910). In response to the service request, EES 944 can determine the private network address information of UE 910 based on the EEC identification table (e.g., Table 3), and can use the private network address information of UE 910 (e.g., "190.1.1.5:1111") as the key for the 3GPP network API to execute the 3GPP network API to obtain the location of UE 910. The 3GPP network can return information indicating the location of UE 910. EES 944 can include information indicating the location of UE 910 in response message 1020.

[0168] Figure 11 is a flowchart 1100 of a wireless communication method. The method can be executed by a UE (e.g., UE 410; device 1302 / 1302'; processing system 1414, which may include memory 360 and may be the entire UE 410 or elements of UE 410, such as TX processor 368, RX processor 356 and / or controller / processor 359).

[0169] At 1102, the UE receives a token from the first server in the edge data network. In some instances, referring to Figure 6, EEC 422 in UE 410 receives the token in message 606 from EAS 462.

[0170] At 1104, the UE transmits UE-associated identification information to a second server (e.g., EES 464) of the edge data network. This identification information includes at least a token, a UE identifier (e.g., GPSI), and a first server identifier (e.g., EAS ID), wherein the UE identifier is independent of the UE's Internet Protocol (IP) address. In some instances, referring to FIG6, EEC 422 may transmit message 612, which includes a token, a UE identifier (also referred to as UE identifier and UE ID), and an EAS 462 identifier.

[0171] In some instances, the UE's identifier is the General Public Subscription Identifier (GPSI). In some instances, the first server is the Edge Application Server (EAS), and the second server is the Edge Enabler Server (EES). In some instances, the identification information is associated with the identifier of the Edge Enabler Client (EEC) in the UE.

[0172] Figure 12 is a flowchart 1200 of a wireless communication method. This method can be executed by a UE (e.g., UE 710; device 1302 / 1302'; processing system 1414, which may include memory 360 and may be a component of the entire UE 710 or UE 410, such as TX processor 368, RX processor 356, and / or controller / processor 359). In Figure 12, actions indicated by dashed lines represent optional operations.

[0173] At 1202, the UE receives the network address of a first server configured to provide public network address information associated with the UE. In some instances, the UE may receive the network address of the first server from an entity in the core network (e.g., AMF and / or SMF) via parameters in the Protocol Configuration Options (PCO) Information Element (IE). For example, referring to FIG8A, UE 710 may receive the network address of the first server (e.g., STUN server 730) from an entity in the core network 720 (e.g., AMF and / or SMF) (e.g., via messages 812, 814). In some instances, the UE may receive the network address of the first server from an edge configuration server in the edge data network (e.g., ECS 750 in FIG8A). In some instances, the UE may receive the network address of the first server from an edge enabler server in the edge data network (e.g., via message 834 from EES 744 in FIG8A). In some instances, the first server is a communication time-travel utility (STUN) server used for NAT.

[0174] At 1204, the UE uses this network address to transmit a request to the first server for public network address information associated with the UE. For example, referring to FIG8A, the EEC 712 of UE 710 can transmit message 836, which includes private network address information associated with UE 710, to STUN server 730.

[0175] At 1206, the UE receives public network address information associated with the UE in response to the request from the first server. For example, the STUN server 730 can use the private network address information associated with the UE 710 to transmit message 838 to the EEC 712 of the UE 710, wherein message 838 includes the public network address information associated with the UE 710.

[0176] At point 1208, the UE determines whether Network Address Translation (NAT) is applied to the private network address information associated with the UE. In some instances, the EEC 712 can compare the private network address information associated with the UE 710 with the public network address information in message 838. If the private network address information associated with the UE 710 matches the public network address information in message 838, the EEC 712 can determine that NAT is not applied. If the private network address information associated with the UE 710 does not match the public network address information in message 838, the EEC 712 can determine that NAT is applied.

[0177] At point 1210, when network address translation is applied to the private network address information associated with the UE, the UE transmits the public network address information associated with the UE and the private network address information associated with the UE to a second server in the edge data network. In some instances, the second server is an edge enabler server (EES).

[0178] At position 1212, the UE transmits its identifier to the second server. In some instances, the UE's identifier is the General Public Subscription Identifier (GPSI).

[0179] Figure 13 is a conceptual data flow diagram 1300 illustrating the data flow between different components / elements in an exemplary device 1302. This device may be a UE. The device includes a receiving element 1304 that receives communications from network entities (e.g., edge enabler server 1360, edge application server 1362, STUN server 1364, edge configuration server 1368, core network 1366). The device also includes a token receiving element 1306 that receives token 1320 from a server 1362 (e.g., an edge application server) in an edge data network. The device also includes a UE identification information transmission element 1308 that performs the following operations: transmitting UE-associated identification information 1322 to the server 1360 of the edge data network, wherein the identification information includes at least token 1320, a UE identifier, and a server identifier 1362, wherein the UE identifier is independent of the UE's IP address; and transmitting the UE identifier to a second server.

[0180] The device also includes a network address information receiving element 1310, which receives a network address 1330 from a server 1364 (e.g., a STUN server) configured to provide public network address information associated with the UE. The network address information receiving element 1310 further receives public network address information 1334 associated with the UE from the server 1364 via a signal 1334.

[0181] Network address 1330 may be received from edge configuration server 1368 via signal 1324, from core network (CN) 1366 via signal 1326, and / or from edge enabler server 1360 via signal 1328. The apparatus also includes a network address information request transmission element 1312, which transmits a request 1332 to server 1364 for public network address information associated with the UE based on network address 1330. The apparatus also includes a network address translation application determination element 1314, which determines whether network address translation is applied to the UE's private network address information. Signal 1336 may include the UE's public network address information, and signal 1338 may include an indication of whether network address translation is applied.

[0182] The device also includes a network address information transmission element 1316, which performs the following operations: when network address translation is applied to private network address information associated with the UE, it transmits a message 1340 to a server 1360 in the edge data network, including public network address information associated with the UE and private network address information associated with the UE.

[0183] The device also includes a transmission element 1318 that transmits communications to network entities (e.g., edge enabler server 1360, STUN server 1364).

[0184] The device may include additional elements for each of the blocks that execute the algorithms in the flowcharts of Figures 11 and 12 above. Therefore, each of the blocks in the flowcharts of Figures 11 and 12 above can be executed by elements, and the device may include one or more of those elements. Elements may be one or more hardware elements specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by the processor, or some combination thereof.

[0185] Figure 14 is a schematic diagram 1400 illustrating an example of a hardware implementation of a device 1302' employing a processing system 1414. The processing system 1414 can be implemented using a bus architecture (typically represented by bus 1424). Bus 1424 may include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system 1414. Bus 1424 connects various circuits including one or more processors and / or hardware components (represented by processor 1404, components 1304, 1306, 1308, 1310, 1312, 1314, 1316, 1318, and computer-readable media / memory 1406). Bus 1424 may also connect various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0186] Processing system 1414 may be coupled to transceiver 1410. Transceiver 1410 is coupled to one or more antennas 1420. Transceiver 1410 provides components for communicating with various other devices over a transmission medium. Transceiver 1410 receives signals from one or more antennas 1420, extracts information from the received signals, and provides the extracted information to processing system 1414 (specifically, receiving element 1304). Additionally, transceiver 1410 receives information from processing system 1414 (specifically, transmitting element 1318) and generates signals to be applied to one or more antennas 1420 based on the received information. Processing system 1414 includes processor 1404 coupled to computer-readable media / memory 1406. Processor 1404 is responsible for general processing, including the execution of software stored on computer-readable media / memory 1406. When executed by processor 1404, the software causes processing system 1414 to perform the various functions described above for any particular device. Computer-readable media / memory 1406 may also be used to store data manipulated by processor 1404 during software execution. Processing system 1414 also includes at least one of elements 1304, 1306, 1308, 1310, 1312, 1314, 1316, and 1318. Elements may be software elements that execute in processor 1404, reside / store in computer-readable media / memory 1406, one or more hardware elements coupled to processor 1404, or some combination thereof. Processing system 1414 may be an element of UE 350 and may include at least one of TX processor 368, RX processor 356, and controller / processor 359 and / or memory 360. Alternatively, processing system 1414 may be the entire UE (e.g., see 350 in FIG. 3).

[0187] In one configuration, the device 1302 / 1302' for wireless communication includes: means for receiving a symbol from a first server in an edge data network; means for transmitting identification information associated with the device to a second server in the edge data network, wherein the identification information includes at least a symbol, an identifier of the device, and an identifier of the first server, wherein the identifier of the device is independent of the device's Internet Protocol (IP) address; means for receiving the network address of the first server configured to provide public network address information associated with the device; and means for transmitting information to the first server based on the network address. The server transmits a request for public network address information associated with the device; a server receives public network address information associated with the device in response to the request from a first server; a server transmits public network address information associated with the device and private network address information associated with the device to a second server in an edge data network when network address translation is applied to private network address information associated with the device; a server transmits an identifier of the device to the second server; and a server determines whether network address translation is applied to private network address information associated with the UE.

[0188] The aforementioned components may be one or more of the elements described in the device 1302 and / or the processing system 1414 of the device 1302' configured to perform the functions described in the aforementioned components. As mentioned above, the processing system 1414 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned components may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described in the aforementioned components.

[0189] Figure 15 is a flowchart 1500 of a wireless communication method. This method can be executed by a server (e.g., EES 464; device 1802 / 1802'; processing system 1914) in an edge data network.

[0190] At 1502, the server (e.g., EES 464) receives identification information associated with the user equipment (UE) from the UE. This identification information includes at least the UE's identifier, the identifier of the application server (e.g., EAS) in the edge data network, and a token associated with the application server. The UE's identifier is independent of the UE's Internet Protocol (IP) address. For example, EES 464 may receive message 612 including a token, the identifier of UE 410 (also referred to as the UE identifier and UE ID), and the identifier of EAS 462.

[0191] At 1504, the server assigns a second identifier to the UE, and at 1506, the server transmits the second identifier of the UE to the application server. For example, at 614, EES 464 may assign an optional identifier (also referred to herein as optional UE identifier, optional UE ID, and edge UE ID) to UE 410. Subsequently, EES 464 may transmit message 616, which includes the optional identifier of UE 410, to EAS 462.

[0192] At 1508, the server generates a table that includes mappings between symbols, application server identifiers, and UE identifiers. For example, at 618, EES 464 generates an EEC identification table (e.g., EEC identification table 510 in Figure 5). In some instances, the EEC identification table may include one or more EEC IDs and mappings between each EEC ID and its corresponding symbol, EAS identifier, and / or UE identifier. In some versions of this work, optional UE identifiers may be mapped to EEC IDs in the EEC identification table. In some instances, different symbols or different UE IDs (EEC ID, edge UE ID) may address the same UE. An exemplary EEC identification table generated at 618 is shown in Table 1.

[0193] At 1510, the server receives a service request (e.g., EDGE-3 API) from the application server, which includes at least a token and the application server's identifier, where the server includes a mapping between the Edge Enabler Client ID (EEC ID), the token, the application server's identifier, and the UE's identifier. For example, the service request may be included in message 620 from EAS 462.

[0194] At 1512, the server responds to the service request by determining at least one of the following: the EEC ID or the UE's identifier, based on the token, the application server's identifier, and the mapping between the EEC ID, the token, the application server's identifier, and the UE's identifier. For example, EES 464 can match the token and identifier (EAS ID) of EAS 462 received in message 620 with the token and identifier (EAS ID) of EAS 462 in the EEC identification table (e.g., Table 1). In one instance, referring to Table 1, if the token and identifier (EAS ID) of EAS 462 received in message 620 are "OACR1" and "EAS ID1" respectively, then EES 464 can find "OACR1" and "EAS ID1" in Table 1 and can determine that the EEC ID corresponding to "OACR1" and "EAS ID1" is "EEC ID1".

[0195] At point 1514, the server executes a service request based on at least one of the EEC ID or the UE's identifier. In some instances, the server may execute a service request via a Network Open Functions (NEF) Application Programming Interface (API) based on private network address information associated with the UE.

[0196] At 1516, the server transmits a message in response to the service request to the application server in the edge data network. In some cases, and as described herein, the server transmits the message in response to the service request based at least on a mapping (e.g., response message 626).

[0197] Figure 16 is a flowchart 1600 of a wireless communication method. This method can be executed by a server (e.g., EES 744; device 1802 / 1802'; processing system 1914) in an edge data network.

[0198] At 1602, the server transmits to the UE the network address of a server (e.g., STUN server 730 in Figure 8A) that is configured to provide public network address information associated with the UE.

[0199] At 1604, the server receives at least public network address information associated with the user equipment (UE). In some cases, the server also receives private network address information associated with the UE. In some instances, the public network address information associated with the UE includes a first Internet Protocol (IP) address and a first port number, and the private network address information associated with the UE includes a second IP address and a second port number. In some instances, the EES 744 can receive message 842 which includes both private network address information associated with the UE 710 and public network address information associated with the UE 710.

[0200] At 1606, the server assigns an identifier (e.g., edge UE ID) to the UE, and at 1608, the server transmits the UE's identifier to the application server (e.g., EAS).

[0201] At 1610, the server receives the UE's identifier from the UE. In some instances, the UE's identifier is the General Public Subscription Identifier (GPSI).

[0202] At 1612, the server generates a table that includes a mapping between private network address information associated with the UE and public network address information associated with the UE. An example of the generated table is described with reference to Table 2. In some instances, the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifiers (e.g., assigned identifiers (such as edge UE ID), and / or received identifiers (such as GPSI)) to the private network address information associated with the UE and the public network address information associated with the UE.

[0203] At 1614, the server receives a service request (e.g., EDGE-3 API) from an application server (e.g., EAS) in the edge data network, which includes at least public network address information associated with the UE. For example, referring to FIG8B, the service request may be included in message 846. The server includes a mapping between private network address information associated with the UE and public network address information associated with the UE. For example, EES 744 may include and / or may access the EEC identification table as described with reference to Table 2.

[0204] At 1616, the server responds to the service request by determining the private network address information associated with the UE based on the public network address information associated with the UE and the mapping between the private network address information associated with the UE and the public network address information associated with the UE. For example, EES 744 can match the public network address information of UE 710 received in message 846 with the public network address information entry in the EEC identification table. Subsequently, EES 744 can determine the private network address information corresponding to the public network address information of UE 710 that matches in the EEC identification table.

[0205] At point 1618, the server executes the service request based on the private network address information associated with the UE. In some instances, the server executes the service request via a Network Open Functions (NEF) Application Programming Interface (API) based on the private network address information associated with the UE.

[0206] At 1620, the server transmits a message in response to the service request to the application server in the edge data network. In some formats, and as described herein, the server transmits the message in response to the service request at least based on a mapping (e.g., response message 852). For example, EES 744 may include information returned from the API in the response message to EAS 742 (e.g., including the location of UE 710 in response message 852).

[0207] Figure 17 is a flowchart 1700 of a wireless communication method. This method can be executed by a server (e.g., EES 944; device 1802 / 1802'; processing system 1914) in an edge data network.

[0208] At 1702, the server (e.g., EES 944) receives a message from the UE (e.g., UE 910) that includes at least one user plane data packet. For example, during the registration process, EEC 912 may transmit registration message 1002 to EES 944. In some instances, registration message 1002 may include one or more data packets (e.g., user plane (UP) data packets). The user plane (UP) protocol of the one or more data packets may include public network address information associated with UE 910.

[0209] At 1704, the server uses this message to determine the UE's public network address information. In some instances, EES 944 derives the public network address information associated with UE 910 (e.g., UE 910's public IP address and port number) based on the UP protocol used for registration message 1002.

[0210] At 1706, the server determines the UE's identifier based on the public network address information associated with the UE. In some instances, the UE's identifier is the General Public Subscription Identifier (GPSI).

[0211] At 1708, the server receives private network address information associated with the UE from the Network Address Translation (NAT) device. For example, the NAT server 930 may transmit message 1010 to the server (e.g., EES 944) including private network address information associated with the UE 910 (e.g., the private IP address and port number of the UE 910).

[0212] At 1710, the server assigns an identifier (e.g., edge UE ID) to the UE, and at 1712, the server transmits the identifier to the application server.

[0213] At 1714, the server generates a table that includes a mapping between private network address information associated with the UE and public network address information associated with the UE. In some instances, the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifiers (e.g., assigned identifiers (such as edge UE ID), and / or received identifiers (such as GPSI)) to the private network address information associated with the UE and the public network address information associated with the UE.

[0214] For example, referring to Figure 10, at 1012, EES 944 generates an EEC identification table. In some instances, the EEC identification table may include one or more private network address information entries (e.g., private Internet Protocol (IP) addresses and port numbers) and a mapping between each private network address information entry and a corresponding public network address information entry (e.g., public Internet Protocol (IP) addresses and port numbers). In some instances, the EEC identification table may optionally include a first identifier of UE 910 (also referred to as UE ID_1) and / or a second identifier of UE 910 (also referred to as UE ID_2). In some instances, the second identifier of UE 910 may be an edge UE ID assigned by EES 944. The first identifier of UE 910 and / or the second identifier of UE 910 may be mapped to private network address information entries in the EEC identification table. An exemplary EEC identification table generated at 1012 is shown in Table 3.

[0215] At point 1716, the server receives a service request (e.g., EDGE-3 API) from an application server (e.g., EAS) in the edge data network, which includes at least public network address information associated with the UE. The server includes a mapping between private network address information associated with the UE and public network address information associated with the UE.

[0216] At 1718, the server responds to the service request by determining the private network address information associated with the UE based on the public network address information associated with the UE and the mapping between the private network address information associated with the UE and the public network address information associated with the UE.

[0217] For example, referring to Figure 10, at 1016, EES 944 can determine the private network address information and / or the identifier of UE 910 based on an EEC identification table (e.g., the exemplary EEC identification table shown in Table 3). For example, EES 944 can match the public network address information of UE 910 received in message 1014 with the public network address information entries in the EEC identification table. Subsequently, EES 944 can determine the private network address information corresponding to the public network address information of UE 910 that matches in the EEC identification table.

[0218] At 1720, the server executes the service request based on the private network address information associated with the UE. In some instances, the server executes the service request by triggering the Network Open Functions (NEF) Application Programming Interface (API) based on the private network address information associated with the UE.

[0219] At 1722, the server transmits a message in response to a service request to the application server in the edge data network. In some formats, and as described herein, the server transmits the message in response to the service request at least based on a mapping (e.g., response message 1020). For example, EES 944 may include information returned from the API in the response message to EAS 942 (e.g., including the location of UE 910 in response message 1020).

[0220] Figure 18 is a conceptual data flow diagram 1800 illustrating the data flow between different components / elements in an exemplary device 1802. This device may be a server device (e.g., an edge enabler server in an edge data network).

[0221] The device includes a receiving element 1804 that receives communications from network entities (e.g., UE 1880, edge application server 1890, NAT server 1892).

[0222] The device also includes an identification information receiving element 1806, which performs the following operations: receiving identification information 1842 associated with a UE from a UE (e.g., UE 1880), wherein the identification information includes at least a UE identifier, an application server identifier in an edge data network, and a symbol associated with the application server, wherein the UE identifier is independent of the UE's IP address; and receiving the UE identifier from the UE.

[0223] The apparatus also includes a message receiving element 1808 that receives from an application server (e.g., an edge application server 1890) a message (e.g., message 1840) including a service request. The service request includes at least a token and an identifier of the application server, wherein the server includes a mapping between an Edge Enabler Client ID (EEC ID), the token, the application server identifier, and the UE's identifier. In some instances, the service request includes at least public network address information associated with the UE. The message receiving element 1808 further receives from the UE a message 1834 including at least one user plane data packet.

[0224] The device also includes a network address information receiving element 1810, which performs the following operations: receiving public network address information and private network address information associated with the UE from the UE (e.g., via message 1834); and receiving private network address information 1830 associated with the UE from a network address translation (NAT) device (e.g., NAT server 1892) (e.g., in response to a query in signal 1828).

[0225] The device also includes an identifier assignment element 1812, which assigns a second identifier 1852 to the UE. The device also includes an identifier transmission element 1814, which transmits the second identifier 1852 of the UE to an application server (e.g., an edge application server 1890).

[0226] The device also includes a table generating element 1816, which generates a table including a mapping between symbols, application server identifiers, and UE identifiers. The symbols, application server identifiers, and UE identifiers can be included in signal 1846. Table generating element 1816 also generates a table including a mapping between private network address information associated with the UE and public network address information associated with the UE. The public and private network address information associated with the UE can be included in signal 1848. The generated table can be included in signal 1851.

[0227] The device also includes a decision element 1818 that performs the following operations: in response to a service request included in input signal 1856, determining at least one of an EEC ID or a UE identifier based on a symbol, an application server identifier, and a mapping between the EEC ID, the symbol, the application server identifier, and the UE identifier (e.g., the mapping in the table generated in signal 1851); and in response to a service request, determining private network address information associated with the UE based on public network address information associated with the UE and a mapping between private network address information associated with the UE and public network address information associated with the UE (e.g., the mapping in the table generated in signal 1851). The decision element 1818 also determines the UE's public network address information based on message 1834. The decision module 1818 also determines the UE's identifier based on the public network address information associated with the UE.

[0228] The device also includes a service request execution element 1820, which performs the following operations: executing a service request based on at least one of the EEC ID or the UE's identifier (e.g., the service request in signal 1860); and executing a service request based on private network address information associated with the UE (e.g., the private network address information associated with the UE in signal 1858).

[0229] The device also includes a message transmission element 1822, which transmits a message 1862 in response to a service request to an application server.

[0230] The device also includes a network address information transmission element 1824, which transmits to the UE (e.g., UE 1880) the network address 1854 of a server configured to provide public network address information associated with the UE.

[0231] The device also includes a transmission element 1826 that transmits communications to network entities (e.g., UE 1880, edge application server 1890, NAT server 1892).

[0232] The device may include additional elements for each of the blocks that execute the algorithms in the flowcharts of Figures 15-17. Therefore, each of the blocks in the flowcharts of Figures 15-17 can be executed by elements, and the device may include one or more of these elements. Elements may be one or more hardware elements specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by the processor, or some combination thereof.

[0233] Figure 19 is a schematic diagram 1900 illustrating an example of a hardware implementation of a device 1802' employing a processing system 1914. The processing system 1914 can be implemented using a bus architecture (typically represented by bus 1924). Bus 1924 can include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system 1914. Bus 1924 connects various circuits including one or more processors and / or hardware components (represented by processor 1904, components 1804, 1806, 1808, 1810, 1812, 1814, 1816, 1818, 1820, 1822, 1824, 1826, and computer-readable media / memory 1906). Bus 1924 can also connect various other circuits such as timing sources, peripheral devices, voltage regulators and power management circuits, which are well known in the art and will therefore not be described further.

[0234] Processing system 1914 may be coupled to transceiver 1910. Transceiver 1910 is coupled to one or more antennas 1920. Transceiver 1910 provides components for communicating with various other devices over a transmission medium. Transceiver 1910 receives signals from one or more antennas 1920, extracts information from the received signals, and provides the extracted information to processing system 1914 (specifically, receiving element 1804). Additionally, transceiver 1910 receives information from processing system 1914 (specifically, transmitting element 1826) and generates signals to be applied to one or more antennas 1920 based on the received information. Processing system 1914 includes processor 1904 coupled to computer-readable media / memory 1906. Processor 1904 is responsible for general processing, including the execution of software stored on computer-readable media / memory 1906. When executed by processor 1904, the software causes processing system 1914 to perform the various functions described above for any particular device. Computer-readable media / memory 1906 may also be used to store data manipulated by processor 1904 when executing the software. Processing system 1914 also includes at least one of elements 1804, 1806, 1808, 1810, 1812, 1814, 1816, 1818, 1820, 1822, 1824, and 1826. Elements may be software elements that execute in processor 1904, reside / store in computer-readable media / memory 1906, one or more hardware elements coupled to processor 1904, or some combination thereof.

[0235] In one configuration, the apparatus 1802 / 1802' for wireless communication includes: a component for receiving identification information associated with a user equipment (UE) from a user equipment (UE), wherein the identification information includes at least a UE identifier, an application server identifier in an edge data network, and a symbol associated with the application server, wherein the UE identifier is independent of the UE's Internet Protocol (IP) address; a component for receiving a service request from the application server including at least a symbol and an application server identifier, wherein the component includes a mapping between an Edge Enabler Client Identifier (EEC ID), a symbol, an application server identifier, and a UE identifier; a component for transmitting a message responding to the service request to the application server; a component for determining at least one of an EEC ID or a UE identifier based on the symbol, the application server identifier, and the mapping between the EEC ID, the symbol, the application server identifier, and the UE identifier in response to the service request; and a component for determining at least one of an EEC ID or a UE identifier based on the EEC ID; The device includes: a component for executing a service request based on at least one of the ID or UE identifier; a component for generating a table including a mapping between a symbol, an application server identifier, and a UE identifier; a component for assigning a second identifier to the UE; a component for transmitting the second identifier of the UE to the application server; a component for receiving public network address information and private network address information associated with the UE from a user equipment (UE); a component for receiving a service request from an application server in an edge data network, including at least public network address information associated with the UE, wherein the device includes a mapping between private network address information associated with the UE and public network address information associated with the UE; a component for transmitting a message responding to the service request to the application server in the edge data network; and a component for responding to the service request based on the public network address information associated with the UE and the private network address information associated with the UE and the UE identifier. The components include: a component for mapping between public network address information associated with a UE to determine the private network address information associated with the UE; a component for performing a service request based on the private network address information associated with the UE; a component for activating a Network Open Functions (NEF) Application Programming Interface (API) based on the private network address information associated with the UE; a component for transmitting to the UE the network address of a server configured to provide public network address information associated with the UE; a component for receiving a UE identifier from the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE identifier to the private network address information associated with the UE and the public network address information associated with the UE; a component for receiving a message from a user equipment (UE) including at least one user plane data packet; and a component for determining the public network address information of the UE based on the message.The device includes components for receiving private network address information associated with a UE from a Network Address Translation (NAT) device; components for receiving a service request from an application server in an edge data network, the service request including at least public network address information associated with the UE, wherein the device includes a mapping between the private network address information associated with the UE and the public network address information associated with the UE; components for transmitting a message responding to the service request to the application server in the edge data network; and components for determining an identifier for the UE based on the public network address information associated with the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the UE's identifier to the private network address information associated with the UE and the public network address information associated with the UE.

[0236] The aforementioned components may be one or more of the elements of device 1802 and / or a processing system 1914 of device 1802' configured to perform the functions described therein. As mentioned above, processing system 1914 may include TX processor 316, RX processor 370, and controller / processor 375. Therefore, in one configuration, the aforementioned components may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described therein.

[0237] The following provides an overview of the various aspects of this case:

[0238] Sample 1: A wireless communication method comprising the steps of: receiving a symbol from a first server in an edge data network; and transmitting identification information associated with a user equipment (UE) to a second server in the edge data network, wherein the identification information includes at least the symbol, an identifier of the UE, and an identifier of the first server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address.

[0239] State 2: According to the method of State 1, wherein the identifier of the UE is the General Public Subscription Identifier (GPSI).

[0240] State 3: According to the method of State 1 or 2, wherein the first server is an Edge Application Server (EAS) and the second server is an Edge Enabler Server (EES).

[0241] State 4: According to any one of the states 1 to 3, wherein the identification information is associated with the identifier of the edge enabler client (EEC) in the UE.

[0242] State 5: An apparatus for wireless communication, comprising: a memory; at least one processor coupled to the memory and configured to perform a method according to any one of states 1 to 4.

[0243] Sample 6: An apparatus for wireless communication, comprising: at least one component for performing the method according to any one of Samples 1 to 4.

[0244] State 7: A computer-readable medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of states 1 to 4.

[0245] Sample 8: A method for wireless communication of a device, comprising the steps of: receiving identification information associated with the user equipment (UE) from the user equipment (UE), wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of the UE's Internet Protocol (IP) address; receiving a service request from the application server including at least the symbol and the identifier of the application server, wherein the device includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE; and transmitting a message responding to the service request to the application server.

[0246] Version 9: The method according to Version 8 also includes the following steps: in response to the service request, determining at least one of the EEC ID or the UE identifier based on the symbol, the application server identifier and the mapping between the EEC ID, the symbol, the application server identifier and the UE identifier; and executing the service request based on at least one of the EEC ID or the UE identifier.

[0247] State 10: According to the method of State 8 or 9, it also includes the following steps: generating a table that includes the mapping between the symbol, the identifier of the application server and the identifier of the UE.

[0248] State 11: According to the method of any one of states 8 to 10, wherein the identifier of the UE is a General Public Subscription Identifier (GPSI) or the symbol.

[0249] Version 12: The method according to any one of versions 8 to 11 also includes the following steps: assigning a second identifier to the UE; and transmitting the second identifier of the UE to the application server; wherein the mapping between the edge enabler client identifier (EEC ID), the symbol, the application server identifier and the UE identifier maps the second identifier of the UE to the edge enabler client identifier (EEC ID), the symbol, the application server identifier and the UE identifier.

[0250] Sample 13: An apparatus for wireless communication, comprising: a memory; at least one processor coupled to the memory and configured to perform a method according to any one of Samples 8 to 12.

[0251] Sample 14: An apparatus for wireless communication, comprising: at least one component for performing the method according to any one of Samples 8 to 12.

[0252] Format 15: A computer-readable medium storing computer-executable code, which, when executed by the processor, causes the processor to perform the method according to any one of formats 8 to 12.

[0253] Sample 16: A wireless communication method comprising the steps of: receiving a network address of a first server configured to provide public network address information associated with a user equipment (UE); transmitting a request for the public network address information associated with the UE to the first server based on the network address; receiving the public network address information associated with the UE in response to the request from the first server; and transmitting the public network address information associated with the UE and the private network address information associated with the UE to a second server in an edge data network when network address translation is applied to private network address information associated with the UE.

[0254] Version 17: According to the method of Version 16, receiving the network address of the first server configured to provide public network address information associated with the UE includes performing at least one of the following operations: receiving the network address of the first server from an entity in the core network via parameters in a Protocol Configuration Option (PCO) Information Element (IE), receiving the network address of the first server from an Edge Configuration Server (ECS) in an Edge Data Network, or receiving the network address of the first server from an Edge Enabler Server (EES) in an Edge Data Network.

[0255] State 18: According to the method of State 16 or 17, wherein the first server is a communication period traversal utility (STUN) server for NAT and the second server is an edge enabler server (EES).

[0256] Version 19: The method according to any one of versions 16 to 18 also includes the step of transmitting the UE identifier to the second server.

[0257] State 20: According to any one of states 16 to 19, wherein the identifier of the UE is a General Public Subscription Identifier (GPSI).

[0258] Version 21: The method according to any one of versions 16 to 20 also includes the following steps: determining whether network address translation is applied to the private network address information associated with the UE.

[0259] Sample 22: An apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory and configured to perform a method according to any one of Samples 16 to 21.

[0260] Sample 23: An apparatus for wireless communication, comprising: at least one component for performing the method according to any one of Samples 16 to 21.

[0261] Format 24: A computer-readable medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of formats 16 to 21.

[0262] Sample 25: A method for wireless communication of a device, comprising the steps of: receiving at least public network address information associated with the user equipment (UE) from a user equipment (UE); receiving a service request from an application server in an edge data network that includes at least the public network address information associated with the UE, wherein the device includes a mapping between private network address information associated with the UE and the public network address information associated with the UE; and transmitting a message in response to the service request to the application server in the edge data network.

[0263] Version 26: The method according to Version 25 also includes the following steps: in response to the service request, determining the private network address information associated with the UE based on the public network address information associated with the UE and the mapping between the private network address information associated with the UE and the public network address associated with the UE; and executing the service request based on the private network address information associated with the UE.

[0264] State 27: According to the method of State 25 or 26, the execution of the service request includes: triggering the Network Open Functions (NEF) Application Programming Interface (API) based on the private network address information associated with the UE.

[0265] Version 28: The method according to any one of versions 25 to 27 also includes the step of: transmitting to the UE the network address of a server configured to provide public network address information associated with the UE.

[0266] Version 29: The method according to any one of versions 25 to 28 also includes the following steps: receiving an identifier of the UE from the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the identifier of the UE to the private network address information associated with the UE and the public network address information associated with the UE.

[0267] Sample 30: According to any one of Samples 25 to 29, wherein the identifier of the UE is a General Public Subscription Identifier (GPSI).

[0268] Version 31: According to any one of versions 25 to 30, the public network address information associated with the UE includes a first Internet Protocol (IP) address and a first port number, and the private network address information associated with the UE includes a second IP address and a second port number.

[0269] Version 32: The method according to any one of versions 25 to 31 also includes the following steps: assigning an identifier to the UE; and transmitting the identifier of the UE to the application server, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the identifier of the UE to the private network address information associated with the UE and the public network address information associated with the UE.

[0270] Sample 33: An apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory and configured to perform the method according to any one of samples 25 to 32.

[0271] Sample 34: An apparatus for wireless communication, comprising: at least one component for performing the method according to any one of Samples 25 to 32.

[0272] Format 35: A computer-readable medium storing computer-executable code, which, when executed by a processor, causes the processor to perform the method according to any one of formats 25 to 32.

[0273] Sample 36: A wireless communication method for a device, comprising the steps of: receiving from a user equipment (UE) a message including at least one user plane data packet; determining public network address information of the UE based on the message; receiving private network address information associated with the UE from a network address translation (NAT) device; receiving from an application server in an edge data network a service request including at least the public network address information associated with the UE, wherein the device includes a mapping between the private network address information associated with the UE and the public network address information associated with the UE; and transmitting a message responding to the service request to the application server in the edge data network.

[0274] Version 37: The method according to Version 36 also includes the following steps: determining the identifier of the UE based on the public network address information associated with the UE, wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the identifier of the UE to the private network address information associated with the UE and the public network address information associated with the UE.

[0275] State 38: According to the method of State 36 or 37, wherein the identifier of the UE is a General Public Subscription Identifier (GPSI).

[0276] Version 39: The method according to any one of versions 36 to 38 also includes the following steps: assigning an identifier to the UE; and transmitting the identifier to the application server; wherein the mapping between the private network address information associated with the UE and the public network address information associated with the UE maps the identifier to the private network address information associated with the UE and the public network address information associated with the UE.

[0277] Sample 40: An apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory and configured to perform a method according to any one of samples 36 to 39.

[0278] Sample 41: An apparatus for wireless communication, comprising: at least one component for performing the method according to any one of Samples 36 to 39.

[0279] Format 42: A computer-readable medium storing computer-executable code, which, when executed by a processor, causes the processor to perform any one of formats 36 to 39.

[0280] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of exemplary methods. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. Furthermore, some blocks can be merged or omitted. The appended method request provides the elements of the individual blocks in a sampling order, and is not intended to limit us to the specific order or hierarchy provided.

[0281] The foregoing description is provided to enable any person skilled in the art to implement the various forms described herein. Various modifications to these forms will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other forms. Therefore, the request is not intended to be limited to the forms shown herein, but is given the full scope consistent with the verbal request, wherein, unless expressly stated otherwise, references to the singular form do not mean "one and only one," but rather "one or more." The term "exemplary" as used herein means "serving as an example, instance, or illustration." Any form described herein as "exemplary" is not necessarily to be construed as superior to or having an advantage over other forms. Unless expressly stated otherwise, the term "some" means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members or several members of A, B, or C. All structural and functional equivalents of the elements permeating the various states described herein, and intended to be included in the claims, are known to or to be known later by a person skilled in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as "module," "mechanism," "element," "device," etc., are not necessarily substitutes for the term "component." Therefore, no element of the claims should be interpreted as a component plus function unless the element is explicitly described using the phrase "component for..."

[0282] 100: Wireless communication systems and access networks 102: Base Station 102': Small cells 104:UE 110: Geographical coverage area 110': Coverage area 120: Communication Link 132: Backload Link 134: Backload Link 150: Wi-Fi Access Point (AP) 152: Wi-Fi Station (STA) 154: Communication Link 158:D2D communication link 160:EPC 162: Management Entity (MME) 164: Other MMEs 166: Service Gateway 168: Multimedia Broadcast Multicast Service (MBMS) Gateway 170: Broadcast Multicast Service Center (BM-SC) 172: Packet Data Network (PDN) Gateway 174: Home Subscriber Server (HSS) 176: IP Service 180:gNB 182: Beamforming 182': Transmission direction 182'': Receiving direction 184: Backload Link 190: Core Network 192: Access and Mobility Management Functions (AMF) 193: Other AMF 194: Communication Management Function (SMF) 195: User Plane Function (UPF) 196: Unified Data Management (UDM) 197: IP Service 198: Component Symbol 200: Schematic diagram 230: Schematic diagram 250: Schematic diagram 280: Schematic diagram 310: Base Station 316: Transmission (TX) Processor 318: Transmitter / Receiver 320: Antenna 350:UE 352: Antenna 354: Transmitter / Receiver 356:RX processor 358: Channel Estimator 359: Controller / Processor 360: Memory 368:TX processor 370: Receiver (RX) Processor 374: Channel Estimator 375: Controller / Processor 376: Memory 400: Network Architecture 410:UE 412: Application Processor 414: Application Client (AC) 416:EDGE-5 API 420: Data machine equipment 422:EEC 424: Non-Access Layer (NAS) Protocol Layer 426: Access Layer Protocol Layer 428: Private network address 430: Radio Access Network 432: Base Station 440: Core Network 442: First Network Equipment 443: User Plane Function (UPF) 444: Second network device 446: Access and Mobility Management Functions (AMF) 448: Communication Management Function (SMF) 450: Network Address Translation (NAT) Server 452: Public network address 460: Edge Data Network 462:EAS 464:EES 466: Edge Configuration Server (ECS) 468: EDGE-3 reference point 472: Application Data Service 474: EDGE-1 reference point 476: Edge Signal Transmission 477: NAS Signal Transmission 478: Radio signal transmission 510: EEC Identification Table 600: Signal Flow Diagram 602: Message 604: Component Symbol 606: Message 608: Message 610: Component Symbol 612: Message 614: Component Symbol 616: Message 618: Component Symbol 620: Message 622: Component Symbol 624: Component Symbol 626: Message 700: Network Architecture 710:UE 712: Edge Enabler Client (EEC) 714: Non-Access Layer (NAS) Protocol Layer 720: Core Network 722: Network equipment 723: Access and Mobility Management Functions (AMF) 725: Communication Management Function (SMF) 730: STUN Server 735: Network Address Translation (NAT) Server 740: Edge Data Network 742:EAS 744: Edge Enabler Server (EES) 746: EEC Identification Table 748: EDGE-3 reference point 750:ECS 752: EDGE-6 reference point 754: STUN Interface 756: EDGE-1 reference point 758: Edge Signal Transmission 760: EDGE-4 reference point 762: Edge Signal Transmission 764: NAS Signal Transmission 800: Signal Flow Diagram 810: Optional communication 812: NAS Message 814: NAS Message 820: Optional communication 822: Message 830: Optional communication 832: Message 834: Message 836: Message 838: Message 840: Component Symbol 842: Message 844: Component Symbol 846: Message 848: Component Symbol 850: Component Symbol 852: Message 900: Network Architecture 910: User Equipment (UE) 912:EEC 920: Core Network 930: NAT Server 940: Edge Data Network 942:EAS 944:EES 946: EDGE-3 reference point 948: EEC Identification Table 950:ECS 952: EDGE-6 reference point 954: EDGE-7 reference point 956: EDGE-1 reference point 958: Edge Signal Transmission 960: EDGE-2 reference point 962: External Open Signal Transmission 964: Interface 1000: Signal Flow Diagram 1002: Registration Message 1006: Component Symbol 1007: Component Symbol 1008: Message 1010: Message 1012: Component Symbol 1014: Message 1016: Component Symbol 1018: Component Symbol 1020: Message 1100: Flowchart 1102: Component Symbol 1104: Component Symbol 1200: Flowchart 1202: Component Symbol 1204: Component Symbol 1206: Component Symbol 1208: Component Symbol 1210: Component Symbol 1212: Component Symbol 1300: Conceptual Data Flowchart 1302: Apparatus 1302': Apparatus 1304: Receiving element 1306: Symbol Receiving Element 1308: UE Identification Information Transmission Element 1310: Network Address Information Receiving Element 1312: Network Address Information Request Transmission Element 1314: Network address translation application determining element 1316: Network Address Information Transmission Component 1318: Transmission element 1320: Symbol 1322: Information Identification 1324: Signal 1326: Signal 1328: Signal 1330: Network address 1332: Request 1334: Signal 1336: Signal 1338: Signal 1340: Message 1360: Edge Enabler Server 1362: Edge Application Server 1364: STUN Server 1366: Core Network 1368: Edge Configuration Server 1400: Schematic diagram 1404: Processor 1406: Computer-readable media / memory 1410: Transceiver 1414: Processing System 1420: Antenna 1424: Busbar 1500: Flowchart 1502: Component Symbol 1504: Component Symbol 1506: Component Symbol 1508: Component Symbol 1510: Component Symbol 1512: Component Symbol 1514: Component Symbol 1516: Component Symbol 1600: Flowchart 1602: Component Symbol 1604: Component Symbol 1606: Component Symbol 1608: Component Symbol 1610: Component Symbol 1612: Component Symbol 1614: Component Symbol 1616: Component Symbol 1618: Component Symbol 1620: Component Symbol 1700: Flowchart 1702: Component Symbol 1704: Component Symbol 1706: Component Symbol 1708: Component Symbol 1710: Component Symbol 1712: Component Symbol 1714: Component Symbol 1716: Component Symbol 1718: Component Symbol 1720: Component Symbol 1722: Component Symbol 1800: Conceptual Data Flowchart 1802: Apparatus 1802': Apparatus 1804: Receiving element 1806: Identify information receiving element 1808: Message receiving element 1810: Network Address Information Receiving Element 1812: Identifier Assignment Component 1814: Identifier Transmission Element 1816: Table generating element 1818: Determining Components 1820: Service Request Execution Element 1822: Message Transmission Element 1824: Network Address Information Transmission Element 1826: Transmission element 1828: Signal 1830: Private Network Address Information 1834: Message 1840: Message 1842: Identifying Information 1846: Signal 1848: Signal 1851: Signal 1852: Second Identifier 1854: Network address 1856: Input signal 1858: Signal 1860: Signal 1862: Message 1880:UE 1890: Edge Application Server 1892: NAT Server 1900: Schematic diagram 1904: Processor 1906: Computer-readable media / memory 1910: Transceiver 1914: Processing System 1920: Antenna 1924: Busbar D:DL DMRS RX: Demodulated RS U:UL X: Flexible

[0283] Domestic storage information (please note in order of storage institution, date, and number) none Overseas storage information (please note in the order of storage country, institution, date, and number) none

Claims

1. A device for wireless communication, comprising: A component for receiving a symbol from a first server in an edge data network; And a component for transmitting identification information associated with the device to a second server in the edge data network, wherein the identification information includes at least the symbol, an identifier of the device and an identifier of the first server, wherein the identifier of the device is independent of an Internet Protocol (IP) address of the device.

2. The device according to request item 1, wherein the identifier of the device is a General Public Subscription Identifier (GPSI).

3. The apparatus according to claim 1, wherein the first server is an edge application server (EAS) and the second server is an edge enabler server (EES).

4. The device according to request item 1, wherein the identification information is associated with an identifier of an edge enabler client (EEC) in the device.

5. An apparatus for wireless communication, comprising: A means for receiving identification information associated with a user equipment (UE) from a user equipment (UE), wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of an Internet Protocol (IP) address of the UE; a means for receiving a service request from the application server including at least the symbol and the identifier of the application server, wherein the means includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE; and a means for transmitting a message responding to the service request to the application server at least based on the mapping.

6. The apparatus according to claim 5, the apparatus further comprising: responding to the service request by determining at least one of the EEC ID or the identifier of the UE based on the symbol, the identifier of the application server, and the mapping between the EEC ID, the symbol, the identifier of the application server, and the identifier of the UE; and performing the service request based on at least one of the EEC ID or the identifier of the UE.

7. The apparatus according to claim 5, the apparatus further comprising: a component for generating a table including the mapping between the symbol, the identifier of the application server and the identifier of the UE.

8. The device according to request item 5, wherein the identifier of the UE is a General Public Subscription Identifier (GPSI) or the symbol.

9. The apparatus of claim 5, further comprising: a component for assigning a second identifier to the UE; a component for transmitting the second identifier of the UE to the application server; and wherein the mapping between the Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server and the identifier of the UE maps the second identifier of the UE to the Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server and the identifier of the UE.

10. A method for wireless communication, the method being performed by a device and comprising: Receive a token from a first server in an edge data network; and transmit identification information associated with the device to a second server in the edge data network, wherein the identification information includes at least the token, an identifier of the device, and an identifier of the first server, wherein the identifier of the device is independent of an Internet Protocol (IP) address of the device.

11. A method for wireless communication, the method being performed by a device and comprising: The device receives identification information associated with a user equipment (UE), wherein the identification information includes at least an identifier of the UE, an identifier of an application server in an edge data network, and a symbol associated with the application server, wherein the identifier of the UE is independent of an Internet Protocol (IP) address of the UE; receives a service request from the application server, including at least the symbol and the identifier of the application server, wherein the device includes a mapping between an Edge Enabler Client ID (EEC ID), the symbol, the identifier of the application server, and the identifier of the UE; and transmits a message responding to the service request to the application server at least based on the mapping.

12. A computer program comprising instructions that, when executed by a computer, cause the computer to perform the steps of the method described in either claim 10 or 11.

Images