[go: up one dir, main page]

WO2025194379A1 - Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes - Google Patents

Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes

Info

Publication number
WO2025194379A1
WO2025194379A1 PCT/CN2024/082677 CN2024082677W WO2025194379A1 WO 2025194379 A1 WO2025194379 A1 WO 2025194379A1 CN 2024082677 W CN2024082677 W CN 2024082677W WO 2025194379 A1 WO2025194379 A1 WO 2025194379A1
Authority
WO
WIPO (PCT)
Prior art keywords
nes
cell
supporting
gnb
barred
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/082677
Other languages
English (en)
Inventor
Haijing Hu
Naveen Kumar R Palle VENKATA
Alexander Sirotkin
Peng Cheng
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.)
Apple Inc
Original Assignee
Apple 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 Apple Inc filed Critical Apple Inc
Priority to PCT/CN2024/082677 priority Critical patent/WO2025194379A1/fr
Publication of WO2025194379A1 publication Critical patent/WO2025194379A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for enabling an IP Multimedia Subsystem (IMS) emergency call in a network energy saving (NES) -supporting cell from a non-NES-supporting user equipment (UE) .
  • IMS IP Multimedia Subsystem
  • NES network energy saving
  • UE user equipment
  • Wireless communication systems are rapidly growing in usage.
  • wireless devices such as smart phones and tablet computers have become increasingly sophisticated.
  • many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS) and are capable of operating sophisticated applications that utilize these functionalities.
  • GPS global positioning system
  • LTE Long Term Evolution
  • 5G NR Fifth Generation New Radio
  • 5G-NR also simply referred to as NR
  • NR provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption.
  • NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.
  • Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for an apparatus of a user equipment (UE) comprising one or more processors coupled to a memory.
  • the processors are configured to decode, at the UE, signaling with a Master Information Block (MIB) received from a base station associated with a network energy saving (NES) -supporting cell.
  • MIB Master Information Block
  • NES network energy saving
  • the processors are configured to identify, from the MIB, a cell barred status set to barred.
  • the processors are configured to decode, at the UE, signaling with a System Information Block Type 1 (SIB1) received from the base station associated with the NES-supporting cell.
  • SIB1 System Information Block Type 1
  • the processors are configured to identify, from the SIB1, a cell barred NES status set to not barred.
  • the processors are configured to determine, at the UE, that the NES-supporting cell is acceptable for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • NES network energy saving
  • UE user equipment
  • the method comprises decoding, at the UE, signaling with a Master Information Block (MIB) received from the base station associated with the NES-supporting cell.
  • MIB Master Information Block
  • the method comprises identifying, from the MIB, a cell barred status set to barred.
  • the method comprises decoding, at the UE, signaling with a System Information Block Type 1 (SIB1) received from the base station associated with the NES-supporting cell.
  • SIB1 System Information Block Type 1
  • the method comprises identifying, from the SIB1, a cell barred NES status set to not barred.
  • the method comprises determining, at the non-NES-supporting UE, that the NES-supporting cell is acceptable for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • IMS IP Multimedia Subsystem
  • the apparatus comprises one or more processors coupled to a memory.
  • the processors are configured to encode, at the gNB, signaling with a Master Information Block (MIB) for transmission to a non-network-energy-saving (non-NES) -supporting user equipment (UE) .
  • the processors are configured to indicate, in the MIB, a cell barred status set to barre.
  • the processors are configured to encode, at the gNB, signaling with a System Information Block Type 1 (SIB1) for transmission to the non-NES-supporting UE.
  • SIB1 System Information Block Type 1
  • the processors are configured to indicate, in the SIB1, a cell barred NES status set to not barred.
  • the processors are configured to decode, at the gNB, signaling from the non-NES-supporting UE with a connection request (CR) for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell.
  • CR connection request
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • NES non-network-energy-saving
  • UE user equipment
  • gNB next generation Node B
  • the method comprises encoding, at the gNB, signaling with a Master Information Block (MIB) for transmission to the non-NES-supporting UE.
  • MIB Master Information Block
  • the method comprises indicating, in the MIB, a cell barred status set to barred.
  • the method comprises encoding, at the gNB, signaling with a System Information Block Type 1 (SIB1) for transmission to the non-NES-supporting UE.
  • SIB1 System Information Block Type 1
  • the method comprises indicating, in the SIB1, a cell barred NES status set to not barred.
  • the method comprises decoding, at the gNB, signaling from the non-NES-supporting UE with a connection request (CR) for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell.
  • CR connection request
  • IMS IP Multimedia Subsystem
  • UAVs unmanned aerial vehicles
  • UACs unmanned aerial controllers
  • base stations access points
  • cellular phones tablet computers
  • wearable computing devices portable media players, and any of various other computing devices.
  • FIG. 1A illustrates an example wireless communication system according to some embodiments.
  • FIG. 1B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.
  • UE user equipment
  • FIG. 2 illustrates an example block diagram of a base station, according to some embodiments.
  • FIG. 3 illustrates an example block diagram of a server according to some embodiments.
  • FIG. 4 illustrates an example block diagram of a UE according to some embodiments.
  • FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.
  • FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.
  • FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.
  • FIG. 8 illustrates example components of a core network according to some embodiments.
  • FIG. 9 illustrates an example of signaling during cell selection, according to some embodiments.
  • FIG. 10 illustrates a flow chart of an example of a method for enabling an emergency call in NES, according to some embodiments.
  • FIG. 11 illustrates a flow chart of an example of a method for enabling an emergency call in NES, according to some embodiments.
  • FIG. 12 illustrates an example of signaling during cell selection, according to some embodiments.
  • FIG. 13 illustrates an example of ASN. 1 code used for the network to configure the SIB1, according to some embodiments.
  • FIG. 14 illustrates an example of signaling during cell selection, according to some embodiments.
  • FIG. 15 illustrates an example of signaling during cell selection, according to some embodiments.
  • FIG. 16 illustrates an example of signaling during handover, according to some embodiments.
  • FIG. 17 illustrates an example of signaling during handover, according to some embodiments.
  • FIG. 18 illustrates an example of signaling during handover, according to some embodiments.
  • Memory Medium Any of various types of non-transitory memory devices or storage devices.
  • the term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc.
  • the memory medium may include other types of non-transitory memory as well or combinations thereof.
  • the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution.
  • the term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network.
  • the memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.
  • Carrier Medium a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • a physical transmission medium such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays) , PLDs (Programmable Logic Devices) , FPOAs (Field Programmable Object Arrays) , and CPLDs (Complex PLDs) .
  • the programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores) .
  • a programmable hardware element may also be referred to as "reconfigurable logic” .
  • Computer System any of various types of computing or processing systems, including a personal computer system (PC) , mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA) , television system, grid computing system, or other device or combinations of devices.
  • PC personal computer system
  • mainframe computer system workstation
  • network appliance Internet appliance
  • PDA personal digital assistant
  • television system grid computing system, or other device or combinations of devices.
  • computer system can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
  • UE User Equipment
  • UE Device any of various types of computer systems devices which are mobile or portable and which performs wireless communications.
  • UE devices include mobile telephones or smart phones (e.g., iPhone TM , Android TM -based phones) , portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM , Gameboy Advance TM , iPhone TM ) , laptops, wearable devices (e.g., smart watch, smart glasses) , PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones) , UAV controllers (UACs) , and so forth.
  • UAVs unmanned aerial vehicles
  • UACs UAV controllers
  • Base Station has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.
  • Processing Element refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device.
  • Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit) , programmable hardware elements such as a field programmable gate array (FPGA) , as well any of various combinations of the above.
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • channel widths may be variable (e.g., depending on device capability, band conditions, etc. ) .
  • LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz.
  • 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1) and up to 400 MHz in FR2.
  • WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 MHz wide.
  • Other protocols and standards may include different definitions of channels.
  • some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different uses such as data, control information, etc.
  • band has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.
  • spectrum e.g., radio frequency spectrum
  • Automatically refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc. ) , without user input directly specifying or performing the action or operation.
  • a computer system e.g., software executed by the computer system
  • device e.g., circuitry, programmable hardware elements, ASICs, etc.
  • An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually” , where the user specifies each action to perform.
  • a user filling out an electronic form by selecting each field and providing input specifying information is filling out the form manually, even though the computer system will update the form in response to the user actions.
  • the form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields.
  • the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed) .
  • the present specification provides various examples of operations being automatically performed in response to actions the user has taken.
  • Concurrent refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner.
  • concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism” , where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.
  • 3GPP Legacy -The 3rd Generation Partnership Project
  • 3GPP specifications cover cellular telecommunications technologies, including radio access, core network and service capabilities, which provide a complete system description for mobile telecommunications.
  • 3GPP uses a system of parallel “Releases” that provide developers with a stable platform for the implementation of features at a given point and then allow for the addition of new functionality in subsequent releases. Release 17 was released in 2022. Release 18 (Rel-18) , at the time of this disclosure, is nearing release as its specifications have been largely defined. Accordingly, implementations and concepts compatible with Rel-18, or previous Releases, are sometimes referred to herein as “Legacy. ” One or more embodiments of the present disclosure may be adopted in future Releases, e.g., Release 19.
  • rN when used in conjunction with an Information Element (IE) refers to a UE that is capable of supporting 3GPP Release N.
  • IE Information Element
  • r18 denotes a UE capable of supporting 3GPP release 18.
  • a UE that is capable of supporting a release greater than N may also be capable of supporting 3GPP Release N.
  • a UE that is not capable of supporting 3GPP Release N may not be capable of supporting the IEs that include rN.
  • Various components may be described as “configured to” perform a task or tasks.
  • “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected) .
  • “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on.
  • the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.
  • the example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals.
  • the example embodiments relate to enabling an IP Multimedia Subsystem (IMS) emergency call with a non-network-energy-saving (NES) user equipment (UE) on an NES-supporting cell.
  • IMS IP Multimedia Subsystem
  • NES non-network-energy-saving
  • UE user equipment
  • the example embodiments are described with regard to communication between a base station, such as a next generation Node B (gNB) , associated with a NES-supporting cell and a non-NES-supporting UE.
  • a base station such as a next generation Node B (gNB)
  • gNB next generation Node B
  • reference to a gNB or a UE is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to support gapless RRM measurements. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronic component.
  • FIGS 1A and 1B Communication Systems
  • FIG. 1A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.
  • the example wireless communication system includes a base station 102A which communicates over a transmission medium with one or more user devices 106A, 106B, etc., through 106N.
  • Each of the user devices may be referred to herein as a “user equipment” (UE) .
  • UE user equipment
  • the user devices 106 are referred to as UEs or UE devices.
  • the base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station” ) and may include hardware that enables wireless communication with the UEs 106A through 106N.
  • BTS base transceiver station
  • cellular base station a “cellular base station”
  • the communication area (or coverage area) of the base station may be referred to as a “cell. ”
  • the base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs) , also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces) , LTE, LTE-Advanced (LTE-A) , 5G new radio (5G NR) , HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD) , etc.
  • RATs radio access technologies
  • GSM Global System for Mobile communications
  • UMTS associated with, for example, WCDMA or TD-SCDMA air interfaces
  • LTE LTE-Advanced
  • 5G NR 5G new radio
  • 3GPP2 CDMA2000 e.g., 1xRT
  • the base station 102A is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, it may alternately be referred to as an 'eNodeB' or ‘eNB’ .
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNB Evolved Universal Terrestrial Radio Access Network
  • the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’ .
  • the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN) , and/or the Internet, among various possibilities) .
  • a network 100 e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN) , and/or the Internet, among various possibilities
  • PSTN public switched telephone network
  • the base station 102A may facilitate communication between the user devices and/or between the user devices and the network 100.
  • the cellular base station 102A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and/or data services.
  • Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.
  • each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and/or any other base stations) , which may be referred to as “neighboring cells” .
  • Such cells may also be capable of facilitating communication between user devices and/or between user devices and the network 100.
  • Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells which provide any of various other granularities of service area size.
  • base stations 102A-B illustrated in FIG. 1A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.
  • base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB” .
  • a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • a gNB cell may include one or more transition and reception points (TRPs) .
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • a UE 106 may be capable of communicating using multiple wireless communication standards.
  • the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc. ) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces) , LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD) , etc. ) .
  • GSM Global System for Mobile communications
  • UMTS associated with, for example, WCDMA or TD-SCDMA air interfaces
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • 5G NR Fifth Generation
  • HSPA High Speed Packet Access
  • the UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS) , one or more mobile television broadcasting standards (e.g., ATSC-M/H or DVB-H) , and/or any other wireless communication protocol, if desired.
  • GNSS global navigational satellite systems
  • mobile television broadcasting standards e.g., ATSC-M/H or DVB-H
  • any other wireless communication protocol if desired.
  • Other combinations of wireless communication standards including more than two wireless communication standards are also possible.
  • FIG. 1B illustrates user equipment 106 (e.g., one of the devices 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments.
  • the UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.
  • non-cellular communication capability e.g., Bluetooth, Wi-Fi, and so forth
  • the UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.
  • a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.
  • the UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies.
  • the UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT /1xEV-DO /HRPD /eHRPD) , LTE/LTE-Advanced, or 5G NR using a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NR using the single shared radio.
  • the shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications.
  • a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc. ) , or digital processing circuitry (e.g., for digital modulation as well as other digital processing) .
  • the radio may implement one or more receive and transmit chains using the aforementioned hardware.
  • the UE 106 may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above.
  • the UE 106 may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate.
  • the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol.
  • the UE 106 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or 1xRTTor LTE or GSM) , and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.
  • FIG. 2 Block Diagram of a Base Station
  • FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor (s) 204 which may execute program instructions for the base station 102. The processor (s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor (s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.
  • MMU memory management unit
  • the base station 102 may include at least one network port 270.
  • the network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.
  • the network port 270 may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider.
  • the core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices 106.
  • the network port 270 may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider) .
  • base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB” .
  • base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs) .
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • the base station 102 may include at least one antenna 234, and possibly multiple antennas.
  • the at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230.
  • the antenna 234 communicates with the radio 230 via communication chain 232.
  • Communication chain 232 may be a receive chain, a transmit chain or both.
  • the radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.
  • the base station 102 may be configured to communicate wirelessly using multiple wireless communication standards.
  • the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies.
  • the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR.
  • the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station.
  • the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc. ) .
  • multiple wireless communication technologies e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.
  • the BS 102 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) , or a combination thereof.
  • processor 204 of the BS 102 in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.
  • processor (s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor (s) 204. Thus, processor (s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor (s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 204.
  • circuitry e.g., first circuitry, second circuitry, etc.
  • radio 230 may be comprised of one or more processing elements.
  • one or more processing elements may be included in radio 230.
  • radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of radio 230.
  • the base station or gNB 102, and/or processors 204 thereof can be capable of and configured to encode signaling with a Master Information Block (MIB) for transmission to a non-NES-supporting UE, and indicate, in the MIB, a cell barred status (e.g. cellBarred) set to barred.
  • MIB Master Information Block
  • the base station or gNB 102, and/or processors 204 thereof can be capable of and configured to encode signaling with a System Information Block Type 1 (SIB1) for transmission to the non-NES-supporting UE, and indicate, in the SIB1, a cell barred NES status (e.g. cellBarredNES) set to not barred.
  • SIB1 System Information Block Type 1
  • the base station or gNB 102, and/or processors 204 thereof can be further configured to indicate an IMS emergency support cell status (e.g. ims-EmergencySupport) set to true, and an emergency support non-NES cell status (e.g. emergencySupport-nonNES) set to true.
  • the base station or gNB 102, and/or processors 204 thereof can be capable of and configured to decode signaling from the non-NES-supporting UE with a connection request (CR) for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell.
  • CR connection request
  • IMS IP Multimedia Subsystem
  • FIG. 3 Block Diagram of a Server
  • FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor (s) 344 which may execute program instructions for the server 104. The processor (s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor (s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.
  • MMU memory management unit
  • the server 104 may be configured to provide a plurality of devices, such as base station 102, and UE devices 106 access to network functions, e.g., as further described herein.
  • the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network.
  • the server 104 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • the server 104 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) , or a combination thereof.
  • the processor 344 of the server 104 in conjunction with one or more of the other components 354, 364, and/or 374 may be configured to implement or support implementation of part or all of the features described herein.
  • processor (s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor (s) 344.
  • processor (s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor (s) 344.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 344.
  • FIG. 4 Block Diagram of a UE
  • FIG. 4 illustrates an example simplified block diagram of a communication device 106, according to some embodiments. It is noted that the block diagram of the communication device of FIG. 4 is only one example of a possible communication device.
  • communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device) , a tablet, an unmanned aerial vehicle (UAV) , a UAV controller (UAC) and/or a combination of devices, among other devices.
  • the communication device 106 may include a set of components 400 configured to perform core functions.
  • this set of components may be implemented as a system on chip (SOC) , which may include portions for various purposes.
  • SOC system on chip
  • this set of components 400 may be implemented as separate components or groups of components for the various purposes.
  • the set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 106.
  • the communication device 106 may include various types of memory (e.g., including NAND flash 410) , an input/output interface such as connector I/F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc. ) , the display 460, which may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth TM and WLAN circuitry) .
  • communication device 106 may include wired communication circuitry (not shown) , such as a network interface card, e.g., for Ethernet.
  • the cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown.
  • the short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown.
  • the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438.
  • the short to medium range wireless communication circuitry 429 and/or cellular communication circuitry 430 may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.
  • MIMO multiple-input multiple output
  • cellular communication circuitry 430 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR) .
  • cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs.
  • a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.
  • a first RAT e.g., LTE
  • a second radio may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.
  • the communication device 106 may also include and/or be configured for use with one or more user interface elements.
  • the user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display) , a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display) , a mouse, a microphone and/or speakers, one or more cameras, one or more buttons, and/or any of various other elements capable of providing information to a user and/or receiving or interpreting user input.
  • the communication device 106 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC (s) (Universal Integrated Circuit Card (s) ) cards 445.
  • SIM Subscriber Identity Module
  • UICC Universal Integrated Circuit Card
  • SIM entity is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC (s) cards 445, one or more eUICCs, one or more eSIMs, either removable or embedded, etc.
  • the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and/or otherwise implement SIM functionality.
  • each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card.
  • the SIM (s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards” )
  • the SIMs 410 may be one or more embedded cards (such as embedded UICCs (eUICCs) , which are sometimes referred to as “eSIMs” or “eSIM cards” ) .
  • one or more of the SIM (s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM (s) may execute multiple SIM applications.
  • Each of the SIMs may include components such as a processor and/or a memory; instructions for performing SIM/eSIM functionality may be stored in the memory and executed by the processor.
  • the UE 106 may include a combination of removable smart cards and fixed/non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality) , as desired.
  • the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs.
  • Various other SIM configurations are also contemplated.
  • the UE 106 may include two or more SIMs.
  • the inclusion of two or more SIMs in the UE 106 may allow the UE 106 to support two different telephone numbers and may allow the UE 106 to communicate on corresponding two or more respective networks.
  • a first SIM may support a first RAT such as LTE
  • a second SIM 410 support a second RAT such as 5G NR.
  • Other implementations and RATs are of course possible.
  • the UE 106 may support Dual SIM Dual Active (DSDA) functionality.
  • DSDA Dual SIM Dual Active
  • the DSDA functionality may allow the UE 106 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks.
  • the DSDA functionality may also allow the UE 106 to simultaneously receive voice calls or data traffic on either phone number.
  • the voice call may be a packet switched communication.
  • the voice call may be received using voice over LTE (VoLTE) technology and/or voice over NR (VoNR) technology.
  • the UE 106 may support Dual SIM Dual Standby (DSDS) functionality.
  • the DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and/or data connection. In DSDS, when a call/data is established on one SIM, the other SIM is no longer active.
  • DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUICC) that executes multiple SIM applications for different carriers and/or RATs.
  • the SOC 400 may include processor (s) 402, which may execute program instructions for the communication device 106 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460.
  • the processor (s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor (s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and/or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I/F 420, and/or display 460.
  • the MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor (s) 402.
  • the communication device 106 may include hardware and software components for implementing the above features for a communication device 106 to communicate a scheduling profile for power savings to a network.
  • the processor 402 of the communication device 106 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) .
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the processor 402 of the communication device 106 in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.
  • processor 402 may include one or more processing elements.
  • processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 402.
  • cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements.
  • one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429.
  • cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of cellular communication circuitry 430.
  • the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of short to medium range wireless communication circuitry 429.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of identify, from the MIB, a cell barred status (e.g. cellBarred) set to barred; identify, from the SIB1, a cell barred NES status (e.g. cellBarredNES) set to not barred; identify an IMS emergency support cell status (e.g. ims-EmergencySupport) set to true; identify an emergency support non-NES cell status (e.g.
  • emergencySupport-nonNES set to true; determine, at the UE, that the NES-supporting cell is acceptable for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • IMS IP Multimedia Subsystem
  • FIG. 5 Block Diagram of Cellular Communication Circuitry
  • FIG. 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of FIG. 5 is only one example of a possible cellular communication circuit.
  • cellular communication circuitry 530 which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 106 described above.
  • communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device) , a tablet and/or a combination of devices, among other devices.
  • UE user equipment
  • the cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in FIG. 4) .
  • cellular communication circuitry 530 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR) .
  • cellular communication circuitry 530 may include a modem 510 and a modem 520.
  • Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
  • a first RAT e.g., such as LTE or LTE-A
  • modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
  • modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 530.
  • RF front end 530 may include circuitry for transmitting and receiving radio signals.
  • RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534.
  • receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.
  • DL downlink
  • modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540.
  • RF front end 540 may include circuitry for transmitting and receiving radio signals.
  • RF front end 540 may include receive circuitry 542 and transmit circuitry 544.
  • receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.
  • a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572.
  • switch 570 may couple transmit circuitry 544 to UL front end 572.
  • UL front end 572 may include circuitry for transmitting radio signals via antenna 336.
  • switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572) .
  • switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572) .
  • the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein.
  • the processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) .
  • processor 512 in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.
  • processors 512 may include one or more processing elements.
  • processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processors 512.
  • the processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) .
  • the processor 522 in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.
  • processors 522 may include one or more processing elements.
  • processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processors 522.
  • FIG. 6 Block Diagram of a Baseband Processor Architecture for a UE
  • FIG. 6 illustrates example components of a device 600 in accordance with some embodiments. It is noted that the device of FIG. 6 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various UEs, as desired.
  • the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
  • the components of the illustrated device 600 may be included in a UE 106 or a RAN node.
  • the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC) .
  • the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
  • C-RAN Cloud-RAN
  • the application circuitry 602 may include one or more application processors.
  • the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) .
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 600.
  • processors of application circuitry 602 may process IP data packets received from an EPC.
  • the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
  • Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor (s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G) , sixth generation (6G) , etc. ) .
  • the baseband circuitry 604 e.g., one or more of baseband processors 604A-D
  • baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT) , precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 604 may include one or more audio digital signal processor (s) (DSP) 604F.
  • the audio DSP (s) 604F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC) .
  • SOC system on a chip
  • the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) .
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
  • RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 604 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a necessity.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection) .
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO) , although that is not a necessity.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA) .
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO) .
  • the RF circuitry 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
  • the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606) .
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610) .
  • PA power amplifier
  • the PMC 612 may manage power provided to the baseband circuitry 604.
  • the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604, in other embodiments the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
  • the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in a radio resource control_Connected (RRC_Connected) state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.
  • RRC_Connected radio resource control_Connected
  • DRX Discontinuous Reception Mode
  • the device 600 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 600 may not receive data in this state, in order to receive data, it will transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 604 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) .
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • the baseband circuitry 604 can be used to encode a message for transmission between a UE and a gNB, or decode a message received between a UE and a gNB.
  • the baseband circuitry 604 can be used to decode, at the UE, signaling with a Master Information Block (MIB) received from a base station associated with a network energy saving (NES) -supporting cell; and decode, at the UE, signaling with a System Information Block Type 1 (SIB1) received from the base station associated with the NES-supporting cell.
  • MIB Master Information Block
  • SIB1 System Information Block Type 1
  • FIG. 7 Block Diagram of an Interface of Baseband Circuitry
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.
  • the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
  • Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
  • the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604) , an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6) , an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
  • an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG.
  • an RF circuitry interface 716 e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a wireless hardware connectivity interface 718 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, components (e.g., Low Energy) , components, and other communication components
  • NFC Near Field Communication
  • components e.g., Low Energy
  • components e.g., Low Energy
  • components e.g., Low Energy
  • components e.g., Low Energy
  • components e.g., Low Energy
  • a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
  • FIG. 8 Core Network
  • FIG. 8 illustrates an example architecture of a system 800 including a core network (CN) 820 in accordance with various embodiments.
  • the CN 820 may be a core network for a 5G System (which may be referred to as a 5GC) .
  • the system 800 is shown to include a UE 801, which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R) AN 102, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 803, which may be, for example, operator services, Internet access, or 3rd party services; and a CN 820.
  • a UE 801 which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously
  • R AN 102
  • DN data network
  • the CN 820 may include a number of network functions including an Authentication Server Function (AUSF) 822; an Access and Mobility Management Function (AMF) 821; a Session Management Function (SMF) 824; a Network Exposure Function (NEF) 823; a Policy Control Function (PCF) 826; a Network Repository Function (NRF) 825; a Unified Data Management (UDM) 827; an Application Function (AF) 828; a User Plane Function (UPF) 802; and a Network Slice Selection Function (NSSF) 829.
  • AUSF Authentication Server Function
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • NEF Network Exposure Function
  • PCF Policy Control Function
  • NRF Network Repository Function
  • UDM Unified Data Management
  • AF Application Function
  • UPF User Plane Function
  • NSSF Network Slice Selection Function
  • the UPF 802 may act as an anchor point for intra-RAT and inter-RAT mobility, an external packet data unit (PDU) session point of interconnect to DN 803, and a branching point to support mufti-homed PDU session.
  • PDU session is a logical connection between the UE and the DN.
  • the UPF 802 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (user plane (UP) collection) , perform traffic usage reporting, perform quality of service (QoS) handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement) , perform Uplink Traffic verification (e.g., Service Data Flows (SDF) to QoS flow mapping) , transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 802 may include an uplink classifier to support routing traffic flows to a data network.
  • the DN 803 may represent various network operator services, Internet access, or third party services. DN 803 may include, or be similar to, application server 430 discussed previously.
  • the UPF 802 may interact with the SMF 824 via an N4 reference point between the SMF 821 and the UPF 802.
  • the AUSF 822 may store data for authentication of UE 801 and handle authentication-related functionality, The AUSF 822 may facilitate a common authentication frame work for various access types.
  • the AUSF 822 may communicate with the AMF 821 via an N12 reference point between the AMF 821 and the AUSF 822; and may communicate with the UDM 827 via an N13 reference point between the UDM 827 and the AUSF 822. Additionally, the AUSF 822 may exhibit an Nausf service-based interface.
  • the AMF 821 may be responsible for registration management (e.g., for registering UE 801, etc. ) , connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 821 may be a termination point for the an N11 reference point between the AMF 821 and the SMF 824.
  • the AMF 821 may provide transport for SM messages between the UE 801 and the SMF 824, and act as a transparent proxy for routing SM messages.
  • AMF 821 may also provide transport for Short Message Service (SMS) messages between UE 801 and an SMSF (not shown by FIG. 8) .
  • SMS Short Message Service
  • AMF 821 may act as a security anchor function (SEAF) , which may include interaction with the AUSF 822 and the UE 801, receipt of an intermediate key that was established as a result of the UE 801 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 821 may retrieve the security material from the AUSF 822. AMF 821 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys.
  • SEAF security anchor function
  • SCM Security Context Management
  • AMF 821 may be a termination point of a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R)AN 810 and the AMF 821; and the AMF 821 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • CP RAN control plane
  • Nl NAS
  • AMF 821 may also support NAS signaling with a UE 801 over a non-3GPP Inter-Working Function (N3IWF) interface.
  • the N3IWF may be used to provide access to untrusted entities.
  • N3IWF may be a termination point for the N2 interface between the (R) AN 810 and the AMF 821 for the control plane, and may be a termination point for the N3 reference point between the (R) AN 810 and the UPF 802 for the user plane.
  • the AMF 821 may handle N2 signaling from the SMF 824 and the AMF 821 for PDU sessions and encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking while considering QoS requirements associated with such marking received over N2.
  • N3IWF may also relay uplink and downlink control plane non-access stratum (NAS) signaling between the UE 801 and AMF 821 via an N1 reference point between the UE 801 and the AMF 821, and relay uplink and downlink user-plane packets between the UE 801 and UPF 802.
  • NAS non-access stratum
  • the N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 801.
  • IPsec internet protocol security
  • the AMF 821 may exhibit an Namf service based interface, and may be a termination point for an N14 reference point between two AMFs 821 and an N17 reference point between the AMF 821 and a 5G Equipment Identity Register (5G-EIR) (not shown by FIG. 8) .
  • 5G-EIR 5G Equipment Identity Register
  • the UE 801 may need to register with the AMF 821 in order to receive network services.
  • Registration Management is used to register or deregister the UE 801 with the network (e.g., AMF 821) , and establish a UE context in the network (e.g., AMF 821) .
  • the UF 801 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 801 is not registered with the network, and the UE context in AMF 821 holds no valid location or routing information for the UE 801 so the UE 801 is not reachable by the AMF 821.
  • the UE 801 In the RM REGISTERED state, the UE 801 is registered with the network, and the UE context in AMF 821 may hold a valid location or routing information for the UE 801 so the UE 801 is reachable by the AMF 821.
  • the UE 801 In the RM-REGISTERED state, the UE 801 may perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 801 is still active) , and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.
  • the AMF 821 may store one or more RM contexts for the UE 801, where each RM context is associated with a specific access to the network.
  • the RM context may be a data structure, database object, etc. that indicates or stores, inter glia, a registration state per access type and the periodic update timer.
  • the AMF 821 may also store a 5GC mobility management (MM) context that may be the same or similar to the evolved packet services (EPS) Mobility Management (E) MM context discussed previously.
  • EPS evolved packet services
  • E Mobility Management
  • the AMF 821 may store a CE mode B Restriction parameter of the UE 801 in an associated MM context or registration management (RM) context.
  • the AMF 821 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context) .
  • CM Connection Management
  • the signaling connection is used to enable NAS signaling exchange between the UE 801 and the CN 820, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 801 between the AN (e.g., AN 810) and the AMF 821.
  • the UE 801 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode.
  • the UE 801 When the UE 801 is operating in the CM-IDLE state/mode, the UE 801 may have no NAS signaling connection established with the AMF 821 over the N1 interface, and there may be (R) AN 810 signaling connection (e.g., N2 and/or N3 connections) for the UE 801.
  • the UE 801 When the UE 801 is operating in the CM-CONNECTED state/mode, the UE 801 may have an established NAS signaling connection with the AMF 821 over the Nl interface, and there may be a (R) AN 810 signaling connection (e.g., N2 and/or N3 connections) for the UE 801.
  • Establishment of an N2 connection between the (R) AN 810 and the AMF 821 may cause the UE 801 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 801 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R) AN 810 and the AMF 821 is released.
  • the SMF 824 may be responsible for session management (SM) session establishment, modify and release, including tunnel maintain between UPF and AN node) ; UE IP address allocation and management (including optional authorization) ; selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system) ; termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session.
  • SM session management
  • SM may refer to management of a PDU session
  • a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 801 and a data network (DN) 803 identified by a Data Network Name (DNN) .
  • PDU sessions may be established upon UE 801 request, modified upon UE 801 and CN 820 request, and released upon UE 801 and CN 820 request using NAS SM signaling exchanged over the N1 reference point between the UE 801 and the SMF 824.
  • the CN 820 may trigger a specific application in the UE 801.
  • the UE 801 may pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE 801.
  • the identified application (s) in the UE 801 may establish a PDU session to a specific data network name (DNN) .
  • the SMF 824 may check whether the UE 801 requests are compliant with user subscription information associated with the UE 801. In this regard, the SMF 824 may retrieve and/or request to receive update notifications on SMF 824 level subscription data from the UDM 827.
  • the SMF 824 may include the following roaming functionality: handling local enforcement to apply QoS SLAB virtual Public Land Mobile Network (VPLMN) ; charging data collection and charging interface (VPLMN) ; lawful intercept (in VPLMN for SM events and interface to LI system) ; and support for interaction with external DN for transport of signaling for PDU session authorization/authentication by external DN.
  • An N16 reference point between two SMFs 824 may be included in the system 800, which may be between another SMF 824 in a visited network and the SMF 824 in the home network in roaming scenarios. Additionally, the SMF 824 may exhibit the Nsmf service-based interface.
  • the NEF 823 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF 828) , edge computing or fog computing systems, etc.
  • the NEF 823 may authenticate, authorize, and/or throttle the AFS.
  • NEF 823 may also translate information exchanged with the AF 828 and information exchanged with internal network functions. For example, the NEF 823 may translate between an AF-Service-Identifier and an internal SCC information.
  • NEF 823 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 823 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 823 to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF 823 may exhibit an Nnef service-based interface.
  • NFs network
  • the NRF 825 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 825 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate, " “instantiation, “ and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 825 may exhibit the Nnrf service based interface.
  • the PCF 826 may provide policy rules to control plane function (s) to enforce them, and may also support unified policy framework to govern network behavior,
  • the PCF 826 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM 827.
  • the PCF 826 may communicate with the AMF 821 via an N15 reference point between the PCF 826 and the AMF 821, which may include a PCF 826 in a visited network and the AMF 821 in case of roaming scenarios.
  • the PCF 826 may communicate with the AF 828 via an NS reference point between the PCF 826 and the AF 828; and with the SMF 824 via an N7 reference point between the PCF 826 and the SMF 824,
  • the system 800 and/or CN 820 may also include an N24 reference point between the PCF 826 (in the home network) and a PCF 826 in a visited network, Additionally, the PCF 826 may exhibit an Npcf service-based interface.
  • the UDM 827 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 801. For example, subscription data may be communicated between the UDM 827 and the AMF 821 via an NS reference point between the UDM 827 and the AMF.
  • the UDM 827 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 8) .
  • the UDR may store subscription data and policy data for the UDM 827 and the PCF 826, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 801) for the NEF 823.
  • the Nadr service-based interface may be exhibited by the UDR 221 to allow the UDM 827, PCF 826, and NEF 823 to access a particular set of the stored data, as well as to read, update (e.g., add, modify) , delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDR may interact with the SMF 824 via an Nl0 reference point between the UDM 827 and the SMF 824.
  • UDM 827 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 827 may exhibit the Nudm service based interface.
  • the AF 828 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control.
  • the NCE may be a mechanism that allows the CN 820 and AF 828 to provide information to each other via NEF 823, which may be used for edge computing implementations.
  • the network operator and third party services may be hosted close to the UE 801 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5GC may select a UPF 802 close to the UE 801 and execute traffic steering from the UPF 502 to ON 803 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 828.
  • the AF 828 may influence UPF (re) selection and traffic routing. Based on operator deployment, when AF 828 is considered to be a trusted entity, the network operator may permit AF 828 to interact directly with relevant NFs. Additionally, the AF 828 may exhibit an Naf service-based interface.
  • the NSSF 829 may select a set of network slice instances serving the UE 501.
  • the NSSF 829 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI) is, if needed.
  • the NSSF 829 may also determine the AMF set to be used to serve the UE 801, or a list of candidate AMF (s) 821 based on a suitable configuration and possibly by querying the NRF 825.
  • the selection of a set of network slice instances for the UE 801 may be triggered by the AMF 821 with which the UE 801 is registered by interacting with the NSSF 829, which may lead to a change of AMF 821.
  • the NSSF 829 may interact with the AMF 821 via an N22 reference point between AMF 821 and NSSF 829; and may communicate with another NSSF 829 in a visited network via an N31 reference point (not shown by FIG. 8) . Additionally, the NSSF 829 may exhibit an Nnssf service-based interface.
  • the CN 820 may include a short message service function (SMSF) , which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 801 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router.
  • SMS may also interact with AMF 821 and UDM 827 for a notification procedure that the UE 801 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 827 when UE 801 is available for SMS) .
  • SMS short message service function
  • the CN 820 may also include other elements that are not shown by FIG. 8, such as a Data Storage system/architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP) , and the like.
  • the Data Storage system may include a Structured Data Storage Network Function (SDSF) , air Unstructured Data Storage Function (UDSF) , and/or the like.
  • SDSF Structured Data Storage Network Function
  • UDSF air Unstructured Data Storage Function
  • Any network function (NF) may store and retrieve unstructured data into/from the UDSF (e.g., UE contexts) , via N18 reference point between any NF and the UDSF (not shown by FIG.
  • Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Addition-ally, the UDSF may exhibit an Nudsf service-based interface (not shown by FIG. 8) .
  • the 5G-EIR may be an NF that checks the status of permanent equipment identifier (PEI) for determining whether particular equipment/entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.
  • PEI permanent equipment identifier
  • SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.
  • the CN 820 may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 821 in order to enable interworking between CN 820 and a CN in a 4G system.
  • Nx interface is an inter-CN interface between a mobility management entity (MME) and the AMF 821 in order to enable interworking between CN 820 and a CN in a 4G system.
  • Other example interfaces/reference points may include an N5G-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.
  • NES Network Energy Savings
  • the NES may change legacy operation of base stations, e.g. gNBs, and UEs to allow additional power savings at the gNB.
  • 3GPP RAN2 the operation of cell level Discontinuous Transmission (DTX) and Discontinuous Reception (DRX) would configure NES supporting UEs to align with the current cell state (active or Cell DTX or Cell DRX) .
  • the enhancement on cell DTX/DRX mechanism includes the alignment of cell DTX/DRX and UE DRX in RRC_CONNECTED mode, and inter-node information exchange on cell DTX/DRX in RAN2, RAN1, and RAN3.
  • the enhancement may have no change for Synchronization Signal Block (SSB) transmission due to cell DTX/DRX.
  • SSB Synchronization Signal Block
  • SIB1 System Information Block Type 1
  • An optional new field in SIB1 may be cellBarredNES with a value “not barred” .
  • the network (NW) can bar every UE except NES-supporting UEs in case there is a deployment of NES being phased in.
  • the NES supporting UE logic can comprise: if the field is absent, then the UE may continue to use the cell. If the field is present, the usefulness of this field depends on whether the cell is barred. If the cell is barred, and this field is present, the NES-supporting UEs can continue using the cell.
  • Non-NES-UE can access the cell, and non-NES-supporting UEs may consider this cell as barred.
  • the gNB may only allow NES-supporting UEs.
  • the NON-NES-supporting UE logic can comprise: If the cell is barred, even when cellBarredNES is set to notBarred, the non-NES-supporting UEs will bar the cell.
  • Cell barring by the UE in 3GPP RAN2 logic can comprise: If the UE cannot support ‘basic’ downlink (DL) and uplink (UL) capabilities to support a CONNECTED mode session, then channel bandwidth is unsupported, carrier as well as bandwidth part (BWP) bandwidth, and sub-carrier spacing for the operating frequency/bandwidth (BW) is unsupported.
  • BWP bandwidth part
  • BW bandwidth part
  • BW sub-carrier spacing for the operating frequency/bandwidth
  • the cell may restrict operation of the UE for the following functions: for RedCap UEs: 1 Rx chain UEs and 2Rx chain UEs; for enhanced reduced capability (eRedCap) UEs: 1 Rx chain UEs and 2Rx chain UEs; half-duplex operation the same for both RedCap and eRedCap; and non-NES-supporting UEs in certain cases.
  • RedCap UEs 1 Rx chain UEs and 2Rx chain UEs
  • eRedCap enhanced reduced capability
  • the UE may be expected to ‘bar’ the cell. Furthermore, the UE may not be allowed to make an emergency call on these cells.
  • TS Technical Specification
  • the UE is not permitted to select/reselect this cell, not even for emergency calls.
  • the UE shall select another cell according to the following rule:
  • the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds.
  • the UE may select another cell on the same frequency if the selection criteria are fulfilled.
  • NES can be an enhancement to the gNBs and legacy gNBs may be enhanced with NES. Separate gNBs may not be deployed just for NES alone. NES-supporting gNBs may also provide legacy service, including handling emergency calls. Since NES-supporting gNBs occupy a geographical area, legacy (i.e. non-NES-supporting UEs) may roam into these NES-supporting cells. If the field cellBarredNES is set in the SIB1, then these legacy, non-NES-supporting UEs may bar this NES-supporting cell. In addition, the logic of barring the cells may not allow legacy, non-NES-supporting UEs to receive emergency broadcast messages. It is beneficial to enable UEs to be able to make and receive emergency calls in as many cells as possible.
  • a NES-supporting gNB can be configured to enable emergency calls within a NES-supporting cell to any UEs, including non-NES-supporting UEs. Changes may be made mostly in CONNECTED mode, without impact to IDLE/INACTIVE UEs. In addition, in CONNECTED mode, since the NES-supporting cell servicing emergency calls can transmit during Cell DTX time.
  • UE IDLE mode In UE IDLE mode, once a UE is powered on “or” moves from CONNECTED mode to IDLE (to INACTIVE) , the UE is in an ‘Any cell selection state’ .
  • the UE is configured to search for cells, as disclosed in 3GPP TS 38.304 V. 18.0.0 (2023-12) (hereinafter referred to as “TS 38.304) in Sections 5.2.7 and 5.2.8.
  • the UE can attempt to find a cell referred to as a ‘suitable’ cell.
  • a cell is ‘suitable’ if: the cell is not barred (TS 38.304 -sec 5.3.1) ; the cell selection criteria are fulfilled (TS 38.304 -sec 5.2.3.2) ; and the cell is part of a registered public land mobile network (PLMN) . There may be other requirements. If a suitable cell is found, the UE can move to a ‘camped normally’ state. If a suitable cell is not found, the UE can attempt to find a cell referred to as an ‘acceptable’ cell. A cell is acceptable if: the cell is not barred (TS 38.304 -sec 5.3.1) ; and the cell selection criteria are fulfilled (TS 38.304 -sec 5.2.3.2) .
  • the UE can move to a ‘camp on any cell’ state and continue to be in this state. It is expected that UE will attempt searching again based on an external trigger, e.g. when a user places a call, or on a periodic occasion.
  • FIG. 9 Enabling Emergency Call in NES Without NW Signaling
  • NES Network energy saving
  • 3GPP Rel-18 3GPP Rel-18 to allow power savings at a base station, such as a next generation Node B (gNB) .
  • gNB next generation Node B
  • a legacy, non-NES-supporting user equipment (UE) may be barred from connecting to an NES cell, even for emergency calls.
  • IMS emergency calling can be enabled without NW signaling and without IMS emergency dependency. If a legacy, non-NES-supporting UE cannot find any suitable cell, then the UE can consider an NES-supporting cell which has a Master Information Block (MIB) set to barred, and a SIB1 with a cell barred NES status, e.g. cellBarredNES, set to not barred, as an acceptable cell. Thus, the non-NES-supporting UE may make an emergency call, and/or receive emergency broadcast messages. In this case, there is no expectation that the NW should support an IMS EM call. It may be expected that the NES-supporting cell supports EM calls.
  • MIB Master Information Block
  • the specification can specify:
  • the UE is not permitted to select/reselect this cell, not even for emergency calls except for the below cases:
  • the UE can consider the cell as acceptable cell if cellBarred in MIB is set to “barred” and in SIB1, cellBarredNES is set to “not barred” .
  • FIG. 9 provides an illustration of example signaling 900 during cell selection, according to some embodiments.
  • an apparatus of a user equipment (UE) 106 can comprise one or more processors 402, 604 coupled to a memory 406, 604G.
  • the processors 604 can be configured to decode, at the UE 106, signaling 910 with a Master Information Block (MIB) received from a base station 102 associated with a network energy saving (NES) -supporting cell.
  • MIB Master Information Block
  • NES network energy saving
  • the processors 604 can be configured to decode, at the UE 106, signaling 920 with a System Information Block Type 1 (SIB1) received from the base station 102 associated with the NES-supporting cell.
  • SIB1 System Information Block Type 1
  • the processors 402 can be configured to identify, from the SIB1, a cell barred NES status set to not barred.
  • the processors 402 can be configured to determine, at the UE 106, that the NES-supporting cell is acceptable for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • IMS IP Multimedia Subsystem
  • the UE 106 can be a non-NES-supporting UE.
  • the processors 402 can further be configured to determine, at the UE 106, that the NES-supporting cell is barred for a non-IMS-emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • the processors 604 can further be configured to decode, at the UE 106, signaling received from neighboring base stations.
  • Each base station can be associated with a cell having a MIB and a SIB1.
  • the processors 402 can further be configured to determine, at the UE 106, that cells associated with the neighboring base stations are not suitable cells based on one or more factors comprising that the cells: are MIB or SIB1 barred; do not fulfill cell selection criteria; or are not part of a registered Public Land Mobile Network (PLMN) .
  • PLMN Public Land Mobile Network
  • the processors 604 can further be configured to encode, at the UE 106, signaling 930 for transmission to the cell with a connection request (CR) for the IMS emergency call.
  • CR connection request
  • an apparatus of a next generation Node B (gNB) 102 can be associated with a network energy saving (NES) -supporting cell.
  • the apparatus can comprise one or more processors 204 coupled to a memory 206.
  • the processors 204 can be configured to encode, at the gNB 102, signaling 910 with a Master Information Block (MIB) for transmission to a non-network-energy-saving (non-NES) -supporting user equipment (UE) 106.
  • MIB Master Information Block
  • UE non-network-energy-saving
  • the processors 204 can be configured to indicate, in the MIB, a cell barred status set to barred.
  • the processors 204 can be configured to encode, at the gNB 102, signaling 920 with a System Information Block Type 1 (SIB1) for transmission to the non-NES-supporting UE.
  • SIB1 System Information Block Type 1
  • the processors 204 can be configured to indicate, in the SIB1, a cell barred NES status set to not barred.
  • the processors 204 can be configured to decode, at the gNB 102, signaling 930 from the non-NES-supporting UE 106 with a connection request (CR) for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell.
  • CR connection request
  • IMS IP Multimedia Subsystem
  • FIG. 10 Flow Chart for a Method of Enabling an Emergency Call in NES
  • FIG. 10 illustrates a flow chart of an example of a method for enabling an emergency call in NES, according to some embodiments.
  • the method shown in FIG. 10 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.
  • a method 1000 is for enabling an IP Multimedia Subsystem (IMS) emergency call with a base station 102 associated with a network energy saving (NES) -supporting cell, at a non-NES-supporting user equipment (UE) 106.
  • the method 1000 can comprise decoding 1010, at the UE 106, signaling with a Master Information Block (MIB) received from the base station 102 associated with the NES-supporting cell.
  • MIB Master Information Block
  • the method 1000 can comprise identifying 1020, from the MIB, a cell barred status set to barred.
  • the method 1000 can comprise decoding1030, at the UE 106, signaling with a System Information Block Type 1 (SIB1) received from the base station 102 associated with the NES-supporting cell.
  • SIB1 System Information Block Type 1
  • the method 1000 can comprise identifying 1040, from the SIB1, a cell barred NES status set to not barred.
  • the method 1000 can comprise determining 1050, at the non-NES-supporting UE 106, that the NES-supporting cell is acceptable for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • IMS IP Multimedia Subsystem
  • the method 1000 can comprise determining, at the non-NES-supporting UE 106, that the NES-supporting cell is barred for a non-IMS-emergency call in the NES-supporting cell based on the cell barred status of the MIB and the cell barred NES status of the SIB1.
  • the method 1000 can comprise decoding, at the non-NES-supporting UE 106, signaling received from neighboring base stations.
  • Each neighboring base station can be associated with a cell having a MIB and a SIB1.
  • the method 1000 can comprise determining, at the non-NES-supporting UE 106, that the cells associated with the neighboring base stations are not suitable cells based on one or more factors comprising that the cells: are MIB or SIB1 barred; do not fulfill cell selection criteria; and are not part of a registered Public Land Mobile Network (PLMN) .
  • PLMN Public Land Mobile Network
  • the method 1000 can comprise encoding, at the non-NES-supporting UE 106, signaling for transmission to the cell with a connection request (CR) for the IMS emergency call.
  • CR connection request
  • FIG. 11 Flow Chart for a Method of Enabling an Emergency Call in NES
  • FIG. 11 illustrates a flow chart of an example of a method for enabling an emergency call in NES, according to some embodiments.
  • the method shown in FIG. 11 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.
  • a method 1100 is for enabling an IP Multimedia Subsystem (IMS) emergency call with a non-network-energy-saving (NES) user equipment (UE) 106, at a next generation Node B (gNB) 102 associated with a NES-supporting cell.
  • the method 1100 can comprise encoding 1110, at the gNB 102, signaling with a Master Information Block (MIB) for transmission to the non-NES-supporting UE 106.
  • the method 1100 can comprise indicating 1120, in the MIB, a cell barred status set to barred.
  • IMS IP Multimedia Subsystem
  • MIB Master Information Block
  • the method 1100 can comprise encoding 1130, at the gNB 102, signaling with a System Information Block Type 1 (SIB1) for transmission to the non-NES-supporting UE.
  • SIB1 System Information Block Type 1
  • the method 1100 can comprise indicating 1140, in the SIB1, a cell barred NES status set to not barred.
  • the method 1100 can comprise decoding 1150, at the gNB 102, signaling from the non-NES-supporting UE 106 with a connection request (CR) for an IP Multimedia Subsystem (IMS) emergency call in the NES-supporting cell.
  • CR connection request
  • IMS IP Multimedia Subsystem
  • FIG. 12 Enabling Emergency Call in NES Without NW Signaling
  • IMS emergency calling can be enabled without NW signaling. If a legacy, non-NES-supporting UE cannot find any suitable cell, then the UE can consider an NES-supporting cell which has a Master Information Block (MIB) set to barred, and a SIB1 with a cell barred NES status, e.g. cellBarredNES, set to not barred, as an acceptable cell. Thus, the non-NES-supporting UE may make an emergency call, and/or receive emergency broadcast messages.
  • the NW can support handling IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS) based emergency calls in this NES-supporting cell.
  • IMS IP Multimedia Core Network Subsystem
  • the specification can specify:
  • the UE is not permitted to select/reselect this cell, not even for emergency calls except for the below cases:
  • the UE can consider the cell as acceptable cell if cellBarred in MIB is set to “barred” and in SIB1, cellBarredNES is set to “not barred” and ims-EmergencySupport is set to “true” .
  • FIG. 12 provides an illustration of example signaling 1200 during cell selection, according to some embodiments.
  • the SIB1 further comprises an IMS emergency support cell status set to true 1220.
  • the processors 402 can further be configured to determine, at the UE 106, that the NES-supporting cell is acceptable for the IMS emergency call in the NES-supporting cell further based on the IMS emergency support cell status.
  • the processors 204 of the gNB 102 can further be configured to indicate that the SIB1 further comprises an IMS emergency support cell status set to true.
  • the SIB1 can further comprise an IMS emergency support cell status set to true.
  • the method 1000 can further comprise determining, at the non-NES-supporting UE 106, that the NES-supporting cell is acceptable for the IMS emergency call in the NES-supporting cell further based on the IMS emergency support cell status.
  • the method 1100 of FIG. 11 can further comprise the SIB1 further comprising an IMS emergency support cell status set to true.
  • FIGs. 13 and 14 Enabling Emergency Call in NES With NW Signaling
  • FIG. 13 provides an illustration of example of ASN. 1 code 1300 used for the network to configure the SIB1, according to some embodiments.
  • a new SIB1 bit can inform if UEs can be allowed to place an emergency call.
  • a new SIB1 field e.g. emergencySupport-nonNES, can be added, as shown in bold in FIG. 13. This may restrict UEs which are configured to support 3GPP Release 18 (R18) , but are non-NES-supporting.
  • the specification can specify:
  • the UE is not permitted to select/reselect this cell, not even for emergency calls except for the below cases:
  • the UE can consider the cell as acceptable cell if cellBarred in MIB is set to “barred” and in SIB1, cellBarredNES is set to “not barred” and emergencySupport-nonNES is set to “true” and ims-EmergencySupport is set to “true” .
  • FIG. 14 provides an illustration of example signaling 1400 during cell selection, according to some embodiments.
  • the SIB1 can further comprise an emergency support non-NES cell status set to true 1420.
  • the processors 402 can be further configured to determine, at the UE 106, that the NES-supporting cell is acceptable for the IMS emergency call in the NES-supporting cell further based on the emergency support non-NES cell status.
  • the processors 204 of the gNB 102 can further be configured to indicate that the SIB1 further comprises an emergency support non-NES cell status set to true.
  • the SIB1 can further comprise an emergency support non-NES cell status set to true.
  • the method 1000 can further comprise determining, at the UE 106, that the NES-supporting cell is acceptable for the IMS emergency call in the NES-supporting cell further based on the emergency support non-NES cell status.
  • the method 1100 of FIG. 11 can further comprise the SIB1 further comprising an emergency support non-NES cell status set to true.
  • FIG. 15 Enabling Emergency Call in NES With NW Signaling
  • IMS emergency calling can be enabled with NW signaling, and without IMS emergency dependency.
  • the specification can specify:
  • the UE is not permitted to select/reselect this cell, not even for emergency calls except for the below cases:
  • the UE can consider the cell as acceptable cell if cellBarred in MIB is set to “barred” and in SIB1, cellBarredNES is set to “not barred” and emergencySupport-nonNES is set to “true” .
  • FIG. 15 provides an illustration of example signaling 1500 during cell selection, according to some embodiments.
  • the SIB1 further comprises an emergency support non-NES cell status set to true 1520.
  • the processors 402 can be further configured to determine, at the UE 106, that the NES-supporting cell is acceptable for the IMS emergency call in the NES-supporting cell further based on the emergency support non-NES cell status.
  • the processors 204 of the gNB 102 can further be configured to indicate that the SIB1 further comprises an emergency support non-NES cell status set to true.
  • the method 1100 of FIG. 11 can further comprise the SIB1 further comprising an emergency support non-NES cell status set to true.
  • FIGs. 16-18 Enabling Emergency Call on Inter-Node Exchange
  • IMS emergency calling can be enabled with inter-node exchange.
  • Network (Xn) interface can be changed to allow a source gNB 102C to inform a target gNB 102D about the support and/or no-support of the IMS emergency calling feature (where NW signaling is utilized) . If the target gNB 102D does not support emergency call by non-NES-supporting UEs 106, e.g. if the field emergencySupport-nonNES is not present in the target cell.
  • the source gNB 102C which is handling the emergency call, can find other cells to assess as the candidate for handover for the UE.
  • FIG. 16 provides an illustration of example signaling 1600 during handover, according to some embodiments.
  • the gNB is a source gNB 102C.
  • the processors 204 can further be configured to encode, at the source gNB, signaling 1610 for transmission to a target gNB 102D with a handover request with an emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the processors 204 can be configured decode, at the source gNB 102C, signaling 1620 received from the target gNB 120D with a handover request acknowledgement indicating support of IMS emergency call for a non-NES-supporting UE.
  • FIG. 17 provides an illustration of example signaling 1700 during handover, according to some embodiments.
  • the gNB is a source gNB 102C.
  • the processors 204 can be configured to encode, at the source gNB 102C, signaling 1610 for transmission to a first target gNB 102D with a first handover request with an emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the processors 204 can be configured to decode, at the source gNB 102C, signaling 1720 received from the first target gNB 102D with a handover request rejection indicating non-support of IMS emergency call for a non-NES-supporting UE.
  • the processors 204 can be configured to encode, at the source gNB 102C, signaling 1730 for transmission to a second target gNB 102E with a second handover request with an emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the method 1100 of FIG. 11 can further comprise encoding, at the source gNB 102C, signaling for transmission to a first target gNB 102D with a first handover request with an emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the method 1100 can comprise decoding, at the source gNB 102C, signaling received from the first target gNB 102D with a handover request rejection indicating non-support of IMS emergency call for a non-NES-supporting UE.
  • the method 1100 can comprise encoding, at the source gNB 102C, signaling for transmission to a second target gNB 102E with a second handover request with an emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the Xn interface exchange can be at an operator management system (OMS) (cell configuration time) and each gNB can know which neighbor cells support the emergency call feature, and which neighbor cells do not support the emergency call feature.
  • OMS operator management system
  • the source gNB may only configure the NCell for measurement, or trigger handover to the cells that support the emergency call feature.
  • FIG. 18 provides an illustration of example signaling 1800 during handover, according to some embodiments.
  • the processors 604 can be configured to encode, at the source gNB 102C, signaling 1810 for transmission to a neighbor gNB 102D with a network (Xn) setup request with an inquiry regarding support of emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the processors 604 can be configured to decode, at the source gNB 102C, signaling 1820 received from the neighbor gNB 102D with an Xn setup response indicating support or non-support of IMS emergency call for a non-NES-supporting UE.
  • the method 1100 of FIG. 11 can further comprise encoding, at the source gNB 102C, signaling for transmission to a neighboring gNB 102D with a network (Xn) setup request with an inquiry regarding support of emergency support non-NES cell status indicating support of IMS emergency call for a non-NES-supporting UE.
  • the method 1100 can comprise decoding, at the source gNB 102C, signaling received from the neighboring gNB 102D with an Xn setup response indicating support or non-support of IMS emergency call for a non-NES-supporting UE.
  • Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.
  • a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.
  • a device e.g., a UE 106 may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets) .
  • the device may be realized in any of various forms.
  • Any of the methods described herein for operating a user equipment may be the basis of a corresponding method for operating a base station, by interpreting each message/signal X received by the UE in the downlink as message/signal X transmitted by the base station, and each message/signal Y transmitted in the uplink by the UE as a message/signal Y received by the base station.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un appareil d'un équipement utilisateur (UE) comprenant un ou plusieurs processeurs couplés à une mémoire. Les processeurs sont configurés pour décoder, au niveau de l'UE, la signalisation avec un bloc d'informations maître (MIB) reçu d'une station de base associée à une cellule prenant en charge l'économie d'énergie du réseau (NES), et identifier, à partir du MIB, un état de blocage de cellule défini sur bloqué. Les processeurs sont configurés pour décoder, au niveau de l'UE, la signalisation avec un bloc d'informations système de type 1 (SIB1) reçu de la station de base associée à la cellule prenant en charge le NES, et identifier, à partir du SIB1, un état NES de cellules interdites défini comme non interdit. Les processeurs sont configurés pour déterminer, au niveau de l'UE, que la cellule prenant en charge le NES est acceptable pour un appel d'urgence IMS (IP Multimedia Subsystem) dans la cellule prenant en charge le NES, en fonction de l'état de blocage de la cellule dans le MIB et de l'état de blocage NES de la cellule dans le SIB1.
PCT/CN2024/082677 2024-03-20 2024-03-20 Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes Pending WO2025194379A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/082677 WO2025194379A1 (fr) 2024-03-20 2024-03-20 Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/082677 WO2025194379A1 (fr) 2024-03-20 2024-03-20 Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes

Publications (1)

Publication Number Publication Date
WO2025194379A1 true WO2025194379A1 (fr) 2025-09-25

Family

ID=97138298

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/082677 Pending WO2025194379A1 (fr) 2024-03-20 2024-03-20 Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes

Country Status (1)

Country Link
WO (1) WO2025194379A1 (fr)

Similar Documents

Publication Publication Date Title
WO2021196161A1 (fr) Déduction et rafraîchissement de clé de fonction d'application
US12267800B2 (en) Network (NW) techniques for constraints on simultaneous use of network slices
US12284719B2 (en) Revocation and modification of user consent
US12137432B2 (en) User equipment (UE) techniques for constraints on simultaneous use of network slices
EP3941116A1 (fr) Transfert de session pdu
US20220022103A1 (en) PDU Session Handover
EP4156767B1 (fr) Gestion de description de flux de paquets axée sur l'ue
WO2025194379A1 (fr) Activation d'appels d'urgence et réception de diffusion d'urgence dans des cellules nes
WO2025171543A1 (fr) Améliorations apportées à un retard de commutation d'indicateur de configuration de transmission (tci) unifié avec deux avances temporelles (ta) dans la gamme de fréquences 2 (fr2)
WO2025208436A1 (fr) Optimisation d'utilisation de chercheur pour mesure ca/cc
WO2025091347A1 (fr) Sélection de cellule voisine pour mesure l1
WO2025199856A1 (fr) Configuration et procédés d'ue pour mettre en œuvre une mobilité déclenchée par l1/l2 (ltm) inter-cu
WO2025160752A1 (fr) Améliorations de la couverture pour pusch avec format dci 0_3
WO2025091354A1 (fr) Partage d'opportunités de mesure entre la couche 1 et la couche 3
WO2025231713A1 (fr) Amélioration de l'activation d'une cellule secondaire (scell) à l'aide d'un rapport de mesure précoce (emr)
WO2025199805A1 (fr) Mesure lte inter-rat sans intervalle de mesure
WO2025231663A1 (fr) Rrm, rlm et bfd dans une adaptation de ssb
WO2025179534A1 (fr) Améliorations d'ai/ml centrées sur l'ue pour ltm
WO2025231658A1 (fr) Informations d'assistance pour modèle ia/ml pour positionnement
WO2025174705A1 (fr) Configuration de format de créneau pour fonctionnement en duplex intégral de sous-bande (sbfd)
US20250365589A1 (en) Near Real Time Wireless Network Outage Detection
WO2025231755A1 (fr) Amélioration de restriction de planification pour commutation de satellite douce sans changement de pci
WO2025231660A1 (fr) Minimisation des tests mobiles (mdt) pour collecte de données d'entraînement d'intelligence artificielle (ai)
WO2025174748A1 (fr) Enregistrement de double orientation
WO2025065456A1 (fr) Amélioration de réseau d'intelligence artificielle (ia) avec des liaisons entre homologues

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

Country of ref document: EP

Kind code of ref document: A1