WO2019099661A1

WO2019099661A1 - Enhanced paging monitoring in 5g

Info

Publication number: WO2019099661A1
Application number: PCT/US2018/061270
Authority: WO
Inventors: Kyle Jung-Lin Pan; Nirav B. Shah; Fengjun Xi
Original assignee: Idac Holdings, Inc.
Priority date: 2017-11-15
Filing date: 2018-11-15
Publication date: 2019-05-23
Also published as: TW201933817A

Abstract

Methods and systems for paging monitoring, which may be performed by wireless transmit/receive unit (WTRU) that supports multi-beam communications, are disclosed herein. A WTRU may receive a configuration for enhanced paging. The WTRU may determine a first subcarrier spacing (SCS) for a synchronization signal block (SSB) and a second SCS for a paging reception. The WTRU may determine a paging multiplexing type (PMT) based on the first SCS and second SCS, where the PMT is of a first type if the first and second SCS are different and a second type if the first and second SCS are the same. The WTRU may determine a beam, time and frequency relationship among a paging control resource set (CORESET), a paging message, and/or the SSB based on the determined PMT. The WTRU may monitor a paging occasion (PO) in one or more beams based on the determined beam, time and frequency relationship.

Description

ENHANCED PAGING MONITORING IN 5G

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application Serial No.

62/586,513, filed November 15, 2017, and U.S. Provisional Application Serial No. 62/652,809, filed April 4, 2018, the contents of which are hereby incorporated by reference herein.

BACKGROUND

[0002] Recent Third Generation Partnership Project (3GPP) standards discussions define several deployment scenarios such as indoor hotspot, dense urban, rural, urban macro, and high speed. Based on general requirements set out by International Telecommunication Union Radiocommunication Sector (ITU-R), Next Generation Mobile Networks (NGMN) and 3GPP, a broad classification of the use cases for emerging Fifth Generation (5G) systems may be classified as enhanced mobile broadband (eMBB), massive machine type communications (mMTC) and ultra reliable and low latency communications (URLLC). These use cases focus on meeting different performance requirements such as higher data rate, higher spectrum efficiency, low power and higher energy efficiency, and/or lower latency and higher reliability. Moreover, a wide range of spectrum bands ranging from 700 MHz to 80 GHz are being considered for a variety of deployment scenarios.

[0003] In wireless communications, as the carrier frequency increases, severe path loss may become a crucial limitation to guarantee sufficient coverage. Transmission in millimeter wave (mmW) systems may additionally suffer from non-line-of-sight losses, such as diffraction loss, penetration loss, oxygen absorption loss, and/or foliage loss. During initial access, a base station and WTRU may need to overcome these high path losses and discover each other. Utilizing dozens or even hundreds of antenna elements to generate beamformed signals is an effective way to compensate for severe path loss by providing significant beamforming gain. Beamforming techniques may include digital, analogue and hybrid beamforming.

SUMMARY

[0004] Methods and systems for paging monitoring, which may be performed by wireless transmit/receive unit (WTRU) that supports multi-beam communications, are disclosed herein. A WTRU may receive a configuration for enhanced paging. The WTRU may determine a first subcarrier spacing (SCS) for a synchronization signal block (SSB) and a second SCS for a paging reception. The WTRU may determine a paging multiplexing type (PMT) based on the first SCS and second SCS, such that the PMT is determined to be a first type on a condition that the first SCS and second SCS are different and a second type on a condition that first SCS and second SCS are the same. The WTRU may determine a beam, time and frequency relationship among a paging control resource set (CORESET), a paging message, and/or the SSB based on the determined PMT. The WTRU may monitor a paging occasion (PO) in one or more beams of the PO for the paging message based on the determined beam, time and frequency relationship.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

[0006] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

[0007] FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit

(WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0008] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0009] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0010] FIG. 2 is a frame format diagram of an example slot format including frequency division multiplexed (FDM) paging downlink control information (DCI) and synchronization signal block (SSB);

[001 1] FIG. 3 is a frame format diagram of an example slot format including FDM paging

DCIs and SSB;

[0012] FIG. 4 is a frame format diagram of another example slot format including time divisionl multiplexed (TDM) pagion occasions (POs) with SSB;

[0013] FIG. 5 is a frame format diagram of another example slot format including TDM DCI and POs with SSB;

[0014] FIG. 6 is a frame format diagram of another example slot format including TDM DCI and POs with SSB with frequency hopping; [0015] FIG. 7 is a resource format for an example paging scheduling, where the POs are defined over a sweep of four beams with a mini-slot of size two symbols;

[0016] FIG. 8 is a resource format for example paging scheduling where the POs are defined over a sweep of four beams with a mini-slot format consisting of two orthogonal frequency division multiplexing (OFDM) symbols respectively;

[0017] FIG. 9 is a resource format for example paging scheduling where POs are swept together;

[0018] FIG. 10 is a resource format for example paging scheduling;

[0019] FIG. 1 1 is a flow diagram of an example paging beam selection procedure;

[0020] FIG. 12 is a messaging diagram of an example paging multiplexing format during a

PO;

[0021] FIG. 13 is a messaging diagram of an example paging multiplexing format during a

PO;

[0022] FIG. 14 is an example multiplexing pattern 1 for a PO configuration where the paging control resource set (CORESET) is TDM with synchronization signal/physical broadcast channel (SS/PBCH) block;

[0023] FIG. 15 is another example multiplexing pattern 1 for a PO configuration where the paging CORESET is TDM with an SS/PBCH block;

[0024] FIG. 16 is another example multiplexing pattern 1 for a PO configuration where the paging CORESET is TDM with an SS/PBCH block;

[0025] FIG. 17 is another example multiplexing pattern 1 for a PO configuration where the paging CORESET is TDM with an SS/PBCH block;

[0026] FIG. 18 is an example multiplexing pattern 3 for a PO configuration where the paging CORESET is FDM with an SS/PBCH block;

[0027] FIG. 19 is an example multiplexing pattern 3 for a PO configuration where the paging CORESET is FDM with an SS/PBCH block;

[0028] FIG. 20 is a signalling diagram of an example PO configuration; and

[0029] FIG. 21 is a signalling diagram of an example PO configuration.

DETAILED DESCRIPTION

[0030] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0031] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/1 13, a ON 106/1 15, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 1 12, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a“station” and/or a“STA”, may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0032] The communications systems 100 may also include a base station 1 14a and/or a base station 114b. Each of the base stations 1 14a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 1 10, and/or the other networks 112. By way of example, the base stations 1 14a, 1 14b may be a base transceiver station (BTS), a Node-B, an eNode B, a Flome Node B, a Flome eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 1 14a, 1 14b may include any number of interconnected base stations and/or network elements.

[0033] The base station 114a may be part of the RAN 104/1 13, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 1 14a and/or the base station 1 14b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 1 14a may be divided into three sectors. Thus, in one embodiment, the base station 1 14a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 1 14a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

[0034] The base stations 114a, 114b may communicate with one or more of the WTRUs

102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 1 16 may be established using any suitable radio access technology (RAT).

[0035] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 1 14a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 1 15/116/1 17 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (FISPA+). HSPA may include High-Speed Downlink (DL) Packet Access (FISDPA) and/or High- Speed UL Packet Access (FISUPA).

[0036] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 1 16 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).

[0037] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 1 16 using New Radio (NR).

[0038] In an embodiment, the base station 1 14a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 1 14a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).

[0039] In other embodiments, the base station 1 14a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.1 1 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0040] The base station 1 14b in FIG. 1A may be a wireless router, Flome Node B, Flome eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.1 1 to establish a wireless local area network (WLAN). In an embodiment, the base station 1 14b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 1 14b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 1 14b may have a direct connection to the Internet 1 10. Thus, the base station 1 14b may not be required to access the Internet 1 10 via the CN 106/1 15.

[0041] The RAN 104/1 13 may be in communication with the CN 106/1 15, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/1 15 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or the CN 106/1 15 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/1 13 or a different RAT. For example, in addition to being connected to the RAN 104/1 13, which may be utilizing a NR radio technology, the CN 106/1 15 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0042] The CN 106/1 15 may also serve as a gateway for the WTRUs 102a, 102b, 102c,

102d to access the PSTN 108, the Internet 1 10, and/or the other networks 1 12. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 1 10 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 1 12 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 1 12 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.

[0043] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system

100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 1 14a, which may employ a cellular-based radio technology, and with the base station 1 14b, which may employ an IEEE 802 radio technology.

[0044] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG.

1 B, the WTRU 102 may include a processor 1 18, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0045] The processor 1 18 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 1 18 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 1 18 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 1 18 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip. [0046] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 1 16. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0047] Although the transmit/receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 1 16.

[0048] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.1 1 , for example.

[0049] The processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 1 18 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0050] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0051] The processor 1 18 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 1 16 from a base station (e.g., base stations 1 14a, 1 14b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0052] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.

[0053] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 1 18). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0054] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0055] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.

[0056] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell

(not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0057] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME)

162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0058] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the

RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.

[0059] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the

RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0060] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs

102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0061] The CN 106 may facilitate communications with other networks. For example, the

CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

[0062] Although the WTRU is described in FIGS. 1A-1 D as a wireless WTRU, it is contemplated that in certain representative embodiments that such a WTRU may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0063] In representative embodiments, the other network 1 12 may be a WLAN.

[0064] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point

(AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer- to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.1 1e DLS or an 802.1 1 z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an“ad-hoc” mode of communication.

[0065] When using the 802.1 1 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.1 1 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0066] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0067] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or

160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0068] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11h, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0069] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11h, 802.11ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0070] In the United States, the available frequency bands, which may be used by

802.1 1 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 1 ah is 6 MHz to 26 MHz depending on the country code.

[0071] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 1 15 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 1 13 may also be in communication with the CN 115.

[0072] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 1 13 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).

[0073] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0074] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs

102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0075] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0076] The CN 115 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0077] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b,

180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 1 13 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

[0078] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 1 15 via an N1 1 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 1 15 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

[0079] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b,

180c in the RAN 1 13 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0080] The CN 115 may facilitate communications with other networks. For example, the

CN 1 15 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 1 15 and the PSTN 108. In addition, the CN 1 15 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0081] In view of Figures 1A-1 D, and the corresponding description of Figures 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 1 14a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions. [0082] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

[0083] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0084] In wireless communications systems, cell search may refer to a procedure by which a WTRU acquires time and frequency synchronization with a cell and detects the cell identification (Cell ID) of the cell. In an example, LTE synchronization signals may be transmitted by a base station (e.g., eNB, gNB) in the 0^th and 5^th subframes of every radio frame and may be used for time and frequency synchronization during initialization. As part of the system acquisition process, a WTRU may synchronize sequentially to the OFDM symbol, slot, subframe, half-frame, and/or radio frame based on the synchronization signals. The synchronization signals may include a primary synchronization signal (PSS) and secondary synchronization signal (SSS). The PSS may be used to obtain slot, subframe and/or half-frame boundary. The PSS may provide the physical layer cell identity (PCI) within the cell identity group. The SSS may be used to obtain the radio frame boundary. The SSS may enable the WTRU to determine the cell identity group, which may range from 0 to 167.

[0085] Following a successful synchronization and PCI acquisition, the WTRU may decode the Physical Broadcast Channel (PBCH) (e.g., using a cell-specific reference signal (CRS)) and acquire the the master information block (MIB) information regarding system bandwidth, System Frame Number (SFN) and/or physical hybrid automatic repeat request (FIARQ) indicator channel (PHICH) configuration. LTE synchronization signals and/or PBCH may be transmitted periodically according to the standardized periodicity.

[0086] Paging may be used for network-initiated connection setup to a WTRU when the

WTRU is in RRCJDLE mode. In LTE, paging may operate similarly to downlink data transmission on the downlink shared channel (DL-SCH) and a WTRU may monitor the layer 1 and layer 2 (L1/L2) control signaling for downlink scheduling assignments related to paging. Because the location of the WTRU may not be known on a cell level, a paging message may be transmitted across multiple cells in a defined tracking area. Paging may also be used to inform WTRUs in RRCJDLE and/or RRC_CONNECTED about changes of system information or emergency information.

[0087] An efficient paging procedure may allow the WTRU (e.g., in IDLE mode or RRC inactive mode) to sleep with no receiver processing most of the time and to briefly wake up the receiver at predefined time intervals to monitor paging information from the network. Accordingly, a paging cycle may be defined allowing the WTRU to sleep most of the time and only briefly wake up to monitor the L1/L2 control signaling. If when the WTRU wakes up it detects a group identity used for paging (e.g., by scrambling the cyclic redundancy check (CRC) of the downlink control information (DCI) using a paging radio network temporary identifier (P-RNTI) that represents a paging indication), the WTRU may process the corresponding downlink paging message transmitted on the paging channel (PCH). The paging message may include the identity of the WTRU(s) being paged, and a WTRU that does not find its identity in the paging message may discard the received information in the paging message and sleep according to the discontinuous reception (DRX) cycle.

[0088] The network may configure the subframes for which a WTRU should wake up and listen to the channel for paging. The subframe configuration may be cell-specific, and may or may not be used in combination with a WTRU-specific configuration. A frame in which a given WTRU should wake up and search for the P-RNTI on a physical downlink control channel (PDCCH) may be determined by an equation taking as input the identity of the WTRU, a cell-specific paging cycle, and/or a WTRU-specific paging cycle. For example, the paging cycle for a WTRU may range from once every 256 frames to once every 32 frames. The subframe within a frame to monitor for paging may be derived from the international mobile subscriber identity (IMSI), which may be linked to the cellular service subscription. Because different WTRUs have different IMSIs, the WTRUs may compute different paging instances. Thus, from a network perspective, paging may be transmitted more often than once every 32 frames (or other paging cycle), although not all WTRUs may be paged at all paging occasions as they are distributed across the possible paging instances.

[0089] Paging messages may be transmitted only in a subset of subframes within a frame.

For example, a paging message may be sent in a range from one up to four subframes per frame in the paging cycle. From a network perspective, the cost of a short paging cycle may be minimal because resources not used for paging may be used for data or other transmission and not wasted. However, from a WTRU perspective, a short paging cycle increases the power consumption at the WTRU because the WTRU needs to wake up more frequently to monitor the paging instants.

