TW201933817A - Apparatus and systems for paging and L1 mobility in NR - Google Patents

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

Paging and L1 mobile devices and systems in NR

Cross-reference to related applications

The present application claims the benefit of U.S. Provisional Application No. 62/586, 513, filed on Nov. 15, the,,,,,,,,,, It was introduced as a reference.

The recent 3rd Generation Partnership Project (3GPP) standards discussion defines several deployment scenarios, such as indoor hotspots, dense cities, rural, urban macro cells, and high speed. Based on the general requirements of the Next Generation Mobile Network (NGMN), 3GPP, and the International Telecommunications Union Radiocommunication Sector (ITU-R), the rough classification of emerging fifth-generation (5G) system use cases can be divided into Enhanced Mobile Broadband (eMBB) Large-scale machine type communication (mMTC) and ultra-reliable low-latency communication (URLLC). These use cases focus on meeting different performance requirements, such as higher data rates, higher spectral efficiency, lower power and higher energy efficiency, and/or lower latency and higher reliability. In addition, various deployment scenarios take into account the broad spectrum range from 700 MHz to 80 GHz.

In wireless communication, as the carrier frequency increases, severe path loss may become a critical constraint to ensure adequate coverage. Transmissions in millimeter wave (mmW) systems are also likely to suffer from non-line-of-sight losses such as diffraction loss, penetration loss, oxygen absorption loss, and/or blade loss. During initial access, the base station and the WTRU may need to overcome these high path losses and discover each other. Using tens or even hundreds of antenna elements to generate a beamformed signal is an effective way to compensate for severe path loss by providing significant beamforming gain. Beamforming techniques can include digital, analog, and hybrid beamforming.

Methods and systems for paging monitoring that can be performed by a wireless transmit/receive unit (WTRU) that supports multi-beam communications are disclosed herein. The 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 paging reception. The WTRU may determine a paging multiplex type (PMT) based on the first SCS and the second SCS such that the PMT is determined to be the first type under the condition that the first SCS is different from the second SCS, and the first SCS is the same as the second SCS Under the conditions, the PMT is determined to be the second type. The WTRU may determine beam, time, and frequency relationships between the paging control resource set (CORESET), the paging message, and/or the SSB based on the determined PMT. The WTRU may monitor the PO in one or more beams of a paging occasion (PO) based on the determined beam, time, and frequency relationship to discover a paging message.

FIG. 1A is a diagram showing an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content for a plurality of wireless users, such as voice, data, video, messaging, broadcast, and the like. The communication system 100 can enable multiple wireless users to access such content via sharing system resources including wireless bandwidth. For example, communication system 100 can use 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 extended OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC) Wait.

As shown in FIG. 1A, communication system 100 can include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104/113, CN 106/115, public switched telephone network (PSTN) 108, the Internet. Path 110 and other networks 112, however, it should be understood that the disclosed embodiments encompass 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. For example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as "station" and/or "STA", which may be configured to transmit and/or receive wireless signals, and may include a user Equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, mobile phone, personal digital assistant (PDA), smart phone, laptop, laptop, PC, wireless Sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head mounted displays (HMD), vehicles, drones, medical devices and applications (eg remote surgery), industrial devices And applications (such as robotics and/or other wireless devices operating in industrial and/or automated processing chain environments), consumer electronic devices, and devices operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as UEs.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a and/or the base stations 114b can be configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to cause them to access one or more communication networks (eg, Any type of device of CN 106/115, Internet 110, and/or other network 112). For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNodeB, a local Node B, a local eNodeB, a gNB, an NR Node B, a website controller, an access point (AP), and Wireless routers and more. While each of the base stations 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b can include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104/113, and the RAN 104/113 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, and more. Base station 114a and/or base station 114b can be configured to transmit and/or receive wireless signals on one or more carrier frequencies known as cells (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of authorized and unlicensed spectrum. Cells may provide wireless service coverage for a particular geographic area that is relatively fixed or that may change over time. Cells can be further divided into cell sectors. For example, a cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, that is, each transceiver corresponds to one sector of a cell. In an embodiment, base station 114a may use multiple input multiple output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and/or receive signals in a desired spatial direction.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via the null plane 116, where the null plane may be any suitable wireless communication link (e.g., radio frequency (RF), Microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The empty intermediaries 116 can be established using any suitable radio access technology (RAT).

More specifically, as noted above, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, to name a few. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104/113 may implement radio technologies, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), where the techniques may use Wideband CDMA (WCDMA) To establish an empty intermediary plane 115/116/117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and/or High Speed UL Packet Access (HSUPA).

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and/or Or an advanced LTE (LTE-A) and/or an advanced LTE Pro (LTE-A Pro) to establish an empty inter-plane 116.

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, where the radio technology may establish an empty intermediation plane 116 using a new radio (NR).

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a variety of radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together (e.g., using a dual connectivity (DC) principle). Thus, the null intermediaries used by the WTRUs 102a, 102b, 102c may be characterized via multiple types of radio access technologies and/or transmissions to/from multiple types of base stations (e.g., eNBs and gNBs).

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement, for example, IEEE 802.11 (ie, Wireless High Fidelity (WiFi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000. EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate (EDGE) for GSM Evolution And radio technology such as GSM EDGE (GERAN).

The base station 114b in FIG. 1A may be, for example, a wireless router, a local Node B, a local eNodeB or an access point, and may use any suitable RAT to facilitate wireless connectivity in a local area, such as a business Locations, homes, vehicles, campuses, industrial facilities, air corridors (eg for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In still another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular based RAT (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or Femtocell. As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Therefore, the base station 114b does not need to access the Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with a CN 106/115, which may be configured to provide voice, data, applications, and/or the Internet to one or more of the WTRUs 102a, 102b, 102c, 102d Any type of network for Voice over Voice (VoIP) services. The data can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. The CN 106/115 may provide call control, billing services, mobile location based services, prepaid calling, internet connectivity, video distribution, etc., and/or may perform high level security functions such as user authentication. Although not shown in FIG. 1A, it should be appreciated that the RAN 104/113 and/or CN 106/115 may communicate directly or indirectly with other RANs that use the same RAT or different RATs as the RAN 104/113. For example, in addition to being connected to the RAN 104/113 using NR radio technology, the CN 106/115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA or WiFi radio technology. .

The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include a circuit switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 may include global use of public communication protocols such as TCP in the Transmission Control Protocol (TCP)/Internet Protocol (IP) Internet Protocol suite, User Datagram Protocol (UDP), and/or IP. Sexually interconnected computer network device system. Network 112 may include a wired or wireless communication network that is owned and/or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as RAN 104/113.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple communications with different wireless networks over different wireless links) transceiver). For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that uses a cellular-based radio technology, and with a base station 114b that can use an IEEE 802 radio technology.

FIG. 1B is a system diagram showing an exemplary WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/trackpad 128, a non-removable memory 130, and a removable Memory 132, power source 134, global positioning system (GPS) chipset 136, and other peripheral devices 138. It should be appreciated that the WTRU 102 may also include any sub-combination of the aforementioned elements while remaining consistent with the embodiments.

The processor 118 can 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 associated with the DSP core, a controller, a microcontroller , dedicated integrated circuit (ASIC), field programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), state machine, and so on. The processor 118 can perform signal encoding, 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 118 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it should be understood that the processor 118 and the transceiver 120 can also be integrated together in an electronic component or wafer.

The transmit/receive element 122 can be configured to transmit signals to or from a base station (e.g., base station 114a) via the null plane 116. For example, in one embodiment, the transmit/receive element 122 can be an antenna configured to transmit and/or receive RF signals. For example, in another embodiment, the transmit/receive element 122 can be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals. In still another embodiment, the transmit/receive element 122 can be configured to transmit and receive RF as well as optical signals. It should be appreciated that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) that transmit and receive wireless signals via the null intermediate plane 116.

The transceiver 120 can be configured to modulate signals to be transmitted by the transmission/reception element 122 and to demodulate signals received by the transmission/reception element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, transceiver 120 may include multiple transceivers that enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

The processor 118 of the WTRU 102 may be coupled to a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may Receive user input from these components. The processor 118 can also output user profiles to the speaker/microphone 124, keypad 126, and/or display/trackpad 128. In addition, processor 118 can access signals from any suitable type of memory, such as non-removable memory 130 and/or removable memory 132, and store information to such memory. Non-removable memory 130 may include random access memory (RAM), read only memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 can include a Subscriber Identity Module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access signals from the memory that are not physically located in the WTRU 102 and store the data to the memory. For example, such memory may be located on a server or a home computer (not shown). .

The processor 118 can receive power from the power source 134 and can be configured to distribute and/or control power for other elements in the WTRU 102. Power source 134 may be any suitable device that powers WTRU 102. For example, the power source 134 may include one or more dry battery packs (such as nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-hydrogen (NiMH), lithium-ion (Li-ion), etc.), solar cells, and Fuel cells and more.

The processor 118 can also be coupled to a GPS chipset 136 that can be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. Additionally or alternatively to the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base station 114a, 114b) via the null plane 116 and/or receive from two or more nearby base stations. Signal timing to determine its position. It should be appreciated that the WTRU 102 may obtain location information using any suitable positioning method while remaining consistent with the embodiments.

The processor 118 can also be coupled to other peripheral devices 138, where the peripheral devices can include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, peripheral device 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photo and video), a universal serial bus (USB) port, a vibrating device, a television transceiver, a hands-free headset, a Bluetooth® mode. Group, FM radio unit, digital music player, media player, video game console module, internet browser, virtual reality and/or augmented reality (VR/AR) device, and activity tracker, etc. Wait. The peripheral device 138 can include one or more sensors, which can be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, proximity Sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors and/or Or humidity sensor.

The WTRU 102 may include a full-duplex radio for which some or all of the signals (e.g., specific sub-messages for UL (e.g., for transmission) and downlink (e.g., for reception) The reception or transmission of the box association may be parallel and/or simultaneous. Full-duplex radios may include reduced and/or substantially eliminated self-processing via hardware (eg, choke coils) or via signal processing by a processor (eg, a separate processor (not shown) or via processor 118) Interference interference management unit 139. In an embodiment, the WTRU 102 may include a half-duplex radio that transmits or receives some or all of the signals (e.g., associated with a particular subframe for UL (e.g., for transmission) or downlink (e.g., for reception). Device.

1C is a system diagram showing RAN 104 and CN 106, in accordance with an embodiment. As described above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c via the null plane 116 to use the E-UTRA radio technology. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include eNodeBs 160a, 160b, 160c, however it should be appreciated that the RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. Each of the eNodeBs 160a, 160b, 160c may include one or more transceivers that communicate with the WTRUs 102a, 102b, 102c via the null intermediaries 116. In one embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNodeB 160a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a.

Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, uplink (UL), and/or downlink (DL) User scheduling in ) and so on. As shown in FIG. 1C, the eNodeBs 160a, 160b, 160c can communicate with each other via the X2 interface.

The CN 106 shown in FIG. 1C 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 is described as being part of CN 106, it should be understood that any of these elements can be owned and/or operated by entities other than the CN operator.

The MME 162 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for verifying the users of the WTRUs 102a, 102b, 102c, performing bearer activation/deactivation, and selecting a particular service gateway during the initial connection of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide control plane functionality for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM or WCDMA.

SGW 164 may be connected to each of eNodeBs 160a, 160b, 160c in RAN 104 via an S1 interface. The SGW 164 can generally route and forward user data packets to the WTRUs 102a, 102b, 102c/route and forward user data packets from the WTRUs 102a, 102b, 102c. SGW 164 may perform other functions, such as anchoring the user plane during handover between eNBs, triggering paging when DL data is available to WTRUs 102a, 102b, 102c, and managing and storing the context of WTRUs 102a, 102b, 102c, etc. .

The SGW 164 can be coupled to the PGW 166, which can provide the WTRUs 102a, 102b, 102c with access to a packet switched network (e.g., the Internet 110) to facilitate the WTRUs 102a, 102b, 102c and IP enabled devices. Communication between.

The CN 106 can facilitate communication with other networks. For example, CN 106 may provide WTRUs 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communication devices. For example, CN 106 may include or communicate with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server), and the IP gateway may act as an interface between CN 106 and PSTN 108. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to network 112, which may include other wired or wireless networks that other service providers own and/or operate.

Although the WTRU is described as a wireless WTRU in Figures 1A through 1D, it is contemplated that in certain exemplary embodiments such a WTRU may (e.g., temporarily or permanently) use a wired connection to a communication network. Communication interface.

In a typical embodiment, the other network 112 can be a WLAN.

A WLAN employing an 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 can access or interface to a distributed system (DS) or another type of wired/wireless network that carries traffic and/or carries the BSS. Traffic originating outside the BSS and to the STA may arrive via the AP and be delivered to the STA. Traffic originating from the STA and destined to a destination outside the BSS can be sent to the AP to be delivered to the respective destination. Traffic between STAs within the BSS may be sent via 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. Traffic between STAs within a BSS can be considered and/or referred to as point-to-point traffic. The point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) with direct link setup (DLS). In some exemplary embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within the IBSS or using the IBSS may communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure operating mode or a similar mode of operation, the AP can transmit beacons on fixed channels (eg, primary channels). The main channel can have a fixed width (eg, a bandwidth of 20 MHz) or a dynamically set width via messaging. The primary channel may be the operational channel of the BSS and may be used by the STA to establish a connection with the AP. In some exemplary embodiments, carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented (eg, in an 802.11 system). For CSMA/CA, STAs including APs (eg, each STA) can sense the primary channel. If a particular STA senses/detects and/or determines that the primary channel is busy, then that particular STA may fall back. In a given BSS, one STA (eg, only one station) can transmit at any given time.

High throughput (HT) STAs can communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide main channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).

Very high throughput (VHT) STAs can support channels of 20 MHz, 40 MHz, 80 MHz and/or 160 MHz wide. A 40 MHz and/or 80 MHz channel can be formed by combining successive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two discrete 80 MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel encoding, the data can be passed through the segmentation parser, which splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed separately on each stream. This stream can be mapped on two 80 MHz channels and the data can be transmitted by a transmitting STA. At the receiver of a receiving STA, the above operations for the 80+80 configuration may be reversed and the combined material may be sent to the Media Access Control (MAC).

802.11af and 802.11ah support the next 1 GHz mode of operation. The channel operation bandwidth and carrier reduction are used in 802.11af and 802.11ah compared to the channel operation bandwidth and carrier used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidth in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. In accordance with an exemplary embodiment, 802.11ah can support meter type control/machine type communication (eg, MTC devices in a macro coverage area). The MTC may have certain capabilities, including, for example, support (e.g., support only) certain and/or limited bandwidth limited capabilities. The MTC device can include a battery and the battery life of the battery is above a threshold (eg, to maintain a very long battery life).

WLAN systems that support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and/or limited by STAs in all STAs operating in the BSS supporting the minimum bandwidth mode of operation. In the 802.11ah example, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth modes of operation, support (eg, only support) 1 MHz mode STAs (For example, an MTC type device), the main channel can be 1 MHz wide. Carrier sensing and/or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (for example, because the STA (which only supports 1 MHz mode of operation) transmits the AP), then the entire available frequency band can be considered busy even though most of the frequency bands remain idle and available for use.

In the United States, the available frequency band available for 802.11ah is 902 MHz to 928 MHz. In Korea, the available frequency band is 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz, depending on the country code.

FIG. 1D is a system diagram showing RAN 113 and CN 115, in accordance with an embodiment. As described above, the RAN 113 may use NR radio technology to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. The RAN 113 can also communicate with the CN 115.

