WO2021184330A1 - Accès à un service d'application périphérique - Google Patents

Accès à un service d'application périphérique Download PDF

Info

Publication number
WO2021184330A1
WO2021184330A1 PCT/CN2020/080319 CN2020080319W WO2021184330A1 WO 2021184330 A1 WO2021184330 A1 WO 2021184330A1 CN 2020080319 W CN2020080319 W CN 2020080319W WO 2021184330 A1 WO2021184330 A1 WO 2021184330A1
Authority
WO
WIPO (PCT)
Prior art keywords
ladn
area
request
response
identifier
Prior art date
Application number
PCT/CN2020/080319
Other languages
English (en)
Inventor
Tom Chin
Edward Robert HALL
Alan SOLOWAY
Ajith Tom Payyappilly
Juan Zhang
Huichun LIU
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/080319 priority Critical patent/WO2021184330A1/fr
Priority to PCT/CN2021/077433 priority patent/WO2021169942A1/fr
Publication of WO2021184330A1 publication Critical patent/WO2021184330A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

  • aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for obtaining access to an edge application service.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These 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, etc. ) .
  • available system resources e.g., bandwidth, transmit power, etc.
  • multiple-access systems examples include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, 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, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • LTE-A LTE Advanced
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • New radio e.g., 5G NR
  • 5G NR is an example of an emerging telecommunication standard.
  • NR is a set of enhancements to the LTE mobile standard promulgated by 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 OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) .
  • CP cyclic prefix
  • NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • MIMO multiple-input multiple-output
  • the method generally includes sending, to a first network entity, a request for local area data network (LADN) information, wherein the request includes at least one of an application identifier or a service identifier.
  • LADN local area data network
  • the method also includes receiving, from the first network entity, a response indicating a first LADN and a first area associated with the first LADN and communicating with the first LADN based at least in part on the indicated first area.
  • the method generally includes receiving, from a user equipment (UE) , a request for local area data network (LADN) information, wherein the request includes at least one of an application identifier or a service identifier.
  • LADN local area data network
  • the method also includes determining that an LADN is associated with at least one of the application identifier or the service identifier and sending, to the UE, a response indicating the LADN and an area associated with the LADN.
  • the method generally includes receiving, from a user equipment (UE) , a registration request message including a local area data network (LADN) indication; transmitting, to the UE, a registration accept message without LADN information; receiving, from the UE, a request for LADN information in response to the registration accept message without LADN information.
  • the method also includes transmitting, to the UE, a response indicating an LADN and an area associated with the LADN; transmitting, to the UE, an area identifier associated with the network entity and the area of the LADN; and forwarding traffic between the UE and the LADN.
  • aspects of the present disclosure provide means for, apparatus, processors, and computer-readable mediums for performing the methods described herein.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the appended drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
  • FIG. 1 is a block diagram conceptually illustrating an example wireless communication network, in accordance with certain aspects of the present disclosure.
  • FIG. 2 is a block diagram conceptually illustrating a design of an example a base station (BS) and user equipment (UE) , in accordance with certain aspects of the present disclosure.
  • BS base station
  • UE user equipment
  • FIG. 3 is a block diagram illustrating an example wireless communication network with an edge data network, in accordance with certain aspects of the present disclosure.
  • FIG. 4 illustrates an example signaling flow for communicating local area data network (LADN) information to the UE from the edge data network, in accordance with certain aspects of the present disclosure.
  • LADN local area data network
  • FIG. 5 illustrates an example signaling flow for communicating the LADN information to the UE from a radio access network, in accordance with certain aspects of the present disclosure.
  • FIG. 6 illustrates an example signaling flow of the UE requesting the LADN information from the RAN, in accordance with certain aspects of the present disclosure.
  • FIG. 7 illustrates an example signaling flow for communicating with an LADN of the edge data network, in accordance with certain aspects of the present disclosure.
  • FIG. 8 is a flow diagram illustrating example operations for wireless communication by a UE, in accordance with certain aspects of the present disclosure.
  • FIG. 9 is a flow diagram illustrating example operations for wireless communication by a BS, in accordance with certain aspects of the present disclosure.
  • FIG. 10 is a flow diagram illustrating example operations for wireless communication by an edge device, in accordance with certain aspects of the present disclosure.
  • FIG. 11 illustrates a communications device (e.g., a UE, BS, or edge device) that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • a communications device e.g., a UE, BS, or edge device
  • FIG. 11 illustrates a communications device (e.g., a UE, BS, or edge device) that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums to communicate certain edge data network information to a user equipment (UE) .
  • the UE may obtain the LADN information from an edge data network (e.g., an edge enabler server, an DNS server, an edge application server, and/or an edge configuration server) as further described herein with respect to FIG. 4.
  • the UE may obtain the LADN information from a radio access network (RAN) and identify an LADN for edge services among the LADN information received from the RAN and edge data network, for example, as further described herein with respect to FIG. 5. That is, the LADN information from the RAN may supplement or replace the LADN information from the edge data network.
  • RAN radio access network
  • the UE may request the LADN information from the access network, for example, as further described herein with respect to FIG. 6.
  • the various techniques for communicating the LADN information described herein may reduce the latency in establishing a session with a particular LADN.
  • edge application service access in communication systems, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
  • RAT may also be referred to as a radio technology, an air interface, etc.
  • a frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • the techniques described herein may be used for various wireless networks and radio technologies. While aspects may be described herein using terminology commonly associated with 3G, 4G, and/or new radio (e.g., 5G NR) wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems.
  • 3G, 4G, and/or new radio e.g., 5G NR
  • NR access may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond) , millimeter wave (mmWave) targeting high carrier frequency (e.g., e.g., 24 GHz to 53 GHz or beyond) , massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mmWave millimeter wave
  • mMTC massive machine type communications MTC
  • URLLC ultra-reliable low-latency communications
  • These services may include latency and reliability requirements.
  • These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
  • TTI transmission time intervals
  • QoS quality of service
  • these services may co-exist in the same subframe.
  • NR supports beamforming and beam direction may be dynamically configured.
  • MIMO transmissions with precoding may also be supported.
  • MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE.
  • Multi-layer transmissions with up to 2 streams per UE may be supported.
  • Aggregation of multiple cells may be supported with up to 8 serving cells.
  • FIG. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be performed.
  • the wireless communication network 100 may be an NR system (e.g., a 5G NR network) .
  • the BS 110a includes an edge manager 112 that provides certain LADN information (e.g., LADN information that indicates an LADN and an area associated with the LADN) to a UE, in accordance with aspects of the present disclosure.
  • the UE 120a includes an edge manager 122 that obtains LADN information from the edge data network or RAN, in accordance with aspects of the present disclosure.
  • the edge data network 150 includes an edge manager 152 that provides LADN information to the UE, in accordance with certain aspects of the present disclosure.
  • the wireless communication network 100 may include a number of BSs 110a-z (each also individually referred to herein as BS 110 or collectively as BSs 110) and other network entities.
  • a BS 110 may provide communication coverage for a particular geographic area, sometimes referred to as a “cell” , which may be stationary or may move according to the location of a mobile BS 110.
  • the BSs 110 may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in wireless communication network 100 through various types of backhaul interfaces (e.g., a direct physical connection, a wireless connection, a virtual network, or the like) using any suitable transport network.
  • backhaul interfaces e.g., a direct physical connection, a wireless connection, a virtual network, or the like
  • the BSs 110a, 110b and 110c may be macro BSs for the macro cells 102a, 102b and 102c, respectively.
  • the BS 110x may be a pico BS for a pico cell 102x.
  • the BSs 110y and 110z may be femto BSs for the femto cells 102y and 102z, respectively.
  • a BS may support one or multiple cells.
  • the BSs 110 communicate with UEs 120a-y (each also individually referred to herein as UE 120 or collectively as UEs 120) in the wireless communication network 100.
  • the UEs 120 (e.g., 120x, 120y, etc. ) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.
  • Wireless communication network 100 may also include relay stations (e.g., relay station 110r) , also referred to as relays or the like, that receive a transmission of data and/or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE 120 or a BS 110) , or that relays transmissions between UEs 120, to facilitate communication between devices.
  • relay stations e.g., relay station 110r
  • relays or the like that receive a transmission of data and/or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE 120 or a BS 110) , or that relays transmissions between UEs 120, to facilitate communication between devices.
  • a network controller 130 may be in communication with a set of BSs 110 and provide coordination and control for the BSs 110 (e.g., via a fronthaul or backhaul link) .
  • the network controller 130 may be in communication with a core network 132 (e.g., a 5G Core Network (5GC) ) , which provides various network functions such as Access and Mobility Management, Session Management, User Plane Function, Policy Control Function, Authentication Server Function, Unified Data Management, Application Function, Network Exposure Function, Network Repository Function, Network Slice Selection Function, etc.
  • 5GC 5G Core Network
  • An edge data network 150 may be in communication with one or more BSs 110 and/or the core network 132.
  • the edge data network 150 may provide various edge services to the UEs 120 through the one or more BSs 110. In certain cases, the edge data network 150 may provide prefetching, caching, processing, and/or serving of various content sent to the UE 120.
  • the edge data network 150 may reduce the latency at the UE and/or reduce the demand on backhaul links of the core network 132.
  • FIG. 2 illustrates example components of BS 110a and UE 120a (e.g., the wireless communication network 100 of FIG. 1) , which may be used to implement aspects of the present disclosure.
  • a transmit processor 220 may receive data from a data source 212 and control information from a controller/processor 240.
  • the control information may be for the physical broadcast channel (PBCH) , physical control format indicator channel (PCFICH) , physical hybrid ARQ indicator channel (PHICH) , physical downlink control channel (PDCCH) , group common PDCCH (GC PDCCH) , etc.
  • the data may be for the physical downlink shared channel (PDSCH) , etc.
  • a medium access control (MAC) -control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes.
  • the MAC-CE may be carried in a shared channel such as a physical downlink shared channel (PDSCH) , a physical uplink shared channel (PUSCH) , or a physical sidelink shared channel (PSSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • PSSCH physical sidelink shared channel
  • the processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
  • the transmit processor 220 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • DMRS PBCH demodulation reference signal
  • CSI-RS channel state information reference signal
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a-232t.
  • MIMO modulation reference signal
  • Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 232a-232t may be transmitted via the antennas 234a-234t, respectively.
  • a respective output symbol stream e.g., for OFDM, etc.
  • Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • Downlink signals from modulators 232a-232t may be transmitted via the antennas 234a-234t, respectively.
  • the antennas 252a-252r may receive the downlink signals from the BS 110a and may provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator may further process the input samples (e.g., for OFDM, etc. ) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all the demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to a data sink 260, and provide decoded control information to a controller/processor 280.
  • a transmit processor 264 may receive and process data (e.g., for the physical uplink shared channel (PUSCH) ) from a data source 262 and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor 280.
  • the transmit processor 264 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) .
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modulators in transceivers 254a-254r (e.g., for SC-FDM, etc. ) , and transmitted to the BS 110a.
  • the uplink signals from the UE 120a may be received by the antennas 234, processed by the modulators 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 120a.
  • the receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller/processor 240.
  • the memories 242 and 282 may store data and program codes for BS 110a and UE 120a, respectively.
  • a scheduler 244 may schedule UEs for data transmission on the downlink and/or uplink.
  • Antennas 252, processors 266, 258, 264, and/or controller/processor 280 of the UE 120a and/or antennas 234, processors 220, 230, 238, and/or controller/processor 240 of the BS 110a may be used to perform the various techniques and methods described herein.
  • the controller/processor 240 of the BS 110a has an edge manager 241 that provides certain LADN information (e.g., LADN information that indicates an LADN and an area associated with the LADN) to a UE, according to aspects described herein.
  • LADN information e.g., LADN information that indicates an LADN and an area associated with the LADN
  • the controller/processor 280 of the UE 120a has an edge manager 281 that obtains LADN information from the edge data network or RAN, according to aspects described herein. Although shown at the controller/processor, other components of the UE 120a and BS 110a may be used to perform the operations described herein.
  • NR may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink.
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • NR may support half-duplex operation using time division duplexing (TDD) .
  • OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers may be dependent on the system bandwidth.
  • the minimum resource allocation may be 12 consecutive subcarriers.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover multiple RBs.
  • NR may support a base subcarrier spacing (SCS) of 15 KHz and other SCS may be defined with respect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. ) .
  • SCS base subcarrier spacing
  • FIG. 3 illustrates an example wireless communication network 300 with an edge data network 150, in which aspects of the present disclosure may be practiced.
  • an edge enabled client at a UE 120 may allow an application client 124 to access edge services.
  • the application client 124 may communicate with an edge enabler client 126 using an interface (e.g., shown as EDGE-5) .
  • the edge enabler client 126 may request certain information (such as area information for the edge data network 150) from the edge data network 150 as further described herein.
  • the edge data network 150 may include various network entities including one or more edge application servers 154, an edge enabler server 156, and, in some cases, an edge configuration server 158.
  • the UE 120 may communicate with the edge data network 150 via the edge enabler client 126 through one or more interfaces (e.g., EDGE-1 and EDGE-4) and/or via the radio access network (RAN) 140, while the RAN 140 may communicate with the edge data network 150 via one or more interfaces (e.g., EDGE-2, EDGE-7, and EDGE-8) .
  • a local DNS server may be integrated into the edge data network 150 (e.g., the edge application server or the edge enabler server) , such that the edge data network 150 support its own DNS resolution for edge applications or services.
  • the RAN 140 may include various radio access network entities such as one or more BSs 110 (e.g., a distributed unit) , and in some cases, the network controller 130 (e.g., a central unit) .
  • the RAN 140 may also include the core network 132.
  • the network controller 130 and/or the core network 132 may include a central DNS server that provides DNS resolution across a wireless network.
  • Local caching may be employed in various edge data network deployments, such as mobile content delivery networks (CDNs) or multi-access edge computing (MEC) .
  • CDNs mobile content delivery networks
  • MEC multi-access edge computing
  • local caching is designed to push/pull desired content (e.g., media of various types) to the edge devices closest to the requesting users (e.g., at UEs) .
  • a local cache is physically close to or inside of an edge device such as an edge router or base station. Local caching reduces the traffic load on fronthaul and/or backhaul links and speeds up access times for the requesting users.
  • content may be cached on the network-side close to or inside an edge router (e.g., a user plane function (UPF) in a 5G or NR system, a packet gateway (PGW) in an LTE system, or a gateway general packet radio service (GPRS) support node (GGSN) in a 3G or universal mobile telecommunications service (UMTS) network) , within a core network, or at a base station or a network of base stations.
  • edge router e.g., a user plane function (UPF) in a 5G or NR system, a packet gateway (PGW) in an LTE system, or a gateway general packet radio service (GPRS) support node (GGSN) in a 3G or universal mobile telecommunications service (UMTS) network
  • Prefetching, caching, processing, and/or serving data at edge devices may also reduce overall demand on the fronthaul and/or backhaul links and help limit signaling and user traffic to and/or from core networks.
  • a UE is able to access certain edge devices after receiving information about the edge data network, such as the names (or identities) of local area data networks (LADNs) and the area associated with such LADNs.
  • LADN may include an edge device that provides various edge services such as prefetching, caching, processing, and/or serving content.
  • the UE With the area of the LADN, the UE is able to identify which network entities (e.g., BSs) are in communication with a certain LADN, and with the names of the LADNs, the UE is able to identify which applications or services correspond to the LADN.
  • a particular LADN may provide edge services for certain gaming applications, and the LADN may service a certain area including one or more BSs within a wireless network, such as a public land mobile network (PLMN) .
  • PLMN public land mobile network
  • the UE may obtain the LADN information from the edge data network (e.g., an edge enabler server, an edge application server, an edge configuration server, a domain name system (DNS) server, and/or a local DNS server) as further described herein with respect to FIG. 4.
  • the UE may obtain the LADN information from the RAN (e.g., a BS) and identify an LADN for edge services among the LADN information received from the RAN and edge data network, for example, as further described herein with respect to FIG. 5. That is, the LADN information from the RAN may supplement or replace the LADN information from the edge data network.
  • the UE may request the LADN information from the RAN with a new type of message, for example, as further described herein with respect to FIG. 6.
  • the techniques for communicating the LADN information described herein may provide various sources (e.g., the RAN or various edge devices) for the LADN information and reduce the latency in establishing a session with a particular LADN.
  • the LADN information may indicate an LADN and an area (e.g., an area including one or more BSs) associated with the LADN.
  • the area of the LADN may be a sub-area of a wireless network, such as a public land mobile network (PLMN) .
  • PLMN public land mobile network
  • the area of the LADN may include a cell-specific area including a single cell, an LADN-specific area including one or more cells, or a tracking area including multiple cells.
  • the area of the LADN may be indicated as a list of one or more cell identifiers (e.g., a cell global identity (CGI) ) , one or more tracking areas (e.g., tracking area identities (TAIs) or tracking area codes (TACs) ) , and/or one or more LADN-specific areas.
  • CGI cell global identity
  • An LADN-specific area may be a unique area for an LADN within a wireless network such as a PLMN.
  • the UE may receive the LADN information from the edge data network.
  • FIG. 4 illustrates an example signaling flow for communicating the LADN information to the UE from the edge data network, in accordance with certain aspects of the present disclosure.
  • a protocol data unit (PDU) session may be setup between the UE 120 and the RAN 140.
  • a modem 128 of the 120 may be in communication with the RAN 140 through the PDU session.
  • the edge enabler client 126 of the UE 120 may send a request for LADN information to the edge data network 150.
  • the request for LADN information may include an application identifier (e.g., a unique identifier for a certain application such as a gaming application, video streaming application, navigation application, etc. ) and/or a service identifier (e.g., a unique identifier for a certain type of service such as cloud gaming, live video streaming, augmented reality, vehicle-to-everything (V2X) , URLLC, etc. ) associated with an LADN.
  • an application identifier e.g., a unique identifier for a certain application such as a gaming application, video streaming application, navigation application, etc.
  • a service identifier e.g., a unique identifier for a certain type of service such as cloud gaming, live video streaming, augmented reality, vehicle-to-everything (V2X) , URLLC, etc.
  • the network entity that receives the request for LADN information at the edge data network 150 may include an edge application server, an edge enabler server, an edge configuration server, a DNS server, and/or a local DNS server.
  • the network entity that receives the request for LADN information at the edge data network 150 may be common to a certain area of a wireless network or common to a wireless network (e.g., PLMN) .
  • the request at 404 may be various types of messages, such as a message in a communication protocol, in a DNS protocol, or from an application layer.
  • the communication protocol may include the hypertext transfer protocol (HTTP) or HTTP Secure.
  • HTTP hypertext transfer protocol
  • the request at 404 may be an HTTP GET or POST message.
  • the request at 404 may be a discovery request from an application layer such as the 3GPP SA6 application layer, and in such a case, the network entity that receives the request at the edge data network 150 may include an edge configuration server or edge enabler server.
  • the request at 404 may be a DNS query message, and in such a case, the network entity that receives the request at the edge data network 150 may include a central DNS server, a local DNS server, or DNS resolver.
  • the edge enabler client 126 of the UE 120 may receive, from the edge data network 150, a response indicating the LADN and an area associated with the LADN.
  • the area indicated in the response may also be associated with the application identifier and/or service identifier sent in the request at 404.
  • the response at 406 may be an HTTP RSP (response) message.
  • the response at 406 may be a discovery response for the application layer of the UE (e.g., the 3GPP SA6 application layer) , and in such a case, the network entity that sends the response at the edge data network 150 may include an edge configuration server or edge enabler server.
  • the response at 406 may be a DNS response, and in such a case, the network entity that sends the response at the edge data network 150 may include a central DNS server, a local DNS server, or DNS resolver.
  • the UE 120 may map the application identifier and/or service identifier to the LADN.
  • the UE may determine the LADN (e.g., an LADN identifier such as a data network name (DNN) ) based on the application identifier and/or service identifier sent in the request at 404, and the UE 120 may associate the mapped LADN to the area received at 406.
  • the UE 120 may use a UE route selection policy (URSP) to determine the LADN based on the application identifier and/or service identifier.
  • the UE 120 may communicate with the LADN of the edge data network 150, for example, as further described herein with respect to FIG. 7.
  • communicating with the LADN may include the UE 120 transmitting data to and/or receiving data from the LADN of the edge data network 150 through the RAN 140.
  • the UE may receive the LADN information from the RAN.
  • FIG. 5 illustrates an example signaling flow for communicating the LADN information to the UE from the RAN, in accordance with certain aspects of the present disclosure.
  • the edge enabler client 126 may send an LADN request to the modem 128 of the UE.
  • the UE 120 may transmit, to the RAN 140, a NAS registration request message including an LADN indication.
  • the LADN indication may include the one or more LADN identifiers (e.g., DNNs) provided by the edge enabler client 126.
  • the UE 120 may receive, from the RAN 140, a NAS registration accept message indicating an LADN and an area associated with the LADN.
  • the registration accept message at 506 may include an LADN identifier (e.g., an DNN) and an area identifier (e.g., a list of CGIs and/or TAIs) associated with the LADN identifier.
  • the modem 128 may provide the edge enabler client 126 with the LADN information received at 506.
  • the UE 120 may identify whether a certain network entity of the RAN is part of one of the multiple LADN areas received from the edge data network 150 and the RAN 140. That is, the UE 120 may supplement the LADN information from the RAN with the LADN information from the edge data network 150 in determining whether certain network entities of the RAN are part of a given LADN area. For example, the LADN information from the edge data network 150 and the RAN 140 may be used to setup a PDU session when in coverage of an edge service.
  • the UE 120 may communicate with one of the LADNs of the edge data network 150 identified at 510, for example, as further described herein with respect to FIG. 7.
  • the UE may request the LADN information from the RAN after establishing NAS registration without receiving any LADN information.
  • FIG. 6 illustrates an example signaling flow of the UE requesting the LADN information from the RAN, in accordance with certain aspects of the present disclosure.
  • the edge enabler client 126 may send an LADN request to the modem 128 of the UE.
  • the UE 120 may transmit, to the RAN 140, a NAS registration request message with or without an LADN indication.
  • the UE 120 may receive, from the RAN 140, a NAS registration accept message without LADN information (e.g., an information element (IE) for the LADN information indicates the list of LADNs is empty or has zero entries) .
  • the modem 128 may provide the edge enabler client 126 with the LADN information received at 606.
  • the UE 120 may complete the NAS registration without discovering any LADNs.
  • the edge enabler client 126 of the UE 120 may send an LADN request to the modem 128 of the UE 120.
  • the modem 128 of the UE 120 may transmit, to the RAN 140, a request for LADN information in response to the NAS registration accept message without LADN information.
  • the request at 614 may be a new type of message to directly query the RAN 140 for LADN information before or after NAS registration.
  • the request at 614 may allow the UE to query the Access and Mobility function (AMF) of a core network, such as a 5GC.
  • AMF Access and Mobility function
  • the modem 128 of the UE 120 may receive, from the RAN 140, a response indicating an LADN and an area associated with the LADN.
  • the response may include an LADN identifier (e.g., an DNN) and an area identifier (e.g., a list of CGIs and/or TAIs) associated with the LADN identifier.
  • the response at 616 may be a new type of message for the RAN to provide LADN information to the UE.
  • the new messages at 614 and 616 may provide the UE with an alternative or additional means for obtaining LADN information, and thus, reducing the latency encountered in accessing edge devices.
  • the modem 128 may provide the edge enabler client 126 with the LADN information received at 616.
  • the UE 120 may communicate with one of the LADNs indicated in the LADN information received at 616, for example, as further described herein with respect to FIG. 7.
  • the UE may communicate with an edge device (e.g., an LADN) based at least in part on the LADN information received from the edge data network, and in certain cases, the RAN.
  • FIG. 7 illustrates an example signaling flow for communicating with an LADN of the edge data network, in accordance with certain aspects of the present disclosure.
  • the modem 128 of the UE 120 may receive system information (e.g., a system information block (SIB) ) indicating an area identifier, such as a CGI, TAI, or an LADN-specific area.
  • SIB system information block
  • the UE 120 may provide the edge enabler client 126 with the area identifier received at 702.
  • the UE 120 may identify whether the area identifier corresponds to an LADN area (i.e., an area of the LADN or associated with the LADN) received from the edge data network 150 and/or the RAN 140, for example, as described herein with respect to FIGs. 4-6.
  • the edge enabler client 126 may send, the modem 128 of the UE 120, a setup request message indicating the LADN (e.g., via the DNN) identified at 706.
  • the UE 120 may receive, from the RAN 140, a PDU session establishment response.
  • the modem 128 may provide the edge enabler client 126 with an indication of the successful setup of the PDU session.
  • the UE 120 may communicate with the LADN of the edge data network 150 identified at 706.
  • FIG. 8 is a flow diagram illustrating example operations 800 for wireless communication, in accordance with certain aspects of the present disclosure.
  • the operations 800 may be performed, for example, by a UE (e.g., the UE 120a) .
  • the operations 800 may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor 280 of FIG. 2) .
  • the transmission and reception of signals by the UE in operations 800 may be enabled, for example, by one or more antennas (e.g., antennas 252 of FIG. 2) .
  • the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor 280) obtaining and/or outputting signals.
  • the operations 800 may begin at 802, where the UE sends, to a first network entity (e.g., the edge data network 150, the edge DNS/application server 154, the edge enabler server 156, or the edge configuration server 158) , a request for local area data network (LADN) information.
  • a first network entity e.g., the edge data network 150, the edge DNS/application server 154, the edge enabler server 156, or the edge configuration server 1508
  • the request includes at least one of an application identifier or a service identifier.
  • the UE may receive, from the first network entity, a response indicating a first LADN (e.g., the edge DNS/application server 154) and a first area associated with the first LADN.
  • the UE may communicate with the first LADN based at least in part on the indicated first area.
  • the UE may send the request to the first network entity through a RAN, such as the RAN 140.
  • the UE may transmit one or more packets including the request to the RAN, and the RAN may forward the request to the first network entity, for example, via backhaul interface.
  • the UE may receive the response from the first network entity through the RAN.
  • the first network entity may send the response to the RAN, which may forward the response to the UE by transmitting one or more packets including the response to the UE.
  • the UE may communicate with the first LADN, for example, as described herein with respect to FIG. 7.
  • communicating with the LADN may include the UE transmitting data to and/or receiving data from the LADN of an edge data network through the RAN.
  • the first network entity may be a network entity of an edge data network.
  • the first network entity may be an edge device including an edge application server, a local DNS server, an edge enabler server, and/or an edge configuration server.
  • the request at 802 and/or response at 804 may be various types of messages, such as a message in a communication protocol, in a DNS protocol, or at an application layer of the UE.
  • the request and response are messages in a communication protocol.
  • the communication protocol may include HTTP or HTTP Secure.
  • HTTP or HTTP Secure the request may be an HTTP GET or POST message, and the response may be an HTTP RSP (response) message.
  • the request may be a discovery request from an application layer of the UE (e.g., the 3GPP SA6 application layer)
  • the response may be a discovery response for the application layer of the UE (e.g., the 3GPP SA6 application layer) .
  • the first network entity may be an edge configuration server or edge enabler server.
  • the request and response may be messages in a DNS protocol.
  • the request may be an DNS query
  • the response may be an DNS response.
  • the request is an extension to an DNS query (such as a 3GPP SA2 extension)
  • the response is included in an extension to an DNS response.
  • the response may include a TXT record with one or more LADN identifiers to add context to the DNS record.
  • the first network entity may be a central DNS server, a local DNS server, or a DNS resolver.
  • communicating with the LADN at 806 may include the UE mapping the application identifier or service identifier to an LADN.
  • the UE may determine an LADN identifier (e.g., a DNN) associated with at least one of the application identifier or the service identifier according to a UE route selection policy (URSP) .
  • the URSP may identify which PDU session on a network slice (e.g., an IoT slice, eMBB slice, or URLLC slice) a given service or application is to use when the service or application is activated.
  • the UE may identify that the LADN identifier corresponds to the first LADN.
  • the UE may communicate with the first LADN based on the identification of the LADN identifier. For example, after activating a service or application, the UE may communicate with the first LADN associated with the LADN identifier when the UE has entered the coverage area of the first LADN.
  • the UE may receive the LADN information from the RAN and use that LADN information to supplement or replace the LADN information from the edge data network.
  • the UE may transmit, to a second network entity (e.g., the BS 110) , a non-access stratum (NAS) registration request message including an LADN indication.
  • the LADN indication may include one or more LADN identifiers (e.g., DNNs) for which the UE is requesting area information.
  • the second network entity may be a base station, an access point, a gNodeB, a relay station, a network controller, or any other suitable wireless communication device in a wireless network.
  • the UE may receive, from the second network entity, a NAS registration accept message indicating a second LADN and a second area associated with the second LADN.
  • the registration accept message at 506 may include an LADN identifier (e.g., an DNN) and an area identifier (e.g., a list of CGIs and/or TAIs) associated with the LADN identifier.
  • the UE may receive, from the second network entity, an area identifier associated with the second network entity.
  • the UE may receive system information (e.g., a SIB) indicating an area identifier (such as a CGI, TAI, or an LADN-specific area) associated with an LADN.
  • SIB system information
  • the UE may identify that the area identifier corresponds to the first area (from the edge data network) or the second area (from the RAN) .
  • the UE may communicate with the first LADN or the second LADN based on the identification, for example, as described herein with respect to FIG. 7.
  • the UE may request the LADN information from the RAN after establishing NAS registration without receiving any LADN information, for example, as described herein with respect to FIG. 6.
  • the UE may transmit, to a second network entity, a NAS registration request message including an LADN indication.
  • the UE may receive, from the second network entity, a NAS registration accept message without LADN information.
  • the UE may transmit, to the second network entity, a request for LADN information in response to the NAS registration accept message without LADN information.
  • the request may be a new type of message to directly query the RAN for LADN information before or after NAS registration.
  • the UE may receive, from the second network entity, a response indicating a second LADN and a second area associated with the second LADN.
  • the response may include an LADN identifier (e.g., an DNN) and an area identifier (e.g., a list of CGIs and/or TAIs) associated with the LADN identifier.
  • the response may be a new type of message for the RAN to provide LADN information to the UE.
  • the new request and response messages may provide the UE with an alternative or additional means for obtaining LADN information, and thus, reduce the latency encountered in accessing edge devices.
  • the UE may receive, from the second network entity, an area identifier (e.g., a CGI, TAIs, or an LADN-specific area) associated with the second network entity and/or an LADN.
  • an area identifier e.g., a CGI, TAIs, or an LADN-specific area
  • the UE may identify that the area identifier corresponds to the first area (from the edge data network) or the second area (from the RAN) , and the UE may communicate with the first LADN or the second LADN based on the identification.
  • communicating with the first LADN may include receiving, from a second network entity, an area identifier associated with the second network entity and/or an LADN (e.g., the first LADN or second LADN) .
  • the UE may receive system information (e.g., a system information block (SIB) ) indicating an area identifier (such as a CGI, TAI, or an LADN-specific area) associated with an LADN.
  • SIB system information block
  • the UE may identify that the area identifier corresponds to the first area, and the UE may communicate with the first LADN based on the identification.
  • the LADN may be indicated by a data network name (DNN) .
  • the DNN is in the form of an access point name (e.g., service1. xyz. com) .
  • the first LADN may be indicated in the response from the first network entity by a DNN.
  • the area of the LADN may be indicated by one or more area identifiers, for example, one or more cell-specific identifier (e.g., a CGI) or an area-specific identifier (e.g., a TAI or LADN-specific identifier) .
  • the first area may be indicated in the response from the first network entity by at least one of one or more cell identifiers or one or more area identifiers.
  • the one or more area identifiers may include a tracking area identifier or an LADN-specific identifier.
  • the LADN-specific identifier may be a unique identifier for the area of an LADN within a wireless network such as a PLMN.
  • the area of an LADN may include one or more cells or base stations.
  • FIG. 9 is a flow diagram illustrating example operations 900 for wireless communication, in accordance with certain aspects of the present disclosure.
  • the operations 900 may be performed, for example, by a network entity (e.g., the BS 110a) .
  • the operations 900 may be complimentary to the operations 800 performed by the UE.
  • the operations 900 may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor 240 of FIG. 2) .
  • the transmission and reception of signals by the BS in operations 900 may be enabled, for example, by one or more antennas (e.g., antennas 234 of FIG. 2) .
  • the transmission and/or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., controller/processor 240) obtaining and/or outputting signals.
  • the operations 900 may begin at 902, where the network entity may receive, from a UE (e.g., the UE 120) , a registration request message including an LADN indication.
  • the network entity may transmit, to the UE, a registration accept message without LADN information.
  • the network entity may receive, from the UE, a request for LADN information in response to the registration accept message without LADN information.
  • the network entity may transmit, to the UE, a response indicating an LADN and an area associated with the LADN.
  • the network entity may transmit, to the UE, an area identifier associated with the network entity and the area of the LADN.
  • the network entity may forward traffic between the UE and the LADN.
  • the request at 906 may be a new type of message for the UE to directly query the RAN for LADN information before or after NAS registration.
  • the response at 908 may be a new type of message for the RAN to provide LADN information to the UE.
  • the response at 908 may include an LADN identifier (e.g., a DNN) and one or more area identifiers associated with the LADN.
  • the new request and response messages may provide the UE with an alternative or additional means for obtaining LADN information, and thus, reduce the latency encountered in accessing edge devices.
  • the network entity may transmit system information (e.g., a SIB) indicating an area identifier (such as a CGI, TAI, or an LADN-specific area) associated with an LADN.
  • system information e.g., a SIB
  • an area identifier such as a CGI, TAI, or an LADN-specific area
  • the network entity may forward downlink traffic from the LADN to the UE, and in certain cases, the network entity may forward uplink traffic from the UE to the LADN.
  • the registration request and registration accept may be received or sent via NAS signaling.
  • the registration request message is a NAS registration request message
  • the registration accept message is a NAS registration accept message.
  • the LADN may be indicated by a data network name (DNN) .
  • the DNN is in the form of an access point name (e.g., service1. xyz. com) .
  • the LADN may be indicated in the response from the network entity by a DNN.
  • the area of the LADN may be indicated by one or more area identifiers, for example, one or more cell-specific identifier (e.g., a CGI) or an area-specific identifier (e.g., a TAI or LADN-specific identifier) .
  • the area may indicated in the response from the network entity by at least one of one or more cell identifiers or one or more area identifiers.
  • the one or more area identifiers may include a tracking area identifier or an LADN-specific identifier.
  • the LADN-specific identifier may be a unique identifier for the area of an LADN within a wireless network such as a PLMN.
  • the area of an LADN may include one or more cells or base stations.
  • FIG. 10 is a flow diagram illustrating example operations 1000 for wireless communication, in accordance with certain aspects of the present disclosure.
  • the operations 1000 may be performed, for example, by a network entity (e.g., the edge data network 150, the edge DNS/Application server 154, the edge enabler server 156, or the edge configuration server 158) .
  • the operations 1000 may be complimentary to the operations 800 performed by the UE.
  • the operations 1000 may be implemented as software components that are executed and run on one or more processors of the edge data network or an edge device.
  • the operations 1000 may begin at 1002, where the network entity may receive, from a UE (e.g., the UE 120) , a request for LADN information.
  • the request includes at least one of an application identifier or a service identifier.
  • the network entity may determine that an LADN is associated with at least one of the application identifier or the service identifier.
  • the network entity may send, to the UE, a response indicating the LADN and an area associated with the LADN.
  • the network entity may receive the request from the UE through a RAN, such as the RAN 140.
  • a UE may transmit one or more packets including the request to the RAN, and the RAN may forward the request to the network entity, for example, via a backhaul interface.
  • the network entity may send the response to the UE through the RAN.
  • the network entity may send the response to the RAN via the backhaul interface, and the RAN may forward the response to the UE by transmitting one or more packets including the response to the UE.
  • the network entity may include an edge device which provides certain edge services assigned to the LADN.
  • the network entity may communicate with the UE via another network entity, such as the RAN, where the LADN includes the network entity and the other network entity.
  • the network entity may communicate with the UE, for example, as described herein with respect to FIG. 7.
  • communicating with the UE may include the network entity receiving data from and/or sending data to the UE through the RAN.
  • the request at 1002 and/or response at 1006 may be various types of messages, such as a message in a communication protocol, in a DNS protocol, or at an application layer of the UE.
  • the request and response are messages in a communication protocol.
  • the communication protocol may include HTTP or HTTP Secure.
  • HTTP or HTTP Secure the request may be an HTTP GET or POST message, and the response may be an HTTP RSP (response) message.
  • the request may be a discovery request from an application layer of the UE (e.g., the 3GPP SA6 application layer)
  • the response may be a discovery response for the application layer of the UE (e.g., the 3GPP SA6 application layer) .
  • the network entity may be an edge configuration server or edge enabler server.
  • the request and response may be messages in a DNS protocol.
  • the request may be an DNS query
  • the response may be an DNS response.
  • the request is an extension to an DNS query (such as a 3GPP SA2 extension)
  • the response is included in an extension to an DNS response.
  • the response may include a TXT record with one or more LADN identifiers to add context to the DNS record.
  • the network entity may be a central DNS server, a local DNS server, or DNS resolver.
  • the LADN may be indicated by a data network name (DNN) .
  • the DNN is in the form of an access point name (e.g., service1. xyz. com) .
  • the LADN may be indicated in the response from the network entity by a DNN.
  • the area of the LADN may be indicated by one or more area identifiers, for example, one or more cell-specific identifier (e.g., a CGI) or an area-specific identifier (e.g., a TAI or LADN-specific identifier) .
  • the area may be indicated in the response from the network entity by at least one of one or more cell identifiers or one or more area identifiers.
  • the one or more area identifiers may include a tracking area identifier or an LADN-specific identifier.
  • the LADN-specific identifier may be a unique identifier for the area of an LADN within a wireless network such as a PLMN.
  • the area of an LADN may include one or more cells or base stations.
  • FIG. 11 illustrates a communications device 1100 (e.g., a UE, BS, or edge device) that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIGs. 8-10.
  • the communications device 1100 includes a processing system 1102 coupled to a transceiver 1108 (e.g., a transmitter and/or a receiver) .
  • the transceiver 1108 is configured to transmit and receive signals for the communications device 1100 via an antenna 1110, such as the various signals as described herein.
  • the processing system 1102 may be configured to perform processing functions for the communications device 1100, including processing signals received and/or to be transmitted by the communications device 1100.
  • the processing system 1102 includes a processor 1104 coupled to a computer-readable medium/memory 1112 via a bus 1106.
  • the computer-readable medium/memory 1112 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 1104, cause the processor 1104 to perform the operations illustrated in FIGs. 8-10, or other operations for performing the various techniques discussed herein for edge access.
  • computer-readable medium/memory 1112 stores code for receiving 1114, code for transmitting 1116, code for sending 1118, code for determining (or identifying) 1120, and/or code for communicating 1122.
  • the processor 1104 has circuitry configured to implement the code stored in the computer-readable medium/memory 1112.
  • the processor 1104 includes circuitry for receiving 1124, circuitry for transmitting 1126, circuitry for sending 1128, circuitry for determining (or identifying) 1130, and/or circuitry for communicating 1132.
  • NR e.g., 5G NR
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA Universal Terrestrial Radio Access
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as NR (e.g. 5G RA) , Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, etc.
  • NR e.g. 5G RA
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • LTE and LTE-A are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • NR is an emerging wireless communications technology under development.
  • the term “cell” can refer to a coverage area of a Node B (NB) and/or a NB subsystem serving this coverage area, depending on the context in which the term is used.
  • NB Node B
  • BS next generation NodeB
  • AP access point
  • DU distributed unit
  • TRP transmission reception point
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • a UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE) , a cellular phone, 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.
  • CPE Customer Premises Equipment
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine-type communication
  • eMTC evolved MTC
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a BS, another device (e.g., remote device) , or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • a network e.g., a wide area network such as Internet or a cellular network
  • Some UEs may be considered Internet-of-Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.
  • IoT Internet-of-Things
  • NB-IoT narrowband IoT
  • a scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
  • Base stations are not the only entities that may function as a scheduling entity.
  • a UE may function as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs) , and the other UEs may utilize the resources scheduled by the UE for wireless communication.
  • a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network.
  • P2P peer-to-peer
  • UEs may communicate directly with one another in addition to communicating with a scheduling entity.
  • the methods disclosed herein comprise one or more steps or actions for achieving the methods.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “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) .
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • an example hardware configuration may comprise a processing system in a wireless node.
  • the processing system may be implemented with a bus architecture.
  • the bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints.
  • the bus may link together various circuits including a processor, machine-readable media, and a bus interface.
  • the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
  • the network adapter may be used to implement the signal processing functions of the PHY layer.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • the bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
  • the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
  • the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium.
  • Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • the processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media.
  • a computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
  • the machine- readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files.
  • machine-readable storage media may include, by way of example, RAM (Random Access Memory) , flash memory, ROM (Read Only Memory) , PROM (Programmable Read-Only Memory) , EPROM (Erasable Programmable Read-Only Memory) , EEPROM (Electrically Erasable Programmable Read-Only Memory) , registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • PROM Programmable Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrical Erasable Programmable Read-Only Memory
  • registers magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • the machine-readable media may be embodied in a computer-program product.
  • a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
  • the computer-readable media may comprise a number of software modules.
  • the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
  • the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
  • a software module may be loaded into RAM from a hard drive when a triggering event occurs.
  • the processor may load some of the instructions into cache to increase access speed.
  • One or more cache lines may then be loaded into a general register file for execution by the processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared (IR) , radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media) .
  • computer-readable media may comprise transitory computer-readable media (e.g., a signal) . Combinations of the above should also be included within the scope of computer-readable media.
  • certain aspects may comprise a computer program product for performing the operations presented herein.
  • a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein, for example, instructions for performing the operations described herein and illustrated in FIG. 8, FIG. 9, and/or FIG. 10.
  • modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
  • a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
  • various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc. ) , such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
  • storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
  • CD compact disc
  • floppy disk etc.
  • any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Certains aspects de la présente divulgation concernent des techniques d'accès à un service d'application périphérique. Un procédé susceptible d'être exécuté par un équipement utilisateur (UE) comprend en général les étapes consistant à : envoyer à une première entité de réseau une demande d'informations d'un réseau local de données (LADN), la demande contenant un identifiant d'application et/ou un identifiant de service; recevoir de la première entité de réseau une réponse indiquant un premier LADN et une première zone associée au premier LADN; et communiquer avec le premier LADN au moins en partie sur la base de la première zone indiquée.