[0090] In an example, paging scheduling DCI and paging messages may be sent in the same slot. The approach of paging DCI followed by a paging message has been shown to work efficiently in LTE and is therefore expected to also be robust in NR for single beam systems. However, in multi-beam systems (where analogue beams may be formed in different physical directions), a gNB and WTRU may have to sweep the set of all transmit and/or receive (TX/RX) beams (e.g., to determine which beam to receive paging on). In an example, if a gNB transmits a paging signal using up to 64 beams or directions and if the WTRU sweeps 4 RX beams, then the gNB may have to transmit a paging signal four times towards each of the 64 beams/directions or a total of 256 transmissions. Thus, such an approach for paging over multi-beam results in enormous signal and beam sweep overhead for paging. A WTRU in IDLE mode may not know which TX beam is best to receive (e.g., in terms of signal-to-noise ratio (SNR) or ability of the WTRU to decode a signal on a TX amongst the set of TX beams). Receiving all the TX beams may increase processing delay and power consumption at the WTRU. Quasi-colocation (QCL) of the paging signal with synchronization signal block (SSB) may help the WTRU to pre-identify a suitable TX beam to receive. Examples are described herein to reduce overhead for paging.

[0091] In an example, paging signals may be multiplexed in time and/or frequency with other signals. A paging message may be scheduled by DCI carried by NR-PDCCH such that a WTRU may decode the NR-PDCCH carrying DCI for paging message within a preconfigured search space. For example, the network may provide a control resource set (CORESET) and control channel search space for paging reception. The WTRU may be configured with CORESET for paging reception. The configured CORESET and/or search space for paging may be the same or derived from the configured CORESET and/or search space for remaining minimum system information (RMSI) reception. Parameters or a set of parameters for paging occasions (POs) may be explicitly signalled to WTRUs. The parameters for POs may include, but is not limited to include, the periodicity for the WTRU to monitor the paging scheduling DCI. In an example, POs may be frequency multiplexed and/or time multiplexed with SSB. In another example, POs may be frequency multiplexed and/or time multiplexed with the configuration information or CORESET. In another example, multiple POs may be frequency multiplexed and/or time multiplexed together. The POs, CORESET and/or the search space may be a function of the WTRU ID. [0092] In an example, frequency division multiplexing (FDM) may be used to multiplex the paging DCI and paging message with SSBs. NR-PSS, NR-SSS, NR-PBCH may each occupy respective numbers of resource blocks (RBs) per OFDM symbol. For example, NR-PSS may occupy K1 RBs, NR-SSS may occupy K2 RBs, and NR-PBCFI may occupy K3, K4 and K5 RBs. In an example, K1 and K2 may be 12 RBs, K3 and K5 may be 20 RBs, and K4 may be 8 RBs. The OFDM symbol with NR-PSS may have some RBs that can carry more data. The RBs that can carry more data may be used for carrying the paging DCI and/or paging message (which may also be transmitted in beams where SSBs are transmitted). Paging DCI may be scheduled in CORESET (e.g., in non-overlapping CORESET) with SSB and may indicate the physical resource blocks (PRBs) (i.e., resource blocks) carrying the paging message. An indication that the paging DCI and/or paging message will be multiplexed by FDM may be included in a synchronization signals or broadcast channels (e.g., NR-PSS, NR-SSS, NR-PBCFIs). Default OFDM symbol(s) within SSB where paging DCI and/or paging messages may be multiplexed and may be predefined.

[0093] A paging DCI CORESET may be FDM (frequency division multiplexed) with SSBs.

NR-PDCCFI carrying paging DCI may be scheduled in CORESET, for example in non-overlapping CORESET with SSB. The paging DCI may indicate the location of the paging message in NR- PDSCFI in the same slot or in a different slot. If overlap of CORESET on SSB occurs, NR-PDCCFI carrying paging DCI may be rate matched around the resource elements (REs) occupied by SSB (e.g., those REs may be punctured during the rate matching process). For example, rate matching may be determined by: NR-PDCCFI candidate, search space or search space set; or the positions of SSBs which may be known to the WTRU. POs may be defined in frequency or combined frequency/time.

[0094] FIG. 2 is a frame format diagram of an example slot format 200 including FDM paging DCIs and SSB. The slot format 200 may be transmitted by multiple beams, such as beam 201 and beam 203. The slot format 200 may include paging DCIs 204 and 206 that are FDM with each other an SSB 208 (e.g., on PSS), and paging DCIs 212 and 214 that are FDM with each other an SSB 216 (e.g., on PSS). The slot format 200 may also include PBCHs 210 and 218. Different POs 221 -224 may be defined using paging DCIs 204, 206, 212 and 214 in a same OFDM symbol in different PRB. In the example of FIG. 2, the paging messages transmitted in the POs 221 -224 are shown as being TDM for different POs 221 -224, and the paging DCI 204, 206, 212, 214 may be FDM or hybrid FDM/TDM for different POs 221 -224 within the slot format 200.

[0095] POs may be defined in frequency or hybrid frequency/time. In an example, paging messages for different POs may be FDM or hybrid FDM/TDM. A paging message may be configured anywhere in the slot. There may or may not be restriction on number of paging DCI which may be FDM with an SSB. FIG. 3 is a frame format diagram of an example slot format 300 including FDM paging DCIs and SSB. The slot format 300 may be transmitted by multiple beams, such as beam 301 and beam 303. In FIG. 3, four paging DCIs 304, 306, 308, 310 may be FDM with the SSB 312 (e.g., on PSS), and similarly four paging DCIs 316, 318, 320, 322 may be FDM with the SSB 324 (e.g., on PSS). The slot format 300 may also include PBCFIs 314 and 326. The paging message of the POs 331 -338 may be FDM, TDM or hybrid TDM/FDM in the slot format 300, and are shown as hybrid TDM/FDM in FIG. 3.

[0096] In the examples above, the CORESET and search space for the POs may be predefined or indicated in system information (e.g., RMSI). POs may be defined in terms of SSB. For example, a PO may be defined per group of SSBs, per transmitted SSBs or for a maximum number of SSBs (either transmitted or not transmitted). For example, a PO may be defined per group of beams, per subset of beams or for all beams.

[0097] In an example, SSB and paging DCI CORESET may be TDM (time division multiplexed). NR-PDCCFI carrying paging DCI may be TDM with SSB. NR-PDCCFI carrying paging DCI may be scheduled such that it is not overlapping with SSB using scheduling restriction. In case of TDM, the time offset of paging DCI CORESET from SSB may be predetermined (e.g., fixed and known to the WTRU) or different for different PO (where the PO may be a function of the WTRU ID). The time offset may be indicated in system information (e.g., NR-PBCFI), RMSI or other system information (OSI), and the time offset may be a function of the WTRU ID or computed based on the WTRU ID.

[0098] FIG. 4 is a frame format diagram of another example slot format 400 including TDM

POs with SSB. The slot format 400 may be transmitted by multiple beams, such as beam 401 and beam 403. The slot format 400 may also include PSS 402, SSS 406, and PBCFIs 404 and 408.

[0099] In the example of FIG. 4, the slot format 400 is of a 14 OFDM symbol duration, and a mini-slot is of a two OFDM symbol duration (other sizes may be used such as 4 or 7 OFDM symbols). In the example of FIG. 4, same slot scheduling may be used, although cross slot scheduling may be used. Paging DCI and paging message (PM) may be part of a same mini-slot (in non-slot format). POs 421 -424 may occur in different OFDM symbols of a slot 400.

[0100] FIG. 5 is a frame format diagram of another example slot format 500 including TDM

DCI and POs with SSB. The slot format 500 may be transmitted by multiple beams, such as beam 501 and beam 503. The slot format 500 may include PSS 510, SSS 514, and PBCFIs 512 and 516. In the example of FIG. 5, paging DCI 502, 504, 506, 508 may be transmitted before the paging message and may be TDM with SSB (on PSS 510 and SSS 514). Same slot scheduling and cross slot scheduling may be used without loss of generality. CORESET or search spaces for all paging DCIs 502, 504, 506, 508 may be FDM with each other (i.e., the first OFDM symbol including DCI 502, 504, 506, 508, may be one symbol CORESET). POs 521 -524 may occur in different OFDM symbols of the slot 500.

[0101] FIG. 6 is a frame format diagram of another example slot format 600 including TDM

DCI and POs with SSB with frequency hopping. The slot format 600 may be transmitted by multiple beams, such as beam 601 and beam 603. The slot format 600 may include PSS 610, SSS 614, and PBCFIs 612 and 616. The different paging DCI 602, 604, 606 may be TDM (i.e., transmitted in different OFDM symbols) and the frequency locations for the POs 621-623 may be different. Frequency locations for those CORESET, search spaces or paging DCIs 602, 604, 606 may be fixed, indicated in system information (e.g., RMSI) and/or may be a function of WTRU ID (e.g., using a modulo operation) or computed based on WTRU ID. The frequency locations for the PO DCIs 602, 604, 606 may be different or identical for beam-repetition pattern (e.g., may be the same or different for beam 601 and beam 603). The frequency location for the paging DCI 602, 604, 606 may be blind decoded.

[0102] For the cases above, the CORESET and search spaces for PO may be predefined, indicated in RMSI, or derived from RMSI. For the cases above, each PO from the WTRU’s perspective (e.g., POs 621 -623 in FIG. 6) may be defined as per a group of beams or for all beams (e.g., as a combination over a subset or a group of beams or all the beams).

[0103] A WTRU may monitor POs and associated beams with corresponding POs in order to be able to receive paging messages intended for the WTRU. For example, a WTRU may monitor a PO in a group of beams that are associated with the PO or monitor all beams for the PO. A WTRU may monitor a PO and associated SSBs with a corresponding PO. For example, a WTRU may monitor a PO in a group of SSBs that are associated with the PO or monitor all SSBs for a PO. A WTRU may monitor multiple POs (e.g., more than one PO) and associated beams with corresponding POs. A WTRU may monitor multiple POs (e.g., more than one PO) and associated SSBs with corresponding POs. A WTRU may monitor the PO derived from WTRUJD in each transmission beam which may be associated with different SSBs that are actually transmitted.

[0104] TDM and FDM may be supported for SSB and Paging DCI CORESET. Paging DCI

CORESET may be configured for FDM with SSB in a non-overlapping manner (e.g., in the case of large bandwidth transmission). Paging DCI CORESET may be configured FDM with SSB in an overlapping manner (e.g., in the case of small bandwidth transmission). The search space may or may not overlap with the SSB. If there is overlap the CORESET and SSB, then any one or more of the following actions may be performed: rate matching may be performed around the SSB, such that the NR-PDCCFI may or may not be decoded; and/or the paging DCI may be discarded for an overlapping area, which may include transmitting the DCI and message in the next PO, such that the NR-PDCCH may or may not be decoded.

[0105] Two different modes, FDM and TDM, may be used for the multiplexing of paging

DCI, and paging message(s), and 1-bit indication may be provided to switch between the modes. The indication may be carried in system information (e.g., RMSI and/or OSI). In an example, some Paging DCI CORESET may be TDM and other Paging DCI CORESET may be FDM with dynamic selection. The dynamic selection may increase scheduling flexibility. The TDM or FDM for the configuration of current paging CORESET(s) may be indicated using one or more bits. The indication may be carried in system information (e.g., RMSI and/or OSI). If the mode (e.g., FDM or TDM) is not indicated, the WTRU may perform blind detection for FDM or TDM for the paging CORESET. In an example, FDM may be used for larger bandwidths (e.g., over 6 GHz) and TDM may be used for smaller bandwidths (e.g., under 6 GHz).

[0106] In an example, POs may be configured with beam-based design. The WTRU may use discontinuous reception (DRX) in idle mode in order to reduce power consumption. One PO is a unit where there may be P-RNTI transmitted on PDCCFI addressing the paging message. One Paging Frame (PF) may be one radio frame, which may contain one or multiple POs. When DRX is used, the WTRU may only monitor one PO per DRX cycle. The WTRU in RRCJDLE and RRCJNACTIVE state may monitor paging every DRX cycle. The length of the DRX cycle may be configurable. A default DRX cycle length may be provided in system information (e.g., NR-PBCFI, RMSI or OSI). A WTRU-specific DRX cycle length may be provided to WTRU via dedicated signaling. The WTRU may be specifically configured with a PO, slot and/or mini-slot (in non-slot format) to monitor for a paging signal. The number of POs in the DRX cycle may be configurable and provided in system information (e.g., NR-PBCFI, RMSI or OSI). If multiple POs are configured by the network in the DRX cycle, then the WTRUs may be distributed to these POs based on the WTRU ID (e.g., IMSI or system architecture evolution (SAE)-Temporary Mobile Subscriber Identity (s-TMSI)).

[0107] Paging may be transmitted in different directions using (analogue) beam sweeping.

A paging DCI may use beam sweep and a paging message (PM) may use the same beam quasi- co-located with the Paging DCI. A paging DCI and a paging message may use separate beam sweeps. Examples conditions for using different beams for paging DCI and paging message include, but are not limited to, the following conditions: paging DCI and paging message may need different beams or beam widths; and/or the paging DCI beam may be outdated for the paging message (e.g., due to cross slot scheduling). [0108] A PO may comprise any set, subset or combination of time slots, non-slots (e.g., mini-slots), subframes and/or OFDM symbols. Multiple time slots, non-slots (e.g., mini-slots), subframes and/or OFDM symbols may enable transmission of paging using a different set of downlink TX beam(s) in each time slot, non-slots (e.g., mini-slots), subframe or OFDM symbols, or may enable TX/RX beam repetition. The number of time slots, non-slots (e.g., mini-slots), subframes and/or OFDM symbols (e.g., 2, 4, or 7 OFDM symbols per non-slot) in a PO may be provided in system information (e.g., NR-PBCFI, RMSI or OSI).

