EP4476642A1 - Benutzergeräteidentifizierung in edge-kommunikationsarchitektur - Google Patents

Benutzergeräteidentifizierung in edge-kommunikationsarchitektur

Info

Publication number
EP4476642A1
EP4476642A1 EP23708107.0A EP23708107A EP4476642A1 EP 4476642 A1 EP4476642 A1 EP 4476642A1 EP 23708107 A EP23708107 A EP 23708107A EP 4476642 A1 EP4476642 A1 EP 4476642A1
Authority
EP
European Patent Office
Prior art keywords
identification information
identifier
edge
request
network node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23708107.0A
Other languages
English (en)
French (fr)
Inventor
Nishant Gupta
Sunghoon Kim
Alan SOLOWAY
Dario Serafino Tonesi
Tom Chin
Ajith Tom Payyappilly
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/154,698 external-priority patent/US20230254912A1/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP4476642A1 publication Critical patent/EP4476642A1/de
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2117—User registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like).
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC- FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE).
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
  • UMTS Universal Mobile Telecommunications System
  • a wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs.
  • a UE may communicate with a network node via downlink communications and uplink communications.
  • Downlink (or “DL”) refers to a communication link from the network node to the UE
  • uplink (or “UL”) refers to a communication link from the UE to the network node.
  • Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples).
  • SL sidelink
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • New Radio which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • MIMO multiple-input multiple-output
  • the UE may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to transmit a request for identification information, the request including at least one identifier of the UE.
  • the one or more processors may be configured to receive, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information.
  • the one or more processors may be configured to communicate based at least in part on receiving the identification information.
  • the network node may include a memory and one or more processors coupled to the memory.
  • the one or more processors may be configured to receive a request for identification information, the request including at least one identifier of a UE.
  • the one or more processors may be configured to transmit, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information.
  • the one or more processors may be configured to communicate based at least in part on transmitting the identification information.
  • the method may include transmitting a request for identification information, the request including at least one identifier of the UE.
  • the method may include receiving, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information.
  • the method may include communicating based at least in part on receiving the identification information.
  • the method may include receiving a request for identification information, the request including at least one identifier of a UE.
  • the method may include transmitting, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information.
  • the method may include communicating based at least in part on transmitting the identification information.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to transmit a request for identification information, the request including at least one identifier of the UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to communicate based at least in part on receiving the identification information.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to receive a request for identification information, the request including at least one identifier of a UE.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to transmit, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to communicate based at least in part on transmitting the identification information.
  • the apparatus may include means for transmitting a request for identification information, the request including at least one identifier of the apparatus.
  • the apparatus may include means for receiving, as a response to the request for identification information, a response message including the identification information, the identification information including an edge apparatus identifier assigned to the apparatus based at least in part on the request for the identification information.
  • the apparatus may include means for communicating based at least in part on receiving the identification information.
  • the method may include receiving, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the method may include communicating using the identification information.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to transmit identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to communicate based at least in part on transmitting the identification information.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instmctions for wireless communication by a network node.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to receive, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the set of instructions when executed by one or more processors of the network node, may cause the network node to communicate using the identification information.
  • the apparatus may include means for transmitting identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the apparatus may include means for communicating based at least in part on transmitting the identification information.
  • the apparatus may include means for receiving, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the apparatus may include means for communicating using the identification information.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
  • Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
  • some aspects may be implemented via integrated chip embodiments or other non-modulecomponent based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, rctail/purchasing devices, medical devices, and/or artificial intelligence devices).
  • Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components.
  • Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
  • transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers).
  • RF radio frequency
  • FIG. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • UE user equipment
  • FIG. 3 is a diagram illustrating an example of a disaggregated base station architecture, in accordance with the present disclosure.
  • Fig. 4 is a diagram illustrating an example of a network architecture that includes an edge network, in accordance with the present disclosure.
  • Fig. 5 is a diagram illustrating an example of a network architecture that includes a plurality of mobile network operators, in accordance with the present disclosure.
  • FIGs. 6-10 are diagrams illustrating examples associated with UE identification in an edge communications architecture, in accordance with the present disclosure.
  • FIGs. 11-12 are diagrams illustrating example processes associated with UE identification in an edge communications architecture, in accordance with the present disclosure.
  • FIGs. 13-14 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.
  • FIGs. 15-16 are diagrams illustrating example processes associated with UE identification in an edge communications architecture, in accordance with the present disclosure.
  • Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples.
  • 5G e.g., NR
  • 4G e.g., Long Term Evolution (LTE) network
  • the wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 1 lOd), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other entities.
  • a network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes.
  • a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit).
  • RAN radio access network
  • a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
  • CUs central units
  • DUs distributed units
  • RUs radio units
  • a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU.
  • a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU.
  • a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU.
  • a network node 110 may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs.
  • a network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission reception point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof.
  • the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
  • a network node 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used.
  • a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)).
  • a network node 110 for a macro cell may be referred to as a macro network node.
  • a network node 110 for a pico cell may be referred to as a pico network node.
  • a network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig.
  • the network node 110a may be a macro network node for a macro cell 102a
  • the network node 110b may be a pico network node for a pico cell 102b
  • the network node 110c may be a femto network node for a femto cell 102c.
  • a network node may support one or multiple (e.g., three) cells.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node).
  • base station or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof.
  • base station or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof.
  • the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110.
  • the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices.
  • the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device.
  • the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110).
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the network node 1 lOd e.g., a relay network node
  • the network node 110a e.g., a macro network node
  • a network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).
  • macro network nodes may have a high transmit power level (e.g., 5 to 40 watts)
  • pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).
  • a network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110.
  • the network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link.
  • the network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
  • a UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor,
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity.
  • Some UEs 120 may be considered Intemet-of-Things (loT) devices, and/or may be implemented as NB-IoT (narrowband loT) devices.
  • Some UEs 120 may be considered a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
  • any number of wireless networks 100 may be deployed in a given geographic area.
  • Each wireless network 100 may support a particular RAT and may operate on one or more frequencies.
  • a RAT may be referred to as a radio technology, an air interface, or the like.
  • a frequency may be referred to as a carrier, a frequency channel, or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another).
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device -to -device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz - 24.25 GHz
  • FR3 7.125 GHz - 24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • FR4a or FR4-1 52.6 GHz - 71 GHz
  • FR4 52.6 GHz - 114.25 GHz
  • FR5 114.25 GHz - 300 GHz.
  • Each of these higher frequency bands falls within the EHF band.
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • frequencies included in these operating bands may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • the UE 120 may include a communication manager 140.
  • the communication manager 140 may transmit identification information, wherein the identification information includes a UE identifier or connectivity information; and communicate based at least in part on transmitting the identification information.
  • the communication manager 140 may transmit a request for identification information, the request including at least one identifier of the UE; receive , as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information; and communicate based at least in part on receiving the identification information. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • a network node may include a communication manager 150.
  • the communication manager 150 may receive, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information; and communicate using the identification information.
  • the communication manager 150 may receive a request for identification information, the request including at least one identifier of a UE; transmit , as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information; and communicate based at least in part on transmitting the identification information. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • the network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T> 1).
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1).
  • the network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232.
  • a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node.
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120.
  • MCSs modulation and coding schemes
  • the transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols.
  • the transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)).
  • reference signals e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
  • synchronization signals e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)
  • a transmit (TX) multiple -input multiple -output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, fdter, and/or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the downlink signals from the network node 110 and/or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r.
  • R received signals e.g., R received signals
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
  • a channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI CQI parameter
  • the network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
  • the network controller 130 may include, for example, one or more devices in a core network.
  • the network controller 130 may communicate with the network node 110 via the communication unit 294.
  • One or more antennas may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280.
  • the transmit processor 264 may generate reference symbols for one or more reference signals.
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • the UE 120 includes a transceiver.
  • the transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266.
  • the transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 6-14).
  • the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240.
  • the network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
  • the network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
  • the modem 232 of the network node 110 may include a modulator and a demodulator.
  • the network node 110 includes a transceiver.
  • the transceiver may include any combination of the antenna(s) 234, the modem/ s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 6-14).
  • the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of Fig. 2 may perform one or more techniques associated with UE identification in an edge communications architecture, as described in more detail elsewhere herein.
  • the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of Fig. 2 may perform or direct operations of, for example, process 1100 ofFig. 11, process 1200 of Fig. 12, process 1500 of Fig. 15, process 1600 of Fig. 16, and/or other processes as described herein.
  • the memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively.
  • the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 1100 of Fig. 11, process 1200 ofFig. 12, process 1500 of Fig. 15, process 1600 ofFig. 16, and/or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
  • the UE 120 includes means for transmitting identification information, wherein the identification information includes a UE identifier or connectivity information; and/or means for communicating based at least in part on transmitting the identification information.
  • the UE 120 includes means for transmitting a request for identification information, the request including at least one identifier of the UE 120; means for receiving, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE 120 based at least in part on the request for the identification information; and/or means for communicating based at least in part on receiving the identification information.
  • the means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • a network node 110 includes means for receiving, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information; and/or means for communicating using the identification information.
  • the network node 110 includes means for receiving a request for identification information, the request including at least one identifier of a UE; means for transmitting, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information; and/or means for communicating based at least in part on transmitting the identification information.
  • the means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • Fig. 2 While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
  • the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Deployment of communication systems may be arranged in multiple manners with various components or constituent parts.
  • a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, among other examples
  • a base station may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.
  • Network entity or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit).
  • a disaggregated base station e.g., a disaggregated network node
  • a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.
  • VCU virtual central unit
  • VDU virtual distributed unit
  • VRU virtual radio unit
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed.
  • a disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
  • Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure.
  • the disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both).
  • a CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces.
  • Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links.
  • Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links.
  • RF radio frequency
  • Each of the units may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium.
  • each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • a wireless interface which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 310 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310.
  • the CU 310 may be configured to handle user plane functionality (for example, Central Unit - User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit - Control Plane (CU-CP) functionality), or a combination thereof.
  • the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • a CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration.
  • the CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.
  • Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340.
  • the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3 GPP.
  • the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples.
  • FEC forward error correction
  • the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples.
  • FFT fast Fourier transform
  • iFFT inverse FFT
  • PRACH physical random access channel
  • Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
  • Each RU 340 may implement lower-layer functionality.
  • an RU 340, controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3 GPP), such as a lower layer functional split.
  • a functional split for example, a functional split defined by the 3 GPP
  • each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120.
  • OTA over the air
  • the SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface).
  • the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface).
  • a cloud computing platform such as an open cloud (O-Cloud) platform 390
  • network element life cycle management such as to instantiate virtualized network elements
  • cloud computing platform interface such as an 02 interface
  • virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325.
  • the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface.
  • OF-eNB open eNB
  • the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface.
  • the SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.
  • the Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy -based guidance of applications/features in the Near-RT RIC 325.
  • the Non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 325.
  • the Near-RT RIC 325 may be configured to include a logical function that enables near-real- time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.
  • the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions.
  • the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance.
  • the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).
  • Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
  • FIG. 4 is a diagram illustrating an example of network architecture 400 that includes an edge network, in accordance with the present disclosure.
  • the network architecture 400 includes a UE 120, a radio network 410, a core network 420, and an edge network 430.
  • UE 120 may include an applications processor 440, which includes one or more application clients (ACs) 442, and a modem 444, which includes a non-access stratum (NAS) layer 446 and an access stratum (AS) layer 448.
  • UE 120 may also be associated with an edge enabler client (EEC) 450, which may communicate with the one or more ACs 442 via an EDGE-5 interface.
  • ACs application clients
  • EEC edge enabler client
  • radio network 410 may include a network entity (NE) 412, which may communicate, using radio signaling, with the AS layer 448 of UE 120.
  • Core network 420 may include a user plane function (UPF) 422 and an access and mobility management function (AMF) and/or session management function (SMF) (AMF/SMF) 424.
  • AMF/SMF 424 may communicate with NAS layer 446 via NAS signaling.
  • Edge network 430 may include an edge application server (EAS) 432, an edge enabler server (EES) 434, and an edge configuration server (ECS) 436.
  • EAS edge application server
  • EES edge enabler server
  • ECS edge configuration server
  • UE 120 may attempt to communicate with network entities of edge network 430 (e.g., EAS 432 and EES 434).
  • UEs may be publicly identified using a generic public subscription identifier (GPSI), such as a mobile station integrated services digital network (MSISDN) (e.g., a mobile number or another external identifier, such as a domain address).
  • GPSI public subscription identifier
  • MSISDN mobile station integrated services digital network
  • core network 420 may expose one or more application programming interfaces (APIs) that allow the use of a UE’s IP address for UE identification.
  • APIs application programming interfaces
  • a mobile network operator (MNO) may deploy network address translation (NAT) function to enable IP communication for many UEs within a public network.
  • UE 120 may have a private Internet Protocol (IP) address assigned to UE 120, and a network address translation function (NAT) 452 may translate the private IP address to a public IP address when IP communication is exposed by core network 420 to an external public network.
  • IP Internet Protocol
  • NAT network address translation function
  • NAT 452 may translate a private IP address to a first public IP address A for UE 120 and AC 442 and to a second public IP address B for UE 120 and EEC 450. This may occur because NATs, such as NAT 452, may not have enough available public IP version 4 (IPv4) addresses to assign unique IPv4 address to each possible device. Accordingly, the NATs map multiple local private addresses to a unique public IP address and cycle through the multiple local private addresses.
  • IPv4 public IP version 4
  • EAS 432 may have access to the first public IP address A based at least in part on received application data IP packets.
  • EES 434 may have access to the second public IP address B based at least in part on received edge signaling IP packets on an EDGE-1 interface.
  • the first public IP address A and the second public IP address B will be the same IP address, such an occurrence is not guaranteed. Accordingly, if EAS 432 queries EES 434 with the first public IP address A, EES 434 may not recognize that EAS 432 is querying regarding UE 120. In other words, EES 434 may not have information associating the first public IP address A with the second public IP address B (e.g., as belonging to the same UE 120).
  • Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
  • Fig. 5 is a diagram illustrating an example of a network architecture 500 that includes a plurality of mobile network operators (MNOs), in accordance with the present disclosure.
  • MNOs mobile network operators
  • first MNO 510-1 and a second MNO 510-2 may provide communication networks in which UEs 120 may operate.
  • first MNO 510-1 may include a first UE 120-1 in communication with a core network (CN) 512-1 and second MNO 510-2 may include a second UE 120-1 in communication with a second CN 512-2.
  • An edge data network (EDN) 520 may include an EES 522 and an EAS 524.
  • EES 522 may serve a plurality of MNOs 510.
  • EES 522 may serve first UE 120-1 in first MNO 510-1 and second UE 120-2 in second MNO 510-2.
  • EES 522 may serve first UE 120-1 in first MNO 510-1 and second UE 120-2 in second MNO 510-2.
  • EES 522 may receive a request from EAS 524 including identification information, such as a UE IP address (e.g., a private IP address) or a GPSI. However, EES 522 may lack information to map the identification information (e.g., the private IP address or GPSI) to a correct MNO 510 and to query for UE 120 for related information. Furthermore, when a UE 120 is operating in a roaming state and connected with EES 522 via a visited public land mobile network (vPLMN), EES 522 may lack information associated with identifying a roaming CN that the UE 120 is using.
  • identification information such as a UE IP address (e.g., a private IP address) or a GPSI.
  • vPLMN visited public land mobile network
  • Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
  • FIG. 6 is a diagram illustrating an example 600 associated with UE identification in an edge communications architecture, in accordance with the present disclosure. As shown in Fig.
  • AC 605 and/or EEC 610 may be components or entities included in or associated with UE 120.
  • EES 615 and EAS 620 may be components or entities included in or associated with a network node of an edge network, such as a network node 110 or other network entity.
  • AC 605 may transmit a UE identification request to EEC 610.
  • AC 605 may request (via an API of EEC 610) that EEC 610 provide a UE identifier (UE ID) to AC 605.
  • EEC 610 may have the UE ID to provide to AC 605 based at least in part on receiving a request.
  • EEC 610 may transmit a response to AC 605.
  • EEC 610 may provide a UE ID to AC 605.
  • AC 605 may transmit identification information indicating the UE ID and may receive an acknowledgement message as a response.
  • AC 605 may transmit a message that includes one or more fields set to identify or indicate the UE ID to EAS 620.
  • EAS 620 may store the UE ID and may communicate with EES 615 to invoke EDGE-3 services using the UE ID.
  • one or more network entities of the edge network that includes EES 615 and EAS 620 may communicate with UE 120 (e.g., AC 605 and EEC 610).
  • Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.
  • Fig. 7 is a diagram illustrating an example 700 associated with UE identification in an edge communications architecture, in accordance with the present disclosure. As shown in Fig.
  • AC 705 and/or EEC 710 may be components or entities included in or associated with UE 120.
  • EES 715 and EAS 720 may be components or entities included in or associated with a network node of an edge network, such as a network node 110 or other network entity.
  • AC 705 may transmit identification information indicating a private IP address (e.g., of UE 120) and may receive an acknowledgement message as a response. For example, AC 705 may transmit a message that includes one or more fields set to identify or indicate the private IP address to EAS 720. In this way, AC 705 can enable EAS 720 to use EDGE-3 services of the EES 715 using UE ID information as is described with regard to Fig. 6. Additionally, or alternatively, using the private IP address may reduce a security issue that may occur with regard to providing the UE ID to AC 705 and/or EAS 720.
  • EAS 720 may store the private IP address and may communicate with EES 715 to invoke EDGE-3 services using the private IP address.
  • one or more network entities of the edge network that includes EES 715 and EAS 720 may communicate with UE 120 (e.g., AC 705 and EEC 710).
  • an EDGE-3 service may implement an IP address to UE ID translation functionality, in which case, EAS 720 and/or EES 715 may use the UE ID to access EDGE-3 services after using the IP address to UE ID translation functionality.
  • Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.
  • Fig. 8 is a diagram illustrating an example 800 associated with UE identification in an edge communications architecture, in accordance with the present disclosure.
  • an AC 805, an EEC 810, an EES 815, and an EAS 820 may communicate with one another.
  • AC 805 and/or EEC 810 may be components or entities included in or associated with UE 120.
  • EES 815 and EAS 820 may be components or entities included in or associated with a network node of an edge network, such as a network node 110 or other network entity.
  • AC 805 may transmit a UE identification request to EEC 810.
  • EEC 810 may request (via an API of EEC 810) that EEC 810 provide a UE ID (e.g., a GPSI) to AC 805.
  • EEC 810 may have the UE ID stored and available to provide to AC 805.
  • EEC 810 may not have the UE ID stored and available to provide to AC 805.
  • EEC 810 may obtain the UE ID based at least in part on a request from AC 805.
  • EEC 810 may obtain the UE ID, as described in more detail herein.
  • EEC 810 may transmit a response to AC 805 identifying the UE ID.
  • EEC 810 may provide a GPSI to AC 805.
  • AC 805 may transmit identification information indicating the UE ID to EAS 820 and EAS 820 may store the UE ID.
  • one or more network entities of the edge network may use the UE ID to access an EDGE-3 API associated with the UE 120 (e.g., AC 805 and EEC 810)).
  • EEC 810 may provide connectivity information to AC 805 as a response to the request for the UE ID. For example, EEC 810 may provide, to AC 805, information identifying an IP address (e.g., a private IP address), a home public land mobile network (hPLMN) identifier (hPLMN ID), or a serving public land mobile network (PLMN) (serving PLMN) identifier (serving PLMN ID), among other examples. Additionally, or alternatively, AC 805 may determine the connectivity information without receiving the connectivity information from EEC 810.
  • IP address e.g., a private IP address
  • hPLMN home public land mobile network
  • PLMN ID serving public land mobile network
  • AC 805 may determine the connectivity information without receiving the connectivity information from EEC 810.
  • the connectivity information may be conveyed in a Connectivity Information type of information element.
  • the Connectivity Information type of information element may be configured to convey a PLMN identifier (PLMN ID), a service set identifier (SSID), a home PLMN or hPLMN ID (e.g., for non-roaming use), a serving PLMN ID (e.g., for roaming use, in which case the serving PLMN ID may be a visited PLMN ID (vPLMN ID)), a slice identifier, or an edge computing service provider (ECSP) identifier.
  • PLMN ID PLMN identifier
  • SSID service set identifier
  • a home PLMN or hPLMN ID e.g., for non-roaming use
  • a serving PLMN ID e.g., for roaming use, in which case the serving PLMN ID may be a visited PLMN ID (vPLMN ID)
  • AC 805 may transmit identification information indicating the connectivity information to EAS 820.
  • AC 805 may provide information identifying the iP address, the hPLMN fD, or the serving PLMN fD, among other examples to EAS 820.
  • connectivity information provided to identify UE f20 is updated using an hPLMN fD and/or serving PLMN fD to enable disambiguation of different MNOs in which UE 120 may be operating.
  • EAS 820 uses the EDGE-3 API for identification translation.
  • EAS 820 may use the IP address, hPLMN ID, and/or serving PLMN ID.
  • EES 815 may have the IP address translated to a UE ID associated with a correct core network for the UE 120 by using the hPLMN ID and the serving PLMN ID (e.g., which enables functionality in both non-roaming and roaming scenarios).
  • EES 815 may convert the UE ID to an EAS-specific edge UE ID and may provide the edge UE ID to EAS 820 for subsequent use, as shown by reference numbers 866 and 868.
  • a network node of the edge network may then use the edge UE ID to access the EDGE-3 API associated with the UE 120 (e.g., AC 805 and/or EEC 810).
  • the UE 120 and the network node of the edge network enable communication in cases when EEC 810 has the UE ID available and when EEC 810 does not have the UE ID available.
  • Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.
  • Fig. 9 is a diagram illustrating an example 900 associated with UE identification in an edge communications architecture, in accordance with the present disclosure.
  • an AC 905, an EEC 910, an EES 915, and an EAS 920 may communicate with one another.
  • AC 905 and/or EEC 910 may be components or entities included in or associated with UE 120.
  • EES 915 and EAS 920 may be components or entities included in or associated with a network node of an edge network, such as a network node 110 or other network entity.
  • EEC 910 may transmit (via an API call to an EDGE-1 interface associated with EES 915) an EEC registration request to EES 915.
  • EEC 910 may provide connectivity information, such as a private IP address, an hPLMN ID, or a serving PLMN ID, among other examples to EES 915.
  • connectivity information such as a private IP address, an hPLMN ID, or a serving PLMN ID, among other examples to EES 915.
  • a new EES service may be instantiated, which may trigger EES 915 to translate a private IP into a UE ID and assign an edge UE ID, as described herein.
  • EES 915 may translate the private IP address to a UE ID, assign an edge UE ID based at least in part on the UE ID, and provide an EEC registration response to EEC 910 to indicate the edge UE ID.
  • EES 915 may use the hPLMN ID and the serving PLMN ID to identify an MNO associated with a UE 120 (e.g., associated with AC 905 and EEC 910) and translate the private IP into a UE ID based at least in part on identifying the MNO.
  • EES 915 may associate a time limitation with the edge UE ID. For example, EES 915 may cause the edge UE ID to expire (e.g., become not usable for communication and invoking EDGE-3 services) after a period of time, which may improve information security by reducing tracking of UE 120.
  • EEC 810 may obtain an edge UE ID (e.g., or, in another example, a UE ID when EES 915 forgoes assignment of the edge UE ID) for subsequent use, which may enable dynamic private IP addresses to be allocated without causing issues to communication between the network node of the edge network and UE 120.
  • EES 915 can optimize allocation of the edge UE ID, as described herein, which may enable optimization by using a single core network subscription for a plurality of EASs 920.
  • AC 905 may request the edge UE ID and receive a response indicating the edge UE ID.
  • AC 905 may transmit a request for identification information and may receive the edge UE ID as a response.
  • AC 905 may transmit identification information to EAS 920 and receive an acknowledgement of the identification information from EAS 920.
  • AC 905 may transmit an indication of the edge UE ID.
  • EAS 920 may store the edge UE ID
  • EAS 920 and/or EES 915 may access EDGE-3 services using the edge UE ID
  • EES 915 may use the UE ID and/or edge UE ID to access a set of APIs of a core network associated with UE 120.
  • Fig. 9 is provided as an example. Other examples may differ from what is described with respect to Fig. 9.
  • Fig. 10 is a diagram illustrating an example 1000 associated with UE identification in an edge communications architecture, in accordance with the present disclosure.
  • an AC 1005, an EEC 1010, an EES 1015, and an EAS 1020 may communicate with one another.
  • AC 1005 and/or EEC 1010 may be components or entities included in or associated with UE 120.
  • EES 1015 and EAS 1020 may be components or entities included in or associated with a network node of an edge network, such as a network node 110 or other network entity.
  • AC 1005 may transmit a request for EEC 1010 to provide an edge UE ID for UE 120.
  • AC 1005 may transmit an EAS ID request to cause EEC 1010 to provide an edge UE ID for UE 120.
  • the request from the AC 1005 may include a list of EASs 1020 associated with the request.
  • EEC 1010 may transmit a request for the edge UE ID to EES 1015 based at least in part on receiving the request from AC 1005.
  • EEC 1010 may provide connectivity information, such as a private IP address, an hPLMN ID, a serving PLMN ID, or the list of EASs 1020 associated with the UE ID request, among other examples to EES 1015.
  • EES 1015 may translate the private IP address to a UE ID, assign an EAS ID specific edge UE ID (e.g., an edge UE ID specific to the EAS 1020) based at least in part on the UE ID, and provide an EEC registration response to EEC 1010 to indicate the edge UE ID.
  • EES 1015 may use the hPLMN ID and the serving PLMN ID to identify an MNO associated with a UE 120 (e.g., associated with AC 1005 and EEC 1010) and translate the private IP into a UE ID based at least in part on identifying the MNO.
  • EES 1015 may use an AC identifier to assign the edge UE ID on a per AC basis.
  • the edge UE ID request may include an AC identifier indicating (e.g., including a field conveying a string, including an index value for a lookup table, or including another type of value, among other examples) the AC 1005, of the plurality of ACs 1005, with which the request is associated.
  • EES 1015 may determine the edge UE ID for the AC 1005 (and other edge UE IDs for other ACs 1005).
  • EEC 1010 may provide a response to the edge UE ID request from AC 1005. For example, EEC 1010 may provide identification information indicating the edge UE ID as a response.
  • AC 1005 may transmit identification information to EAS 1020 and receive an acknowledgement of the identification information from EAS 1020. For example, AC 1005 may transmit an indication of the edge UE ID.
  • EAS 1020 may store the edge UE ID
  • EAS 1020 and/or EES 1015 may access EDGE-3 services using the edge UE ID
  • EES 1015 may use the UE ID and/or edge UE ID to access a set of APIs of a core network associated with UE 120.
  • the private IP address can be an IPv4 address or an IPv6 address.
  • Fig. 10 is provided as an example. Other examples may differ from what is described with respect to Fig. 10.
  • FIG. 11 is a diagram illustrating an example process 1100 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 1100 is an example where the UE (e.g., UE 120) performs operations associated with UE identification.
  • process 1100 may include transmitting identification information, wherein the identification information includes a UE identifier or connectivity information (block 1110).
  • the UE e.g., using communication manager 140 and/or transmission component 1304, depicted in Fig. 13
  • process 1100 may include communicating based at least in part on transmitting the identification information (block 1120).
  • the UE e.g., using communication manager 140 and/or reception component 1302 and/or transmission component 1304, depicted in Fig. 13
  • Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 1100 includes obtaining the UE identifier, and transmitting the identification information comprises transmitting an indication of the UE identifier based at least in part on obtaining the UE identifier.
  • the UE identifier is unavailable, and transmitting the identification information comprises transmitting an indication of the connectivity information based at least in part on the UE identifier being unavailable.
  • process 1100 includes providing the connectivity information to an edge enabler server, and receiving, based at least in part on providing the connectivity information, a UE identifier.
  • the UE identifier includes an edge UE identifier.
  • the edge UE identifier is valid for a period of time constrained by a time interval.
  • the edge UE identifier is associated with the UE.
  • transmitting the identification information comprises transmitting the identification information via an EDGE-5 interface.
  • transmitting the identification information comprises transmitting the identification information to an edge application server by an application client on the UE.
  • process 1100 includes receiving a request for the identification information via an application programming interface, and transmitting the identification information comprises transmitting the identification information based at least in part on receiving the request.
  • transmitting the identification information comprises transmitting a connectivity information type information element that includes the identification information.
  • the connectivity information type information element includes at least one of an internet protocol address, a home public land mobile network identifier, a serving public land mobile network identifier, a slice identifier, a UE identifier such as GPSI, or an edge computing service provider identifier.
  • the identification information includes information identifying a serving public land mobile network.
  • process 1100 includes exposing an identification information service via an edge-1 interface, and transmitting the identification information comprises transmitting the identification information based at least in part on exposing the identification information service.
  • process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.
  • Fig. 12 is a diagram illustrating an example process 1200 performed, for example, by a network node, in accordance with the present disclosure.
  • Example process 1200 is an example where the network node (e.g., network node 110 or the network nodes described with regard to Figs. 4-10) performs operations associated with UE identification.
  • the network node e.g., network node 110 or the network nodes described with regard to Figs. 4-10 performs operations associated with UE identification.
  • process 1200 may include receiving, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information (block 1210).
  • the network node e.g., using communication manager 150 and/or reception component 1402, depicted in Fig. 14
  • process 1200 may include communicating using the identification information (block 1220).
  • the network node e.g., using communication manager 150 and/or reception component 1402 and/or transmission component 1404, depicted in Fig. 14
  • Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • receiving the identification information comprises receiving an indication of the UE identifier.
  • process 1200 includes receiving the connectivity information from an edge enabler client, and transmitting, based at least in part on receiving the connectivity information, a UE identifier.
  • the UE identifier includes an edge UE identifier.
  • the edge UE identifier is valid for a period of time constrained by a time interval.
  • the edge UE identifier is associated with the UE.
  • receiving the identification information comprises receiving the identification information from an application client on the UE.
  • process 1200 includes transmitting a request for the identification information via an application programming interface, and receiving the identification information comprises receiving the identification information based at least in part on receiving the request.
  • receiving the identification information comprises receiving a connectivity information type information element that includes the identification information.
  • the connectivity information type information element includes at least one of an internet protocol address, a home public land mobile network identifier, a serving public land mobile network identifier, a slice identifier, a UE identifier such as GPSI, or an edge computing service provider identifier.
  • the identification information includes information identifying a serving public land mobile network.
  • process 1200 includes accessing an identification information service via an edge-1 interface, and receiving the identification information comprises receiving the identification information based at least in part on accessing the identification information service.
  • process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.
  • Fig. 13 is a diagram of an example apparatus 1300 for wireless communication.
  • the apparatus 1300 may be a UE, or a UE may include the apparatus 1300.
  • the apparatus 1300 includes a reception component 1302 and a transmission component 1304, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
  • the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using the reception component 1302 and the transmission component 1304.
  • the apparatus 1300 may include the communication manager 140.
  • the communication manager 140 may include one or more of an AC component 1308 or an EEC component 1310, among other examples.
  • the apparatus 1300 may be configured to perform one or more operations described herein in connection with Figs. 6-10. Additionally, or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as process 1100 of Fig. 11 or process 1600 of Fig. 16.
  • the apparatus 1300 and/or one or more components shown in Fig. 13 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 13 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non- transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1306.
  • the reception component 1302 may provide received communications to one or more other components of the apparatus 1300.
  • the reception component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1300.
  • the reception component 1302 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1306.
  • one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmission component 1304 for transmission to the apparatus 1306.
  • the transmission component 1304 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1306.
  • the transmission component 1304 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the transmission component 1304 may be co-located with the reception component 1302 in a transceiver.
  • the transmission component 1304 may transmit identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the reception component 1302 and/or the transmission component 1304 may communicate based at least in part on transmitting the identification information.
  • the AC component 1308 and/or the EEC component 1310 may obtain the UE identifier.
  • the AC component 1308 and/or the EEC component 1310 may provide the connectivity information to an edge enabler server.
  • the reception component 1302 may receive, based at least in part on providing the connectivity information, a UE identifier.
  • the reception component 1302 may receive a request for the identification information via an application programming interface.
  • the AC component 1308 and/or the EEC component 1310 may expose an identification information service via an edge-1 interface.
  • Fig. 13 The number and arrangement of components shown in Fig. 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 13. Furthermore, two or more components shown in Fig. 13 may be implemented within a single component, or a single component shown in Fig. 13 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 13 may perform one or more functions described as being performed by another set of components shown in Fig. 13.
  • Fig. 14 is a diagram of an example apparatus 1400 for wireless communication.
  • the apparatus 1400 may be a network node, or a network node may include the apparatus 1400.
  • the apparatus 1400 includes a reception component 1402 and a transmission component 1404, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
  • the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, network node, network entity, or another wireless communication device) using the reception component 1402 and the transmission component 1404.
  • the apparatus 1400 may include the communication manager 150.
  • the communication manager 150 may include a edge computing component 1408, among other examples.
  • the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 6-10. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 1200 of Fig. 12 or process 1500 of Fig. 15.
  • the apparatus 1400 and/or one or more components shown in Fig. 14 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1406.
  • the reception component 1402 may provide received communications to one or more other components of the apparatus 1400.
  • the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1400.
  • the reception component 1402 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2.
  • the transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1406.
  • one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1406.
  • the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1406.
  • the transmission component 1404 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in a transceiver.
  • the reception component 1402 may receive, from a UE, identification information, wherein the identification information includes a UE identifier or connectivity information.
  • the reception component 1402 and/or the transmission component 1404 may communicate using the identification information.
  • the reception component 1402 may receive the connectivity information from an edge enabler client.
  • the transmission component 1404 may transmit, based at least in part on receiving the connectivity information, a UE identifier.
  • the transmission component 1404 may transmit a request for the identification information via an application programming interface.
  • the edge computing component 1408 may access an identification information service via an edge-1 interface.
  • Fig. 14 The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may perform one or more functions described as being performed by another set of components shown in Fig. 14.
  • Fig. 15 is a diagram illustrating an example process 1500 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 1500 is an example where the UE (e.g., UE 120) performs operations associated with UE identification in edge communications.
  • process 1500 may include transmitting a request for identification information, the request including at least one identifier of the UE (block 1510).
  • the UE e.g., using transmission component 1304 and/or communication manager 140, depicted in Fig. 13
  • process 1500 may include receiving, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information (block 1520).
  • the UE may receive, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information, as described above.
  • process 1500 may include communicating based at least in part on receiving the identification information (block 1530).
  • the UE e.g., using reception component 1302, transmission component 1304, and/or communication manager 140, depicted in Fig. 13
  • Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 1500 includes transmitting the identification information, wherein the identification information includes the edge UE identifier, and wherein the one or more processors, to communicate based at least in part on receiving the identification information, are configured to communicate based at least in part on transmitting the identification information.
  • process 1500 includes transmitting connectivity information to an edge enabler server, and receiving, based at least in part on providing the connectivity information, the edge UE identifier.
  • the edge UE identifier is valid for a period of time constrained by a time interval.
  • process 1500 includes transmitting the identification information via an EDGE-5 interface.
  • process 1500 includes transmitting the identification information to an edge application server by an application client on the UE.
  • process 1500 includes receiving a request for the identification information via an application programming interface, and transmitting the identification information based at least in part on receiving the request.
  • process 1500 includes transmitting a connectivity information type information element that includes the identification information.
  • the connectivity information type information element includes at least one of an internet protocol address, a home public land mobile network identifier, a serving public land mobile network identifier, a slice identifier, a UE identifier such as GPSI, or an edge computing service provider identifier.
  • the identification information includes information identifying a serving public land mobile network.
  • process 1500 includes exposing an identification information service via an edge-1 interface, and transmitting the identification information based at least in part on exposing the identification information service.
  • process 1500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 15. Additionally, or alternatively, two or more of the blocks of process 1500 may be performed in parallel.
  • Fig. 16 is a diagram illustrating an example process 1600 performed, for example, by a network node, in accordance with the present disclosure.
  • Example process 1600 is an example where the network node (e.g., network node 110) performs operations associated with UE identification in edge communications.
  • process 1600 may include receiving a request for identification information, the request including at least one identifier of a UE (block 1610).
  • the network node e.g., using reception component 1402 and/or communication manager 150, depicted in Fig. 14
  • process 1600 may include transmitting, as a response to the request for identification information, a response message including the identification information, the identification information including an edge UE identifier assigned to the UE based at least in part on the request for the identification information (block 1620).
  • the network node e.g., using transmission component 1404 and/or communication manager 150, depicted in Fig. 14
  • process 1600 may include communicating based at least in part on transmitting the identification information (block 1630).
  • the network node e.g., using reception component 1402, transmission component 1404, and/or communication manager 150, depicted in Fig. 14
  • Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 1600 includes receiving, from the UE, the identification information, wherein the identification information includes the edge UE identifier, and wherein the one or more processors, to communicate based at least in part on transmitting the identification information, are configured to communicate based at least in part on receiving the identification information.
  • process 1600 includes receiving the connectivity information from an edge enabler client, and transmitting, based at least in part on receiving the connectivity information, the edge UE identifier.
  • the edge UE identifier is valid for a period of time constrained by a time interval.
  • process 1600 includes receiving the identification information from an application client on the UE.
  • process 1600 includes transmitting a request for the identification information via an application programming interface, and receiving the identification information based at least in part on receiving the request.
  • process 1600 includes receiving a connectivity information type information element that includes the identification information.
  • the connectivity information type information element includes at least one of an internet protocol address, a home public land mobile network identifier, a serving public land mobile network identifier, a slice identifier, a UE identifier such as GPSI, or an edge computing service provider identifier.
  • the identification information includes information identifying a serving public land mobile network.
  • process 1600 includes accessing an identification information service via an edge-1 interface, and receiving the identification information based at least in part on accessing the identification information service.
  • process 1600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 16. Additionally, or alternatively, two or more of the blocks of process 1600 may be performed in parallel.
  • Aspect 1 A method of wireless communication performed by a user equipment (UE), comprising: transmitting identification information, wherein the identification information includes a UE identifier or connectivity information; and communicating based at least in part on transmitting the identification information.
  • UE user equipment
  • Aspect 2 The method of Aspect 1, wherein the UE includes an edge enabler client.
  • Aspect 3 The method of any of Aspects 1 to 2, further comprising: transmit the identification information, wherein the identification information includes the edge UE identifier; and communicating based at least in part on transmitting the identification information.
  • Aspect 4 The method of any of Aspects 1 to 3, the received edge UE identifier is valid for a period of time constrained by a time interval.
  • Aspect 5 The method of any of Aspects 1 to 4, further comprising: transmitting the identification information via an EDGE-5 interface to an application client.
  • Aspect 6 The method of any of Aspects 1 to 5, further comprising transmitting the identification information to an edge application server by an application client on the UE.
  • Aspect 7 The method of any of Aspects 1 to 6, further comprising: receiving a request for the identification information via an application programming interface; and transmitting the identification information based at least in part on receiving the request.
  • Aspect 8 The method of any of Aspects 1 to 7, further comprising transmitting a particular identifier of the UE to a network node; and receiving, based at least in part on transmitting the particular identifier of the UE, the edge UE identifier .
  • Aspect 9 The method of any of Aspects 1 to 8, wherein the particular identifier of the UE includes at least one of an internet protocol address, a home public land mobile network identifier, a serving public land mobile network identifier, a slice identifier, a UE identifier, a generic public subscription identifier, or an edge computing service provider identifier.
  • Aspect 10 The method of any of Aspects 1 to 9, wherein the edge UE identifier is valid for use by a pre-configured set of applications.
  • Aspect 11 The method of any of Aspects 1 to 10, wherein the request for identification information is transmitted in connection with an edge enabler client registration request, and wherein the response is received in connection with an edge enabler client registration response.
  • a method of wireless communication performed by a network node comprising: receiving, from a user equipment (UE), identification information, wherein the identification information includes a UE identifier or connectivity information; and communicating using the identification information.
  • UE user equipment
  • Aspect 13 The method of Aspect 12, wherein the network node is an edge enabler server.
  • Aspect 14 The method of any of Aspects 12 to 13, further comprising: receiving, from the UE, the identification information, wherein the identification information includes the edge UE identifier; and communicating based at least in part on receiving the identification information.
  • Aspect 15 The method of any of Aspects 12 to 14, further comprising: receiving a particular identifier of the UE from the UE; and transmitting, based at least in part on receiving the particular identifier of the UE, the edge UE identifier.
  • Aspect 16 The method of any of Aspects 12 to 15, wherein the transmitted edge UE identifier is valid for a period of time constrained by a time interval.
  • Aspect 17 The method of any of Aspects 12 to 16, further comprising: receiving a particular identifier of the UE from an edge enabler client on the UE.
  • Aspect 18 The method of any of Aspects 12 to 17, further comprising: receiving a request for the identification information via an application programming interface; and transmitting the identification information based at least in part on receiving the request.
  • Aspect 19 The method of any of Aspects 12 to 18, further comprising receiving the identifier of the UE included as part of a connectivity information type information element.
  • Aspect 20 The method of any of Aspects 12 to 19, wherein a particular identifier of the UE includes at least one of an internet protocol address, a home public land mobile network identifier, a serving public land mobile network identifier, a slice identifier, a UE identifier, a generic public subscription identifier, or an edge computing service provider identifier.
  • Aspect 21 The method of any of Aspects 12 to 20, wherein the transmitted edge UE identifier is valid for use by one or more pre-configured applications.
  • Aspect 22 The method of any of Aspects 12 to 21, wherein the request for identification information is received in connection with an edge enabler client registration request, and wherein the response is transmitted in connection with an edge enabler client registration response.
  • Aspect 23 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-22.
  • Aspect 24 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-22.
  • Aspect 25 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-22.
  • Aspect 26 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instmctions executable by a processor to perform the method of one or more of Aspects 1-22.
  • Aspect 27 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-22.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).
  • the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Power Engineering (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
EP23708107.0A 2022-02-08 2023-01-26 Benutzergeräteidentifizierung in edge-kommunikationsarchitektur Pending EP4476642A1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
IN202221006637 2022-02-08
US18/154,698 US20230254912A1 (en) 2022-02-08 2023-01-13 User equipment identification in edge communications architecture
PCT/US2023/061373 WO2023154628A1 (en) 2022-02-08 2023-01-26 User equipment identification in edge communications architecture

Publications (1)

Publication Number Publication Date
EP4476642A1 true EP4476642A1 (de) 2024-12-18

Family

ID=85410239

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23708107.0A Pending EP4476642A1 (de) 2022-02-08 2023-01-26 Benutzergeräteidentifizierung in edge-kommunikationsarchitektur

Country Status (2)

Country Link
EP (1) EP4476642A1 (de)
WO (1) WO2023154628A1 (de)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025065707A1 (en) * 2023-09-29 2025-04-03 Apple Inc. Enablement layer proxy mechanism

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113812134B (zh) * 2019-05-10 2025-04-18 三星电子株式会社 边缘计算服务中用于管理ue的标识符的方法和设备
KR102838527B1 (ko) * 2019-05-10 2025-07-28 삼성전자 주식회사 에지 컴퓨팅 서비스에서 단말의 식별자 관리 방법 및 장치

Also Published As

Publication number Publication date
WO2023154628A1 (en) 2023-08-17

Similar Documents

Publication Publication Date Title
WO2023150996A1 (en) Network assisted information
US20250047737A1 (en) Using an edge repository
EP4381670A1 (de) Konfigurationen eines sounding-referenzsignal-ressourcensatzes
US12568491B2 (en) Scheduling of an uplink transmission of multiple transport blocks
US20250392937A1 (en) Serving cell measurement objects associated with active bandwidth parts
WO2023184131A1 (en) Registration management of personal internet of things network elements
WO2023154628A1 (en) User equipment identification in edge communications architecture
WO2024148447A1 (en) Traffic route selection in personal internet of things networks
WO2024044532A1 (en) Indicating sub-band locations for sub-band full duplex communication
WO2024039546A1 (en) Capability for multiple beamforming codebooks
US20230254912A1 (en) User equipment identification in edge communications architecture
WO2024040553A1 (en) Power control parameters for a configured grant physical uplink shared channel
US20240284240A1 (en) Non-binding analytics-based information for a wireless link
WO2024221378A1 (en) System frame number information for candidate cell
WO2024156071A1 (en) Relay context handling during inactive state
WO2024092703A1 (en) Maximum quantities of timing advance groups
US20240089724A1 (en) Multiplexing at a forwarding node
WO2023066097A1 (en) Performing a transmission of a first subscription using information of a second subscription
US20250063386A1 (en) Artificial intelligence model assistance information
WO2025081376A1 (en) Uplink transmit switching at a user equipment
US20240284455A1 (en) Control resource set and physical downlink control channel puncturing
WO2024011437A1 (en) Physical downlink channel repetitions in subbands
CN118647993A (zh) 边缘通信架构中的用户装备标识
WO2024173694A1 (en) Control resource set and physical downlink control channel puncturing
EP4515751A1 (de) Planung einer uplink-übertragung mehrerer transportblöcke

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20240531

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)