Wake-up Signal (WUS) Design and Configuration for Paging

Abstract

The present disclosure provides details of sequence-based WUS design and signaling, as well as details of DCI-based WUS design that is also used as scheduling DCI. For sequence-based WUS, there are two variants. The first is based on CSI-RS, which is relatively wideband, so the sequence occupies a wider frequency band compared to SSB transmission. The second is more similar to a secondary synchronization signal (SSS) type of sequence in that it occupies a narrower frequency band over the entire bandwidth.

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, including WUS design and configuration for paging. Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0003] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0004] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency range 1 (FR1) may include frequency bands operating at frequencies below 6 GHz, some of which may be used by previous standards and may potentially be expanded to cover new spectrum products from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 may have a smaller range but potentially higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0006] Figure 1 is a block diagram of a system for wireless communications according to one embodiment.

[0007] Figure 2 is an annotated block diagram of a WUS and corresponding paging frame according to one embodiment.

[0008] Figure 3 is an annotated block diagram of a WUS and corresponding paging frame according to one embodiment.

[0009] Figure 4 is an annotated block diagram of a WUS and corresponding paging frame according to one embodiment.

[0010] Figure 5 is an annotated block diagram of a WUS and corresponding paging frame according to one embodiment.

[0011] Figure 6 is an annotated block diagram of a WUS and corresponding paging frame according to one embodiment.

[0012] Figure 7 is an annotated block diagram of a WUS and corresponding paging frame according to one embodiment.

[0013] Figure 8 is an excerpt from PCCH-Config according to one implementation.

[0014] Fig. 9 is a block diagram according to one embodiment. DETAILED DESCRIPTION

[0015] In 3GPP Release 17 (Rel-17), it is desirable to achieve UE power saving enhancements for idle and inactive modes as well as active mode. Therefore, efforts are being made to study and specify paging enhancements to reduce unnecessary UE paging reception without impacting legacy UEs. Efforts are also being made to specify a way to provide idle / inactive mode UEs with potential Tracking Reference Signal (TRS) / Channel State Information (CSI)-Reference Signal (RS) moments available in connected mode, thereby minimizing system overhead impact.

[0016] Idle mode UEs do not have any RAN context, while inactive mode UEs retain RAN context. However, the typical UE process for receiving paging is similar for idle / inactive UEs. First, the network configures the paging frame (PF) and paging occasion (PO) for radio resource control (RRC) idle or RRC inactive UEs. Second, the UE wakes up at a time before the paging occasion and attempts to acquire time and frequency synchronization. How long the UE wakes up before the paging occasion is a UE implementation detail. Generally speaking, the UE may wake up a few synchronization signal blocks (SSBs) earlier to ensure correct paging downlink control information (DCI) and paging physical downlink shared channel (PDSCH) detection. Third, the UE decodes the DCI scrambled by the P-Radio Network Temporary Identifier (RNTI). If DCI is detected and PDSCH is scheduled, the UE proceeds with PDSCH decoding for the paging message. If the UE does not detect DCI scrambled by the P-RNTI, the UE goes back to sleep.

[0017] When the UE does not get the paging message, the typical UE process will have problems. The UE still performs SSB detection and physical downlink control channel (PDCCH) decoding, which wastes UE power.

[0018] The Paging Indication Channel was introduced in 3GPP Universal Mobile Telecommunications Service (UMTS). In 3GPP UMTS, there is a channel called Paging Indication. The network sends physical layer information (Paging Indication) indicating whether the UE should read higher layer control information on the corresponding control channel, such as a sequence.

[0019] In another attempt, a WUS design is described in the NB-IoT Rel-15 implementation. For example, if a WUS is detected, the UE decodes the PDCCH at the paging occasion. The WUS in the form of a relatively long Zadoff–Chu (ZC) sequence is designed for reliable reception (<1% probability of missed detection). The network is configured to enable or disable WUS, which is an optional feature. If disabled, normal PDCCH monitoring for paging is required (every paging occasion). The design envisions that a low-power receiver in the UE can be used to receive the paging indication WUS without turning on the full receiver chain for PDCCH / PDSCH reception.

[0020] In the past RAN1 meeting (RAN1#102-e), both sequence-based WUS and DCI-based WUS were proposed. The main discussion was about different evaluation methods, ie, different evaluation assumptions for high SNR and low SNR.

[0021] The present disclosure provides details of sequence-based WUS design and signaling, as well as details of DCI-based WUS design that is also used as scheduling DCI. For sequence-based WUS, there are two variants. The first is based on CSI-RS, which is wideband, so the sequence occupies a wider frequency band compared to SSB transmission. The second is more similar to a secondary synchronization signal (SSS) type sequence because it occupies a narrower frequency band over the entire bandwidth.

[0022] Figure 1 An exemplary architecture of a system 100 of a network according to various embodiments is shown. The following description is provided for an example system 100 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0023] like Figure 1As shown, the system 100 includes a UE 122 and a UE 120. In this example, the UE 122 and the UE 120 are illustrated as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashboard mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0024] In some embodiments, UE 122 and / or UE 120 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0025] UE 122 and UE 120 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R)AN 108). In an embodiment, (R)AN 108 may be an NG RAN or SG RAN, an E-UTRAN, or a traditional RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to an (R)AN 108 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (R)AN 108 operating in an LTE or 4G system. UE 122 and UE 120 utilize connections (or channels) (shown as connection 104 and connection 102, respectively), each connection (or channel) comprising a physical communication interface or layer (discussed in further detail below).