The RAN 113 may include gNBs 180a, 180b, 180c, but it should be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each gNB 180a, 180b, 180c may each include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. In one embodiment, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may use beamforming to transmit signals to and/or receive signals from gNBs 180a, 180b, 180c. Thus, for example, gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a. In an embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers may be on the unlicensed spectrum, while the remaining component carriers may be on the licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement Cooperative Multipoint (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and the gNBs 180b (and/or the gNBs 180c).

The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable parameter numerology. For example, the OFDM symbol spacing and/or the OFDM subcarrier spacing may be different for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may use subframes or transmission time intervals (TTIs) having different or scalable lengths (eg, including different numbers of OFDM symbols and/or continuing different absolute time lengths) to interact with the gNBs 180a, 180b, 180c communicates.

The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c that employ independent and/or non-independent configurations. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may use signals in the unlicensed band to communicate with the gNBs 180a, 180b, 180c. In a non-independent configuration, the WTRUs 102a, 102b, 102c may communicate/connect with the gNBs 180a, 180b, 180c while communicating/connecting with another RAN (e.g., eNodeBs 160a, 160b, 160c). For example, the WTRUs 102a, 102b, 102c may implement the DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c. In a non-independent configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and/or throughput to serve the WTRU 102a, 102b, 102c.

Each of 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, user scheduling in UL and/or DL, support network Road cutting, implementation of dual connectivity, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPF) 184a, 184b, and routing control plane information to access and mobility management functions ( AMF) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c can communicate with each other via the Xn interface.

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 is described as being part of CN 115, it should be understood that any of these elements can be owned and/or operated by other entities than the CN operator.

The AMFs 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, AMFs 182a, 182b may be responsible for authenticating users of WTRUs 102a, 102b, 102c, supporting network cuts (eg, handling different PDU conversations with different needs), selecting specific SMFs 183a, 183b, managing registration areas, terminating NAS Communication, and mobility management, etc. The AMFs 182a, 182b may use network cuts to tailor the CN support provided for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced large-scale mobile broadband (eMBB) access, and/or Services for machine type communication (MTC) access, and the like. AMF 162 may provide for switching between RAN 113 and other RANs (not shown) that use other radio technologies (eg, LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi) Control plane function.

The SMFs 183a, 183b can be connected to the AMFs 182a, 182b in the CN 115 via the N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via the N4 interface. The SMFs 183a, 183b can select and control the UPFs 184a, 184b, and can configure traffic routing via the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU conversations, controlling policy enforcement and QoS, and providing downlink information notifications and the like. The PDU conversation type can be IP based, non IP based, Ethernet based and so on.

The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c to a packet switched network (e.g., the Internet 110). Access to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices, the UPFs 184, 184b may perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU conversations, Handling user plane QoS, caching downlink packets, and providing mobility anchoring and more.

The CN 115 can facilitate communication with other networks. For example, CN 115 may include or may be in communication with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and CN 108. In addition, CN 115 may provide WTRUs 102a, 102b, 102c with access to other networks 112 that 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 the N3 interface between the UPFs 184a, 184b and the DNs 185a, 185b via the N3 interface between the UPFs 184a, 184b and via the UPFs 184a, 184b Local Data Network (DN) 185a, 185b.

In view of the corresponding description of FIGS. 1A-1D and 1A through 1D, one or more or all of the functions described herein in relation to one or more of the following may be performed by one or more emulation devices (not shown) To perform: WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DN185 ab and/or any other device(s) described herein. These emulation devices may be one or more devices configured to emulate one or more or all of the functions herein. For example, these emulation devices can be used to test other devices and/or analog network and/or WTRU functions.

The emulation device can be designed to implement one or more tests of other devices in a laboratory environment and/or an operator network environment. For example, the one or more emulation devices may perform one or more or all of the functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network to test other devices within the communication network . The one or more emulation devices may perform one or more or all of the functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device can be directly coupled to another device to perform the test, and/or can perform the test using over-the-air wireless communication.

One or more emulation devices may perform one or more functions including all functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation device can be used in a test lab and/or in a test scenario of a wired and/or wireless communication network that is not deployed (eg, tested) to perform testing of one or more components. The one or more simulation devices can be test devices. The emulation device can transmit and/or receive data using direct RF coupling and/or wireless communication via an RF circuit (eg, the circuit can include one or more antennas).

In a wireless communication system, cell search may refer to a procedure for the WTRU to acquire time and frequency synchronization with cells, and to detect cell identity (cell ID) of cells. In an example, the LTE synchronization signal may be transmitted by the base station (e.g., eNB, gNB) in the 0th and 5th subframes of each radio frame, and may be used for time and frequency synchronization during initialization. As part of the system acquisition process, the WTRU may sequentially synchronize to OFDM symbols, time slots, subframes, subframes, and/or radio frames based on the synchronization signals. The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). PSS can be used to obtain time slots, sub-frames, and/or half frame boundaries. The PSS can provide a physical layer cell identification code (PCI) within the cell identification code group. SSS can be used to obtain radio frame boundaries. The SSS enables the WTRU to determine a group of cell identifiers, which may range from 0 to 167.

After successful synchronization and PCI acquisition, the WTRU may decode a Physical Broadcast Channel (PBCH) (eg, using Cell Specific Reference Signals (CRS)) and acquire automatic weighting with system bandwidth, system frame number (SFN), and/or entity mix. The Request to Send (HARQ) Indicator Channel (PHICH) configures the relevant Master Information Block (MIB) information. The LTE synchronization signal and/or PBCH may be periodically transmitted in accordance with a standardized period.

When the WTRU is in RRC_IDLE mode, the paging can be used for network initiated connection establishment for the WTRU. In LTE, the paging can operate similarly to the downlink data transmission on the downlink shared channel (DL-SCH), and the WTRU can monitor Layer 1 and Layer 2 for the downlink scheduling assignment associated with the paging (L1/ L2) Control communication. Since the location of the WTRU is not necessarily known at the cell level, it is possible to transmit paging messages across multiple cells in a defined tracking area. The paging can also be used to inform the WTRU in RRC_IDLE and/or RRC_CONNECTED (RRC_CONNECTED) of changes in system information or emergency information.

A valid paging procedure may allow the WTRU to sleep (eg, in idle (IDLE) mode or RRC inactive mode), where no receiver is processed most of the time, and the receiver is woken up for a short time at a predefined time interval to monitor for The paging information of the network. Thus, a paging period can be defined to allow the WTRU to sleep most of the time and only wake up in a short amount of time to monitor L1/L2 control communications. When the WTRU wakes up, if it detects the group identity code for paging (eg, by using the paging radio network temporary identifier (P-RNTI) on behalf of the paging indication to scramble the downlink control information (DCI) cycle Redundancy Check (CRC)), then the WTRU may process the corresponding downlink paging message transmitted on the paging channel (PCH). The paging message may include an identification code of the WTRU(s) being paged, and the WTRU whose identification code is not found in the paging message may discard the received information in the paging message and according to discontinuous reception (DRX). The cycle is dormant.

The network can configure the subframe where the WTRU should wake up and listen for the channel used for paging. The subframe configuration may be cell-specific and may or may not be used in conjunction with a WTRU-specific configuration. A frame in which a given WTRU should wake up and search for a P-RNTI on a physical downlink control channel (PDCCH) may be input by an identifier of the WTRU, a cell-specific paging period, and/or a WTRU-specific paging period. The equation to determine. For example, the WTRU's paging period may range from once every 256 frames to once every 32 frames. The subframes used to monitor the paging within the frame may be derived from an International Mobile User and Identification Code (IMSI) that is subscribed to the cellular service subscription. Since different WTRUs have different IMSIs, the WTRU can calculate different paging instances. Therefore, from a network perspective, the frequency of paging transmissions may be higher than once every 32 frames (or other paging periods), but not all WTRUs will be paged at all paging occasions because they are distributed. On the possible paging instances.

The paging message may only be transmitted in the subset of subframes within the frame. For example, in the paging period, a paging message can be sent in one to four subframes per frame. From a network perspective, the cost of a short paging period is likely to be the lowest, because resources that are not used for paging can be used for data or other transmissions without wasting. However, from the WTRU's perspective, the short paging period increases the WTRU's power consumption because the WTRU needs to wake up more frequently to monitor the paging moment.

In an example, the paging schedule DCI and paging messages can be sent in the same time slot. It has been shown in LTE that the method of paging messages following the paging DCI is very efficient and is therefore expected to be robust to the single beam system in the NR. However, in multi-beam systems where analog beams can be formed in different physical directions, the gNB and the WTRU may have to scan a set of all transmit and/or receive (TX/RX) beams (eg, to determine which beam) Receive paging on). In an example, if the gNB uses up to 64 beams or directions to transmit the paging signal, and if the WTRU scans 4 RX beams, then the gNB may need to direct the paging signal toward each of the 64 beams/directions. / Direction is transmitted four times or a total of 256 transmissions. Therefore, this method for paging through multiple beams can result in a large amount of signal and beam scanning overhead for paging. A WTRU in IDLE mode is unaware of which TX beam is best received (e.g., in terms of signal to noise ratio (SNR) or the ability of the WTRU to decode signals on a TX in a set of TX beams). Receiving all TX beams may increase the processing delay and power consumption of the WTRU. The quasi-co-location (QCL) of the paging signal and the synchronization signal block (SSB) can help the WTRU to pre-identify the appropriate TX beam to receive. An example for reducing paging overhead is described herein.

In one example, the paging signal can be multiplexed with other signals in time and/or frequency. The paging message can be scheduled by the DCI carried by the NR-PDCCH, so that the WTRU can decode the NR-PDCCH carrying the DCI for the paging message in the pre-configured search space. For example, the network can provide a set of control resources (CORESET) for paging reception and control channel search space. The WTRU may be configured as a CORESET for paging reception. The configured CORESET and/or search space may be the same or may be derived from the configured CORESET and/or search space for the remaining minimum system information (RMSI) reception. The parameters or set of parameters for the paging occasion (PO) may be explicitly communicated to the WTRU. The parameters for the PO may include, but are not limited to, including a period for the WTRU to monitor the paging schedule DCI. In an example, the PO can perform frequency multiplexing and/or time multiplexing with the SSB. In another example, the PO can perform frequency multiplexing and/or time multiplexing with configuration information or CORESET. In another example, multiple POs can be frequency multiplexed and/or time multiplexed together. The PO, CORESET, and/or search space may be a function of the WTRU ID.

In one example, Frequency Division Multiplexing (FDM) can be used to multiplex the paging DCI and paging messages with the SSB. Each of NR-PSS, NR-SSS, NR-PBCH can occupy the respective number of resource blocks (RBs) per OFDM symbol. For example, NR-PSS can occupy K1 RBs, NR-SSS can occupy K2 RBs, and NR-PBCH can 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. An OFDM symbol with NR-PSS may have some RBs that carry more data. These RBs, which can carry more data, can be used to carry the paging DCI and/or paging messages (which can also be transmitted in the beam transmitting the SSB). The paging DCI may be scheduled in a CORESET with an SSB (eg, in a non-overlapping CORESET) and may indicate a physical resource block (PRB) (ie, a resource block) carrying the paging message. An indication indicating that the paging DCI and/or paging message will be multiplexed by the FDM may be included in the synchronization signal or broadcast channel (e.g., NR-PSS, NR-SSS, NR-PBCH). The one or more preset OFDM symbols within the SSB where the paging DCI and/or paging message may be multiplexed may be predefined.

The paging DCI CORESET can be FDM (frequency division multiplexing) with the SSB. The NR-PDCCH carrying the paging DCI may be scheduled to be carried in the CORESET (eg, in a non-overlapping CORESET with the SSB). The paging DCI may indicate the location of the paging message in the NR-PDSCH in the same time slot or in different time slots. If a CORESET overlap occurs on the SSB, the NR-PDCCH carrying the paging DCI may be rate matched around the resource elements (RE) occupied by the SSB (eg, these REs will be punctured during the rate matching process). For example, rate matching can be determined by: NR-PDCCH candidate, search space or set of search spaces; or location of an SSB that may be known to the WTRU. The PO can be defined in frequency or combined frequency/time.

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

The PO can be defined in frequency or mixed frequency/time. In an example, paging messages for different POs can be FDM or hybrid FDM/TDM. The paging message can be configured anywhere in the time slot. The number of DCIs that can be advertised with the SSB for FDM may be limited or may be unrestricted. Figure 3 is a block diagram of an exemplary time slot format 300 that includes the paging DCI and SSB of the FDM. The time slot format 300 can be transmitted by multiple beams (e.g., beam 301 and beam 303). In FIG. 3, four paging DCIs 304, 306, 308, 310 may be FDM with SSB 312 (eg, on the PSS), and similarly, four paging DCIs 316, 318, 320, 322 may be associated with SSB 324 (eg, On the PSS) perform FDM. Time slot format 300 may also include PBCHs 314 and 326. In the time slot format 300, the paging messages of the PO 331-338 may be FDM, TDM or hybrid TDM/FDM, and are shown in Figure 3 as being mixed TDM/FDM.

In the above example, the CORESET for the PO and the search space may be predefined or indicated in the system information (eg, RMSI). The PO can be defined in accordance with the SSB. For example, the PO may be defined in accordance with the SSB group, in accordance with the transmitted SSB, or for the maximum number of SSBs (transmitted or untransmitted). For example, the PO may be defined in accordance with a beam group, in accordance with a beam subset, or for all beams.

In an example, the SSB and the paging DCI CORESET can be TDM (time division multiplexing). The NR-PDCCH carrying the paging DCI can perform TDM with the SSB. The NR-PDCCH carrying the paging DCI can be scheduled so that the scheduling restriction can be used so that it does not overlap with the SSB. For TDM, the time offset of the paging DCI CORESET relative to the SSB may be predetermined (eg, fixed or known to the WTRU) or may be different for different POs (where the PO may be a function of the WTRU ID) ). The time offset may be indicated in system information (eg, NR-PBCH), RMSI, or other system information (OSI), and the time offset may be a function of the WTRU ID or calculated based on the WTRU ID.

Figure 4 is a block diagram of another exemplary time slot format 400 that includes a PO for TDM with the SSB. The time slot format 400 can be transmitted by multiple beams (e.g., beam 401 and beam 403). Time slot format 400 may also include PSS 402, SSS 406, and PBCHs 404 and 408.

In the example of FIG. 4, the time slot format 400 has 14 OFDM symbol durations, and the micro time slot has two OFDM symbol durations (other sizes are also usable, such as 4 or 7 OFDM symbols). In the example of Figure 4, simultaneous slot scheduling can be used, but inter-slot scheduling can also be used. The paging DCI and the paging message (PM) can be part of the same micro time slot (in a non-time slot format). PO 421-424 may appear in different OFDM symbols of time slot 400.

Figure 5 is a block diagram of another exemplary time slot format 500 that includes DCI and PO for TDM with the SSB. The time slot format 500 can be transmitted by multiple beams (e.g., beam 501 and beam 503). Time slot format 500 may include PSS 510, SSS 514, and PBCH 512 and 516. In the example of FIG. 5, paging DCIs 502, 504, 506, 508 may be transmitted prior to the paging message and may be TDM (on PSS 510 and SSS 514) with the SSB. Both the slot schedule and the inter-slot schedule can be used without loss of generality. The CORESET or search space for all paging DCIs 502, 504, 506, 508 may be FDM with each other (that is, the first OFDM symbol including DCI 502, 504, 506, 508 may be a symbolic CORESET). PO 521-524 may appear in different OFDM symbols of time slot 500.

Figure 6 is a block diagram of another exemplary time slot format 600 including DCI and PO for hopping with SSB for TDM. Time slot format 600 can be transmitted by multiple beams, such as beam 601 and beam 603. Time slot format 600 may include PSS 610, SSS 614, and PBCH 612 and 616. Different paging DCIs 602, 604, 606 may be TDM (ie, transmitted in different OFDM symbols), and the frequency locations of PO 621-623 may be different. The frequency locations of these CORESET, search space or paging DCIs 602, 604, 606 may be fixed, may be indicated in system information (eg, RMSI), and/or may be a function of the WTRU ID (eg, using modulo operations) Or calculated based on the WTRU ID. The frequency locations of the PO DCIs 602, 604, 606 may be different or the same for the beam repeat pattern (eg, may be the same or different for beam 601 and beam 603). The frequency locations of the paging DCIs 602, 604, 606 can be blindly decoded.

In response to the above, the CORESET and search space for the PO can be predefined, indicated in the RMSI, or derived from the RMSI. In view of the above, from the perspective of the WTRU, each PO (eg, PO 621-623 in FIG. 6) may be defined in accordance with a beam group or for all beams (eg, as a beam subset or group, Or a combination of all beams).

The WTRU may monitor the PO and the beam associated with the corresponding PO to be able to receive paging messages for the WTRU. For example, the WTRU may monitor the PO in a beam group associated with the PO or monitor all beams for the PO. The WTRU may monitor the PO and the SSB associated with the corresponding PO. For example, the WTRU may monitor the POs in an SSB group associated with the PO, or monitor all SSBs for the PO. A WTRU may monitor multiple POs (eg, more than one PO) and beams associated with corresponding POs. The WTRU may monitor multiple POs (eg, more than one PO) and SSBs associated with the corresponding POs. The WTRU may monitor the POs derived from the WTRU_ID in each of the transmission beams associated with the different SSBs actually transmitted.

TDM and FDM can be supported for SSB and paging DCI CORESET. The paging DCI CORESET can be configured to perform FDM with the SSB in a non-overlapping manner (eg, in the case of large bandwidth transmissions). The paging DCI CORESET can be configured to perform FDM with the SSB in an overlapping manner (eg, in the case of small bandwidth transmissions). The search space may overlap with the SSB or may not overlap with the SSB. If the CORESET overlaps with the SSB, any one or more of the following operations may be performed: rate matching may be performed around the SSB, so the NR-PDCCH may or may not be decoded; and/or the paging DCI for the overlapping region may be discarded, The DCI and the message may be included in the next PO such that the NR-PDCCH may or may not be decoded.

Two different modes, FDM and TDM, can be used to page DCI and multiplex of one or more paging messages, and can provide a 1-bit indication to switch between these modes. This indication can be carried in system information such as RMSI and/or OSI. In one example, some paging DCI CORESETs can be TDM, while other paging DCI CORESETs can be FDM using dynamic selection. This dynamic selection increases scheduling flexibility. The TDM or FDM for the configuration of the current one or more paging CORESETs may be indicated using one or more bits. This indication can be carried in system information such as RMSI and/or OSI. If no mode is indicated (eg, FDM or TDM), the WTRU may blindly detect the FDM or TDM of the paging CORESET. In an example, FDM can be used for larger bandwidths (eg, over 6 GHz), and TDM can be used for smaller bandwidths (eg, below 6 GHz).

In an example, the PO can be configured to have a beam based design. The WTRU may use discontinuous reception (DRX) in idle mode to reduce power consumption. A PO is a unit that can have a P-RNTI transmitted on a PDCCH that addresses a paging message. A paging frame (PF) can be a radio frame that can contain one or more POs. When DRX is used, the WTRU can monitor only one PO per DRX cycle. A WTRU in the RRC_IDLE and RRC_INACTIVE states may monitor the paging in each DRX cycle. The length of the DRX cycle can be configurable. The preset DRX cycle length can be provided in system information such as NR-PBCH, RMSI or OSI. The WTRU-specific DTX cycle length may be provided to the WTRU via dedicated messaging. The WTRU may be specifically configured with a PO, time slot, and/or micro time slot (in a non-time slot format) to monitor the paging signal. The number of POs in the DRX cycle may be configurable and may be provided in system information such as NR-PBCH, RMSI or OSI. If the network is configured with multiple POs in the DRX cycle, the WTRU may be distributed to these POs based on the WTRU ID (eg, IMSI or System Architecture Evolution (SAE) - Temporary Action User Identity (s-TMSI)).

The (analog) beam scan can be used to transmit the paging in different directions. The paging DCI can use beam scanning, and the paging message (PM) can use the same beam that is co-located with the paging DCI. The paging DCI and paging messages can be scanned using separate beams. Exemplary conditions for using different beams for the paging DCI and paging messages include, but are not limited to, the following conditions: paging DCI and paging messages may require different beams or beamwidths; and/or paging DCI beams may be obsolete due to paging messages (eg, Because of the time slot schedule).

The PO may include any set, subset, or combination of time slots, non-time slots (eg, micro time slots), subframes, and/or OFDM symbols. Multiple time slots, non-time slots (eg, micro time slots), subframes, and/or OFDM symbols may be used in each time slot, non-time slot (eg, micro time slot), subframe, or OFDM symbol. Different sets of multiple downlink TX beams are enabled to transmit paging, or can be enabled for TX/RX beam repetition. The number of time slots, non-time slots (eg, micro time slots), subframes, and/or OFDM symbols in the PO (eg, each non-time slot 2, 4, or 7 OFDM symbols) may be in system information (eg, NR- Provided in PBCH, RMSI or OSI).

The WTRU may be grouped to monitor a particular PO. The 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, including a WTRU ID, S-TMSI, or IMSI. Examples of cell-specific parameters may include, but are not limited to, cell ID, cell timing information, SSB index (SSBI), semi-radio frame number, or SFN.

In the case of beam-based design, the definition of PO can be extended. For example, the definition of PO may depend on whether beam scanning is performed with one beam for the entire time slot or with one beam for each time slot. If beam scanning is performed with one beam at each time slot, the PO can be defined based on the time slot and the WTRU can monitor a particular time slot in the frame. If beam scanning is performed with one beam in each non-time slot (eg, micro time slot), the beam may change (or be repeated) for each non-time slot (eg, micro time slot). In this case, the PO may be defined based on the time slot in which the micro time slot is present, or the PO may be defined based on the micro time slot. These methods may be affected by the number of SSBs or beams actually transmitted, and/or the maximum number of SSBs or beams.

For example, a PO can be defined based on a time slot. In this case, the PO can be defined based on the time slot without any offset. The WTRU may calculate its PO, which may be a time slot in which a micro time slot exists. The WTRU may attempt to decode all of the micro time slots to obtain the paging DCI and find a paging for the WTRU. The WTRU can use the QCL or its most recent historical association with its beam or paging location to identify the micro time slot assigned to the WTRU. In the case where the PO that performs beam scanning occupies a plurality of time slots, the PO may be a time slot or a micro time slot at which beam scanning starts. Figure 7 is a resource format 700 for the illustrated paging schedule, where PO is defined by scanning of four beams 710, 712, 714, 716 with a microslot size of 2 symbols. POs 701 and 702 may be defined for micro time slots (non-time slot format), which include subsets of OFDM symbols in time slots X and X+1, respectively. As shown in Figure 7, the PM can use the same beam and can be co-located with the paging DCI (P-DCI).

In another example, the PO can be defined based on a time slot with an offset for the micro time slot. The scheme can use SSBI as an indicator to point to the micro time slot for the PO (eg, using associations). Depending on the frequency band in which the WTRU is operating, there may be different situations, and this in turn indicates the maximum number of SSBIs or the maximum number of beams. An example of the number of time slots used to complete a scan with one beam repeat is shown in Table 1, where nsSym is the number of OFDM symbols in each non-time slot and L is the maximum number of SSBs. This situation can be seen as a configuration. Table 1: Number of time slots used to complete beam scanning

The WTRU may calculate the actual micro-slot location for monitoring the paging DCI when multiple beams (actually transmitted beams) are used and the number of time slots required to complete the scan (transmissions in all directions) is known. Depending on the type of service, a subset of the configurations defined in Table 1 can be defined. URLLC or any other configuration that requires low latency can use a small number of symbols in the micro time slot (eg 1 or 2 OFDM symbols). mMTC or very large scale deployments may use a greater number of symbols (eg, 7 or 14 OFDM symbols) in the micro time slot.

As mentioned above, PO can be defined based on micro time slots. The WTRU may wake up on a particular time slot for the PO, where the time slot may be configured in the RMSI. The non-time slot can include a CORESET for paging DCI and paging messages. In the case of scanning the paging DCI before scanning the paging message, the WTRU may wake up during the transmission of the paging DCI scan. Figure 8 is a resource format 800 for the illustrated paging schedule, where PO 801 and 802 are via four beams having two OFDM symbols 810/812, 814/816, 818/820, and 822/824, respectively. The scan is defined.

As noted above, in any of the above cases, the WTRU may calculate its own PF and/or PO. In a beam-based paging design, the computational process for calculating PF and/or PO can be based on the DRX cycle, the number of POs per DRX cycle, whether the format used is slot-based or non-time slot based, time slot or micro time The number of slots (based on the format of the non-time slot), the number of SSBs (eg, the actual transmitted SSB or maximum SSB) and/or beam configuration. Table 2 gives exemplary parameters for calculating PF and/or PO. Table 2: Example parameters for beam-based paging configuration and calculation of PF and/or PO

In an example, a program can be used to calculate the PF. The PF can be defined as a radio frame in which the WTRU looks for a PM. The PF may include one or more POs on one or more beams. The following example equation can be used to calculate the PF: PF = SFN mod T = (T div N_b) * (WTRU_ID mod N_b) Equation (1) More generally, PF can be calculated as PF = f (SFN, T, N, L, WTRU_ID), where f() is any function or linear combination. In another example, the PF can be pre-defined or pre-configured.

In one example, a program can be used to calculate one or more POs. The PO may be a time slot and/or a time slot (time slot) within the time slot, where the P-RNTI may be transmitted on the PDCCH addressed to the WTRU's PM. Each WTRU may have one or more POs during the DRX cycle.

The function for calculating the PO may be defined based on parameters such as the number of subframes Ns and/or the index i_s pointing to the PO. Different functions can be defined for simultaneous slot or span time slot scheduling for paging DCI and/or PM. The following example equation can be used to calculate PO: PO = (i_s *La + SSBI) * nsSym Equation (2) PO = (i_s *La + SSBI) * nsSym + Offset(i_s) Equation (3) All POs may be contiguously positioned or may not be contiguously positioned, and wherein the Offset() function may be a pattern that shuffles the order of different POs. The Offset() function can be used to assign POs discontinuously. As shown in FIG. 9, the functions in equations (2) and (3) may also assume that beam scanning for the first PO is followed by beam scanning for the second PO, beam scanning for the third PO, and the like. Wait. Figure 9 is a resource format 900 for an example paging schedule in which POs 901, 902, 903 are scanned together (e.g., beam scanning of the first PO 901 (transmitted in all directions), then to the second PO 902 performs beam scanning and then performs beam scanning on the third PO 903). For example, a WTRU may monitor a PO 901 that is part of a beam group (eg, beams 910, 912, 914, 916) associated with PO 901, a beam group associated with PO 902 (eg, beams 910, 912, 914) The PO 902 is monitored, 916), and the PO 903 is monitored in a beam group (e.g., beams 910, 912, 914, 916) associated with the PO 903.

In another example, the WTRU may monitor each PO in all beams. In another example, for each beam, multiple POs can be combined, and the PO set can be scanned across the beam as shown in FIG. Figure 10 is a resource format 1000 for an exemplary paging schedule. In the example of FIG. 10, PO 1001, 1002, 1003, 1004 may be combined for each of the beams 1011, 1012, and 1013.

In an example, i_s and the corresponding time slot (or micro time slot) number of the transmitted PO may be used in a predefined table to define an index i_s pointing to (or associated with) the PO from the subframe. In another example, the index i_s can be derived using the following exemplary equation: i_s = floor(WTRU_ID/N) mod Ns Equation (4) If QCL is not assumed, then it can be assumed that SSBI is defined between 0 and L- In the range of 1, where L is the maximum number of SSBs in the frame. In this case, the L beams can be scanned for the process of transmitting the paging. In another embodiment, the PO table can be defined as the association between i_s and the time slot in which the PO can be transmitted. For simultaneous slot or inter-slot scheduling for paging DCI/PM, a different set of tables (or associations) (between i_s and/or paging time slots of the DCI and/or PM) may be defined.

In an example, the WTRU may be woken up to monitor POs in a particular time slot or non-time slot during a paging period. The paging period can be configured in system information or control communication (eg NR-PBCH, RMSI or OSI). In order to transmit paging DCI and paging messages, different modes can be configured for the WTRU. The sample mode includes a time slot based, non-time slot based or hybrid time slot based and non time slot based paging transmission mode. This transmission mode can be configured in system information or control communication (eg NR-PBCH, RMSI or OSI).

In the example of time slot based paging, the time slot based paging DCI may be followed by a time slot based paging message. In the example of non-time slot based paging, the non-time slot based paging DCI may be followed by a non-time slot based paging message. In the hybrid paging example, the non-time slot based paging DCI may be followed by a time slot based paging message, or the time slot based paging DCI may be followed by a non-time slot based paging message.

Examples of parameter numerology may include, but are not limited to, including subcarrier spacing (SCS) and cyclic prefix (CP). The parameter configuration for paging can include parameter configurations for the paging DCI and the paging message. The parameter configuration for paging can be the same as, or can be derived from, system information (eg, RMSI), which can be indicated in system information (eg, in NR-PBCH). The paging DCI and the paging message may or may not have the same parameter configuration, and the paging parameter configuration may be the same as or different from the parameter configuration of other messages, such as random access channel (RACH) message 2 and message 4.

The PO may be defined or derived based on any one or more of the following parameters: number of FDM POs; number of TDM POs; WTRU ID; SSBI; per beam group or all beams; per SSB group or all SSBs; Preamble index; RACH resource index; time slot index or non-time slot index; OFDM symbol index; search space index; search space set index; CORESET index; bandwidth part (BWP) index; carrier index; cell index or cell Meta ID; and/or transmission and reception point (TRP) index. For example, the PO may be defined or derived based on a combination of paging DCI and paging messages, where the paging DCI and paging messages may be in the same or different time slots, micro time slots, or non-time slots. In another example, the PO may be defined or derived based on any one or more of the following: search space, search space group, search space set, search space collection group, CORESET, CORESET group, BWP, and/or BWP group.

The above techniques can be used to reduce the number of beams and time required to monitor paging in a beam scanning system. In an example, the procedure for determining the beam to be monitored for paging and beam scanning can be defined by the relationship between paging CORESET, paging messages, and/or SSB. In an example, the paging multiplex type (PMT) can be defined based on the relationship between the paging CORESET, the paging message, and/or the SSB to determine the beam for paging. 11 is a flow diagram of an exemplary paging beam selection procedure 1100 that may be performed by a WTRU. At 1102, the WTRU may receive configuration information (eg, parameter configuration, beam SCS, DRX cycle) for paging (eg, via system information (eg, RMSI)). At 1104, the WTRU may determine a parameter configuration (eg, SCS, CP) for paging and an SSB for paging the beam, and may determine an SCS for each of the SSB and the paging DCI/message. At 1106, it is determined whether the SCS for SSB and paging reception is the same or different. If the SCS for the SSB and paging reception is different, then at 1108, it is determined that the PMT is the first type of PMT (PMT A). If the SCS for the SSB and paging reception is the same, then at 1110, it is determined that the PMT is the second type of PMT (PMT B). At 1112, based on the determined PMT (PMT A or PMT B), a beam, time, and frequency relationship between a paging CORESET, a paging message, and an SSB can be determined. In an example, for a different PMT A for SSB and paging reception, the paging CORESET can be TDM with the paging message (eg, using a repeating beam), and the paging message can be time aligned with the SSB (at the same time) In the slot, and the paging message can be FDM with the SSB. In an example, for the same PMT B for SSB and paging received SCS, the paging CORESET can be TDM with the paging message (eg, without using a repeating beam), the paging CORESET and paging messages can be associated with the SSB Time alignment (eg at the same time slot) and FDM with the SSB. At 1114, the WTRU may monitor the PO in one or more beams of the PO based on the determined beam, time, and frequency relationships.