[0109] WTRUs may be grouped to monitor a specific PO. WTRU-specific and/or cell- specific parameters may be used to determine or derive PF and/or PO. Examples of WTRU-specific parameters may include, but are not limited to include, WTRU ID, S-TMSI, or IMSI. Examples of cell-specific parameters may include, but are not limited to include cell ID, cell timing information, SSB Index (SSBI), half radio frame number, or SFN.

[0110] The definition of a PO may be extended in the case of beam-based design. For example, the definition of the PO may depend on whether the beam sweep is performed with one beam for an entire slot or one beam per non-slot. In the case that the beam sweep is performed with one beam per slot, a PO may be defined based on slot, and the WTRU may monitor the specific slot in frame. In the case that the beam sweep is performed with one beam per non-slot (e.g., mini-slot), a beam may change (or be repeated) for every non-slot (e.g., mini-slot). In the case, a PO may be defined based on the slot in which the mini-slot exists or the PO may be defined based on the mini-slots. These approaches may be impacted by the number of SSBs or beams that are actually transmitted, and/or the maximum number of SSBs or beams.

[011 1] For example, a PO may be defined based on a slot. In this case, the PO may be defined based on the slot without any offset. A WTRU may compute its PO, which may be the slot in which the mini-slot exists. A WTRU may try to decode all the mini-slots to obtain the paging DCI and find out the paging for the WTRU. A WTRU may be able to use QCL or the latest historical association with its beam and paging location to identify the mini-slot assigned to the WTRU. A PO may be the slot or mini-slot where the beam sweep starts in the case where the beam swept PO occupies multiple slots. FIG. 7 is a resource format for example paging scheduling 700, where the POs are defined over a sweep of four beams 710, 712, 714, 716 with a mini-slot of size two symbols. The POs 701 and 702 may be defined for a mini-slot (non-slot format), which includes a subset of the OFDM symbols in slots X and X+1 , respectively. As shown in FIG. 7, the PMs may use the same beam and may be quasi-co-located with the Paging DCI (P-DCI).

[0112] In another example, a PO may be defined based on slot with offset for mini-slot.

The scheme may use SSBI as a pointer to the mini-slot for the PO (e.g., using an association). There may be different cases depending on the frequency band in which the WTRU is operating, which in turn may indicate the maximum number of SSBI or maximum number of beams. An example of number of slots to complete the sweep with one beam repetition is shown in Table 1 , where nsSym is the number of OFDM symbols per non-slot and L is the maximum number of SSBs. This may be considered as a configuration.

Table 1 : Number of slot to complete beam sweep

[0113] Using a number of beams (actually transmitted beams) and knowing the number of slots needed to complete the sweep (transmission in all the direction), the WTRU may compute the actual mini-slot location for monitoring for paging DCI. A subset of the configuration defined in Table 1 may be defined depending on the service type. URLLC or any other configuration requiring low latency may use a small number of symbols in a mini-slot (e.g., 1 or 2 OFDM symbols). An mMTC or extremely large deployment may use higher number of symbols in a mini-slot (e.g., 7 or 14 OFDM symbols).

[0114] As described above, a PO may be defined based on mini-slot. A WTRU may wake up on the specific non-slot for the PO, which may be configured in RMSI. The non-slot may include the CORESET for the paging DCI and paging message. In the case that the paging DCI is swept before the sweeping of the paging message, the WTRU may wake up during the transmission of the paging DCI sweep. FIG. 8 is a resource format for example paging scheduling 800 where the POs 801 and 802 are defined over a sweep of four beams with a mini-slot format consisting of 2 OFDM symbols 801/812, 814/816, 818/820 and 822/824, respectively.

[0115] As described above, and in any of the cases above, the WTRU may compute its own PF and/or PO. In beam-based design for paging, the computations for calculating PF and/or PO may be based on the DRX cycle, number of PO per DRX cycle, the format used being slot or non-slot based, the number of slot or mini-slots (on non-slot based format), the number of SSBs (e.g., actually transmitted SSBs or maximum SSBs) and/or the beam configuration. Table 2 gives example parameters for computation of a PF and/or PO.

Table 2: Example Parameters for Beam-based Paging Configuration and Computation of PF and/or PO

[0116] In an example, a procedure may be used for computing a PF. A PF may be defined as a radio frame in which the WTRU is looking for a PM. A PF may contain one or multiple PO(s) on one of more beams. The following example equation may be used for computing a PF:

PF = SFN mod T= (T div N_b)*(WTRUJD mod N_b) Equation (1 )

More generally, PF may be computed as PF = f (SFN, T, N, L, WTRUJD) , where f() is any function or linear combination. In another example, a PF may be predefined or preconfigured.

[0117] In an example, a procedure may be used for computing PO(s). A PO may be a slot and/or mini-slot (non-slot) within a slot, where a P-RNTI may be transmitted on PDCCFI addressing a PM for the WTRU. There may be one or more than one PO for each WTRU in a DRX cycle.

[0118] A function for computing a PO may be defined based on parameters (e.g., the number of subframes Ns, and/or an index i_s pointing to the PO). A different function may be defined for same-slot or cross-slot scheduling for paging DCI and/or PM. The following example equation may be used for computing a PO:

PO = (i_s *La + SSBI) * nsSym Equation (2)

PO = (i_s *La + SSBI) * nsSym + Offset(Ls) Equation (3) such that all the POs may or may not be located contiguously, and where the Offset() function may be a pattern that may shuffle the order of different POs. The Offset() function may be used to allocate the POs non-contiguously. The functions in Equations (2) and (3) may also assume that a beam sweep for a first PO may be followed by beam sweep for a second PO, and a third PO and so on, as shown in FIG. 9. FIG. 9 is a resource format for example paging scheduling 900 where POs 901 , 902, 903 are swept together (e.g., the first PO 901 is beam-swept (transmitted all the directions), then the second PO 902 is beam-swept, then the third PO 903 is beam-swept). For example, a WTRU may monitor PO 901 that is part of group of beams (e.g., beams 910, 912, 914, 916) that are associated with PO 901 , PO 902 in a group of beams (e.g., beams 910, 912, 914, 916) that are associated with the PO 902, and PO 903 in a group of beams (e.g., beams 910, 912, 914, 916) that are associated with PO 903.

[0119] In another example, the WTRU may monitor each PO in all beams. In another example, multiple POs may be combined for each beam, and the set of POs may be swept across beams as shown in FIG. 10. FIG. 10 is a resource format for example paging scheduling 1000. In the example of FIG. 10, POs 1001 , 1002, 1003, 1004 may be combined for each beam 101 1 , 1012 and 1013.

[0120] In an example, the index i_s pointing to (or associated with) a PO from subframe pattern may be defined in the predefined table with i_s and corresponding slot (or mini-slot) number in which PO may be transmitted. In another example, the index i_s may be derived using the following example equation:

i_s = floor(WTRUJD/N) mod Ns Equation (4)

If QCL is not assumed, then it may be assumed that the SSBI is defined over the range 0 to L-1 , where L is the maximum number of SSBs in a frame. In this case, L beams may be swept for the process of transmitting paging. In another embodiment, a PO table may be defined as an association between i_s and the slot where PO may be transmitted. Different sets of tables (or associations) may be defined (between i_s and/or the slot of paging DCI and/or the PM) for same- slot or cross-slot scheduling for paging DCI/PM.

[0121] In an example, the WTRU may wake up to monitor a PO in a specific slot or nonslot within the paging periodicity. Paging periodicity may be configured in system information or control signaling (e.g., NR-PBCFI, RMSI or OSI). For transmission of the paging DCI and paging message, different modes may be configured for the WTRU. Example modes include slot-based, non-slot-based, or hybrid slot and non-slot-based modes of transmission for paging. The mode of transmission may be configured in system information or control signaling (e.g., NR-PBCH, RMSI or OSI).

[0122] In an example of slot-based paging, a slot-based paging DCI may be followed by slot-based paging message. In an example of non-slot based paging, a non-slot based paging DCI may be followed by non-slot based paging message. In examples of hybrid paging, a non-slot based paging DCI may be followed by slot-based paging message, or a slot-based paging DCI may be followed by a non-slot based paging message.

[0123] Examples of numerology may include, but is not limited to include, subcarrier spacing (SCS) and cyclic prefix (CP). A numerology for paging may include numerology for the paging DCI and the paging message. The numerology for paging may be identical to, or derived from system information (e.g., RMSI), which may be indicated in system information (e.g., in NR- PBCH). The paging DCI and paging message may or may not have the same numerology, and the paging numerology may or may not be same as the numerology for other messages, such as random access channel (RACH) message 2 and message 4.

[0124] A PO may be defined or derived based on any one or more of the following parameters: a number of FDM POs; a number of TDM POs; a WTRU ID; an SSBI; per group of beams or all beams; per group of SSBs or all SSBs; preamble index; RACH resource index; slot index or non-slot index; OFDM symbol index; search space index; search space set index; CORESET index; Bandwidth Part (BWP) index; carrier index; cell index or cell ID; and/or transmit and receive point (TRP) index. For example, a PO may be defined or derived based on a combination of paging DCI and paging message in which paging DCI and the paging message may be in the same or different slot, mini-slot or non-slot. In another example, a PO may be defined or derived based on any one or more of the following: a search space, a group of search spaces, a search space set, a group of search space sets, a CORESET, a group of CORESETs, a BWP, and/or a group of BWPs.

[0125] The above techniques may be used to reduce the number of beams and time needed for monitoring paging in a beam swept system. In an example, a procedure for determining the beams to monitor for paging and beam sweeping may be defined by a relationship among paging CORESETs, paging messages, and/or SSBs. In an example, a paging multiplexing type (PMT) may be defined based on the relationship among paging CORESETs, paging messages, and/or SSBs for determining the beams for paging. FIG. 11 is a flow diagram of an example paging beam selection procedure 1100, which may be performed by a WTRU. At 1102, the WTRU may receive configuration information (e.g., numerology, beam SCS, DRX cycle) for paging, for example via system information (e.g., RMSI). At 1 104, the WTRU may determine numerology (e.g., SCS, CP) for paging and SSB for the paging beams, and determine a SCS for each of SSB and paging DCI/message. At 1 106, it is determined if the SCS for SSB and paging reception are the same or different. If the SCS for SSB and paging reception are different, then at 1 108 the PMT is determined for a 1 ^st type of PMT (PMT A). If the SCS for SSB and paging reception are the same, then at 11 10 the PMT is determined for a 2nd type of PMT (PMT B). At 1 112, a beam, time and frequency relationship among a paging CORESET, a paging message, and an SSB may be determined based on the determined PMT (PMT A or PMT B). In an example, for PMT A where the SCS for SSB and paging reception are different, the paging CORESET may be TDM with the paging message (e.g., using a repeated beam), the paging message may be time aligned (in the same slot) as the SSB, and the paging message may be FDM with the SSB. In an example, for PMT B the SCS for SSB and paging reception are the same, the paging CORESET may be TDM with the paging message (e.g., without using a repeated beam), the paging CORESET and the paging message may be time aligned (e.g., in the same slot) with the SSB and FDM with the SSB. At 11 14, the WTRU may monitor a PO in one or more beams of the PO based on the determined beam, time and frequency relationship.

[0126] FIG. 12 is a messaging diagram of an example paging multiplexing format 1200 during a PO 1210, for PMT A where there is different SCS between paging messages 1206 and SSB 1208. In the example of FIG. 12, 2L beams are repeated for paging CORESET 1204 and paging message 1206/SSB 1208 per PO 1210. In other words, beams 1202_I...1202_L are each repeated one time in the PO 1210 (for a total of two transmissions per beam in PO 1210). The paging CORESET 1204 and paging message 1206 may be TDM on each beam 1202_I...1202_L (i.e., across the two transmissions on each beam 1202_I...1202_L). The SSB 1208 may be FDM with the paging message 1206 on the second transmission for each beam 1202_I...1202_L.

[0127] FIG. 13 is a messaging diagram of an example paging multiplexing format 1300 during a PO 1310, for PMT B where there is the same SCS between paging messages 1306 and SSB 1308. In the example of FIG. 13, L beams 1302_I...1302_L are transmitted for paging CORESET 1304 and paging message 1306/SSB 1308 per PO 1310. Beams 1302_I...1302_L are transmitted once in the PO 1310. The paging CORESET 1304 and paging message 1306 may be TDM on each beam 1302_I...1302_L (within the same beam transmission). The SSB 1308 may be FDM with the CORESET 1304 and paging message 1306 for each beam 1202_I...1202_L.

[0128] Examples of configuration for POs are described herein. ^{SFN pagmg} and ^{/ϊ ,}"'^ί'"^ίί' may be defined as the SFN and slot index of the CORESET, respectively, for paging based on SCS of the paging CORESET.

the WTRU may determine a number of consecutive resource blocks and/or a number of consecutive symbols for the CORESET that includes the paging search space, using paging configuration (e.g., in RMSI) and/or The WTRU’s own WTRUJD.

[0129] A WTRU may be configured with a paging search space configured by a higher layer parameter. For example, using PDCCFI candidates, control channel element (CCE) aggregation levels, and/or known P-RNTI, a WTRU may be able to blind-decode the paging DCI. There may be multiple paging search spaces configured (e.g., in potentially different CORESETs) and the WTRU may select one of paging search spaces based on its WTRUJD. If the WTRU is not provided higher layer parameter(s) for the paging-search space, the association between monitoring occasions for paging search space and the SS/PBCH block index may be the same as the association of monitoring occasions for RMSI. In all the occasions, the SCS and the CP length for the PDCCFI paging search space may be the same as for search space for RMSI.

[0130] The paging CORESET(s) may be TDM or FDM with an SSB. This may be based on the multiplexing pattern used for SSB and RMSI CORESET. Different multiplexing schemes for POs for different WTRU groups may be used. Different POs for different WTRU groups (e.g., based on WTRUJD) may be TDM or FDM. In beam-based systems, FDM POs may reduce the beamsweeping overhead for paging. TDM PO may be defined in terms of different slots in which the paging DCI may be present. FDM of multiple POs may be performed in terms of multiple BWP, CORESETs and/or search spaces in which paging DCI may be present. Flowever, two-dimensional multiplexing (i.e., TDM and FDM) may offer added flexibility.

[0131] The default association between SSB and monitoring window of PDCCFI containing a paging DCI may be same as association between the SSB and its RMSI monitoring window. In an example, RMSI may be transmitted at a maximum of every 160 ms. Flowever, paging may be transmitted based on a DRX cycle, which may be configured to a particular WTRU. Based on the DRX cycle, a WTRU may be able to identify the frame for the PO. If multiple WTRUs are paged in FDM POs, the formulas to compute the paging frame may be modified. The number of paging frames within the WTRU’s DRX cycles, N, and the number of subframes used for paging within paging frame, Ns, may be modified based on the number of FDM POs (nFDMp). This may in turn modify the computation of SFN that the WTRU monitors for paging based on nFDMp.

[0132] In an example, the SFN may be computed for paging based on WTRUJD, configured DRX cycle for the WTRU, T, and the number of FDM POs. If all POs are transmitted in TDM fashion, nFDMp may be set to 1. T may be the DRX cycle of the WTRU (example values include 32, 64, 128, 256). nB may be a number of PO per DRX Cycle (example values include T, 2T, T, T/2, T/4, T/8, T/16, T/32, T/64, T/128, and T/256). nFDMp may be the number of FDM PO (e.g., search spaces/BWP or different CORESET). N may be a number of paging frames within the WTRU’s DRX cycle (example values may include Min (T, nB /nFDMp), or [T, T/2, T/4, T/8, T/16, T/32, T/64, T/128, and T/256]/ nFDMp). Ns may be a number of subframes used for paging within a paging frame (an example formula may be Ns= Max (1 , nB/ (nFDMp *T)): (16,8,4,2,1 )/nFDMp). For computing the SFN for paging ( SFN_paging mod T), the paging may be transmitted in a frame where SFN mod T is equal to (T div N )*(WTRUJD mod N).

[0133] A different physical resource may be defined for multiplexing multiple POs. For example, a physical resource may be defined based on search spaces, CORESETs, BWPs, and/or slots (or mini-slots). Slot (or mini-slot) based multiplexed POs, TDM POs and search space, CORESET and BWP based multiplexed POs, and FDM POs may be considered. If different slots are used to enable TDM of POs, the slot offset may be computed from a reference point. For example, the reference point may be a 5 ms boundary, start of system frame, computed CORESET location for TypeO-PDCCFI (e.g., configured by NR-PBCFI) or a different (e.g., fixed or configured) periodicity. The slot offset may be computed as function of the WTRUJD of the WTRU. If different BWPs are used to enable FDM of POs, the BWP for paging DCI may be configured by the gNB or may be a function of the WTRUJD. If a BWP is a function of the WTRUJD, the BWP used for paging may be computed by the WTRU to locate a PO to monitor.

[0134] If different CORESETs are used to enable FDM of POs, the CORESET index for a paging DCI may be configured by the gNB. The CORESET index may be part of the search space configuration. If the CORESET carrying a PO is a function of WTRUJD, the CORESET may get reflected in the search space ID (SearchSpaceJD). The corresponding search space may be associated with the CORESET carrying the PO. If different search spaces are used to enable multiple FDM of POs, the search space index for the paging DCI may be configured by the gNB or may be computed by the WTRU using the WTRUJD. A combination of any of BWP, CORESET and/or search space may be used for multiplexing different PO during a beam sweep. For full flexibility, TDM, FDM or hybrid TDM/FDM may be used between different POs. POs for these scenarios are defined herein.

[0135] In an example of a multiplexing pattern (“multiplexing pattern 1”), the PO configuration may be such that the RMSI CORESET may be TDM with SS/PBCH block and a default association for paging monitoring may be the same as the RMSI monitoring window. In an example of a PO configuration for multiplexing pattern 1 , TDM may be used for different POs. A PO may be defined as a period of beam sweeping with different slot offsets from the RMSI CORESET associated with the PO. The RMSI may also be beam swept. The time offsets for each POs may be fixed, configured or based on the WTRUJD. The time offsets may be defined in terms of slots or non-slot (mini-slots) (e.g. 2,4,7 OFDM symbol slots). The frequency of monitoring the PO may depend on the DRX cycle and/or the SFN to be monitored for the paging, which may be computed by the WTRU. For the SS/PBCH block that is actually transmitted with SSBI /^', the WTRU may determine an index of the paging monitoring slot (or mini-slot) n_paging within a paging frame using a function. The paging monitoring slot (or mini-slot) n_paging may be a function of WTRUJD, and/or the 0, M values (0 and M may be predefined for example in a WTRU procedure for monitoring TypeO-PDCCFI common search space) for RMSI CORESET (which may be configured in NR-PBCFI). In this case, the number of FDM POs (nFDMp = 1 ) may be 1. A different slot offset may be computed based on the index for the PO i_s, which may be computed using the WTRUJD, a number of paging frames within the WTRUs DRX cycle (N), and/or a number of subframes used for paging within paging frame (Ns). This slot offset may be tabulated or may be a function based on different variables, such as i_s, and/or SOS used for the paging PDCCFI.

[0136] The following is an example equation to compute a slot n_paging containing a PO using the WTRUJD:

Equation (5)

f(i_s ) is a table, function (e.g., hash function) or other association that associates index i_s to the paging slot number, and i_s = floor(WTRUJD/N) mod Ns (PO according to WTRUJD). In Equation (5), 0 and M are defined for RMSI CORESET. A computation of the slot offset may also depend on the SCS (m). A computation for K^ ^ing may be modified if mini-slot based sweep is performed, but the general concept remains the same. A PO may be defined by tίr aging for the entire sweep of beams (e.g., for i = 0-63 for >6GHz, i=0-7 for <6GHz, or more generally depending on the number of actually of transmitted SSBs).

[0137] In another example, the same equation as an RMSI CORESET ma be used to compute a slot containing a PO using the WTRUJD:

)mod N ^ ^m Equation (6) tz paging

o_{p s} - slot _ offset Equation (7) where o_{p s} is a PDCCFI monitoring offset, which may be configured by parameter monitoringSlotPeriodicityAndOffset for the search space for paging, and K^ ^ing = f(i_s) is a table, function (e.g., hash function) or other association that associates index i_s to the paging slot number. In o_{p s}, s may be the search space set index used for paging, and p = 0, which is the index for RMSI CORESET. The slot in which paging occurs may depend on SCS. [0138] A time duration for the paging CORESET may be defined by the top level parameter CORESET-time-duration-paging or may be the same as RMSI CORESET. A set of resource blocks for the paging CORESET may be defined by a top level parameter CORESET-freq- dom-paging or may be the same as the RMSI CORESET.

[0139] In an example, paging may be transmitted in each BWP in the same slot or slots in staggered fashion. If it is in staggered fashion, the BWPJD may be used to compute the n_paging slot containing the PO. The multiple sweeps for the PO may be mini-slot based to decrease overhead of the sweeping.

[0140] FIG. 14 is an example multiplexing pattern 1 for a PO configuration 1400 where the paging CORESET is TDM with SS/PBCH block. S is the OFDM symbol number, and a slot includes 14 symbols. In this example, slot 1413 includes OFDM symbols 28-41. Arrows indicate OFDM symbols that are quasi-co-located and transmitted on a same beam. The slot n_paging(4,1 ) includes PO 1401 for beams associated with beam 1444 and 1455. In the notation n_paging(x,y), the first index x, is the SSBI (associated the slot n_paging) and second index y is the ID of PO (pojd). In this example, M = 0.5 (and may be predefined, as described above), which implies two SSB 1404 and 1405 may be associated with the slots n_paging(4, 1) and n_paging(4,2), respectively, containing two paging CORESETs. A WTRU that is synchronized to SSBI 1404 may receive the corresponding location in subsequent slots indicated by SSB1 1404 to find the paging CORESET or paging DCI. In this case, slot n_paging(4, 1 ) and n_paging(4,2) may be identical. The slot n_paging(4,2) may include PO 1402 for beams associated with beam 1444 and 1445. In the example of FIG. 14, each PO 1401 and 1402 may be transmitted in its own beam sweep. This method may have higher latency, but the implementation is greatly simplified by reducing the number of beams for paging. The WTRU may be configured (implicitly or explicitly) to monitor only one search space 1421 corresponding to the PO 1401 and/or 1402 in different beams 1444 and 1445 based on the WTRUJD to receive paging messages 1431 and/or 1432.

[0141] In another example, different (TDM) POs may occur with the same periodicity of

SSB. For example, if SSBs are transmitted at slot T1 , T2, T3, T4, then P01 may be transmitted at slot T1 +K, P02 may be transmitted at slot T2+K, and so on, where K is an offset. The value of offset K may be 0 or any value greater than 0. In this case in TDM mode, identical paging DCI and paging messages may be transmitted in all the BWP with cell defining SS/PBCH block. In an example, a paging DCI and paging message may be transmitted for a WTRU’s initial active BWPs and hence a different paging message may be transmitted in each BWP which may depend on the different WTRUs camped on that BWP. A gNB may register the initial active BWP with the cell defining SS/PBCH Block. In an example, a mechanism may be defined for the WTRU to indicate to the gNB its cell-defining SS/PBCH block.

[0142] An example procedure performed by a WTRU for determining the configuration of

POs that are TDM is described herein. The WTRU may synchronize with PSS/SSS and/or receive a MIB from the PBCH. The WTRU may find a CORESET for RMSI from the MIB and perform blind decoding for TypeO-PDCCH. The WTRU may receive SIB1 from the PDSCH as indicated by the TypeO-PDCCH. The WTRU may find paging configurations and configure a DRX cycle and paging- searchSpace. The WTRU may compute SFN_pagmg using the DRX cycle and WTRUJD. The WTRU may compute the index i_s based on the DRX cycle and WTRUJD. Using i_s, the WTRU may compute the offset for a PO from the RMSI CORESET.

[0143] The WTRU may find the slot(s), non-slot(s) or mini-slot(s) in which it is supposed to monitor paging (e.g., for each of the beams). The SS/PBCH Block and associated paging search space may be quasi-co-located. Hence, the WTRU may use an associated beam for each slot. If the SSB that are actually transmitted are different from the defined SSB, the association between the paging search space may be performed with a logical index of SS/PBCH block or a physical index (or SSBI). If there are not further actions for the WTRU, the WTRU may enter IDLEJVIODE.

[0144] The WTRU may wake up in a slot according to a computed SFN and associated with a strongest last registered beam. If the WTRU is configured for sweeping beams, the WTRU may wake up in a first beam and sweep all the beams in slots associated with the PO for the WTRU. The WTRU may use slot or mini-slot computations, for example as described above. Using the search space definitions for paging, the WTRU may find the paging CORESET. If the CORESET is not defined, the WTRU may use CORESET 0 (e.g., CORESET for RMSI). The WTRU may use a search space table to blind decode the Type2-PDCCH using P-RNTI. If the WTRU finds Type2- PDCCH, the WTRU receives the PDSCH indicated by the PDCCH to determine if the WTRU was paged. If the WTRU was paged, the WTRU may establish a connection with the gNB. If the WTRU was not paged, the WTRU may revert to IDLEJVIODE.

[0145] In another example of a PO configuration for multiplexing pattern 1 , FDM may be used for different POs. In an example, a PO may be transmitted only on a WTRU’s initial active BWP (i.e., the BWP first synchronized on by the WTRU). In this case, the WTRU may switch from a current active BWP to the initial active BWP for its PO to check if it was paged. It may be assumed that the paging message is transmitted in the same BWP as the paging (indicator) DCI. If a disproportionately large number of WTRUs have the same BWP as their initial active BWP, then load balancing may be challenging for the gNB. In this case, the POs for different WTRUs may be distributed amongst different BWPs based on WTRUJD. [0146] In this case, a PO may be defined as a period of beam sweeping for the RMSI

CORESET associated with the PO. All the POs may FDM together in a same slot without an offset. The POs may be in a different search space and in a same or different CORESET of the same slot. The search space (and associated CORESET) for the WTRU to monitor for Type2-PDCCH may depend on the WTRUJD. The frequency for the WTRU to monitor the PO may depend on DRX, and the SFN to be monitored by the WTRU for paging may be computed by the WTRU. The paging slot computation may be same as for RMSI.

[0147] Different POs may be transmitted on all BWPs, or multiplexed over BWPs. If the

POs are multiplexed in different BWPs, the BWP to monitor for a WTRU may be configured by the gNB or computed by the WTRU and may depend on WTRUJD. For example, if there are a total of 4 FDM POs, and there are 2 BWPs on which POs are multiplexed, each BWP may contain 2 POs. This distribution may be a function of the WTRUJD. The 2 POs in a same BWP may be in the same or a different CORESET.

[0148] In each BWP, a PO may be assigned to different search spaces. These search spaces may be associated with a same CORESET or a different CORESET. If the search spaces are associated with different CORESETs, the CORESET to monitor by a WTRU may be predefined for or based on the WTRUJD. For example, if there are 4 POs in a BWP, and there are 2 CORESETs on which POs are multiplexed, each CORESET may contain 2 POs in two search spaces. This distribution may be a function of the WTRUJD. The search space with the CORESET-ID may be computed by the WTRU using the WTRUJD. If the CORESET-ID is not computed by the WTRU using the WTRUJD, the gNB may indicate the associated paging CORESET while configuring the paging-searchSpace. POs in the same CORESET may be in different search spaces. These search spaces may be pre-configured to groups of WTRUs or a WTRU may be able to compute the common search space for monitoring the WTRU’s PO using the WTRUJD. In order for a WTRU to compute a slot to monitor for the PO, the same formula for RMSI may be used. The BWP, CORESET and/or search spaces to be monitored by the WTRU may be function of the WTRUJD. The BWP, CORESET and/or search spaces may be function of any one or more the following parameters: a total number of POs; a number of FDM POs in BWP (nFDMp_bwp); a number of FDM POs in CORESETs (nFDMp_coreset); a number of FDM POs in search spaces (nFDMp_ss); nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss] for the cases where there is no TDM of PO; a number of paging frames within the WTRU’s DRX cycle; and/or a number of slots used for paging within a paging frame.

[0149] An example of a PO computation is described in the following. The slot containing the PO may be calculated using the following equation:

In the case of a different number of actually transmitted SSBs, a logical index of the SSB may be associated with the slot for the paging sweep. The BWP to be monitored and the search space to be monitored may be a function of the PO index and/or a total number of FDM POs in each of the dimensions mentioned above (e.g., BWP, CORESET, search space). The CORESET associated with each search space may be included in the search space configuration and hence may not be explicitly mentioned.

[0150] In this example, the ID of the BWP may be calculated as BWPJd = f (POJd, nFDMp), and the ID of the search space may be calculated as SearchSpaceJd = f (POJd, nFDMp), where POJd may be an index of the PO. The number of FDM POs may be calculated as nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss], where nFDMp_bwp is the number of FDM POs in a BWP, nFDMp_coreset is the number of FDM POs in a CORESET, and nFDMp_ss is the number of FDM POs in a SS. If the number of FDM POs in a BWP is nFDMp_bwp = 1 , then that may imply that the POs are not multiplexed over the BWP, or same the POs are transmitted on different configured BWPs. If the number of FDM POs in a CORESET is nFDMp_coreset = 1 , then that may imply that the POs are not multiplexed over CORESETs. An index of the PO (POJd) may be computed using WTRUJD and a modulo (mod) function, for example POJd = floor(WTRUJD/N) mod Ns. In this example scenario, a gNB scheduler may avoid the overlap of paging CORESETs with RMSI-CORESET if the two CORESETs are different. In an example, multiple RNTI may be used for paging on the same common search-space. The multiple different RNTIs may be assigned to different groups of WTRUs (e.g., based on WTRUJD). If multiple RNTIs (or a range of RNTI) are used for paging, a WTRU may be able to identify its own RNTI based on its WTRUJD and may be able to find its PDCCFI that includes its paging DCI. The multiple RNTIs may be selected from a range of paging RNTI (PG-RNTI).

[0151] FIG. 15 is another example multiplexing pattern 1 for a PO configuration 1500 where the paging CORESET is TDM with an SS/PBCH block. In Fig. 15, it may be assumed that the SCS is 120 kHz corresponding SS/PBCH block pattern. S is the OFDM symbol number, and a slot includes 14 symbols. In this example, slot 1513 includes OFDM symbols 28-41 (e.g., corresponding to a 3^rd slot in the SS/PBCH block pattern). In the example of FIG. 15, M = 0.5 (and may be predefined, as described above). Flence, two beams with SSBIs 1504 and 1505 may be associated with the same slot 1513 containing two different paging CORESETs (each with 4 OFDM mini slots) in slot n_paging for the two different beams with SSBI 1504 and 1505, respectively. OFDM symbol S = 32,33,34,35 may be transmitted in one direction and OFDM symbol 36,37,38,39 may be transmitted in another direction (i.e., on different beams). Both CORESETs may include POs 1541 - 1544 in 4 different search spaces (SSp) 1521-1524. The WTRU may find the paging search space 1521 -1524 associated with the WTRU using its WTRUJD so that the WTRU may find its own PO from 1541 -1544, and locate paging messages 1531 -1534.

[0152] FIG. 16 is another example multiplexing pattern 1 for a PO configuration 1600 where the paging CORESET is TDM with an SS/PBCH block. In the example of FIG. 16, two beams with SSBI 1604 and 1605 are associated with the same slot 1613 containing four different paging CORESETs (two paging CORESETs associated with SSB1 1604 have 4 OFDM symbol minislots, and two paging CORESETs associated with SSBI 1605 have 3 OFDM symbol mini-slots). Each beam in slot n_paging (two beams total) is associated with two CORESETs each with two search spaces: search spaces 1631 and 1632, and search spaces 1633 and 1634, respectively. The WTRU may find its paging search space and CORESET (e.g., search spaces 1621 and 1622 associated with respective beams associated with SSBI 1604 and 1605 combine to make a CORESET) depending on a WTRUJD and finds its own PO (e.g., PO 1641 , 1642, 1643 or 1644).

[0153] FIG. 17 is another example multiplexing pattern 1 for a PO configuration 1700 where the paging CORESET is TDM with an SS/PBCH block. In the example of FIG. 17, four beams with SSBI 1704, 1705, 1706 and 1707 are associated with the same slot 1713, which may contain four different paging CORESETs. Each beam (e.g., symbols S = 32,33,34,35 are transmitted in one direction and symbol 36,37,38,39 are transmitted in another direction on different beams) is associated with one CORESET with four search space SS 1721 -1724 for each CORESET. The WTRU may find the paging search space (e.g., SSp 1721 , 1722, 1723, and/or 1724 depending on which SSBI 1704, 1705, 1706, or 1707 that the WTRU is synchronized to) and CORESET based on its WTRUJD and finds its own PO based on the SS/PBCH block 1704, 1705, 1706, or 1707 that the WTRU synchronizes to. The paging slot n_paging may include 4 POs FDM in each beam and transmitted in four beams.

[0154] In the examples described above, the paging DCI (e.g., PDCCFI) and the paging message (e.g., PDSCFI) may be in the same slot. Flowever, PDCCFI may schedule the PDSCFI in a different slot (e.g., cross slot scheduling). A PO may include the pair of paging DCI and paging message for the entire beam sweep. In the case of cross slot scheduling, the PPO may include different and/or more slots than in slot-based scheduling where the paging message and paging DCI are in the same slot. In the examples described herein, different common search spaces may be assigned to different groups of WTRUs for paging. In this case, a group common search space may be used for the purpose FDM POs.

[0155] An example procedure performed by a WTRU for determining the configuration of

POs that are FDM is described herein. According to the example procedure, a WTRU may synchronize with PSS/SSS and may receive a MIB from the PBCH. The WTRU may find a CORESET for RMSI from the MIB, and perform blind decoding for TypeO-PDCCH. The WTRU may receive a SIB1 from the PDSCH pointed by the TypeO-PDCCH. The WTRU may find paging configurations including a DRX cycle, a paging-searchSpace and nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. The WTRU may compute SFN_paging using the DRX cycle, WTRUJD and/or the number of FDM POs. The WTRU may compute the POJd based on DRX cycle, WTRUJD and/or the number of FDM POs. Using a POJd and/or nFDMp, the WTRU may compute BWPJd and/or SearchSpaceJd. The CORESETJd may be associated with the SearchSpaceJd. Hence, using a different CORESET may be reflected in a different SearchSpaceJd.

[0156] The WTRU may find the slot(s) or mini-slots in which it is supposed to monitor the

SearchSpaceJd and BWPJd (e.g., for some or all the beams). The SS/PBCH Block and associated paging search space may be quasi-co-located. Hence, the WTRU may use an associated beam for each slot. The paging search space may be a group-common search space. If the SSB actually transmitted are different than the defined SSB, the association between the paging search space may be performed with the logical index of the SS/PBCH block or the physical index (or SSBI). The WTRU may use resource block 0 (RBO) of the common search space (same SearchSpaceJd with different RB offset for each of the WTRU groups) and may use the WTRUJD to compute the offset for each group. If the WTRU has no more actions to complete, the WTRU may enter IDLEJVIODE.

[0157] The WTRU wakes up in the computed SFN slot (or mini-slot) associated with the strongest last registered beam. If the WTRU is configured for sweeping beams, the WTRU may wake up in a first beam and sweep all the beams in slots associated with the PO for the WTRU. The WTRU may use the slot or mini-slot computations, for example as described above. Using the search space definitions for paging, the WTRU may find the paging CORESET in the precomputed BWPJd. The WTRU may use the search spaces table to blind decode the Type2-PDCCH using P- RNTI. If multiple RNTI are assigned from a group of paging RNTI (PG-RNTI), the WTRU may use the RNTI used for its own group. This RNTI for the WTRU may be derived using WTRUJD or may be assigned to the WTRU using (e.g., WTRU-specific) RRC signalling. If the WTRU finds Type2- PDCCH, the WTRU receives the PDSCH indicated by the PDCCH to determine if the WTRU was paged. If the WTRU was paged, the WTRU may establish a connection with the gNB. If the WTRU was not paged, the WTRU may revert to IDLEJVIODE.

[0158] In an example of a PO configuration for multiplexing pattern 1 , a hybrid of TDM and

FDM may be used for different POs. A combination of the any of the methods for TDM and FDM described above may be used for hybrid TDM and FDM, and may be fully flexible in terms of scheduling POs for different users. Using hybrid TDM and FDM, POs may be distributed in terms of time and frequency. The frequency of monitoring the PO may depend on DRX. The SFN to be monitored for the paging may computed by the WTRU, for example as described above. Each beam in the PO may be associated with a different SS/PBCH block. The time offset in terms of slot(s) (or mini-slot(s)) may be applied to compute the PO. The time offset may be preconfigured or based on the WTRUJD.

[0159] Different POs may be present on all BWPs, or multiplexed across BWPs. If the different POs are multiplexed across different BWPs, the BWP to be monitored by the WTRU may be configured by the gNB or computed by the WTRU and may depend on the WTRUJD. In an example, for a total of 4 POs, 2 POs may be FDM in a slot and the other 2 POs may be TDM in different slots. Each BWP may contain 2 POs per slot. This distribution may be a function of the WTRUJD.

[0160] In each BWP, a PO may be assigned to different search spaces in different slots.

The search spaces may be associated with the same CORESET or different CORESET. If the search spaces are associated with different CORESETs, the CORESET to be monitored by the WTRU may be predefined or based on the WTRUJD. In an example, for 4 POs in a BWP, there may be 2 CORESETs on which POs are multiplexed, and each CORESET may contain 1 PO in two different slots. This distribution of slots and CORESETs may be function of the WTRUJD.

[0161] If the search spaces are associated with the same CORESET, the search space to be monitored by the WTRU may be predefined or based on the WTRUJD. In an example, if there are 4 POs in a BWP, and there are 2 search spaces on which POs are multiplexed, each search space may contain 1 PO in two different slots. This distribution of slots and search space may be function of the WTRUJD. Similarly, there may be a multi-dimensional mapping of POs over different search spaces present in different CORESETs in different BWP in multiple slots. Flence, a group common search space may be for FDM POs.

[0162] The slot number for a PO n_paging may be computed using a formula similar to RMSI, but may include an offset. As a result, the time offset, BWPJd, SearchSpaceJd and/or CORESETJd may be function of the WTRUJD. The time offset, BWPJd, SearchSpaceJd and/or CORESETJd may also be a function of any one or more of the following parameters: total number of POs; total number of TDM POs (nTDMp); a number of FDM POs in BWP (nFDMp_bwp); a number of FDM POs in CORESETs (nFDMp_coreset); a number of FDM POs in search spaces (nFDMp_ss); nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]; number of paging frames within the WTRUs DRX cycle; and/or a number of subframes used for paging within a paging frame. [0163] For each SSBI i, there may be a quasi-co-located location for paging. For a PO, all values of i (or the entire beam sweep) may be included in equation for calculating the slot number for a PO npaging. An example of such a calculation is given in the following equation:

Equation (9)

In a case of a different number of actually transmitted SSBs, the logical index of the SSB may be associated with the slot for the paging sweep.

[0164] In an example, the following parameters may be a function of POJd, nTDMp, and/or nFDMp: K^ ^m3, BWPJd, and/or SearchSpaceJd. In other words, [ K^₀ ⁿ⁹ , BWPJd, SearchSpaceJd] = f(PO_id, nTDMp, nFDMp), where K³“₀ ³ _t ^m9 may be the slot in which paging occurs, BWPJd may be BWP where paging is found, SearchSpaceJd may be the search space where paging DCI may be found. If the total number of TDM POs nTDMp = 1 , that may imply that all the POs are transmitted using FDM in a same slot. If the total number of TDM POs nTDMp = total number of POs, that may imply that all the POs are transmitted in different slots and not FDM. In this scenario, the BWP, CORESET, and/or search space may be identical. The number of FDM POs nFDMp may be a function of (nFDMp_bwp, nFDMp_coreset, nFDMp_ss). If a number of FDM POs in a BWP nFDMp_bwp = 1 , that may imply that the POs are not multiplexed over the BWP, or the same POs are transmitted on different configured BWPs. If a number of FDM POs in CORESETs nFDMp_coreset = 1 , that may imply that the POs are not multiplexed over CORESETS. An index of the PO (POJd) may be computed using the WTRUJD and a modulo function, for example POJd = floor(WTRUJD/N) mod Ns. The function f() in this case may be a round robin distribution function or a complex hashing function, and/or may be based on SFN_paging.

[0165] An example procedure performed by a WTRU for determining the configuration of

POs that are hybrid FDM and TDM is described herein. According to the example procedure, a WTRU may synchronize with PSS/SSS and receive the MIB from the PBCH. The WTRU find the CORESET for RMSI from the MIB, and perform blind decoding for TypeO-PDCCFI. The WTRU may receive SIB1 from the PDSCFI as indicated by the TypeO-PDCCFI. The WTRU may find paging configurations from the SIB1 , including for example a DRX cycle, a paging-searchSpace, nTDMp and/or nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. The WTRU may compute SFN_paging using the DRX cycle, WTRUJD and/or a number of FDM POs. The WTRU may compute the POJd based on the DRX cycle, the WTRUJD and/or the number of FDM POs. Using POJd, nFDMp and/or nTDMp, the WTRU may compute a slot (or mini-slot) offset

BWPJd, and/or SearchSpaceJd (and CORESETJd associated with the SearchSpaceJd). The slot offset may depend on the SOS. The SS/PBCFH Block and associated paging search space may be quasi-co- located. Hence, the WTRU may use an associated beam for each slot. If the SSB actually transmitted are different than the defined SSB, the association between the paging search space may be performed with the logical index of the SS/PBCH block or the physical index (or SSBI). The paging search space may be a group-common search space. The WTRU may use RBO of the common search space (same searchSpaceJd with different RB offset for each of the groups) and may use the WTRUJD to compute the offset for each group. The WTRU may find the slot(s), non- slot(s) or mini-slots in which it is supposed to monitor the searchSpaceJd and BWPJd (e.g., for all the beams). The WTRU may enter IDLEJVIODE.