[0026] In this example, connection 104 and connection 102 are air interfaces for enabling communication coupling, and may conform to a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 122 and UE 120 may exchange communication data directly via a ProSe interface 110. ProSe interface 110 may alternatively be referred to as a sidelink (SL) interface 110, and may include one or more logical channels, including, but not limited to, PSCCH, PSSCH, PSDCH, and PSBCH.

[0027] UE 120 is illustrated as being configured to access AP 112 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 124. Connection 124 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 112 would include Wireless Fidelity. router. In this example, AP 112 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 120, (R)AN 108, and AP 112 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 120 in RRC_CONNECTED being configured by RAN node 114 or RAN node 116 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 120 using WLAN radio resources (e.g., connection 124) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 124. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0028] (R)AN 108 may include one or more AN nodes, such as RAN node 114 and RAN node 116, that enable connection 104 and connection 102. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN nodes," and the like may refer to RAN nodes (e.g., gNBs) operating in NR or SG systems, while the terms "E-UTRAN nodes," and the like may refer to RAN nodes (e.g., eNBs) operating in LTE or 4G systems 100. According to various embodiments, the RAN node 114 or the RAN node 116 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0029] In some embodiments, all or part of the RAN node 114 or RAN node 116 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116); MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116); or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes. This virtualization framework allows idle processor cores of the RAN node 114 or RAN node 116 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Figure 1In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CUs may be operated by a server (not shown) located in the (R)AN 108 or by a server pool in a manner similar to the CRAN / vBBUP. Additionally or alternatively, one or more of the RAN node 114 or the RAN node 116 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE 122 and the UE 120 and is connected to the SGC via an NG interface (discussed below). In a V2X scenario, the RAN node 114 or one or more of the RAN nodes 116 may be an RSU or act as an RSU.

[0030] The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz direct short range communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0031] The RAN node 114 and / or the RAN node 116 may terminate the air interface protocol and may be the first point of contact for the UE 122 and the UE 120. In some embodiments, the RAN node 114 and / or the RAN node 116 may perform various logical functions of the (R)AN 108, 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.

[0032] In an embodiment, UE 122 and UE 120 may be configured to communicate with each other or with RAN node 114 and / or RAN node 116 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0033] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 114 and / or RAN node 116 to UE 122 and UE 120, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0034] According to various embodiments, UE 122 and UE 120 and RAN node 114 and / or RAN node 116 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0035] To operate in the unlicensed spectrum, the UE 122 and the UE 120 and the RAN node 114 or the RAN node 116 may operate using LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, the UE 122 and the UE 120 and the RAN node 114 or the RAN node 116 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0036] LBT is a mechanism by which equipment (e.g., UE 122 and UE 120, RAN node 114 or RAN node 116, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0037] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 122, AP 112, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0038] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0039] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are referred to as SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require the UE 122 to undergo a switch. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0040] The PDSCH carries user data and higher layer signaling to UE 122 and UE 120. The PDCCH carries, among other information, information about transport formats and resource allocations related to the PDSCH channel. It may also inform UE 122 and UE 120 about transport formats, resource allocations, and HARQ information related to uplink shared channels. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 120 within a cell) may be performed at either RAN node 114 or RAN node 116 based on channel quality information fed back from either UE 122 and UE 120. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 122 and UE 120.

[0041] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0042] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0043] The RAN node 114 or the RAN node 116 may be configured to communicate with each other via the interface 130. In an embodiment where the system 100 is an LTE system (e.g., when the CN 106 is an EPC), the interface 130 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful delivery of PDCP PDUs from the SeNB to the UE 122 in sequence for user data; information about PDCP PDUs that are not delivered to the UE 122; information about the current minimum expected buffer size at the Se NB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0044] In an embodiment where the system 100 is an SG or NR system (e.g., when the CN 106 is an SGC), the interface 130 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to an SGC, between a RAN node 114 (e.g., a gNB) and an eNB connected to an SGC, and / or between two eNBs connected to a 5GC (e.g., CN 106). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 122 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 114 or RAN nodes 116. Mobility support may include context transfer from the old (source) service RAN node 114 to the new (target) service RAN node 116, and control of the user plane tunnel between the old (source) service RAN node 114 and the new (target) service RAN node 116. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0045] (R)AN 108 is illustrated as being communicatively coupled to a core network—in this embodiment, to CN 106. CN 106 may include one or more network elements 132 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 122 and UE 120) connected to CN 106 via (R)AN 108. Components of CN 106 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instantiation of CN 106 may be referred to as a network slice, and a logical instantiation of a portion of CN 106 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0046] In general, the application server 118 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 118 may also be configured to support one or more communication services for UE 122 and UE 120 via the EPC (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.). The application server 118 may communicate with the CN 106 via the IP communication interface 136.

