[go: up one dir, main page]

WO2025231656A1 - Conception commune pour deux types de complexité de dispositifs de l'ido ambiant - Google Patents

Conception commune pour deux types de complexité de dispositifs de l'ido ambiant

Info

Publication number
WO2025231656A1
WO2025231656A1 PCT/CN2024/091713 CN2024091713W WO2025231656A1 WO 2025231656 A1 WO2025231656 A1 WO 2025231656A1 CN 2024091713 W CN2024091713 W CN 2024091713W WO 2025231656 A1 WO2025231656 A1 WO 2025231656A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
iot device
iot
control
layer
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/091713
Other languages
English (en)
Inventor
Peng Cheng
Alexander Sirotkin
Haijing Hu
Naveen Kumar R Palle VENKATA
Fangli Xu
Ping-Heng Kuo
Ralf ROSSBACH
Yuqin Chen
Zhibin Wu
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/091713 priority Critical patent/WO2025231656A1/fr
Publication of WO2025231656A1 publication Critical patent/WO2025231656A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for using an Ambient Internet of Things (IoT) device in a cellular communications network.
  • IoT Ambient Internet of Things
  • Ambient Internet of Things is a new device type which operates on energy harvested from the environment, such as electromagnetic, solar, thermal, or pressure sources.
  • Ambient IoT e.g., A-IoT
  • Ambient IoT devices are designed to be inexpensive, small form factor, and consume very low power, positioning them in the lowest segment of IoT device categories in terms of cost, complexity, and power consumption, well below Narrowband IoT (NB-IoT) and enhanced Machine-Type Communication (eMTC) devices.
  • NB-IoT Narrowband IoT
  • eMTC enhanced Machine-Type Communication
  • A-IoT devices eliminate the need for battery replacements, which significantly reduces maintenance efforts and associated costs.
  • the cost-effectiveness of A-IoT technology enables the connection of a vast number of devices to a network, making it an attractive solution for large-scale implementations.
  • the combination of low cost, compact size, and battery-free operation makes A-IoT devices particularly well-suited for these use cases, offering a practical and efficient solution for a wide range of industries.
  • Ambient IoT technology The key motivations behind the development of Ambient IoT technology include reducing or removing the effort and cost associated with battery replacement and maintenance, enabling deployment in use cases where frequent human access is difficult or costly and allowing large numbers of devices to be connected to a network due to their low cost. Ambient IoT devices are particularly well-suited for applications such as asset tracking and monitoring in supply chain scenarios, including manufacturing, shipping, and warehousing.
  • Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for a ambient Internet of Things (A-IoT) device configured for communicating in a wireless communication network, comprising: one or more processors, coupled to a memory, configured to: communicate with a wireless device or wireless network via a low medium access control (L-MAC) configured for a basic functionality set sufficient to control the A-IoT device without any other protocols in a protocol stack; wherein the L-MAC is configured to communicate with an upper medium access control (U-MAC) layer configured for supporting advanced functionality when the U-MAC is installed on the A-IoT, and wherein the L-MAC supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) .
  • A-IoT ambient Internet of Things
  • L-MAC low medium access control
  • A-IoT ambient Internet of Things
  • the L-MAC comprising one or more processors, coupled to a memory, configured to: communicate with a wireless device or wireless network on a low complexity A-IoT device using a basic functionality set sufficient to control the A-IoT device without any other protocols in a protocol stack; and communicate with the wireless device or the wireless network on a higher complexity A-IoT device, relative to the low complexity A-IOT device, via the L-MAC coupled to an upper medium access control (U-MAC) layer configured for supporting advanced functionality; wherein the L-MAC supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) .
  • SDU Service Data Unit
  • CE selected number of control elements
  • PDU control plane protocol data units
  • a base station comprising: one or more processors, coupled to a memory, configured to: communicate with an ambient Internet of Things (A-IoT) device via one or more of: a low medium access control (L-MAC) layer configured for a basic functionality set sufficient to control the A-IoT device, wherein the L-MAC layer of the A-IoT supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) , and wherein the L-MAC layer can be used to control a low complexity A-IoT device without any other protocols in a protocol stack; and an upper medium access control (U-MAC) layer configured for supporting advanced functionality when the U-MAC is installed on the A-IoT.
  • A-IoT ambient Internet of Things
  • L-MAC low medium access control
  • U-MAC upper medium access control
  • 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. 1 B 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 an example of a control plane protocol stack in accordance with some embodiments.
  • FIG. 9 illustrates an example of a user plane protocol stack in accordance with some embodiments.
  • FIG. 10A illustrates an example topology of ambient internet of things (A-IoT) devices communicating with a base station and a user equipment (UE) .
  • A-IoT ambient internet of things
  • UE user equipment
  • FIG. 10B illustrates an example topology of ambient internet of things (A-IoT) devices with downlink assistance.
  • A-IoT ambient internet of things
  • FIG. 10C illustrates an example topology of ambient internet of things (A-IoT) devices with uplink assistance.
  • A-IoT ambient internet of things
  • FIG. 10D illustrates an example topology of ambient internet of things (A-IoT) devices communicates bidirectionally with a user equipment (UE) .
  • A-IoT ambient internet of things
  • UE user equipment
  • FIG. 11A illustrates an example illustration of low-end ambient internet of things (A-IoT) device and high-end ambient internet of things (A-IoT) device.
  • A-IoT low-end ambient internet of things
  • A-IoT high-end ambient internet of things
  • FIG. 11 B illustrates an example illustration of a dedicated control plane protocol for a high-end ambient internet of things (A-IoT) device.
  • A-IoT ambient internet of things
  • FIG. 12 illustrates an example illustration of a wireless communication system for enhancing Secondary Cell (SCell) activation with Early Measurement Results (EMR) in accordance with some embodiments.
  • SCell Secondary Cell
  • EMR Early Measurement Results
  • 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, a cellular network device, an Internet of Things (Iot) reader, or an IoT device such as, for example, and Ambient IoT 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.
  • a processor in an Ambient IoT device can comprise logic elements configured to receive a signal and send data such as, for example, a data packet or numeric value in response to receiving the signal.
  • 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 provides developers with a stable platform for the implementation of features at a given point and then allows 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 on June 22, 2024, 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 Releases. ” One or more embodiments of the present disclosure may be adopted in future Releases, e.g., Release 19.
  • 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 enhancing Secondary Cell (SCell) activation with Early Measurement Report (EMR) .
  • SCell Secondary Cell
  • EMR Early Measurement Report
  • the example embodiments are described with regard to communication between a reader (e.g., a base station or a UE) and a device.
  • a reader e.g., a base station or a UE
  • a base station 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 enhancing SCell activation with EMR. Therefore, the base station or UE as described herein is used to represent any appropriate type of electronic component.
  • the example embodiments are also described with regard to a fifth generation (5G) New Radio (NR) network that may configure a UE to control the UE side for enhancing Secondary Cell (SCell) activation with Early Measurement Report (EMR) .
  • 5G fifth generation
  • NR New Radio
  • SCell Secondary Cell
  • EMR Early Measurement Report
  • reference to a 5G NR network is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any appropriate type of network.
  • the mechanisms of the illustrated embodiments provide a low medium access control (L-MAC) configured for an ambient Internet of Things (A-IoT) device, the L-MAC comprising one or more processors, coupled to a memory, configured to: communicate with a network on a low complexity A-IoT device using a basic functionality set sufficient to control the A-IoT device; and communicate with the network on a higher complexity A-IoT device via an upper medium access control (U-MAC) layer configured for supporting advanced functionality; where the L-MAC layer supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , or one or more control plane protocol data units (PDU) , and wherein the L-MAC layer can be used to control the low complexity A-IoT device without any other protocols in a protocol stack.
  • L-MAC low medium access control
  • A-IoT ambient Internet of Things
  • 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 ‘base station’ .
  • 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 “base station” .
  • a base station may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (5GC) network.
  • EPC legacy evolved packet core
  • NR NR core
  • a base station 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 base stations.
  • 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 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 FIGs. 1A, 1B 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 “base station” .
  • base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (5GC) network.
  • EPC legacy evolved packet core
  • NR core NR core
  • a new radio core (NR core) is also called a fifth-generation core network (5GC network) .
  • 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 base stations.
  • 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.
  • a base station may be configured to operate as a 3GPP device sending and receiving 3GPP signals.
  • the base station can be configured to operate as a reader capable of sending signaling such as, for example, a carrier wave configured to activate the A-IoT device and sending and receiving Internet of Things (IoT) data with the A-IoT device.
  • signaling such as, for example, a carrier wave configured to activate the A-IoT device and sending and receiving Internet of Things (IoT) data with the A-IoT device.
  • IoT Internet of Things
  • 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 (5GC) network.
  • EPC legacy evolved packet core
  • 5GC 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 User Equipment
  • 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 supports 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.
  • a UE may be configured to operate as a 3GPP device sending and receiving 3GPP signals.
  • the UE can be configured to operate as an A-IoT reader capable of sending signaling such as, for example, a carrier wave configured to activate the A-IoT device and sending and receiving Internet of Things (IoT) data with the A-IoT device.
  • signaling such as, for example, a carrier wave configured to activate the A-IoT device and sending and receiving Internet of Things (IoT) data with the A-IoT device.
  • IoT Internet of Things
  • 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 535.
  • RF front end 535 may include circuitry for transmitting and receiving radio signals.
  • RF front end 535 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, 535, 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 102A.
  • 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 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 base station, or decode a message received between a UE and a base station.
  • 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 Control Plane Protocol Stack
  • FIG. 8 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 800 is shown as a communications protocol stack between the UE 106a (or alternatively, the UE 106b) , the RAN node 102A (or alternatively, the RAN node 102B) , and the mobility management entity (MME) 621.
  • MME mobility management entity
  • the PHY layer 801 may transmit or receive information used by the MAC layer 802 over one or more air interfaces.
  • the PHY layer 801 may further perform link adaptation or adaptive modulation and coding (AMC) , power control, cell search (e.g., for initial synchronization and handover purposes) , and other measurements used by higher layers, such as the RRC layer 805.
  • AMC link adaptation or adaptive modulation and coding
  • the PHY layer 801 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer 802 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) , and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • the RLC layer 803 may operate in a plurality of modes of operation, including: Transparent Mode (TM) , Unacknowledged Mode (UM) , and Acknowledged Mode (AM) .
  • the RLC layer 803 may execute transfer of upper layer protocol data units (PDUs) , error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • PDUs protocol data units
  • ARQ automatic repeat request
  • the RLC layer 803 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • the PDCP layer 804 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs) , perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc. ) .
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer 805 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS) ) , broadcast of system information related to the access stratum (AS) , paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • SIBs may comprise one or more information elements (IEs) , which may each comprise individual data fields or data structures.
  • the UE 106a and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 801, the MAC layer 802, the RLC layer 803, the PDCP layer 804, and the RRC layer 805.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 806 form the highest stratum of the control plane between the UE 601 and the MME 621.
  • the NAS protocols 806 support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.
  • the S1 Application Protocol (S1-AP) layer 815 may support the functions of the S1 interface and comprise Elementary Procedures (EPs) .
  • An EP is a unit of interaction between the RAN node 102A and the CN 100.
  • the S1-AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM) , and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 814 may ensure reliable delivery of signaling messages between the RAN node 102A and the MME 621 based, in part, on the IP protocol, supported by the IP layer 813.
  • the L2 layer 812 and the L1 layer 811 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 102A and the MME 621 may utilize an S1-MME interface to exchange control plane data via a protocol stack comprising the L1 layer 811, the L2 layer 812, the IP layer 813, the SCTP layer 814, and the S1-AP layer 815.
  • Wireless communication systems provide mobility by enabling user equipment (UEs) to move between cells via a process referred to as handover.
  • Handover occurs when a mobile UE switches from one cell to another neighboring cell.
  • Mechanisms have been established to help ensure a smooth transition between cells.
  • NR supports different types of handover that were not supported in the previous 4G LTE specification.
  • the basic handover in NR has been based on LTE handover mechanisms in which the network controls UE mobility based on UE measurement reporting. This measurement reporting typically involves Layer 3 (L3) measurements of neighbor cells and reporting from the UE to the eNB.
  • L3 Layer 3
  • RLF radio link failure
  • UE user equipment
  • RLF refers to cases where the radio link quality deteriorates below certain thresholds such that communication between a user equipment (UE) and serving base station is disrupted.
  • the current RLF procedure has some limitations in that it reacts to failures only after they have already occurred, rather than proactively avoiding them.
  • the procedure also relies on a limited set of reference signal measurements that may not fully capture emerging radio link problems. Additionally, downlink signals and uplink signals are assessed independently even though they are often correlated in indicating radio link conditions.
  • FIG. 9 User Plane Protocol Stack
  • FIG. 9 is an illustration of an example of a user plane protocol stack in accordance with some embodiments.
  • a user plane 900 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B or 106N) , the RAN node 102A (or alternatively, the RAN node 102B) , the S-GW 622, and the P-GW 623.
  • the user plane 900 may utilize at least some of the same protocol layers as the control plane 800.
  • the UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 801, the MAC layer 802, the RLC layer 803, the PDCP layer 804.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 904 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 903 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 102A and the S-GW 622 may utilize an S1-U interface to exchange user plane data via a protocol stack comprising the L1 layer 811, the L2 layer 812, the UDP/IP layer 903, and the GTP-U layer 904.
  • the S-GW 622 and the P-GW 623 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 811, the L2 layer 812, the UDP/IP layer 903, and the GTP-U layer 904.
  • NAS protocols support the mobility of the UE 106 and the session management procedures to establish and maintain IP 813 connectivity between the UE 106 and the P-GW 623.
  • FIG. 10A-10D Various topologies of Ambient Internet of Things (A-IoT) devices
  • Ambient Internet of Things is a new device type which operates on energy harvested from the environment, such as electromagnetic, solar, thermal, or pressure sources.
  • Ambient IoT e.g., A-IoT
  • Ambient IoT devices are designed to be inexpensive, small form factor, and consume very low power, positioning them in the lowest segment of IoT device categories in terms of cost, complexity, and power consumption, well below Narrowband IoT (NB-IoT) and enhanced Machine-Type Communication (eMTC) devices.
  • NB-IoT Narrowband IoT
  • eMTC enhanced Machine-Type Communication
  • A-IoT devices eliminate the need for battery replacements, which significantly reduces maintenance efforts and associated costs.
  • the cost-effectiveness of A-IoT technology enables the connection of a vast number of devices to a network, making it an attractive solution for large-scale implementations.
  • the combination of low cost, compact size, and battery-free operation makes A-IoT devices particularly well-suited for these use cases, offering a practical and efficient solution for a wide range of industries.
  • Ambient IoT technology The key motivations behind the development of Ambient IoT technology include reducing or removing the effort and cost associated with battery replacement and maintenance, enabling deployment in use cases where frequent human access is difficult or costly and allowing large numbers of devices to be connected to a network due to their low cost. Ambient IoT devices are particularly well-suited for applications such as asset tracking and monitoring in supply chain scenarios, including manufacturing, shipping, and warehousing.
  • Ambient IoT technology encompasses both passive backscattering devices and active devices with energy harvesting and storage capabilities.
  • Backscattering devices communicate by modulating and reflecting incident radio frequency (RF) signals, without generating their own RF energy. This allows for extremely low power consumption but typically limits the communication range.
  • active devices with energy storage can generate their own RF signals, enabling longer communication ranges and better quality of service at the cost of slightly higher power consumption.
  • energy harvesting plays a crucial role in enabling ambient IoT technology, with various energy sources such as RF signals, solar, vibration, and thermal being available.
  • these sources differ in terms of their availability and energy density.
  • RF signals have a low energy density and require longer charging times, they can be directly controlled by a wireless network, making them a suitable choice for ambient IoT.
  • the use of RF signals as an energy source significantly impacts the system design and operation of ambient IoT, necessitating the 5G system to provide both communication and energy signals to support ambient IoT devices.
  • Other energy sources can be opportunistically harvested based on their availability, with minimal impact on the 5G system design.
  • the energy harvesting process can be achieved through various means, such as RF-Direct Current converters, photovoltaic cells, thermoelectric devices, or piezoelectric harvesters, with the harvested energy being stored in capacitors, the size of which depends on the device type.
  • the harvested energy may be stored in chemical storage devices such as batteries. Alternatively, the harvested energy may be stored in physical devices such as capacitors.
  • Backscattering a technique widely used in RFID, allows a device to communicate with a network by reflecting and modulating the incident waves with the information to be transmitted.
  • the device can be powered by either the incident RF signal (e.g. a carrier signal) or stored energy.
  • the incident RF signal e.g. a carrier signal
  • the active signal generation method employs traditional active RF components to generate signals, offering benefits such as improved coverage and the ability to perform more complex operations, increasing the likelihood of leveraging the existing functionality of 5G networks.
  • A-IoT Ambient Internet of Things
  • 3GPP Third Generation Partnership Project
  • RFID Radio Frequency Identification
  • 3GPP Release 18 has defined two device topologies, with different levels of complexity.
  • Device type 1 is defined as devices with a peak power consumption of approximately ⁇ 1 microWatt ( ⁇ W) , energy storage, an initial sampling frequency offset (SFO) of up to 10X ppm, and no downlink or uplink amplification. These devices'uplink transmission is backscattered on an externally provided carrier wave.
  • Device types 2a/2b are devices with a peak power consumption of less than ( ⁇ ) a few hundred ⁇ W, energy storage, an initial SFO up to 10X ppm, and both downlink and/or uplink amplification. These devices' uplink transmission may be either generated internally or backscattered on an externally provided carrier wave.
  • a base station e.g., gNB
  • A-IoT devices there are three types of traffic for A-IoT devices: 1) Device-Terminated (DT) : e.g., command use case, 2) Device Originated-DT Triggered (DO-DTT) : e.g., inventory use case, and 3) Device Originated-Autonomous (DO-A) : e.g., sensor use case.
  • DT Device-Terminated
  • DO-DTT Device Originated-DT Triggered
  • DO-A Device Originated-Autonomous
  • the coverage design target for A-IoT devices may be a maximum distance of 10-50 meters for indoor devices, with the exact range to be determined by the working groups (WGs) .
  • WGs working groups
  • Topologies 1 and 2 as illustrated in FIG. 10A, where a user equipment (UE) acts as an intermediate node under network control, there are no Radio Resource Control (RRC) states, mobility (i.e., no cell selection/re-selection-like function) , Hybrid Automatic Repeat Request (HARQ) , or Automatic Repeat Request (ARQ) .
  • RRC Radio Resource Control
  • HARQ Hybrid Automatic Repeat Request
  • ARQ Automatic Repeat Request
  • topology 1 e.g., an indoor micro-cell/co-site
  • the Ambient IoT device 1002 directly and bidirectionally communicates with a base station (BS) 102 communicating Ambient IoT data signal.
  • the communication between the base station 102 and the ambient IoT device 1001 includes Ambient IoT data and/or signaling.
  • This topology includes the possibility that the BS 102 transmitting to the Ambient IoT device 1001 is a different from the BS 102 receiving from the Ambient IoT device 1001.
  • a UE 1004 functions as intermediate node, under network control.
  • the intermediate node may be indoor.
  • the Ambient IoT device 1002 communicates bidirectionally with an intermediate node such as, for example, the UE 1004 between the Ambient IoT device 1002 and base station 102.
  • the intermediate node can be a relay, integrated access and backhaul (IAB) node, UE, repeater, etc. which is capable of Ambient IoT communication.
  • the intermediate node transfers Ambient IoT data and/or signaling between the BS 102 and the Ambient IoT device 1002.
  • Topology 3 is depicted with downlink assistance illustrated in FIG. 10B and uplink assistance illustrated in FIG. 10C.
  • the Ambient IoT device 1006 transmits data/signaling to a base station 102 and receives data/signaling from the assisting node such as, for example, the UE 1004.
  • the Ambient IoT device 1008 receives data/signaling from a base station 102 and transmits data/signaling to the assisting node 1004 such as, for example, the UE 106.
  • the assisting node 1004 can be a relay, IAB, UE, repeater, etc. which is capable of ambient IoT.
  • the BS 102 can communicate 3GPP signals via a Uu connection with the assisting node 1004.
  • the assisting node 1004 can then communicate Ambient IoT data/signaling to the Ambient IoT device 1006 and 3GPP configured uplink and downlink data to the BS 102.
  • the Ambient IoT device 1006 can communicate Ambient IoT data/signaling to the BS 102 and the assisting node 1004, as shown in FIG. 10B (showing downlink assistance) and 10C (showing uplink assistance) .
  • Topology 4 is depicted in FIG. 10D where the Ambient IoT device 1008 communicates bidirectionally with a UE 1004.
  • the UE 1004 is configured to operate as a reader.
  • a reader is configured to send and receive Ambient IoT data/signaling.
  • the UE 1004 can send a carrier wave to activate the Ambient IoT device 1008.
  • the Ambient IoT device 1008 can send Ambient IoT data/signaling to the UE 1004 in response to receiving the carrier wave.
  • the communication between UE 1004 and the ambient IoT device 1008 includes Ambient IoT data and/or signaling.
  • a base station and a UE may be configured to operate as a 3GPP device sending and receiving 3GPP signals.
  • the base station and the UE can be configured to operate as a reader capable of sending signaling such as, for example, a carrier wave configured to activate the A-IoT device and sending and receiving Internet of Things (IoT) data with the A-IoT device.
  • signaling such as, for example, a carrier wave configured to activate the A-IoT device and sending and receiving Internet of Things (IoT) data with the A-IoT device.
  • IoT Internet of Things
  • an ambient Internet of Things (A-IoT) device configured for communicating in a wireless communication network, comprising: one or more processors, coupled to a memory, configured to: communicate with a wireless device or wireless network via a low medium access control (L-MAC) configured for a basic functionality set sufficient to control the A-IoT device without any other protocols in a protocol stack; wherein the L-MAC is configured to communicate with an upper medium access control (U-MAC) layer configured for supporting advanced functionality when the U-MAC is installed on the A-IoT, and wherein the L-MAC supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) .
  • A-IoT ambient Internet of Things
  • L-MAC low medium access control
  • A-IoT ambient Internet of Things
  • the L-MAC comprising one or more processors, coupled to a memory, configured to: communicate with a wireless device or wireless network on a low complexity A-IoT device using a basic functionality set sufficient to control the A-IoT device without any other protocols in a protocol stack; and communicate with the wireless device or the wireless network on a higher complexity A-IoT device, relative to the low complexity A-IOT device, via the L-MAC coupled to an upper medium access control (U-MAC) layer configured for supporting advanced functionality; wherein the L-MAC supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) .
  • SDU Service Data Unit
  • CE selected number of control elements
  • PDU control plane protocol data units
  • a base station comprising: one or more processors, coupled to a memory, configured to: communicate with an ambient Internet of Things (A-IoT) device via one or more of: a low medium access control (L-MAC) layer configured for a basic functionality set sufficient to control the A-IoT device, wherein the L-MAC layer of the A-IoT supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) , and wherein the L-MAC layer can be used to control a low complexity A-IoT device without any other protocols in a protocol stack; and an upper medium access control (U-MAC) layer configured for supporting advanced functionality when the U-MAC is installed on the A-IoT.
  • A-IoT ambient Internet of Things
  • L-MAC low medium access control
  • U-MAC upper medium access control
  • mechanisms of the illustrated embodiments provide for a user equipment (e.g., a reader) comprising: one or more processors, coupled to a memory, configured to: communicate with an ambient Internet of Things (A-IoT) device via one or more of: a low medium access control (L-MAC) layer configured for a basic functionality set sufficient to control the A-IoT device, wherein the L-MAC layer of the A-IoT supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) , and wherein the L-MAC layer can be used to control a low complexity A-IoT device without any other protocols in a protocol stack; and an upper medium access control (U-MAC) layer configured for supporting advanced functionality when the U-MAC is installed on the A-IoT.
  • A-IoT ambient Internet of Things
  • L-MAC low medium access control
  • SDU Service Data
  • FIG. 11A-11B Example illustration of two types of ambient internet of things (A- IoT) devices
  • the mechanisms of the illustrated embodiments address the problem of catering to both the simplest design and more complex design approaches for A-IoT devices without introducing unnecessary complexity.
  • One way of providing devices with variable complexity while minimizing cost is to re-use portions of the simplest device in more complex topologies.
  • mechanisms of the illustrated embodiments provide two protocol layers: a Low Medium Access Control (L-MAC) layer and an Upper Medium Access Control (U-MAC) layer.
  • L-MAC Low Medium Access Control
  • U-MAC Upper Medium Access Control
  • FIG. 11A illustrates an example illustration of low-end ambient internet of things (A-IoT) device 1102 and a high-end ambient internet of things (A-IoT) device 1104.
  • A-IoT low-end ambient internet of things
  • A-IoT high-end ambient internet of things
  • a low-end (e.g. low complexity) A-IoT device 1102 includes an application layer and the L-MAC layer.
  • the low complexity A-IOT device 1102 can wirelessly communicate with a reader, UE, BS, or other type of wireless device without any other protocols in a protocol stack.
  • a high-end (e.g. high complexity) A-IoT device 1104 includes at least the application layer, the L-MAC layer, and the U-MAC layer.
  • the U-MAC layer can include additional protocols that are not included in the L-MAC layer.
  • the same L-MAC layer is common to both the low-end A-IoT device 1102 and the high-end A-IoT device 1104.
  • the low-end A-IoT device 1102 and the high-end A-IoT device 1104 can be differentiated by a capability or different permanent device identifier (ID) ranges. It is important to note that the protocol names (e.g., L-MAC) used in this solution are tentative and may differ in the actual implementation.
  • the L-MAC layer may support a bare minimum functionality to enable the A-IoT device 1102 to function, which may include device identifier (ID) , a fixed-length field, and a payload or Service Data Unit (SDU) .
  • ID device identifier
  • SDU Service Data Unit
  • the L-MAC is designed for the most basic functionality and does not support "advanced" features such as ciphering, integrity protection, etc. It should be noted that the advanced functionality may be adopted and implemented, but would be supported in the U-MAC layer in the high-end A-IoT device 1104 with a more complex topology than 1102.
  • the L-MAC layer is common to both low and high complexity A-IoT devices, while only high complexity A-IoT devices implement the A-IoT U-MAC layer.
  • the payload can be either a U-MAC Protocol Data Unit (PDU) in the case of a high-end A-IoT device 1104 or application data in the case of the low-end A-IoT device 1102.
  • PDU U-MAC Protocol Data Unit
  • CE MAC Control Elements
  • the L-MAC layer may support a limited number of CEs.
  • the L-MAC layer can support a limited number of control plane PDUs.
  • the L-MAC protocol can support all the control plane functions applicable to both low-end and high-end devices. Examples of "basic" control plane functions supported by the L-MAC include, but not limited to, random access and paging.
  • the L-MAC layer can be self-sufficient, meaning it can be used to control the A-IoT device 1102 without any other protocols in the protocol stack.
  • the U-MAC layer is supported only by the high-end A-IoT device 1104 and may include functionalities such as ciphering, integrity protection, sequence numbers, segmentation and reassembly (such as in uplink only) , and Quality of Service (QoS) .
  • the U-MAC layer's payload/SDU can be application data.
  • the U-MAC layer may also support CE or control PDUs for "advanced" control plane functionality if the control plane is realized through CEs.
  • advanced control features may be supported in the L-MAC layer but only for high-end devices. Examples of "advanced" control functions include, but are not limited to, timing advance, Discontinuous Reception (DRX) , and capability transfer (if Radio Resource Control (RRC) is not supported) .
  • DRX Discontinuous Reception
  • RRC Radio Resource Control
  • the low-end A-IoT device 1102 and the high-end A-IoT device 1104 are depicted, where the high-end A-IoT device 1104 is depicted as having a more complex control plane.
  • the high-end A-IoT device 1104 includes a dedicated Radio Resource Control (RRC) protocol (e.g., a protocol that functions similarly to an "RRC" protocol) .
  • RRC Radio Resource Control
  • such a dedicated RRC protocol may be supported by the high-end A-IoT device 1104 and can be transferred on top of the U-MAC, either as a special control PDU or as a data PDU.
  • the U-MAC layer treats the RRC-like protocol and the application layer SDU identically.
  • the RRC-like protocol can also be transferred together with U-MAC control PDUs and/or CEs. Examples of dedicated RRC protocol functions include, but are not limited to, capability transfer and DRX configuration.
  • the high end A-IOT device illustrated in FIG. 11 B can also include a protocol similar to an RRC protocol.
  • the complex control plane solution illustrated in 1102 and 1104 of FIG. 11 B provides a flexible approach that caters to both the simplest (e.g., low-end A-IoT device 1102) and the more complex design (e.g., the high-end A-IoT device 1104) preferences by using a layered protocol stack.
  • the L-MAC layer ensures basic functionality for all A-IoT devices, while the U-MAC layer allows for the inclusion of advanced features in high complexity devices (e.g., the high-end A-IoT device 1104) without burdening low complexity devices (e.g., low-end A-IoT device 1102) with unnecessary complexity.
  • the optional RRC-like protocol further extends the flexibility for high-end devices that require even more control plane complexity.
  • Low-end A-IoT devices may be configured to support only one type of device identifier (ID) , which may be a global ID similar to an Electronic Product Code (EPC) .
  • ID device identifier
  • high-end A-IoT devices e.g., the high-end A-IoT device 1104 may support both a global ID and a temporary ID, which can be used for privacy protection. The temporary ID allocation functionality would be realized in the U-MAC layer.
  • the L-MAC layer is configured and designed to carry either a permanent/global ID for low-end devices or a temporary ID for high-end devices, which may have different lengths.
  • One solution to accommodate this difference is to include a 1-bit indication in the L-MAC header of the L-MAC, specifying the type of ID used (global or temporary) or in the specific ID (global ID or local ID) . This indication can be used to derive the ID length.
  • the ID ranges may be split with one range dedicated to low-end devices and another range for high-end devices.
  • the same field in the protocol can then be used for both ID types.
  • the first bit of the ID may be used to indicate the device type (low-end or high-end) .
  • the global ID can be stored in a Universal Integrated Circuit Card (UICC) for high-end devices or in the device's read-only memory for low-end devices.
  • UICC Universal Integrated Circuit Card
  • the mechanisms of the illustrated embodiments provide three alternatives for capability signaling in the low-end A-IoT device 1102 and the high-end A-IoT device 1104.
  • the first alternative only the device type (high-end A-IoT device 1104) is signaled, and all other capabilities, such as support for U-MAC, are derived from the device type.
  • the second alternative is a slightly different variant, where even the device type is not required to be explicitly signaled. Instead, the device ID space may be split, with one range indicating low-end devices and another range indicating high-end devices.
  • the third alternative allows an ambient IoT device to individually signal support for U-MAC and specific high-end U-MAC functions, such as ciphering. This can be realized, for example, through a capabilities L-MAC Control Element (CE) or control Protocol Data Unit (PDU) that includes a bitmap, with each bit corresponding to a specific feature.
  • CE capabilities L-MAC Control Element
  • PDU Protocol Data Unit
  • an ambient IoT device may support both L-MAC and U-MAC layers, but the usage of the U-MAC layer may be dynamically configured or activated.
  • the U-MAC layer can be activated or configured based on various factors, such as network configuration, application preference, packet characteristics, or energy storage status.
  • the usage of the "RRC" protocol may be activated in a comparable manner to the U-MAC layer.
  • one embodiment allows for the definition of more than two device types, with each type supporting a specific combination of the protocols described in this solution.
  • a device type may support L-MAC + U-MAC, L-MAC + RRC, or L-MAC + U-MAC + RRC.
  • FIG. 12 Flow Chart for a Method of using two complex types of Ambient IoT devices.
  • FIG. 12 illustrates an example flow chart of a method 1200 of using two complexity types of Ambient IoT devices in a wireless communication system, according to some embodiments.
  • the method shown in FIG. 12 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, 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 1200 for using two complexity types of Ambient IoT devices in a wireless communication system, comprises communicating with a wireless device or wireless network on a low complexity A-IoT device using a basic functionality set sufficient to control the A-IoT device without any other protocols in a protocol stack, wherein the L-MAC supports one or more of a device identifier, a length field, a payload, Service Data Unit (SDU) , a selected number of control elements (CE) , and one or more control plane protocol data units (PDU) , as in block 1210.
  • SDU Service Data Unit
  • CE control elements
  • PDU control plane protocol data units
  • the method 1200 further comprises communicating with the network on a higher complexity A-IoT device, relative to the low complexity A-IOT device, via the L-MAC coupled to an upper medium access control (U-MAC) layer configured for supporting advanced functionality, as in block, 1220.
  • U-MAC medium access control
  • the L-MAC supports control plane functionality.
  • the control plane functionality is implemented using MAC control elements (CEs) , and wherein the L-MAC supports a limited number of CEs.
  • CEs MAC control elements
  • control plane functionality is implemented using MAC control PDUs, and wherein the L-MAC layer supports a limited number of control plane PDUs.
  • control plane functionality is implemented using one or more of MAC CEs and the MAC control PDUs, and wherein the L-MAC layer supports all control plane functions applicable to both the low complexity and higher complexity A-IoT devices.
  • the basic functionality set supported by the L-MAC layer includes random access and paging.
  • one or more of the payload and the SDU of the L-MAC comprises application data.
  • one or more of the payload and the SDU of the L-MAC comprises an upper medium access control (U-MAC) layer for supporting the advanced functionality.
  • U-MAC medium access control
  • the U-MAC layer supports one or more of ciphering, integrity protection, sequence numbers, segmentation and reassembly, and quality of service (QoS) .
  • QoS quality of service
  • the U-MAC layer supports advanced control plane functionality through one or more of CEs or the one or more control PDUs.
  • the advanced control plane functionality supported by the U-MAC layer includes one or more of timing advance, discontinuous reception (DRX) , and capability transfer.
  • DRX discontinuous reception
  • the higher complexity A-IoT device further comprises a dedicated radio resource control (RRC) protocol layer.
  • RRC radio resource control
  • the RRC protocol layer supports functions including one or more of capability transfer and DRX configuration.
  • the device identifier supported by the L-MAC layer is a global identifier for the low complexity A-IoT device.
  • the device identifier supported by the L-MAC layer is a temporary identifier for the higher complexity A-IoT device, wherein the U-MAC layer supports temporary identifier allocation functionality.
  • the L-MAC layer uses a 1-bit indication to indicate a type of device identifier or length of the device identifier.
  • those of a plurality of device identifiers having a similar device identifier length are split into separate ranges to indicate use for the low complexity A-IoT device and the high complexity A-IoT devices.
  • the device identifier supported by the L-MAC layer is a global identifier, wherein the global identifier is stored in a universal integrated circuit card (UICC) .
  • UICC universal integrated circuit card
  • the L-MAC layer is configured to determine the device type of the ambient IoT device.
  • support for the U-MAC layer and other device capabilities are derived from the device type of the A-IoT device.
  • one or more of the low complexity A-IoT device and the higher complexity A-IoT device signals support for the U-MAC layer and advanced U-MAC functions using a capabilities CE or control PDU with a bitmap for each supported feature.
  • usage of the U-MAC layer is one or more of dynamically configured and activated based on one or more of a network configuration, application preference, packet characteristics, and energy storage status.
  • usage of the RRC protocol layer is dynamically activated.
  • the A-IoT device may have a peak power consumption of approximately 1 ⁇ W, has energy storage, an initial sampling frequency offset (SFO) up to 10X parts-per-million (ppm) , and does not have downlink or uplink amplification.
  • SFO initial sampling frequency offset
  • the A-IoT device performs uplink transmissions using backscattering on a carrier wave provided externally.
  • the A-IoT device has a peak power consumption less than or equal to a few hundred microwatts ( ⁇ W) , has energy storage, an initial SFO up to 10X ppm, and has downlink and/or uplink amplification.
  • ⁇ W microwatts
  • the A-IoT device performs uplink transmissions by generating the uplink transmissions internally.
  • the A-IoT device performs uplink transmissions using backscattering on a carrier wave provided externally.
  • the A-IoT device has a maximum communication range of 10-50 meters when located indoors.
  • the A-IoT device communicates directly with a base station, and wherein the base station is a micro-cell.
  • the A-IoT device communicates with a base station via an intermediate node under network control, wherein the base station is a macro-cell, and wherein the intermediate node is located indoors.
  • communication with the A-IoT device is performed without radio resource control (RRC) states, mobility operations, hybrid automatic repeat request (HARQ) , or automatic repeat request (ARQ) .
  • RRC radio resource control
  • HARQ hybrid automatic repeat request
  • ARQ automatic repeat request
  • an apparatus is disclosed that is configured to cause a base station to assist with performing any of the operations of the method 1200.
  • an apparatus is disclosed that is configured to cause a user equipment (UE) to assist with performing any of the operations of the method 1200.
  • UE user equipment
  • a computer program product comprising computer instructions which, when executed by one or more processors, perform any of the operations described with respect to the method 1200.
  • a computer program product comprising computer instructions which, when executed by one or more processors, perform any of the operations described with respect to the method 1200.
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une commande d'accès au support faible (L-MAC) configurée pour un dispositif de l'Internet des objets ambiant (IdO-A) en vue d'une communication dans un réseau de communication sans fil par un équipement utilisateur (UE). La L-MAC comprend un ou plusieurs processeurs, couplés à une mémoire et configurés pour : communiquer avec un dispositif sans fil ou un réseau sans fil sur un dispositif IdO-A de faible complexité à l'aide d'un ensemble de fonctionnalités de base suffisant pour commander le dispositif IdO-A sans aucun autre protocole dans une pile de protocoles ; et communiquer avec le dispositif sans fil ou le réseau sans fil sur un dispositif IdO-A de complexité supérieure, par rapport au dispositif IdO-A de faible complexité, par l'intermédiaire de la L-MAC couplée à une couche de commande d'accès au support supérieure (U-MAC) configurée pour prendre en charge une fonctionnalité avancée. La L-MAC prend en charge un ou plusieurs éléments parmi un identifiant de dispositif, un champ de longueur, une charge utile, une unité de données de service (SDU), un nombre sélectionné d'éléments de commande (CE) et une ou plusieurs unités de données de protocole de plan de commande (PDU).
PCT/CN2024/091713 2024-05-08 2024-05-08 Conception commune pour deux types de complexité de dispositifs de l'ido ambiant Pending WO2025231656A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/091713 WO2025231656A1 (fr) 2024-05-08 2024-05-08 Conception commune pour deux types de complexité de dispositifs de l'ido ambiant

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/091713 WO2025231656A1 (fr) 2024-05-08 2024-05-08 Conception commune pour deux types de complexité de dispositifs de l'ido ambiant

Publications (1)

Publication Number Publication Date
WO2025231656A1 true WO2025231656A1 (fr) 2025-11-13

Family

ID=97674261

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/091713 Pending WO2025231656A1 (fr) 2024-05-08 2024-05-08 Conception commune pour deux types de complexité de dispositifs de l'ido ambiant

Country Status (1)

Country Link
WO (1) WO2025231656A1 (fr)

Similar Documents

Publication Publication Date Title
US10812169B2 (en) User equipment measurements for new radio
CN107258107A (zh) 用于支持扩展非连续接收机制的移动性管理实体、用户设备和方法
US20190373497A1 (en) Measurement gap configuration for new radio (nr) systems
EP3596999A1 (fr) Retransmission de pdu pdcp par des noeuds centralisés d'une architecture ran
EP3626016B1 (fr) Procédé et appareil de surveillance de liaison radio
WO2017123288A1 (fr) Techniques de coexistence de technologies d'accès radio
WO2018031649A1 (fr) Accès à des technologies existantes au moyen d'un équipement utilisateur
WO2025231656A1 (fr) Conception commune pour deux types de complexité de dispositifs de l'ido ambiant
WO2025208463A1 (fr) Rrm basé sur une lp-wur en mode edrx de veille et inactif
WO2025199933A1 (fr) Prédiction de défaillance de transfert (ho)/défaillance de liaison radio (rlf) basée sur l'intelligence artificielle
WO2025208420A1 (fr) Prédiction de mesure de modèle basée sur l'intelligence artificielle côté réseau
WO2025208462A1 (fr) Validation d'inférence de modèle basée sur l'intelligence artificielle côté réseau
WO2025112009A1 (fr) Appareil et procédé de configuration pf/po en grappe et de transmission pei pour l'économie d'énergie du réseau
WO2025030430A1 (fr) Signalisation et capacité d'agrégation de porteuses sans ssb inter-bandes
WO2025171549A1 (fr) Procédés d'adaptation de ressources pour signal de synchronisation et signaux prach dans une communication sans fil
WO2025091266A1 (fr) Conception cssf pour opération scell sans ssb
WO2025111920A1 (fr) Configuration pour signal de réveil d'ue déclenchant une transmission et une surveillance de sib1
WO2025171562A1 (fr) Procédés pour la transmission de signaux de diffusion et la gestion de cellules dans des communications sans fil
WO2025065252A1 (fr) Application d'un support conjoint de nfg et de ncsg
WO2025111950A1 (fr) Prédiction de défaillance de liaison radio basée sur l'ia/ml
WO2025065210A1 (fr) Mesures rrm pour ue prenant en charge une bwp sans restriction
WO2025208436A1 (fr) Optimisation d'utilisation de chercheur pour mesure ca/cc
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
WO2025179534A1 (fr) Améliorations d'ai/ml centrées sur l'ue pour ltm