WO2021155552A1 - Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn) - Google Patents

Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn) Download PDF

Info

Publication number
WO2021155552A1
WO2021155552A1 PCT/CN2020/074470 CN2020074470W WO2021155552A1 WO 2021155552 A1 WO2021155552 A1 WO 2021155552A1 CN 2020074470 W CN2020074470 W CN 2020074470W WO 2021155552 A1 WO2021155552 A1 WO 2021155552A1
Authority
WO
WIPO (PCT)
Prior art keywords
dnn
ladn
service
ladn service
pdu session
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.)
Ceased
Application number
PCT/CN2020/074470
Other languages
English (en)
Inventor
Tom Chin
Ajith Tom Payyappilly
Juan Zhang
Huichun LIU
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
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/074470 priority Critical patent/WO2021155552A1/fr
Publication of WO2021155552A1 publication Critical patent/WO2021155552A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information

Definitions

  • This disclosure relates generally to wireless communications and, more specifically, to establishing a protocol data unit (PDU) session with a local area data network (LADN) service.
  • PDU protocol data unit
  • LADN local area data network
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (such as time, frequency, and power) .
  • multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems (such as a Long Term Evolution (LTE) system or a Fifth Generation (5G) New Radio (NR) system) .
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • LTE Long Term Evolution
  • NR Fifth Generation
  • a wireless multiple-access communications system may include a number of base stations or access network nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • 5G New Radio NR
  • 3GPP Third Generation Partnership Project
  • 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable low latency communications
  • the method may be performed by a user equipment (UE) including at least a modem and a high-level operating system (HLOS) configured to execute an application on the UE, and may include sending a local area data network (LADN) Registration Request from the application to the modem via the HLOS, the LADN Registration Request including at least a data network name (DNN) of the LADN service; transmitting, to a core network associated with a radio access network (RAN) , a registration request message including a request to register the application with the LADN service and indicating the DNN of the LADN service; receiving, from the core network, a registration accept message including the DNN of the LADN service and a tracking area identity (TAI) associated with the DNN; sending a LADN indication message from the modem to the application via the HLOS, the LADN indication message including the DNN of the LADN service, the TAI associated with the DNN, and an indication that the UE application is registered
  • LADN local area data network
  • TAI tracking area identity
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCCH physical downlink control channel
  • establishing the PDU session may include transmitting, to the core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may be determined to be within the LADN service area when the TAI associated with the DNN matches one TAI of the number of TAIs in the broadcasted TAI list, and the UE may be determined to be outside the LADN service area when the TAI associated with the DNN does not match any TAI of the number of TAIs in the broadcasted TAI list. In some other implementations, determining whether the UE is within the LADN service area also may be based on a cell identity (ID) of the BS.
  • ID cell identity
  • the method also may include sending a setup request from the application to the modem via the HLOS, and sending a setup response from the modem to the application via the HLOS.
  • the setup request may include the DNN of the LADN service and a request to register the application with the LADN service, and the setup response may indicate successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may include one or more processors, a memory, a modem, and a high-level operating system (HLOS) configured to execute an application on the UE.
  • the memory may be coupled to the one or more processors, and may store instructions that, when executed by the one or more processors, cause the UE to perform a number of operations.
  • the number of operations may include sending a local area data network (LADN) Registration Request from the application to the modem via the HLOS, the LADN Registration Request including at least a data network name (DNN) of the LADN service; transmitting, to a core network associated with a radio access network (RAN) , a registration request message including a request to register the application with the LADN service and indicating the DNN of the LADN service; receiving, from the core network, a registration accept message including the DNN of the LADN service and a tracking area identity (TAI) associated with the DNN; sending a LADN indication message from the modem to the application via the HLOS, the LADN indication message including the DNN of the LADN service, the TAI associated with the DNN, and an indication that the UE application is registered with the LADN service; receiving, from a base station (BS) , a broadcasted TAI list containing a number of TAIs indicative of a coverage area of the BS; determining whether the UE is within a
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCCH physical downlink control channel
  • establishing the PDU session may include transmitting, to the core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may be determined to be within the LADN service area when the TAI associated with the DNN matches one TAI of the number of TAIs in the broadcasted TAI list, and the UE may be determined to be outside the LADN service area when the TAI associated with the DNN does not match any TAI of the number of TAIs in the broadcasted TAI list. In some other implementations, determining whether the UE is within the LADN service area also may be based on a cell identity (ID) of the BS.
  • ID cell identity
  • execution of the instructions may cause the UE to perform operations further including sending a setup request from the application to the modem via the HLOS, and sending a setup response from the modem to the application via the HLOS.
  • the setup request may include the DNN of the LADN service and a request to register the application with the LADN service
  • the setup response may indicate successful establishment of the PDU session with the DNN of the LADN service.
  • the method may be performed by a user equipment (UE) including at least a modem and a high-level operating system (HLOS) configured to execute an application on the UE, and may include sending a Request and Setup message from the application to the modem via the HLOS; and transmitting, to a core network associated with a radio access network (RAN) , a message including a request to register the application with a local area data network (LADN) service, a request to setup a protocol data unit (PDU) session with a data network name (DNN) of the LADN service when available to the UE, and the DNN of the LADN service.
  • the Request and Setup message may include a request to register the application with the LADN service, a request to setup the PDU session with the LADN service when available to the UE, and the DNN of the LADN service.
  • the method also may include receiving, from the core network, an accept message; determining that the LADN service is available to the UE; and establishing the PDU session with the DNN of the LADN service based on the determination that the LADN service is available to the UE and the request to setup the PDU session.
  • the accept message may include the DNN of the LADN service, a tracking area identity (TAI) associated with the DNN, and an indication that the UE is registered with the LADN service.
  • determining that the LADN service area is available to the UE may include receiving a UE Presence Indication from the core network.
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCCH physical downlink control channel
  • establishing the PDU session may include transmitting, to the core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may include one or more processors, a memory, a modem, and a high-level operating system (HLOS) configured to execute an application on the UE.
  • the memory may be coupled to the one or more processors, and may store instructions that, when executed by the one or more processors, cause the UE to perform a number of operations.
  • the number of operations may include sending a Request and Setup message from the application to the modem via the HLOS; and transmitting, to a core network associated with a radio access network (RAN) , a message including a request to register the application with a local area data network (LADN) service, a request to setup a protocol data unit (PDU) session with a data network name (DNN) of the LADN service when available to the UE, and the DNN of the LADN service.
  • the Request and Setup message may include a request to register the application with the LADN service, a request to setup the PDU session with the LADN service when available to the UE, and the DNN of the LADN service.
  • execution of the instructions may cause the UE to perform operations further including receiving, from the core network, an accept message; determining that the LADN service is available to the UE; and establishing the PDU session with the DNN of the LADN service based on the determination that the LADN service is available to the UE and the request to setup the PDU session.
  • the accept message may include the DNN of the LADN service, a tracking area identity (TAI) associated with the DNN, and an indication that the UE is registered with the LADN service.
  • determining that the LADN service area is available to the UE may include receiving a UE Presence Indication from the core network.
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCCH physical downlink control channel
  • establishing the PDU session may include transmitting, to the core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the method may be performed by a user equipment (UE) , and may include transmitting a registration request message including a request to register a UE application with a local area data network (LADN) service and indicating at least a data network name (DNN) of the LADN service; receiving a registration accept message including the DNN of the LADN service and a tracking area identity (TAI) associated with the DNN; receiving, from a base station (BS) , a broadcasted TAI list containing a number of TAIs indicative of a coverage area of the BS; determining whether the UE is within a service area of the LADN based at least in part on a comparison between the TAI associated with the DNN and the number of TAIs in the broadcasted TAI list; and establishing a protocol data unit (PDU) session with the DNN of the LADN service based on the determination indicating that the UE is within a service area of the LADN
  • PDU protocol data unit
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCCH physical downlink control channel
  • establishing the PDU session may include transmitting, to a core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may be determined to be within the LADN service area when the TAI associated with the DNN matches one TAI of the number of TAIs in the broadcasted TAI list, and the UE may be determined to be outside the LADN service area when the TAI associated with the DNN does not match any TAI of the number of TAIs in the broadcasted TAI list. In some other implementations, determining whether the UE is within the LADN service area also may be based on a cell identity (ID) of the BS.
  • ID cell identity
  • the UE also may include at least a modem and a high-level operating system (HLOS) configured to execute the application
  • the method also may include sending a LADN Registration Request from the application to the modem via the HLOS, the LADN Registration Request including at least the DNN of the LADN service; and sending a LADN indication message from the modem to the application via the HLOS, the LADN indication message including the DNN of the LADN service, the TAI associated with the DNN, and an indication that the UE application is registered with the LADN service.
  • HLOS high-level operating system
  • the method also may include sending a setup request from the application to the modem via the HLOS, the setup request including the DNN of the LADN service and a request to register the UE application with the LADN service; and sending a setup response from the modem to the application via the HLOS, the setup response indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may include one or more processors coupled to a memory.
  • the memory may store instructions that, when executed by the one or more processors, cause the UE to perform a number of operations.
  • the number of operations may include transmitting a registration request message including a request to register a UE application with a local area data network (LADN) service and indicating at least a data network name (DNN) of the LADN service; receiving a registration accept message including the DNN of the LADN service and a tracking area identity (TAI) associated with the DNN; receiving, from a base station (BS) , a broadcasted TAI list containing a number of TAIs indicative of a coverage area of the BS; determining whether the UE is within a service area of the LADN based at least in part on a comparison between the TAI associated with the DNN and the number of TAIs in the broadcasted TAI list; and establishing a protocol data unit (PDU) session with the DNN of the LADN service based on the determination indicating that the UE is within a service area of the LADN.
  • LADN local area data network
  • TAI tracking area identity
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCCH physical downlink control channel
  • establishing the PDU session may include transmitting, to a core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the UE may be determined to be within the LADN service area when the TAI associated with the DNN matches one TAI of the number of TAIs in the broadcasted TAI list, and the UE may be determined to be outside the LADN service area when the TAI associated with the DNN does not match any TAI of the number of TAIs in the broadcasted TAI list. In some other implementations, determining whether the UE is within the LADN service area also may be based on a cell identity (ID) of the BS.
  • ID cell identity
  • the UE also may include at least a modem and a high-level operating system (HLOS) configured to execute the application, and the number of operations also may include sending a LADN Registration Request from the application to the modem via the HLOS, the LADN Registration Request including at least the DNN of the LADN service; and sending a LADN indication message from the modem to the application via the HLOS, the LADN indication message including the DNN of the LADN service, the TAI associated with the DNN, and an indication that the UE application is registered with the LADN service.
  • HLOS high-level operating system
  • the number of operations also may include sending a setup request from the application to the modem via the HLOS, the setup request including the DNN of the LADN service and a request to register the UE application with the LADN service; and sending a setup response from the modem to the application via the HLOS, the setup response indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the method may be performed by a user equipment (UE) , and may include transmitting a message including a request to register a UE application with a local area data network (LADN) service, a request to setup a protocol data unit (PDU) session with a data network name (DNN) of the LADN service when available to the UE, and the DNN of the LADN service; receiving an accept message including the DNN of the LADN service, a tracking area identity (TAI) associated with the DNN, and an indication that the UE is registered with the LADN service; determining that the LADN service is available to the UE; and establishing the PDU session with the DNN of the LADN based on the determination and the request to setup the PDU session.
  • LADN local area data network
  • PDU protocol data unit
  • DNN data network name
  • TAI tracking area identity
  • establishing the PDU session may include transmitting, to a core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the method also may include receiving a system information block (SIB) broadcast from a base station (BS) , and determining that the LADN service is available to the UE may be based on identity information included in the broadcasted SIB.
  • the identity information may include at least one of a tracking area identity (TAI) or a cell identifier (ID) .
  • determining that the LADN service is available to the UE may include receiving a UE Presence Indication from a core network.
  • the UE also may include at least a modem and a high-level operating system (HLOS) configured to execute the application
  • the method also may include sending a Request and Setup message from the application to the modem via the HLOS, the Request and Setup message including the request to register the UE application, the request to setup the PDU session, and the DNN of the LADN service; and sending a setup response message from the modem to the application via the HLOS, the setup response message indicating successful establishment of the PDU session with the LADN service.
  • HLOS high-level operating system
  • the UE may include one or more processors coupled to a memory.
  • the memory may store instructions that, when executed by the one or more processors, cause the UE to perform a number of operations.
  • the number of operations may include transmitting a message including a request to register a UE application with a local area data network (LADN) service, a request to setup a protocol data unit (PDU) session with a data network name (DNN) of the LADN service when available to the UE, and the DNN of the LADN service; receiving an accept message including the DNN of the LADN service, a tracking area identity (TAI) associated with the DNN, and an indication that the UE is registered with the LADN service; determining that the LADN service is available to the UE; and establishing the PDU session with the DNN of the LADN based on the determination and the request to setup the PDU session.
  • LADN local area data network
  • PDU protocol data unit
  • DNN data network name
  • TAI tracking area identity
  • establishing the PDU session may include transmitting, to a core network, a PDU Session Establishment request including at least the DNN of the LADN service; and receiving, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • the number of operations also may include receiving a system information block (SIB) broadcast from a base station (BS) , and determining that the LADN service is available to the UE may be based on identity information included in the broadcasted SIB.
  • the identity information may include at least one of a tracking area identity (TAI) or a cell identifier (ID) .
  • determining that the LADN service is available to the UE may include receiving a UE Presence Indication from a core network.
  • the UE also may include at least a modem and a high-level operating system (HLOS) configured to execute the application, and the number of operations also may include sending a Request and Setup message from the application to the modem via the HLOS, the Request and Setup message including the request to register the UE application, the request to setup the PDU session, and the DNN of the LADN service; and sending a setup response message from the modem to the application via the HLOS, the setup response message indicating successful establishment of the PDU session with the LADN service.
  • HLOS high-level operating system
  • Figure 1 shows a diagram illustrating an example wireless communications system.
  • Figure 2A shows an example of a first 5G NR frame.
  • Figure 2B shows example downlink (DL) channels within a 5G NR slot.
  • Figure 2C shows an example of a second 5G NR frame.
  • Figure 2D shows example uplink (UL) channels within a 5G NR slot.
  • Figure 3 shows a diagram illustrating an example base station and user equipment (UE) in an access network.
  • UE user equipment
  • Figure 4 shows a block diagram of an example user equipment (UE) .
  • UE user equipment
  • Figure 5 shows a diagram illustrating another example wireless communications system.
  • Figure 6 shows a sequence diagram for wireless communication that supports establishing a protocol data unit (PDU) session between a UE and a local area data network (LADN) service.
  • PDU protocol data unit
  • LADN local area data network
  • Figure 7 shows another sequence diagram for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figure 8 shows a flowchart depicting an example operation for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figures 9A–9B show flowcharts depicting example operations for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figure 10 shows a flowchart depicting an example operation for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figures 11A–11C show flowcharts depicting example operations for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figure 12 shows a flowchart depicting an example operation for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figures 13A–13D show flowcharts depicting example operations for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figure 14 shows a flowchart depicting an example operation for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • Figures 15A–15C show flowcharts depicting example operations for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the following description is directed to some particular implementations for the purposes of describing innovative aspects of this disclosure.
  • RF radio frequency
  • 3GPP 3rd Generation Partnership Project
  • IEEE Institute of Electrical and Electronics Engineers
  • IEEE 802.11 standards
  • IEEE 802.15 standards
  • SIG Bluetooth Special Interest Group
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • SU single-user
  • MIMO multiple-input multiple-output
  • MU multi-user MIMO
  • the described implementations also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless wide area network (WWAN) , a wireless personal area network (WPAN) , a wireless local area network (WLAN) , or an internet of things (IOT) network.
  • WWAN wireless wide area network
  • WPAN wireless personal area network
  • WLAN wireless local area network
  • IOT internet of things
  • Implementations of the subject matter described in this disclosure may allow UEs to establish a protocol data unit (PDU) session with a LADN service.
  • a UE application seeking access to a local area data network (LADN) service may register with the LADN service and obtain the tracking area identity (TAI) of a data network name (DNN) associated with the LADN service.
  • the TAI of the DNN may be stored in the UE, and may be used to determine when the LADN service is available to the UE.
  • the UE may compare one or more TAIs received in broadcast messages from a serving cell with the TAI of the DNN to determine whether the UE is located within the LADN service area.
  • a match between the TAI of the DNN and one of the TAIs contained in the broadcast messages may indicate that the UE is within the tracking area identified by the matching TAIs, and therefore also may be located in the LADN service area.
  • a mismatch between the TAI of the DNN and all of the TAIs contained in the broadcast messages may indicate that the UE is not within the tracking area identified by the matching TAIs, and therefore may be located outside of the LADN service area.
  • the UE may determine that the LADN service is available, and may request and establish a PDU Session with the DNN of the LADN service.
  • the UE may determine that the LADN service is not available, and may refrain from requesting or establishing the PDU Session with the DNN of the LADN service.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the aforementioned types of computer-readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
  • FIG. 1 shows a diagram of an example wireless communications system 100.
  • the wireless communications system 100 which may be a Next Generation RAN (NG-RAN) , includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190.
  • the base stations 102 may include macrocells (high power cellular base station) or small cells (low power cellular base station) .
  • the macrocells include base stations.
  • the small cells include femtocells, picocells, and microcells.
  • the base stations 102 configured for 4G LTE may interface with the EPC 160 through backhaul links 132 via S1 interfaces, and the base stations 102 configured for 5G NR may interface with the core network 190 through backhaul links 184.
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (such as handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • the base stations 102 may communicate directly or indirectly (such as through the EPC 160 or the core network 190) with each other over backhaul links 134 (such as the X2 interface) .
  • the backhaul links 134 may be wired or wireless.
  • the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macrocells may be known as a heterogeneous network.
  • a heterogeneous network also may include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity.
  • the communication links may be through one or more carriers.
  • the base stations 102 and UEs 104 may use spectrum up to Y MHz (such as 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • D2D communication link 158 may use the DL/UL WWAN spectrum.
  • the D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia,
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 2.4 GHz unlicensed frequency spectrum, a 5 GHz unlicensed frequency spectrum, or both.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 in a 2.4 GHz unlicensed frequency spectrum, a 5 GHz unlicensed frequency spectrum, or both.
  • CCA clear channel assessment
  • the small cell 102’ may operate in a licensed or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102’ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102, ’ employing NR in an unlicensed frequency spectrum, may boost coverage to or increase capacity of the access network.
  • a base station 102 may include an eNB, gNodeB (gNB) , or another type of base station.
  • Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, or near mmW frequencies in communication with the UE 104.
  • mmW millimeter wave
  • mmW base station Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum.
  • EHF Extremely high frequency
  • EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW or near mmW radio frequency band (such as between 3 GHz –300 GHz) has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
  • the base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182’.
  • the UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182” .
  • the UE 104 also may transmit a beamformed signal to the base station 180 in one or more transmit directions.
  • the base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions.
  • the base station 180 and UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 and UE 104.
  • the transmit and receive directions for the base station 180 may or may not be the same.
  • the transmit and receive directions for the UE 104 may or may not be the same.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting MBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195.
  • the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
  • the AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190.
  • the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195.
  • the UPF 195 provides UE IP address allocation as well as other functions.
  • the UPF 195 is connected to the IP Services 197.
  • the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, or other IP services.
  • IMS IP Multimedia Subsystem
  • the base station also may be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 or the core network 190 for a UE 104.
  • Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (such as an MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the UEs 104 may be referred to as IoT devices (such as a parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) .
  • the UE 104 also may be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • Figure 2A shows an example of a first slot 200 within a 5G NR frame structure.
  • Figure 2B shows an example of DL channels 230 within a 5G NR slot.
  • Figure 2C shows an example of a second slot 250 within a 5G NR frame structure.
  • Figure 2D shows an example of UL channels 280 within a 5G NR slot.
  • the 5G NR frame structure may be FDD in which, for a particular set of subcarriers (carrier system bandwidth) , slots within the set of subcarriers are dedicated for either DL or UL transmissions.
  • the 5G NR frame structure may be TDD in which, for a particular set of subcarriers (carrier system bandwidth) , slots within the set of subcarriers are dedicated for both DL and UL transmissions.
  • the 5G NR frame structure is based on TDD, with slot 4 configured with slot format 28 (with mostly DL) , where D indicates DL, U indicates UL, and X indicates that the slot is flexible for use between DL and UL, and with slot 3 configured with slot format 34 (with mostly UL) . While slots 3 and 4 are shown with slot formats 34 and 28, respectively, any particular slot may be configured with any of the various available slot formats 0–61.
  • Slot formats 0 and 1 are all DL and all UL, respectively.
  • Other slot formats 2–61 include a mix of DL, UL, and flexible symbols.
  • UEs may be configured with the slot format, either dynamically through downlink control information (DCI) or semi-statically through radio resource control (RRC) signaling by a slot format indicator (SFI) .
  • DCI downlink control information
  • RRC radio resource control
  • SFI slot format indicator
  • the configured slot format also may apply to a 5G NR frame structure that is based on FDD.
  • a frame may be divided into a number of equally sized subframes. For example, a frame having a duration of 10 microseconds (ms) may be divided into 10 equally sized subframes each having a duration of 1 ms.
  • Each subframe may include one or more time slots.
  • Subframes also may include mini-slots, which may include 7, 4, or 2 symbols.
  • Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols.
  • the symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols.
  • the symbols on UL may be CP-OFDM symbols (such as for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (such as for power limited scenarios) .
  • DFT discrete Fourier transform
  • SC-FDMA single carrier frequency-division multiple access
  • the number of slots within a subframe is based on the slot configuration and the numerology.
  • different numerologies ( ⁇ ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe.
  • different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe.
  • the subcarrier spacing and symbol length/duration are a function of the numerology.
  • the subcarrier spacing may be equal to 2 ⁇ *15 kHz, where ⁇ is the numerology 0 to 5.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the subcarrier spacing is 15 kHz and symbol duration is approximately 66.7 microseconds ( ⁇ s) .
  • a resource grid may be used to represent the frame structure.
  • Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB) ) that extends across 12 consecutive subcarriers and across a number of symbols. The intersections of subcarriers and across 14 symbols. The intersections of subcarriers and of the RB define multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
  • RB resource block
  • PRB physical RB
  • some of the REs carry a reference signal (RS) for the UE.
  • one or more REs may carry a demodulation reference signal (DM-RS) (indicated as Rx for one particular configuration, where 100x is the port number, but other DM-RS configurations are possible) .
  • DM-RS demodulation reference signal
  • one or more REs may carry a channel state information reference signal (CSI-RS) for channel measurement at the UE.
  • the REs also may include a beam measurement reference signal (BRS) , a beam refinement reference signal (BRRS) , and a phase tracking reference signal (PT-RS) .
  • BRS beam measurement reference signal
  • BRRS beam refinement reference signal
  • PT-RS phase tracking reference signal
  • FIG. 2B illustrates an example of various DL channels within a subframe of a frame.
  • the physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including nine RE groups (REGs) , each REG including four consecutive REs in an OFDM symbol.
  • a primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe or symbol timing and a physical layer identity.
  • a secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
  • the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DM-RS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block.
  • the MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) .
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
  • SIBs system information blocks
  • some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station.
  • the UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) .
  • the PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH.
  • the PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used.
  • the UE may transmit sounding reference signals (SRS) .
  • the SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
  • FIG. 2D illustrates an example of various UL channels within a subframe of a frame.
  • the PUCCH may be located as indicated in one configuration.
  • the PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK/NACK feedback.
  • UCI uplink control information
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 shows a block diagram of an example base station 310 and UE 350 in an access network.
  • IP packets from the EPC 160 may be provided to a controller/processor 375.
  • the controller/processor 375 implements layer 3 and layer 2 functionality.
  • Layer 3 includes a radio resource control (RRC) layer
  • layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (such as the MIB and SIBs) , RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs
  • the transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions.
  • Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • the TX processor 316 handles mapping to signal constellations based on various modulation schemes (such as binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) .
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • the coded and modulated symbols may then be split into parallel streams.
  • Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot signal) in the time or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • IFFT Inverse Fast Fourier Transform
  • the OFDM stream is spatially pre-coded to produce multiple spatial streams.
  • Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal or channel condition feedback transmitted by the UE 350.
  • Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX.
  • Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 354RX receives a signal through its respective antenna 352.
  • Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356.
  • the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
  • the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream.
  • the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) .
  • FFT Fast Fourier Transform
  • the frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel.
  • the data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
  • the controller/processor 359 can be associated with a memory 360 that stores program codes and data.
  • the memory 360 may be referred to as a computer-readable medium.
  • the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160.
  • the controller/processor 359 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.
  • the controller/processor 359 provides RRC layer functionality associated with system information (such as the MIB and SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (such as the MIB and SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with header compression /
  • Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • Each receiver 318RX receives a signal through its respective antenna 320.
  • Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
  • the controller/processor 375 can be associated with a memory 376 that stores program codes and data.
  • the memory 376 may be referred to as a computer-readable medium.
  • the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160.
  • the controller/processor 375 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.
  • Information to be wirelessly communicated (such as for LTE or NR based communications) is encoded and mapped, at the PHY layer, to one or more wireless channels for transmission.
  • each antenna 352 of the UE 350 is coupled to a respective transmitter 354TX.
  • the UE 350 may include fewer transmitters (or transmit chains) than receive (RX) antennas.
  • each transmitter may be coupled to a respective power amplifier (PA) which amplifies the signal to be transmitted.
  • PA power amplifier
  • the combination of a transmitter and a PA may be referred to herein as a “transmit chain” or “TX chain. ”
  • the same PA may be reused to transmit signals over multiple RX antennas.
  • one or more TX chains of a UE may be selectively coupled to multiple RX antennas ports.
  • FIG 4 shows a block diagram of an example UE 400.
  • the UE 400 may be one example of the UE 104 of Figure 1 or the UE 350 of Figure 3.
  • the UE 400 may include an application layer 410, a modem control interface (MCI) 420, and a modem 430.
  • the application layer 410 may include hardware or a processor executing software (or both) that can store and execute one or more applications on the UE 400, and may include protocols for exchanging communications across an Internet Protocol (IP) network.
  • IP Internet Protocol
  • the application layer 410 includes an application processor 412 and a memory 414 coupled one another by a bus 415.
  • the application layer 410 is coupled to the modem 430 by the MCI 420, and may be responsible for executing one or more software applications on the UE 400.
  • the application layer 410 also may be used to provide end-to-end services between applications executing in the UE 400 and one or more other devices, entities, or networks according to any number of suitable communication protocols.
  • the memory 414 may be any suitable type of memory that can store computer-readable, computer-executable software code containing instructions that, when executed by the application processor 412, causes the UE 400 to perform various functions or operations.
  • the memory 414 may store a number of UE applications 416, a high-level operating system (HLOS) 418, and data generated by one or more of the application processor 412, the applications 416, or the HLOS 418.
  • the HLOS 418 may be a set of software that manages hardware resources on the UE 400, provides common services for applications residing in the application layer 410, and performs various other high-level functions and operations for the UE 400.
  • the application processor 412 which may be a specially-configured processor designed to support applications running in a mobile operating system environment, can be implemented as a general purpose processor, a Digital Signal Processor (DSP) , an Application Specific Integrated Circuit (ASIC) , a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the application processor 412 and the memory 414 may implement the HLOS 418.
  • the modem 430 may include a plurality of radios 432 (1) –432 (N) that may be used to communicate with other devices, systems, networks, entities, and nodes any number of suitable communication protocols.
  • a first radio 432 (1) may be configured for cellular communications
  • a second radio 432 (2) may be configured for WLAN communications
  • a third radio 432 (3) may be configured for Bluetooth communications.
  • the MCI 420 may be distributed between the radios 432 (1) –432 (N) and the application layer 410, and may manage connection points between one or more of the radios 432 (1) –432 (N) and the HLOS 418.
  • the application layer 410 may include a number of application program interfaces (API) and corresponding drivers that can establish connection points between applications residing in the memory 414 and one or more of the radios 432 (1) –432 (N) .
  • API application program interfaces
  • a first driver may be a Mobile Broadband driver and a first API may be a Mobile Broadband API set
  • a second driver may be a WLAN driver and a second API may be a WLAN API set
  • a third driver may be a Bluetooth driver and a third API may be a Bluetooth API set.
  • the connection points may be established via a radio interface layer (RIL) , which is a layer in the HLOS 418 that provides an interface to radio resources of the modem 430.
  • RIL radio interface layer
  • FIG. 5 shows a diagram of an example wireless communications system 500.
  • the wireless communications system 500 which may be one implementation of the wireless communications system 100 of Figure 1, includes a radio access network (RAN) 510, a core network 520, and a local area data network (LADN) 530.
  • the RAN 510 may include a plurality of base stations 502 (1) –502 (3) that can wirelessly communicate with a number of wireless communication devices (such as a UE 504) , and may provide access points for the wireless communication devices to connect to the core network 520 and the LADN 530.
  • the base stations 502 (1) –502 (3) may be one example of the base station 102 of Figure 1 or the base station 310 of Figure 3, and the UE 504 may be one example of the UE 104 of Figure 1, the UE 350 of Figure 3, or the UE 400 of Figure 4. Although only three base stations 502 (1) –502 (3) are shown in Figure 5 for simplicity, the RAN 510 may include any suitable number of base stations.
  • the radio access network may be any suitable RAN including, for example, a 5G NR access network.
  • Each of the base stations 502 (1) –502 (3) may provide communication coverage for a respective geographic area or cell.
  • the first base station 502 (1) may provide communication coverage for a first geographic area 512 (1)
  • the second base station 502 (2) may provide communication coverage for a second geographic area 512 (2)
  • the third base station 502 (3) may provide communication coverage for a third geographic area 512 (3) .
  • the first geographic area 512 (1) may be referred to as cell–1, and may correspond to a first tracking area (TA) identified by a first tracking area identity (TAI–1)
  • the second geographic area 512 (2) may be referred to as cell–2, and also may correspond to the first tracking area TAI–1.
  • the third geographic area 512 (3) may be referred to as cell–3, and may correspond to a second TA identified by TAI–2.
  • the first tracking area TAI–1 may include cell–1 and cell–2, and the second tracking area TAI–2 may include cell–3.
  • the core network 520 may include an Access and Mobility Management Function (AMF) 521, a Session Management Function (SMF) 522, a User Plane Function (UPF) 523, an Authentication Server Function (AUSF) 524, and a Unified Data Management (UDM) 525.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • the core network 520 also may include a Policy Control Function (PCF) , an Application Function (AF) , and other components, devices, and functions in accordance with one or more releases of the 3GPP Technical Specifications.
  • PCF Policy Control Function
  • AF Application Function
  • the core network 520 may be a 5G Core Network (5G CN) in communication with an EPC (not shown for simplicity) .
  • the AMF 521 is connected to the SMF 522 at reference point N11, is connected to the AUSF 524 at reference point N12, and is connected to the UDM at reference point N8.
  • the AMF 521 may support mobility functions for the UE 504 such as, for example, terrestrial cell change and handovers.
  • the AMF 521 also may provide a signaling connection to the UE 504 via the N1 interface, and provide a signaling connection to each of the base stations 502 (1) –502 (3) via the N2 interfaces (only one N2 interface shown for simplicity) .
  • the AMF 521 may configure the service area of the LADN 530, and may manage Protocol Data Unit (PDU) sessions between the UE 504 and the LADN 530 on behalf of the SMF 522.
  • PDU Protocol Data Unit
  • the SMF 522 is connected to the UPF 523 at reference point N4, and provides a connection between the AMF 521 and the UPF 523.
  • the SMF 522 is responsible for managing the establishment, modification, and release of PDU sessions for the UE 504.
  • the SMF 522 may perform IP address allocation and management for UE 504, and may act as a Dynamic Host Configuration Protocol (DHCP) server for the UE 504.
  • DHCP Dynamic Host Configuration Protocol
  • the SMF 522 also may select and control the UPF 523 on behalf of the UE 504.
  • the UPF 523 is connected to the LADN 530 at reference point N6, and may provide a signaling connection to each of the base stations 502 (1) –502 (3) via the N3 interfaces (only one N3 interface shown for simplicity) .
  • the UPF 523 is responsible for packet routing, packet forwarding, downlink packet buffering, and downlink data notifications triggering.
  • the UPF 523 may support voice and data bearers for the UE 504, and may enable the UE 504 to access other networks such as the LADN 530.
  • the UPF 523 may provide an interconnect point for PDU sessions between the UE 504 and the LADN 530, may enforce policy rules for the user plane, and may provide Quality of Service (QoS) for the user plane.
  • QoS Quality of Service
  • the core network 520 also may include a location management function (LMF) and a Gateway Mobile Location Center (GMLC) .
  • the LMF may determine positioning information of the UE 504 using various positioning techniques such as Assisted GNSS (A-GNSS) , Observed Time Difference of Arrival (OTDOA) , Precise Point Positioning (PPP) , Enhanced Cell ID (ECID) , Round Trip Time (RTT) , and other positioning procedures.
  • A-GNSS Assisted GNSS
  • OTDOA Observed Time Difference of Arrival
  • PPP Precise Point Positioning
  • ECID Enhanced Cell ID
  • RTT Round Trip Time
  • the LMF may process location services requests received from an external client 540, and the GMLC may support positioning functions for the external client 540.
  • the LADN 530 may be a data network that provides one or more services (such as operator services, Internet access, and 3rd party services) to UEs that establish a connection with the LADN 530 through the core network 520.
  • the data network may be identified by a data network name (DNN) or an access point name (APN) , and may be available within a specified service area.
  • the service area of the data network may correspond to a single cell, a group of cells, or an entire registration area.
  • the service area of the data network may correspond to one or more tracking areas.
  • the tracking areas of data networks associated with the LADN 530 may collectively define a service area of the LADN 530, and the TAIs of the tracking areas may be grouped together in a TAI list indicative of the service area of the LADN 530.
  • the AMF 521 may allocate a registration area that includes one or more tracking areas associated with the RAN 510, and may identify the LADNs which are available within the UE’s registration area.
  • the AMF 521 may indicate the available LADNs to the UE 504 by sending data network information to the UE using NAS signaling.
  • the data network information may include DNNs, TAI lists, cell IDs, and PLMN IDs associated with the available data networks.
  • the UE may use the data network information received from the AMF 521 to establish a PDU session with the LADN 530.
  • the UE application may send a LADN setup request message to the UE’s modem.
  • the UE may generate a PDU Session ID, determine the DNN associated with the requested LADN service, and transmit a PDU Session Establishment Request message that requests the core network 520 to establish a PDU session between the UE and the LADN service.
  • the PDU Session Establishment Request message may include the DNN of the requested LADN service, the PDU Session ID, a PDU session type, Single Network Slice Selection Assistance Information (S-NSSAI) , and a Service and Session Continuity (SSC) mode.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • SSC Service and Session Continuity
  • the AMF 521 receives the PDU Session Establishment Request message from the UE, and may forward some or all of the PDU Session Establishment Request message to the SMF 522.
  • the SMF 522 may determine whether the PDU Session Establishment Request is compliant with the user’s subscriptions and local policies, and also may determine whether the UE is located within the LADN service area based on user location information provided by the AMF 521. If the user location information does not indicate that the UE is located within the LADN service area, the SMF 522 may reject the PDU Session Establishment Request (such as because the UE is outside of the LADN service area) , and the AMF 521 may send a PDU Session Establishment failure indication to the UE.
  • the UE application may repeatedly send LADN setup request messages to the UE’s modem, which prompts the UE to repeatedly transmit PDU Session Establishment Request messages to the core network 520.
  • the core network 520 may continue sending failure indications to the UE. Repeatedly requesting and failing to establish a PDU session with the LADN service not only consumes power of the UE, but also consumes signaling overhead of the RAN 510.
  • a UE application seeking access to a LADN service may register with the LADN service and obtain the TAI of a DNN associated with the LADN service.
  • the TAI of the DNN may be stored in the UE, and may be used to determine when the LADN service is available to the UE.
  • the UE may compare one or more TAIs received in broadcast messages from a serving cell with the TAI of the DNN to determine whether the UE is located within the LADN service area.
  • the UE may determine that the LADN service is available, and thereafter request and establish a PDU Session with the DNN of the LADN service.
  • Figure 6 shows a sequence diagram depicting an example message exchange 600 between a UE 610 and a core network 620.
  • the core network 620 may be associated with a radio access network (RAN) that includes a plurality of base stations such as base station 630.
  • the UE 610 may be one example of the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, or the UE 504 of Figure 5.
  • the base station 630 may be one example of the base station 102 of Figure 1, the base station 310 of Figure 3, or the base stations 502 (1) –502 (3) of Figure 5.
  • the base station 630 may be any suitable base station or node including, for example, a gNB or an eNB.
  • the RAN may be any suitable radio access network, and may include any suitable radio access technology.
  • the RAN may be one example of the RAN 510 of Figure 5.
  • the core network 620 may be any suitable core network including, for example, a 5G Core Network (5G CN) in communication with an EPC (not shown for simplicity) .
  • the core network 620 may be one example of the core network 520 of Figure 5.
  • the UE 610 is shown to include a HLOS 612, a modem 614, and an MCI (other components of the UE 610 are not shown for simplicity) .
  • the HLOS 612 may reside in an application processor of the UE 610, and is coupled to the modem 614 via the MCI.
  • the HLOS 612 may be one example of the HLOS 418 of Figure 4
  • the modem 630 may be one example of the modem 430 of Figure 4
  • the MCI may be one example of the MCI 420 of Figure 4.
  • An application executed by the HLOS 612 may select or otherwise identify a LADN service with which to establish a connection through the core network 620, and the UE 610 may register the application with the identified LADN service before attempting to establish a PDU session with the identified LADN service.
  • the application sends a LADN Registration Request to the modem 614 via the MCI.
  • the LADN Registration Request may include at least a data network name (DNN) of the LADN service, and may prompt the modem 614 to initiate a registration procedure with the LADN service.
  • DNN data network name
  • the modem 614 receives the LADN Registration Request, and transmits a registration request (REG REQ) message to the core network 620.
  • the REG REQ message may include a request to register the application with the LADN service, and may indicate the DNN of the LADN service.
  • the core network 620 accepts the registration request, registers the application with the identified LADN service, and sends a Registration Accept (REG ACCEPT) message to the UE 610.
  • the REG ACCEPT message indicates that the application has been registered with the identified LADN service, and may include the DNN of the LADN service and a TAI associated with the DNN.
  • the modem 614 receives the REG ACCEPT message, and may store the TAI of the DNN in a suitable memory within the UE 610.
  • the modem 614 receives, from the base station 630, a System Information Block (SIB) containing a TAI list that includes one or more TAIs.
  • SIB System Information Block
  • the base station 630 may periodically or aperiodically broadcast SIBs containing TAIs or a TAI list.
  • Each of the TAIs contained in the SIB may identify a corresponding tracking area, and the tracking areas identified by the TAIs contained in the SIB may collectively indicate the service area of the base station 630.
  • the first base station 502 (1) may broadcast a SIB containing TAI–1 to indicate that the tracking area identified by TAI–1 includes or corresponds to Cell–1
  • the second base station 502 (2) may broadcast a SIB containing TAI–1 to indicate that the tracking area identified by TAI–1 includes or corresponds to Cell–2
  • the third base station 502 (3) may broadcast a SIB containing TAI–2 to indicate that the tracking area identified by TAI–2 includes or corresponds to Cell–3.
  • the UE 610 may compare the TAIs contained in the SIB with the TAI of the DNN to determine whether the UE 610 is located within the LADN service area.
  • a match between the TAI of the DNN and one of the TAIs contained in the broadcast TAI list may indicate that the UE 610 is within the tracking area identified by the matching TAIs, and therefore also may indicate that the UE 610 is within the service area of the LADN.
  • a mismatch between the TAI of the DNN and the TAIs contained in the broadcast TAI list may indicate that the UE 610 is not located within the tracking area identified by the matching TAIs, and therefore also may indicate that the UE 610 is not located within the service area of the LADN.
  • the TAI of the DNN matches one of the TAIs contained in SIB received from the base station 630, and the UE 610 determines that it is located within the service area of the identified LADN.
  • the modem 614 sends a LADN indication message to the application via the HLOS 612 based on the determination that the UE 610 is located within the service area of the identified LADN.
  • the LADN indication message may indicate that the UE application is registered with the identified LADN service, and may include the DNN of the identified LADN service and the TAI associated with the DNN of the LADN service.
  • the modem 614 may determine when the UE 610 is within a vicinity of the service area of the identified LADN based on the TAIs contained in the SIB, and may indicate the proximity of the DNN of the identified LADN service to the HLOS 612.
  • the application may send a setup request (Setup REQ) message to the modem 614 via the HLOS 612 based on the indication that the UE application is registered with the identified LADN service.
  • the Setup REQ message may include a request to setup a PDU session with the LADN service, and may contain the DNN of the LADN service.
  • the modem 614 sends a PDU Session Establishment Request message to the core network 620.
  • the PDU Session Establishment Request message may include the DNN of the identified LADN service and a request to establish a PDU session between the UE 610 and the identified LADN service.
  • the core network 620 receives the PDU Session Establishment Request message, and may accept or deny the requested PDU Session based on a number of factors (such as whether the PDU Session Establishment Request is compliant with the user’s subscriptions and local policies, and whether the UE 610 is located within the service area of the identified LADN) .
  • the core network 620 determines that the UE 610 is located within the service area of the identified LADN, and accepts the PDU Session Establishment Request.
  • the core network 620 may indicate acceptance of the PDU session request by sending a PDU Session Establishment Accept message to the UE 610.
  • the PDU Session Establishment Accept message may include the DNN of the identified LADN service and the TAI of the DNN.
  • the modem 614 receives the PDU Session Establishment Accept message, and sends a setup response (Setup RSP) message indicating “success” to the application via the HLOS 612.
  • setup response Setup RSP
  • the application may access the DNN of the identified LADN service using the established PDU session.
  • the UE application may register with a LADN service and request setup of a PDU session with the LADN service, concurrently.
  • Figure 7 shows a sequence diagram depicting another example message exchange 700 for establishing a PDU session between a UE and a LADN service.
  • the core network 720 may be associated with a radio access network (RAN) that includes a plurality of base stations such as base station 730.
  • the UE 710 may be one example of the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, or the UE 504 of Figure 5.
  • the base station 730 may be one example of the base station 102 of Figure 1, the base station 310 of Figure 3, or the base stations 502 (1) –502 (3) of Figure 5.
  • the base station 730 may be any suitable base station or node including, for example, a gNB or an eNB.
  • the RAN may be any suitable radio access network, and may include any suitable radio access technology.
  • the RAN may be one example of the RAN 510 of Figure 5.
  • the core network 720 may be any suitable core network including, for example, a 5G Core Network (5G CN) in communication with an EPC (not shown for simplicity) .
  • the core network 720 may be one example of the core network 520 of Figure 5.
  • the UE 710 is shown to include a HLOS 712, a modem 714, and an MCI (other components of the UE 710 are not shown for simplicity) .
  • the HLOS 712 may reside in an application processor of the UE 710, and is coupled to the modem 714 via the MCI.
  • the HLOS 712 may be one example of the HLOS 418 of Figure 4
  • the modem 730 may be one example of the modem 430 of Figure 4
  • the MCI may be one example of the MCI 420 of Figure 4.
  • An application executed by the HLOS 712 may select or otherwise identify a LADN service with which to establish a connection through the core network 720, and the UE 710 may register the application with the identified LADN service and request setup of a PDU session with the identified LADN service, concurrently.
  • the application sends a LADN Request and Setup message to the modem 714 via the HLOS 712.
  • the LADN Request and Setup message may include a request to register the application with the identified LADN service, a request to setup the PDU session with the identified LADN service when available to the UE 710, and the DNN of the identified LADN service.
  • the modem 714 receives the LADN Request and Setup message, and transmits a registration and setup request (REG &SETUP REQ) message to the core network 720.
  • the REG &SETUP REQ message may include a DNN of the identified LADN service, a request to register the application with the identified LADN service, and a request to setup a PDU session with the DNN of the identified LADN service when available to the UE 710.
  • the core network 720 accepts the registration and setup request, registers the application with the identified LADN service, and sends a Registration Accept (REG ACCEPT) message to the UE 710.
  • the REG ACCEPT message may include the DNN of the LADN service, a TAI associated with the DNN, and an indication that the UE 710 is registered with the identified LADN service.
  • the modem 714 receives the REG ACCEPT message, and may store the TAI of the DNN in a suitable memory within the UE 710.
  • the modem 714 receives, from the base station 730, a SIB containing a TAI list that includes one or more TAIs.
  • the base station 730 may periodically or aperiodically broadcast SIBs containing TAIs or a TAI list, where each of the TAIs contained in the SIB may identify a corresponding tracking area.
  • the tracking areas identified by the TAIs contained in the SIB may collectively indicate the service area of the base station 730.
  • the UE 710 may compare the TAIs contained in the SIB with the TAI of the DNN to determine whether the UE 710 is located within the LADN service area. As described with reference to Figure 6, a match between the TAI of the DNN and one of the TAIs contained in the broadcast TAI list may indicate that the UE 710 is within the service area of the DNN of the identified LADN, and a mismatch between the TAI of the DNN and the TAIs contained in the broadcast TAI list may indicate that the UE 710 is not located within the service area of the DNN of the identified LADN.
  • the TAI of the DNN matches one of the TAIs contained in SIB received from the base station 730, and the UE 710 determines that it is located within the service area of the identified LADN.
  • the modem 714 Based on the determination that the UE 610 is located within the service area of the identified LADN, the modem 714 sends a PDU Session Establishment Request message to the core network 720.
  • the PDU Session Establishment Request message may include the DNN of the identified LADN service and a request to establish a PDU session between the UE 710 and the identified LADN service.
  • the core network 720 receives the PDU Session Establishment Request message, and determines that the UE 710 is located within the service area of the identified LADN.
  • the core network 720 accepts the PDU Session Establishment Request, and indicates acceptance of the PDU session request by sending a PDU Session Establishment Accept message to the UE 710.
  • the PDU Session Establishment Accept message may include the DNN of the identified LADN service, the TAI of the DNN, and an indication that the UE 710 is registered with the identified LADN service.
  • the modem 714 receives the PDU Session Establishment Accept message, and sends a setup response (Setup RSP) message indicating “success” to the application via the HLOS 712.
  • setup response Setup RSP
  • the application may access the DNN of the identified LADN service using the established PDU session.
  • FIG 8 shows a flowchart depicting an example operation 800 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 800 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 800 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 800 may be performed by another suitable wireless communication device.
  • HLOS high-level operating system
  • the application sends a local area data network (LADN) Registration Request to the modem via the HLOS, the LADN Registration Request including at least a data network name (DNN) of the LADN service.
  • LADN local area data network
  • the UE transmits, to a core network associated with a radio access network (RAN) , a registration request message including a request to register the application with the LADN service and indicating the DNN of the LADN service.
  • RAN radio access network
  • the UE receives, from the core network, a registration accept message including the DNN of the LADN service and a tracking area identity (TAI) associated with the DNN.
  • TAI tracking area identity
  • the modem sends a LADN indication message to the application via the HLOS, the LADN indication message including the DNN of the LADN service, the TAI associated with the DNN, and an indication that the UE application is registered with the LADN service.
  • the UE receives, from a base station (BS) , a broadcasted TAI list containing a number of TAIs indicative of a coverage area of the BS.
  • the UE determines whether the UE is within a service area of the LADN based at least in part on a comparison between the TAI associated with the DNN and the number of TAIs in the broadcasted TAI list.
  • the UE establishes a protocol data unit (PDU) session with the DNN of the LADN service based on the determination.
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCH physical downlink control channel
  • the UE may be determined to be within the LADN service area when the TAI associated with the DNN matches one TAI of the number of TAIs in the broadcasted TAI list, and the UE may be determined to be outside the LADN service area when the TAI associated with the DNN does not match any TAI of the number of TAIs in the broadcasted TAI list.
  • the LADN service area may be determined to be available to the UE based on identity information included in the broadcasted SIB.
  • the identity information may include at least one of a TAI or a cell identifier (ID) .
  • the TAI may be received from the base station on a physical downlink control channel (PDCCH) .
  • PDCCH physical downlink control channel
  • Figure 9A shows a flowchart depicting an example operation 900 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 900 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 900 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 900 may be one example of establishing the PDU session in block 812 of the operation 800 of Figure 8.
  • the UE transmits, to the core network, a PDU Session Establishment request including at least the DNN of the LADN service.
  • the UE receives, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • Figure 9B shows a flowchart depicting an example operation 910 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 910 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 910 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 910 may be performed after the modem sends the LADN indication in block 808 of the operation 800 of Figure 8.
  • the application sends a setup request to the modem via the HLOS, the setup request including the DNN of the LADN service and a request to setup the PDU session with the DNN of the LADN service.
  • the modem sends a setup response to the application via the HLOS, the setup response indicating successful establishment of the PDU session with the DNN of the LADN service.
  • FIG 10 shows a flowchart depicting an example operation 1000 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1000 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1000 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 1000 may be performed by another suitable wireless communication device.
  • HLOS high-level operating system
  • the application sends a Request and Setup message to the modem via the HLOS, the Request and Setup message including a request to register the application with a local area data network (LADN) service, a request to setup a protocol data unit (PDU) session with the LADN service when available to the UE, and a data network name (DNN) of the LADN service.
  • the UE transmits a message to the core network, the message including a request to register the application with the LADN service, a request to setup the PDU session with the DNN of the LADN service when available to the UE, and the DNN of the LADN service.
  • the UE receives, from the core network, an accept message including the DNN of the LADN service, a tracking area identity (TAI) associated with the DNN, and an indication that the UE is registered with the LADN service.
  • the UE determines that the LADN service is available to the UE.
  • the UE establishes a PDU session with the DNN of the LADN service based on the determination that the LADN service is available to the UE and the request to setup the PDU session.
  • TAI tracking area identity
  • FIG 11A shows a flowchart depicting an example operation 1100 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1100 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1100 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 1100 may be performed after establishing the PDU session in block 1010 of the operation 1000 of Figure 10.
  • the modem sends a setup response message to the application via the HLOS, the setup response message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • FIG 11B shows a flowchart depicting an example operation 1110 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1110 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1110 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 1110 may be performed before determining that the LADN service is available in block 1008 of the operation 1000 of Figure 10.
  • the UE receives a system information block (SIB) broadcast from a base station (BS) .
  • SIB system information block
  • the LADN service area may be determined to be available to the UE based on identity information included in the broadcasted SIB.
  • the identity information may include at least one of a TAI or a cell identifier (ID) .
  • the TAI may be received from the base station on a physical downlink control channel (PDCCH) .
  • PDCH physical downlink control channel
  • Figure 11C shows a flowchart depicting an example operation 1120 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1120 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1120 may be one example of establishing the PDU session in block 1010 of the operation 1000 of Figure 10.
  • the UE transmits, to the core network, a PDU Session Establishment request including at least the DNN of the LADN service.
  • the UE receives, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • FIG 12 shows a flowchart depicting an example operation 1200 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1200 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the UE transmits a registration request message including a request to register the application with a local area data network (LADN) service and indicating at least a data network name (DNN) of the LADN service.
  • the UE receives a registration accept message including the DNN of the LADN service and a tracking area identity (TAI) associated with the DNN.
  • LADN local area data network
  • TAI tracking area identity
  • the UE receives, from a base station (BS) , a broadcasted TAI list containing a number of TAIs indicative of a coverage area of the BS.
  • the UE determines whether the UE is within a service area of the LADN based at least in part on a comparison between the TAI associated with the DNN and the number of TAIs in the broadcasted TAI list.
  • the UE establishes a protocol data unit (PDU) session with the DNN of the LADN service based on the determination indicating that the UE is within a service area of the LADN.
  • the broadcasted TAI list may be included in a system information block (SIB) received from the BS on a physical downlink control channel (PDCCH) .
  • SIB system information block
  • PDCH physical downlink control channel
  • the UE may be determined to be within the LADN service area when the TAI associated with the DNN matches one TAI of the number of TAIs in the broadcasted TAI list, and the UE may be determined to be outside the LADN service area when the TAI associated with the DNN does not match any TAI of the number of TAIs in the broadcasted TAI list.
  • the LADN service area may be determined to be available to the UE based on identity information included in the broadcasted SIB.
  • the identity information may include at least one of a TAI or a cell identifier (ID) .
  • the TAI may be received from the base station on a physical downlink control channel (PDCCH) .
  • PDCCH physical downlink control channel
  • FIG 13A shows a flowchart a depicting an example operation 1300 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1300 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 1300 may be performed after determining whether the UE is within the service area of the LADN in block 1208 of the operation 1200 of Figure 12.
  • the UE refrains from requesting or establishing the PDU session with the DNN of the LADN service based on the determination indicating that the UE is not within the service area of the LADN.
  • Figure 13B shows a flowchart a depicting an example operation 1310 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1310 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 1310 may be one example of establishing the PDU session in block 1210 of the operation 1200 of Figure 12.
  • the UE transmits, to a core network, a PDU Session Establishment request including at least the DNN of the LADN service.
  • the UE receives, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • Figure 13C shows a flowchart a depicting an example operation 1320 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1320 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 1320 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a HLOS 418 configured to execute an application 416 on the UE 400.
  • the operation 1320 may be performed after determining whether the UE is within the service area of the LADN in block 1208 of the operation 1200 of Figure 12.
  • the application sends a LADN Registration Request to the modem via the HLOS, the LADN Registration Request including at least the DNN of the LADN service.
  • the modem sends a LADN indication message to the application via the HLOS, the LADN indication message including the DNN of the LADN service, the TAI associated with the DNN, and an indication that the UE application is registered with the LADN service.
  • Figure 13D shows a flowchart a depicting an example operation 1330 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1330 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 610 of Figure 6.
  • the operation 1330 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a HLOS 418 configured to execute an application 416 on the UE 400.
  • the operation 1330 may be performed after the modem sends the LADN indication message in block 1324 of the operation 1320 of Figure 13C.
  • the application sends a setup request to the modem via the HLOS, the setup request including the DNN of the LADN service and a request to setup the PDU session with the DNN of the LADN service.
  • the modem sends a setup response to the application via the HLOS, the setup response indicating successful establishment of the PDU session with the DNN of the LADN service.
  • Figure 14 shows a flowchart depicting an example operation 1400 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1400 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the UE transmits a message including a request to register the application with the LADN service, a request to setup the PDU session with the DNN of the LADN service when available to the UE, and the DNN of the LADN service.
  • the UE receives an accept message including the DNN of the LADN service, a tracking area identity (TAI) associated with the DNN, and an indication that the UE is registered with the LADN service.
  • the UE determines that the LADN service is available to the UE.
  • the UE establishes the PDU session with the DNN of the LADN service based on the determination that the LADN service is available to the UE and the request to setup the PDU session.
  • TAI tracking area identity
  • FIG 15A shows a flowchart depicting an example operation 1500 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1500 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1500 may be performed before determining that the LADN service is available in block 1406 of the operation 1400 of Figure 14.
  • the UE receives a system information block (SIB) broadcast from a base station (BS) .
  • SIB system information block
  • the LADN service area may be determined to be available to the UE based on identity information included in the broadcasted SIB.
  • the identity information may include at least one of a TAI or a cell identifier (ID) .
  • the TAI may be received from the base station on a physical downlink control channel (PDCCH) .
  • PDCH physical downlink control channel
  • Figure 15B shows a flowchart depicting an example operation 1510 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1510 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1510 may be one example of establishing the PDU session in block 1408 of the operation 1400 of Figure 14.
  • the UE transmits, to a core network, a PDU Session Establishment request including at least the DNN of the LADN service.
  • the UE receives, from the core network, a PDU Session Establishment accept message indicating successful establishment of the PDU session with the DNN of the LADN service.
  • Figure 15C shows a flowchart depicting an example operation 1520 for wireless communication that supports establishing a PDU session between a UE and a LADN service.
  • the operation 1520 may be performed by a wireless communication device such as the UE 104 of Figure 1, the UE 350 of Figure 3, the UE 400 of Figure 4, the UE 504 of Figure 5, or the UE 710 of Figure 7.
  • the operation 1520 is described with reference to the UE 400 of Figure 4, which includes at least a modem 430 and a high-level operating system (HLOS) 418 configured to execute an application 416 on the UE 400.
  • the operation 1520 may be performed by another suitable wireless communication device.
  • HLOS high-level operating system
  • the application sends a Request and Setup message to the modem via the HLOS, the Request and Setup message including the request to register the application, the request to setup the PDU session, and the DNN of the LADN service.
  • the modem sends a setup response message to the application via the HLOS, the setup response message indicating successful establishment of the PDU session with the LADN service.
  • 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.
  • the hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single-or multi-chip processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
  • a general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine.
  • a processor also may be implemented as a combination of computing devices (such as 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.
  • particular processes and methods may be performed by circuitry that is specific to a given function.
  • the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents thereof, or in any combination thereof. Implementations of the subject matter described in this specification also can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage media for execution by, or to control the operation of, data processing apparatus.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program from one place to another.
  • a storage media may be any available media that may be accessed by a computer.
  • such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer.
  • Disk and disc includes compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine readable medium and computer-readable medium, which may be incorporated into a computer program product.

Landscapes

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

Abstract

La présente invention concerne des systèmes, des procédés et un appareil, notamment des programmes informatiques codés sur des supports d'enregistrement informatiques, pour un équipement utilisateur (UE) pour établir une session d'unité de données de protocole (PDU) avec un service de réseau de données local (LADN). Dans certains modes de réalisation, l'UE peut s'enregistrer auprès du service LADN et obtenir une identité de zone de suivi (TAI) associée à un nom de réseau de données (DNN) du service LADN. La TAI du DNN peut être stockée dans l'UE et peut être utilisée pour déterminer la disponibilité du service LADN pour l'UE. L'UE peut comparer une ou plusieurs TAI reçues dans des messages de diffusion provenant d'une cellule de desserte à la TAI du DNN pour déterminer si l'UE se situe dans la zone de service LADN. Lorsqu'il est déterminé que l'UE est dans la zone de service LADN, l'UE demande et établit une session PDU avec le DNN du service LADN.
PCT/CN2020/074470 2020-02-07 2020-02-07 Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn) Ceased WO2021155552A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/074470 WO2021155552A1 (fr) 2020-02-07 2020-02-07 Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/074470 WO2021155552A1 (fr) 2020-02-07 2020-02-07 Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn)

Publications (1)

Publication Number Publication Date
WO2021155552A1 true WO2021155552A1 (fr) 2021-08-12

Family

ID=77199738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/074470 Ceased WO2021155552A1 (fr) 2020-02-07 2020-02-07 Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn)

Country Status (1)

Country Link
WO (1) WO2021155552A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2610305A (en) * 2021-07-28 2023-03-01 Samsung Electronics Co Ltd Improvements in and relating to local area data network service information
EP4476964A1 (fr) 2022-05-04 2024-12-18 Samsung Electronics Co., Ltd Application de restriction de zone de service dans un réseau sans fil

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190007500A1 (en) * 2017-07-03 2019-01-03 Electronics And Telecommunications Research Institute Method for protocol data unit (pdu) session anchor relocation and 5g network registration
CN109246853A (zh) * 2017-06-08 2019-01-18 华为技术有限公司 一种会话处理方法、装置及系统
WO2019157864A1 (fr) * 2018-02-13 2019-08-22 华为技术有限公司 Procédé et appareil de détermination d'informations de localisation
CN110622572A (zh) * 2017-05-09 2019-12-27 夏普株式会社 用户装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110622572A (zh) * 2017-05-09 2019-12-27 夏普株式会社 用户装置
CN109246853A (zh) * 2017-06-08 2019-01-18 华为技术有限公司 一种会话处理方法、装置及系统
US20190007500A1 (en) * 2017-07-03 2019-01-03 Electronics And Telecommunications Research Institute Method for protocol data unit (pdu) session anchor relocation and 5g network registration
WO2019157864A1 (fr) * 2018-02-13 2019-08-22 华为技术有限公司 Procédé et appareil de détermination d'informations de localisation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP； TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: "System architecture for the 5G System (5GS)； Stage 2 (Release 15)", 3GPP TS 23.501 V15.8.0 (2019-12), 31 December 2019 (2019-12-31) *
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.501, vol. SA WG2, no. V15.8.0, 22 December 2019 (2019-12-22), pages 1 - 248, XP051840929 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2610305A (en) * 2021-07-28 2023-03-01 Samsung Electronics Co Ltd Improvements in and relating to local area data network service information
GB2610305B (en) * 2021-07-28 2025-04-09 Samsung Electronics Co Ltd Improvements in and relating to local area data network service information
EP4476964A1 (fr) 2022-05-04 2024-12-18 Samsung Electronics Co., Ltd Application de restriction de zone de service dans un réseau sans fil
EP4476964A4 (fr) * 2022-05-04 2025-05-21 Samsung Electronics Co., Ltd Application de restriction de zone de service dans un réseau sans fil