[0047] In an embodiment, CN 106 may be an SGC, and (R)AN 116 may be connected to CN 106 via an NG interface 134. In an embodiment, NG interface 134 may be divided into two parts: an NG user plane (NG-U) interface 126, which carries traffic data between RAN node 114 or RAN node 116 and UPF; and an S1 control plane (NG-C) interface 128, which is a signaling interface between RAN node 114 or RAN node 116 and access and mobility management function (AMF).

[0048] In an embodiment, CN 106 may be an SG CN, while in other embodiments, CN 106 may be an EPC. In the case where CN 106 is an EPC, (R)AN 116 may be connected to CN 106 via an S1 interface 134. In an embodiment, S1 interface 134 may be divided into two parts: an S1 user plane (S1-U) interface 126, which carries traffic data between RAN node 114 or RAN node 116 and S-GW; and an S1-MME interface 128, which is a signaling interface between RAN node 114 or RAN node 116 and MME.

[0049] In one embodiment for implementing WUS in FR1 or FR2, one CSI-RS with multiple ports is used for a wideband WUS design based on CSI-RS / TRS configuration. The function of this CSI-RS is overloaded by another type of function of WUS. Therefore, the CSI-RS configuration is used for different purposes, where there is another CRI-RS configuration for WUS and its association is one CSI-RS port configuration per paging frame.

[0050] In a paging frame, according to Figure 8 The "Ns" information element parameter in the "PCCH-Config" shown in FIG. 3 is used to configure one, two or four paging periods. The Ns parameter and associated formula for determining the time position of the paging frame are described in 3GPP TS 38.304.

[0051] The number of CSI-RS ports is configured to correspond to the number of paging occasions within a paging frame, thereby mapping one CSI-RS port to one paging occasion. If Ns is equal to 1, the number of CSI-RS ports is 1; if Ns is equal to 2, the number of CSI-RS ports is 2; and so on. For example, Figure 2 A paging frame 202 is shown. Within the paging frame 202 there are two paging occasions, paging occasion 204 and paging occasion 206, in which case there are two CSI-RS ports. A WUS 208 is configured per (each) paging frame 202, and different numbers of paging occasions may be configured for different paging frames.

[0052] In some embodiments, two or four CSI-RS ports may reuse a code division multiplexing (CDM) configuration in a CSI-RS configuration. CDM uses the orthogonality of random sequences to carry information. In the context of WUS, one random sequence corresponds to one WUS. Different random sequences are transmitted on the same time / frequency resources. For example, within four ports, CDM allows the same resources to be occupied and distinguished by code rate in order to distinguish the coded sequences. In another embodiment, resources may be divided by frequency division multiplexing (FDM).

[0053] The WUS 208 is sent at least a minimum gap 210 before the paging frame to allow the UE to decode and process the WUS 208 to decide whether to wake up. The UE detects the presence of the CSI-RS per port configuration to detect the WUS 208. Even though the WUS may be configured with four ports, each single UE may receive and detect one port. The UE may monitor only one paging occasion in the entire DRX cycle, so the UE wakes up and then receives the WUS 208 for its specific configured port to detect whether the port carries the preconfigured sequence. If the sequence is received, the UE waits for its corresponding paging occasion to receive. If the sequence is not received, the UE will go back to sleep. Figure 2 In the example of FIG. 2 , WUS 208 includes two ports for paging occasion 204 and paging occasion 206 , which correspond to two different UEs configured for different ports.

[0054] In another embodiment, the detection of WUS may also indicate the presence of a preconfigured TRS before the paging frame or each paging occasion. If WUS is not transmitted, then TRS is not transmitted. This minimizes the (fixed) system overhead impact by providing idle / inactive mode UEs with potential TRS / CSI-RS moments that are available in connected mode. Note that when WUS enables on-demand TRS / CSI-RS transmission, there is no need to perform always-on TRS / CSI-RS transmission by the gNB.

[0055] Since there are various network deployments and support for different UE types (reduced capability UE, extended coverage UE, etc.), WUS sequence configuration is performed. For example, the WUS position and sequence length are configured by additional RRC signaling including "WUS-config-r17" in RadioResourceCommonSIB. The WUS-Config-r17 configures the number of CSI-RS / SSS symbols, frequency positions, number of ports, port to paging occasion mapping, CDM configuration in the WUS resource set.