PCT/CN2020/080319 2020-02-27 2020-03-20 Accès à un service d'application périphérique WO2021184330A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/080319 WO2021184330A1 (fr) 2020-03-20 2020-03-20 Accès à un service d'application périphérique
PCT/CN2021/077433 WO2021169942A1 (fr) 2020-02-27 2021-02-23 Accès à un service d'application périphérique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/080319 WO2021184330A1 (fr) 2020-03-20 2020-03-20 Accès à un service d'application périphérique

Publications (1)

Publication Number Publication Date
WO2021184330A1 true WO2021184330A1 (fr) 2021-09-23

Family

ID=77769590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/080319 WO2021184330A1 (fr) 2020-02-27 2020-03-20 Accès à un service d'application périphérique

Country Status (1)

Country Link
WO (1) WO2021184330A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279397A1 (en) * 2017-03-27 2018-09-27 Qualcomm Incorporated Local area data network connectivity
WO2019052434A1 (fr) * 2017-09-12 2019-03-21 华为技术有限公司 Procédé, appareil, et système de transmission de données fondés sur l'emplacement d'un équipement utilisateur
WO2019076195A1 (fr) * 2017-10-16 2019-04-25 华为技术有限公司 Procédé de gestion de mobilité, terminal et dispositif de réseau central

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279397A1 (en) * 2017-03-27 2018-09-27 Qualcomm Incorporated Local area data network connectivity
WO2019052434A1 (fr) * 2017-09-12 2019-03-21 华为技术有限公司 Procédé, appareil, et système de transmission de données fondés sur l'emplacement d'un équipement utilisateur
WO2019076195A1 (fr) * 2017-10-16 2019-04-25 华为技术有限公司 Procédé de gestion de mobilité, terminal et dispositif de réseau central

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TDIA ET AL.: "Addition of 5GC Test case 10.1.5.1", 3GPP TSG-RAN5 MEETING #82， R5-192816, 1 March 2019 (2019-03-01), XP051608578 *

