[go: up one dir, main page]

WO2025241524A1 - Configuration de radiorecherche - Google Patents

Configuration de radiorecherche

Info

Publication number
WO2025241524A1
WO2025241524A1 PCT/CN2024/142003 CN2024142003W WO2025241524A1 WO 2025241524 A1 WO2025241524 A1 WO 2025241524A1 CN 2024142003 W CN2024142003 W CN 2024142003W WO 2025241524 A1 WO2025241524 A1 WO 2025241524A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
pos
pfs
legacy
paging
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/142003
Other languages
English (en)
Inventor
Yuantao Zhang
Xiaoying Xu
Ran YUE
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.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
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 Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/142003 priority Critical patent/WO2025241524A1/fr
Publication of WO2025241524A1 publication Critical patent/WO2025241524A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present disclosure relates to wireless communications, and more specifically to a user equipment (UE) , a base station, processors for wireless communication and methods for paging configuration.
  • UE user equipment
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • paging may be utilized for various purposes. Enhancements on paging, particularly configuration and determination of paging-related monitoring occasion, are still needed.
  • the present disclosure relates to methods, apparatuses, and systems that support paging configuration.
  • the signaling overhead for R19 paging configuration may be reduced and the network energy saving may be improved.
  • a UE receives, from a network entity, configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs.
  • the UE determines a target PO for paging monitoring from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • the signaling overhead for paging configuration may be reduced and the network energy saving may be improved.
  • Some implementations of the method and apparatuses described herein may further include: determining a first reference radio frame for monitoring a paging early indication (PEI) associated with the target PO based on a frame offset relative to a second reference radio frame associated with the target PO, wherein the second reference radio frame comprises the reference time unit.
  • PEI paging early indication
  • the reference time unit is a reference PO comprised in the first set of POs.
  • the target PO is associated with a target PF comprised in the second set of PFs, and wherein the target PF is comprised in the first set of PFs, and is associated with the reference PO.
  • the target PF is associated with at least one PO among the first set of POs
  • the reference PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the target PO is associated with a target PF comprised in the second set of PFs
  • the reference time unit is a reference virtual PO
  • an association between the target PF and the reference virtual PO is identical with an association between a PF among the first set of PFs and a PO among the first set of POs.
  • the PF is associated with at least one PO among the first set of POs
  • the PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the reference time unit is a second reference radio frame containing a PO comprised in the first set of POs.
  • the target PO is associated with a target PF comprised in the second set of PFs, and wherein the target PF is comprised in the first set of PFs, and is associated with the PO.
  • the target PF is associated with at least one PO among the first set of POs
  • the PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the target PO is associated with a target PF comprised in the second set of PFs
  • the reference time unit is a second reference radio frame containing a virtual PO, wherein an association between the target PF and the virtual PO is identical with an association between a PF among the first set of PFs and a PO among the first set of POs.
  • the PF is associated with at least one PO among the first set of POs
  • the PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the target PO is associated with a target PF comprised in the second set of PFs
  • the reference time unit is a second reference radio frame associated with the target PF.
  • the configuration information comprises an indication of the second reference radio frame associated with the target PF.
  • the target PO is within the time window starting from the reference time unit.
  • the at least one time offset comprises a time offset
  • the target PO is determined based on the time offset relative to the reference time unit.
  • a first paging monitoring occasion (PMO) associated with the target PO is after a start of the reference time unit by the time offset.
  • the target PO is determined based on a sum of the at least one time offset relative to the reference time unit.
  • the target PO is associated with a target PF
  • the at least one time offset is associated with at least one PO associated with the target PF
  • a first PMO associated with the target PO is after a start of the reference time unit by the sum of the at least one time offset.
  • the configuration information comprises at least one of the following: an indication of a duration of the time window; an indication of the time offset; or an indication of a time domain location of the reference time unit.
  • time domain location information for the second set of POs is absent in the configuration information.
  • the target PO is associated with a target PF, and a first PMO of a first PO associated with the target PF starts from one of the following: a start of the target PF; or an end of a last PO among the first set of POs associated with the target PF, wherein the target PF is comprised in the first set of PFs.
  • a network entity transmits configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs.
  • the network entity determines a target PO for paging a user equipment (UE) from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • PFs paging frames
  • POs paging occasions
  • UE user equipment
  • Some implementations of the method and apparatuses described herein may further include: determining a first reference radio frame for transmitting a paging early indication (PEI) associated with the target PO based on a frame offset relative to a second reference radio frame associated with the target PO, wherein the second reference radio frame comprises the reference time unit.
  • PEI paging early indication
  • the reference time unit is a reference PO comprised in the first set of POs.
  • the target PO is associated with a target PF comprised in the second set of PFs, and wherein the target PF is comprised in the first set of PFs, and is associated with the reference PO.
  • the target PF is associated with at least one PO among the first set of POs
  • the reference PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the target PO is associated with a target PF comprised in the second set of PFs
  • the reference time unit is a reference virtual PO
  • an association between the target PF and the reference virtual PO is identical with an association between a PF among the first set of PFs and a PO among the first set of POs.
  • the PF is associated with at least one PO among the first set of POs
  • the PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the reference time unit is a second reference radio frame containing a PO comprised in the first set of POs.
  • the target PO is associated with a target PF comprised in the second set of PFs, and wherein the target PF is comprised in the first set of PFs, and is associated with the PO.
  • the target PF is associated with at least one PO among the first set of POs
  • the PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the target PO is associated with a target PF comprised in the second set of PFs
  • the reference time unit is a second reference radio frame containing a virtual PO, wherein an association between the target PF and the virtual PO is identical with an association between a PF among the first set of PFs and a PO among the first set of POs.
  • the PF is associated with at least one PO among the first set of POs
  • the PO is one of the following: a first PO among the at least one PO; a last PO among the at least one PO; a PO determined from the at least one PO based on a predefined rule; or a PO determined from the at least one PO based on an indication in the configuration information.
  • the target PO is associated with a target PF comprised in the second set of PFs
  • the reference time unit is a second reference radio frame associated with the target PF.
  • the configuration information comprises an indication of the second reference radio frame associated with the target PF.
  • the target PO is within the time window starting from the reference time unit.
  • the at least one time offset comprises a time offset
  • the target PO is determined based on the time offset relative to the reference time unit.
  • a first paging monitoring occasion (PMO) associated with the target PO is after a start of the reference time unit by the time offset.
  • the target PO is determined based on a sum of the at least one time offset relative to the reference time unit.
  • the target PO is associated with a target PF
  • the at least one time offset is associated with at least one PO associated with the target PF
  • a first PMO associated with the target PO is after a start of the reference time unit by the sum of the at least one time offset.
  • the configuration information comprises at least one of the following: an indication of a duration of the time window; an indication of the time offset; or an indication of a time domain location of the reference time unit.
  • time domain location information for the second set of POs is absent in the configuration information, wherein the target PO is associated with a target PF, and a first PMO of a first PO associated with the target PF starts from one of the following: a start of the target PF; or an end of a last PO among the first set of POs associated with the target PF, wherein the target PF is comprised in the first set of PFs.
  • FIG. 1A illustrates an example of a wireless communications system that supports paging configuration in accordance with aspects of the present disclosure.
  • FIG. 1B illustrates an example of some relevant fields in a PCCH-Config information element in SIB1.
  • FIG. 1C illustrates an example of a first PMO configuration for each POs for an associated PF.
  • FIG. 1D illustrates an example of a PEI configuration for POs associated with one or two PF (s) .
  • FIG. 2 illustrates an example signaling chart of a communication process that supports paging configuration in accordance with some example embodiments of the present disclosure.
  • FIG. 3A illustrates an example of a PO configuration for R19 UEs with a time window starting from a legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 3B illustrates an example of a PO configuration for R19 UEs with a time window starting from a virtual legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 4A illustrates an example of a PO configuration for R19 UEs with a time window starting from a radio frame containing a legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 4B illustrates an example of a PO configuration for R19 UEs with a time window starting from a radio frame containing a virtual legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 5 illustrates an example of a PO configuration for R19 UEs with a time window starting from an indicated reference radio frame in accordance with some example embodiments of the present disclosure.
  • FIG. 6A illustrates an example of a PO configuration for R19 UEs with a time offset relative to a legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 6B illustrates an example of a PO configuration for R19 UEs with at least one time offset relative to a legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 7A illustrates an example of a PO determination for R19 UEs starting from a start of the target PF in accordance with some example embodiments of the present disclosure.
  • FIG. 7B illustrates an example of a PO determination for R19 UEs starting after a legacy PO in accordance with some example embodiments of the present disclosure.
  • FIG. 8A illustrates an example of a PEI-O configuration for R19 UEs based on a legacy scheme similar with a PEI-O configuration for legacy UEs.
  • FIG. 8B illustrates an example of a PEI-O configuration for R19 UEs in accordance with some example embodiments of the present disclosure.
  • FIG. 9 illustrates an example of a device that supports paging configuration in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates an example of a processor that supports paging configuration in accordance with aspects of the present disclosure.
  • FIGS. 11 through 12 illustrate flowcharts of methods that support paging adaptation in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • the term “communication network” refers to a network following any suitable communication standards, such as, 5G NR, long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band internet of things (NB-IoT) , and so on.
  • LTE long term evolution
  • LTE-A LTE-advanced
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • NB-IoT narrow band internet of things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • any suitable generation communication protocols including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.
  • the term “network device” generally refers to a node in a communication network via which a terminal device can access the communication network and receive services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto BS, a pico BS, and so forth, depending on the BS
  • terminal device generally refers to any end device that may be capable of wireless communications.
  • a terminal device may also be referred to as a communication device, a user equipment (UE) , an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) .
  • UE user equipment
  • SS subscriber station
  • UAV unmanned aerial vehicle
  • MS mobile station
  • AT access terminal
  • the terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable terminal device, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an internet of things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain
  • FIG. 1A illustrates an example of a wireless communications system 100 that supports paging configuration in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1A.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1A.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • paging allows the network to reach UEs in RRC_IDLE/RRC_INACTIVE state through paging messages, and to notify UEs of system information modification and ETWS/CMAS indications through paging short messages.
  • the UE may use discontinuous reception (DRX) in RRC_IDLE/RRC_INACTIVE state to reduce power consumption.
  • the UE may only monitor only one paging occasion (PO) of one paging frame (PF) per discontinuous reception (DRX) cycle (i.e., paging cycle) .
  • PO paging occasion
  • PF paging frame
  • a PF is one radio frame and may be associated with one or multiple PO (s) or starting point (s) of PO (s) .
  • a PO is a set of PDCCH monitoring occasions (PMOs) and may consist of multiple time slots for transmitting paging DCI.
  • the paging DCI is per-beam transmitted and the beams for paging transmission are same with those for synchronization and PBCH signal blocks (SSBs) transmission.
  • the PF/PO for UE monitoring is determined based on the UE identity (ID) .
  • the paging configurations are broadcasted through PCCH-Config information element (IE) in system information block 1 (SIB1) (shown in FIG. 1B) .
  • IE PCCH-Config information element
  • SIB1 system information block 1
  • the paging configurations in PCCH-Config IE includes paging cycle, PF number per paging cycle, PO number per PF, etc.
  • Table 1 shows some of the relevant fields in PCCH-Config IE and the descriptions for each configuration field.
  • Table1 Relevant fields in paging configuration PCCH-Config
  • a first PMO of a PO does not need to be within the associated PF.
  • a PO associated with a PF may start in the PF or after the PF.
  • the first PMO of a PO may be configured in any symbol in a set of radio frames including the associated PF and the radio frames between the associated PF and the PF next to the associated PF. This provides full flexibility of PO location, but at the cost of higher signalling overhead.
  • FIG. 1C illustrates an example of first PMOs of POs for an associated PF.
  • SCS 15kHz
  • n_PF i.e., value “n” in PCCH-Config
  • 4 means there is one PF for each 4 radio frames.
  • the first PMO of a PO may be configured to be any symbol of 560 symbols.
  • the 560 symbols are calculated from 140 *4, where “140” is the number of symbols in a radio frame and “4” is the number of radio frames, which contain the PO-associated PF as well as three radio frames between the PO-associated PF and next PF.
  • the first PMOs for the POs of an associated PF are shown to the in a sequential order in FIG. 1C, it is merely for illustration without suggesting any limitations.
  • the first PMO for each PO of an associated PF may be configured to be any symbol among the 560 symbols.
  • PFs/POs paging adaptation.
  • the basic idea is to configure PFs/POs based on traffic needs.
  • dedicated PFs/POs can be configured for R19 UEs, while allowing legacy UEs and R19 UEs to co-exist in the same PF/PO.
  • the number of POs associated with a PF may extend to 8 or an even larger value, so that more POs can be allocated in a time consecutive manner. More POs may be aggregated so that the network may have more chance to stay in sleep mode and achieves network energy saving (NES) .
  • NES network energy saving
  • R19 UEs may refer to UEs supporting paging adaptation
  • legacy UEs may refer to UEs not supporting paging adaptation
  • R19 PF may refer to a PF for R19 UEs while the terminology “legacy PF” may refer to a PF for legacy UEs
  • R19 PO may refer to a PO for R19 UEs
  • legacy PO may refer to a PO for legacy UEs.
  • a PO/PF for R19 UEs may or may overlap with a legacy PO/PF based on network configuration.
  • R19 UEs may only monitor the PF (s) /PO (s) that are configured in a separate paging configuration.
  • An R19 UE may determine a target PO from a set of at least one R19 POs that are associated with an R19 PF based on e.g., UE ID. This is similar with legacy PO and PF determination.
  • the signaling overhead for the paging configuration might be significantly large.
  • enhancements on the PO configuration are needed for signaling overhead reduction.
  • enhancements may be also needed for control signaling overhead reduction on paging early indication (PEI) configuration.
  • PO configuration change might impact PEI occasion (PEI-O) determination or provide opportunity to refine PEI-O design to achieve more NES.
  • PEI may be utilized to reduce UE power consumption on paging monitoring.
  • the UE may monitor paging if an associated PEI indicates that paging message will be transmitted for the UE subgroup that the UE belongs. Otherwise, the UE will not monitor paging in the target PO. Then, the UE may stay in a longer sleep mode and thus power consumption for paging monitoring can be reduced.
  • a PEI is associated with one or multiple POs associated with up to two consecutive PFs.
  • PEI is transmitted in a PEI-O.
  • a PEI-O is a set of PMOs and may consist of multiple time slots where PEI may be sent.
  • FIG. 1D illustrates an example of a PEI configuration for POs associated with one or two PF (s) .
  • the time location of PEI-O for POs is determined by two parameters, pei-FrameOffset and firstPDCCH-MonitoringOccasionOfPEI-O.
  • the pei-FrameOffset refers to a frame-level offset from the start of the first PF of the PF (s) associated with the PEI-O, from which the radio frame associated with PEI-O is determined.
  • the firstPDCCH-MonitoringOccasionOfPEI-O is a symbol level offset from the start of the determined radio frame to the start of the first PDCCH MO of this PEI-O.
  • the set of at least one R19 PO which are associated with a same R19 PF, may be configured/determined from OFDM symbols of a time window, which starts from a reference time unit, or determined based on at least one time offset relative to start of a reference time unit.
  • the reference time unit could be either a reference PO (e.g., a legacy PO) or a reference radio frame (e.g., a radio frame containing a legacy PO, or an indicated radio frame) .
  • a reference PO e.g., a legacy PO
  • a reference radio frame e.g., a radio frame containing a legacy PO, or an indicated radio frame
  • FIG. 2 illustrates an example signaling chart of a communication process that supports paging configuration in accordance with some example embodiments of the present disclosure.
  • the process 200 may involve the UE 104 and the network entity 102.
  • the network entity 102 may be implemented as a base station.
  • the UE 104 may be implemented as a R19 UE supporting paging adaptation. It is to be understood that the steps and the order of the steps in FIG. 2 are merely for illustration, and not for limitation. It is to be understood that process 200 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the base station 102 transmits (202) configuration information 204 for configuring at least one of a first set of PFs associated with a first set of POs or a second set of PFs associated with a second set of POs.
  • the UE 104 receives (206) the configuration information 204 from the base station 102.
  • the UE 104 determines (208) a target PO for paging monitoring from the second set of POs based on a time window or at least one time offset associated with a reference time unit.
  • the reference time unit is determined based on the configuration information 204.
  • the network entity 102 determines (210) the target PO for paging the UE 104.
  • a R19 PO may be configured or determined based on a time window or time offset (s) relative to a reference time unit.
  • the sequence size for the configuration field firstPdcch-MonitoringOccasionOfPO in the paging configuration for R19 UEs may be based on the time window length or the maximum time offset.
  • the signaling overhead on configuration of R19 POs may thus be reduced.
  • the target PO may be within the time window starting from the reference time unit.
  • the configuration information 204 may include an indication of a duration of the time window. Alternatively or additionally, the configuration information 204 may include an indication of a time domain location of the reference time unit. In some alternative embodiments, the R19 PO may be determined based on time offset (s) relative to the reference time unit. In some implementations, the configuration information 204 may include an indication of the time offset. Alternatively or additionally, the configuration information 204 may include an indication of a time domain location of the reference time unit.
  • the reference time unit may be a reference PO included in the first set of POs.
  • a R19 PO may be configured or determined based on a time window or time offset (s) relative to a legacy PO.
  • the target PO may be associated with a target PF included in the second set of PFs, and the target PF may be included in the first set of PFs, and may be associated with the reference PO.
  • the target PF may be associated with both legacy PO (s) and R19 PO (s) .
  • the target PF may be associated with at least one PO among the first set of POs.
  • the reference PO may be a first PO among the at least one PO among the first set of POs.
  • the reference PO may be a last PO among the at least one PO.
  • the reference PO may be a PO determined from the at least one PO based on a predefined rule.
  • the reference PO may be a PO determined from the at least one PO based on an indication in the configuration information 204. In other words, the last legacy PO or the first legacy PO or an indicated legacy PO associated with the target PF may be taken as the reference PO.
  • the reference PO is a legacy PO.
  • the set of at least one R19 PO, which are associated with a same R19 PF, may be configured/determined within a time window, which starts from the beginning of the reference PO.
  • the legacy POs and R19 POs may co-exist in the network. Some PFs may be associated with both legacy PO (s) and R19 PO (s) , while others may only be associated with R19 POs, based on the network configuration. From a R19 UE point of view, if the target PF is associated with both legacy PO (s) and R19 PO (s) , a legacy PO, e.g., the last legacy PO or the first legacy PO or an indicated legacy PO associated with the target PF, may be taken as the reference PO to determine the time window for configuring R19 POs. In other words, the start of this legacy PO (i.e., the legacy PO taken as a reference RO) is the start of the time window for configuring the R19 POs. In some implementations, the legacy PO and the R19 POs may be time consecutively located, which is beneficial in terms of network energy saving. Besides, the time window may contain (much) less OFDM symbols than legacy, so the configuration overhead for R19 POs are reduced.
  • FIG. 3A illustrates an example of a PO configuration for R19 UEs with a time window starting from a legacy PO in accordance with some example embodiments of the present disclosure.
  • the target PF is a R19 PF and is also a legacy PF.
  • the target PF may be associated with one legacy PO and two R19 POs for R19 UEs.
  • the legacy PO may be determined based on the configuration field firstPdcch-MonitoringOccasionOfPO in the paging configuration for legacy UEs.
  • the time window for configuring/determining R19 POs starts from the beginning of the first PMO of legacy PO and contains K OFDM symbols, where K is predefined or configured.
  • the R19 UE determines the target PO from the two R19 POs based on e.g., UE ID.
  • the target PO may be associated with a target PF included in the second set of PFs
  • the reference time unit may be a reference virtual PO.
  • An association between the target PF and the reference virtual PO may be identical with an association between a PF among the first set of PFs and a PO among the first set of POs.
  • the PF among the first set of PFs may be associated with at least one PO among the first set of POs.
  • the PO associated with the PF among the first set of PFs may be a first PO among the at least one PO.
  • the PO associated with the PF among the first set of PFs may be a last PO among the at least one PO.
  • the PO associated with the PF among the first set of PFs may be a PO determined from the at least one PO based on a predefined rule.
  • the PO associated with the PF among the first set of PFs may be a PO determined from the at least one PO based on an indication in the configuration information 204.
  • the reference PO is a virtual legacy PO determined by assuming that the target PF is also a legacy PF associated with legacy PO (s) .
  • the last virtual legacy PO or the first virtual legacy PO or an indicated virtual legacy PO associated with the target PF may be taken as the reference virtual PO.
  • the time window for R19 POs associated with a R19 PF may start from the last/first/indicated virtual legacy PO.
  • R19 POs associated with a R19 PF may be determined based on the time offset (s) relative to the last/first/indicated virtual legacy PO.
  • FIG. 3B illustrates an example of a PO configuration for R19 UEs with a time window starting from a virtual legacy PO in accordance with some example embodiments of the present disclosure.
  • the target PF is a R19 PF and is not a legacy PF.
  • Virtual legacy PO (s) associated with the target PF may be determined based on the legacy PO configuration by assuming the target PF was a legacy PF.
  • the target PF may be associated with one virtual legacy PO and two R19 POs for R19 UEs.
  • the time window for configuring/determining R19 POs starts from the beginning of the first PMO of virtual legacy PO and contains K OFDM symbols, where K is predefined or configured.
  • the R19 UE determines the target PO from the two R19 POs based on e.g., UE ID.
  • the reference time unit may be a virtual legacy PO if the target PF is not a legacy PF.
  • the reference time unit may be a legacy RO if the target PF is also a legacy PF.
  • the time window for the case where the target PF is not associated with legacy PO (s) may be same with the case where the target PF is associated with both legacy PO (s) and R19 PO (s) .
  • the relative position for the time window with respect to the associated R19 PF for a target PF associated with legacy PO (s) is the same as for a target PF not associated with legacy PO (s) .
  • the time window may have a different starting point, which is e.g., the starting of the associated PF, or the starting of an indicated radio frame.
  • the relative time position of the time window for configuring/determining the R19 POs is same for the case that the target PF is not associated with legacy PO (s) and the case that the target PF is associated with legacy PO (s) .
  • the UE may firstly determine the relative time position of the time window for the case that the target PF is associated with legacy PO (s) , as described in the above embodiments, then determine the time window for the case that the target PF is not associated with legacy PO (s) .
  • the relative time position of the time window may be the position relative to the associated PF.
  • the reference time unit may be a second reference radio frame containing a PO included in the first set of POs.
  • a R19 PO may be configured or determined based on a time window or time offset (s) relative to a reference radio frame containing a legacy PO.
  • the target PO may be associated with a target PF included in the second set of PFs.
  • the target PF may be included in the first set of PFs, and may be associated with the PO included in the first set of POs.
  • the target PF may be associated with both legacy PO (s) and R19 PO (s) .
  • the target PF may be associated with at least one PO among the first set of POs.
  • the PO in the second reference radio frame may be a first PO among the at least one PO among the first set of POs.
  • the PO may be a last PO among the at least one PO.
  • the PO may be a PO determined from the at least one PO based on a predefined rule.
  • the PO may be a PO determined from the at least one PO based on an indication in the configuration information 204. In other words, the radio frame containing the last legacy PO or the first legacy PO or an indicated legacy PO associated with the target PF may be taken as the reference radio frame.
  • the reference radio frame is the one containing a legacy PO.
  • the set of at least one R19 PO, which are associated with a same R19 PF, may be configured/determined within a time window, which starts from the beginning of the reference radio frame.
  • the legacy POs and R19 POs may co-exist in the network. Some PFs may be associated with both legacy PO (s) and R19 PO (s) , while others may only be associated with R19 POs, based on the network configuration. From a R19 UE point of view, if the target PF is associated with both legacy PO (s) and R19 PO (s) , a radio frame containing a legacy PO, e.g., the last legacy PO or the first legacy PO or an indicated legacy PO associated with the target PF, may be taken as the reference radio frame to determine the time window for configuring R19 POs. In other words, the start of this reference radio frame is the start of the time window for configuring the R19 POs.
  • a radio frame containing a legacy PO e.g., the last legacy PO or the first legacy PO or an indicated legacy PO associated with the target PF
  • the legacy PO and the R19 POs may be time consecutively located, which is beneficial in terms of network energy saving. Besides, the time window may contain (much) less OFDM symbols than legacy, so the configuration overhead for R19 POs are reduced.
  • the reference radio frame may be determined from a legacy PO. For example, it might be the radio frame next to the last legacy PO.
  • FIG. 4A illustrates an example of a PO configuration for R19 UEs with a time window starting from a radio frame containing a legacy PO in accordance with some example embodiments of the present disclosure.
  • the target PF is a R19 PF and is also a legacy PF.
  • the target PF may be associated with one legacy PO and two R19 POs for R19 UEs.
  • the legacy PO may be determined based on the configuration field firstPdcch-MonitoringOccasionOfPO in the paging configuration for legacy UEs.
  • the time window for configuring/determining R19 POs starts from the beginning of the radio frame containing a legacy PO and contains K OFDM symbols, where K is predefined or configured.
  • the R19 UE determines the target PO from the two R19 POs based on e.g., UE ID.
  • the target PO may be associated with a target PF included in the second set of PFs
  • the reference time unit may be a second reference radio frame containing a virtual PO.
  • An association between the target PF and the virtual PO may be identical with an association between a PF among the first set of PFs and a PO among the first set of POs.
  • the PF among the first set of PFs may be associated with at least one PO among the first set of POs.
  • the PO associated with the PF among the first set of PFs may be a first PO among the at least one PO among the first set of POs.
  • the PO associated with the PF among the first set of PFs may be a last PO among the at least one PO.
  • the PO associated with the PF among the first set of PFs may be a PO determined from the at least one PO based on a predefined rule.
  • the PO associated with the PF among the first set of PFs may be a PO determined from the at least one PO based on an indication in the configuration information 204.
  • the reference radio frame is a radio frame containing a virtual legacy PO determined by assuming that the target PF is also a legacy PF associated with legacy PO (s) .
  • the radio frame containing the last virtual legacy PO or the first virtual legacy PO or an indicated virtual legacy PO associated with the target PF may be taken as the reference time unit.
  • the time window for R19 POs associated with a R19 PF may start from the start of the radio frame containing the last/first/indicated virtual legacy PO.
  • R19 POs associated with a R19 PF may be determined based on the time offset (s) relative to the start of the radio frame containing the last/first/indicated virtual legacy PO.
  • FIG. 4B illustrates an example of a PO configuration for R19 UEs with a time window starting from a radio frame containing a virtual legacy PO in accordance with some example embodiments of the present disclosure.
  • the target PF is a R19 PF and is not a legacy PF.
  • Virtual legacy PO (s) associated with the target PF may be determined based on the legacy PO configuration by assuming the target PF was a legacy PF.
  • the target PF may be associated with one virtual legacy PO and two R19 POs for R19 UEs.
  • the time window for configuring/determining R19 POs starts from the beginning of the radio frame containing the virtual legacy PO and contains K OFDM symbols, where K is predefined or configured.
  • the R19 UE determines the target PO from the two R19 POs based on e.g., UE ID.
  • the reference time unit may be a radio frame containing a virtual legacy PO if the target PF is not a legacy PF.
  • the reference time unit may be a radio frame containing a legacy RO if the target PF is also a legacy PF.
  • the time window for the case where the target PF is not associated with legacy PO (s) may be same with the case where the target PF is associated with both legacy PO (s) and R19 PO (s) .
  • the relative position for the time window with respect to the associated R19 PF for a target PF associated with legacy PO (s) is the same as for a target PF not associated with legacy PO (s) .
  • the time window may have a different starting point, which is e.g., the starting of the associated PF, or the starting of an indicated radio frame.
  • the relative time position of the time window for configuring/determining the R19 POs is same for the case that the target PF is not associated with legacy PO (s) and the case that the target PF is associated with legacy PO (s) .
  • the UE may firstly determine the relative time position of the time window for the case that the target PF is associated with legacy PO (s) , as described in the above embodiments, then determine the time window for the case that the target PF is not associated with legacy PO (s) .
  • the relative time position of the time window may be the position relative to the associated PF.
  • the target PO may be associated with a target PF included in the second set of PFs
  • the reference time unit may be a second reference radio frame associated with the target PF.
  • the association means that the second reference radio frame may be a radio frame among the target PF and at least one PF between the target PF and a PF subsequent to the target PF among the second set of PFs.
  • the configuration information 204 may include an indication of the second reference radio frame associated with the target PF.
  • the reference radio frame for the time window or the at least one time offset may be indicated by the base station 102.
  • the reference time unit may be the target PF.
  • the reference time unit may be the second reference radio frame associated with the target PF regardless of whether the target PF is also a legacy PF.
  • the reference time unit may be the second reference radio frame associated with the target PF; while if the target PF is also a legacy PF, the reference time unit may be determined in other manners, e.g., may be determined as a legacy RO or a radio frame containing a legacy RO.
  • the reference radio frame may be indicated by the base station.
  • the set of at least one R19 PO, which are associated with a same R19 PF, may be configured/determined within a time window, which starts from the beginning of the reference radio frame.
  • the reference radio frame may be the one indicated among the target PF and the radio frames between the target PF and the next R19 PF, or among a subset of these radio frames. In this way, some flexibility is still kept on the location of the POs. Besides, the time window may contain (much) less OFDM symbols than legacy, so the configuration overhead for R19 POs are reduced.
  • FIG. 5 illustrates an example of a PO configuration for R19 UEs with a time window starting from an indicated reference radio frame in accordance with some example embodiments of the present disclosure.
  • the target PF may be associated with two R19 POs for R19 UEs.
  • the time window for configuring/determining R19 POs starts from the beginning of the indicated reference radio frame and contains K OFDM symbols, where K is predefined or configured.
  • the R19 UE determines the target PO from the two R19 POs based on e.g., UE ID.
  • FIGS. 3A through 5 illustrates example embodiments of R19 PO determination based on the time window starting from the reference time unit.
  • such reference time unit may be applied to R19 PO determination based on time offset (s) .
  • the reference time unit may be either a reference PO (e.g., a legacy PO or a virtual legacy PO) or a reference radio frame (e.g., a radio frame containing a legacy PO or a virtual legacy PO, or an indicated radio frame) .
  • the at least one time offset may include a time offset
  • the target PO may be determined based on the time offset relative to the reference time unit.
  • the first PMO associated with the target PO may be after a start of the reference time unit by the time offset.
  • a R19 PO may be configured/determined based on a time offset from the beginning of the reference time unit.
  • the reference PO is a legacy PO.
  • the set of at least one R19 PO, which are associated with a same R19 PF, may be configured/determined from a set of at least one time offset.
  • the set of time offsets are defined as such, the kth time offset in the set is the gap between a legacy PO (e.g., the last/first/indicated legacy PO associated with the target PF) and the kth R19 PO associated with the R19 PF.
  • the legacy PO is taken as the reference PO to determine the time location of the target R19 PO.
  • the starting position of the first PMO of the target PO (with index k) is starting of the legacy PO + time offset k.
  • the legacy PO and the R19 POs may be time consecutively located, which is beneficial in terms of network energy saving.
  • the time offset should be configured from a set of values, each corresponding to limited number of OFDM symbols, so the configuration overhead for R19 POs are reduced.
  • FIG. 6A illustrates an example of a PO configuration for R19 UEs with a time offset relative to a legacy PO in accordance with some example embodiments of the present disclosure.
  • the target PF is a R19 PF and is also a legacy PF.
  • the target PF is associated with one legacy PO and two R19 POs.
  • the legacy PO as the reference PO may be determined in a similar manner as the example in FIG. 3A, and detailed description thereof will be omitted.
  • the target PO is the PO#0
  • the UE determines the starting PO#0 to be starting of legacy PO + offset 0.
  • the target PO is PO#1
  • UE determines the starting PO#0 to be starting of legacy PO + offset 1.
  • the reference time unit is illustrated as a legacy PO in FIG. 6A, it may be a virtual legacy PO as in FIG. 3B, or a radio frame as in FIGS. 4A, 4B or 5 in other implementations.
  • the target PO may be determined based on a sum of the at least one time offset relative to the reference time unit.
  • the target PO may be associated with a target PF, and the at least one time offset may be associated with at least one PO associated with the target PF.
  • a first PMO associated with the target PO may be after a start of the reference time unit by the sum of the at least one time offset.
  • a R19 PO may be configured/determined based on a sum of at least one time offset from the beginning of the reference time unit.
  • the reference PO is a legacy PO.
  • the set of at least one R19 PO which are associated with a same R19 PF, may be configured/determined from a set of at least one time offset.
  • the set of time offsets are defined as such, the first time offset in the set is the gap between a legacy PO (e.g., the last/first/indicated legacy PO associated with the target PF) and the first R19 PO; the second time offset is the gap between the first R19 PO and the second R19 PO, and so on for other R19 POs.
  • the legacy PO is taken as the reference PO to determine the time location of the target R19 PO.
  • the starting position of the first PMO of the target PO (with index k) is starting of the legacy PO + time offset k+ time offset of PO#k-1 + ...+ time offset 0.
  • the legacy PO and the R19 POs may be time consecutively located, which is beneficial in terms of network energy saving.
  • the time offset should be configured from a set of values, each corresponding to limited number of OFDM symbols, so the configuration overhead for R19 POs are reduced.
  • FIG. 6B illustrates an example of a PO configuration for R19 UEs with at least one time offset relative to a legacy PO in accordance with some example embodiments of the present disclosure.
  • the target PF is a R19 PF and is also a legacy PF.
  • the target PF is associated with one legacy PO and two R19 POs.
  • the legacy PO as the reference PO may be determined in a similar manner as the example in FIG. 3A, and detailed description thereof will be omitted.
  • the target PO is the PO#0
  • the UE determines the starting PO#0 to be starting of legacy PO + offset 0.
  • the target PO is PO#1
  • UE determines the starting PO#0 to be starting of legacy PO + offset 1 + offset 0.
  • the reference time unit is illustrated as a legacy PO in FIG. 6B, it may be a virtual legacy PO as in FIG. 3B, or a radio frame as in FIGS. 4A, 4B or 5 in other implementations.
  • time domain location information for the second set of POs may be absent in the configuration information 204.
  • the first PMOs for R19 POs may be optionally configured for the UEs.
  • the first PMO for each of R19 POs is not configured, while the first PMO of each of legacy POs is configured.
  • the first PMO of both R19 POs and legacy POs are not configured.
  • the target PO may be associated with a target PF.
  • a first PMO of a first PO associated with the target PF may start from a start of the target PF.
  • the first PMO of the first R19 PO of the set of R19 POs that are associated with a same PF may start from the beginning of the associated target PF.
  • Such implementation for R19 ROs is aligned with the legacy scheme.
  • a first PMO of a first PO associated with the target PF may start from an end of a last PO among the first set of POs associated with the target PF, wherein the target PF is included in the first set of PFs.
  • the first PMO of the first R19 PO of the set of R19 POs that associated with a same PF may start after the last legacy PO.Such implementation for R19 ROs may provide a better NES gain since legacy PO (s) and R19 PO (s) are aggregated.
  • the UE 104 may receive, from the network entity, an indication of whether the first PMO of a first R19 PO starts from a start of the target PF or starts after a last legacy PO associated with the target PO.
  • the second R19 PO is located consecutively to the first R19 PO and so on for other R19 POs.
  • FIG. 7A illustrates an example of a PO determination for R19 UEs starting from a start of the target PF in accordance with some example embodiments of the present disclosure.
  • FIG. 7B illustrates an example of a PO determination for R19 UEs starting after a legacy PO in accordance with some example embodiments of the present disclosure.
  • each PO is illustrated as occupying two symbols in FIG. 7A and 7B. It should be understood that each PO may occupy more symbols, e.g., eight symbols in which each PO is associated with four PMOs and each PMO occupies two symbols.
  • the UE 104 may determine a first reference radio frame for monitoring a PEI associated with the target PO based on a frame offset relative to a second reference radio frame associated with the target PO.
  • the second reference radio frame may include the reference time unit.
  • the time location of a target PEI-O for a target R19 PO may be determined based on a reference time point and at least one symbol offset relative to the reference time point.
  • the reference time point may be the start of a reference radio frame for PEI, determined by a frame level offset relative to the start of the reference radio frame for the target R19 PO.
  • the reference radio frame for the target R19 PO may be a radio frame containing a last/first/indicated (virtual) legacy PO or may be a radio frame configured by the network entity. It should be understood that the reference time unit for the PEI-O determination may be the same or different from the reference time unit for the PO determination. In other words, the R19 PO determination and the R19 PEI-O determination may be implemented independently. For example, the reference time unit for the PEI-O determination may be a radio frame containing a legacy PO, while the R19 PO reference time unit for the PEI-O determination may be an indicated radio frame.
  • FIG. 8A illustrates an example of a PEI-O configuration for R19 UEs based on a legacy scheme similar with a PEI-O configuration for legacy UEs.
  • the reference radio frame for PEI may be determined from a frame offset, which is relative to the PEI associated PF.
  • FIG. 8B illustrates an example of a PEI-O configuration for R19 UEs in accordance with some example embodiments of the present disclosure.
  • the reference radio frame for PEI may be determined from a frame offset, which is relative to the reference radio frame for R19 POs.
  • R19 POs which are associated with a same R19 PF, may be configured/determined within a time window, which starts from the beginning of the reference radio frame containing a legacy PO.
  • the PEI-O configuration in FIG. 8B enables the PEI-O to be located closer to the associated PF/POs. This is beneficial for network energy saving.
  • FIG. 9 illustrates an example of a device 900 that supports paging configuration in accordance with aspects of the present disclosure.
  • the device 900 may be an example of a network entity 102 or a UE 104 as described herein.
  • the device 900 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 900 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 902, a memory 904, a transceiver 906, and, optionally, an I/O controller 908. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 902, the memory 904, the transceiver 906, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 902, the memory 904, the transceiver 906, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 902 and the memory 904 coupled with the processor 902 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904) .
  • the processor 902 may support wireless communication at the device 900 in accordance with examples as disclosed herein.
  • the processor 902 may be configured to operable to support a means for receiving, from a network entity, configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs; and a means for determining a target PO for paging monitoring from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • PFs paging frames
  • POs paging occasions
  • a second set of PFs associated with a second set of POs
  • the processor 902 may support wireless communication at the device 900 in accordance with examples as disclosed herein.
  • the processor 902 may be configured to operable to support a means for transmitting configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs; and a means for determining a target PO for paging a user equipment (UE) from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • PFs paging frames
  • POs paging occasions
  • UE user equipment
  • the processor 902 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 902 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 902.
  • the processor 902 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 904) to cause the device 900 to perform various functions of the present disclosure such that the device 900 may perform any process of the disclosure as discussed with reference to FIGS. 2 to 8B.
  • the memory 904 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 902 cause the device 900 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 902 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 904 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 908 may manage input and output signals for the device 900.
  • the I/O controller 908 may also manage peripherals not integrated into the device M02.
  • the I/O controller 908 may represent a physical connection or port to an external peripheral.
  • the I/O controller 908 may utilize an operating system such as or another known operating system.
  • the I/O controller 908 may be implemented as part of a processor, such as the processor 906.
  • a user may interact with the device 900 via the I/O controller 908 or via hardware components controlled by the I/O controller 908.
  • the device 900 may include a single antenna 910. However, in some other implementations, the device 900 may have more than one antenna 910 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 906 may communicate bi-directionally, via the one or more antennas 910, wired, or wireless links as described herein.
  • the transceiver 906 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 906 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 910 for transmission, and to demodulate packets received from the one or more antennas 910.
  • the transceiver 906 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 910 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 910 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 10 illustrates an example of a processor 1000 that supports paging configuration in accordance with aspects of the present disclosure.
  • the processor 1000 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1000 may be implemented in a device or its components as described herein.
  • the device may be an example of a network entity 102 or a UE 104 as described herein.
  • the processor 1000 may include a controller 1002 configured to perform various operations in accordance with examples as described herein.
  • the processor 1000 may optionally include at least one memory 1004, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1000 may optionally include one or more arithmetic-logic units (ALUs) 1006.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 1000 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1000) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 1002 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein.
  • the controller 1002 may operate as a control unit of the processor 1000, generating control signals that manage the operation of various components of the processor 1000. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1002 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1004 and determine subsequent instruction (s) to be executed to cause the processor 1000 to support various operations in accordance with examples as described herein.
  • the controller 1002 may be configured to track memory address of instructions associated with the memory 1004.
  • the controller 1002 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1002 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1000 to cause the processor 1000 to support various operations in accordance with examples as described herein.
  • the controller 1002 may be configured to manage flow of data within the processor 1000.
  • the controller 1002 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1000.
  • ALUs arithmetic logic units
  • the memory 1004 may include one or more caches (e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000) . In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000) .
  • caches e.g., memory local to or included in the processor 1000 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 1004 may reside within or on a processor chipset (e.g., local to the processor 1000) . In some other implementations, the memory 1004 may reside external to the processor chipset (e.g., remote to the processor 1000) .
  • the memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1000, cause the processor 1000 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the controller 1002 and/or the processor 1000 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the processor 1000 to perform various functions.
  • the processor 1000 and/or the controller 1002 may be coupled with or to the memory 1004, and the processor 1000, the controller 1002, and the memory 1004 may be configured to perform various functions described herein.
  • the processor 1000 may include multiple processors and the memory 1004 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 1006 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 1006 may reside within or on a processor chipset (e.g., the processor 1000) .
  • the one or more ALUs 1006 may reside external to the processor chipset (e.g., the processor 1000) .
  • One or more ALUs 1006 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 1006 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 1006 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1006 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1006 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1000 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1000 may be configured to or operable to support a means for receiving, from a network entity, configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs; and a means for determining a target PO for paging monitoring from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • PFs paging frames
  • POs paging occasions
  • a second set of PFs associated with a second set of POs
  • a means for determining a target PO for paging monitoring from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • the processor 1000 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 1000 may be configured to or operable to support a means for transmitting configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs; and a means for determining a target PO for paging a user equipment (UE) from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • PFs paging frames
  • POs paging occasions
  • UE user equipment
  • FIG. 11 illustrates a flowchart of a method 1100 that supports paging configuration in accordance with aspects of the present disclosure.
  • the operations of the method 1100 may be implemented by a device or its components as described herein.
  • the operations of the method 1100 may be performed by a UE 104 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a network entity, configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs.
  • PFs paging frames
  • POs paging occasions
  • the operations of 1105 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1105 may be performed by a device as described with reference to FIG. 1A.
  • the method may include determining a target PO for paging monitoring from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • the operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG. 1A.
  • FIG. 12 illustrates a flowchart of a method 1200 that supports paging configuration in accordance with aspects of the present disclosure.
  • the operations of the method 1200 may be implemented by a device or its components as described herein.
  • the operations of the method 1200 may be performed by a network entity 102 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting configuration information for configuring at least one of a first set of paging frames (PFs) associated with a first set of paging occasions (POs) or a second set of PFs associated with a second set of POs.
  • PFs paging frames
  • POs paging occasions
  • the operations of 1205 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1205 may be performed by a device as described with reference to FIG. 1A.
  • the method may include determining a target PO for paging a user equipment (UE) from the second set of POs based on a time window or at least one time offset associated with a reference time unit, wherein the reference time unit is determined based on the configuration information.
  • the operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by a device as described with reference to FIG. 1A.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

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