[0056] WUS-config-r17 can also configure whether trs-info is true. In the case where WUS is used as TRS, this field indicates that WUS uses TRS format. If this field is false, the WUS can indicate that TRS will be transmitted at a preconfigured position after this WUS.

[0057] WUS-config-r17 may also configure timeOffsetDRX to indicate the minimum time offset for starting a paging occasion. If this field is true, the UE may use the WUS sequence itself to perform time / frequency estimation.

[0058] Figure 3Another implementation of WUS in FR2 using UE beam scanning is shown, where one CSI-RS with multiple ports is adopted for a wideband WUS design based on CSI-RS / TRS configuration.

[0059] When beam scanning is used, for each beam direction, similar to paging occasions, the same WUS is transmitted with SSB per transmission configuration indicator (TCI). For example, Figure 3 A paging frame 302 including two paging periods 304 is shown. For CSI-RS based WUS, UE receive (Rx) beam scanning within an OFDM symbol can be enabled by appropriately configuring the "frequencyDomainAllocation" parameter in the CSI-RS-resourceMapping configuration. In the case of frequency domain downsampling, the gNB ensures that there is one transmit tone and the other tones are empty to form a time domain repetition of the sequence 306. The UE trains an Rx beam 308 for each transmit (Tx) beam (SSB TCI state). It can then use the best Rx beam trained from the WUS to receive the corresponding PDCCH and PDSCH at the paging occasion 304.

[0060] The UE may also combine repeated copies of the same paging occasion to enhance the performance of both WUS detection and paging occasion reception. Figure 3 As shown, there are two paging occasions and four beam directions are used to transmit each paging occasion. Therefore, the paging message is repeated four times (once for each beam).

[0061] As previously described, the detection of a WUS may also indicate the presence of a TRS at a preconfigured location prior to the paging occasion.

[0062] WUS-config-r17 can be configured with the above combination Figure 2 Parameters discussed. Another parameter in WUS-config-r17 for FR2 is EnableRxBeamSearch. If this field is true, a repeating sequence per Tx beam is sent to allow the UE to perform Rx beam training per Tx beam.

[0063] Figure 4 Another embodiment for implementing WUS in FR 1 or FR2 is shown, where multiple CSI-RS are used for a wideband WUS design based on a CSI-RS / TRS configuration. For example, each WUS may include one OFDM symbol, with a density of one or three at a 20MHz bandwidth. In another embodiment, similar to the TRS structure, the WUS is two OFDM symbols separated by four OFDM symbols.

[0064] and Figure 2 Compared with the implementation scheme, Figure 4 A paging frame 402 is shown that includes two paging occasions and multiple WUSs, where each WUS is associated by paging occasion rather than by paging frame. Therefore, there are multiple CSI-RS configurations, one CSI-RS configuration per paging occasion, and one port per CSI-RS configuration. The location of each WUS is configured by paging occasion. As previously described, each WUS is at least one gap ahead of the corresponding paging occasion in the paging frame.

[0065] The detection of a WUS may also indicate the presence of a TRS at a preconfigured location prior to each paging occasion.

[0066] WUS-config-r17 can be configured with the above combination Figure 2 Parameters for discussion.

[0067] Figure 5 A paging frame 502 is shown in which multiple CSI-RS correspond to multiple WUS in FR2. Figure 3 As described in the implementation scheme of , the same WUS is transmitted using SSB according to TCI. Figure 3 Compared to the implementation scheme of FIG. 5 , each CSI-RS configuration is associated with a paging occasion instead of a paging frame.

[0068] For each CSI-RS configuration, appropriate configuration of the "frequencyDomainAllocation" parameter in the CSI-RS-resourceMapping configuration enables UE Rx beam scanning within an OFDM symbol. The gNB ensures that other tones are empty to create a time domain repetition of sequence 504. The UE can train the Rx beam for each Tx beam (SSB TCI state). It can then use the best Rx beam trained from the WUS to receive the corresponding PDCCH and PDSCH at the paging occasion.

[0069] The UE may also combine different repetitions of the same paging occasion to enhance the performance of both WUS detection and paging occasion reception.

[0070] The detection of a WUS may also indicate the presence of a TRS at a preconfigured location prior to the paging occasion.

[0071] WUS-config-r17 can be configured with the above combination Figure 2 Parameters discussed. Another parameter in WUS-config-r17 for FR2 is EnableRxBeamSearch. If this field is true, a repeating sequence per TX beam is sent to allow the UE to perform RX beam training for each Tx beam.

[0072] Figure 6An example of a paging frame 602 employing SSS 604 for WUS is shown. SSS-based WUS enables narrowband reception without SSB detection for potentially greater power saving benefits.

[0073] The UE may also use the last SSB 606 to refine time / frequency synchronization before the paging occasion 608. In another embodiment, if a potential location of a TRS is configured before the paging occasion 608, the UE may use the TRS to refine time / frequency synchronization.

[0074] Different SSB sequences can be multiplexed within one WUS timing position, with a 1:1 sequence mapping to a paging occasion. Different orthogonal sequences are CDMed together, similar to the CDM of different CSI-RS ports at the same time / frequency position described previously.

[0075] The term SSB sequence generally refers to an SSS-like sequence. In NR, SSS is generated using an m-sequence with a cell ID as one input parameter. Here, WUS can follow a similar design using an m-sequence definition, where the paging occasion index is one of the input parameters for generating the sequence, but is similar in nature in the m-sequence definition.

[0076] When beam scanning is used, the SSS-based WUS is also transmitted in the SSB TCI state. UE beam scanning occurs from one SSS symbol to the next.

[0077] WUS-config-r17 can be configured with the above combination Figure 2 Parameters discussed, and include EnableRxBeamSearch for FR2 implementations. However, the WUS position and sequence length will vary depending on whether the specific implementation is SSS-based WUS or CSI-RS-based WUS.

[0078] Figure 7 A DCI based WUS with a relatively large scheduling gap is shown. The enhanced DCI 702 carries UE grouping information (discussed in RAN2), provides TRS scheduling information, has scheduling information and short messages. With the new DCI format, Rel-17 UEs do not need to read the legacy DCI 704 scrambled by the P-RNTI. Both DCIs point to the same paging.

[0079] Regarding UE behavior, there is no change for legacy UEs. For Rel-17 UEs, the UE wakes up to detect SSB and get a rough time / frequency. The UE searches for the new WUS paging of the enhanced DCI 702. If no DCI is detected, the UE will go back to sleep. If the correct UE subgroup is detected, the UE will use SSB or TRS (if carried using the new WUS enhanced DCI 702) to further refine the time / frequency, and then it can decode the paging message. In other words, the UE grouping is mapped to the paging occasion. Within a paging occasion, further subgrouping is currently under discussion.

[0080] Figure 8 It is shown that the location of the new DCI can be signaled in SIB1, PCCH-Config 802. The WUSPDCCH DCI search space is derived from the previous paging DCI search space configuration with a configuration offset. For enhanced DCI 702 ( Figure 7 ), use firstWUSPDCCH-offset-MonitoringOccasionOfPO 804 to signal the offset field.

[0081] The AMF and RAN configurations for CSR-RS based, SSS based and DCI based WUS implementations are as follows.

[0082] For UEs in RRC idle state, the AMF sends RAN paging assistance information including WUS assistance information, which indicates whether the UE supports WUS, whether the UE supports Rx beam scanning for WUS received in FR2, and sub-grouping information when grouping is based on traffic or device type.

[0083] The RAN paging assistance information also includes assistance information for coverage extension UEs or reduced capability (RedCap) UEs. The assistance information includes, for example, DCI coverage related parameters, such as the maximum number of aggregation levels, PDCCH repetitions, and other DCI coverage related parameters. The assistance information also includes PDSCH coverage related parameters, such as PDSCH repetitions, TBS scaling, and other parameters.

[0084] For RRC idle UE, when the UE is suspended, the UE context is saved in the gNB. When the UE moves out of the area, the RAN notification area update process is triggered when the UE moves, and the gNB will forward the relevant UE context, including WUS information, coverage information to the next gNB.

[0085] Fig. 9is a block diagram illustrating a component 900 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig. 9 A schematic diagram of hardware resources 902 is shown, which includes one or more processors 906 (or processor cores), one or more memory / storage devices 914, and one or more communication resources 924, each of which may be communicatively coupled via a bus 916. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 922 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 902.

[0086] Processor 906 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 908 and processor 910.

[0087] The memory / storage device 914 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 914 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0088] The communication resources 924 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 904 or one or more databases 920 via the network 918. For example, the communication resources 924 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components.

[0089] The instructions 912 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 906 to perform any one or more of the methods discussed herein. The instructions 912 may reside completely or partially in at least one of the processors 906 (e.g., in a cache memory of the processor), the memory / storage device 914, or any suitable combination thereof. In addition, any portion of the instructions 912 may be transmitted to the hardware resources 902 from any combination of the peripheral device 904 or the database 920. Therefore, the memory of the processor 906, the memory / storage device 914, the peripheral device 904, and the database 920 are examples of computer-readable and machine-readable media.

[0090] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the examples section below.

[0091] Examples

[0092] The following examples relate to additional embodiments.

[0093] Embodiment 1 is a wake-up signal (WUS) detection method for facilitating paging in a wireless communication system, performed by a user equipment (UE), the method comprising: receiving configuration information indicating a channel state information (CSI)-reference signal (RS) port corresponding to a paging occasion in a paging frame from a next generation node B (gNB); detecting the presence of a WUS in the CSI-RS port corresponding to the paging occasion; and attempting to decode a sequence of the WUS received via resources of the CSI-RS port to determine whether the paging occasion includes a paging message for the UE.

[0094] Embodiment 2 is the method described in embodiment 1, wherein the paging frame includes multiple paging occasions corresponding to multiple CSI-RS ports, and the configuration information maps one of the multiple paging occasions to one of the multiple CSI-RS ports.

[0095] Embodiment 3 is the method of embodiment 2, wherein the multiple CSI-RS ports are configured to use code division multiplexing (CDM).

[0096] Embodiment 4 is the method of embodiment 1, wherein the detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) prior to the paging frame or prior to each paging opportunity in the paging frame.

[0097] Embodiment 5 is the method described in embodiment 1, further comprising receiving a WUS transmitted according to a transmission configuration indicator (TCI) for each UE beam direction among multiple UE beam directions.

[0098] Embodiment 6 is the method described in embodiment 1, further comprising receiving a repeated WUS sequence in beam scanning.

[0099] Embodiment 7 is the method of embodiment 1, wherein the paging frame includes multiple paging occasions, and each of the multiple paging occasions corresponds to a different CSI-RS configuration.

[0100] Embodiment 8 is the method described in Embodiment 1, wherein the configuration information includes the WUS-config-r17 parameter in RadioResourceCommonSIB.

[0101] Embodiment 9 is a wake-up signal (WUS) detection method performed by a user equipment (UE) to facilitate paging in a wireless communication system, the method comprising: receiving configuration information indicating a secondary synchronization signal (SSS)-like sequence corresponding to a paging occasion in a paging frame from a next generation node B (gNB); detecting the presence of a WUS in the SSS corresponding to the paging occasion; and attempting to decode the SSS-like sequence of the WUS received via a resource of the SSS to determine whether the paging occasion includes a paging message for the UE.

[0102] Embodiment 10 is the method of embodiment 9, wherein the WUS is associated with multiple paging occasions.

[0103] Embodiment 11 is the method of embodiment 9, further comprising refining the time and frequency tracking based on a last synchronization signal block (SSB) before the paging opportunity.

[0104] Embodiment 12 is the method of embodiment 9, wherein the detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) prior to the paging frame or prior to each paging opportunity in the paging frame.

[0105] Embodiment 13 is the method described in embodiment 9, further comprising receiving a WUS transmission according to a synchronization signal block (SSB) transmission configuration indicator (TCI) state.

[0106] Embodiment 14 is the method described in Embodiment 9, wherein the configuration information includes the WUS-config-r17 parameter in RadioResourceCommonSIB.

[0107] Embodiment 15 is a wake-up signal (WUS) detection method performed by a user equipment (UE) to facilitate paging in a wireless communication system, the method comprising: detecting a synchronization signal block (SSB) for time and frequency tracking; searching for WUS in downlink control information (DCI) corresponding to a paging occasion in a paging frame, the DCI comprising sub-group information; in response to detecting the WUS, checking the sub-group information; and in response to the sub-group information being applied to the UE, attempting to decode a paging message at the paging occasion.

[0108] Embodiment 16 is the method of embodiment 15, wherein the location of the DCI is signaled in system information block (SIB) 1, PCCH-Config information.

[0109] Embodiment 17 is the method of embodiment 15, wherein the search space of the DCI is derived from PCCH-Config information including firstWUSPDCCH-offset-MonitoringOccasionOfPO.

[0110] Embodiment 18 is the method of embodiment 15, further comprising further refining time and frequency tracking using a tracking reference signal (TRS) in response to the subgrouping information being applied to the UE.

[0111] Embodiment 19 is the method described in embodiment 15, wherein the scheduling gap between the DCI and the paging opportunity includes one or more SSBs.

[0112] Embodiment 20 is a non-transitory computer-readable storage medium, which includes instructions that, when executed by a computer, cause the computer to: receive configuration information indicating a channel state information (CSI)-reference signal (RS) port corresponding to a paging occasion in a paging frame from a next-generation Node B (gNB); detect the presence of a WUS in the CSI-RS port corresponding to the paging occasion; and attempt to decode a sequence of the WUS received via resources of the CSI-RS port to determine whether the paging occasion includes a paging message for the UE.

[0113] Embodiment 21 is the computer-readable storage medium of embodiment 20, wherein the paging frame includes multiple paging occasions corresponding to multiple CSI-RS ports, and the configuration information maps one of the multiple paging occasions to one of the multiple CSI-RS ports.

[0114] Embodiment 22 is the computer-readable storage medium of embodiment 21, wherein the plurality of CSI-RS ports are configured to use code division multiplexing (CDM).

[0115] Embodiment 23 is the computer-readable storage medium of embodiment 20, wherein the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) prior to the paging frame or prior to each paging opportunity in the paging frame.