[0166] The WTRU may wake up in the computed SFN slot (or mini-slot) associated with the strongest last registered beam. If the WTRU is configured for sweeping beams, the WTRU may wake up in a first beam and sweep all the beams in slots associated with the PO for the WTRU. The WTRU may use slot or mini-slot computation as described above. The WTRU may find its slot (or mini-slot) as computed using slot offset o_{p s} or Ksiofoff_Set ^{for the}

Using the paging search space definition, the WTRU may find the paging CORESET in the precomputed BWPJd in the previously found slot and may use the search spaces table to blind decode the Type2-PDCCH using P-RNTI. If multiple RNTI are assigned from a group of paging RNTI (PG-RNTI), the WTRU may use the RNTI used for its own group. This may be derived using WTRUJD or assigned to the WTRU using WTRU-specific (e.g., RRC) signalling. The WTRU may find Type2-PDCCH, the WTRU receives the PDSCH indicated by the PDCCH to determine if the WTRU was paged. If it was paged, it establishes connection with gNB. If the WTRU was paged, the WTRU may establish a connection with the gNB. If the WTRU was not paged, the WTRU may revert to IDLEJVIODE.

[0167] In an example of a PO configuration for multiplexing pattern 1 described above

(using TDM, FDM, or hybrid TDM and FDM), the equation for RMSI CORESET may be used with an offset configured for each search space. For example, the slot number for a PO n_paging may be calculated using the following equation:

Equation (10)

In the case of a different number of actually transmitted SSBs, the logical index of the SSB may be associated with the slot for the paging sweep.

[0168] Moreover, the offset o_{p s} = K^^a _0t ^gL^_fset, where o_{p s} may be defined as a PDCCH monitoring offset, and which may be configured by parameter monitoringSlotPeriodicityAndOffset for the search space for paging. The slot in which paging occurs K^ ^ma= function(POJd, nTDMp, nFDMp), as described above. In o_{p s}, s may be the search space set index used for paging, and p = 0, which is the index for RMSI CORESET. If the time offset is in terms of mini-slots, the computation of ripaging may be similar.

[0169] In another example of a PO configuration for multiplexing pattern 1 , simple FDM may be employed for the entire beam sweep. For example, multiple FDM POs may be defined for the entire beam-sweep. In this case, paging beam sweep for all POs may be followed by the SS/PBCH block sweep. Each SS/PBCH block may be associated with a slot (or mini-slot) of the paging beam sweep. In the case of a different number of actually transmitted SSBs, a logical index of the SSB may be associated with the slot for the paging sweep. Multiple POs may be based on the WTRUJD and may be FDM in a different BWP, different CORESET, and/or different search spaces. The frequency of monitoring the PO by the WTRU may depend on the DRX and the SFN to be monitored by the WTRU for paging may be computed by the WTRU. Based on SSBI of the best SS/PBCH Block, the WTRU may compute the slot (or mini-slot) offset from the SS/PBCH block or other another known reference point in time, such as the 5 ms or half-frame boundary (or a multiple of 5 ms, which may be configured, for example, via RMSI PDCCFI). The slot offset may depend on SCS and may decrease if SCS increases. A gNB may configure or the WTRU may compute the BWP, CORESET and/or search space based on the WTRUJD.

[0170] In any of the examples of PO configuration for multiplexing pattern 1 described above (TDM, FDM, hybrid TDM and FDM, simple FDM across beam sweep), a collision and/or overlap may occur between the location for paging and the location of SS/PBCH block. In an example scenario, a gNB may transmit paging in a slot after the scheduled slot, when there is an overlap between the slot and the scheduled slot. This slot offset may be predefined, configured by the gNB, based on a rule, and/or computed by the WTRU. In another example scenario, the gNB may be able to configure CORESET so that it is in a different PRB than the SS/PBCH blocks. The PRB offset may be pre-determined, configured by the gNB, based on a rule, and/or computed by the WTRU. In another example scenario, the WTRU may assume that no SS/PBCH block is transmitted in resource elements (REs) used for monitoring the paging CORESET.

[0171] In an example of a multiplexing pattern (“multiplexing pattern 2/3”), the PPO configuration may be such that the paging CORESET may be FDM with SSB. In an example, the multiplexing pattern 2/3 may be used in frequencies great than 6GHz. The formula based methods to compute the BWP and/or CORESET and/or search space using WTRUJD, nFDMp, N, Ns, as described above, may also be used for multiplexing pattern 2/3, in which RMSI and SSB are FDM.

[0172] A BWP to be monitored by the WTRU and a search space to be monitored by the

WTRU may be a function of a PO index and/or total number of FDM POs in each of the dimension mentioned above (e.g., BWP, CORESET, search space). The CORESET associated with each search space may be included in the search space configuration and hence may not be explicitly mentioned.

[0173] In this example, the ID of the BWP may be calculated as BWPJd = f (POJd, nFDMp), and the ID of the search space may be calculated as SearchSpaceJd = f (POJd, nFDMp), where POJd may be an index of the PO. The number of FDM POs may be calculated as nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. If the number of FDM POs in a BWP is nFDMp_bwp = 1 , then that may imply that the POs are not multiplexed over the BWP, or same the POs are transmitted on different configured BWPs. If the number of FDM POs in a CORESET is nFDMp_coreset = 1 , then that may imply that the POs are not multiplexed over CORESETs. An index of the PO (POJd) may be computed using WTRUJD and a modulo function, for example POJd = floor(WTRUJD/N) mod Ns. The function f() in this case may be a round robin distribution function or a complex hashing function, and/or may be based on SFN_paging.

[0174] FIG. 18 is an example multiplexing pattern 3 for a PO configuration 1800 where the paging CORESET is FDM with an SS/PBCH block. The slot 1813 with SS/PBCH includes CORESETs for beams associated with SSB1 1804 and 1805. The CORESETs 1851 and 1852 may each include 4 paging search spaces 1821 -1824 (in POs 1841-1844). The paging messages 1831 - 1834 indicated by the paging DCI in the CORESETs 1851 and 1852 may be FDM with the SS/PBCH blocks (carrying SSB with SSB1 1804 and 1805).

[0175] FIG. 19 is an example multiplexing pattern 3 for a PO configuration 1900 where the paging CORESET is FDM with an SS/PBCH block. The slot 1913 with SS/PBCH may include CORESETs 1951 and 1952 for beams associated with SSB1 1904 and 1905. The CORESETs 1951 and 1952 may each include 4 paging search spaces 1921 -1924. The paging messages 1931 -1934 indicated by the paging DCI may be in a different slot 1913+N. The slot offset N may be indicated in the paging DCI (which may be located in search spaces 1921 -1924). The examples in FIG. 18 and FIG. 19 show multiplexing pattern 3. Multiplexing pattern 2, where the CORESET may be present in OFDM symbols before the SS/PBCH and/or the paging message may be present in PDSCFI FDM with SS/PBCH, may be similar to multiplexing pattern 3.

[0176] An example procedure performed by a WTRU for determining the configuration of

POs for multiplexing pattern 2/3 is described herein. According to the example procedure, a WTRU may synchronize with PSS/SSS and may receive a MIB from the PBCH. The WTRU may find the CORESET for RMSI from MIB, and may perform blind decoding for TypeO-PDCCFI. The WTRU may receive SIB1 from the PDSCFI as indicated by the TypeO-PDCCFI. The WTRU may find paging configurations including a DRX cycle, a paging-searchSpace and nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. The WTRU may compute SFN_pagj_ng using the DRX cycle, WTRUJD and/or the number of FDM POs. The WTRU may compute the POJd based on DRX cycle, WTRUJD and/or the number of FDM POs. Using a POJd and/or nFDMp, the WTRU may compute BWPJd and/or SearchSpaceJd. The CORESETJd may be associated with the SearchSpaceJd. Flence, using a different CORESET may be reflected in a different SearchSpaceJd.

[0177] The WTRU may use RBO of the common search space (same SearchSpaceJd with different RB offset for each of the groups). The WTRU may find the slot(s), non-slot(s) or mini-slots in which it is supposed to monitor the SearchSpaceJd and BWPJd (e.g., for all the beams). SS/PBCH Block and associated paging search space may be in the same slot and may be quasi-colocated. If the actually transmitted SSB are different than the defined SSB, the paging search space may be FDM with the actually transmitted SSBs. If there are not further actions for the WTRU, the WTRU may enter lDLEJVIODE.

[0178] The WTRU may wake up in slot, non-slot (or mini-slot) according to a computed

SFN and associated with a strongest last registered beam. If the WTRU is configured for sweeping beams, the WTRU may wake up in a first beam and sweep all the beams in slots associated with the PO for the WTRU. Using the search space definition for paging, the WTRU may find the paging CORESET in the precomputed BWPJd. The WTRU may use the search spaces table to blind decode the Type2-PDCCFI using P-RNTI. If multiple RNTI are assigned from a group of paging RNTI (PG-RNTI), the WTRU may use the RNTI used for its own group. The RNTI may be derived using the WTRUJD or assigned to the WTRU using WTRU-specific (e.g., RRC) signalling. If the WTRU finds Type2-PDCCFI, the WTRU receives the PDSCFI indicated by the PDCCFI to determine if the WTRU was paged. If the WTRU was paged, the WTRU may establish a connection with the gNB. If the WTRU was not paged, the WTRU may revert to IDLEJVIODE.

[0179] In an example, paging DCI may be used without paging messages. For example, a short paging message may be compressed into the paging DCI. Examples of short paging messages may include, but are not limited to include, any of the following: a paging message for a single WTRU; a system information update or modification; and/or emergency information or indications for public safety (e.g., public warning system (PWS), commercial mobile alert system (CMAS), earthquake and tsunami warning system (ETWS)). A DCI format may be defined for paging DCI based paging without paging PDSCFI (i.e., without separate paging messages). The DCI format may have a longer format to accommodate a paging message. The DCI format may include, but is not limited to include, any of the following information: a control information field; and/or a message field. The control information field may include, but is not limited to include, any of the following information: a resource allocation for the paging message; and/or a flag to indicate paging message or system information. The flag may be a field of X bits identifying the nature of short message (e.g., X may be a small number such as 2 or 3). The flag may be a bitmap of Y number of bits (e.g., Y may be 2^X such as 4 or 8 bits). The message field may include a paging message. If the control information field indicates that it is paging message for a single WTRU, then the message field may include the WTRUJD (e.g., IMSI, or a compressed form of WTRUJD) that is being paged. The message field may include system information (SI) and/or a change notification. The SI may include emergency system information or short system information message. AN SI change notification may override the paging message. The DCI may be coded with a Reed Muller (RM) code or Polar code. The DCI may be coded with two different coding schemes depending on the payload. For example, a system message may be coded with RM codes. Single user paging may be coded with polar codes with predefined code-rate or RM codes.

[0180] SSBs and paging DCI/paging messages may be associated. NR may have long

DRX cycles. A quick approach to search for the best gNB-TX/WTRU-RX beam-pair (e.g., with the highest SNR at the receiver) may use synchronization signals (e.g., PSS, SSS) in the SSB. If a gNB ensures that the antenna ports used to transmit paging (paging DCI and/or paging message) and synchronization signals are the same (e.g., are quasi-co-located), the WTRU may use the same TX/RX beam-pair to receive paging DCI as for receiving SSB. The use of the TX/RX beam-pair may be presumed or indicated implicitly or explicitly (e.g., OSI or RMSI). Predefined time-frequency association rule(s) between SSB and paging facilitate may the WTRU to quickly check the location for paging DCI/paging message. In the following description QCL with paging message may imply the DMRS of NR-PDSCH for the paging message is quasi-co-located with the paging DCI and or that the DMRS of NR-PDCCH is transmitted in the CORESET for the paging DCI. In some cases, the QCL assumption may not be valid or accurate.

[0181] Examples methods may be used for the association of SSBs and paging

DCI/messages. Paging DCI and/or paging message may be quasi-co-located with SSB. Example modes may include default mode (QCL mode) and non-default mode (Non-QCL mode). A flag (e.g., in RMSI or OSI) may be used to indicate which mode is being use, default mode or non-default mode, and/or an implicit rule regarding mode may be known at the WTRU.

[0182] In a default mode (QCL mode), a WTRU may assume the paging DCI and/or paging message is quasi-co-located with the detected SSB based on the association rule for the SSB and paging DCI/message. In a non-default mode (Non-QCL mode), a WTRU may receive an indication if the paging DCI and/or paging message is not quasi-co-located with the detected SSB. If SSB and paging DCI and/or message are not close in time, then QCL may not be assumed. For example, the gNB may use different beams or the same beam with different beam widths between SSB and paging DCI/message. [0183] A time threshold may be used for the association of SSBs and paging

DCI/message. In an example, let T be the time between the detected SSB and PO for a given WTRU. If T is less than the time threshold, then QCL between the SSB and paging DCI/message may be assumed. Otherwise, QCL may not be assumed. A time threshold may be used in combination with QCL flag. For example, If T < time threshold, QCL may be assumed, otherwise if the flag is set to QCL (e.g., a bit set to‘1’), then QCL may be assumed, otherwise QCL may not be assumed. A reference signal received power (RSRP) based threshold may be used, and the threshold may be absolute or relative. For example, an absolute threshold may be set to a predefined fixed number. A relative threshold (e.g., with respect to a previously selected SSB) may be dependent on any one or more of the following example conditions: WTRU mobility; Doppler; orientation; and/or relative RSRP. A function may be used to compute the threshold.

[0184] A QCL assumption may be applied to a subset of the paging DCI/message, and a fixed method or indication method for the subset may be used. In a fixed method, QCL may be applied to a fixed subset of paging DCI/messages. In a dynamic/semi-static method, QCL may be applied to a subset of paging DCI/messages that may be indicated (e.g., by the gNB). Within the subset, the WTRU may assume paging DCI and/or paging message is quasi-co-located with the detected SSB based on the association rule of an SSB and a paging DCI/message.

