[go: up one dir, main page]

WO2024168666A1 - Procédés de fonctionnement inactif edrx étendu - Google Patents

Procédés de fonctionnement inactif edrx étendu Download PDF

Info

Publication number
WO2024168666A1
WO2024168666A1 PCT/CN2023/076403 CN2023076403W WO2024168666A1 WO 2024168666 A1 WO2024168666 A1 WO 2024168666A1 CN 2023076403 W CN2023076403 W CN 2023076403W WO 2024168666 A1 WO2024168666 A1 WO 2024168666A1
Authority
WO
WIPO (PCT)
Prior art keywords
edrx
inactive state
extended
rrc inactive
ran
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/CN2023/076403
Other languages
English (en)
Inventor
Naveen Kumar R. PALLE VENKATA
Yuqin Chen
Haijing Hu
Sudeep Manithara Vamanan
Fangli Xu
Zhibin Wu
Ping-Heng Kuo
Ralf ROSSBACH
Behrouz Aghili
Vivek G. Gupta
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 CN202380094215.1A priority Critical patent/CN120712841A/zh
Priority to PCT/CN2023/076403 priority patent/WO2024168666A1/fr
Publication of WO2024168666A1 publication Critical patent/WO2024168666A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication

Definitions

  • the invention relates to wireless communications, and more particularly to apparatuses, systems, and methods for extended (e.g., greater than 10.24 seconds) enhanced discontinuous reception cycle (eDRX) operation, e.g., in cellular systems, such as LTE systems, 5G NR systems, and beyond.
  • extended e.g., greater than 10.24 seconds
  • eDRX enhanced discontinuous reception cycle
  • Wireless communication systems are rapidly growing in usage.
  • wireless devices such as smart phones, wearable devices or accessory devices
  • tablet computers have become increasingly sophisticated.
  • mobile devices In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS) , and are capable of operating sophisticated applications that utilize these functionalities.
  • GPS global positioning system
  • LTE Long Term Evolution
  • 5G NR Fifth Generation New Radio
  • 5G-NR also simply referred to as NR
  • NR provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption.
  • NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.
  • Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for extended (e.g., greater than 10.24 seconds) enhanced discontinuous reception cycle (eDRX) operation, e.g., in 5G NR systems and beyond.
  • extended e.g., greater than 10.24 seconds
  • eDRX enhanced discontinuous reception cycle
  • a UE may be configured to indicate support for extended eDRX while in RRC inactive state (e.g., an eDRX cycle greater than 10.24 seconds) to at least one of a radio access network (RAN) , e.g., such as a base station of the RAN, or a core network (CN) , e.g., such as an AMF of the CN.
  • RAN radio access network
  • CN core network
  • the UE may be configured to receive from a serving cell of the RAN, a configuration for extended eDRX while in RRC inactive state.
  • the configuration for extended eDRX while in RRC inactive state may include a list of cells of the RAN that support extended eDRX while in RRC inactive state and/or an eDXR while in RRC inactive state configuration.
  • the UE may be configured to operate according to the configuration for extended eDRX while in RRC inactive state.
  • a base station may be configured to receive, from a UE, an indication of support for extended eDRX while in RRC inactive state (e.g., an eDRX cycle greater than 10.24 seconds) .
  • the indication may be received as a UE capability indication via a UE capability information message.
  • the base station may send, to the UE, a configuration for extended eDRX while in RRC inactive state.
  • the configuration for extended eDRX while in RRC inactive state may include a list of cells of the RAN that support extended eDRX while in RRC inactive state and/or an eDXR while in RRC inactive state configuration.
  • UAVs unmanned aerial vehicles
  • UACs unmanned aerial controllers
  • UTM server base stations
  • access points cellular phones
  • tablet computers wearable computing devices
  • portable media players portable media players
  • Figure 1A illustrates an example wireless communication system according to some embodiments.
  • Figure 1B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.
  • UE user equipment
  • Figure 2 illustrates an example block diagram of a base station, according to some embodiments.
  • Figure 3 illustrates an example block diagram of a server according to some embodiments.
  • Figure 4 illustrates an example block diagram of a UE according to some embodiments.
  • Figure 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.
  • Figure 6A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments.
  • 3GPP e.g., cellular
  • non-3GPP e.g., non-cellular
  • Figure 6B illustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments.
  • dual 3GPP e.g., LTE and 5G NR
  • non-3GPP access to the 5G CN
  • Figure 7 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.
  • Figure 8 illustrates UE eDRX idle state operation in 3GPP Release 17.
  • Figure 9 illustrates an example of a UE capability indication parameter, according to some embodiments.
  • Figure 10 illustrates an example of a SIB1 parameter, according to some embodiments.
  • FIGS 11 and 12 illustrate examples of SIB1 parameters, according to some embodiments.
  • Figure 13 illustrates examples of information elements, according to some embodiments.
  • FIGS 14 and 15 illustrate block diagrams of examples of methods for extended enhanced discontinuous reception cycle (eDRX) operation while in a radio resource control (RRC) inactive state, according to some embodiments.
  • eDRX extended enhanced discontinuous reception cycle
  • RRC radio resource control
  • ⁇ UE User Equipment
  • ⁇ RF Radio Frequency
  • ⁇ MAC Medium Access Control
  • ⁇ CSI-RS Channel State Information Reference Signal
  • ⁇ PDCCH Physical Downlink Control Channel
  • ⁇ PDSCH Physical Downlink Shared Channel
  • Memory Medium Any of various types of non-transitory memory devices or storage devices.
  • the term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc.
  • the memory medium may include other types of non-transitory memory as well or combinations thereof.
  • the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution.
  • the term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network.
  • the memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.
  • Carrier Medium a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • a physical transmission medium such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays) , PLDs (Programmable Logic Devices) , FPOAs (Field Programmable Object Arrays) , and CPLDs (Complex PLDs) .
  • the programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores) .
  • a programmable hardware element may also be referred to as “reconfigurable logic” .
  • Computer System any of various types of computing or processing systems, including a personal computer system (PC) , mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA) , television system, grid computing system, or other device or combinations of devices.
  • PC personal computer system
  • mainframe computer system workstation
  • network appliance Internet appliance
  • PDA personal digital assistant
  • television system grid computing system, or other device or combinations of devices.
  • computer system can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
  • UE User Equipment
  • UE Device any of various types of computer systems devices which are mobile or portable and which performs wireless communications.
  • UE devices include mobile telephones or smart phones (e.g., iPhone TM , Android TM -based phones) , portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM , Gameboy Advance TM , iPhone TM ) , laptops, wearable devices (e.g., smart watch, smart glasses) , PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones) , UAV controllers (UACs) , and so forth.
  • UAVs unmanned aerial vehicles
  • UACs UAV controllers
  • Base Station has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.
  • Processing Element refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device.
  • Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit) , programmable hardware elements such as a field programmable gate array (FPGA) , as well any of various combinations of the above.
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • Channel a medium used to convey information from a sender (transmitter) to a receiver.
  • 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.
  • WLAN channels may be 22MHz wide while Bluetooth channels may be 1Mhz 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
  • Wi-Fi has the full breadth of its ordinary meaning, and at least includes a wireless communication network or RAT that is serviced by wireless LAN (WLAN) access points and which provides connectivity through these access points to the Internet.
  • WLAN wireless LAN
  • Most modern Wi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards and are marketed under the name “Wi-Fi” .
  • Wi-Fi (WLAN) network is different from a cellular network.
  • 3GPP Access refers to accesses (e.g., radio access technologies) that are specified by 3GPP standards. These accesses include, but are not limited to, GSM/GPRS, LTE, LTE-A, and/or 5G NR. In general, 3GPP access refers to various types of cellular access technologies.
  • Non-3GPP Access refers any accesses (e.g., radio access technologies) that are not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and/or fixed networks. Non-3GPP accesses may be split into two categories, “trusted” and “untrusted” : Trusted non-3GPP accesses can interact directly with an evolved packet core (EPC) and/or a 5G core (5GC) whereas untrusted non-3GPP accesses interwork with the EPC/5GC via a network entity, such as an Evolved Packet Data Gateway and/or a 5G NR gateway. In general, non-3GPP access refers to various types on non-cellular access technologies.
  • EPC evolved packet core
  • 5GC 5G core
  • 5G NR gateway an Evolved Packet Data Gateway
  • non-3GPP access refers to various types on non-cellular access technologies.
  • 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 must 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.
  • 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.
  • FIGS 1A and 1B Communication Systems
  • Figure 1A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of Figure 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 wireless devices, such as user devices 106A, 106B, etc., through 106N, as well as accessory devices, such as user devices 107A, 107B.
  • Each of the user devices may be referred to herein as a “user equipment” (UE) .
  • UE user equipment
  • the user devices 106 and 107 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 as well as UEs 107A and 107B.
  • 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/107 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., 1
  • the base station 102A may alternately be referred to as an ‘eNodeB’ or ‘eNB’ .
  • eNodeB evolved NodeB
  • gNodeB gNodeB
  • 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/107 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.
  • base station 102A may act as a “serving cell” for UEs 106/107 as illustrated in Figure 1, each UE 106/107 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 Figure 1 might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.
  • base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB” .
  • a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • a gNB cell may include one or more transition and reception points (TRPs) .
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • a UE 106/107 may be capable of communicating using multiple wireless communication standards.
  • the UE 106/107 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/107 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.
  • accessory devices 107A/B may include cellular communication capability and hence are able to directly communicate with cellular base station 102A via a cellular RAT. However, since the accessory devices 107A/B are possibly one or more of communication, output power, and/or battery limited, the accessory devices 107A/B may in some instances selectively utilize the UEs 106A/B as a proxy for communication purposes with the base station 102Aand hence to the network 100. In other words, the accessory devices 107A/B may selectively use the cellular communication capabilities of its companion device (e.g., UEs 106A/B) to conduct cellular communications.
  • its companion device e.g., UEs 106A/B
  • the limitation on communication abilities of the accessory devices 107A/B may be permanent, e.g., due to limitations in output power or the RATs supported, or temporary, e.g., due to conditions such as current battery status, inability to access a network, or poor reception.
  • Figure 1B illustrates user equipment 106 (e.g., one of the devices 106A through 106N) and accessory device (or user equipment) 107 (e.g., one of the devices 107A or 107B) in communication with a base station 102 and an access point 112 as well as one another, according to some embodiments.
  • the UEs 106/107 may be devices with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a wearable device, a hand-held device, a computer or a tablet, or virtually any type of wireless device.
  • the accessory device 107 may be a wearable device such as a smart watch.
  • the accessory device 107 may comprise cellular communication capability and be capable of directly communicating with the base station 102 as shown. Note that when the accessory device 107 is configured to directly communicate with the base station, the accessory device may be said to be in “autonomous mode. ” In addition, the accessory device 107 may also be capable of communicating with another device (e.g., UE 106) , referred to as a proxy device, intermediate device, or companion device, using a short-range communications protocol; for example, the accessory device 107 may according to some embodiments be “paired” with the UE 106, which may include establishing a communication channel and/or a trusted communication relationship with the UE 106.
  • another device e.g., UE 106
  • the accessory device 107 may use the cellular functionality of this proxy device for communicating cellular voice and/or data with the base station 102.
  • the accessory device 107 may provide voice and/or data packets intended for the base station 102 over the short-range link to the UE 106, and the UE 106 may use its cellular functionality to transmit (or relay) this voice and/or data to the base station on behalf of the accessory device 107.
  • the voice and/or data packets transmitted by the base station and intended for the accessory device 107 may be received by the cellular functionality of the UE 106 and then may be relayed over the short-range link to the accessory device.
  • the UE 106 may be a mobile phone, a tablet, or any other type of hand-held device, a media player, a computer, a laptop or virtually any type of wireless device.
  • the accessory device 107 when the accessory device 107 is configured to indirectly communicate with the base station 102 using the cellular functionality of an intermediate or proxy device, the accessory device may be said to be in “relay mode. ”
  • the UE 106/107 may include a processor that is configured to execute program instructions stored in memory.
  • the UE 106/107 may perform any of the method embodiments described herein by executing such stored instructions.
  • the UE 106/107 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.
  • FPGA field-programmable gate array
  • the UE 106/107 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/107 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/107 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/107 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/107 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or 1xRTTor LTE or GSM) , and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.
  • FIG. 1 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 Figure 3 is merely one example of a possible base station.
  • the base station 102 may include processor (s) 204 which may execute program instructions for the base station 102.
  • the processor (s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor (s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.
  • MMU memory management unit
  • the base station 102 may include at least one network port 270.
  • the network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.
  • the network port 270 may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider.
  • the core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices 106.
  • the network port 270 may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider) .
  • base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB” .
  • base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs) .
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • the base station 102 may include at least one antenna 234, and possibly multiple antennas.
  • the at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230.
  • the antenna 234 communicates with the radio 230 via communication chain 232.
  • Communication chain 232 may be a receive chain, a transmit chain or both.
  • the radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.
  • the base station 102 may be configured to communicate wirelessly using multiple wireless communication standards.
  • the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies.
  • the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR.
  • the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station.
  • the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc. ) .
  • multiple wireless communication technologies e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.
  • the BS 102 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) , or a combination thereof.
  • processor 204 of the BS 102 in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.
  • processor (s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor (s) 204. Thus, processor (s) 204 may include one or more integrated circuits (Ics) that are configured to perform the functions of processor (s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 204.
  • Ics integrated circuits
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 204.
  • 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.
  • 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 Figure 3 is merely one example of a possible server.
  • 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, UE devices 106, and/or UTM 108, access to network functions, e.g., as further described herein.
  • the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network.
  • the server 104 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • the server 104 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) , or a combination thereof.
  • the processor 344 of the server 104 in conjunction with one or more of the other components 354, 364, and/or 374 may be configured to implement or support implementation of part or all of the features described herein.
  • processor (s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor (s) 344.
  • processor (s) 344 may include one or more integrated circuits (Ics) that are configured to perform the functions of processor (s) 344.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 344.
  • Figure 4 Block Diagram of a UE
  • FIG. 4 illustrates an example simplified block diagram of a communication device 106/107, according to some embodiments. It is noted that the block diagram of the communication device of Figure 4 is only one example of a possible communication device. According to embodiments, communication device 106/107 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 wearable device, a tablet, an unmanned aerial vehicle (UAV) , a UAV controller (UAC) and/or a combination of devices, among other devices. As shown, the communication device 106/107 may include a set of components 400 configured to perform core functions.
  • UE user equipment
  • UAV unmanned aerial vehicle
  • UAC UAV controller
  • 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/107 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/107, and wireless communication circuitry 430.
  • the wireless communication circuitry 430 may include a cellular modem 434 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication logic 436 (e.g., Bluetooth TM and WLAN circuitry) .
  • communication device 106/107 may include wired communication circuitry (not shown) , such as a network interface card, e.g., for Ethernet.
  • the wireless communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a, 435b, and 435c (e.g., 435a-c) as shown.
  • the wireless communication circuitry 430 may include local area network (LAN) logic 432, the cellular modem 434, and/or short-range communication logic 436.
  • the LAN logic 432 may be for enabling the UE device 106/107 to perform LAN communications, such as Wi-Fi communications on an 802.11 network, and/or other WLAN communications.
  • the short-range communication logic 436 may be for enabling the UE device 106/107 to perform communications according to a short-range RAT, such as Bluetooth or UWB communications.
  • the cellular modem 434 may be a lower power cellular modem capable of performing cellular communication according to one or more cellular communication technologies.
  • cellular modem 434 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 modem 434 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/107 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/107 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/107 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/107, 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/107 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/107 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/107 may include two or more SIMs.
  • the inclusion of two or more SIMs in the UE 106/107 may allow the UE 106/107 to support two different telephone numbers and may allow the UE 106/107 to communicate on corresponding two or more respective networks.
  • a first SIM may support a first RAT such as LTE
  • a second SIM 410 support a second RAT such as 5G NR.
  • Other implementations and RATs are of course possible.
  • the UE 106/107 may support Dual SIM Dual Active (DSDA) functionality.
  • DSDA Dual SIM Dual Active
  • the DSDA functionality may allow the UE 106/107 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/107 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/107 may support Dual SIM Dual Standby (DSDS) functionality.
  • the DSDS functionality may allow either of the two SIMs in the UE 106/107 to be on standby waiting for a voice call and/or data connection.
  • 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 be configured to communicate using wireless and/or wired communication circuitry.
  • the communication device 106 may be configured to perform methods for extended (e.g., greater than 10.24 seconds) eDRX inactive operation, e.g., in 5G NR systems and beyond, as further described herein.
  • the communication device 106/107 may include hardware and software components for implementing the above features for a communication device 106/107to communicate a scheduling profile for power savings to a network.
  • the processor 402 of the communication device 106/107 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.
  • 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 Figure 5 is only one example of a possible cellular communication circuit.
  • cellular communication circuitry 530 which may be cellular modem circuitry 434, may be included in a communication device, such as communication device 106/107described above.
  • communication device 106/107 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, a wearable device, 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 535a-c (which may be antennas 435a-c of Figure 4) .
  • cellular communication circuitry 530 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR) .
  • cellular communication circuitry 530 may include a modem 510 and a modem 520.
  • Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
  • a first RAT e.g., such as LTE or LTE-A
  • modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
  • modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 530.
  • RF front end 530 may include circuitry for transmitting and receiving radio signals.
  • RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534.
  • receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 535a.
  • 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 535b.
  • 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 535c.
  • 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 cellular communication circuitry 530 may be configured to perform methods for extended (e.g., greater than 10.24 seconds) eDRX inactive operation, e.g., in 5G NR systems and beyond, as further described herein.
  • 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) .
  • the processor 512 in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 535a-c 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 modem 520 may include hardware and software components for implementing the above features for extended (e.g., greater than 10.24 seconds) eDRX inactive operation, e.g., in 5G NR systems and beyond, as well as the various other techniques described herein.
  • 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, 535a-c 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.
  • Ics integrated circuits
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processors 522.
  • FIGS. 6A, 6B and 7 5G Core Network Architecture –Interworking with Wi-Fi
  • the 5G core network may be accessed via (or through) a cellular connection/interface (e.g., via a 3GPP communication architecture/protocol) and a non-cellular connection/interface (e.g., a non-3GPP access architecture/protocol such as Wi-Fi connection) .
  • Figure 6A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments.
  • a user equipment device may access the 5G CN through both a radio access network (RAN, e.g., such as gNB 604, which may be a base station 102) and an access point, such as AP 612.
  • the AP 612 may include a connection to the Internet 600 as well as a connection to a non-3GPP inter-working function (N3IWF) 603 network entity.
  • the N3IWF may include a connection to a core access and mobility management function (AMF) 605 of the 5G CN.
  • the AMF 605 may include an instance of a 5G mobility management (5G MM) function associated with the UE 106/107.
  • 5G MM 5G mobility management
  • the RAN e.g., gNB 604
  • the 5G CN may support unified authentication over both connections as well as allow simultaneous registration for UE 106/107 access via both gNB 604 and AP 612.
  • the AMF 605 may be in communication with a location management function (LMF) 609 via a networking interface, such as an NLs interface.
  • the LMF 609 may receive measurements and assistance information from the RAN (e.g., gNB 604) and the UE (e.g., UE 106) via the AMF 605.
  • the LMF 609 may be a server (e.g., server 104) and/or a functional entity executing on a server.
  • the LMF may determine a location of the UE.
  • the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., network slice selection function (NSSF) 620, short message service function (SMSF) 622, application function (AF) 624, unified data management (UDM) 626, policy control function (PCF) 628, and/or authentication server function (AUSF) 630) .
  • these functional entities may also be supported by a session management function (SMF) 606a and an SMF 606b of the 5G CN.
  • the AMF 605 may be connected to (or in communication with) the SMF 606a.
  • the gNB 604 may in communication with (or connected to) a user plane function (UPF) 608a that may also be communication with the SMF 606a.
  • the N3IWF 603 may be communicating with a UPF 608b that may also be communicating with the SMF 606b.
  • Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and/or the Internet 600 and Internet Protocol (IP) Multimedia Subsystem/IP Multimedia Core Network Subsystem (IMS) core network 610.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem/IP Multimedia Core Network Subsystem
  • FIG. 6B illustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments.
  • a user equipment device e.g., such as UE 106
  • the AP 612 may include a connection to the Internet 600 as well as a connection to the N3IWF 603 network entity.
  • the N3IWF may include a connection to the AMF 605 of the 5G CN.
  • the AMF 605 may include an instance of the 5G MM function associated with the UE 106/107.
  • the RAN e.g., gNB 604
  • the 5G CN may support unified authentication over both connections as well as allow simultaneous registration for UE 106/107 access via both gNB 604 and AP 612.
  • the 5G CN may support dual-registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604) .
  • the eNB 602 may have connections to a mobility management entity (MME) 642 and a serving gateway (SGW) 644.
  • MME mobility management entity
  • SGW serving gateway
  • the MME 642 may have connections to both the SGW 644 and the AMF 605.
  • the SGW 644 may have connections to both the SMF 606a and the UPF 608a.
  • the AMF 605 may be in communication with an LMF 609 via a networking interface, such as an NLs interface, e.g., as described above, and may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and/or AUSF 630) .
  • UDM 626 may also include a home subscriber server (HSS) function and the PCF may also include a policy and charging rules function (PCRF) .
  • HSS home subscriber server
  • PCF policy and charging rules function
  • the AMF 606 may be connected to (or in communication with) the SMF 606a.
  • the gNB 604 may in communication with (or connected to) the UPF 608a that may also be communication with the SMF 606a.
  • the N3IWF 603 may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and/or the Internet 600 and IMS core network 610.
  • one or more of the above-described network entities may be configured to perform methods for extended (e.g., greater than 10.24 seconds) eDRX inactive operation, e.g., in 5G NR systems and beyond, e.g., as further described herein.
  • extended e.g., greater than 10.24 seconds
  • Figure 7 illustrates an example of a baseband processor architecture for a UE (e.g., such as UE 106) , according to some embodiments.
  • the baseband processor architecture 700 described in Figure 7 may be implemented on one or more radios (e.g., radios 429 and/or 430 described above) or modems (e.g., modems 510 and/or 520) as described above.
  • the non-access stratum (NAS) 710 may include a 5G NAS 720 and a legacy NAS 750.
  • the legacy NAS 750 may include a communication connection with a legacy access stratum (AS) 770.
  • AS legacy access stratum
  • the 5G NAS 720 may include communication connections with both a 5G AS 740 and a non-3GPP AS 730 and Wi-Fi AS 732.
  • the 5G NAS 720 may include functional entities associated with both access stratums.
  • the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724.
  • the legacy NAS 750 may include functional entities such as short message service (SMS) entity 752, evolved packet system (EPS) session management (ESM) entity 754, session management (SM) entity 756, EPS mobility management (EMM) entity 758, and mobility management (MM) /GPRS mobility management (GMM) entity 760.
  • the legacy AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and/or GSM/GPRS AS 776.
  • the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) .
  • the 5G MM may maintain individual connection management and registration management state machines for each connection.
  • a device e.g., UE 106
  • PLMN e.g., 5G CN
  • 5G CN e.g., 5G CN
  • there may be common 5G-MM procedures e.g., registration, de-registration, identification, authentication, as so forth for both accesses.
  • one or more of the above-described functional entities of the 5G NAS and/or 5G AS may be configured to perform methods for extended (e.g., greater than 10.24 seconds) eDRX inactive operation, e.g., in 5G NR systems and beyond, e.g., as further described herein.
  • an extended discontinuous reception cycle eDRX
  • RRC radio resource control
  • RAN radio access network
  • CN core network
  • eDRX for CN paging may be configured by upper layers.
  • a hyper system frame number may be broadcast by the cell and may increment one when a system frame number (SFN) wraps around.
  • a paging hyyperframe may refer to an H-SFN in which a UE starts monitoring paging DRX during a paging time window (PTW) used in an RRC idle state.
  • the PH and PTW may be determined based on a formula (see, e.g., 3GPP TS 38.304) that may be known by an AMF, UE, and RAN.
  • These values e.g., H-SFN, PH, and PTW
  • H-SFN, PH, and PTW are used if and/or when an eDRX cycle is greater than 10.24 seconds and when an RRC idle state eDRX cycle is longer than a system information modification period, the UE may verify that stored system information remains valid before establishing an RRC connection.
  • support of eDRX inactive state operation is optional for both the UE and network and a UE that supports eDRX inactive state operation should support eDRX idle state operation as well.
  • Figure 8 illustrates UE eDRX idle state operation in 3GPP Release 17.
  • a UE may send a registration request to a core network.
  • the registration request may include a UE capability that indicates support for eDRX.
  • the UE may receive a registration accept message from the core network (CN) that includes an eDRX configuration.
  • the CN may also send the eDRX configuration to a radio access network (RAN) communicating with the UE.
  • RAN radio access network
  • the UE may enter an eDRX cycle and only monitor for CN pages during an eDRX paging window, as shown. In other words, the UE may only monitor for pages during the eDRX paging window and may ignore RAN paging opportunities outside of the eDRX paging window.
  • the CN may notify the RAN of a CN page to the UE and the RAN may send the CN page to the UE during an eDRX paging window, as shown.
  • 3GPP Release 18 has introduced enhancements to eDRX operations.
  • 3GPP Release 18 extends a maximum value of an eDRX cycle to 10485.76 seconds (2.91 hours) for a UE in an RRC inactive state.
  • CN buffering of data for the UE is the preferred solution.
  • unresolved issues remain for actual implementation of the extended eDRX paging cycle in 3GPP Release 18 and beyond. For example, information exchange between the RAN/CN and UE for the UE to indicate support of the extended eDRX paging cycle has not been resolved.
  • Embodiments described herein provided systems, methods, and mechanisms for extended (e.g., greater than 10.24 seconds) eDRX inactive operation, including systems, methods and mechanisms for a UE to indicate support of an extended eDRX paging cycle to a RAN/CN, a RAN to indicated support of an extended eDRX paging cycle to a UE, UE procedures for mobility between nodes (e.g., base stations and/or AMFs) supporting extended eDRX paging cycles and nodes not supporting extended eDRX paging cycles as well as UE behavior in terms of applying extended eDRX paging cycles between supporting and non-supporting nodes has not been addressed, and internode exchange between RAN nodes of different configuration/support levels of extended eDRX paging cycles.
  • nodes e.g., base stations and/or AMFs
  • a UE such as UE 106
  • the UE may indicate, via a RAN capability indication, support for an eDRX paging cycle greater than 10 seconds while in an RRC inactive state.
  • the paging cycle greater than 10 seconds may be greater than 10.24 seconds.
  • the indication of support may be via a UE capability indication parameter, such as an extendedDRX-CycleAbove10SecInactive-r18 parameter as illustrated by Figure 9. As shown, such a parameter may be an optional, enumerated parameter.
  • a UE such as UE 106, may indicate support to a core network (CN) , e.g., to an AMF of the CN, such as AMF 605, for an extended eDRX paging cycle while in an RRC inactive state.
  • the UE may indicate, via a network access stratum (NAS) registration message support for an eDRX paging cycle greater than 10.24 seconds while in an RRC inactive state.
  • NAS network access stratum
  • Such an indication may be a UE capability, a request for an AMF on usefulness of an extended eDRX paging cycle, and/or a registration request message with an extended DRX parameters information element (IE) .
  • IE extended DRX parameters information element
  • the AMF may send inactive assistance information, e.g., regarding the extended eDRX paging cycle, to a RAN supporting the UE.
  • the RAN may determine eDRX parameters when the UE is in an RRC inactive state.
  • the RAN may indicate the determined eDRX parameters via an N2 message between the RAN and the AMF.
  • the AMF may request (or ask) the RAN for eDRX parameters in an N2 request and/or N2 response message.
  • a base station such as base station 102
  • SIB system information broadcast
  • the indication of support may be via a parameter, such as an eDRX-Above10SecAllowedInactive-r18 parameter as illustrated by Figure 10. As shown, such a parameter may be an optional, enumerated parameter.
  • a base station in addition to broadcasting information regarding support of an extended eDRX paging cycle when a UE, such as UE 106, is in an RRC inactive state, a base station, such as base station 102, may support on-demand requests from the UE regarding such support.
  • the UE may transmit a random access control channel (RACH) message to request on-demand information regarding whether the base station supports extended eDRX paging cycle when the UE is in an RRC inactive state.
  • RACH random access control channel
  • the base station may transmit a broadcast response, e.g., such as a SIB1 as described in reference to Figure 10, that includes support information.
  • a UE such as UE 106
  • the UE may follow its current configuration (e.g., the UE may not change its current DRX cycle when entering the new cell) .
  • the UE when the UE has been configured with an extended eDRX paging cycle when in an RRC inactive state and enters a new cell (e.g., changes serving base stations) that does not support the extended eDRX paging cycle when the UE is in the RRC inactive state, the UE may follow the RAN paging cycle for the new cell (e.g., the UE may not use extended eDRX) .
  • a new cell e.g., changes serving base stations
  • a configuration for an extended eDRX paging cycle when the UE is in an RRC inactive state may also include a 3GPP Release 17 eDRX configuration, e.g., as illustrated by Figure 11.
  • a base station may include a list of neighboring base stations that support the extended eDRX paging cycle when the UE is in an RRC inactive state.
  • the base station may specify a validity area of base station in which the UE may assume support of the extended eDRX paging cycle when the UE is in an RRC inactive state.
  • such a list may be sent to the UE via a suspendConfig message, e.g., as illustrated by Figure 12.
  • paging information e.g., cycles used by a UE from a base station’s perspective
  • support of an extended eDRX paging cycles when a UE is in an RRC inactive state needs to be exchanged across different supporting base stations.
  • Such information may be conveyed via Xn signaling, e.g., as illustrated by Figure 13.
  • extended eDRX paging cycles for supporting and/or configured UEs may be exchanged across participating candidate base stations.
  • a base station gNB needs to inform an AMF about the paging cycle length as well as paging time window (PTW) duration.
  • PGW paging time window
  • Such information may be conveyed from the base station to the AMF via an N2 interface using a configuration update message that includes a cycle length and PTW windows size as well as information as illustrated by Figure 13.
  • Figure 14 illustrates a block diagram of an example of a method for extended enhanced discontinuous reception cycle (eDRX) operation while in a radio resource control (RRC) inactive state, according to some embodiments.
  • the method shown in Figure 14 may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.
  • a UE such as UE 106 may indicate support for extended eDRX while in RRC inactive state (e.g., an eDRX cycle greater than 10.24 seconds) to at least one of a radio access network (RAN) , e.g., such as a base station 102, or a core network (CN) .
  • RAN radio access network
  • CN core network
  • the UE may send, to the RAN, a UE capability indication via a UE capability information message.
  • the indication of support may be via a UE capability indication parameter, such as an extendedDRX-CycleAbove10SecInactive-r18 parameter.
  • the UE may send, to an access and mobility management function (AMF) of the CN, such as AMF 605, a network access stratum (NAS) registration message.
  • AMF access and mobility management function
  • NAS network access stratum
  • the NAS registration message may include an indication of support for extended eDRX while in RRC inactive state indication.
  • the indication may be a NAS capability and/or a request on usefulness of extended eDRX while in RRC inactive state.
  • the indication may be via an information element of the NAS registration message.
  • the information element may be a field of a 5GMM capability field parameter. Further, the information element may be an extended DRX parameters information element.
  • the AMF of the CN and the RAN may exchange, over an N2 interface, information associated with eDRX parameters for RRC inactive state.
  • the information associated with the eDRX parameters for RRC inactive state may include AMF provided inactive assistance information and/or RAN determined eDRX parameters for RRC inactive state.
  • the UE may receive from a serving cell of the RAN (e.g., such as base station 102) , a configuration for extended eDRX while in RRC inactive state.
  • the configuration for extended eDRX while in RRC inactive state may include a list of cells of the RAN that support extended eDRX while in RRC inactive state.
  • the configuration for extended eDRX while in RRC inactive state may include an eDXR while in RRC inactive state configuration.
  • the UE may operate according to the configuration for extended eDRX while in RRC inactive state. In other words, upon entering an RRC inactive state, the UE may operate using an extended eDRX paging cycle.
  • the UE may receive, from the RAN, extended eDRX while in RRC inactive state support information via a broadcast message.
  • the broadcast message may be a system information broadcast (SIB) type 1 (SIB1) broadcast message.
  • SIB1 may include a parameter indicating whether or not the RAN supports extended eDRX while in RRC inactive state.
  • the parameter may include an eDRX-Above10SecAllowedInactive-r18 parameter.
  • the UE may transmit, to the RAN, a UE random access channel (RACH) request for on-demand information regarding extended eDRX while in RRC inactive state support and receive, from the RAN, extended eDRX while in RRC inactive state support information via a broadcast response message.
  • RACH UE random access channel
  • the UE may transition to a new cell of the RAN that does not support extended eDRX while in RRC inactive state and may continue to use the configuration for extended eDRX while in RRC inactive state.
  • the UE may transition to a new cell of the RAN that does not support extended eDRX while in RRC inactive state and may discontinue use of the configuration for extended eDRX while in RRC inactive state. In such instances, the UE may adopt a RAN paging cycle of the new cell.
  • the UE may transition to a new cell of the RAN that does not support extended eDRX while in RRC inactive state and may receive, from the new cell, an indication of support of eDRX while in RRC inactive state. In such instances, the UE may continue to use the configuration for extended eDRX while in RRC inactive state.
  • the UE may transition to a new cell of the RAN that does not support extended eDRX while in RRC inactive state and may receive, from the new cell, an indication of support of eDRX while in RRC inactive state. In such instances, the UE may discontinue use of the configuration for extended eDRX while in RRC inactive state and adopt a RAN paging cycle of the new cell.
  • the UE may transition to a new cell of the RAN that does not support extended eDRX while in RRC inactive state and may receive, from the new cell, an indication of support of eDRX while in RRC inactive state.
  • the UE may discontinue use of the configuration for extended eDRX while in RRC inactive state and adopting a configuration for eDRX while in RRC inactive state.
  • the configuration for eDRX while in RRC inactive state may be received from the new cell.
  • the configuration for eDXR while in RRC inactive state may be received as part of the configuration for extended eDRX while in RRC inactive state.
  • Figure 15 illustrates a block diagram of another example of a method for extended eDRX operation while in an RRC inactive state, according to some embodiments.
  • the method shown in Figure 15 may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.
  • a base station such as base station 102, of a RAN may receive, from a UE, such as UE 106, an indication of support for extended eDRX while in RRC inactive state (e.g., an eDRX cycle greater than 10.24 seconds) .
  • the indication may be received as a UE capability indication via a UE capability information message.
  • the indication of support may be via a UE capability indication parameter, such as an extendedDRX-CycleAbove10SecInactive-r18 parameter.
  • the base station may exchange, over an N2 interface, information associated with eDRX parameters for RRC inactive state with an AMF, such as AMF 605, of a core network (CN) .
  • the base station may receive inactive assistance information from the AMF and may determine eDRX parameters for RRC inactive state based, at least in part, on the inactive assistance information.
  • the base station may send, to the UE, a configuration for extended eDRX while in RRC inactive state.
  • the configuration for extended eDRX while in RRC inactive state may include a list of cells of the RAN that support extended eDRX while in RRC inactive state.
  • the configuration for extended eDRX while in RRC inactive state may include an eDXR while in RRC inactive state configuration.
  • the UE may operate according to the configuration for extended eDRX while in RRC inactive state. In other words, upon entering an RRC inactive state, the UE may operate using an extended eDRX paging cycle.
  • the base station may broadcast extended eDRX while in RRC inactive state support information via a broadcast message.
  • the broadcast message may be a system information broadcast (SIB) type 1 (SIB1) broadcast message.
  • SIB1 may include a parameter indicating whether or not the RAN supports extended eDRX while in RRC inactive state.
  • the parameter may include an eDRX-Above10SecAllowedInactive-r18 parameter.
  • the base station may receive, from the UE, a UE random access channel (RACH) request for on-demand information regarding extended eDRX while in RRC inactive state support and send, to the UE, extended eDRX while in RRC inactive state support information via a broadcast response message.
  • RACH UE random access channel
  • the base station may exchange the configuration for extended eDRX while in RRC inactive with one or more neighboring (e.g., participating) base stations within the RAN via Xn signaling.
  • the base station may include configuration parameters for extended eDRX while in RRC inactive in an NR Paging eDRX Cycle Inactive parameter (e.g., group or information element) and/or an NR paging time window parameter.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
  • 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)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des appareils, des systèmes et des procédés pour un fonctionnement inactif eDRX étendu (par exemple, supérieur à 10,24 secondes), par exemple, dans des systèmes NR 5G et au-delà. Un UE peut indiquer un support pour eDRX étendu tout en étant dans un état inactif RRC à au moins l'un d'un réseau d'accès radio (RAN), par exemple, tel qu'une station de base du RAN, ou un réseau central (CN), par exemple, tel qu'une AMF du CN. De plus, l'UE peut être conçu pour recevoir, en provenance d'une cellule de desserte du RAN, une configuration pour eDRX étendu tout en étant dans un état inactif RRC. La configuration pour eDRX étendu tout en étant dans un état inactif RRC peut comprendre une liste de cellules du RAN qui prennent en charge un eDRX étendu tout en étant dans un état inactif RRC et/ou un eDXR tout en étant dans une configuration d'état inactif RRC. De plus, l'UE peut être conçu pour fonctionner selon la configuration pour un eDRX étendu tout en étant dans un état inactif RRC.