Figure 12 is a message transfer diagram of an exemplary paging multiplex format 1200 for PMT A during PO 1210, where there is a different SCS between paging message 1206 and SSB 1208. In the example of FIG. 12, at each PO 1210, 2L beams are repeated for paging CORESET 1204 and paging message 1206/SSB 1208. In other words, each of the beams 1202 ₁ ... 1202 _L will be repeated once in the PO 1210 (in PO 1210, a total of two transmissions per beam). The paging CORESET 1204 and the paging message 1206 can be TDM on each of the beams 1202 ₁ ... 1202 _L (ie, two transmissions across each of the beams 1202 ₁ ... 1202 _L ). For each beam 1202 ₁ ... 1202 _L , the SSB 1208 can be FDM with the paging message 1206 on the second transmission.

Figure 13 is a message transfer diagram of an exemplary paging multiplex format 1300 for PMT B during PO 1310, where the same SCS exists between paging message 1306 and SSB 1308. In the example of FIG. 13, for each PO 1310, L beams 1302 ₁ ... 1302 _L are transmitted for the paging CORESET 1304 and for the paging message 1306 / SSB 1308. Beams 1302 ₁ ... 1302 _L are transmitted once in PO 1310. The paging CORESET 1304 and paging message 1306 can be TDM (within the same beam transmission) on each of the beams 1302 ₁ ... 1302 _L. For each of the beams 1302 ₁ ... 1302 _L , the SSB 1308 can be FDM with the CORESET 1304 and the paging message 1306.

An example of a configuration for a PO is described herein. as well as The SFN and time slot index, which can be defined as CORESET, respectively, are used for paging based on the SCS of the paging CORESET. If the WTRU is at SFN= And time slot = The WTRU may then use the paging configuration (eg, in the RMSI) and/or the WTRU's own WTRU_ID to determine the number of consecutive resource blocks and/or the number of consecutive symbols for the CORESET that includes the paging search space.

The WTRU may be configured with a paging search space configured by higher layer parameters. For example, using a PDCCH candidate, a Control Channel Element (CCE) aggregation level, and/or a known P-RNTI, the WTRU can blindly decode the paging DCI. The configured paging search space may be multiple (eg, where there may be different CORESETs), and the WTRU may select one of the paging search spaces based on its WTRU_ID. If the WTRU is not provided with one or more higher layer parameters for the paging search space, the association between the monitoring opportunity for the paging search space and the SS/PBCH block index may be the same as the association for the monitoring opportunity for the RMSI. At all times, the SCS and CP length for the PDCCH paging search space may be the same as the search space for the RMSI.

One or more paging CORESETs can be TDM or FDM with the SSB. This can be based on multiplexed patterns for SSB and RMSI CORESET. Different multiplex schemes for POs of different WTRU groups can be used. Different POs for different WTRU groups (eg, based on WTRU_ID) may be TDM or FDM. In a beam-based system, the FDM-based PO can reduce the beam scanning overhead for paging. POs via TDM can be defined in terms of different time slots where paging DCI is likely to exist. The FDM of multiple POs may be performed in accordance with a plurality of BWPs, CORESETs, and/or search spaces where there may be paging DCIs. However, two-dimensional multiplexing (ie TDM and FDM) can provide additional flexibility.

The preset association between the SSB and the monitoring window of the PDCCH containing the paging DCI may be the same as the association between the SSB and its RMSI monitoring window. In one example, the RMSI can be transmitted once every 160 ms to the maximum. However, the paging can be transmitted based on the DRX cycle configured for the particular WTRU. Based on the DRX cycle, the WTRU is able to identify the frame for the PO. If multiple WTRUs are paged in the PDM's PO, the formula used to calculate the paging frame can be modified. The number N of paging frames in the WTRU's DRX cycle and the number Ns of subframes used for paging within the paging frame may be modified based on the number of POs (nFDMp) being FDM. This, in turn, can modify the calculation of the SFN that the WTRU monitors for paging based on nFDMp.

In an example, the SFN for paging may be calculated based on the WTRU_ID, the DRX period T configured for the WTRU, and the number of POs that are FDM. If all POs are transmitted in TDM, nFDMp can be set to 1. T may be the WTRU's DRX cycle (exemplary values include 32, 64, 128, 256). nB can be the number of POs per DRX cycle (exemplary values include T, 2T, T, T/2, T/4, T/8, T/16, T/32, T/64, T/128, and T/ 256). nFDMp can be the number of POs that are FDM (eg, search space/BWP or different CORESET). N may be the number of paging frames within the WTRU's DRX cycle (exemplary 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 can be the number of subframes used for paging in the paging frame (the exemplary formula can be Ns = Max (1, nB/ (nFDMp *T)): (16,8,4,2,1)/nFDMp ). In order to calculate the SFN (SFNpaging mod T) for paging, the paging may be sent in a frame with SFN mod T equal to (T div N )* (WTRU_ID mod N).

Different physical resources for multiplexing multiple POs can be defined. For example, physical resources can be defined based on search space, CORESET, BWP, and/or time slots (or hour slots). Multiplex POs based on time slots (or micro time slots), POs by TDM, and search spaces, multiplexed POs based on CORESET and BWP, and POs by FDM can be considered. If a different time slot is used to enable the TDM of the PO, then the time slot offset from the reference point can be calculated. For example, the reference point may be a 5 millisecond boundary, a system frame start, a calculated CORESET position for the Type 0-PDCCH (eg, configured by NR-PBCH), or a different (eg, fixed or configured) period. The time slot offset may be calculated as a function of the WTRU's WTRU_ID. If a different BWP is used to enable the FDM of the PO, the BWP for paging DCI may be configured by the gNB, or the BWP may be a function of the WTRU_ID. If the BWP is a function of WTRU_ID, the WTRU may calculate a BWP for paging to locate the PO to be monitored.

If a different CORESET is used to enable the FDM of the PO, the CORESET index for paging DCI can be configured by the gNB. The CORESET index can be part of the search space configuration. If the CORESET carrying the PO is a function of the WTRU_ID, the CORESET can be reflected in the search space ID (SearchSpace_ID). The corresponding search space can be associated with a CORESET carrying a PO. If different search spaces are used to enable multiple FDMs for the PO, the lookup spatial index of the paging DCI may be configured by the gNB, or the index may be calculated by the WTRU using the WTRU_ID. During beam scanning, a combination of any of BWP, CORESET, and/or search space can be used to multiplex different POs. For complete flexibility, TDM, FDM or hybrid TDM/FDM can be used between different POs. The POs used for these scenarios are defined here.

In the example of a multiplexed pattern ("Multiplex Pattern 1"), the PO configuration may cause the RMSI CORESET to be TDM with the SS/PBCH block, and the preset association for paging monitoring may be the same as the RMSI monitoring window. In the example of PO configuration of multiplexed pattern 1, TDM can be used for different POs. The PO can be defined as a beam scanning period with different time slot offsets for the RMSI CORESET associated with the PO. The RMSI can also be scanned by the beam. The time offset for each PO can be fixed, configured, or based on WTRU_ID. The time offset can be defined in terms of time slots or non-time slots (micro time slots) (eg, 2, 4, 7 OFDM symbol time slots). The frequency of monitoring the PO may depend on the DRX cycle and/or the SFN to be monitored for paging, and it may be calculated by the WTRU. For SS/PBCH blocks that are actually transmitted with SSBI i , the WTRU may use a function to determine the paging monitoring time slot (or micro time slot) within the paging frame. index of. Paging monitoring time slot (or micro time slot) It may be a WTRU_ID and/or an O, M value for RMSI CORESET (which may be configured in the NR-PBCH) (eg, O and M may be pre-in the WTRU procedure for monitoring the Type0-PDCCH common search space) Defined) function. In this case, the number of POs (nFDMp = 1) of the FDM may be 1. Different time slot offsets may be calculated based on the index of PO i_s, where the index may use WTRU_ID, the number of paging frames (N) in the WTRU DRX cycle, and/or the number of subframes used for paging within the paging frame (Ns) to calculate. The slot offset may now be tabulated or may be a function based on different variables (eg, i_s and/or SCS for paging PDCCH).

The following is the use of WTRU_ID to calculate the time slot containing PO Exemplary equation: Equation (5) where , Is a table, function (eg, hash function) or other association that associates index i_s with the slot number of the paging, and i_s = floor(WTRU_ID/N) mod Ns (PO according to WTRU_ID). In equation (5), O and M are defined for RMSI CORESET. The calculation of the time slot offset can also depend on the SCS ( ). If you perform a micro-slot-based scan, you can modify about The calculations, but the general concepts will remain the same. For the entire beam scan (eg, at greater than 6 GHz, i = 0-63, at less than 6 GHz, i = 0-7, or, more generally, depending on the number of SSBs actually delivered), PO can be For the entire beam scan To define. [1]

In another example, the same equation as RMSI CORESET can be used to calculate the time slot containing the PO using WTRU_ID: Equation (6) Equation (7) where Is a PDCCH monitoring offset, which can be configured by the parameter monitoringSlotPeriodicityAndOffset of the search space for paging, and Is a table, function (such as a hash function), or other association that associates the index i_s with the slot number of the paging. in Where s can be the search space set index for paging, and p=0, which is the index of the RMSI CORESET. The time slot in which the paging occurs can depend on the SCS.

The duration of the paging CORESET can be defined by the top-level parameter CORESET-time-duration-paging or can be the same as the RMSI CORESET. The set of resource blocks used to page CORESET may be defined by the top level parameter CORESET-freq-dom-paging or may be the same as RMSI CORESET. In an example, the paging may be transmitted in each BWP in an interleaved manner in one or more of the same time slots. If you use interleaving, you can use BWP_ID to calculate the PO-containing Time slot. Multiple scans for PO can be based on micro time slots to reduce scan overhead.

Figure 14 is an exemplary multiplex pattern 1 for a PO configuration 1400 in which the paging CORESET is TDM with the SS/PBCH block. S is an OFDM symbol number, and the time slot includes 14 symbols. In this example, time slot 1413 includes OFDM symbols 28-41. The arrows indicate OFDM symbols that are quasi-co-located and transmitted on the same beam. Time slot (4,1) A PO 1401 is included for the beams associated with beams 1444 and 1455. At symbol In the first index x is SSBI (with time slot) Associated), the second index y is the ID (po_id) of the PO. In this example, M = 0.5 (and can be predefined as described above), which means that the two SSBs 1404 and 1405 can be associated with the time slot, respectively. as well as Associated, so it contains two paging CORESETs. The WTRU synchronized to SSBI 1404 may receive the corresponding location in the subsequent time slot indicated by SSBI 1404 to discover the paging CORESET or paging DCI. In this case, the time slot as well as Can be the same. Time slot A PO 1402 for beams associated with beams 1444 and 1445 can be included. In the example of Figure 14, each of the POs 1401 and 1402 can be transmitted in its own beam scan. This approach may have a higher latency, but greatly simplifies implementation by reducing the number of beams used for paging. The WTRU may be configured (recessively or explicitly) to monitor only one of the search spaces 1421 corresponding to the POs 1401 and/or 1402 of the different beams 1444 and 1445 based on the WTRU_ID to receive the paging messages 1431 and/or 1432.

In another example, different (TDM) POs may occur in the same SSB cycle. For example, if the SSB is transmitted at time slots T1, T2, T3, T4, then PO1 can be transmitted at time slot T1+K, PO2 can be transmitted at time slot T2+K, and so on, where K is partial shift. The value of the offset K can be 0 or any value greater than zero. In this case, in TDM mode, the same paging DCI and paging message can be transmitted in all BWPs with cells defining the SS/PBCH block. In an example, the paging DCI and paging message may be transmitted at the WTRU's initial active BWP, and thus different paging messages may be transmitted in each BWP, which may depend on the different WTRUs residing on the BWP. The gNB can register the initial active BWP with the cell that defines the SS/PBCH block. In an example, a mechanism for the WTRU to indicate the SS/PBCH block of its cell definition to the gNB may be defined.

Exemplary procedures for determining the configuration of POs that are TDMs performed by the WTRU are described herein. The WTRU may synchronize with the PSS/SSS and/or receive the MIB from the PBCH. The WTRU may discover a CORESET for the RMSI from the MIB and may perform blind decoding for the Type 0-PDCCH (Type 0-PDCCH). The WTRU may receive SIB1 from the PDSCH indicated by Type0-PDCCH. The WTRU may discover the paging configuration and may configure the DRX cycle as well as the paging search space. The WTRU may use the DRX cycle and the WTRU_ID to calculate . The WTRU may calculate an index i_s based on the DRX cycle and the WTRU_ID. Using i_s, the WTRU can calculate the offset for the PO from the RMSI CORESET.

The WTRU may find one or more time slots, one or more time slots, or one or more time slots (eg, for each beam) that it should monitor for paging. The SS/PBCH block and associated paging search space can be quasi-co-located. Thus, the WTRU can use the associated beam for each time slot. If the actually transmitted SSB is different from the defined SSB, the association between the paging search spaces can be performed using the logical index or entity index (or SSBI) of the SS/PBCH block. The WTRU may enter the idle_mode (IDLE_MODE) if there is no further operation with respect to the WTRU.

The WTRU may wake up in a time slot that is based on the calculated SFN and the last strongest beam registered. If the WTRU is configured to scan for a beam, the WTRU may wake up in the first beam and may scan all beams in a time slot associated with the PO for the WTRU. The WTRU may use time slot or micro time slot calculations such as those described above. Using the search space definition for paging, the WTRU may discover the paging CORESET. If no CORESET is defined, the WTRU may use CORESET 0 (eg, CORESET for RMSI). The WTRU may use the search space table to blindly decode the Type 2-PDCCH (Type 2-PDCCH) using the P-RNTI. If the WTRU finds a Type2-PDCCH, the WTRU receives the PDSCH indicated by the PDCCH to determine if the WTRU is paged. If the WTRU is paged, the WTRU may establish a connection with the gNB. If the WTRU is not paging, the WTRU may revert to IDLE_MODE.

In another example of PO configuration for multiplexed pattern 1, FDM can be used for different POs. In one example, the PO may transmit the PO only on the WTRU's initial active BWP (ie, the WTRU's first synchronized BWP). In this case, the WTRU may switch from the currently active BWP to the initial active BWP for its PO to check if it is paged. The paging message can be assumed to be transmitted in the same BWP as the paging (indicator) DCI. If a large number of disproportionate WTRUs have the same BWP as their initial active BWP, load balancing will be a challenge for gNBs. In this case, POs for different WTRUs may be distributed between different BWPs based on the WTRU_ID.

In this case, the PO can be defined as the beam scanning period of the RMSI CORESET associated with the PO. All POs can be FDM together in the same time slot without offset. POs can be in different search spaces and can be in the same or different CORESETs of the same time slot. The search space (and associated CORESET) for the WTRU to monitor the Type2-PDCCH may depend on the WTRU_ID. The frequency at which the WTRU monitors the PO may depend on the DRX, and the SFN for the WTRU to monitor the paging may be calculated by the WTRU. For RMSI, the paging time slot calculation can be the same.

Different POs can be transmitted on all BWPs or can be multiplexed on the BWP. If the PO is multiplexed in a different BWP, the BWP used to monitor the WTRU may be configured by the gNB or calculated by the WTRU and may depend on the WTRU_ID. For example, if there are 4 POs that are FDM in total, and there are 2 BWPs on which the PO is multiplexed, then each BWP can contain 2 POs. This distribution can be a function of the WTRU_ID. Two POs in the same BWP can be in the same or different CORESET.

In each BWP, POs can be assigned to different search spaces. These search spaces can be associated with the same CORESET or a different CORESET. If these search spaces are associated with different CORESETs, the WTRU monitored CORESET may be pre-defined for WTRU_ID or based on WTRU_ID. For example, if there are 4 POs in the BWP and there are 2 CORESETs on which the PC is multiplexed, then each CORESET can contain 2 POs in both search spaces. This distribution can be a function of the WTRU_ID. The WTRU may use the WTRU_ID to calculate a search space with a CORESET-ID. If the CORESET-ID is not calculated by the WTRU using the WTRU_ID, then the gNB may indicate the associated paging CORESET when configuring the paging search space. POs that are in the same CORESET may be located in different search spaces. These search spaces may be pre-configured to the WTRU group, or the WTRU may use the WTRU_ID to calculate a common search space for monitoring the WTRU's PO. In order for the WTRU to calculate the time slot for monitoring the PO, the same formula for the RMSI can be used. The BWP, CORESET, and/or seek space that the WTRU is to monitor may be a function of the WTRU_ID. The BWP, CORESET, and/or search space may be a function of any one or more of the following parameters: the total number of POs; the number of FDM POs in the BWP (nFDMp_bwp); the number of FDM POs in the CORESET (nFDMp_coreset); Number of FDM POs (nFDMp_ss); in the absence of TDM for POs, nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]; number of paging frames within the WTRU's DRX cycle; and/or paging within the paging frame The number of time slots used.

An example of PO calculation is described below. The time slot containing the PO can be calculated using the following equation: Equation (8) In the case where the number of SSBs actually transmitted is different, the logical index of the SSB can be associated with the time slot for the paging scan. The BWP to be monitored and the search space to be monitored may be a function of the PO index and/or the total number of FDM POs in each of the above dimensions (eg, BWP, CORESET, search space). The CORESET associated with each search space can be included in the search space configuration and therefore does not have to be explicitly mentioned.

In this example, the ID of the BWP can be calculated according to BWP_id = f (PO_id, nFDMp), and the ID of the search space can be calculated according to SearchSpace_id = f (PO_id, nFDMp), where PO_id can be an index of the PO. The number of FDM POs can be calculated according to nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss], where nFDMp_bwp is the number of FDM POs in the BWP, nFDMp_coreset is the number of FDM POs in the CORESET, and nFDMp_ss is the number of FDM POs in the SS. If the number of FDM POs in the BWP is nFDMp_bwp=1, then this may mean that the PO is not multiplexed on the BWP, or the PO is transmitted on the different BWPs configured. If the number of FDM POs in the CORESET is nFDMp_coreset=1, then this may mean that the PO is not multiplexed on the CORESET. The PO's index (PO_id) can be calculated using the WTRU_ID and modulo (mod) function, such as PO_id = floor(WTRU_ID/N) mod Ns. In this exemplary scenario, if the paging CORESET is different from the RMSI-CORESET, the gNB scheduler can avoid the overlap of the paging CORESET and the RMSI-CORESET. In an example, multiple RNTIs can be used for paging on the same common search space. A plurality of different RNTIs may be assigned to different WTRU groups (eg, based on WTRU_ID). If multiple RNTIs (or a series of RNTIs) are used for paging, the WTRU can identify its own RNTI based on its WTRU_ID and can discover the PDCCH including its paging DCI. The plurality of RNTIs may be selected from a series of paging RNTIs (PG-RNTIs).

Figure 15 is another exemplary multiplex pattern 1 for PO configuration 1500 in which the paging CORESET is TDM with the SS/PBCH block. In Fig. 15, it is assumed that the SCS is 120 kHz corresponding to the SS/PBCH block pattern. S is the OFDM symbol number, and the time slot includes 14 symbols. In this example, time slot 1513 includes OFDM symbols 28-41 (e.g., corresponding to the third time slot in the SS/PBCH block pattern). In the example of Figure 15, M = 0.5 (and may be predefined as described above). Therefore, two beams with SSBI 1504 and 1505 can respectively contain time slots for two different beams with SSBI 1504 and 1505. The same time slot 1513 of two different paging CORESETs (each having 4 OFDM micro time slots) is associated. The OFDM symbols S = 32, 33, 34, 35 can be transmitted in one direction, and the OFDM symbols 36, 37, 38, 39 can be transmitted in the other direction (i.e., on different beams). These two CORESETs can include PO 1541-1544 in 4 different search spaces (SSp) 1521-1524. The WTRU may use its WTRU_ID to find the paging search space 1521-1524 associated with the WTRU such that the WTRU may find its own PO from 1541-1544, as well as locate paging messages 1531-1534.

Figure 16 is another exemplary multiplex pattern 1 for PO configuration 1600 in which the paging CORESET and the SS/PBCH block are TDM. In the example of Figure 16, two beams with SSBI 1604 and 1605 are associated with the same time slot 1613 containing four different paging CORESETs (two paging CORESETs associated with SSBI 1604 have 4 OFDM symbol micro time slots) And the two paging CORESETs associated with SSBI 1605 have 3 OFDM symbol micro time slots). Time slot Each of the beams (two beams in total) is associated with two CORESETs, each of which has two search spaces: search spaces 1631 and 1632 and search spaces 1633 and 1634, respectively. The WTRU may discover its paging search space and CORESET depending on the WTRU_ID (eg, the search spaces 1621 and 1622 associated with respective beams associated with SSBI 1604 and 1605 may combine to generate CORESET), and may discover its own PO (eg, PO 1641, 1642, 1643 or 1644).

Figure 17 is another exemplary multiplex pattern 1 for PO configuration 1700 in which the paging CORESET and the SS/PBCH block are TDM. In the example of Figure 17, four beams with SSBIs 1704, 1705, 1706, and 1707 are associated with the same time slot 1713, which may contain four different paging CORESETs. Each beam (eg, symbols S=32, 33, 34, 35 are transmitted in one direction, and symbols 36, 37, 38, 39 are transmitted in the other direction on different beams) associated with a CORESET Each of the CORESETs has four search spaces SS 1721-1724. The WTRU may find a paging search space based on its WTRU_ID (eg, SSp 1721, 1722, 1723, and/or 1724, depending on which SSBI 1704, 1705, 1706, or 1707 the WTRU is synchronized to) and CORESET, and based on the SS/s that the WTRU is synchronized to. PBCH block 1704, 1705, 1706 or 1707 finds its own PO. Paging time slot It may include 4 POs that are transmitted by FDM in each beam and in four beams.

In the above example, the paging DCI (eg, PDCCH) and the paging message (eg, PDSCH) may be in the same time slot. However, the PDCCH may schedule PDSCH (eg, time slot scheduling) at different time slots. The PO may include a pairing of paging DCIs and paging messages for the entire beam scan. In the case of a time slot schedule, the PPO may include a time slot-based schedule that is different from the paging time and the paging DCI in the same time slot and/or more time slots. In the example described herein, different common search spaces may be assigned to different groups of WTRUs for paging. In this case, the group common search space can be used for the destination FDM PO.

Exemplary procedures performed by the WTRU to determine the configuration of the PO of the FDM are described herein. According to this exemplary procedure, the WTRU may synchronize with the PSS/SSS and may receive the MIB from the PBCH. The WTRU may find a CORESET for the RMSI from the MIB and may perform blind decoding for the Type 0-PDCCH. The WTRU may receive SIB1 from the PDSCH pointed to by the Type 0-PDCCH. The WTRU may discover a paging configuration including a DRX cycle, a paging search space, and nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. The WTRU may calculate using the number of DRX cycles, WTRU_IDs, and/or FDM POs. . The WTRU may calculate the PO_id based on the number of DRX cycles, WTRU_IDs, and/or FDM POs. Using PO_id and/or nFDMp, the WTRU may calculate BWP_id and/or search space _id (SearchSpace_id). CORESET_id can be associated with SearchSpace_id. Therefore, using different CORESETs can be reflected in different SearchSpace_ids.

The WTRU may find one or more time slots or micro time slots (eg, for some or all of the beams) that it should monitor for SearchSpace_id and BWP_id. The SS/PBCH block and associated paging search space can be quasi-co-located. Thus, the WTRU can use the associated beam for each time slot. The paging search space can be a group common search space. If the actually transmitted SSB is different from the defined SSB, the association between the paging search spaces can be performed using the logical index or entity index (or SSBI) of the SS/PBCH block. The WTRU may use Resource Block 0 (RB0) of the Common Search Space (with the same searchSpace_id for different RB offsets for each WTRU group) and may use WTRU_ID to calculate the offset for each group. If the WTRU does not have an operation to complete, the WTRU may enter IDLE_MODE.

The WTRU wakes up in the calculated SFN time slot (or micro time slot) associated with the last recorded strongest beam. If the WTRU is configured to scan for a beam, the WTRU may wake up in the first beam and may scan all beams in a time slot associated with the PO for that WTRU. The WTRU may calculate using time slots or micro time slots (e.g., as described above). Using the search space definition for paging, the WTRU may find a paging CORESET in the pre-computed BWP_id. The WTRU may use the search space table to blindly decode the Type2-PDCCH using the P-RNTI. If multiple RNTIs are assigned from a paging RNTI (PG-RNTI) group, the WTRU may use the RNTI for its own group. The RNTI for the WTRU may be derived using the WTRU_ID or may be assigned to the WTRU using (e.g., WTRU-specific) RRC messaging. If the WTRU finds a Type2-PDCCH, the WTRU receives the PDSCH indicated by the PDCCH to determine if the WTRU is paged. If the WTRU is paged, the WTRU may establish a connection with the gNB. If the WTRU is not paging, the WTRU may revert to IDLE_MODE.

In the example of PO configuration for multiplexed pattern 1, mixed TDM and FDM can be used for different POs. The combination of any of the methods described above for TDM and FDM can be used for mixed TDM as well as FDM, and is completely flexible in scheduling PO for different users. By using mixed TDM and FDM, PO can be distributed in terms of time and frequency. The frequency at which the PO is monitored can depend on the DRX. The WTRU may calculate the SFN to be monitored for paging (e.g., as described above). Each beam in the PO can be associated with a different SS/PBCH block. A time offset in accordance with one or more time slots (or one or more micro time slots) can be applied to calculate the PO. The time offset may be pre-configured or may be based on the WTRU_ID.

Different POs may exist on all BWPs or may be multiplexed on the BWP. If different POs are multiplexed on different BWPs, the BWP to be monitored by the WTRU may be configured by the gNB or calculated by the WTRU and may depend on the WTRU_ID. In one example, if there are a total of 4 POs, then 2 POs can be FDM in one time slot, while the other 2 POs can be TDM in different time slots. Each BWP can contain 2 POs per slot. This distribution can be a function of the WTRU_ID.

In each BWP, POs can be assigned to different search spaces in different time slots. This search space can be associated with the same CORESET or a different CORESET. If the search space is associated with a different CORESET, the CORESET monitored by the WTRU may be predefined or based on the WTRU_ID. In an example, if there are 4 POs in the BWP, there may be 2 CORESETs on which the PO is multiplexed, and each CORESET can include 1 PO in two different time slots. This distribution of time slots and CORESET can be a function of the WTRU_ID.

If the search space is associated with the same CORESET, the search space that the WTRU is to monitor may be predefined or based on the WTRU_ID. In one example, if there are 4 POs in the BWP and there are two search spaces on which the PO is multiplexed, then each search space can include one PO in two different time slots. This distribution of time slots and search spaces can be a function of the WTRU_ID. Also, in multiple time slots, there may be multi-dimensional mapping of POs on different search spaces of different CORESETs present in different BWPs. Therefore, the group common search space can be used for FDM PO.

PO slot number A formula similar to RMSI can be used to calculate, but it is possible to include an offset. Thus, the time offset BWP_id, SearchSpace_id, and/or CORESET_id may be a function of the WTRU_ID. The time offset BWP_id, SearchSpace_id, and/or CORESET_id may also be a function of any one or more of the following parameters: the total number of POs; the total number of TDM POs (nTDMp); the number of FDM POs in the BWP (nFDMp_bwp); Number of FDM POs (nFDMp_coreset); number of FDM POs in the search space (nFDMp_ss); nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]; number of paging frames in the WTRU DRX cycle; and/or use in paging The number of sub-frames for paging. [2]

For each SSBI i, there may be a quasi-co-location location for paging. For PO, all i values (or the entire beam scan) can be included in the time slot number used to calculate the PO In the equation. An example of such a calculation is given in the following equation: Equation (9) If the number of SSBs actually transmitted is different, the logical index of the SSB can be associated with the time slot used for paging scanning.

In an example, the following parameters can be functions of PO_id, nTDMp, and/or nFDMp: , BWP_id and / or SearchSpace_id. in other words,[ , BWP_id, SearchSpace_id] = f(PO_id, nTDMp, nFDMp), where It may be a time slot in which paging occurs, BWP_id may be a BWP that discovers paging, and SearchSpace_id may be a search space in which paging DCI can be found. If the total number of TDM POs is nTDMp = 1, this may mean that all POs are transmitted in FDM in the same time slot. If the total number of TDM POs, nTDMp, is equal to the total number of POs, this may mean that all POs are transmitted in different time slots and are not FDM. In this case, the BWP, CORESET, and/or search space may be the same. The number of FDM POs nFDMp can be a function of (nFDMp_bwp, nFDMp_coreset, nFDMp_ss). If the number of FDM POs in the BWP is nFDMp_bwp=1, this may mean that the PO is not multiplexed on the BWP or the same PO is transmitted on the different BWPs configured. If the number of FDM POs in CORESET is nFDMp_coreset=1, this may mean that the PO is not multiplexed on CORESET. The PO's index (PO_id) can be calculated using the WTRU_ID and a modulo function (eg, PO_id = floor(WTRU_ID/N) mod Ns). In this case, the function f() may be a round robin distribution function or a complex hash function, and/or may be based on .

Exemplary procedures performed by the WTRU for determining PO configuration (which may be hybrid FDM and TDM) are described herein. According to this exemplary procedure, the WTRU may synchronize with the PSS/SSS and receive the MIB from the PBCH. The WTRU finds a CORESET for the RMSI from the MIB and can perform blind decoding for the TypeO-PDCCH. The WTRU may receive SIB1 from the PDSCH indicated by Type0-PDCCH. The WTRU may discover the paging configuration from SIB1, for example, including DRX cycle, paging search space, nTDMp, and/or nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. The WTRU may calculate using the number of DRX cycles, WTRU_IDs, and/or FDM POs. . The WTRU may calculate the PO_id based on the number of DRX cycles, WTRU_IDs, and/or FDM POs. Using PO_id, nFDMp, and/or nTDMp, the WTRU can calculate the time slot (or micro time slot) offset ( ), BWP_id and/or SearchSpace_id (and CORESET_id associated with SearchSpace_id). This time slot offset can depend on the SCS. The SS/PBCH block and associated paging search space may be quasi-co-located. Thus, the WTRU can use the associated beam for each time slot. If the actually transmitted SSB is different from the defined SSB, the association between the paging search spaces can be performed using the logical index of the SS/PBCH block, or the entity index (or SSBI). The paging search space can be a group common search space. The WTRU may use RB0 of the common search space (with the same searchSpace_id for different RB offsets for each group) and may use WTRU_ID to calculate the offset for each group. The WTRU may discover one or more time slots, one or more time slots or micro time slots (eg, for all beams) that should be used by it to monitor searchSpace_id and BWP_id. The WTRU may enter IDLE_MODE.