[0185] A paging DCI and paging message may be spatially QCL with SSB (e.g., for an analogue beam sweeping of narrow beams). In other words, the PDCCH and the DMRS for PDCCH containing the paging DCI may be spatially quasi-co-located with the SSB (e.g., QCL type A + D as defined in the standards, such that the QCL type may depend on Doppler shift, Doppler spread, average delay, delay spread or other parameters). In the same way, the DMRS for PDSCH containing the paging message may be spatially quasi-co-located with SSB (e.g., QCL type A+D). In another example, the paging channel may be non-spatially QCL with SSB (e.g., for omnidirectional or wide beam transmission). In this case, paging DCI and paging message may be spatially QCL with SSB with respect to average delay, Doppler shift, delay spread and/or Doppler spread estimation (e.g., QCL Type A).

[0186] Association rules may be used for associate of SSBs and paging DCI/messages.

There may be associations between SSBs and subsets of paging DCI/messages. A WTRU may use any one or more of the following example for CL associations: QCL association with SS/PBCH block; one-to-one association between one SS/PBCH block and one paging DCI/message; one-to- many association between one SS/PBCH block and multiple paging DCI/messages (e.g., a subset of paging messages or all paging messages); and/or many-to-one association between multiple SS/PBCH blocks and one paging DCI/messages (e.g., subset of SSB). A QCL association with RMSI may be defined. A RMSI block index may be defined similar to the SS block index. The RMSI block index (RMSI ID) may be included in RMSI and may be implicit or explicit. The RMSI block index (RMSI ID) may be assumed to be same as the SSBI in the case that RMSI may be associated with the SS block. A one-to-one association may exist between one RMSI block and a paging DCI/message. A one-to-many association may exist between one RMSI block and multiple Paging DCI/Messages (subset of paging messages). A many-to-one association may exist between multiple RMSI blocks and one paging DCI/message (subset of SSB).

[0187] A QCL association with OSI may be defined. An OSI block index may be defined similar to the SS block index. The OSI block index (OSI ID) may be included in OSI and may be implicit or explicit. The OSI block index (OSI ID) may be assumed to be the same as SSBI in the case that the OSI may be associated with SS Block. A one-to-one association may exist between one OSI block and one paging DCI/message. A one-to-many association may exist between one OSI block and multiple paging DCI/messages (e.g., a subset or all of paging messages). A many- to-one association between multiple OSI blocks and one paging DCI/messages (e.g., subset or all of SSBs). A QCL association may be across a BWP for a wideband component carrier (CC). A many- to-one association may involve a different BWP SSB associated with the paging DCI/message. With a one-to-many association, one BWP SSB may be associated with a different paging DCI/message. With one-to-one association, one BWP SSB may be associated with one paging DCI/message. QCL and WTRU behavior for the paging message association may be based on any one or more of the following example criteria: QCL association with paging DCI; one-to-one association between paging DCI and paging messages; QCL association with SS/PBCH block; QCL association with RMSI; and/or QCL association with OSI.

[0188] A WTRU may assume by default QCL based on SS/PBCH block, RMSI and/or OSI.

A WTRU may use a different QCL or override the default QCL based on an explicit method or an implicit method. According to an explicit method, an association may be configured by the network. A WTRU may be provided an indication (e.g., from the gNB) of which association to follow: an SS/PBCH, RMSI or OSI association. A bitmap may be used to indicate the association of paging DCI/message with any of SS/PBCH, RMSI or OSI. The bitmap may be included in the RMSI or OSI. The bitmap may be transmitted in WTRU-specific (e.g., RRC) signaling. According to an implicit method, an association may be assumed based on the shortest time span between the WTRU’s computed PPO for the WTRU and the detected or decoded SS/PBCH block, RMSI or OSI. P is the number of a PO in the DRX cycle, the PO may be associated (by the SSB to paging DCI/messages resource association rule) with the actually transmitted SSBs in the SS burst set period. P may be greater than, equal to or smaller than the number of actually transmitted SSB in the SS burst set. [0189] Paging deliver may be slot and/or non-slot based. Combinations of the slot and non-slot configurations for PDCCH and PDSCH may result in any one or more of the following options. For example, slot-based paging may include slot-based paging DCI followed by a slot- based paging message. In this case, the beam-sweeping may be slot-based. The paging DCI and paging message may be located in the same slot for each beam. The paging DCI and paging message may be multiplexed with other symbols including, but not limited to, data, control, SSB, RMSI, and/or OSI, which may be beam swept. Cross slot scheduling may be used. In the case of cross slot scheduling, the paging DCI may point to a PRB for the paging message in a different slot than the slot for the paging DCI. The offset between slots may be known or indicated (e.g., by the gNB). Each slot may sweep beam(s) in different directions or a beam may be repeated (e.g., in different slots if the paging DCI and paging message are in different slots).

[0190] Non-slot based paging may include non-slot based paging DCI followed by a nonslot based paging message. Using non-slot based paging may reduce the sweeping overhead caused by slots. In this configuration, the beam-sweeping may be done on non-slot basis. The non-slot symbols may contain the paging CORESET and/or the paging message. The non-slot symbols may be multiplexed with other symbols, including but not limited to data and/or control information, which may be scheduled and beam swept. In an example, beam sweeping for nonslots for paging DCI may be followed by beam sweeping for non-slots for the paging message. In a different PO, the payload for messages (e.g., paging, control data) may be different. In a different PO, the number of OFDM symbols used for the paging message may be different. To facilitate nonslot based paging, a slot format indicator (SFI) may be used. In an example, cross slot scheduling is performed.

[0191] In an example of a hybrid paging approach (“hybrid paging I”), a non-slot based paging DCI may be followed by a slot-based paging message. In this configuration, the paging DCI sweep may be performed quickly using the non-slot format. The DCI sweep may be followed by beam sweep based on a slot that carries the paging message. The paging message may be multiplexed with other information (e.g., data, control, SSB, RMSI, and/or OSI), which may be beam swept. In another example of a hybrid paging approach (“hybrid paging II”), a slot-based paging DCI may be followed by non-slot based paging message. In this configuration, the paging DCI sweep may be multiplexed with other information (e.g., data, control, SSB, RMSI, and/or OSI), which are beam swept. The DCI sweep may be followed by quick non-slot based beam-sweep carrying the paging message. According to this hybrid paging approach, a paging DCI may be close to an SSB or any other beam-swept symbol and therefore may be quasi-co-located with the SSB or other beam-swept symbol. [0192] In example approaches described above, a WTRU may be configured for paging with same slot scheduling or cross slot scheduling. The WTRU may receive an indication or follow predefined rules to adapt dynamic changes based on slot or non-slot scheduling and/or the transmission format. The dynamic changes may include, but are not limited to include, changing the monitored starting OFDM symbol for paging DCI, determining the number of OFDM symbols distance between the paging DCI and the paging message, and/or determining the number of OFDM symbols for paging message.

[0193] Paging delivery may be non-slot based. For example, PDSCFI may be non-slot based. A K OFDM symbol duration for Paging PDSCFI may be used (e.g., K=1 , 2, 4 or 7). Different options for indicating format for non-slot based PDSCFI may be used. For example, an explicit indication for non-slot based format may be used. For an explicit indication, PO sizes may vary, based on the use of different non-slot sizes, which in turn may depend on the number of users (WTRUs) paged together in the PO. One PO with beam sweep (e.g., with 2, 4, 7 symbols) may be used for a different number of users paged simultaneously. A number of symbols may be indicated in the paging DCI. Beam sweeping for paging DCI may be performed before the sweep of the paging message. Beam sweeping may occupy a slot or multiple slots depending on the number of beams. WTRUs may be configured to monitor the slots occupying the paging DCI for each WTRU’s own PO (and beam QCL with SSB). FIG. 20 is a signalling diagram of an example PO configuration 2000 including POs 2001 and 2002. In FIG. 20, PO 2002 includes paging message for a larger number of users (WTRUs) as compared to PO 2001 and hence includes more OFDM symbols for paging message. In FIG. 20, he paging DCI are transmitted in four beams and the paging messages (PMs) are transmitted in four beams, such that the paging DCI and PMs are in separate beam sweeps. Each of the POs 2001 and 2002 is used to page four groups (of WTRUs).

[0194] DCI may be part of non-slot paging message. FIG. 21 is a signalling diagram of an example PO configuration 2100 including POs 2101 and 2102. The example in FIG. 21 shows varying size POs (PO 2102 has a larger bandwidth than PO 2101 ) with self-contained paging DCI (p-DCI) in non-slots. In FIG. 21 , the paging DCI are transmitted in four beams and the paging messages (PMs) are transmitted in the same beam sweep.

[0195] A paging message (PM) may be rate matched around the paging DCI. The format for paging may be indicated in the SFI. Information indicated in a paging DCI may include any one or more of the following indications: an indication of slot or non-slot based paging PDSCFI; an indication of non-slot size if non-slot based paging is indicated; an indication of same-slot or crossslot scheduling for paging message(s); an indication of time offset if cross-slot scheduling is indicated for a paging message (e.g., in terms of OFDM symbols, mini-slots, or slots); and/or a flag in a paging scheduling DCI to indicate if there is a corresponding paging PDSCH.

[0196] In another example, PDCCH may be non-slot based. Non-slot based paging delivery may enable faster and/or more flexible paging message delivery, for example in beam sweeping mode. It may not be meaningful if non-slot based transmission of paging PDSCH is supported but non-slot based transmission of paging PDCCH is not supported. A WTRU may monitor non-slot PDCCH for POs that may be configured by the paging CORESET (e.g., non-slot based PDCCH transmissions in the case where PDCCH monitoring POs may be located in the middle of a slot). In an example, non-slot based PDSCH transmission may have 2, 4, or 7 OFDM symbol duration. In this case, from the PDCCH perspective, non-slot based transmission/scheduling may be related to CORESET monitoring periodicity less than one slot. Nonslot based PDCCH transmission may support 1 , 2, 4, 7 OFDM symbol durations. In order to reduce beam sweeping latency, a smaller number of OFDM symbols per non-slot may be supported (e.g., for PDCCH-based paging without PDSCH, 1 symbol may be supported). PDCCH may be transmitted for paging DCI and PDSCH may be transmitted for paging messages in the same OFDM symbols, so that paging DCI and paging messages may be transmitted in the same beam in the sweep.

[0197] In an example, for cross slot scheduling the sweep may be performed for PDCCH for paging DCI before the sweep for the paging message. In order to enable efficient sweeping mechanisms for Paging DCI/message delivery, non-slot based scheduling may also be supported for paging PDCCH. The number of OFDM symbol may be reduced to 1 for the PDCCH for paging DCI. In an example, [X, Y, Z] OFDM-symbol duration (referring to sizes of mini-slots) for the paging CORESET may be fixed for non-slot based PDCCH for PDSCH of symbols [2, 4, 7], Different values for [X, Y, Z] may be supported (e.g., [X, Y, Z] = [1 , 1 , 2] or [1 , 2, 2]).

[0198] Paging delivery may be based on cross slot scheduling. A WTRU may decode a paging message after detecting a paging DCI using any one or more of the following example rules. According to an example rule, a WTRU may decode a paging message after any one or more of the following elements are received: P OFDM symbols; P mini-slots (in non-slot based system); P slots; P subframes; and/or P frames. For example, a WTRU may decode a paging message after P1 nonslots and P2 OFDM symbols. In an example scenario, P may be fixed and known to WTRU. For example, P may be associated with number of beams, and/or slot/non-slot format for PDCCH and PDSCH. In another example, a predefined table may be used to find N. In another example scenario, P may be indicated to the WTRU. This may be performed explicitly by the paging scheduling DCI. For example, the paging scheduling DCI may carry the offset N, which may allow greater flexibility with slight overhead. The paging scheduling DCI may include the unit of P (e.g., OFDM symbol, mini-slot, slot, subframe, frame or combination thereof). P may be implicitly computed by the WTRU using any one or more of the following example parameters: a number of beams to be swept; a slot or non-slot based PDCCH; a slot or non-slot based PDSCH; and/or a fixed or indicated offset between the end of PDCCH sweep for paging DCI and a PDSCH sweep for a paging message.

[0199] Procedures may make use of the PO duration or interval. A PO may consist of P

OFDM symbols, slots, non-slots, subframes or frames (or a combination thereof). The duration or interval of the PO may be used to enable the following for both TX and RX beams: TX beam sweeping; TX beam repetition; RX beam sweeping; and/or RX beam repetition.

[0200] The number of elements in a PO, N, may be determined at WTRU using any one or more of the following example methods: based on the actually transmitted SSBs (e.g., which may be indicated in RMSI or RRC); based on a maximum number of SSBs which may be determined by frequency range; based on an indication or configuration; based on sweeping configuration information (e.g., M1 TX beam sweep, M2 RX beam sweep); and/or based on repetition configuration information (e.g., K1 TX beam repetition, K2 RX beam repetition). An indicator for the number of elements in a PO P may indicate any one or more of the following example information: beam sweeping operation mode; a beam repetition operation mode; or a hybrid beam sweep/repetition operation mode.

[0201] Methods may be used for advanced paging delivery. A paging message may be scheduled by the paging DCI carried in NR-PDCCH and may be transmitted in the associated NR- PDSCH. A paging delivery system may be designed for the case where the paging DCI and paging message may be swept in all directions for all WTRU. It may be desirable to wake up WTRUs properly and reduce time for which WTRUs monitor the paging group indicator(s), which may reduce WTRU battery power consumption. For finer WTRU grouping granularity, a large number of beams to sweep for paging may be used.

[0202] Advanced paging delivery may be implemented with a second level of grouping. In this case, a paging message may be followed by a paging delivery (e.g., base paging). In this case, WTRUs may be grouped without feedback or WTRU beam reporting. The group of WTRUs may be paged at the same time, for example using paging group indicator. A bitmap of groups may be sent in the paging group indicator DCI masked by P-RNTI. The paging group indicator may instruct WTRUs in the indicated WTRU groups to perform any one or more of the following example functions: receive paging scheduling DCI (according to base paging); and/or transmit a feedback message such as a dedicated PRACH preamble (advanced paging with feedback). This advanced paging approach may reduce the wake up process for a WTRU and save power for WTRUs that are not paged as part of the group.

[0203] Advanced paging delivery may include feedback. In this method, feedback from the