[0116] Embodiment 24 is the computer-readable storage medium of embodiment 20, wherein the instructions further configure the computer to receive a WUS transmitted in accordance with a transmission configuration indicator (TCI) for each UE beam direction of a plurality of UE beam directions.

[0117] Embodiment 25 is the computer readable storage medium of embodiment 20, wherein the instructions further configure the computer to receive a repeating WUS sequence in a beam scan.

[0118] Embodiment 26 is the computer-readable storage medium of embodiment 20, wherein the paging frame includes a plurality of paging occasions, and each of the plurality of paging occasions corresponds to a different CSI-RS configuration.

[0119] Embodiment 27 is the computer-readable storage medium of embodiment 20, wherein the configuration information comprises a WUS-config-r17 parameter in a RadioResourceCommonSIB.

[0120] Embodiment 28 is a non-transitory computer-readable storage medium, which includes instructions that, when executed by a computer, cause the computer to: receive configuration information indicating a secondary synchronization signal (SSS)-like sequence corresponding to a paging occasion in a paging frame from a next-generation Node B (gNB); detect the presence of a WUS in the SSS corresponding to the paging occasion; and attempt to decode the SSS-like sequence of the WUS received via a resource of the SSS to determine whether the paging occasion includes a paging message for the UE.

[0121] Embodiment 29 is the computer-readable storage medium of embodiment 28, wherein the WUS is associated with a plurality of paging occasions.

[0122] Embodiment 30 is the computer readable storage medium of embodiment 28, wherein the instructions configure the computer to further configure the computer to refine the time and frequency tracking based on a last synchronization signal block (SSB) prior to the paging opportunity.

[0123] Embodiment 31 is the computer-readable storage medium of embodiment 28, wherein the detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) prior to the paging frame or prior to each paging opportunity in the paging frame.

[0124] Embodiment 32 is the computer-readable storage medium of embodiment 28, wherein the instructions further configure the computer to receive a WUS transmission in a synchronization signal block (SSB) transmission configuration indicator (TCI) state.

[0125] Embodiment 33 is the computer-readable storage medium of embodiment 28, wherein the configuration information comprises a WUS-config-r17 parameter in a RadioResourceCommonSIB.

[0126] Embodiment 34 is a non-transitory computer-readable storage medium, which includes instructions that, when executed by a computer, cause the computer to: detect a synchronization signal block (SSB) for time and frequency tracking; search for a WUS in downlink control information (DCI) corresponding to a paging occasion in a paging frame, the DCI including sub-group information; in response to detecting the WUS, check the sub-group information; and in response to the sub-group information being applied to the UE, attempt to decode a paging message at the paging occasion.

[0127] Embodiment 35 is the computer-readable storage medium of embodiment 34, wherein the location of the DCI is signaled in system information block (SIB) 1, PCCH-Config information.

[0128] Embodiment 36 is the computer-readable storage medium of embodiment 34, wherein the search space of the DCI is derived from PCCH-Config information including a firstWUSPDCCH offset MonitoringOccasionOfPO.

[0129] Embodiment 37 is the computer-readable storage medium of embodiment 34, wherein the instructions further configure the computer to further refine time and frequency tracking using a tracking reference signal (TRS) in response to applying the subgrouping information to the UE.

[0130] Embodiment 38 is the computer-readable storage medium of embodiment 34, wherein the scheduling gap between the DCI and the paging opportunity includes one or more SSBs.

[0131] Embodiment 39 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0132] Embodiment 40 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0133] Embodiment 41 may include a device comprising logic components, modules, or circuits for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0134] Embodiment 42 may include methods, techniques or processes described in or related to any of the above embodiments, or parts or components thereof.

[0135] Embodiment 43 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described in any one of or related to the above embodiments.

[0136] Embodiment 44 may include a signal or a portion or component thereof as described in or related to any of the above embodiments.

[0137] Embodiment 45 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in or related to any of the above embodiments, or content otherwise described in the present disclosure.

[0138] Embodiment 46 may include a signal encoded with data or a portion or component thereof as described in or related to any of the above embodiments, or content described in other ways in this disclosure.

[0139] Embodiment 47 may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0140] Embodiment 48 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described in or related to any of the above embodiments.

[0141] Embodiment 49 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any of the above embodiments.

[0142] Embodiment 50 may include signals in a wireless network as shown and described herein.

[0143] Embodiment 51 may include a method of communicating in a wireless network as shown and described herein.

[0144] Embodiment 52 may include a system for providing wireless communications as shown and described herein.

[0145] Embodiment 53 may include an apparatus for providing wireless communications as shown and described herein.