Abstract

Divers aspects de la présente divulgation concernent la configuration d'une radiorecherche. Selon un aspect, un UE reçoit, en provenance d'une entité de réseau, des informations de configuration pour configurer un premier ensemble de trames de radiorecherche (PF) associées à un premier ensemble d'occasions de radiorecherche (PO) et/ou un second ensemble de PF associées à un second ensemble de PO. L'UE détermine une PO cible pour la surveillance d'une radiorecherche à partir du second ensemble de PO sur la base d'une fenêtre temporelle ou d'au moins un décalage temporel associé à une unité temporelle de référence, l'unité temporelle de référence étant déterminée sur la base des informations de configuration.
PCT/CN2024/142003 2024-12-24 2024-12-24 Configuration de radiorecherche Pending WO2025241524A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/142003 WO2025241524A1 (fr) 2024-12-24 2024-12-24 Configuration de radiorecherche

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/142003 WO2025241524A1 (fr) 2024-12-24 2024-12-24 Configuration de radiorecherche

Publications (1)

Publication Number Publication Date
WO2025241524A1 true WO2025241524A1 (fr) 2025-11-27

Family

ID=97794602

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/142003 Pending WO2025241524A1 (fr) 2024-12-24 2024-12-24 Configuration de radiorecherche

Country Status (1)