The WTRU may wake up in the calculated SFN time slot (or micro time slot) associated with the last recorded strongest beam. If the WTRU is configured to scan for beams, the WTRU may wake up in the first beam and may scan all beams in a time slot associated with the PO of the WTRU. The WTRU may use time slot or micro time slot calculations as described above. The WTRU can use the time slot offset of the PO or To find its time slot (or micro time slot). Using the paging search space definition, the WTRU may discover the paging CORESET in the pre-computed BWP_id in the previously discovered time slot and may use the search space table to blindly decode the Type2-PDCCH using the P-RNTI. If multiple RNTIs are assigned from a paging RNTI (PG-RNTI) group, the WTRU may use the RNTI for its own group. The RNTI may be derived using the WTRU_ID or may be assigned to the WTRU using WTRU-specific (eg, RRC) messaging. The WTRU may find a Type2-PDCCH that receives the PDSCH indicated by the PDCCH to determine if the WTRU is paged. If it is paged, it establishes a connection with the gNB. If the WTRU is paged, the WTRU may establish a connection with the gNB. If the WTRU is not paged, the WTRU may revert to IDLE_MODE.

In an example of a PO configuration for multiplexed pattern 1 as described above (using TDM, FDM, or hybrid TDM and FDM), the equation for RMSI CORESET can be used with the offset configured for each search space. . For example, the time slot number of the PO It can be calculated using the following equation: Equation (10) If the number of SSBs actually transmitted is different, the logical index of the SSB can be associated with the time slot used for paging scanning.

In addition, offset ,among them It can be defined as a PDCCH monitoring offset and can be configured as a search space for paging by the parameter monitoringSlotPeriodicityAndOffset . As mentioned above, the time slot in which the paging occurs = function(PO_id, nTDMp, nFDMp). in Medium, s can be used for The paging search space collection index, and p = 0, which is the index for the RMSI CORESET. If the time offset is based on the micro time slot, then The calculations can be similar.

In another example of a PO configuration for multiplexed pattern 1, a simple FDM can be used for the entire beam scan. For example, multiple FDM POs can be defined for individual beam scanning. In this case, the SS/PBCH block scan can be followed after the paging beam scan for all POs. Each SS/PBCH block can be associated with a time slot (or micro time slot) for paging beam scanning. If the number of SSBs actually transmitted is different, the logical index of the SSB can be associated with the time slot used for paging scanning. Multiple POs may be based on the WTRU_ID and may be FDM in different BWPs, different CORESETs, and/or different search spaces. The frequency at which the WTRU monitors the PO may depend on the DRX, and the SFN to be monitored by the WTRU for paging may be calculated by the WTRU. Based on the SSBI of the best SS/PBCH block, the WTRU may calculate an SS/PBCH block or other known reference time point (eg, 5 milliseconds or a half frame boundary (or a multiple of 5 milliseconds, eg, it may be via RMSI) The time slot (or micro time slot) of the PDCCH is configured to be offset. The time slot offset may be dependent on the SCS and may be reduced if the SCS is increased. The gNB may be configured or the WTRU may calculate the BWP based on the WTRU_ID, CORESET and / or search space.

In any of the examples of PO configuration for the multiplexed pattern 1 described above (TDM, FDM, hybrid TDM, and FDM, simple FDM across beam scanning), there is a possibility between the location for paging and the location of the SS/PBCH block. Conflicts and/or overlaps. In an exemplary scenario, when there is an overlap between the time slot and the scheduled slot, the gNB can transmit a page in the time slot after the scheduled slot. The slot offset may now be predefined, configured by the gNB based on rules, and/or calculated by the WTRU. In another exemplary scenario, the gNB can configure the CORESET such that it is in a different PRB than the SS/PBCH block. The PRB offset may be predetermined, configured by the gNB based on rules, and/or calculated by the WTRU. In another exemplary scenario, the WTRU may assume that no SS/PBCH block is transmitted in the resource element (RE) used to monitor the paging CORESET.

In the example of a multiplexed pattern ("Multiplex Pattern 2/3"), the PPO configuration would cause the paging CORESET to be FDM with the SSB. In an example, the multiplex pattern 2/3 can be used at frequencies greater than 6 GHz. As described above, a formula-based method of calculating BWP and/or CORESET and/or search space using WTRU_ID, nFDMp, N, Ns can also be used for multiplexed pattern 2/3, where RMSI and SSB are FDM.

The BWP monitored by the WTRU and the search space monitored by the WTRU may be a function of the PO index and/or the total number of FDM POs in each of the dimensions (e.g., BWP, CORESET, search space) described above. The CORESET associated with each search space can be included in the search space configuration and therefore does not have to be explicitly mentioned.

In this example, the ID of the BWP can be calculated as BWP_id = f (PO_id, nFDMp), and the search space ID can be calculated as SearchSpace_id = f (PO_id, nFDMp), where PO_id can be an index of the PO. The number of FDM POs can be calculated as nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. If the number of FDM POs in the BWP is nFDMp_bwp=1, then it is possible that the PO is not multiplexed on the BWP, or the PO is transmitted on a different BWP that is configured. If the number of FDM POs in CORESET is nFDMp_coreset=1, then it is possible that the PO is not multiplexed on CORESET. The PO's index (PO_id) can be calculated using the WTRU_ID and the modulo function, such as PO_id = floor(WTRU_ID/N) mod Ns. In this case, the function f() may be a round robin distribution function or a complex hash function, and/or may be based on .

Figure 18 is an exemplary multiplex pattern 3 for a PO configuration 1800 in which the paging CORESET and the SS/PBCH block are FDM. The time slot 1813 with SS/PBCH includes a CORESET for the beams associated with SSBI 1804 and 1805. Each of CORESET 1851 and 1852 can include 4 paging search spaces 1821-1824 (in PO 1841-1844). The paging messages 1831-1834 indicated by the paging DCI in CORESET 1851 and 1852 can be FDM with the SS/PBCH block (carrying the SSB with SSBI 1804 and 1805).

Figure 19 is an exemplary multiplex pattern 3 for PO configuration 1900 in which the paging CORESET is FDM with the SS/PBCH block. The time slot 1913 with SS/PBCH may include CORESETs 1951 and 1952 for beams associated with SSBI 1904 and 1905. Each of CORESET 1951 and 1952 can include 4 paging search spaces 1921-1924. The paging messages 1931-1934 indicated by the paging DCI may be in different time slots 1913+N. A time slot offset N (which may be located in the search space 1921-1924) may be indicated in the paging DCI. The example in Fig. 18 and Fig. 19 shows the multiplex pattern 3. In the multiplex pattern 2, the CORESET may exist in the OFDM symbol before the SS/PBCH, and/or the paging message may exist in the PDSCH that performs FDM with the SS/PBCH, and the multiplex pattern 2 may be similar to the multiplex pattern 3.

Exemplary procedures performed by the WTRU for determining PO configurations for multiplexed graphics 2/3 are described herein. According to this exemplary procedure, the WTRU may synchronize with the PSS/SSS and may receive the MIB from the PBCH. The WTRU may discover a CORESET for the RMSI from the MIB and may perform blind decoding on the Type0-PDCCH. The WTRU may receive SIB1 from the PDSCH indicated by Type0-PDCCH. The WTRU may find a paging configuration including a DRX cycle, a paging search space, and nFDMp = [nFDMp_bwp, nFDMp_coreset, nFDMp_ss]. The WTRU may calculate using the number of DRX cycles, WTRU_IDs, and/or FDM POs. . The WTRU may calculate the PO_id based on the number of DRX cycles, WTRU_IDs, and/or FDM POs. Using PO_id and/or nFDMp, the WTRU may calculate BWP_id and/or SearchSpace_id. CORESET_id can be associated with SearchSpace_id. Therefore, using a different CORESET may be reflected in a different SearchSpace_id.

The WTRU may use RB0 of the common search space (with the same searchSpace_id for different RB offsets for each group). The WTRU may discover one or more time slots, one or more time slots or micro time slots (eg, for all beams) in which searchSpace_id and BWP_id should be monitored. The SS/PBCH block and associated paging search space may be in the same time slot and may be co-located. If the actually transmitted SSB is different from the defined SSB, the paging search space can be FDM with the actually transmitted SSB. If the WTRU has no further operations, the WTRU may enter IDLE_MODE.

The WTRU may wake up in a time slot, a non-time slot (or a micro time slot) that is associated with the calculated SFN and associated with the last recorded strongest beam. If the WTRU is configured to scan for beams, the WTRU may wake up in the first beam and may scan all beams in the time slot associated with the PO of the WTRU. Using the search space definition for paging, the WTRU may find a paging CORESET in the pre-computed BWP_id. The WTRU may use the search space table to blindly decode the Type2-PDCCH using the P-RNTI. If multiple RNTIs are allocated from a paging RNTI (PG-RNTI) group, the WTRU may use the RNTI for its own group. The RNTI may be derived using the WTRU_ID or assigned to the WTRU using WTRU-specific (eg, RRC) messaging. If the WTRU finds a Type2-PDCCH, the WTRU receives the PDSCH indicated by the PDCCH to determine if the WTRU is paged. If the WTRU is paged, the WTRU may establish a connection with the gNB. If the WTRU is not paged, the WTRU may revert to IDLE_MODE.

In one example, the paging DCI can be used without a paging message. For example, a short page message can be compressed into a paging DCI. Examples of short paging messages may include, but are not limited to, any of the following: paging messages for a single WTRU; system information updates or modifications; and/or for public safety (eg, public alert system (PWS), commercial action alerts) Emergency information or instructions for the System (CMAS), Earthquake and Tsunami Warning System (ETWS). The DCI format can be defined for paging based DCI-based paging without paging PDSCH (ie, no separate paging messages). The DCI format can have a longer format to accommodate paging messages. The DCI format may include, but is not limited to, any of the following information: control information fields; and/or message fields. The control information field may include, but is not limited to, any of the following information: a resource configuration for the paging message; and/or a flag for indicating the paging message or system information. The flag may be a field of X bits used to identify the characteristics of the short message (eg, X may be a small number, say 2 or 3). The flag can be a bitmap of Y bits (eg, Y can be 2 ^X , such as 4 or 8 bits). The message field can include a paging message. If the control information field indicates that it is a paging message for a single WTRU, the message field may include the WTRU_ID being paged (eg, a compressed form of IMSI or WTRU_ID). The message field can include system information (SI) and/or change notifications. The SI can include emergency system information or short system information messages. The SI change notification can override the paging message. The DCI can be encoded with a Reed Muller (RM) code or a polarization code. The DCI can be encoded in accordance with the payload using two different coding schemes. For example, system messages can be encoded in RM code. A single user page can be encoded with a polarization code or RM code with a predefined code rate.

The SSB and paging DCI/Paging messages can be associated. The NR can have a long DRX cycle. A fast method for searching for the best gNB-TX/WTRU-RX beam pair (e.g., having the highest SNR at the receiver) may use a synchronization signal (e.g., PSS, SSS) in the SSB. If the gNB ensures that the antennas used to send the paging (paging DCI and/or paging messages) and the synchronization signal are the same (eg, quasi-co-located), the WTRU may use the same TX/RX beam pair to receive as received SSB Paging DCI. The use of TX/RX beam pairs can be implicitly or explicitly assumed or indicated (eg, OSI or RMSI). The predefined one or more time-frequency association rules between the SSB and the paging may cause the WTRU to quickly check the location of the paging DCI/Paging message. In the following description, the QCL with the paging message may imply that the DMRS of the NR-PDSCH for the paging message is quasi-co-located with the paging DCI, and/or the DMRS of the NR-PDCCH is transmitted in the CORESET for paging the DCI. In some cases, this QCL assumption may be invalid or inaccurate.

An exemplary method can be used for association of SSBs and paging DCI/messages. The paging DCI and/or paging message can be co-located with the SSB. Exemplary modes may include a preset mode (QCL mode) and a non-preset mode (non-QCL mode). A flag (eg, in RMSI or OSI) can be used to indicate which mode is being used (preset mode or non-preset mode), and/or implicit rules regarding the mode are likely to be known on the WTRU.

In the default mode (QCL mode), the WTRU may assume that the paging DCI and/or paging message is co-located with the detected SSB based on the association rules of the SSB and the paging DCI/message. In the non-preset mode (non-QCL mode), if the paging DCI and/or paging message is not co-located with the detected SSB, the WTRU will receive an indication. If the SSB and paging DCI and/or messages are not closed in time, then QCL will not be assumed. For example, the gNB can use different beams or the same beam with different beamwidths between the SSB and the paging DCI/message.

The time threshold can be used to correlate the SSB with the paging DCI/message. In an example, let T be the time between the SSB and the PO detected for a given WTRU. If T is less than the time threshold, then the QCL between the SSB and the paging DCI/message can be assumed. Otherwise the QCL will not be assumed. The time threshold can be used in combination with the QCL flag. For example, if T is less than the time threshold, QCL can be assumed, and if the flag is set to QCL (eg, setting a bit to "1"), then QCL can be assumed, otherwise QCL will not be assumed. A threshold based on Reference Signal Received Power (RSRP) may also be used, and the threshold may be absolute or relative. For example, the absolute threshold can be set to a predefined fixed amount. The relative threshold (eg, relative to the previously selected SSB) may depend on any one or more of the following exemplary conditions: WTRU mobility; Doppler; azimuth; and/or relative RSRP. A function can be used to calculate the threshold.

The QCL hypothesis can be applied to a subset of the paging DCI/message and a fixed method or indication method can be used for the subset. In the fixed method, the QCL can be applied to a fixed subset of paging DCI/messages. In a dynamic/semi-static approach, the QCL can be applied to a subset of paging DCI/messages that can be indicated (eg, by gNB). Within the subset, the WTRU may assume that the paging DCI and/or paging message is co-located with the detected SSB based on the association rules of the SSB and paging DCI/message.

The paging DCI and paging messages and SSBs can be spatially QCL (eg analog beam scanning for narrow beams). In other words, the PDCCH and the DMRS for the PDCCH containing the paging DCI may be spatially co-located with the SSB (eg, the QCL type A+D defined in the standard, such that the QCL type may depend on the Doppler shift, both Buller extensions, average delays, delay spreads, or other parameters). Similarly, the DMRS for the PDSCH containing the paging message may be spatially co-located with the SSB (eg, QCL type A+D). In another example, the paging channel and the SSB can be non-spatially QCL (eg, for omnidirectional or wide beam transmission). In this case, the paging DCI and the paging message and the SSB may be spatially QCL (eg, QCL Type A) in terms of average delay, Doppler shift, delay spread, and/or Doppler spread estimation.

Association rules can be used for associations between SSBs and paging DCI/messages. There may be an association between the SSB and the paging DCI/message subset. The WTRU may use any one or more of the following examples for CL association: association of QCL with SS/PBCH block; one-to-one association between one SS/PBCH block and one paging DCI/message; one SS/PBCH a one-to-many association between a block and multiple paging DCI/messages (eg, a subset of paging messages or all paging messages); and/or a many-to-one association between multiple SS/PBCH blocks and a paging DCI/message ( For example, a subset of SSB). The QCL association with RMSI can be defined. The RMSI block index can be defined to be similar to the SS block index. The RMSI block index (RMSI ID) can be included in the RMSI and can be implicit or explicit. In the case where the RMSI can be associated with an SS block, it can be assumed that the RMSI block index (RMSI ID) is the same as the SSBI. There may be a one-to-one association between an RMSI block and a paging DCI/message. There may be a one-to-many association between one RMSI block and multiple paging DCI/messages (a subset of paging messages). There may be many-to-one associations between multiple RMSI blocks and one paging DCI/message (SSB subset).

The association of QCL with OSI can be defined. The OSI block index can be defined to be similar to the SS block index. The OSI Block Index (OSI ID) may be included in the OSI and may be implicit or explicit. In the case where the OSI can be associated with an SS block, then it can be assumed that the OSI block index (OSI ID) is the same as the SSBI. There may be a one-to-one association between an OSI block and a paging DCI/message. There may be a one-to-many association between an OSI block and multiple paging DCI/messages (eg, a paging message subset or all paging messages). There may be a many-to-one association between multiple OSI blocks and one paging DCI/message (eg, an SSB subset or all SSBs). For wideband component carriers (CC), the QCL association can span the BWP. A many-to-one association may involve different BWP SSBs associated with paging DCI/messages. For a one-to-many association, one BWP SSB can be associated with a different paging DCI/message. For a one-to-one association, a BWP SSB can be associated with a paging DCI/message. The QCL and WTRU behavior for paging message associations may be based on any one or more of the following exemplary criteria: association of QCL with paging DCI; one-to-one association between paging DCI and paging messages; QCL and SS Association of /PBCH blocks; association of QCL with RMSI; and/or association of QCL with OSI.

The WTRU may be preset to assume QCL based on the SS/PBCH block, RMSI, and/or OSI. The WTRU may use a different QCL or override the preset QCL based on an explicit or implicit approach. According to the explicit approach, associations can be configured by the network. The WTRU may be provided with an indication of which association to follow (eg, from gNB): SS/PBCH, RMSI, or OSI association. The bit map can be used to indicate the association of the paging DCI/message with any of the SS/PBCH, RMSI or OSI. This bit map can be included in the RMSI or OSI. This bit map can be transmitted in WTRU-specific (eg, RRC) messaging. In accordance with the implicit approach, the association may be assumed based on the shortest time span between the WTRU's calculated PPO for the WTRU and the detected or decoded SS/PBCH block, RMSI, or OSI. P is the number of the PO in the DRX cycle, and the PO can be associated with the SSB actually transmitted during the SS burst setup period (by SSB and paging DCI/message resource association rules). P may be greater than, equal to, or less than the number of SSBs actually transmitted in the SS burst set.

Paging delivery can be based on time slots and/or based on non-time slots. The combination of time slot and non-time slot configurations for PDCCH and PDSCH results in either or more of the following options. For example, time slot based paging may include a time slot based paging DCI followed by a time slot based paging message. In this case, the beam scan can be time slot based. For each beam, the paging DCI and paging messages can be in the same time slot. The paging DCI and paging messages may be multiplexed with other symbols that may be scanned by the beam, including but not limited to data, control, SSB, RMSI, and/or OSI. Intertemporal slot scheduling can be used. In the case of a time slot schedule, the paging DCI may point to a PRB for a paging message in a time slot that is different from the time slot of the paging DCI. The offset between time slots can be known or can be indicated (eg, by gNB). Each time slot can scan one or more beams in different directions, or the beam can be repeated (eg, in the case of paging DCI and paging messages being repeated in different time slots in different time slots).

The non-time slot based paging may include a non-time slot based paging DCI followed by a non-time slot based paging message. Using non-time slot based paging can reduce the scan overhead caused by time slots. In this configuration, beam scanning can be done based on non-time slots. The non-time slot symbol may contain a paging CORESET and/or paging message. The non-time slot symbols may be multiplexed with other symbols that may be scheduled and scanned by the beam, including but not limited to data and/or control information. In an example, after beam scanning is performed on the non-time slot for paging DCI, beam scanning may be performed on the non-time slot for paging messages. In different POs, the payload of messages (such as paging, control data) can be different. The number of OFDM symbols used for paging messages may be different in different POs. To facilitate non-time slot based paging, a Time Slot Format Indicator (SFI) can be used. In an example, an intertemporal slot schedule can be performed.

In an example of a hybrid paging method ("hybrid paging I"), a time slot based paging message may be followed by a non-time slot based paging DCI. In this configuration, the paging DCI scan can be performed quickly using the non-time slot format. A beam scan based on a time slot carrying a paging message can be performed after the DCI scan is performed. The paging message can be multiplexed with other information that can be scanned by the beam (eg, data, control, SSB, RMSI, and/or OSI). In another example of a hybrid paging method ("Mixed Page II"), a time slot based paging DCI may be followed by a non-time slot based paging message. In this configuration, the paging DCI scan can be multiplexed with other information that can be scanned by the beam (eg, data, control, SSB, RMSI, and/or OSI). A fast beam scan based on a non-time slot carrying a paging message may be performed after the DCI scan is performed. In accordance with this hybrid paging method, the paging DCI can be close to the SSB or any other beam scanning symbol and can therefore be co-located with the SSB or other beam scanning symbols.

In the exemplary method described above, the WTRU may be configured to use a paging of a simultaneous slot schedule or a time slot schedule. The WTRU may receive indications or follow pre-defined rules to accommodate dynamic changes based on time slot or non-time slot scheduling and/or transport formats. The dynamic change may include, but is not limited to, changing the monitored starting OFDM symbol for paging DCI, determining the number of OFDM symbols (the distance between the paging DCI and the paging message), and/or determining the paging message. The number of OFDM symbols.

Paging delivery can be based on non-time slots. For example, the PDSCH can be based on non-time slot. For paging PDSCH, K OFDM symbol durations (eg, K = 1, 2, 4, or 7) may be used. Different options for indicating the format of the non-time slot based PDSCH are available. For example, a dominant indication for a non-time slot based format can be used. For explicit indications, the PO size may vary based on the use of different time slot sizes, which in turn may depend on the number of users (WTRUs) that are paged together in the PO. A PO that uses beam scanning (eg, with 2, 4, 7 symbols) can be used for different numbers of users that are simultaneously paged. The number of symbols can be indicated in the paging DCI. Beam scanning for paging DCI can be performed before scanning the paging message. Beam scanning can occupy one time slot or multiple time slots depending on the number of beams. The WTRU may be configured to monitor the time slot occupying the paging DCI for each WTRU's own PO (and the beam with the QCL with the SSB). Figure 20 is a communication diagram of an exemplary PO configuration 2000 including PO 2001 and 2002. In Figure 20, PO 2002 includes paging messages for a larger number of users (WTRUs) than PO 2001, thus including more OFDM symbols for paging messages. In Fig. 20, the paging DCI is transmitted in four beams, and the paging message (PM) is transmitted in four beams, and therefore, the paging DCI and PM are in separate beam scanning. Each of PO 2001 and 2002 is used to page four groups (WTRUs).

The DCI can be part of a non-time slot paging message. Figure 21 is a communication diagram of an exemplary PO configuration 2100 including POs 2101 and 2102. The example of Figure 21 shows POs of different sizes with self-contained paging DCI (p-DCI) in non-time slots (PO 2102 has a larger bandwidth than PO 2101). In Figure 21, the paging DCI is transmitted in four beams, and the paging message (PM) is transmitted in the same beam scan. The paging message (PM) can be rate matched around the paging DCI. The format used for paging can be indicated in SFI. The information indicated in the paging DCI may include any one or more of the following indications: an indication of a time slot based or non-time slot based paging PDSCH; if the non-time slot based paging is indicated by a non-time slot size An indication of a simultaneous or inter-slot scheduling for one or more paging messages; if the paging message indicates an indication of a time offset across the time slot schedule (eg, in an OFDM symbol, a micro time slot, or And (or time slot aspect); and/or a flag in the paging schedule DCI for indicating whether there is a corresponding paging PDSCH.

In another example, the PDCCH may be based on non-time slot. Non-time slot based paging delivery may enable faster and/or more flexible paging message delivery (eg, in beam scanning mode). If non-time slot based paging PDSCH transmission is supported, but non-time slot based paging PDCCH transmission is not supported, then it would be meaningless. The WTRU may monitor a non-time slot PDCCH for the PO that may be configured by the paging CORESET (eg, non-time slot based PDCCH transmission if the PDCCH monitoring the PO may be in the middle of the time slot). In an example, the non-time slot based PDSCH transmission may have 2, 4 or 7 OFDM symbol durations. In this case, from a PDCCH perspective, non-time slot based transmission/scheduling can be associated with a CORESET monitoring period of less than one time slot. The non-time slot based PDCCH transmission can support 1, 2, 4, 7 OFDM symbol durations. In order to reduce the beam scanning latency, a smaller number of OFDM symbols can be supported in each non-time slot (eg, for a PDCCH-based paging without a PDSCH, one symbol can be supported). The PDCCH may be transmitted for paging DCI, and the PDSCH for paging messages may be transmitted in the same OFDM symbol such that the paging DCI and paging messages may be transmitted in the same beam in the scan.

In an example, for a time slot schedule, the PDCCH for paging DCI may be scanned prior to scanning the paging message. In order to implement an efficient scanning mechanism for paging DCI/message delivery, non-time slot based scheduling may be supported for paging PDCCH. For PDCCHs used for paging DCI, the number of OFDM symbols can be reduced to one. In an example, for a non-time slot based PDCCH for a PDSCH of symbols [2, 4, 7], the [X, Y, Z] OFDM symbol duration for the paging CORESET (refer to the size of the microslot) ) can be fixed. Different values of [X, Y, Z] can be supported (for example, [X, Y, Z] = [1, 1, 2] or [1, 2, 2]).

Page delivery can be based on a time slot schedule. After detecting the paging DCI, the WTRU may use any one or more of the following exemplary rules to decode the paging message. According to an exemplary rule, a WTRU may decode a paging message after receiving any one or more of the following elements: P OFDM symbols; P micro time slots (in a non-time slot based system); P time Slot; P sub-frames; and/or P frames. For example, the WTRU may decode the paging message after P1 non-time slots and P2 OFDM symbols. In an exemplary scenario, P may be fixed and may be known to the WTRU. For example, P may be associated with a number of beams for the PDCCH and the PDSCH and/or a slot/non-time slot format. In another example, a predefined table can be used to find N. In another exemplary scenario, P may be indicated to the WTRU. This can be performed explicitly by paging the scheduling DCI. For example, the paging schedule DCI can carry an offset of N, which allows for greater flexibility with a slight overhead. The paging schedule DCI may include units of P (eg, OFDM symbols, micro time slots, time slots, subframes, frames, or a combination thereof). P may be implicitly calculated by the WTRU using any one or more of the following exemplary parameters: number of beams to be scanned; PDCCH based on time slot or non-time slot; PDSCH based on time slot or time slot; And/or a fixed or indicated offset between the PDCCH scan end for paging DCI and the PDSCH scan for paging messages.

The program can use PO duration or interval. The PO may be composed of P OFDM symbols, time slots, non-time slots, subframes, or frames (or a combination thereof). The duration or interval of the PO can be used to energize the TX and RX beams with the following: TX beam scanning; TX beam repetition; RX beam scanning; and/or RX beam repetition.

On the WTRU, the number N of elements in the PO may be determined by one or more of the following exemplary methods: based on the actual transmitted SSB (eg, it may be indicated in RMSI or RRC); based on the range that can be determined by the frequency range Maximum number of SSBs; based on indication or configuration; based on scan configuration information (eg, M1 TX beam scan, M2 RX beam scan); and/or based on repeated configuration information (eg K1 TX beam repeat, K2 RX beam repeat) . The indicator P for the number of elements in the PO may indicate any one or more of the following exemplary information: beam scan mode of operation; beam repeat mode of operation; or hybrid beam scan/repetition mode of operation.

Some methods can be used for advanced paging delivery. The paging message may be scheduled by the paging DCI carried in the NR-PDCCH and may be transmitted in the associated NR-PDSCH. The paging delivery system can be designed to scan all WTRUs for paging DPI and paging messages in all directions. It would be highly desirable if the WTRU is properly woken up and the time at which the WTRU monitors one or more paging group indicators (which may reduce the WTRU battery power consumption). In order to achieve finer WTRU packet granularity, a large number of beams can be used for scanning to discover paging.

Advanced paging delivery can be implemented with a second level of grouping. In this case, paging delivery (eg, basic paging) can follow the paging message. In this case, the WTRU may be grouped without feedback or WTRU beam reporting. The WTRU group can be paged simultaneously (e.g., using a paging group indicator). The bitmap of the group may be transmitted in a paging group indicator DCI masked by the P-RNTI. The paging group indicator may indicate that the WTRU in the indicated group of WTRUs performs any one or more of the following exemplary functions: receiving a paging schedule DCI (according to a basic paging); and/or transmitting a feedback message (eg dedicated PRACH preamble (advanced paging with feedback)). This advanced paging method can reduce the WTRU's wake-up process and can save power for WTRUs that are not part of the group.

Advanced paging delivery can include feedback. In this method, feedback from the WTRU may be added to the advanced paging delivery method as described above. For example, the feedback can include a paging DCI and/or a paging group indicator. The paging group indicator can be sent or can be part of the paging DCI masked by the P-RNTI or paging message. The paging DCI and/or paging group indicator can be sent as a bitmap of the group. In an example, the paging indication can trigger a WTRU beam report (if supported). For example, the paging indication can be in a paging DCI or a non-scheduled physical channel. In another example, the paging group indicator may indicate whether the WTRU needs to transmit a dedicated PRACH preamble. A WTRU that is part of a group may send a RACH as a feedback, and the feedback may be received by the gNB in one or more particular beams, indicating the presence of the WTRU in the direction of the one or more beams. The paging DCI may be transmitted in the DL direction corresponding to the received dedicated PRACH preamble, followed by the paging message. The mechanism for dedicated beam recovery requests and/or on-demand OSI requests can be reused by transmitting a dedicated PRACH implemented DL beam report. Other enhancements may include: dedicated RACH resources for paging responses. Different RACH preambles can be defined for each group (K groups). The overlay code defined for the preamble can be different. The overlay code may include, but is not limited to, an M sequence, an orthogonal cover code (OCC), and/or a sinusoidal waveform. The RACH preamble may be assigned with a WTRU-specific (e.g., RRC) messaging process. The gNB can change the packet based on feedback for advanced paging. Such packet modification can be signaled by WTRU-specific (e.g., RRC) messaging.

BWP can be used for feedback in advanced paging. In an example, UL BWP k1 can be linked to DL BWP k2. If the WTRU receives a paging indication on DL BWP k2, then in a preset case, the WTRU may use UL BWP k1 to transmit feedback. K1 may be the same as k2 or may be different. Other configurations for BWP links can also be used for paging.

Different configurations can be used for BWP assignments and/or BWP links. In the same configuration, k1 = k2. The WTRU may use the same BWP as the DL-BWP that the WTRU receives its paging indication for uplinking. In a one-to-one mapping configuration, one DL BWP can be joined to exactly one UL BWP. The WTRU may be configured to have and may receive a paging indication on DL BWP k and may be configured with UL BWP k1 = f(k2), where f(k) is a unique function. This function f() can be known to the WTRU. Thus, the WTRU may use the UL-BWP for feedback, which may be linked to the DL BWP that the WTRU receives the paging indication. In a one-to-many mapping configuration, one DL BWP may link multiple UL BWPs; that is, two WTRUs may be configured such that DL BWP k2 may be configured to have any UL BWP (for example, for WTRUl, K2 = f1 (k1), and for WTRU2, k2 = f2 (k1)). For example, from a system perspective, if one DL BWP is available for two different WTRUs to receive a paging indication, the DL BWP can be mapped to two UL BWPs that are available to the WTRU to provide beam information feedback. In this case, the function f() may be based on a modulo function and/or may depend on the WTRU_ID and/or the paging group ID. For beam feedback for paging, different formats can be used (eg, license-free, license-based uplink or PRACH).

Different uplink formats can be used for BWP-based feedback for advanced paging. In one example, an unlicensed winding can be used for this feedback. If the WTRU uses an unlicensed uplink, the WTRU will have pre-configured resources in the pre-configured BWP. In another example, a license-based uplink can be used for this feedback. If the license-based uplink is used for feedback, then if the WTRU wants to dynamically switch BWP and schedule feedback in different BWPs, the gNB can use a longer DCI format (similar to DCI format 0_1 defined in the standard, The format includes the way to dynamically switch the BWP) to schedule the rollup for this feedback. The gNB may reserve multiple orthogonal time/frequency/BWP resources, and the WTRU may select resources from the set of gNB reservations. This resource selection performed by the WTRU may be based on the WTRU_ID. In order to reduce the overhead of DCI (or achieve a better bit rate), you can use the BWP link and / or the shorter DCI format (similar to the DCI format 0_0 defined in the standard, without the BWP indication) to schedule the winding, Give feedback. PRACH resources can be used for this feedback. In advanced paging, if the WTRU uses the resources configured for PRACH for feedback, the BWP link may identify the UL-BWP to transmit RACH resources dedicated to beam feedback.

An example of a paging feedback behavior of a WTRU for beam reporting is described herein. The WTRU may provide feedback for beam reporting. If a BWP connection for UL and DL is used for paging, the WTRU behavior may include any of the following exemplary operations. The WTRU may pre-compute or check the configured BWP for paging DPI. If the BWP is the same as the currently active BWP, the WTRU may receive the paging DCI. Otherwise, the WTRU may switch to the DL BWP for paging DCI. The WTRU may decode the paging DCI and may check if the WTRU is part of the group being paged. If the WTRU is part of a group being paged (that is, the WTRU is paged), advanced paging can be enabled and feedback for the beam can 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 a one-to-one configuration, 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-BWPs, the WTRU may use a predefined algorithm to determine the UL BWP. For example, the UL-BWP can be determined using a modulo function based on the 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 time slot of the scheduled resource. Therefore, the WTRU can transmit beam feedback.

The basic paging process and the advanced paging with feedback can be combined, and the gNB can switch between the basic paging and the advanced paging with feedback, and the two options can be configured based on the scenario and/or deployment. For combined basic and advanced paging, the basic or advanced paging can be indicated, so triggers based on feedback requirements can be enabled or disabled. For example, an indication of a basic or advanced paging can be included in the paging DCI, RMSI, and/or OSI.

For the N groups and the paging groups of the K subgroups, the modulo function can be used to determine. Grouping users (WTRUs) based on location or feedback can be used. However, the second level of packets (eg based on IMSI) does not add a lot of changes. The second packet can be based on another constant K (this constant can also use a modulo operation similar to IMSI). K can be the total number of groups supported that can be paged in the same PO. Different methods for indicating a group are available (eg, bit map, group ID mix). User grouping can reduce WTRU complexity and ambiguity (eg, if a compressed WTRU_ID is used for the paging message). Different groups of paging messages can be FDM or TDM in the same or different time slots or micro time slots.

The paging group indicator can be used. In order to support advanced paging methods, it may be necessary to have finer-grained packets. Finer-grained packets can be indicated by indicators. Packet decisions can be made at higher layers (eg, MAC, RLC, RRC) based on location or other parameters. Multiple groups can be paged in the same PO. Thus, the paging DCI can include an indication of which groups are being paged, and for example, it can indicate that one group is being paged. For example, the paging group indicator can take the form of a bitmap of bits transmitted in the paging DCI (CRC masked by the P-RNTI), the paging message, or any channel or signal. For example, a group bit map (K bit bitmap) can be used in the paging DCI as a paging group indicator. If any of the WTRUs from the group are paged, the bit corresponding to the group may be set in the bit map (eg, set to "1"), otherwise the corresponding bit may be reset (eg, reset to " 0”). In another example, the group ID can be used as a paging group indicator. Different group IDs may be aggregated and transmitted in the paging DCI to indicate that the WTRUs from different groups are being paged. Each group can be represented by a group ID (eg ranging from 0 to K-1). The paging DCI may include the number of groups being paged and/or its group ID.

In an example, a hybrid design for paging group identifiers can be used. In the hybrid approach, a group bit map and a WTRU group bit map can be sent in the paging DCI. This method can provide a finer resolution granularity of the WTRU being paged. The WTRU may be provided with its own group and its location in the bitmap, such that additional WTRU-specific messaging may be used. Multiple P-RNTIs or PG-RNTIs may be used for paging group indicators. Different groups may have different P-RNTIs instead of a single P-RNTI value (PG-RNTI) in LTE. The PG-RNTI may be a sequential or non-sequential RNTI range reserved for different groups being paged. In this case, only one group can use a DCI to page. The CRC of the paging DCI can be masked with the PG-RNTI of the group being paged.

A paging-specific group common PDCCH (P-GC-PDCCH) may be used for the paging group indicator. Similar to the GC-PDCCH used to indicate SFI, the P-GC-PDCCH may indicate a particular time slot format for paging. The P-GC-PDCCH may be located in a common search space that can be monitored by any or all of the WTRUs. The P-GC-PDCCH can be scanned on all beams. The P-GC-PDCCH may be transmitted at the beginning of the time slot for each PO to indicate a symbol associated with the location of the paging message in the time slot or non-time slot transmission. The P-GC-PDCCH may have a paging DCI with a paging group indication. The P-GC-PDCCH may include a bitmap of symbols having symbols that are observed for paging in subsequent slots. The P-GC-PDCCH may be encoded and transmitted in a control channel similar to the GC-PDCCH. The CRC may be masked with a specific number (eg, P-RNTI) or range (eg, PG-RNTI).

The paging-specific SFI can be used to page the group indicator. An entry for the SFI table for paging may be added to the GC-PDCCH indicating the slot format of the paging. These entries can be used as paging schedule information. The WTRU may use an index decoded from the GC-PDCCH to identify one or more paging message locations. The entries of the SFI table can be used to indicate the non-time slot format of multiple time slots for paging. Any of the above methods can be used to identify the group that is using the paging slot format. The GC-PDCCH can be used to dynamically modify the number of symbols used for non-time slots for paging DCI/messages.

While the solutions described herein take into account LTE, LTE-A, Novel Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to such scenarios and are equally applicable to other wireless systems.

Although features and elements of a particular combination are described above, those of ordinary skill in the art will recognize that each feature can be used alone or in any combination with other features and elements. Moreover, the methods described herein can be implemented in a computer program, software or firmware incorporated into a computer readable medium for use by a computer or processor. Examples of computer readable media include electrical signals (transmitted via wired or wireless connections) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor storage devices, magnetic media (eg internal hard drives) And removable magnetic discs), magneto-optical media, and optical media (such as CD-ROM discs and digital versatile discs (DVD)). A processor associated with the software can be used to implement a radio frequency transceiver for use at a WTRU, UE, terminal, base station, RNC, or any computer host.

100‧‧‧Communication system

102, 102a, 102b, 102c, 102d‧ ‧ ‧ wireless transmit / receive unit (WTRU)

104, 113‧‧‧ Radio Access Network (RAN)

106, 115‧‧‧ exemplary core network (CN)

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧Transmission/receiving components

124‧‧‧Speaker/Microphone

126‧‧‧Keypad

128‧‧‧Display/Touchpad

130‧‧‧ Non-removable memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧Other peripheral equipment

160a, 160b, 160c‧‧‧e Node B

162‧‧‧Action Management Entity (MME)

164‧‧‧Service Gateway (SGW)

180a, 180b, 180c‧‧‧ gNB

182a, 182b‧‧‧Action Management Function (AMF)

184a, 184b‧‧‧ User Plane Function (UPF)

183a, 183b‧‧‧Dialog Management Function (SMF)

185a, 185b‧‧‧ Data Network (DN)

200, 400‧‧‧ slot format

201, 203‧‧ beam

208‧‧‧Synchronization Signal Block (SSB)

210, 218, 404, 408‧‧‧ Physical Broadcast Channel (PBCH)

204, 206, 212, 214‧‧ ‧ paging underline control information (DCI)

402‧‧‧Primary Synchronization Signal (PSS)

406‧‧‧Secondary Synchronization Signal (SSS)

CORESET‧‧‧Control Resource Collection

PMT‧‧‧ paging multiplex type

PO‧‧‧ paging time

RMSI‧‧‧Remaining minimum system information

SCS‧‧‧Subcarrier spacing

SSB‧‧‧ sync signal block

A more detailed understanding can be obtained from the following description taken in conjunction with the accompanying drawings, wherein the same reference numerals are used to refer to the same elements, and wherein: FIG. 1A is a diagram showing that one or System diagram of an exemplary communication system of various embodiments; FIG. 1B is a diagram showing an exemplary wireless transmit/receive unit (WTRU) system that can be used within the communication system shown in FIG. 1A, in accordance with an embodiment. 1C is a system diagram showing an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) that can be used within the communication system shown in FIG. 1A, in accordance with an embodiment; 1D is a system diagram showing another exemplary RAN and another exemplary CN that can be used in the communication system shown in FIG. 1A according to an embodiment; FIG. 2 is a diagram including frequency division multiplexing (FDM) paging downlink control information (DCI) and block diagram of the exemplary time slot format of the synchronization signal block (SSB); Figure 3 is a block diagram of an exemplary time slot format including the paging DCI of the FDM and the SSB Figure 4 is included with SSB Block diagram of another exemplary time slot format for paging time division multiplexing (TDM) paging time; Figure 5 is a block diagram of another exemplary time slot format including DCI for TDM with SSB and PO Figure 6 is a block diagram of another exemplary time slot format including DCI and PO for frequency hopping with SSB; Figure 7 is a resource format for exemplary paging schedule, where PO is by size Defined for scanning of four beams of two-symbol micro-time slots; Figure 8 is a resource format for exemplary paging scheduling, where PO is passed by having two orthogonal frequency division multiplexing (OFDM) The scan of the four beams of the symbol's micro-slot format is defined; Figure 9 is a resource format for an exemplary paging schedule in which POs are scanned together; Figure 10 is for exemplary paging schedules Resource format; Figure 11 is a flowchart of an exemplary paging beam selection process; Figure 12 is a message delivery diagram of an exemplary paging multiplex format during PO; Figure 13 is an exemplary paging multiplex format message during PO Transfer diagram; Figure 14 is for PO assignment An exemplary multiplex pattern 1, in which a paging control resource set (CORESET) and a sync signal/physical broadcast channel (SS/PBCH) block are TDM; FIG. 15 is another exemplary multiplex for PO configuration Figure 1, where the paging CORESET and the SS/PBCH block are TDM; Figure 16 is another exemplary multiplex pattern 1 for PO configuration, where the paging CORESET and the SS/PBCH block are TDM; Figure 17 is for the PO Another exemplary multiplex pattern 1 configured, wherein the paging CORESET and the SS/PBCH block are TDM; FIG. 18 is an exemplary multiplex pattern 3 for PO configuration, wherein the paging CORESET and the SS/PBCH block are FDM; Figure 19 is an exemplary multiplex pattern 3 for PO configuration, where the paging CORESET and SS/PBCH blocks are FDM; Figure 20 is a diagram of an exemplary PO configuration; and Figure 21 is a diagram of an exemplary PO configuration. .

Claims (20)

A wireless transmit/receive unit (WTRU) configured to support multi-beam communication and perform paging monitoring, the WTRU comprising: a receiver configured to receive a configuration for enhanced paging; a processor configured to Determining a first subcarrier spacing (SCS) for a synchronization signal block (SSB) and a second SCS for a paging reception; determining a paging multiplex type based on the first SCS and the second SCS (PMT), wherein in the case where the first SCS and the second SCS are different, the PMT is determined to be a first type, and in the case where the first SCS and the second SCS are the same, the PMT is Determining to be a second type; determining a paging control resource set (CORESET), a paging message, and a beam, time, and frequency relationship between the SSBs based on the determined PMT; and the receiver is configured to be based on The determined beam, time, and frequency relationship is used to monitor the PO in one or more beams of a paging occasion (PO) for the paging message. The WTRU as claimed in claim 1, wherein in the case where the PMT is determined to be the first type, the beam, time, and frequency relationship includes: the paging CORESET and the paging message perform time division multiplexing ( TDM), the paging message is time aligned in a same time slot as the SSB, and the paging message is frequency division multiplexed (FDM) with the SSB. The WTRU as claimed in claim 2, wherein the paging CORESET uses a repeating beam to perform TDM with the paging message, resulting in two transmissions per beam of the PO. The WTRU as claimed in claim 1, wherein in the case where the PMT is determined to be the second type, the beam, time, and frequency relationship includes: the paging CORESET and the paging message perform time division multiplexing ( TDM), the paging CORESET, and the paging message are time aligned in a same time slot as the SSB, and the paging CORESET and the paging message are frequency division multiplexed (FDM) with the SSB. The WTRU as claimed in claim 4, wherein the paging CORESET performs TDM with the paging message without using a repeating beam, resulting in one transmission per beam of the PO. The WTRU as claimed in claim 1, wherein: the receiver is further configured to monitor the PO for a paging downlink control information (DCI), wherein the paging DCI includes a schedule information about the paging message. The WTRU of claim 1, wherein: the receiver is further configured to receive the paging CORESET from a gNB. The WTRU as claimed in claim 1, wherein: the receiver is further configured to receive from a gNB that a multiplex type for paging is time division multiplexing (TDM), frequency division multiplexing (FDM) Or an indication of mixing TDM and FDM. The WTRU as claimed in claim 1, wherein the PO comprises at least one of: a time slot, a non-time slot, a subframe, or an orthogonal frequency division multiplexing (OFDM) symbol. The WTRU as described in claim 1 is configured to operate using discontinuous reception (DRX) in an idle mode and wake up during the PO to perform the paging monitoring. A method of paging monitoring performed by a wireless transmit/receive unit (WTRU) configured to support multi-beam communication, the method comprising: receiving a configuration for enhanced paging; determining for a synchronization signal block (SSB) a first subcarrier spacing (SCS) and a second SCS for a paging reception; determining a paging multiplex type (PMT) based on the first SCS and the second SCS, wherein the first SCS and In the case where the second SCS is different, the PMT is determined to be a first type, and in the case that the first SCS and the second SCS are the same, the PMT is determined to be a second type; PMT to determine a paging control resource set (CORESET), a paging message, and a beam, time, and frequency relationship between the SSBs; and based on the determined beam, time, and frequency relationship for a paging message for the paging message The PO is monitored in one or more beams of the opportunity (PO). The method of claim 11, wherein in the case where the PMT is determined to be the first type, the beam, time, and frequency relationship includes: the paging CORESET and the paging message are time-multiplexed ( TDM), the paging message is time aligned in a same time slot as the SSB, and the paging message is frequency division multiplexed (FDM) with the SSB. The method of claim 12, wherein the paging CORESET uses a repeating beam to perform TDM with the paging message, resulting in two transmissions per beam of the PO. The method of claim 11, wherein in the case where the PMT is determined to be the second type, the beam, time, and frequency relationship includes: the paging CORESET and the paging message are time-multiplexed ( TDM), the paging CORESET, and the paging message are time aligned in a same time slot as the SSB, and the paging CORESET and the paging message are frequency division multiplexed (FDM) with the SSB. The method of claim 14, wherein the paging CORESET performs TDM with the paging message without using a repeating beam, resulting in one transmission per beam of the PO. The method of claim 11, further comprising: monitoring the PO for a paging downlink control information (DCI), wherein the paging DCI includes a schedule information about the paging message. The method of claim 11, further comprising: receiving the paging CORESET from a gNB. The method of claim 11, further comprising: receiving, from a gNB, a multiplex type for paging is time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM and FDM. An indication. The method of claim 11, wherein the PO comprises at least one of: a time slot, a non-time slot, a subframe, or an orthogonal frequency division multiplexing (OFDM) symbol. The method of claim 11, further comprising: using discontinuous reception (DRX) in an idle mode, and waking up during the PO to perform the paging monitoring.