WTRU may be added to method for advanced paging delivery described above. For example, feedback may include a paging DCI and/or paging group indicator. A paging group indicator may be sent or part of the paging DCI masked by P-RNTI or by the paging message. The paging DCI and/or paging group indicator may be sent as a bitmap of groups. In an example, a paging indication may trigger WTRU beam reporting (if supported). For example, a paging indication may be in the paging DCI or in a non-scheduled physical channel. In another example, a paging group indicator may indicate whether or not WTRUs need to transmit the dedicated PRACFI preamble. WTRUS part of the group may send RACFI as a feedback, which may be received by the gNB in a specific beam(s) indicating the WTRU’s presence in the direction of that beam(s). The paging DCI followed by the paging message may be transmitted on the DL directions, which may correspond to the received dedicated PRACFI preambles. DL beam reporting by transmitting a dedicated PRACFI may reuse mechanisms for dedicated beam-recovery request and/or on-demand OSI request. Other enhancements may include: a dedicated RACFI resources for paging response. Different RACFI preambles may be defined for each group (K groups). Different cover codes may be defined for the preambles. Cover codes may include, but is not limited to include, M sequence, orthogonal cover codes (OCC), and/or sinusoidal waveform. The RACFI preambles may be assigned using WTRU- specific (e.g., RRC) messaging. A gNB may change grouping based on the feedback for advanced paging. This grouping modification may be signalled by WTRU-specific (e.g., RRC) signalling.

[0204] A BWP may be used for feedback in advanced paging. In an example, UL BWP k1 may be linked with DL BWP k2. If the WTRU receives the paging indication on DL BWP k2, then by default the WTRU may use UL BWP k1 to transmit the feedback. k1 may be same as k2 or they may be different. Other configurations for BWP linkage may be used for paging.

[0205] Different configurations may be used for BWP assignments and/or BWP linking. In a same configuration, k1 = k2. The WTRU may use the same BWP for uplink as the DL-BWP in which the WTRU received its paging indication. In a one-to-one mapping configuration, one DL BWP may be linked to exactly one UL BWP. The WTRU may be configured with and may receive a paging indication on a DL BWP k, and may be configured with UL BWP k1 = f (k2), where f(k) is unique function. This function f() may be known to the WTRU. Hence, the WTRU may use the UL- BWP for feedback, which may be linked to the DL BWP where the WTRU received paging Indication. In a one-to-many mapping configuration, one DL BWP may be linked to multiple UL BWP; that is, two WTRUs may be configured such that DL BWP k2 may be configured with any UL BWP (e.g., for WTRU1 , k2= f1 (k1 ) and for WTRU2, k2 = f2(k1 )). For example, one DL BWP, where the paging indication is received by two different WTRUs, may map to two UL BWPs from a system perspective, where the WTRUs may provide feedback on the beam information. The function f() in this case may be a modulo based function, and/or may depend on WTRUJD and/or the paging group ID. A different format for the beam feedback for paging may be used (e.g., grant free uplink, grant based uplink, or PRACH).

[0206] Different uplink formats may be used for BWP based feedback for advanced paging. In an example, grant free uplink may be used for the feedback. If the WTRU uses grant free uplink, the WTRU may have preconfigured resources in a preconfigured BWP. In another example, grant based uplink may be used for the feedback. If grant based uplink for feedback is used, if the WTRU wants to dynamically switch BWP and schedule feedback in different BWP, then the gNB may use longer DCI format (similar to DCI format 0_1 defined in the standards, which includes a way to dynamically switch BWP) to schedule the uplink for the feedback. The gNB may reserve multiple orthogonal time/frequency/BWP resources and WTRUs may select resources from the set reserved by the gNB. This selection of resources by the WTRUs may be based on WTRUJD. To reduce overhead of DCI (or achieve a better code-rate), a BWP linkage may be used and/or a shorter DCI format (similar to DCI format 0_0 defined in the standards, without indication of BWP) to schedule the uplink for feedback. PRACH resources may be used for the feedback. If the WTRU uses PRACH configured resources for feedback in advanced paging, the BWP linkage may identify the UL-BWP to transmit the RACH resource dedicated for beam-feedback.

[0207] Examples of WTRU behavior for paging feedback for beam reporting are described herein. A WTRU may provide feedback for beam reporting. If BWP linking for UL and DL is used for paging, the WTRU behaviour may include any of the following example actions. The WTRU may precompute or check the configured BWP for the paging DCI. If the BWP is the same as a currently active BWP, then the WTRU may receive the paging DCI. Otherwise, the WTRU may switch to the DL BWP for the paging DCI. The WTRU may decode the paging DCI and check if the WTRU was part of the group that was paged. If the WTRU was part of the group that was paged (i.e., the WTRU was paged), advanced paging may be enabled and feedback for the beam may be used. In this case, the WTRU may find the linked UL BWP for feedback. If the linked UL BWP is the same configuration or one-to-one configuration, then the WTRU may identify the UL-BWP. If the linked UL BWP has a one-to-many mapping between one DL-BWP and multiple UL-BWP, the WTRU may determine the UL BWP using pre-defined algorithm. For example, the UL-BWP may be determined using a modulo function based on a WTRU-ID and/or paging Group-ID. If the linked UL BWP is different from the current BWP, the WTRU may switch the BWP before the slot of scheduled resources. The WTRU may accordingly transmit beam feedback.

[0208] Base paging and advanced paging with feedback may be combined together and a gNB may be able to switch between base paging and advanced paging with feedback, and may configure the two options based on scenario and/or deployment. For combined base and advanced paging, base or advanced paging may be indicated, which may enable or disable the feedback requirement based a trigger. An indication of base or advanced paging may be included for example in a paging DCI, RMSI and/or OSI.

[0209] A paging group for the case of N groups and K subgroups may be determined using a modulo function. Grouping users (WTRUs) based on location or feedback may be used. However, second level grouping based on for example IMSI may not add many changes. There may be a second grouping based on another constant K (this also may use similar modulo operation with IMSI). K may be the total number of groups supported and that may be paged in a same PO. Different methods to indicate groups may be used, (e.g., Bitmap, Group-IDs Hybrid). User grouping may reduce WTRU complexity and ambiguity (e.g., if a compressed WTRUJD is used for the paging message). Different group’s paging messages may be FDM or TDM in a same or different slot or mini-slot.

[0210] A paging group indicator may be used. A finer granularity grouping may be needed to support advance methods for paging. An indicator may be used to indicate the finger granularity grouping. The grouping decision may be made at higher layers (e.g., MAC, RLC, RRC), based on location or other parameters. Multiple groups may be paged in the same PO. Hence, the paging DCI may include an indication of which groups are being paged, and for example may indicate that one group is being paged. For example, a paging group indicator may take the form of a bitmap being sent in a paging DCI (CRC masked by P-RNTI), a paging message or in any channel or signal. For example, a bitmap (K-bits bitmap) of groups may be used in a paging DCI as a paging group indicator. If any WTRU from a group is paged, the bit corresponding to that group may be set (e.g., to ) in the bitmap, and otherwise the corresponding bit may be reset (e.g., to O’). In another example, group-IDs may be used as a paging group indicator. A different group ID may be aggregated and transmitted in a paging DCI to indicate WTRUs from different groups are being paged. Each group may be represented by a group ID (e.g., ranging from 0 to K-1). The paging DCI may include a number of groups being paged and/or their group IDs.

[0211] In an example, a hybrid design for paging group indicator may be used. In a hybrid method a bitmap of group and a bitmap of WTRUs group may be sent in a paging DCI. This method may offer a finer resolution granularity of WTRUs being paged. WTRUs may be provided their own group and their position in the bitmap, which may use additional WTRU-specific signalling. Multiple P-RNTI or PG-RNTI may be used for the paging group indicator. A different group may have a different P-RNTI instead of single P-RNTI value LTE (PG-RNTI). The PG-RNTI may be a sequential or non-sequential range of RNTIs reserved for different groups to be paged. In this case, only one group may be paged with one DCI. The CRC of the paging DCI may be masked with the PG-RNTI of the group that is being paged.

[0212] A group common PDCCH specific for paging (P-GC-PDCCH) may be used for the paging group indicator. Similar to GC-PDCCH, which is used to indicate SFI, a P-GC-PDCCH may indicate paging specific slot format. The P-GC-PDCCH may be located in a common search-space where any or all the WTRUs may monitor it. The P-GC-PDCCH may be swept across all beams. The P-GC-PDCCH may be transmitted at the beginning of slots for each PO indicating symbols for paging message location in the slot or non-slot transmission. The P-GC-PDCCH may have paging DCI with a paging group indication. The P-GC-PDCCH may include a bitmap with symbols in following slots to be observed for paging. The P-GC-PDCCH may be coded and transmitted in control channel similar to GC-PDCCH. A CRC may be masked with a specific number (e.g., P- RNTI) or a range (e.g., PG-RNTI).

[0213] A paging specific SFI may be used for the paging group indicator. Entries to SFI table for paging may be added to the GC-PDCCH indicating paging slot format. These entries may serve as paging scheduling information. WTRU may use the index decoded from GC-PDCCH to identify the paging message location(s). The entries to the SFI table may be used to indicate nonslot format for multiple slots used for paging. Any of the above methods may be used to identify the group for which the paging slot format is being used. GC-PDCCH may be used to dynamically modify the number of symbols for non-slot used for paging DCI/message.

[0214] Although the solutions described herein consider LTE, LTE-A, New Radio (NR) or

5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0215] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer- readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks

(DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, WTRU, base station, RNC, or any host computer.

Claims

CLAIMS What is claimed is:

1. A wireless transmit/receive unit (WTRU) configured to support multi-beam communications and perform paging monitoring, the WTRU comprising:

a receiver configured to receive a configuration for enhanced paging;

a processor configured to:

determine a first subcarrier spacing (SCS) for a synchronization signal block (SSB) and a second SCS for a paging reception;

determine a paging multiplexing type (PMT) based on the first SCS and second SCS, wherein the PMT is determined to be a first type on a condition that the first SCS and second SCS are different and a second type on a condition that first SCS and second SCS are the same;

determine a beam, time and frequency relationship among a paging control resource set (CORESET), a paging message, and the SSB based on the determined PMT; and

the receiver configured to monitor a paging occasion (PO) in one or more beams of the PO for the paging message based on the determined beam, time and frequency relationship.

2. The WTRU of claim 1 , wherein on a condition that the PMT is determined to be the first type, the beam, time and frequency relationship includes the paging CORESET being time division multiplexed (TDM) with the paging message, the paging message being time aligned in a same slot as the SSB, and the paging message being frequency division multiplexed (FDM) with the SSB.

3. The WTRU of claim 2, wherein the paging CORESET is TDM with the paging message using a repeated beam resulting in two transmissions per beam of the PO.

4. The WTRU of claim 1 , wherein on a condition that the PMT is determined to be the second type, the beam, time and frequency relationship includes the paging CORESET being time division multiplexed (TDM) with the paging message, the paging CORESET and the paging message being time aligned in a same slot as the SSB, and the paging CORESET and the paging message being frequency division multiplexed (FDM) with the SSB.

5. The WTRU of claim 4, wherein the paging CORESET is TDM with the paging message without using a repeated beam resulting in one transmission per beam of the PO.

6. The WTRU of claim 1 , wherein:

the receiver is further configured to monitor the PO for a paging downlink control information (DCI), wherein the paging DCI includes scheduling information for the paging message.

7. The WTRU of claim 1 , wherein:

the receiver is further configured to receive the paging CORESET from a gNB.

8. The WTRU of claim 1 , wherein:

the receiver is further configured to receive an indication from a gNB of a type of multiplexing used for paging being time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM and FDM.

9. The WTRU of claim 1 , wherein the PO includes at least one of: time slots, non-slots, subframes or orthogonal frequency division multiplexing (OFDM) symbols.

10. The WTRU of claim 1 configured to operate using discontinuous reception (DRX) in idle mode and wake up during the PO to perform the paging monitoring.

1 1. A method for paging monitoring, performed by wireless transmit/receive unit (WTRU) configured to support multi-beam communications, the method comprising:

receiving a configuration for enhanced paging;

determining a first subcarrier spacing (SOS) for a synchronization signal block (SSB) and a second SOS for a paging reception;

determining a paging multiplexing type (PMT) based on the first SCS and second SCS, wherein the PMT is determined to be a first type on a condition that the first SCS and second SCS are different and a second type on a condition that first SCS and second SCS are the same;

determining a beam, time and frequency relationship among a paging control resource set (CORESET), a paging message, and the SSB based on the determined PMT; and

monitoring a paging occasion (PO) in one or more beams of the PO for the paging message based on the determined beam, time and frequency relationship.

12. The method of claim 11 , wherein on a condition that the PMT is determined to be the first type, the beam, time and frequency relationship includes the paging CORESET being time division multiplexed (TDM) with the paging message, the paging message being time aligned in a same slot as the SSB, and the paging message being frequency division multiplexed (FDM) with the SSB.

13. The method of claim 12, wherein the paging CORESET is TDM with the paging message using a repeated beam resulting in two transmissions per beam of the PO.

14. The method of claim 11 , wherein on a condition that the PMT is determined to be the second type, the beam, time and frequency relationship includes the paging CORESET being time division multiplexed (TDM) with the paging message, the paging CORESET and the paging message being time aligned in a same slot as the SSB, and the paging CORESET and the paging message being frequency division multiplexed (FDM) with the SSB.

15. The method of claim 14, wherein the paging CORESET is TDM with the paging message without using a repeated beam resulting in one transmission per beam of the PO.

16. The method of claim 11 , further comprising:

monitoring the PO for a paging downlink control information (DCI), wherein the paging DCI includes scheduling information for the paging message.

17. The method of claim 11 , further comprising:

receiving the paging CORESET from a gNB.

18. The method of claim 1 1 , further comprising:

receiving an indication from a gNB of a type of multiplexing used for paging being time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM and FDM.

19. The method of claim 1 1 , wherein the PO includes at least one of: time slots, non-slots, subframes or orthogonal frequency division multiplexing (OFDM) symbols.

20. The method of claim 11 , further comprising:

using discontinuous reception (DRX) in idle mode and waking up during the PO to perform the paging monitoring.