PCT/CN2023/076403 2023-02-16 2023-02-16 Procédés de fonctionnement inactif edrx étendu Pending WO2024168666A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380094215.1A CN120712841A (zh) 2023-02-16 2023-02-16 用于扩展的eDRX非活动操作的方法
PCT/CN2023/076403 WO2024168666A1 (fr) 2023-02-16 2023-02-16 Procédés de fonctionnement inactif edrx étendu

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076403 WO2024168666A1 (fr) 2023-02-16 2023-02-16 Procédés de fonctionnement inactif edrx étendu

Publications (1)

Publication Number Publication Date
WO2024168666A1 true WO2024168666A1 (fr) 2024-08-22

Family

ID=92422064

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/076403 Pending WO2024168666A1 (fr) 2023-02-16 2023-02-16 Procédés de fonctionnement inactif edrx étendu

Country Status (2)

Country Link
CN (1) CN120712841A (fr)
WO (1) WO2024168666A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106060912A (zh) * 2013-03-29 2016-10-26 英特尔Ip公司 无线通信网络中的扩展型呼叫非连续接收（drx）周期
CN115053557A (zh) * 2022-05-09 2022-09-13 北京小米移动软件有限公司 资源配置方法/装置/用户设备/网络侧设备及存储介质
CN115086987A (zh) * 2021-03-12 2022-09-20 华为技术有限公司 通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106060912A (zh) * 2013-03-29 2016-10-26 英特尔Ip公司 无线通信网络中的扩展型呼叫非连续接收（drx）周期
CN115086987A (zh) * 2021-03-12 2022-09-20 华为技术有限公司 通信方法及装置
CN115053557A (zh) * 2022-05-09 2022-09-13 北京小米移动软件有限公司 资源配置方法/装置/用户设备/网络侧设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "On eDRX for NR RRC Inactive and Idle", 3GPP DRAFT; R2-2101241, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051974204 *