Similar Documents

Publication Publication Date Title
US11218921B2 (en) Centralized PCI management for IAB network
US20240373357A1 (en) Data transfer between an inactive mode user equipment and a wireless network
US11792704B2 (en) Avoiding simultaneous conditional handover and conditional primary SCG cell change
US11765737B2 (en) DCI triggered SRS enhancements
US11800347B2 (en) User equipment (UE) capability and assistance information exchange over sidelinks
CN112970295B (zh) 对ne-dc中的潜在nr ul传输的指示
US11470678B2 (en) Broadcast of multiple physical cell identity ranges
US12052611B2 (en) Evolved packet system (EPS) mobility configuration from wireless system
WO2019213889A1 (fr) Demande de changement de configuration de liaison montante
WO2021211421A1 (fr) Signalisation de gain de faisceau
WO2022006001A1 (fr) Configuration de ressources flexibles dans un symbole de duplex intégral
EP4186291A2 (fr) Transmission de radiomessagerie et de messages courts fiable avec répétition
WO2021055893A1 (fr) Signalisation de capacité d'ue concernant des états tci ou des relations spatiales pour un groupe de parties de largeurs de bande ou de porteuses composantes
US20200196336A1 (en) Gap transmission in channel occupancy time
US11611910B2 (en) Techniques for resource selection in a wireless communication system
WO2021155552A1 (fr) Interface de système d'exploitation de haut niveau (hlos) pour un service de réseau de données local (ladn)
US12484039B2 (en) Soft A/N report triggering for SPS PDSCH
US11729632B2 (en) Beam refinement reference signal before paging DCI reception
US20220039139A1 (en) Beam specific rmsi transmission
WO2021223233A1 (fr) Signalisation internœuds pour partage de puissance dynamique nr-dc
WO2022052028A1 (fr) Procédés et appareils d'améliorations de fiabilité de réseaux de communication machine massive (mmtc)
WO2022000475A1 (fr) Mise à jour de configuration de liaison montante supplémentaire pour un ensemble de cellules de desserte
WO2021184237A1 (fr) Sélection de station de base dynamique

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: 20917967

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: 20917967

Country of ref document: EP

Kind code of ref document: A1