Country Link
WO (1) WO2025241524A1 (fr)

Similar Documents

Publication Publication Date Title
WO2024159947A1 (fr) Transmission de ssb
WO2025097812A1 (fr) Transmission de sib1
WO2025060447A1 (fr) Groupe d'occasions rach pour répétitions de préambule
WO2024156270A1 (fr) Synchronisation pour un dispositif iot ambiant
WO2024239688A1 (fr) Adaptation de ressources prach
WO2025241524A1 (fr) Configuration de radiorecherche
WO2025200559A1 (fr) Adaptation de ressources de prach
WO2024169553A1 (fr) Détermination de signal de liaison descendante
WO2025241593A1 (fr) Signal d'alerte pour ntn
WO2025200463A1 (fr) Adaptation de radiorecherche
WO2024093394A1 (fr) Récupération d'informations système
WO2025194928A1 (fr) Communication basée sur un motif tdd pour un ntn de l'iot
WO2025241590A1 (fr) Transmission de bloc de signal de synchronisation
WO2025161471A1 (fr) Transmission de msg3 pour accès aléatoire
WO2025194793A1 (fr) Motif de tdd pour ntn de l'ido
WO2025123719A1 (fr) Configuraton de wus
WO2024193732A1 (fr) Radiomessagerie
WO2025123717A1 (fr) Ré-accès pour un système d'ido-a
WO2025123731A1 (fr) Détermination de ressources de wus
WO2025161470A1 (fr) Valeurs temporelles maximales pour transmissions d2r
WO2025035824A1 (fr) Occasion de rach valide
WO2025161464A1 (fr) Accès aléatoire pour réseau non terrestre
WO2025241561A1 (fr) Affinement de faisceau pour accès aléatoire
WO2025035816A1 (fr) Transmission de prach
WO2025030919A1 (fr) Gestion de collision dans un intervalle de mesure