Also Published As

Publication number Publication date
CN120712841A (zh) 2025-09-26

Similar Documents

Publication Publication Date Title
US12267702B2 (en) Method for beam failure recovery based on unified TCI framework
WO2022151168A1 (fr) Manipulation de drb sans sdt
WO2022236520A1 (fr) Révocation et modification de consentement de l'utilisateur
WO2022246796A1 (fr) Amélioration du débit de trafic de liaison montante
WO2022077171A1 (fr) Amélioration de commutation d'antenne de transmission de signal de référence de sondage (srs)
WO2022151231A1 (fr) Mise à jour de rna dans une procédure de sdt
WO2023151018A1 (fr) Détermination de cycle de drx
WO2023164797A1 (fr) Indication de faisceau de liaison montante avec structure tci unifiée
WO2023201680A1 (fr) Amélioration de mécanisme de lecture d'informations de système
US20250150243A1 (en) TCI Configuration for Multi-Beam Indication
EP4569961A1 (fr) Estimation d'emplacement pour dispositifs à capacité réduite
WO2024168666A1 (fr) Procédés de fonctionnement inactif edrx étendu
WO2025039100A1 (fr) Procédés de resélection de port autonome dans une opération à entrées multiples et sorties multiples de liaison montante
WO2024060044A1 (fr) Comportement mac et configuration rrc pour signal de réveil ul
WO2024229692A1 (fr) Période de commutation avec avance temporelle
WO2024020863A1 (fr) Systèmes et procédés d'amélioration de mesures d'ue de couche 1 et de couche 3
WO2024065570A1 (fr) Détermination d'un comportement de répéteur commandé par réseau sur des symboles flexibles
WO2023201673A1 (fr) Rrm pour sdt avec edrx et autres activités d'ue
WO2024016155A1 (fr) Mécanismes pour améliorations de réseau non public
WO2024031430A1 (fr) Procédures de positionnement en mode veille pour dispositifs à capacité réduite
WO2024065617A1 (fr) Améliorations de mobilité d'ue
WO2024031405A1 (fr) Réception de prs pendant drx pour dispositifs à capacité réduite
WO2024031422A1 (fr) Procédures de positionnement par groupe pour dispositifs à capacité réduite
WO2024060063A1 (fr) Configuration pour permettre une adaptation de mode de veille de station de base
WO2023077416A1 (fr) Améliorations de csi

Legal Events

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

Ref document number: 23921825

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE