WO2022031540A1 - Ue power saving in idle/inactive state - Google Patents

Abstract

An apparatus and system to enable wakeup signals (WUS) and reference signals (RS) when a UE is in idle/inactive mode are described. A configuration for each of the WUS and RS indicates parameters and values for periodic RS transmissions. Various parameters and configuration information are provided for WUS and RS occasions. Availability information for RS transmissions are based on a bitmap in which each bit is associated with at least one resource or configuration. The UE determines, based on WUS transmissions, whether to monitor a next paging occasion (PO) if the UE is paged. Dynamic functionality for the WUS or RS is provided via downlink control information (DCI), including whether a sub-group that includes the UE is being paged.

Description

UE POWER SAVING IN IDLE/INACTIVE STATE PRIORITY CLAIM

[0001] This application claims the benefit of pri ority to United States Provisional Patent Application Serial No. 63/061,116, filed August 7, 2020, United States Provisional Patent Application Serial No. 63/093,668, filed October 19, 2020, United States Provisional Patent Application Serial No. 63/138,181, filed January' 15, 2021, and United States Provisional Patent

Application Serial No. 63/142,879, filed January 28, 2021, each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD [0002] Embodiments pertain to fifth generation (5G) wireless communications. In particular, some embodiments relate to wakeup signal (WUS) and reference signal (RS) configuration in 5G systems.

BACKGROUND [0003] The use and complexity of wireless systems, which include 4^th generation (4G) and 5^th generation (5G) networks among others, has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated, especially with the advent of next generation (NG) (or new radio (NR) systems).

As expected, a number of issues abound with the advent of any new technology.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. I A illustrates an architecture of a network, in accordance with some aspects. [0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates synchronization timing in accordance with some embodiments.

[0010] FIG. 4 illustrates a method for UE sub-group identification in accordance with some embodiments.

DETAILED DESCRIPTION

[0011] T he following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0012] FIG. 1A illustrates an architecture of a network in accordance with some aspects. The network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions, A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0013] The network 140A is shown to include user equipment (LIE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0014] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0015] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CloT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short- lived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-loT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep- alive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMFC) UEs or further enhanced MFC (FeMTC) UEs. [0016] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[0017] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA ) network protocol, a Push-to-Talk (PIT) protocol, a PIT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0018] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery' Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[0019] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). [0020] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell), hi some aspects, the communication nodes 111 and 112 can be transmi ssion/recepti on points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0021] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.

[0022] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the S1-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0023] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support. Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. [0024] The S-GW 122 may terminate the SI interface 113 towards the

RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0025] The P-GW 123 may terminate an SGi interface toward a PDN.

The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application sewer 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120. [0026] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123. [0027] In some aspects, the communication network 140A can be an loT network or a 5G or 6G network, including 5G new⁷ radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an ‘‘anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[0028] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G network core (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e.g., a 5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces.

More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces. [0029] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary⁷ node (SN) in a 5G architecture.

[0030] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.

[0031] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0032] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0033] The AF 150 may provide information on the packet flow⁷ to the PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for LIE authentication. [0034] In some aspects, the 5G system architecture I40B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) I64B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.

The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.

[0035] In some aspects, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0036] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 1 10 and the AMF 132), N3 (between the RAN 1 10 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF

142, not shown). Other reference point representations not shown in FIG. 1C can also be used.

[0037] FIG. 1C illustrates a 5G system architecture 140C and a service- based representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository' function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0038] In some aspects, as illustrated in FIG. 1C, sendee-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service- based interfaces: Namf 158H (a sendee-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a senice-based interface exhibited by the NEF 154), Npcf 158D (a sendee-based interface exhibited by the PCF 148), a Nudm 158E (a sendee- based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a sendee-based interface exhibited by the NRF 156), Nnssf 158A (a sendee-based interface exhibited by the NSSF 142), Nausf 158G (a sendee-based interface exhibited by the AUSF 144). Other sendee-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used. [0039] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size.

Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0040] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1 A-1 C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0041] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0042] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general -purpose hardware processor may be configured as respecti ve different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0043] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0044] The storage device 216 may include a n on-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers} configured to store the one or more instructions 224.

[0045] The term “machine readable medium” may include any' medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory , such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory' devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM: and DVD-ROM: disks. [0046] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE

802. 15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.

[0047] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry- may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to cany out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

|0048| The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry' capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

100491 Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile

Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3 GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 1 1), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd

Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.

19, etc.), 3GPP 5G, 5G, 5GNew Radio (5GNR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1 st Generation) (AMPS (IG)), Total Access Communication SystemZExtended Total Access Communication System (TACSZETACS), Digital AMPS (2nd Generation) (D-AMPS (2G )), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System ( AMTS), OUT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for

Mobiitelefoni system D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy- phone System (PUS), Wideband Integrated Digital Enhanced Network (WIDEN), iBurst, Unlicensed Mobile Access ( UM. A), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. 1 l ad, IEEE 802.1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPPZLTE based or IEEE 802.1 Ip or IEEE 802. 1 Ibd and other) Vehicle-to- Vehicle (V2V) and Vehicie-to-X (V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to- Vehicle (12V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European

ITS-G5 system (i.e. the European flavor of IEEE 802.1 Ip based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

[0050] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as ESA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (l lb/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 -- 4200 MHz, 3.55-

3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Sendee), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5,47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC’s "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31 .3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz. (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit.

Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery', automotive, low-latency, drones, etc. applications.

[0051] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g. by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g. with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.

[0052] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

100531 Some of the features in this document are defined for the network side, such as APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP fifth generation (5G) communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

[0054] As above, energy efficiency in 5G/NR UEs, which may have a diverse range of supported applications compared to LTE devices. In idle/inactive mode, the UE may periodically wakeup to receive paging messages from the network. Paging messages can be received in paging occasions (PO) within a predetermined duration, such as within a paging frame. Paging messages are transmitted on a physical downlink control channel (PDCCH) with a shared Radio Network Temporary Identifier (RNTI) such as a paging RNTI (P- RNTI). The UE operates in discontinuous reception (DRX) mode and wakes up at POs to receive the paging message. However, in some circumstances no paging messages are transmitted at the POs. Hence, to avoid unnecessary paging message monitoring/receptions, the network may explicitly indicate to the UE to wakeup only at POs where the network may send paging messages intended for the UE. Moreover, when the UE is in the idle/inactive mode, synchronization signal transmission may not align with the POs and hence, additional reference signals can be useful to maintain tracking and limit frequency /timing errors. Enabling wakeup signal and configuration of additional reference signals to reduce power consumption and maintain tracking in the UE idle/inactive mode are thus disclosed.

[0055] Configuration of Channel Status Information Reference Signals (CSI-RS)ZTracking Reference Signals (TRS) in idle/inactive made [0056] In the idle/inactive mode, cell selection and re-selection is maintained by a UE-initiated process. The UE identifies a first cell with the strongest Synchronization Signal Block (SSB) among other cells, obtains system information from the first cell, and may start initial access with the cell if desired. In the idle/inactive mode, the UE may rely solely on SSB-based measurements and channel tracking. Hence, additional reference signals can be provided to the UE further facilitate measurements, mobility and/or fine tracking of the channel. The methods described herein may be used for a NR UE, including a UE with reduced capability. [0057] In one embodiment, system information (SI) may provide a configuration of one or more reference signals that can be used as a supplementary signal to aid the UE in achieving re-synchronization or maintain tracking for the first cell and/or mobility management and/or reference signal received power (RSRP) measurements. In some embodiments, the SI provides a CSI-RS and/or TRS configuration, either of which can be cell- or group-specific. For example, a master information block (MIB) in the physical broadcast channel (PBCH) or system information block x (SIBx), x = 1 , 2, ...etc., may include the configuration information. In one embodiment, a CSI-RS can be used for cell measurements, such as calculating RSRP or signal strength of the current cell or a different cell and/or more mobility management. In one example, both the SSB and CSI-RS can be used for calculating the RSRP so that, mobility and/or cell sei ection/re- sei ection and/or radio resource management (RRM) can be better managed. In another embodiment, TRS can be used as a supplementary tracking signal for time and/or frequency tracking to be used in addition to the SSB.

[0058] In another embodiment, the CSI-RS and/or TRS configuration indication may include one or more of:

[0059] 1) Time and/or frequency domain resource (e.g., the bandwidth

(BW) in physical resource blocks (PRBs), symbol indexes in a slot). In one example, the BW can be as large as the initial downlink (DL) bandwidth part (BWP). In another example, BW maybe the same as Control Resource Set (CORESET) 0, which is used for scheduling the remaining system information. The PRB allocation may be contiguous or non-contiguous. If more than one symbol is used, one or more symbols configured in a slot can be contiguous or non-contiguous. Non-contiguous symbols can be X symbols apart, where X can be 2, 3, 4, 5, 6, or 7 symbols. In one example, the 5^th and 9^th symbols in the slot are used for CSI-RS or TRS transmission.

[0060] 2) Periodicity. The periodicity may configured to be, for example, 5/10/20/40/80 ms. [0061] 3) Duration (may also be called burst duration). This indicates transmission length of a one-shot transmission of CSI-RS or TRS, which can be one slot or multiple contiguous slots. For example, a one-shot CSI-RS or TRS transmission may occupy 2 slots, where in each slot the same symbol indexes are used.

[0062] 4) Repetition number. This indicates in each periodic occasion, the number of times the CSI-RS or TRS is repeated. The number of repetitions may be, for example, 1-16. For example, a duration of 2 slots and repetition number 4 indicates that the overall CSI-RS or TRS transmission in each periodic occasion would span total 8 slots.

[0063] 5) Offset with respect to a reference point, e.g., the SSB or system frame boundary. This provides the location in time with respect to a reference point to indicate the occasion of periodic transmission. The offset can be expressed in slots or symbols or in ms. Such an offset can be 10 ms with respect to the slot where the SSB of the current/first cell is received.

[0064] 6) RS density, e.g., how many resource elements (REs) per PRB.

In one example, there can be K REs per PRB, where K < 12. In one specific example, K can be 3 or 4 or 6.

[0065] 7) Number of antenna ports. In one example, only a single port can be configured; in other examples multiple ports may be configured. The UE may assume all REs for transmission of the CSI-RS or TRS in a given slot use the same antenna port.

[0066] 8) Whether transmission is periodic, semi-persistent, or aperiodic.

In one example, if the transmission is semi -persistent, the semi-persistent transmission can be activated when the SI is scheduled using a SI-RNTI. In another example, an aperiodic CSI-RS or TRS may be triggered by one or more of a downlink control information (DCI) scheduling SI, a paging DCI, a Wakeup signal (WUS) received before the paging occasion etc.

[0067] 9) Sequence scrambling identifier (ID) or a configurable ID. This ID is used to initialize the pseudo-random sequence generator.

[0068] In another embodiment, one or multiple CSI-RS or TRS configurations can be provided by the SI. A configuration may be associated with a group of POs, and each group may comprise one or more POs. The configuration may include one or more of the parameters as listed above. In one example, the periodicity can be N times the paging DRX cycle length, N can be 1, 2, . . .etc. For N :::: 1, CSI-RS or TRS is periodically configured where the periodic occasion can be an offset before the start of the group of POs. Hence, here the start of group of PO is taken as the reference point to obtain the offset.

In one example, the configuration of CSI-RS or TRS associated with a group of POs can be included the configuration that provides paging related higher layer parameters.

[0069] In one embodiment, UE may assume one or more CSI-RS or TRS configurations, which can be UE-specific, group-specific, or cell-specific.

The CSI-RS or TRS configurations may be configured in RRC-connected mode, as active in the idle/inactive mode. This may be valid when the UE transitions to the idle mode from the connected or inactive mode, or transitions to the inactive mode from the connected mode. In another embodiment, if such a configuration is active in the idle/inactive mode, the UE may ignore the initial CSI-RS or TRS transmission configuration provided by the SI. In another example, the SI or higher layer RRC configuration of the CSI-RS or TRS in the connected mode may include a parameter that may indicate whether the configuration can still be active in the idle/inactive mode. In one example, only a non-zero power CSI-RS configuration may be used in the idle/inactive mode.

[0070] In one embodiment, the CSI-RS or TRS resource is only- monitored by the UE if the periodic occasions of the CSI-RS or TRS overlap with a preparation time/period before the PO. The UE may avoid monitoring of the CSI-RS or TRS resource if the transmission occasion overlaps with a minimum time gap before the PO. During minimum time gap, the UE prepares hardware to wakeup and receive the paging DCI. The UE may report the minimum time gap as the capability.

[0071] In one embodiment, the CSI-RS or TRS transmission used in the idle/inactive mode may also include an SI change notification. [0072] In another embodiment, the CSI-RS or TRS may not always be transmitted in the configured occasion. In one example, if the CSI-RS or TRS is configured in association with the PO and not detected by the UE, then the UE does not wakeup for the next PO. [0073] In one embodiment, information can be provided to the UE that in one or more of the configured TRS and/or CSI-RS occasions following an SSB or during or before a PO, a TRS and/or CSI-RS transmission will be available.

Availability information indicates whether or not a TRS and CSI-RS will be actually transmitted on those occasions, and if indicated as being available, the UE may not perform blind detection on those occasions as the UE determines that a signal (the TRS or CSI-RS) is present. In one example, the availability of the TRS and/or CSI-RS in those occasions can be indicated to the UE by higher layer signalling, such as by a SIB or MIB, or by the DCI where the cyclic redundancy check (CRC) is scrambled by SI or P-RNTI or by another dedicated group RNTI.

[0074] In another example, if the DCI uses a CRC scrambled by a SI- RNTI, one or more of the reserved bits can be used to indicate the availability information. Alternatively, one or more of the fields in the DCI can be repurposed or reinterpreted, or a particular combination of code points in one or more fields in the DCI can be used to indicate the availability of the TRS and/or CSI-RS transmissions in one or more occasions. In yet another example, if a DCI is used in which the CRC is scrambled by a P-RNTI, one or more of the reserved bits can be used to indicate the availability information. Alternatively, one or more of the fields in the DCI can be repurposed or reinterpreted, or a particular combination of code points in one or more fields in the DCI can be used to indicate the availability of the TRS and/or CSI-RS transmissions in one or more occasions. In another example when a DCI is used in which the CRC is scrambled by a P-RNTI, the TRS availability can be indicated, or activated or deactivated, if the Short Message Indicator field indicates ‘00’ (which is reserved in the existing design). Alternatively, if the Short Message Indicator field indicates ‘01 ’, ‘ 10’, or ‘ 11’, the UE may assume one or more of the following TRS and/or CSI-RS occasions are available or available for the following occasions until another signalling, such as higher layer or DCI, deactivates the availability. In another example, detection of a DCI with a CRC scrambled by the P-RNTI and reception of a paging indication or wake-up signal/paging early indication before the PO indicating the UE is to wakeup and monitor the DCI with the CRC scrambled by the P-RNTI during the PO may implicitly indicate to the UE that one or more of the following TRS and/or CSI- RS occasions is available.

[0075] In one embodiment, if a DCI includes availability indication, e.g., whether the UE would assume or expect that the TRS/CSI-RS in one or more of the configured occasions will be transmitted or not, a timer or duration can be configured by higher layer signalling or specified in standards, or the timer/ duration can be included in the DCI. The timer/ duration indicates for how long the indication remains effective or UE’s assumption on the presence or absence of the TRS/CSI-RS at the configured occasions is to remain valid. In one example, upon expiry of the timer, the UE may fall back to a pre-defined or default or configured state. In one example, the availability indication may apply towards one or more of the configured occasions subsequent to receiving the DCI, e.g., the availability indication may apply for the occasions starting from next slot after receiving the DCI. In one example, the DCI may comprise a DCI format in which the CRC is scrambled by the P-RNTI, the SI-RNTI, or any other configured group RNTI, e.g., if the DCI is also used as paging early indication or wake-up signal.

[0076] Following examples can be considered for the embodiment:

[0077] The default state is that the UE assumes/expects the TRS/CSI-RS at the configured occasions is not available, e.g., will not be transmitted. When the UE receives the availability indication in a DCI, the availability indication may indicate the UE to assume/expect that the TRS/CSI-RS will be transmitted/a vail able in subsequent configured occasions, either for a configured duration, until a timer expires, or until the next DCI indicates that the TRS/CSI- RS will not be available/transmitted. Upon expiry of the timer, at the end of the duration, or in response to reception of a DCI that indicates unavailability of the TRS/CSI-RS at the configured occasions, the UE again enters default state. In other words, when the UE is in a default state in which the TRS/CSI-RS are assumed not available at the configured occasions, a DCI may “activate” availability of the TRS/CSI-RS transmission at the configured occasions, and the activation applies for a configured duration, until a timer expires, or until another DCI “deactivates” the availability .

[0078] The default state is that the UE assumes/expects the TRS/CSI-RS at the configured occasions is available, e.g., will be transmitted. When the UE receives the availability indication in a DCI, the availability indication may indicate the UE to assume/expect that the TRS/CSI-RS will not be transmitted/available in subsequent configured occasions, for a configured duration, until a timer expires, or until the next DCI indicates that the TRS/CSI- RS will be avail able/transmitted. Upon expiry' of the timer, at the end of duration, or in response to reception of a DCI that indicates availability of the TRS/CSI-RS at the configured occasions, the UE again enters the default state. In other words, when the UE is in a default state in which the TRS/CSI-RS are assumed available at the configured occasions, a DCI may “deactivate” availability of the TRS/CSI-RS transmission at the configured occasions. The deactivation applies for a configured duration, until a timer expires, or until another DCI “activates” the availability.

100791 In one example, the timer value or duration can be configured/indicated by higher layer signalling such as a SIB, or multiple configured or specified values may be used and the DCI may dynamically indicate the value of time/duration from the configured or specified set of values. In one example, a timer or duration may span one or more POs, one or more paging cycles, or one or more frames. In another example, the tinier and duration can be expressed in ms or in symbols/slots based on the numerology of the initial DL BWP or based on a configured/indicated numerology provided in a higher layer signalling such as a SIB. In one example, when the UE receives the TRS/CSI-RS configuration as part of higher layer signalling such as a SIB, the UE may assume one a) the default state is that a TRS/CSI-RS at the configured occasions is not available or b) the default state is that the TRS/CSI-RS at the configured occasions is available; alternatively, a) or b) may be indicated implicitly or explicitly. For an explicit indication, a parameter may indicate what default state the UE is to assume, e.g., either available or not available. In one example, the parameter maybe included as part of the TRS/CSI-RS configuration. For an implicit indication, the UE may assume that the presence of a TRS/CSI-RS configuration indicates the default state regarding the availability. In another example, if a TRS/CSI-RS configuration is provided, the standards may specify what default state regarding availability to assume for the TRS/CSI-RS transmission at the configured occasions. In one example, the duration or timer may not be configured or explicitly indicated and the DCI may only indicate availability or unavailability of the TRS/CSI-RS at the occasions until the end or beginning of next one or more paging cycles or the beginning of next one or more POs or one or more frames. In another example, the DCI may indicate whether the TRS/CSI-RS is to be transmitted at one or more occasions before each PO from a set of subsequent POs or before a set of POs. For example, the indication may apply to the next N => 1 POs within the current paging frame or multiple paging frames, where the value of N can be configured by higher layer signalling. In particular, the indication of availability may apply to M => 1 occasions before each PO in a set of POs or before a set of POs, and for other occasions, the UE may assume the TRS/CSI-RS may not be available or the UE may avoid monitoring.

[0080] In one example, if the DCI comprises a DCI format in which the CRC is scrambled by a P-RNTI, one or more of fields can be used or repurposed/reinterpreted to indicate availability indication and/or value of duration/timer. These fields include: 1) short message indicator, 2) short messages, 3) frequency domain resource assignment, 4) time domain resource assignment, 5) VRB-to-PRB mapping, 6) modulation and coding scheme (MCS), 7) transport block (TB) scaling, 8) reserved bits.

[0081] In one extension of the above example, when the DCI carries only paging scheduling information, one or more bits from the short messages field can be used for the indication. This indication may apply for a UE following Rel-17 specifications; a legacy UE following prior specifications may instead identify the short messages field as reserved in this case. In another variant, when the DCI carries only a short message, one or more fields numbered from 3 to 7 in the list above can be used for the indication. This indication may apply for a UE following Rel-17 specifications; a legacy UE following prior specifications may identify those fields as reserved in this case. In another variant, a simple w<ay to include the indication is using one or more bits from the reserved bits, specifically if the flexibility of providing the indication is to be used regardless of whether a DCI schedules a short message and/or paging information.

[0082] In one example of the embodiment, the availability indication can be provided as part of the TRS or CSI-RS configuration. The presence of the parameter in the configuration, or if the indication is TRUE, may notify the UE of a TRS or CSI-RS transmission in one or more of the transmission occasions associated with the configuration. If the availability indication is provided and is FALSE, the UE may perform blind detection at the configured occasions since the TRS or CSI-RS may or may not be transmitted at the occasions, e.g., availability is unknown to the UE.

[0083] In the next section, embodiments describe that the TRS/CSI-RS transmission can be used as paging early indication or wakeup signal when the availability indication is FALSE. In another example, the availability indication may apply to a subset of the transmission occasions of a configuration.

[0084] Wake-up Signal (WUS) transmission in idle/inactive mode [0085] One source of power consumption during the idle/inactive mode for a NR UE is when the UE wakes up but does not receive paging message or identifies that a paging message is not intended for the UE. A WUS is introduced for a NR UE in the idle/inactive mode, at least when standalone NR transmission is used. Note that a WUS may also be referred to as a paging early indication (PEI), e.g., a WUS may indicate to the UE whether the UE may expect to receive a paging message in the next PO.

[0086] In one embodiment, the SI may include a configuration of a WU S to be monitored before the PO. In one example, the MIB in a PBCH or SIBx (where x = 1, 2, 3,... etc.) may include the configuration of the WUS. In one embodiment, the WUS may be cell-specific, e.g., addressing all the POs, or group-common and addressing a group of POs in a paging discontinuous reception (DRX) cycle. A given UE may monitor only one PO per paging DRX cycle. In one example, the UE can be configured such that when the UE detects a W US, the UE monitors the following mumPOs POs or optionally, until a paging message including the UE's (non-access stratum) NAS identity is received, whichever is earlier. This may be applicable when extended DRX is used. Here, numPOs refers to a number of consecutive POs mapped to one WUS provided in the system information where (mumPOs>V).

[0087] In another embodiment, multiple WETS occasions may be configured corresponding to a single PO. In such a case, a sub-grouping of the set of UEs sharing a PO can be achieved based on a LIE-ID to reduce “false wake-up events” whereby an unintended UE may be woken up although there may not be any paging for the UE. These multiple WUS occasions may be multiplexed within the corresponding DL BWP (e.g., the initial DL B WP) using a combination of one or more of: time-division multiplexing (TDM), frequency- division multiplexing (FDM), or code-division multiplexing (CDM). Each WUS is associated with a sub-group in the above example. Here, if the WUS corresponding to a sub-group is detected, the detection may imply that UEs belonging the sub-group wakeup in the next PO and expect to receive a paging DCI.

[0088] As an extension of the above embodiment, a group of occasions (e.g., comprising one or more occasions) to be monitored for sub-group specific

WUS may occur, where the monitoring of the group of occasions starts after a reference point, which can be at an offset before the start of the PO. The offset can be a UE capability or configured by higher layer signalling and can be expressed in slots for a given numerology or expressed in ms, such as

60ms. The UE may indicate multiple values via capability signalling. If one or more of the occasions of the group of occasi ons of the WUS overlap with the minimum gap for the UE to wakeup before the PO starts, the UE may not monitor those occasions. In one example, once a WUS is detected, the UE in the sub-group may not monitor the corresponding WUS in the remaining occasions. Alternatively, the UE may still monitor all the valid occasions and the later detected WUS may override the indication of a previously detected WUS before a given PO. In another alternative, the UE does not expect WUS detected on different occasions before a PO to indicate different information.

[0089] In another embodiment, a sequence-based WUS or PEI may include UE sub-group information, such as if the UE detects a first (second) sequence, the sequence may indicate a first (second) sub-group. Based on which sequence is detected, the UE may identify whether the UE is to wakeup for the next PO, e.g., whether the WUS corresponding to the sub-group to which the UE belongs is or is not received. The UE may be configured to try to detect, up to N sequences for the WUS before a given PO, where N is a positive integer, e.g., N can be 1, 2, 3... 10.... In one example, information of M sub-groups can be conveyed via a sequence-based WUS or PEI where M = log2(N), e.g., depending on which sequence is detected, UEs belonging to M sub-groups associated with the WUS or PEI may identify whether or not to monitor the next PO for paging reception. As an option, detection of a sequence among the N sequences indicates a bitmap comprising M bits, where each bit corresponds to a sub-group and reflects whether or not the UEs belonging to that sub-group are to monitor the next PO (e.g.,

monitor next PO,

not monitor next PO). [0090] In one example, if the UE does not detect a WUS, the UE can avoid monitoring the following PO(s). In another example, if the UE missed a WUS occasion (e.g. due to cell reselection), the UE may monitor every PO until the start of next WUS or until a configured window ends.

[0091] In one embodiment, the WUS can be sequence-based, such as a pseudo-random noise (PN)/Gold sequence, Constant Amplitude Zero Autocorrelation (CAZAC) sequence, M-sequence, or PDCCH-based. In one embodiment, the configuration of a sequence-based WUS may include one or more of the following:

[0092] Time and/or frequency domain resource (e.g,, BW in PRBs, symbol indexes in a slot). In one example, the BW can be as large as the initial DL BWP. In another example, the BW may be the same as CORESET 0, which is used for scheduling the remaining system information or the CORESET where a paging DCI can be received. The PRB allocation may be contiguous or non- contiguous. If more than one symbol is used, one or more symbols configured in a slot can be contiguous or non-contiguous. If contiguous, then up to 14 symbols can be used. Non-contiguous symbols can be X symbols apart, where

X can be 2, 3, 4, 5, 6, or 7 symbols. In one example, the 5^th and 9^th symbols in the slot can be used for WUS transmission. In one example, a Resource ID can be conveyed to the UE, which can be used if the UE monitors multiple W USs. [0093] WUS Duration (may also be called burst duration). The WUS duration indicates a transmission length of one transmission of a W US, which can be one slot or multiple contiguous slots. For example, a one-shot WUS transmission may occupy 2 slots, where in each slot the same symbol indexes are used. [0094] Repetition number. The repetition number indicates how many times the WUS is repeated. The repetition number is ≥ 1, e.g., can be 1, 2, 3, ..., 7, 8. ..., 16. For example, a duration of 2 slots and repetition number 4 indicates that the overall WUS transmission spans a total of 8 slots. In one example, repetitions can be absorbed within the WUS duration, e.g., a WUS duration of X slots may indicate a WUS in a slot is repeated over X≥1 consecutive slots, where the symbol indexes in the slots remain the same.

[0095] The time offset between the end of a WUS and start of the first PO of the mumPOs POs the UE is to monitor. The time offset can be obtained in a number of slots based on the numerology of the Div BWP or in ms. The time offset can be used to identify the start of the WUS.

[0096] The time offset before the PO to indicate the start of the WUS transmission or slot after which the UE starts monitoring for the WUS. The time offset before the PO can be obtained in a number of slots based on the numerology of the DL BWP or in ms.

[0097] Density, e.g., how many REs per PRB. In one example, there can be K REs per PRB used for WUS transmission, where K < 12. In one specific example, K can be 3, 4 or 6. Alternatively, all REs in the PRBs in the allocated BW may be used for WUS transmission, e.g., the WUS transmission is contiguous in frequency domain.

[0098] Scrambling ID or group ID

[0099] In some embodiments of the above, a TRS or CSI-RS or SSS~ based sequence configuration can be provided to the UE, where the configuration would include an identification that the signal can be used as WUS/PEI. If such an indication/identifier is included in the configuration, the UE may monitor only the occasions of the sequence transmission before the corresponding PO, such as at an offset before the PO for the purpose of PEI/WUS. The UE may or may not monitor the occasions, if any, before the offset. Even if the UE monitors occasions before/outside the offset, the occasions are not used at the WUS/PEI and may only be used in some embodiments for time/frequency tracking and/or measurements. The occasions used for the WUS/PEI can also be used for time/frequency tracking and/or measurements. In one example, the periodicity may or may not be provided as part of the configuration. If not provided, the UE may merely monitor occasion(s) at the configured offset before the PO for providing the PEI/WUS.

If provided, the UE may only consider the occasion(s) located after the start of an offset with respect to the PO or within a window before the PO for the PEI/WUS, and the UE may not consider the other occasions outside the window or before the offset for the providing the PEI/WUS. The occasions before or after the offset can be used for time/frequency tracking and the UE may only consider the occasion(s) after the offset. for the purpose of providing the PEI/WUS. For example, the TRS or CSI-RS at the occasion(s) after the start of offset before the PO may not be transmitted if the UE is not expected to receive a paging DCI.

[00100] In one embodiment, if an availability indication is provided in the TRS/CSI-RS configuration and is identified as “FALSE”, the UE may assume the TRS/CSI-RS transmission can be used as the PEI/WUS and that the TRS/CSI-RS may or may not be transmitted at the occasions before the PO, e.g., may only be transmitted if the UE expects to receive a paging DCI. If the availability indication is “TRUE”, this indicates the TRS/CSI-RS transmission may be provided at the configured occasions and may not be used as the PEI/WUS. [00101] In another embodiment, if a sequence-based (such as a TRS/CSI-

RS/SSS) configuration includes an identifier that the sequence-based may be used as a WUS/PEI, the UE may ignore the periodicity (e.g., refer to the list of parameters provided under the section configuration of the TRS/CSI-RS) of the sequence transmission, if included, in the configuration and would assume the occasion(s) may only be present or be valid for WUS/PEI monitoring located after the start of an offset with respect to the PO the UE is associated with. [00102] In one embodiment, if a sequence-based WUS transmission comprises multiple symbols in a slot, sequences mapped to different symbols can be same (e.g., repeated) or different (e.g., sequence generation is function of symbol index). In another example, depending on sequence length and allocated BW for the WUS transmission, it may be possible that entire sequence is mapped over multiple symbols in a slot or a number of contiguous slots.

[00103] In another embodiment, the WUS transmission may be similar to the TRS signal structure, e.g., 3 REs per PRB is used for the PRBs in the BW and 2 symbols in a slot are used for transmission where the symbols used are 4 symbols apart. The WUS transmission may also use same sequence generation approach as the TRS (cf 38.21 1). In yet another embodiment, the WUS transmission may be similar to a SSS signal structure, e.g., a certain number of contiguous sub-carriers (e.g., 127) are used in a symbol for sequence mapping. In one example, the sequence can be repeated in one or more symbols in the slot.

[00104] In one embodiment, if the WUS is PDCCH-based, the configuration may include one or more of the following: 1) CORESET and search space configuration. The search space can be common search space, such as type 0, 0A, 1, 2. 2) an offset with respect to PO where the UE starts monitoring for the WUS PDCCH. 3) RNTI for monitoring the PDCCH. The RNTI can be a common RNTI.

[00105] A PDCCH-based WUS may be configured such that the UE monitors for the PDCCH in one or more consecutive slots with valid PDCCH monitoring occasions (MOs) configured as part of the search space set, starting from the first WUS monitoring occasion as indicated by the offset with respect to a PO. This can be achieved by utilizing the “duration” field, provided as part of the search space set configuration, or provided to the UE using a separate parameter as part of the SI.

[00106] In one embodiment, the UE may be configured to monitor either or both a cell-specific or group-common WUS transmissions. Upon detecting either of the cell-specific or group-common WUS transmissions, the UE may monitor the associated one or more POs. [00107] In one embodiment, the offset to identify the first monitoring occasion of a PDCCH-based WUS or PEI can be a UE capability or configured by higher layer signalling and can be expressed in slots for a given numerology or expressed in ms, such as 1, 2, , 60ms. The UE may indicate multiple values via capability signalling. If one or more of the occasions of the WUS overlap with the minimum gap for the UE to wakeup before the PO starts, the UE may avoid monitoring those occasions.

[00108] In another embodiment, the WUS provides information about the offset to start of PO from the end of WUS, and optionally which BWP the EE is to switch to for receiving a paging message. In one example, the BWP for paging message reception can be larger or smaller than the BWP where the WUS is detected, if the BWPs are not the same. In another embodiment, the WUS is monitored in a different BWP than the initial DL BWP, and potentially the WUS monitoring BWP can be smaller/narrower than the initial DL BWP. In one example, upon detecting the WUS in the narrow BWP, the UE may switch back to the default/initial DL BWP for receiving the paging message.

[00109] In another example, a sequence-based WUS can also be used for cell measurement and/or channel tracking before the PO. This may lessen the number of SSBs monitored prior to the PO so that sensitivity to the carrier frequency offset (CFO) remains low for paging DCI reception. This may also facilitate increased power saving since the UE could potentially skip some slots for SSB monitoring. If the WUS is also used for channel tracking, the WUS signal structure can be based on one or a combination of TRS, PSS, SSS transmission resource mapping and sequence design.

[00110] In one embodiment, before the PO, the UE can be configured with a preparation period during that the UE may perform one or more of a predetermined number of SSB monitoring, optionally CSI-RS/TRS occasion monitoring, and/or WUS reception. The preparation period may include or exclude a minimum time gap before the PO during which the UE prepares hardware for waking up and receiving the paging message. In one example, during the minimum time gap reported by the UE capability, the UE may avoid monitoring the WUS or any other transmissions from the network. The minimum time gap can be obtained as the time gap between the end of slot where the WUS transmission ends or the last WUS monitoring occasion exists and start of the PO, and can be expressed in ms. The UE may report one or multiple values of the minimum gap. Possible values include 0 ms, 1 ms, , 20 ms. In another embodiment, the minimum gap may be indicated in terms of a minimum number of SSB occasions that may fall within the period from the end of the WU S an d the start of the PO .

[00111] FIG. 3 illustrates synchronization timing in accordance with some embodiments. In particular, the top portion shows an example in which without the WUS, the number of SSBs to be monitored during preparation window is higher than that in the bottom portion, when the WUS is configured and also used for tracking. In particular, in the top portion, K SSBs are monitored before the PO so that the paging DCI can be received with synchronization in place; in the bottom portion, in which the M SSBs (2 as shown) are monitored - M can be much less than K. For providing tracking functionality, the WUS signal can be mapped to multiple symbols and/or slots, where symbols in the slot can be non- contiguous.

[00112] In one embodiment, for a PDCCH-based WUS, the paging DCI can be used as the WUS and only the paging PDSCH is received during the PO. In this example, the paging DCI is monitored at an offset with respect to the PO, e.g., there is a gap between the PDCCH containing the paging DCI and the corresponding paging PDSCH. In this example, if the paging DCI or the WUS is not received such as during the preparation period after the UE starts monitoring for the PDCCH, the UE does not expect to receive the PDSCH during the PO. In another embodiment, the PDCCH-based WUS carries a newly defined DCI format with a fixed or configurable payload. Alternatively, DCI format 1_0 may be reused with fixed value of certain bit-fields and reinterpretation of other bit-fields, with the identification based on the use of a new RNTI (WUS-RNTI). Further, such a DCI format may indicate one or more of all or part of scheduling information for the paging PDSCH, triggering and corresponding resource information for TRS/CSI-RS transmissions that may be provided during the time gap between the end of the WUS and the start of the PO, the identity of a UE sub-group that corresponds to a sub-group within the group of UEs sharing a PO, etc. The UE sub-groups can be created based on the UE ID and a configured or specified number of sub-groups to reduce “false paging/waking up” events. Accordingly, such a mapping between the UE sub- groups and the corresponding indexing can be specified or configured by system information, and conveyed to the UE using an N-bit bit-field (allowing for

sub-groups) in the PDCCH-based WUS. [00113] In one example, if the PDCCH-based WUS indicates a sub-group index, several methods can be considered: 1) a field in the DCI can be configured to include a bitmap, where each bit corresponds to a sub-group. If the bit value is 0 (value is 1), UEs corresponding to the sub-group may skip the next PO (wakes up in the next PO) for monitoring the paging DCI or vice versa, or 2) an explicit field may not be used, instead separate RNTIs can be considered with respect to different sub-groups for detecting the PDCCH-based WUS or PEI. Alternatively, 3) separate time/frequency resources can be considered to associate PDCCH monitoring occasions with respect to a sub-group, e.g., UEs belonging to different sub-groups monitor a PDCCH based over separate time/frequency resources.

[00114] In one embodiment, the WUS transmission is dropped if there is a SSB occasion is the slot. In this case, the UE wakes up for the next PO. In one example, if the UE is to skip a WUS transmission occasion such as due to overlap with another signal or due to invalid monitoring occasions, the UE wakes up in the next PO.

[00115] In one example, once a PDCCH based WUS is detected, the UE may avoid monitoring the corresponding WUS in the remaining occasions. Alternatively, the UE may still monitor all the valid occasions and the later detected WUS may override the indication of a previously detected WUS before a given PO. In another alternative, the UE does not expect a WUS detected on different occasions before a PO to indicate different information.

[00116] In one embodiment, both a WUS or PEI and a paging DCI may indicate UE sub-grouping information. For example, the PEI may indicate first sub-group information, and the paging DCI may provide further sub-grouping information within the indicated first sub-group. The first sub-group indicated by the PEI may include N ≥1 UEs, and a later paging DCI indicates paging information for M UEs within the indicated sub-group of N UEs, M < N. In this example, UEs belonging to the sub-group(s) indicated by the WUS or PEI monitor for the paging DCI during the PO at the corresponding occasions, and the paging DCI further indicates which sub-group(s) within the sub-group(s) indicated by the WUS or PEI may receive a paging message or a paging PDSCH. In one embodiment, a WUS or PEI is detected and indicates a set of sub-groups, such as M sub-groups. UEs belonging to the set of sub-groups e.g., M sub-groups, monitor the paging DCI during the next PO where the paging DCI further indicates UEs belonging to which sub-groups among the set of M sub-groups would receive a paging PDSCH.

[00117] FIG. 4 illustrates a method for UE sub-group identification in accordance with some embodiments. In the two-step method shown in FIG. 4 UEs identify whether they belong to a sub-group for which a paging PDSCH is expected. As shown, the WUS/PEI indicates sub-group set # 2 which corresponds to M sub-groups, and the paging DCI further indicates UEs of which sub-groups among the M sub-groups would receive the paging PDSCH. Indication of which sub-groups among M sub-groups would receive PDSCH can be done via a M-bit bitmap in a field in the paging DCI; for example, reserved bits in the paging DCI can be used for this purpose. A WUS/PEI can be associated with a sub-group set or may include information for multiple sub- group sets. In this example, K sub-group sets share a common PO. A given WUS/PEI could indicate information of one or more of the K sub-group sets. In one embodiment, one WUS/PEI may be associated with one of the K sub-group sets, e.g., the network could send multiple WUS/PEIs to convey information to all the UEs sharing the PO. WUS/PEIs corresponding to different sub-group set indexes can be multiplexed in time, frequency and/or code domain from the network perspective. Alternatively, a given WUS/PEI may indicate information for a sub-set or all of the K sub-group set indexes; a given detected sequence may indicate the status of the sub-sets or all of the K sub-group set indexes, e.g., whether UEs belonging to a sub-group set are to monitor the PO or not, and in one example, this can be obtained by mapping each sequence of all the possible/valid sequences to a bitmap, where each bit in bitmap corresponds to a sub-group set and indicates the corresponding UE whether to monitor PO.

[00118] Power Saving during PO [00119] In one embodiment, a configuration can be provided by an SI that the UE expects cross-slot, scheduling when a paging DCI is received. This indicates a PDSCH corresponding to the paging DCI is delivered after the slot where the paging DCI is received. This may enable increased power saving during the PO. In another embodiment, the offset between the paging DCI and the paging PDSCH is extended so as to enable the paging PDCCH to be utilized as a WUS. In such a case, the WUS may be configured to be monitored at the PO or within a number of slots starting or ending at a given PO, with the paging PDSCH scheduled using a scheduling offset that may be provided to the UE via a combination of higher layer signaling (e.g., via system information) and the KO-slot offset bit-field in the paging DCI.

[00120] The minimum value of the slot-offset (e.g., the PDSCH is received after a number of slots from the slot where the DC 1 is received) can be indicated by higher layer configuration such as an SI, or may be indicated by a DCI such as a DCI with a CRC scrambled by an SI-RNTI or WUS that can be sequence- or PDCCH-based. The UE expects the indicated slot-offset value for PDSCH scheduling in the paging DCI to be same or larger than the indicated minimum value of the slot-offset.

[00121] In another embodiment, the paging DCI can be received in a first BWP and the corresponding PDSCH is delivered in a second BWP. In one embodiment, the paging DCI may include a BWP indicator field, and the corresponding PDSCH may be delivered in a different BWP than the BWP where paging DCI is received. In another embodiment, there may not be any BWP indicator field included in the paging DCI and an SI may provide configuration of a BWP that is used for paging PDSCH reception.

[00122] In one embodiment, the paging DCI includes UE sub-grouping information, e.g., includes indication of the sub-groups that expect to receive the PDSCH, the corresponding PDSCH may be received after an offset from the paging DCI, e.g., cross-slot scheduling of the PDSCH may be configured or assumed if the paging DCI includes UE sub-grouping information. The offset between the PDCCH of the pagi ng DCI and the PDSCH can be configured by higher layer signaling.

[00123] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00124] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art. upon reviewing the above description. [00125] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00126] The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1 .72(b), requiring an abstract, that, will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

What is claimed is:

1. An apparatus for a 5^th generation NodeB (gNB), the apparatus comprising: processing circuitry configured to: encode a system information block (SIB) for transmission to a user equipment (UE), the SIB containing a tracking reference signal (TRS) configuration that includes TRS occasions for detection by the UE while in at least one of an idle or inactive mode and a wakeup signal

(WUS) configuration; encode, for transmission to the UE while the UE is in the at least one of the idle or inactive mode, a WUS based on the WUS configuration, the WUS configured to indicate whether to expect to receive paging downlink control information in a next paging occasion

(PO); and encode, for transmission to the UE, a TRS transmission configured in accordance with the TRS configuration for at least one of time or frequency tracking in addition to synchronization signal block (SSB)-based tracking; and a memory configured to store the response.

2. The apparatus of claim 1, wherein the TRS configuration includes a time and frequency domain resource of the TRS transmission that indicates a first symbol of the TRS transmission, a starting resource block of the TRS transmission, a number of resource blocks of the TRS transmission, a scrambling identification (ID) of the TRS transmission, and a periodicity and offset of the TRS transmission. 3. The apparatus of claim I, wherein the SIB includes multiple TRS configurations.

•4. The apparatus of claim 3, wherein each TRS configuration is associated with a different group of POs.

5. The apparatus of claim 1, wherein the WUS is sequence-based, selected from a pseudo-random noise (PN) or Gold sequence, a Constant Amplitude Zero Autocorrelation (CAZAC) sequence, an M-sequence, or a physical downlink control channel (PDCCH)-based sequence.

6. The apparatus of claim 1, wherein the processing circuitry' is further configured to decode from the UE a minimum time gap that indicates a time for the UE to wakeup and receive a paging downlink control information (DCI) prior to a PO, the minimum time gap indicating a time over which the UE is unable to monitor a TRS resource.

7. The apparatus of claim I, wherein the processing circuitry is further configured to encode to the UE availability information that, the TRS transmission is to be available in one or more of configured TRS occasions following an SSB or during or before a PO, the availability information indicated by downlink control information (DCI) having a cyclic redundancy code (CRC) scrambled by a Radio Network Temporary' Identifier (RNTI), the RNTI comprising one of a paging RNTI (P-RNTI), a system information (SI) RNTI (SI-RNTI), or dedicated group RNTI, a timer in higher layer signalling or the DCI indicating a length of time the availability information remains valid and after which the UE is to fall back to a default state.

8. The apparatus of claim 7, wherein the default state is one of a first expectation that. TRS transmissions are not available at the one or more of configured TRS occasions unless otherwise indicated by a most recent DCI before the one or more of configured TRS occasions within a time period of the timer, or a second expectation that TRS transmissions are available at the one or more of configured TRS occasions unless otherwise indicated by the most, recent DCI before the one or more of configured TRS occasions within the time period of the timer.

9. The apparatus of claim 8, wherein: a value of the timer is configured by one of higher layer signalling, or by the DCI in response to multiple configured timer values, and the one of higher layer signalling contains a parameter that indicates which of the first expectation or the second expectation the UE is to apply as the default state.

10. The apparatus of claim 1, wherein: the processing circuitry is further configured to encode for transmission to the UE availability information that the TRS transmission is to be available in one or more of configured TRS occasions following an SSB or during or before a PO, the availability information or a timer indicating a length of time the availability information remains valid and after which the UE is to fall back to a default state is indicated by downlink control information (DCI) having a cyclic redundancy code (CRC) scrambled by a Radio Network Temporary Identifier (RNTI), the RNTI comprising one of a paging RNTI (P-RNTI), a system information (SI) RNTI (SI-RNTI), or dedicated group RNTI, and at least one of: the availability information is configured to indicate availability or unavailability of the TRS transmission at the one or more of the configured TRS occasions until an end or beginning of a next one or more paging cycles, or a beginning of a next one or more POs or one or more frames, the DCI configured to indicate the TRS transmission is to be provided for one or more occasions before each PO from among a set of subsequent POs or before a set of POs, or the one of the availability information or the timer is indicated by repurposed information in the DCI, and the repurposed information indicated in at least one field selected from: a short message indicator, short messages, a frequency domain resource assignment, a time domain resource assignment, a Virtual Resource Block (VRB)-to-Physical Resource Block (PRB) mapping, a modulation and coding scheme, a transport block scaling, or reserved bits.

11. The apparatus of claim 1, wherein the WUS configuration indicates to monitor POs until an earlier of: a last of a predetermined number of the POs following the WUS is monitored and a paging message including a non-access stratum identity of the UE is received.

12. The apparatus of claim 1, wherein the processing circuitry' is configured to multiplex multiple WUS occasions within a single downlink bandwidth part using one or more of: time-division multiplexing (TDM), frequency-division multiplexing (FDM), or code-division multiplexing (CDM), each WUS occasion associated with a sub-group of UEs via an identity and configured to indicate to the UEs belonging the sub-group to wake up to monitor a next PO and expect to receive paging downlink control information. 13. The apparatus of claim 12, wherein: a WUS in a given occasion is configured to indicate to the UEs belonging to the sub-group associated with the given occasion to wake up and monitor at least one paging occasion after a reference point at an offset before a start of the next PO, the offset is indicated by one of UE capability or higher layer signalling, and in response to detection of a sub-group WUS, one of: the UEs in the sub- group may avoid monitoring remaining paging occasions, or a later detected WUS overrides an indication of a previously detected WUS before a given PO if the remaining occasions are to be monitored.

14. The apparatus of claim 12, wherein: each WUS includes UE sub-group information is indicated by a different sequence, each sequence conveyed by a bitmap, each bit of the bitmap corresponds to a different sub-group and indicates whether the UEs belonging the sub-group are to monitor the next PO, and the WUS configuration provides an indication of a number of sequences for the UE to try' to detect before a given PO. 15. The apparatus of claim 12, wherein: each WUS includes UE sub-group information is indicated by a different sequence, and a configuration of the sequence indicates at least one of a time or frequency domain resource of the WUS associated with the sequence, a duration of the WUS associated with the sequence, a number of repetitions of the WUS associated with the sequence, a time offset between an end of the WUS associated with the sequence and a start of the next PO, a time offset before the next PO to indicate a start of the WUS associated with the sequence or slot after which the UE is to start monitoring for the WUS associated with the sequence, and a scrambling identification (ID) of the WUS associated with the sequence.

16. The apparatus of claim 1 , wherein the processing circuitry is configured to indicate to the UE to: monitor a particular PO in response to the processing circuitry paging a sub-group of the UE and not monitor the particular PO in response to non- detection by the UE of a WUS transmission in all WUS occasions associated with the particular PO, or monitor the particular PO in response to non-detection by the UE of the WUS transmission in all WUS occasions associated with the particular PO, each WUS transmission configured to indicate whether the UE is to monitor the particular PO.

17. An apparatus for a user equipment (UE), the apparatus comprising: processing circuitry’ configured to, while in at least one of the idle or inactive mode: decode, from a 5^th generation NodeB (gNB), a tracking reference signal (TRS) configuration and a wakeup signal (WUS) configuration, the TRS configuration containing configuration parameters and values for periodic TRS transmissions, determine, based on the TRS configuration, availability information for the TRS transmissions based on a bitmap in which each bit is associated with at least one resource or configuration, and determine, based on detection of a WUS in accordance with the WUS configuration, whether to monitor a next paging occasion (PO) if the UE is paged; and a memory configured to store the TRS and WUS configuration.

18. The apparatus of claim 17, wherein: the WUS configuration includes multiple WUS occasions, each WUS occasion associated with a different sub-group of UEs, and one of: each WUS transmission indicates a particular sub-group, and the processing circuitry is further configured to avoid monitoring a particular PO in response to non-detection of a WUS transmission in all WUS occasions associated with the particular PO, or each WUS transmission indicates whether the UE is to monitor the particular PO, and the processing circuitry is further configured to monitor the particular PO in response to non-detection of the WUS transmission in all WUS occasions associated with the particular PO,

19. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the one or more processors to configure the UE to, when the instructions are executed: while in at least one of the idle or inactive mode: decode, from a 5^th generation NodeB (gNB), a tracking reference signal (TRS) configuration and a wakeup signal (WUS) configuration, the TRS configuration containing configuration parameters and values for periodic TRS transmissions; determine, based on the TRS configuration, availability information for the TRS transmissions based on a bitmap in which each bit is associated with at least one resource or configuration, and determine, based on detection of a WUS in accordance with the WUS configuration, whether to monitor a next paging occasion (PO) if the UE is paged.

20. The medium of claim 19, wherein the one or more processors further configure the UE to, when the instructions are executed: the WUS configuration includes multiple WUS occasions, each WUS occasion associated with a different sub-group of UEs, and one of: each WUS transmission indicates a particular sub-group, avoid monitoring a particular PO in response to non-detection of a WUS transmission in all WUS occasions associated with the particular PO, or each WUS transmission indicates whether the UE is to monitor the particular PO, and monitor the particular PO in response to non-detection of the WUS transmission in all WUS occasions associated with the particular PO.