Similar Documents

Publication Publication Date Title
US11172426B2 (en) Techniques for routing ID update
CN113994718B (zh) 演进型分组系统和第五代系统的互通中的用户装备策略管理
US11540181B2 (en) Handling of network slice information for roaming user equipment (UE)
US11729744B2 (en) Determining numerology for sidelink communication
WO2020244312A1 (fr) Informations de priorité de service pour radiomessagerie d'équipement utilisateur multi-sim
US20230199557A1 (en) Compression techniques for data and reference signal resource elements (res)
US20240129720A1 (en) Restricted access and use control for user equipment with reduced capabilities
US20210099945A1 (en) Reduced overhead network slice selection assistance information (nssai) signaling
EP4085690A1 (fr) Sélection de fonction d'interfonctionnement par un équipement d'utilisateur distant
US20230141754A1 (en) Ensuring compatibility between network slice operating frequencies and user equipment (ue) radio capabilities
WO2022021088A1 (fr) Restriction relative à des informations d'aide à la sélection d'une tranche de réseau unique dans une politique de sélection de trajet d'équipement utilisateur
WO2022000129A1 (fr) Routage de tranchage multi-réseau pour des plmn doubles d'équipements utilisateurs de module d'identité d'abonné doubles
WO2021217565A1 (fr) Gestion de rapport de mesure pour réduire les défaillances de session de communication pendant un transfert intercellulaire
WO2021184330A1 (fr) Accès à un service d'application périphérique
WO2021226942A1 (fr) Restauration de données en paquets commutés lorsqu'un support par défaut est supprimé
WO2022236660A1 (fr) Gestion d'adresse ip d'ue et de cartographie d'id d'ue
WO2021248358A1 (fr) Communications sans fil par dispositif à double sim
WO2021223203A1 (fr) Auto-adaptation d'ue pour connexion de session pdu dans un réseau autonome 5g
WO2022067623A1 (fr) Informations d'aide à la sélection unique d'une tranche de réseau (s-nssai) mappées pour des réseaux mobiles terrestres publics équivalents (eplmn)
US20230016194A1 (en) Modifying a configuration of a radio bearer based on a request for quality of service (qos) for a communication flow
WO2021223132A1 (fr) Liste étendue de cellules voisines
WO2021168766A1 (fr) Coordination de radiomessagerie par internet
WO2021243725A1 (fr) Évitement de problèmes d'accès aléatoire dans des cellules de nouvelle radio non autonomes
WO2021258387A1 (fr) Réduction du coût d'itinérance dans nr
WO2021146974A1 (fr) Techniques d'inscription de réseau

Legal Events

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

Ref document number: 20926210

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20926210

Country of ref document: EP

Kind code of ref document: A1