[0146] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0147] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0148] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0149] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0150] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for detecting a wake-up signal WUS for facilitating paging in a wireless communication system, performed by a user equipment UE, the method comprising: receiving, from a base station, configuration information indicating a channel state information reference signal (CSI-RS) port corresponding to a paging occasion in a paging frame, wherein the paging frame includes a plurality of paging occasions corresponding to a plurality of CSI-RS ports, and the configuration information maps one of the plurality of paging occasions to one of the plurality of CSI-RS ports; detecting the presence of a WUS in the CSI-RS port corresponding to the paging occasion; as well as Attempting to decode the sequence of the WUS received via the resource of the CSI-RS port to determine whether the paging occasion includes a paging message for the UE. 2 . The method according to claim 1 , wherein the plurality of CSI-RS ports are configured to use code division multiplexing (CDM). 3 . The method of claim 1 , wherein detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) before the paging frame or before each paging occasion in the paging frame.

4. The method according to claim 1 also includes receiving a WUS transmitted according to a transmission configuration indicator TCI for each UE beam direction of multiple UE beam directions. The method of claim 1 , further comprising receiving a repeated WUS sequence in a beam scan. 6 . The method according to claim 1 , wherein the paging frame comprises a plurality of paging occasions, and each of the plurality of paging occasions corresponds to a different CSI-RS configuration. 7 . The method of claim 1 , wherein the configuration information comprises a WUS-config-r17 parameter in a RadioResourceCommonSIB.

8. A method for detecting a wake-up signal WUS for facilitating paging in a wireless communication system, performed by a user equipment UE, the method comprising: receiving, from a base station, configuration information indicating a secondary synchronization signal SSS-like sequence corresponding to a paging occasion in a paging frame, wherein the configuration information includes a WUS-config-r17 parameter in a RadioResourceCommonSIB; detecting the presence of a WUS in the SSS corresponding to the paging occasion; as well as Attempting to decode the SSS-like sequence of the WUS received via the resources of the SSS to determine whether the paging occasion includes a paging message for the UE.

9. The method of claim 8, wherein the WUS is associated with a plurality of paging occasions.

10. The method of claim 8, further comprising refining time and frequency tracking based on a last synchronization signal block (SSB) before the paging occasion.

11. The method of claim 8, wherein detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) before the paging frame or before each paging occasion in the paging frame.

12. The method according to claim 8 also includes receiving a WUS transmission according to a synchronization signal block (SSB) transmission configuration indicator (TCI) state.

13. A computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to: receiving, from a base station, configuration information indicating a channel state information reference signal (CSI-RS) port corresponding to a paging occasion in a paging frame, wherein the paging frame includes a plurality of paging occasions corresponding to a plurality of CSI-RS ports, and the configuration information maps one of the plurality of paging occasions to one of the plurality of CSI-RS ports; detecting the presence of a WUS in the CSI-RS port corresponding to the paging occasion; as well as Attempting to decode the sequence of the WUS received via the resource of the CSI-RS port to determine whether the paging occasion includes a paging message for the UE.

14. The computer-readable storage medium of claim 13, wherein the plurality of CSI-RS ports are configured to use code division multiplexing (CDM).

15. The computer-readable storage medium of claim 13, wherein detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) prior to the paging frame or prior to each paging occasion in the paging frame.

16. The computer-readable storage medium of claim 13, wherein the instructions further configure the computer to receive a WUS transmitted according to a transmission configuration indicator (TCI) for each UE beam direction in a plurality of UE beam directions.

17. The computer-readable storage medium of claim 13, wherein the instructions further configure the computer to receive a repeating WUS sequence in a beam sweep.

18. The computer-readable storage medium of claim 13, wherein the paging frame comprises a plurality of paging occasions, and each of the plurality of paging occasions corresponds to a different CSI-RS configuration.

19. The computer-readable storage medium of claim 13, wherein the configuration information comprises a WUS-config-r17 parameter in a RadioResourceCommonSIB.

20. A computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to: receiving, from a base station, configuration information indicating a secondary synchronization signal SSS-like sequence corresponding to a paging occasion in a paging frame, wherein the configuration information includes a WUS-config-r17 parameter in a RadioResourceCommonSIB; detecting the presence of a WUS in the SSS corresponding to the paging occasion; as well as Attempting to decode the SSS-like sequence of the WUS received via the resources of the SSS to determine whether the paging occasion includes a paging message for the UE.

21. The computer-readable storage medium of claim 20, wherein the WUS is associated with a plurality of paging occasions.

22. The computer-readable storage medium of claim 20, wherein the instructions further configure the computer to refine time and frequency tracking based on a last synchronization signal block (SSB) prior to the paging occasion.

23. The computer-readable storage medium of claim 20, wherein detecting the presence of the WUS indicates the presence of a preconfigured tracking reference signal (TRS) prior to the paging frame or prior to each paging occasion in the paging frame.

24. The computer-readable storage medium of claim 20, wherein the instructions further configure the computer to receive a WUS transmission in a synchronization signal block (SSB) transmission configuration indicator (TCI) state.

Images