Dynamic power sharing in a communication network

Abstract

Aspects relate to extending cross-slot scheduling for power efficient paging between different new radio (NR) operation platforms or environments. In some examples, the same paging downlink control information (DCI) can be shared between existing NR user equipment (UEs) and new NR UEs in different slots, with a single paging DCI scheduling multiple paging messages for each operation environment. In some examples, the same paging physical downlink control channel (PDCCH) occasion can be shared in different slots in existing NR operation environments and new NR operation environments to schedule paging messages, but different DCIs are used to schedule the paging messages. In some examples, the same physical downlink shared channel (PDSCH) paging message can be shared between existing NR operation environments and new NR operation environments in different slots.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to non-provisional application No. 17 / 313,887 filed in the U.S. Patent Office on May 6, 2021, and provisional application No. 63 / 025,960 filed in the U.S. Patent Office on May 15, 2020, the contents of which are incorporated by reference as if fully set forth below and for all applicable purposes. TECHNICAL FIELD

[0003] The technology discussed below relates generally to wireless communication networks, and more particularly, to techniques for providing shared paging and scheduling capabilities.

[0004] INTRODUCTION

[0005] In wireless communication systems, such as those specified under standards for 5G New Radio (NR), an access point (e.g., a base station) can communicate with user equipment (UE) (e.g., a smartphone). Dual connectivity is a mode of operation in which a UE equipped with multiple receivers and transmitters can be configured to utilize radio resources of two different schedulers located in two radio base stations (eNBs), a master eNB and a secondary eNB connected via a non-ideal backhaul over an X2 interface. In 5G NR configurations, a UE can connect to a Long Term Evolution (LTE) base station and a 5G NR base station, where each base station can be configured as a master node or a secondary node. In some configurations, a UE can access both LTE and 5G NR simultaneously.

[0006] BRIEF OVERVIEW OF SOME EXAMPLES

[0007] The following presents a summary of one or more aspects of the disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects of the disclosure, and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form that is brief, so as to

[0008] In one example, a method of sharing a paging message in a scheduled entity is disclosed. The method can include receiving paging control information for paging data, processing a time domain resource assignment in the paging control information, and receiving the paging data based on the time domain resource assignment, the paging data including first paging data in a first slot and second paging data in an offset slot.

[0009] Another example provides a scheduled entity for processing a paging message, the scheduled entity comprising a memory, a transceiver, and a processor, wherein the processor and the memory are configured to: receive paging control information for paging data; process a time domain resource assignment in the paging control information; and receive the paging data based on the time domain resource assignment, the paging data comprising first paging data in a first slot and second paging data in an offset slot.

[0010] In another example, a method of sharing a paging message in a scheduled entity is disclosed. The method comprises: receiving first paging control information for a paging message in a first slot; receiving second paging control information for the paging message in an offset slot; processing a time domain resource assignment in the first paging control information and the second paging control information; and receiving paging data for the paging message in the offset slot based on the time domain resource assignment.

[0011] Another example provides a scheduled entity for processing a paging message, the scheduled entity comprising a memory, a transceiver, and a processor, wherein the processor and the memory are configured to: receive first paging control information for a paging message in a first slot; receive second paging control information for the paging message in an offset slot; process a time domain resource assignment in the first paging control information and the second paging control information; and receive paging data for the paging message in the offset slot based on the time domain resource assignment.

[0012] These and other aspects of the application will become more fully understood upon consideration of the following detailed description, in conjunction with the accompanying drawings. Other aspects, features, and examples of the application will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary examples of the application in conjunction with the accompanying drawings. While features of the application are discussed relative to certain examples and drawings, any of the examples of the application can include one or more of the advantageous features discussed herein. In other words, while one or more examples can be discussed as having certain advantageous features, one or more of such features can also be used in accordance with the various examples of the application discussed herein. In similar fashion, while exemplary examples can be discussed herein as devices, systems, or methods, it should be understood that such exemplary examples can be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1 is a schematic illustration of a wireless communication system in accordance with some aspects;

[0015] Figure 2 is a conceptual illustration of an example of a radio access network in accordance with some aspects;

[0016] Figure 3is a diagram illustrating organization of wireless resources in an air interface that utilizes orthogonal frequency division multiplexing (OFDM) in accordance with some aspects;

[0017] Figure 4 is a block diagram illustrating a wireless communications system that supports beamforming and / or multiple-input multiple-output (MIMO) communications in accordance with some aspects;

[0018] Figure 5 is a block diagram illustrating a radio protocol architecture for the user and control planes in accordance with some aspects;

[0019] Figure 6 shows a diagram illustrating a beamformed paging SSB and associated paging signals for decoding by a UE in accordance with some aspects;

[0020] Figure 7 shows a paging signal for an LTE operating environment in accordance with some aspects;

[0021] Figure 8 shows a diagram of cross-slot scheduling of a paging message in a PDCCH of a first slot, where the paging message is received and processed in a PDSCH of an offset slot in accordance with some aspects;

[0022] Figure 9 shows a diagram illustrating paging occasion (PO) sharing for paging messages between LTE-based and NR-based operating environments in accordance with some aspects;

[0023] Figure 10 shows a diagram illustrating paging PDCCH monitoring and occasion sharing in accordance with some aspects;

[0024] Figure 11 shows a diagram of a paging message PDSCH shared between LTE and 5G NR operating environments in accordance with some aspects;

[0025] Figure 12 is a block diagram illustrating an example of a hardware implementation for a scheduled entity employing a processing system in accordance with some aspects; and

[0026] Figure 13 is a block diagram illustrating an example of a hardware implementation for a scheduling entity employing a processing system in accordance with some aspects.

[0027] Figure 14 is a flow diagram illustrating a method for processing a paging message for dynamic power sharing in a scheduled entity in accordance with some aspects.

[0028] Figure 15is a flowchart illustrating a method for processing a paging message having multiple paging control information for dynamic power sharing in a scheduled entity in accordance with some aspects.

[0029] DETAILED DESCRIPTION

[0030] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without

[0031] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, and so on. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with respect to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in various documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is designated as a “millimeter wave” band by the International Telecommunications Union (ITU).

[0032] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and as such can effectively extend the features of FR1 and / or FR2 into the mid-band frequencies. Additionally, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0033] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF frequency band.

[0034] Aspects of the present disclosure relate to extending cross-slot scheduling for power efficient paging between existing operating environments and new 5G NR operating environments. In some examples, the same paging downlink control information (DCI) can be shared between existing user equipment (UEs) and new NR UEs in different slots, with a single paging DCI scheduling multiple paging messages for each operating environment. In some examples, the same paging physical downlink control channel (PDCCH) occasion can be shared between existing operating environments and new 5G NR operating environments in different slots, but different DCIs are used to decode the paging messages. In some examples, the same physical downlink shared channel (PDSCH) paging message can be shared between existing operating environments and new 5G NR operating environments in different slots.

[0035] While aspects and examples are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases can come about in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, examples and / or uses can come about in integrated chip examples and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). Some examples can be or can not be specifically intended to be used in one or more of the below applications or use cases, but the examples described can be universally applicable. The scope of implementations can range from a single component, to a module or subsystem, to a larger system, to a distributed or cloud-computing arrangement. In some practical environments, devices incorporating described aspects and features can also necessarily include additional components and features for implementation and practice of the claimed examples. For example, transmission and reception of wireless signals necessarily includes a number of components, for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.

[0036] The various concepts presented throughout this disclosure can be implemented across a broad variety of telecommunication systems, network architectures, and communication standards. Referring now to FIG. 1, as an illustrative example without limitation, various aspects of the present disclosure are illustrated with reference to the wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By way of Figure 1

[0037] The RAN 104 can implement any suitable wireless communication technique to provide radio access to the UEs 106. As one example, the RAN 104 can operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G. As another example, the RAN 104 can operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as Long Term Evolution (LTE). The 3GPP refers to this hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of the present disclosure.

[0038] As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception to and from UEs in one or more cells. In different technologies, standards, or contexts, a base station can variously be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B, an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP), or some other suitable terminology. In some examples, a base station can include two or more TRPs that can be co-located or non-co-located. Each TRP can communicate on the same or different carrier frequencies. In examples where the RAN 104 operates according to both LTE and 5G NR standards, one of the base stations can be an LTE base station while another base station can be a 5G NR base station.

[0039] ​The RAN 104 is further illustrated with a controller - e.g., an access controller (not shown) - that can enable the management of various techniques associated with the RAN 104. For example, the controller can enable dynamic frequency selection (DFS), load balancing, interference coordination, and the like.

[0040] Within the present disclosure, a "mobile" device need not necessarily have a capability to move and can be stationary. The term mobile device or mobile equipment refers to a broad variety of devices and technologies. A UE can include a number of hardware structural components sized, shaped, and arranged to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, and / or the like electrically coupled to each other.

[0041] Additionally, a mobile device can be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer audio device, a consumer video device, a consumer multimedia device, a wireless cellular telephone device, a wireless telephone device, a gaming device, a multimedia gaming device, a handheld gaming device, a handheld gaming console, a wearable device, a camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a smart home or metrology device, a smart appliance, an appliance, an automotive electronics device, an automotive entertainment device, an automotive navigation device, an automotive communications device, a remote control device, a server computer, a computer, a computer component, a consumer electronics device, a component of a consumer electronics device, a computer peripheral device, a satellite radio, a digital audio player, a digital video player, a television, a computing device, an Internet of Things (IoT) device, or the like. Further, a mobile device can be a digital home or smart home device, such as a home audio, video, and / or multimedia device, a home appliance, a vending machine, a smart lighting device, a home security system, a smart meter, or the like. Further, a mobile device can be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power, lighting, water, or the like (e.g., a smart grid), an industrial automation and enterprise device, a logistics controller and / or agricultural equipment, or the like. Still further, a mobile device can provide for connected medicine or telemedicine support, such as health care at a distance. A remote healthcare device can include a remote healthcare monitoring device and a remote healthcare administration device, whose communication can be given preferential treatment or prioritized access over other types of information, for example, in the form of prioritized access for critical service data transmissions and / or relevant QoS for critical service data transmissions.

[0042] Wireless communication between a RAN 104 and a UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station, such as base station 108, to one or more UEs, such as UE 106, can be referred to as downlink (DL) transmission. In accordance with certain aspects of the present disclosure, the term downlink can refer to a point-to-multipoint transmission from a base station, such as base station 108, to one or more UEs, such as UE 106. Another way to describe this scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE, such as UE 106, to a base station, such as base station 108, can be referred to as uplink (UL) transmissions. In accordance with further aspects of the present disclosure, the term uplink can refer to a point-to-point transmission from a UE, such as UE 106, to a base station, such as base station 108.

[0043] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station 108) allocates resources (e.g., time- frequency resources) to devices and equipment within its service area or cell for the purpose of communicating with UEs. Within the present disclosure, scheduling entities can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communication, a set of UEs 106 (which can be scheduled entities) can utilize resources allocated by the scheduling entity 108.

[0044] Base stations 108 are not the only entities that can function as scheduling entities. That is, in some examples, UEs can function as scheduling entities, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, UEs can communicate directly with other UEs in a peer-to-peer or device-to-device fashion and / or in a relay configuration.

[0045] As Figure 1 As illustrated in FIG. 1, a scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly, a scheduling entity 108 is a node or device responsible for scheduling traffic (including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108) in a wireless communication network. On the other hand, a scheduled entity (e.g., a UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the scheduling entity 108.

[0046] Additionally, uplink and / or downlink control information and / or traffic information can be transmitted on a waveform that can be divided in time into frames, subframes, slots, and / or symbols. As used herein, a symbol can refer to a time unit of one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Multiple subframes or slots can be grouped together to form a single frame or radio frame. Within the present disclosure, a frame can refer to a predetermined duration (e.g., 10 ms) for wireless transmissions, where each frame includes, for example, 10 subframes of 1 ms each. Of course, these definitions are not required and waveforms can be organized in any suitable way and with any suitable duration for the various time divisions thereof.

[0047] Generally, base stations 108 can include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 can provide a link between the base stations 108 and the core network 102. In addition, in some examples, the backhaul network can provide interconnection between respective base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.

[0048] The core network 102 can be a part of the wireless communication system 100, and can be independent of the radio access technology used by the RAN 104. In some examples, the core network 102 can be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 can be configured according to a 4G Evolved-Packet Core (EPC), or any other suitable standard or configuration.

[0049] Reference is now made to Figure 2 , a schematic illustration of a radio access network 200 in accordance with some aspects of the present disclosure is provided, by way of illustrative example, and not by way of limitation. In some examples, the RAN 200 can be the same as the RAN 104 described above and illustrated in FIG. 1, in accordance with various aspects of the present disclosure. Figure 1

[0050] The geographic region over which the RAN 200 provides service can be divided into a number of cells (cellular regions), which can be uniquely identified by a user equipment (UE) based on identifiers broadcast from one access point or base station over the geographic region. Figure 2 ​Cellular cells 202, 204, 206, and 208 are illustrated, each of which can include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identity belonging to that sector. In a cell partitioned into sectors, multiple sectors within a cell can be formed by an antenna group, where each antenna is responsible for communication with UEs in a portion of the cell.

[0051] Various base station arrangements can be utilized. For example, in Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna, or can be connected by a feeder cable to an antenna or RRH 216. In the illustrated example, cells 202, 204, and 206 can be referred to as macrocells, as base stations 210, 212, and 214 support cells having a large size. Further, base station 218 is shown in cell 208, which can overlap with one or more macrocells. In this example, cell 208 can be referred to as a small cell (e.g., a microcell, picocell, femtocell, home base station, home NodeB, Family NodeB, etc.), as base station 218 supports a cell having a relatively small size. Cell size setting can be done according to system design and component constraints.

[0052] It is to be understood that RAN 200 can include any number of wireless base stations and cells. Further, relay nodes can be deployed to extend the size or coverage area of a given cell. Base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile Figure 1 stations 210, 212, 214, and / or 218 can be the same as or similar to scheduling entity 108 described above and illustrated in FIG. 1, in some examples.

[0053] Figure 2 Further included is an unmanned aerial vehicle (UAV) 220, which can be a drone or quadcopter. UAV 220 can be configured to function as a base station, or more specifically as a mobile base station. That is, in some examples, a cell can not necessarily be stationary, and the geographic area of a cell can move according to the location of a mobile base station, such as UAV 220.

[0054] Within the RAN 200, a cell can include UEs that are in communication with one or more sectors of each cell. Moreover, each base station 210, 212, 214, 218, and 220 can be configured to provide an access point to a core network 102 (see Figure 1 for example, UEs 222 and 224 can be in communication with base station 210; UEs 226 and 228 can be in communication with base station 212; UEs 230 and 232 can be in communication with base station 214 via RRH 216; UE 234 can be in communication with base station 218; and UE 236 can be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 can be the same as or similar to UE / scheduled entity 106 described above and Figure 1 illustrated in FIG. 1. In some examples, UAV 220 (e.g., quadcopter) can be a mobile network node and can be configured to function as a UE. For example, UAV 220 can operate within cell 202 by communicating with base station 210.

[0055] In further aspects of the RAN 200, sidelink signals can be used between UEs without necessarily relying on scheduling or control information from a base station. Sidelink communications can be used, for example, in a device-to-device (D2D) network, peer-to-peer (P2P) network, vehicle-to-vehicle (V2V) network, vehicle-to-everything (V2X) network, and / or other suitable sidelink network. For example, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using sidelink signals 237 without the need for relaying that communication through a base station. In some examples, UEs 238, 240, and 242 can each function as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signals 237 therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) that are within a coverage area of a base station (e.g., base station 212) can also communicate sidelink signals 227 over a direct link (sidelink) without communicating that communication through base station 212. In this example, base station 212 can allocate resources to UEs 226 and 228 for sidelink communication.

[0056] To enable transmissions over the air interface to achieve low block error rate (BLER) while still achieving very high data rates, channel coding can be used. That is, wireless communication can generally utilize a suitable error correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can improve the reliability of the message, enabling any bit errors that can occur due to noise to be corrected.

[0057] Data encoding can be implemented in a variety of ways. In earlier 5G NR specifications, user data is encoded using quasi-cyclic low-density parity check (LDPC) with two different base graphs: one base graph is used for large code blocks and / or high code rates, while the other base graph is used otherwise. Control information and physical broadcast channel (PBCH) are encoded using polar coding, based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0058] Aspects of the present disclosure can be implemented with any suitable channel code. Various implementations of base stations and UEs can include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0059] In the RAN 200, the ability for a UE to communicate while moving between different locations is referred to as mobility. The various physical channels between the UE and the RAN 200 are generally set up, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF can include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF can manage the security context for both control plane and user plane functionality, in whole or in part.

[0060] In various aspects of the disclosure, the RAN 200 can utilize DL- based mobility or UL-based mobility to enable mobility and handovers (i.e., transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, a UE can monitor various parameters of signals from its serving and neighboring cells during a call with a scheduling entity, or at any other time. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds that of the serving cell for a given amount of time, the UE can hand over or hand in from the serving cell to the neighboring (target) cell. For example, the UE 224 can move from the geographic area corresponding to its serving cell 202 to the geographic area corresponding to a neighbor cell 206. When the signal strength or quality from the neighbor cell 206 exceeds that of its serving cell 202 for a given amount of time, the UE 224 can transmit a report message to its serving base station 210 indicating this condition. In response, the UE 224 can receive a handover command and the UE can undergo a handover to cell 206.

[0061] In a network configured for UL-based mobility, UL reference signals from each UE can be used by the network to select a serving cell for each UE. In some examples, the base stations 210, 212, and 214 / 216 can broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs), unified Secondary Synchronization Signals (SSSs), and unified Physical Broadcast Channels (PBCHs)). The UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and transmit uplink pilot or reference signals in response to deriving the timing. The uplink pilot signals transmitted by a UE (e.g., the UE 224) can be concurrently received by two or more cells within the RAN 200 (e.g., the base stations 210 and 214 / 216). Each of the cells can measure a strength of the pilot signals, and a radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) can determine a serving cell for the UE 224. As the UE 224 moves within the RAN 200, the RAN 200 can continue to monitor the uplink pilot signals transmitted by the UE 224. When the signal strength or quality of the pilot signals measured by a neighboring cell exceeds that of the signal strength or quality measured by the serving cell, the RAN 200 can hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0062] Although the synchronization signal transmitted by base stations 210, 212, and 214 / 216 can be unified, the synchronization signal can not identify a particular cell, but can instead identify a zone of multiple cells operating on the same frequency and / or with the same timing. The use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network since the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0063] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides for exclusive use of a portion of spectrum to one or more network operators. Unlicensed spectrum provides for shared use of a portion of spectrum to anyone who complies with the technical rules governing use of the spectrum. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or limitations can be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties, such as through determinations made by the suitable license holder.

[0064] Devices communicating in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of the various devices. For example, 5G NR specifications utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) for UL and DL transmissions from and to the UEs 222 and 224 to the base station 210 to provide multiple access combined with frequency domain duplexing (FDD). Additionally, for UL transmissions, 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA)). However, within the scope of the disclosure, multiplexing and multiple access are not limited to the above schemes, and can be provided utilizing time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Further, multiplexing for DL transmissions from the base station 210 to the UEs 222 and 224 can be provided utilizing time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0065] Devices in the radio access network 200 can also utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with one another. Full-duplex means both endpoints can simultaneously communicate with one another. Half-duplex means only one endpoint can send information to the other at a time. Half-duplexing is often implemented with time-division duplex (TDD), in which each endpoint can only send information to the other during different time periods. In TDD, the transmissions in different directions on a given channel are separated by using time division multiplexing. That is, in some scenarios, a channel is dedicated for transmission in one direction at a time, while at other times, the channel is dedicated for transmission in the other direction, where the direction can change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of the transmitter and receiver, and suitable interference cancelation techniques. Full-duplexing is often implemented for wireless links by using frequency-division duplex (FDD) or space-division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from one another using spatial division multiplexing (SDM). In other examples, full-duplex communication can be implemented within unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions are now within different sub-bands of the carrier bandwidth. This type of full-duplex communication can be referred to herein as sub-band full duplex (SBFD), also known as flexible duplex.

[0066] Various aspects of the disclosure will be described in reference to OFDM waveforms, which are schematically illustrated in Figure 3 FIG. 1. It will be understood by those of ordinary skill in the art that various aspects of the disclosure can be applied in substantially the same manner to SC-FDMA waveforms as described hereafter. That is, while some examples of the disclosure can focus on OFDM links for clarity, it will be understood that the same principles can be applied to SC-FDMA waveforms as well.

[0067] Reference is now made to Figure 3 FIG. 2B, which illustrates an expanded view of an exemplary subframe 302, showing an OFDM resource grid. However, as those skilled in the art will appreciate, the PHY transmission structure for any particular application can differ from this example described herein, depending on any number of factors. Here, time is on the horizontal axis and frequency is on the vertical axis.

[0068] The resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids 304 can be available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE, which is 1 subcarrier x 1 symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, a RB can include 12 subcarriers, this number being independent of the numerology used. In some examples, depending on the numerology, a RB can include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB 308 entirely corresponds to a single direction of communication (transmission or reception for a given device).

[0069] A set of contiguous or non-contiguous resource blocks can be referred to herein as a resource block group (RBG), a sub-band, or a bandwidth part (BWP). A set of sub-bands or BWPs can span the entire bandwidth. Scheduling of a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more sub-bands or bandwidth parts (BWPs). As such, a UE generally utilizes only a subset of the resource grid 304. In some examples, an RB can be the smallest unit of resources that can be assigned to a UE. As such, the more RBs scheduled for a UE and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE. RBs can be scheduled by a scheduling entity, such as a base station (e.g., gNB, eNB, etc.), or can be self-scheduled by a UE implementing D2D sidelink communication.

[0070] In this illustration, the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with some subcarriers illustrated above and below the RB 308. In a given implementation, the subframe 302 can have a bandwidth corresponding to any number of one or more RBs 308. Also, in this illustration, the RB 308 is shown as occupying less than the entire duration of the subframe 302, although this is merely one possible example.

[0071] Each 1ms subframe 302 can include one or more adjacent slots. As an illustrative example, in Figure 3In the example shown, a subframe 302 includes four time slots 310. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, with a nominal CP, a time slot may include 7 or 14 OFDM symbols. Additional examples may include mini time slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). In some cases, these mini time slots or shortened transmission time intervals (TTIs) may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0072] An expanded view of time slot 310 illustrates time slot 310 comprising a control region 312 and a data region 314. Generally, control region 312 carries a control channel, while data region 314 carries a data channel. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure described herein is merely exemplary in nature and may utilize different time-slot structures, and may include one or more for each of the control region and data region.

[0073] Although not in Figure 3 The explanation is as follows: However, each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can be used by the receiver equipment to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0074] In some examples, time slot 310 can be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications can refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple target receiving devices. Unicast communications can refer to point-to-point transmissions from one device to a single other device.

[0075] In an example of cellular communication over a cellular carrier via a Uu interface, for DL transmission, a scheduling entity (e.g., a base station) can allocate one or more REs 306 (e.g., within a control region 312) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH), to one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI) including but not limited to power control commands (e.g., one or more open loop power control parameters and / or one or more closed loop power control parameters), scheduling information, grants, and / or RE assignments for DL and UL transmissions. The PDCCH can further carry HARQ feedback transmissions, such as an acknowledgement (ACK) or negative acknowledgement (NACK). HARQ is a technique well-known by those of ordinary skill in the art, wherein for accuracy in reception, the integrity of the packet transmission can be checked, e.g., at the receiving side, utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK can be transmitted, whereas if not confirmed, a NACK can be transmitted. In response to the NACK, the transmitting device can send a HARQ retransmission, which can implement chase combining, incremental redundancy, or the like.

[0076] The base station can further allocate one or more REs 306 (e.g., in the control region 312 or data region 314) to carry other DL signals such as a demodulation reference signal (DMRS); a phase-tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB can be broadcasted at regular intervals based on a periodicity (e.g., 5, 10, 20, 30, 80, or 130 milliseconds). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). A UE can utilize the PSS and SSS to achieve synchronization in time domain for radio frames, subframes, slots, and symbols, identify the center of the channel (system) bandwidth in frequency domain, and identify the physical cell identity (PCI) of the cell.

[0077] The PBCH in the SSB can further include a master information block (MIB) that includes various system information and parameters for decoding a system information block (SIB). The SIB can be, for example, a System Information Type 1 (SystemInformationType1) (SIB1) that can include various additional system information. The MIB and SIB1 together provide the minimum system information (SI) for initial access. Examples of system information transmitted in the MIB can include, but are not limited to, a subcarrier spacing (e.g., a default downlink numerology), a system frame number, a configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), a cell barring indicator, a cell reselection indicator, a raster offset, and a search space for SIB1. Examples of remaining minimum system information (RMSI) transmitted in the SIB1 can include, but are not limited to, a random access search space, a paging search space, downlink configuration information, and uplink configuration information. The base station can also transmit other system information (OSI).

[0078] In UL transmissions, a scheduled entity (e.g., UE) can utilize one or more REs 306 to carry UL control information (UCI) to the scheduling entity including one or more UL control channels, such as a physical uplink control channel (PUCCH). UCI can include various groupings and categories of information, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals can include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI can include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the UCI, the scheduling entity can transmit downlink control information (DCI) that can schedule resources for uplink packet transmissions. UCI can also include HARQ feedback, channel state feedback (CSF) such as a CSI report, or any other suitable UCI.

[0079] In addition to control information, one or more REs 306 (e.g., within data region 314) can be allocated for data traffic. Such data traffic can be carried on one or more traffic channels, such as, for DL transmissions, a physical downlink shared channel (PDSCH); or for UL transmissions, a physical uplink shared channel (PUSCH). In some examples, one or more REs 306 within data region 314 can be configured to carry other signals, such as one or more SIBs and DMRS.

[0080] In an example of sidelink communication over a sidelink carrier via a Proximity Service (ProSe) PC5 interface, the control region 312 of the slot 310 can include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a set of one or more other receiving sidelink devices (e.g., Rx V2X devices or other Rx UEs). The data region 314 of the slot 310 can include a physical sidelink shared channel (PSSCH) including sidelink data traffic transmitted by the transmitting sidelink device within resources reserved by the initiating (transmitting) sidelink device over the sidelink carrier via the SCI. Other information can further be transmitted over various REs 306 within the slot 310. For example, HARQ feedback information can be transmitted from the receiving sidelink device to the transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the slot 310. In addition, one or more reference signals can be transmitted within the slot 310, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0081] The above-described physical channels are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry information blocks, which are referred to as transport blocks (TBs). Transport block size (TBS), which can correspond to a number of information bits, can be a controlled parameter based on a modulation and coding scheme (MCS) and a number of RBs in a given transmission.

[0082] Figure 3 The channels or carriers illustrated in the middle are not necessarily all the channels or carriers available between devices, and one of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, can be available in addition to those illustrated.

[0083] In some aspects of the disclosure, the scheduling entity and / or the scheduled entity can be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4 An example of a wireless communication system 400 that supports beamforming and / or MIMO is illustrated. In a MIMO system, a transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and a receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Thus, there are N x M signal paths 408 from the transmit antennas 404 to the receive antennas 410. Each of the transmitter 402 and the receiver 406 can be implemented, for example, in a scheduling entity, a scheduled entity, or any other suitable wireless communication devices.

[0084] The use of such multi-antenna techniques enables wireless communication systems to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also known as layers) on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being known as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying these data streams by different weights and phase shifts) and then transmitting each spatially precoded stream over multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE with different spatial signatures, which allow each UE to recover one or more data streams intended for that UE. On the uplink, each UE transmits spatially precoded data streams, which allows the base station to identify the source of each spatially precoded data stream.

[0085] The number of data streams or layers corresponds to the transmission rank. Generally, the rank of a MIMO system is limited by the lower of the number of transmit or receive antennas 404 or 408. Additionally, channel conditions at the UE and other considerations (such as available resources at the base station) can also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and therefore the number of data streams) can be determined based on a rank indicator (RI) transmitted from that UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the measured signal-to-interference-noise ratio (SINR) on each receive antenna. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI along with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0086] In one example, such as Figure 4 As shown, rank-2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will transmit one data stream from each transmit antenna 404. Each data stream arrives at each receive antenna 408 along a different signal path 410. Receiver 406 can then reconstruct these data streams using the signals received from each receive antenna 408.

[0087] Beamforming is a signal processing technique that can be used at transmitter 402 or receiver 406 to shape or guide an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between transmitter 402 and receiver 406. Beamforming can be achieved by combining signals transmitted via antennas 404 or 408 (e.g., antenna elements of an antenna array module) such that some of these signals undergo constructive interference while others undergo destructive interference. To create the desired constructive / destructive interference, transmitter 402 or receiver 406 may apply amplitude and / or phase shifts to the signals transmitted or received from each of the antennas 404 or 408 associated with transmitter 402 or receiver 406.

[0088] In some examples, to select a specific beam for communication with the UE, the base station can transmit reference signals, such as SSBs or Channel State Information Reference Signals (CSI-RS), on each of multiple beams (SSB beams) in a beam-sweep manner. The UE can measure the Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or SINR on each beam and transmit a beam measurement report to the base station indicating the RSRP of each measured beam. The base station can then select a specific beam for communication with the UE based on the beam measurement report. In other examples, when the channel is reciprocal, the base station can derive a specific beam for communication with the UE based on uplink measurements of one or more uplink reference signals, such as Probe Reference Signals (SRS).

[0089] For radio access networks (such as) Figure 1 The radio access network 104 and / or shown Figure 2 The radio protocol architecture of the radio access network 200 shown can take various forms depending on the specific application. Figure 5 Examples of radio protocol architectures used for the user plane and control plane are explained.

[0090] like Figure 5 The radio protocol architecture for UE and base station, as explained in the document, consists of three layers: Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). L1 is the lowest layer and implements various physical layer signal processing functions. L1 will be referred to as Physical Layer 506 in this document. L2 508 is above Physical Layer 506 and is responsible for the link between UE and base station above Physical Layer 506.

[0091] In the user plane, L2 layer 508 includes a media access control (MAC) layer 510, a radio link control (RLC) layer 512, a packet data convergence protocol (PDCP) 514 layer, and a service data adaptation protocol (SDAP) layer 516, which are terminated at the base station on the network side. Although not shown, the UE can have several upper layers above the L2 layer 508, including at least one network layer (e.g., IP layer and user data protocol (UDP) layer) and one or more application layers, which are terminated at the user plane function (UPF) on the network side.

[0092] The SDAP layer 516 provides a mapping between a 5G core (5GC) quality of service (QoS) flow and data radio bearers and performs QoS flow ID marking in both downlink and uplink packets. The PDCP layer 514 provides packet sequencing, in-sequence delivery of packets, retransmission of PDCP protocol data units (PDUs), and transfer of upper layer data packets to lower layers. PDUs can include, for example, Internet Protocol (IP) packets, Ethernet frames, and other unstructured data (i.e., machine-type communications (MTC), collectively referred to below as “packets”). The PDCP layer 514 also provides header compression of upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and integrity protection of data packets. A PDCP context can indicate whether PDCP duplication is used for a unicast connection.

[0093] The RLC layer 512 provides segmentation and reassembly of upper layer data packets, error correction through automatic repeat request (ARQ), and independent of PDCP sequence numbering. An RLC context can indicate whether to use an acknowledged mode (e.g., using a reordering timer) or a non-acknowledged mode for the RLC layer 512. The MAC layer 510 provides multiplexing between logical channels and transport channels. The MAC layer 510 is also responsible for the allocation of the various radio resources (e.g., resource blocks) in one cell among the UEs and HARQ operation. A MAC context can implement, for example, a HARQ feedback scheme, a resource selection algorithm, carrier aggregation, beam failure recovery, or other MAC parameters for a unicast connection. The physical layer 506 is responsible for transmitting and receiving data on physical channels (e.g., within a time slot). A PHY context can indicate a transport format and radio resource configuration (e.g., bandwidth part (BWP), numerology, etc.) for a unicast connection.

[0094] In the control plane, the radio protocol architecture for the UE and base station is substantially the same for the L1 506 and L2 508 with the exception that there is no SDAP layer in the control plane and no header compression function for the control plane. The control plane also includes a radio resource control (RRC) layer 518 in the L3 and a higher non-access stratum (NAS) layer 520. The RRC layer 518 is responsible for the establishment and reconfiguration of the signaling radio bearers (SRBs) and data radio bearers (DRBs), paging origination and request in the base station, and system information (SI) acquisition processing. The RRC layer 518 is further responsible for QoS management, mobility control (e.g., handover, cell selection and reselection, inter-RAT mobility), UE measurement and reporting, and security functions. The NAS layer 520 terminates in the AMF in the core network and performs various functions such as authentication, registration management, and connection management.

[0095] During operation, DL channels and signals can be transmitted by a gNB in broadcast or unicast mode to one or more UEs. Downlink physical channels are configured to carry information from higher layers, including but not limited to a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), and a physical downlink control channel (PDCCH). The PDSCH carries DL unicast data and system broadcast messages, the PBCH carries information needed to access a cell, and the PDCCH carries scheduling information that enables a UE to locate its PDSCH. In 5G NR, the PDCCH can also convey short paging messages that can not involve the PDSCH. The MAC can determine which logical channels are mapped to which transport channels and pass that information to the PHY. Logical channel types can be defined by passing what type of information; for example, paging control channels, broadcast control channels, and dedicated traffic channels. These are mapped to appropriate transport channels, such as paging control on a paging channel (PCH), broadcast control on a broadcast channel (PBCH), dedicated traffic channels on a UL or DL shared channel (PUSCH or PDSCH), and so on. Paging and system information notifications (P-RNTI) can be provided on the PCH.

[0096] In the case that an RRC connection is established, the UE can be in an RRC connected (RRC CONNECTED) state or an RRC inactive (RRC INACTIVE) state. If not the case (i.e., an RRC connection is not established), the UE can be in an RRC idle (RRC IDLE) state. During the RRC idle state, UE-specific DRX can be configured by upper layers and UE-controlled mobility can be established based on network configuration. The UE can monitor a paging channel for CN paging using a 5G-S-TMSI, perform neighbor cell measurements and cell selection (reselection), acquire system information, and can send an SI request if configured. During the RRC inactive state, UE-specific discontinuous reception (DRX) can be configured by upper layers for power saving and UE-controlled mobility can be established based on network configuration. The UE can store an AS context and a RAN-based notification area is configured by the RRC layer. The UE can monitor a paging channel for CN paging using a 5G-S-TMSI, perform neighbor cell measurements and cell selection (reselection), perform RAN-based notification area updating periodically when moving outside the configured RAN-based notification area, acquire system information, and send an SI request if configured. The RRC connected state applies when a 5GC-NG-RAN connection (both control plane / user plane) is established for the UE, where the UE AS context is stored in the NG-RAN and the UE, and the NG-RAN knows in which cell the UE belongs. The UE monitors a paging channel if configured, monitors a control channel associated with a shared data channel to determine whether data is scheduled for the UE, provides channel quality and feedback information, performs neighbor cell measurements and measurement reporting, and acquires system information.

[0097] During an idle or inactive mode of operation, a UE can monitor a paging channel to receive a paging message from a scheduling entity (e.g., a base station) via a PDCCH (e.g., a DCI with a CRC scrambled by a P-RNTI) and a corresponding PDSCH (e.g., a paging message). In some examples, the P-RNTI can be common for all UEs, where an identity of a paged UE (IMSI) is included in the paging message information required to access a cell, and the PDCCH carries scheduling information that enables the UE to locate its PDSCH. In NR, the PDCCH can also convey a short paging message that does not involve a PDSCH.

[0098] For LTE (legacy) operating environments, control reference signals (CRS) are transmitted relatively frequently and the operating environment allows for sample capture around the paging occasion (PO) and enables offline mode implementation. For NR operating environments, there can be no CRS or other "always on" reference signals. Accordingly, reference signals can be received as-is via SSB, e.g., with 20 millisecond periodicity. In this configuration, there can be no offline mode due to potentially large gap between SSB and paging message. During operation, a UE can first wake up to receive one or more SSBs (depending on channel conditions) and recover time / frequency synchronization. The UE can be configured to enter "light sleep" between SSBs and / or POs, which can reduce deep sleep time and result in multiple wake-up / enter-sleep overhead. This configuration can result in increased power consumption.

[0099] Figure 6 A diagram 600 is shown illustrating a beamformed paging SSB 602 and associated paging message 604 for decoding by a UE in an existing 5G NR operating environment, in accordance with some aspects. In some examples, the paging message can be beamformed. For FR2, up to 64 beamformed SSBs 602 can be transmitted. Thus, up to 64 beamformed copies of the paging message, having a one-to-one correspondence (shown as dashed lines) with the SSBs, will be transmitted. The UE can select the best beam based on the SSB and decode the corresponding paging message.

[0100] UE power saving paging enhancements can be configured to provide enhancements to idle / inactive mode UE power saving and reduce unnecessary UE paging reception with minimal or no impact to legacy (LTE) UEs. By specifying techniques and art for providing potential PT-RS (hereinafter more simply referred to as tracking reference signal (TRS)) and / or CSI-RS occasions available in connected mode to idle / inactive mode UEs, system overhead impact can be reduced.

[0101] With respect to paging enhancements, when a UE detects a paging PDCCH with P-RNTI, it does not know whether the paging is intended for the UE itself. After completing decoding the paging message (received in PDSCH), the UE can identify whether the paging is addressed to the UE. If the paging is not addressed to the UE, the effort for paging message decoding is wasted. Accordingly, smaller paging groups with different P-RNTI, or paging groups with new paging DCI and group ID can be used to reduce unnecessary paging. With respect to tracking of idle / inactive mode UEs in NR, there is no “always-on” reference signal (e.g., CRS in LTE) in NR that tracks UEs in this manner, and UE-specific reference signals such as TRS and CSI-RS are only configured for connected mode UEs. However, by allowing TRS / CSI-RS measurements for idle / inactive mode UEs, the network can rely less on SSB for tracking, which can improve overall UE power efficiency and allow for early indication of the UE to monitor and / or detect PDCCH within a target paging occasion (PO).

[0102] Figure 7 A paging message 700 for a first NR operating platform or environment (e.g., an existing 5G NR operating platform configured according to 3GPP NR Release 15 or Release 16 specifications) is shown in accordance with some aspects. In this example, the paging message 700 is provided in a scheduled PDCCH 702 and PDSCH 704 in the same slot (slot n). Here, the UE can only buffer the received (Rx) information in the paging slot (e.g., slot n) to capture potential paging DCI. In first platform NR (e.g., existing NR) paging, both the potential PDCCH and PDSCH can be buffered. In Figure 7 In the example shown, the UE can process the PDCCH for paging DCI detection, and if paging DCI is detected, the UE proceeds to process the paging data (buffered PDSCH). Otherwise, the UE can discard the buffered PDSCH. In Figure 7 In the example shown, the paging data is received in the same paging slot. In other examples, a new 5G NR platform (e.g., a 5G NR operating platform configured according to 3GPP Release 17 or later specifications) can provide enhanced paging, where the paging data can be received at K0 (scheduling offset) slots after the PDCCH.

[0103] Figure 8This configuration of enhanced paging is illustrated in the middle illustration, which shows a diagram 800 of cross-slot scheduling of a paging message in a PDCCH 802 in a first slot (slot n). Paging data can then be received and processed in a PDSCH 804 of an offset slot (slot n + K0). Cross-slot scheduling can be used for power efficient paging. If the paging DCI is not detected, the UE goes to sleep. However, UEs using existing platforms for NR-based paging and new platforms for NR-based enhanced paging (cross-slot scheduling) can share the same paging occasion (PO). Accordingly, different PO options can be configured that share different existing paging platforms and new NR-based paging platforms.

[0104] Figure 9 A diagram 900 illustrating PO sharing for paging messages between a first platform NR-based operating environment (e.g., Rel-15, Rel-16) and a second platform NR-based operating environment (e.g., Rel-17 and beyond) is shown. This example demonstrates paging DCI sharing, where the same paging DCI (e.g., same P-RNTI and same DCI format) can be shared between communications from different wireless communication platforms. In this example, a first paging message including paging control information (paging DCI) and paging data is received in slot n, as shown. For example, the paging control information (paging DCI) of the first paging message is received by a first platform NR UE in a PDCCH 902, and the paging data of the first paging message is processed by the first platform NR UE in a PDSCH 904 of slot n, as shown. However, the PDCCH 902 can also be shared with a second paging message including paging data (e.g., PDSCH 906) for a second platform NR UE in an adjacent slot (slot n + K0), as shown. Here, a single paging DCI can be configured to schedule multiple PDSCHs (904, 906) between different platforms.

[0105] In some examples, time domain resource allocation (or time domain resource assignment (TDRA)) can be used for sharing paging messages. The time domain resources are signaled to the scheduled entities informing them about which slots / symbols can be transmitted and / or received. The resource allocation can be performed dynamically or in a semi-persistent manner. Dynamic scheduling in uplink can be performed using PDCCH DCI. For semi-persistent scheduling, PDCCH DCI or RRC signaling can be used. In some examples, PDCCH DCI is used for both dynamic and semi-persistent scheduling (SPS) in downlink. DCI formats 1 0 and 1 1 can be used to dynamically allocate time domain resources for PDSCH. In the case of dynamic scheduling, PDCCH carrying DCI 1 0 and 1 1 is generally addressed to C-RNTI or MCS-C-RNTI. Other RNTIs such as SI-RNTI, P-RNTI, Temporary C-RNTI, and RA-RNTI can also be used for this purpose. DCI formats 1 0 and 1 1 can carry a multi-bit (e.g., 4-bit) field for time domain resource assignment that points to a row in a lookup table that provides parameters for resource allocation. These parameters can include a slot offset K0, which can be used to derive the slot in which PDSCH reception occurs. When K0 = 0, PDSCH reception is intended to be in the same slot in which the DCI is received. When the allocation and PDSCH transmission are contained in the same slot, the slot can be considered a self-contained slot. Another parameter can include a joint encoding start and length indicator value (SLIV), or individual values for the start symbol S (where the first symbol in the slot in which PDSCH will be received) and allocation length L (allocation length in number of OFDM symbols). Additionally, a PDSCH mapping type (e.g., Type A or Type B) can be assumed for PDSCH reception.

[0106] The TDRA field in DCI can be interpreted differently by existing NR UEs and new NR UEs. For example, different TDRA tables for paging can also be used by both existing NR UEs and new NR UEs. Thus, in some examples, a single paging DCI can schedule multiple paging messages (e.g., one paging message for existing NR UEs and another paging message for new NR UEs).

[0107] Figure 10A diagram 1000 illustrating paging PDCCH monitoring and occasion sharing according to some aspects is shown. In this example, the same PDCCH monitoring occasion (i.e., the same quasi co-location (QCL) information) is shared by an existing NR UE and a new NR UE, but different DCIs are used for the existing NR UE and the new NR UE, such as different RNTIs, different DCI formats, different PDCCH candidates, and / or the like. In this example, the existing NR and new NR paging messages can be configured with the same QCL information, which is provided to different portions of the same PDCCH occasion: PDCCH1 1002 and PDCCH2 1004. The existing NR paging message can be provided from PDCCH1 1002 to PDSCH 1006 for processing within slot n, while the new NR paging message can be provided from PDCCH2 1006 to PDSCH 1008 in slot n+K0, as shown.

[0108] Four types of QCL are defined in 5G NR: QCL Type A, QCL Type B, QCL Type C, and QCL Type D. For example, QCL Type A can indicate a downlink reference signal (e.g., SSB or CSI-RS) or an uplink reference signal (e.g., SRS) from which large-scale channel properties (LSCPs) (such as Doppler shift, Doppler spread, average delay, and / or delay spread of a downlink channel or signal or an uplink channel or signal) can be inferred. QCL Type B and QCL Type C can also indicate a reference signal (e.g., SSB, CSI-RS, or SRS) from which certain LSCPs (e.g., Doppler shift and / or Doppler spread for QCL Type B, and average delay and / or delay spread for QCL Type C) can be inferred. QCL Type D can indicate a spatial RX parameter (e.g., a spatial property of a beam on which a downlink / uplink channel or signal is transmitted). The spatial property of a beam can be inferred from a beam used to transmit a reference signal (e.g., SSB, CSI-RS, or SRS), and can indicate, for example, at least one of a beam direction or a beam width.

[0109] Figure 11A diagram 1100 of a paging message PDSCH shared between a first platform NR (e.g., Release 15, 16) and a new second platform NR (e.g., Release 17 and beyond) is shown in accordance with some aspects. In this example, the DCI for the first operating platform or operating environment is received in a PDCCH 1102 in a first slot (slot n), and the DCI for the second operating platform or operating environment is received in a PDCCH 1104 in an offset slot (slot n + K0), as shown. Here, the DCI of the PDCCH 1104 in slot n and the DCI of the PDCCH 112 in the offset slot (slot n + K0) can both include respective paging control information (paging DCI) containing time domain resource allocation for the PDSCH 1106 in the offset slot (slot n + K0). Here, when two different operating platforms or operating environments (e.g., existing NR and new NR) need to page at the same time, the two different paging DCIs (1102, 1106) can be configured to schedule the same paging data (e.g., PDSCH 1106).

[0110] Figure 12 is a block diagram illustrating an example of a hardware implementation for a scheduled entity (UE) 1200 employing a processing system 1214 in accordance with some aspects. The scheduled entity 1200 may, for example, be a user equipment (UE) as Figure 1 and / or any one or more of the user equipment (UE) illustrated in any one or more of

[0111] The scheduled entity 1200 can be implemented with a processing system 1214 (or “processing device”) that includes one or more processors 1204. Examples of processors 1204 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described

[0112] In some examples, the processor 1204 can be implemented via a baseband or modem chip, while in other implementations the processor 1204 can include a number of distinct and different devices from the baseband or modem chip (e.g., which can work cooperatively to achieve examples discussed herein in such scenarios). Also as noted above, various hardware arrangements and components outside of a baseband modem processor can be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0113] In this example, the processing system 1214 can be implemented with a bus architecture, as represented generally by the bus 1202. The bus 1202 can include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1214 and the overall design constraints. The bus 1202 communicatively couples various circuits including one or more processors (represented generally by the processor 1204), memory 1205, and computer-readable media (represented generally by the computer-readable media 1206). The bus 1202 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be further described. A bus interface 1208 provides an interface between the bus 1202, the transceiver 1210, and the antenna array 1250. The transceiver 1210 provides a communication interface or means for communicating with various other apparatus over a transmission medium. Depending upon the nature of the apparatus, a user interface 1212 (e.g., keypad, display, speaker, microphone, joystick) can also be provided. Of course, such a user interface 1212 is optional, and can be omitted in some examples.

[0114] The processor 1204 is responsible for managing the bus 1202 and general processing, including the execution of software stored on the computer-readable medium 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described below for any particular apparatus. The computer-readable medium 1206 and the memory 1205 can also be used for storing data used by the processor 1204 in executing software. For example, the memory 1205 can store a list of one or more allowed network slices 1220 (e.g., allowed NSSAI), a list of one or more activated network slices 1222, and a default RACH resource 1224 used by the processor 1204.

[0115] One or more processors 1204 in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software can reside on a computer-readable medium 1206.

[0116] Computer-readable medium 1206 can be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, for example, magnetic storage devices (e.g., hard disk; floppy disk); optical disk devices (e.g., compact disk (CD); digital versatile disk (DVD)); smart cards; flash memory devices (e.g., card; stick; key drive); random access memories (RAMs); read only memories (ROMs); programmable ROMs (PROMs); erasable PROMs (EPROMs); electrically erasable PROMs (EEPROMs); registers; removable disk; and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1206 can reside in the processing system 1214, external to the processing system 1214, or distributed across multiple entities including the processing system 1214. Computer-readable medium 1206 can be embodied in a computer program product. By way of example, a computer program product can include a computer-readable medium in packaging material. In some examples, computer-readable medium 1206 can be part of a memory 1205. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0117] In some aspects of the disclosure, the processor 1204 can include circuitry configured for various functions. For example, the processor 1204 can include communication and processing circuitry 1218 configured to communicate with a base station (e.g., gNB or eNB) via a Uu link. In some examples, the communication and processing circuitry 1218 can include one or more hardware components that provide the physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing a received signal and / or processing a signal for transmission). For example, the communication and processing circuitry 1218 can include one or more transmit / receive chains.

[0118] In some implementations in which the communication involves receiving information, the communication and processing circuitry 1218 can obtain information from a component of the wireless communication device 1200 (e.g., from a transceiver 1210 that receives information via radio frequency signaling or some other type of signaling appropriate for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1218 can output the information to another component of the processor 1204, to the memory 1205, or to the bus interface 1208. In some examples, the communication and processing circuitry 1218 can receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1218 can receive the information via one or more channels. In some examples, the communication and processing circuitry 1218 can include functionality for receiving. In some examples, the communication and processing circuitry 1218 can include functionality for processing, including functionality for demodulating, functionality for decoding, and the like.

[0119] In some implementations in which the communication involves sending (e.g., transmitting) information, the communication and processing circuitry 1218 can obtain information from (e.g., from another component of the processor 1204, the memory 1205, or the bus interface 1208), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, the communication and processing circuitry 1218 can output the information to the transceiver 1210 (e.g., to transmit the information via radio frequency signaling or some other type of signaling appropriate for the applicable communication medium). In some examples, the communication and processing circuitry 1218 can transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1218 can transmit the information via one or more channels. In some examples, the communication and processing circuitry 1218 can include functionality for transmitting (e.g., for transmitting). In some examples, the communication and processing circuitry 1218 can include functionality for generating, including functionality for modulating, functionality for encoding, and the like.

[0120] In some examples, the communication and processing circuitry 1218 can be configured to communicate (e.g., transmit / receive) beamformed signals at millimeter wave frequencies or sub-6 GHz frequencies via the transceiver 1210 and the antenna array 1250. The communication and processing circuitry 1218 can be further configured to execute communication and processing instructions (software) 1228 stored in the computer-readable medium 1206 to implement one or more functions described herein.

[0121] The processor 1204 can further include timing circuitry 1220 configured to implement, for example, the paging and timing procedures described herein, such as the paging and timing procedures described above in connection with FIG. 1.Figures 6-11 The techniques and skills described herein. The timing circuit system 1220 may be further configured to execute timing instructions (software) 1224 stored in the computer-readable medium 1206 to perform one or more functions described herein.

[0122] Processor 1204 may further include paging circuitry system 1222, which may be configured to, for example, process paging messages (such as those described herein), and the above. Figures 6-11 The technology described herein. The paging circuit system 1222 may be further configured to execute paging instructions (software) 1226 stored in the computer-readable medium 1206 to perform one or more of the functions described herein.

[0123] Of course, in the above examples, the circuitry included in processor 1204 is provided merely as an example, and other means for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 1206, or... Figures 1-2 and Figure 4 Any other suitable apparatus or device that describes and utilizes, for example, the processes and / or algorithms described herein.

[0124] Figure 13 This is a block diagram illustrating an example of a hardware implementation of a scheduling entity 1300 employing a processing system according to some aspects. The scheduling entity 1300 is shown as employing a processing system 1314. For example, the scheduling entity 1300 could be as follows: Figure 1 and 2 The base station (such as eNB, gNB) or other scheduling entity described in any one or more of them.

[0125] Scheduling entity 1300 can be combined with the above. Figure 12 The processing system 1214 discussed is implemented similarly to the processing system 1314, including a bus interface 1308, a bus 1302, a memory 1305, a processor 1304, and a computer-readable medium 1306. Furthermore, the base station 1300 may include components similar to those described above. Figure 12 The user interfaces, transceivers, and antenna arrays described herein are substantially similar to those of optional user interface 1312, transceiver 1310, and antenna array 1350. Processor 1304, as utilized in scheduling entity 1300, can be used to implement any one or more of the processes described herein.

[0126] In some aspects of this disclosure, processor 1304 may include circuitry configured for various functions. For example, processor 1304 may include communication and processing circuitry 1318, which may be combined with the above. Figure 12The described circuitry 1218 is similarly configured. The communication and processing circuitry 1318 can be further configured to execute communication and processing instructions (software) 1328 stored in the computer-readable medium 1306 to implement one or more functions described herein.

[0127] The processor 1304 can further include timing circuitry 1320 configured to implement timing processes related to, for example, the paging messaging procedures described herein, such as the techniques and technologies described above in Figures 6-11 The timing circuitry 1320 can be further configured to execute timing instructions (software) 1324 stored in the computer-readable medium 1306 to implement one or more functions described herein.

[0128] The processor can further include paging circuitry 1322, which can be configured to, for example, implement paging message processing such as those described herein, as well as the techniques described above in Figures 6-11 The paging circuitry 1322 can be further configured to execute paging instructions (software) 1326 stored in the computer-readable medium 1306 to implement one or more functions described herein.

[0129] Of course, in the above examples, the circuitry included in the processor 1304 is provided merely as an example, and other means for carrying out the described functions can be included within various aspects of the disclosure, including but not limited to the instructions stored in the computer-readable storage medium 1306, or any other suitable apparatus or means Figures 1-2 and Figure 4 described and utilized, for example, the processes and / or algorithms described herein.

[0130] Figure 14 is a flow diagram 1400 illustrating a method for processing a paging message for dynamic power sharing in a scheduled entity, in accordance with some aspects. As described below, some or all illustrated features can be omitted in some implementations, and some illustrated features can not be required for implementation of all embodiments. In some examples, the process 1400 can be performed by the scheduled entity 1200 illustrated in Figure 12 In some examples, the process 1400 can be performed by any suitable apparatus or means for performing the functions or algorithm described below.

[0131] At block 1402, the scheduled entity can receive paging control information for paging data. In some examples, the paging control information can be received in a DCI of a PDCCH. In some examples, the paging control information can include a first paging control portion and a second paging control portion that are co-located in a same paging occasion. The first paging control portion and the second paging control portion can be configured with different control information. In some examples, the first paging control portion and the second paging control portion can be configured with the same QCL information. In some examples, the scheduled entity can receive the paging control information for the paging data based on the scheduled entity being in an idle mode or an inactive mode. For example, the paging circuitry 1222 shown and described above in connection with Figure 12 The paging circuitry 1222, together with the communication and processing circuitry 1218 and the transceiver 1210, shown and described above in connection with

[0132] At block 1404, the scheduled entity can process a time domain resource assignment (TDRA) in the paging control information. In some examples, the first paging control portion includes a first time domain resource assignment for first paging data in a first slot, and the second paging control portion includes a second time domain resource assignment for second paging data in an offset slot. For example, the timing circuitry 1220 shown and described above in connection with Figure 12 The timing circuitry 1220, shown and described above in connection with

[0133] At block 1406, the scheduled entity can receive the paging data based on the time domain resource assignment (TDRA), the paging data including first paging data in a first slot and second paging data in an offset slot. In some examples, the scheduled entity can receive the paging data in a physical downlink shared channel (PDSCH). In some examples, the scheduled entity can receive the first paging data in a first PDSCH in the first slot and the second paging data in a second PDSCH in the offset slot. For example, the paging circuitry 1222 and the transceiver 1210 shown and described above in connection with Figure 12 The paging circuitry 1222 and the transceiver 1210, shown and described above in connection with

[0134] Figure 15 is a flowchart 1500 illustrating a method for processing a paging message with multiple paging control information for dynamic power sharing in a scheduled entity, in accordance with some aspects. As described below, some or all of the features can be omitted in particular implementations consistent with the scope of the disclosure, and some features can not be required for implementation of all embodiments. In some examples, the process 1500 can be performed by the scheduled entity 1200 illustrated and described above in connection with Figure 12 In some examples, the process 1400 can be performed by any suitable apparatus or means adapted to perform the functions or algorithms described below.

[0135] At block 1502, the scheduled entity can receive first paging control information of a paging message in a first slot. In some examples, the first paging control information can be received in a first DCI of a first PDCCH. For example, the paging circuitry 1222, shown and described above in connection with FIG. 13, can provide a means for receiving first paging control information of a paging message in a first slot. Figure 12 The paging circuitry 1222, shown and described above in connection with FIG. 13, in combination with the communication and processing circuitry 1218 and the transceiver 1210, can provide a means for receiving first paging control information of a paging message.

[0136] At block 1504, the scheduled entity can receive second paging control information of the paging message in an offset slot. In some examples, the second paging control information can be received in a second DCI of a second PDCCH. In some examples, the first paging control information and the second paging control information are different. In some examples, the first and second paging control information of the paging data are received based on the scheduled entity being in an idle mode or an inactive mode. For example, the paging circuitry 1222, shown and described above in connection with FIG. 13, in combination with the communication and processing circuitry 1218 and the transceiver 1210, can provide a means for receiving second paging control information of a paging message. Figure 12 The paging circuitry 1222, shown and described above in connection with FIG. 13, in combination with the communication and processing circuitry 1218 and the transceiver 1210, can provide a means for receiving second paging control information of a paging message.

[0137] At block 1506, the scheduled entity can process a time domain resource assignment (TDRA) in the first paging control information and the second paging control information. In some examples, the time domain resource assignment in the first paging control information and the second paging control information are processed simultaneously. For example, the paging circuitry 1222 and the timing circuitry 1224, shown and described above in connection with FIG. 13, can provide a means for processing a time domain resource assignment. Figure 12 The paging circuitry 1222 and the timing circuitry 1224, shown and described above in connection with FIG. 13, can provide a means for processing a time domain resource assignment.

[0138] At block 1508, the scheduled entity can receive paging data of the paging message in the offset slot based on the time domain resource assignment. In some examples, the paging data can be received in a PDSCH. The paging data can be received in a first PDSCH in the first slot in a first portion of the paging data and in a second PDSCH in the offset slot in a second portion of the paging data. For example, the paging circuitry 1222, the transceiver 1210, and the timing circuitry 1224, shown and described above in connection with FIG. 13, can provide a means for receiving paging data of a paging message in an offset slot based on a time domain resource assignment. Figure 12 The paging circuitry 1222, the transceiver 1210, and the timing circuitry 1224, shown and described above in connection with FIG. 13, can provide a means for receiving paging data of a paging message in an offset slot based on a time domain resource assignment.

[0139] In one configuration, the scheduled entity configured for wireless communication includes means for processing a paging message, as described in the present disclosure. In one example, the aforementioned means can be the processing system 1312 shown in FIG. 13 configured as described with respect to the processing system 1312. Figure 12The processor 1204 shown in FIG. 12 is configured to perform the functions recited by the aforementioned apparatuses. In another example, the aforementioned apparatuses can be circuits or any equipment configured to perform the functions recited by the aforementioned apparatuses.

[0140] Of course, in the above examples, the circuitry included in the processor 1204 is merely provided as an example, and other means for carrying out the described functions can be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 1206, or at least one of Figure 1 、 2 , 4, and / or 12, and with any other suitable apparatus or means described herein, for example, with respect to the processes and / or algorithms described herein with respect to Figures 14-15 and 15 any of the processes and / or algorithms described herein with respect to

[0141] Figures 1-15 The processes depicted in FIG. 12 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0142] Aspect 1 : A method of sharing a paging message in a scheduled entity, comprising: receiving paging control information for paging data; processing a time domain resource assignment in the paging control information; and receiving the paging data based on the time domain resource assignment, the paging data comprising first paging data in a first slot and second paging data in an offset slot.

[0143] Aspect 2: The method of aspect 1, wherein receiving paging control information comprises: receiving the paging control information in downlink control information (DCI) of a physical downlink control channel (PDCCH).

[0144] Aspect 3: The method of aspect 1 or 2, wherein receiving paging data comprises: receiving the paging data in a physical downlink shared channel (PDSCH).

[0145] Aspect 4: The method of any of aspects 1-3, wherein receiving paging data comprises: receiving first paging data in a first physical downlink shared channel (PDSCH) in a first slot and second paging data in a second PDSCH in an offset slot.

[0146] Aspect 5: The method of any of aspects 1-4, wherein the paging control information comprises a first paging control portion and a second paging control portion that are co-located in a same paging occasion.

[0147] Aspect 6: The method of any of aspects 1-5, wherein the first paging control portion and the second paging control portion comprise different control information.

[0148] Aspect 7: The method of any of aspects 1 through 6, wherein the first paging control portion and the second paging control portion are configured with same quasi co-location (QCL) information.

[0149] Aspect 8: The method of any of aspects 1 through 7, wherein the first paging control portion includes a first time domain resource assignment for first paging data in the first slot, and the second paging control portion includes a second time domain resource assignment for second paging data in the offset slot.

[0150] Aspect 9: The method of any of aspects 1 through 8, wherein receiving the paging control information further comprises receiving the paging control information for the paging data based on the scheduled entity being in an idle mode or an inactive mode.

[0151] Aspect 10: A method of sharing a paging message in a scheduled entity, comprising: receiving, in a first slot, first paging control information for a paging message; receiving, in an offset slot, second paging control information for the paging message; processing time domain resource assignments in the first paging control information and the second paging control information; and receiving, in the offset slot, paging data for the paging message based on the time domain resource assignments.

[0152] Aspect 11: The method of aspect 10, wherein receiving the first paging control information comprises receiving the first paging control information in a first downlink control information (DCI) of a first physical downlink control channel (PDCCH); and receiving the second paging control information comprises receiving the second paging control information in a second downlink control information (DCI) of a second physical downlink control channel (PDCCH).

[0153] Aspect 12: The method of aspect 10 or 11, wherein receiving the paging data comprises receiving the paging data in a physical downlink shared channel (PDSCH).

[0154] Aspect 13: The method of any of aspects 10 through 12, wherein the first paging control information and the second paging control information are different.

[0155] Aspect 14: The method of any of aspects 10 through 13, wherein receiving the paging data comprises receiving a first portion of the paging data in a first physical downlink shared channel (PDSCH) in the first slot and a second portion of the paging data in a second PDSCH in the offset slot.

[0156] Aspect 15: The method of any of aspects 10 through 14, wherein the first paging control information and the second paging control information for the paging data are received based on the scheduled entity being in an idle mode or an inactive mode.

[0157] Aspect 16: The method of any of aspects 10 through 15, wherein the time domain resource assignments in the first and second paging control information are processed simultaneously.

[0158] Aspect 17: A scheduled entity for processing paging messages, comprising a memory, a transceiver, and a processor, wherein the processor and the memory are configured to perform the method of any of aspects 1 through 9 or aspects 10 through 16.

[0159] Aspect 18: An apparatus for processing paging messages, comprising at least one means for performing a method as in any of aspects 1 through 9 or 10 through 16.

[0160] Aspect 19: A non-transitory computer-readable medium having instructions stored therein, the instructions executable by one or more processors of a scheduled entity to perform the method of any of aspects 1 through 9 or aspects 10 through 16.

[0161] Several aspects of a wireless communication network have been presented with reference to example implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure can be extended to other telecommunication systems, network architectures and communication standards.

[0162] By way of example, various aspects can be implemented within other systems defined by 3GPP such as Long-Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunication System (UMTS), and / or Global System for Mobile (GSM). Various aspects can also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0163] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspects" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term "coupled" is used herein to express a direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then object A and C can still be considered coupled to one another, even though they are not directly physically in contact with one another. For instance, a first object can be coupled to a second object even though the first object never physically touches the second object. The terms "circuit" and "circuitry" are used broadly, and intended to include both hardware implementations of electrical devices and conductors that couple the electrical devices in which the functionality of the disclosure is implemented, as well as software implementations where the functionality of the disclosure is implemented using information and / or instructions to processor(s). The functionality described herein can be implemented using hardware, software, or a combination of hardware and software.

[0164] Figure 1 One or more of the components, steps, features and / or functions illustrated in the figures can be rearranged and / or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. ​ 、 2 The apparatus, devices and / or components illustrated in FIGS. 4, 12 and 13 can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0165] It should be understood that the particular order in which the steps of the disclosed methods have been presented and / or described is exemplary only. Based on the description herein, those skilled in the art will appreciate that the steps of the methods can be rearranged, or that some steps can be eliminated, without departing from the novel concepts disclosed herein. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0166] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. The term "at least one of followed by a list of items means any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

1. A method for sharing paging messages among scheduled entities, comprising: Paging control information that receives paging data in the downlink control information (DCI) of the physical downlink control channel (PDCCH); Process the time-domain resource allocation in the paging control information; as well as The paging data is received in the Physical Downlink Shared Channel (PDSCH) based on the time-domain resource assignment. The paging data includes shared paging data, which includes first paging data in a first time slot and second paging data in an offset time slot.

2. The method as described in claim 1, wherein, Receiving the paging data includes: receiving the first paging data in the first physical downlink shared channel (PDSCH) in the first time slot and receiving the second paging data in the second PDSCH in the offset time slot.

3. The method as described in claim 1, wherein, The paging control information includes a first paging control section and a second paging control section that are both in the same paging situation.

4. The method of claim 3, wherein, The first paging control section and the second paging control section include different control information.

5. The method of claim 3, wherein, The first paging control unit and the second paging control unit are configured with the same quasi-coexistence (QCL) information.

6. The method of claim 3, wherein, The first paging control section includes a first time-domain resource assignment for the first paging data in the first time slot, and the second paging control section includes a second time-domain resource assignment for the second paging data in the offset time slot.

7. The method of claim 1, wherein, Receiving the paging control information further includes: receiving the paging control information based on whether the scheduled entity is in an idle mode or an inactive mode.

8. A scheduled entity for processing paging messages, comprising: Memory; transceiver; as well as Processor, wherein the processor and the memory are configured to: Paging control information that receives paging data in the downlink control information (DCI) of the physical downlink control channel (PDCCH); Process the time-domain resource allocation in the paging control information; as well as The paging data is received in the Physical Downlink Shared Channel (PDSCH) based on the time-domain resource assignment. The paging data includes shared paging data, which includes first paging data in a first time slot and second paging data in an offset time slot.

9. The scheduled entity as described in claim 8, wherein, The processor and the memory are configured to receive the first paging data in the first physical downlink shared channel (PDSCH) in the first time slot and to receive the second paging data in the second PDSCH in the offset time slot.

10. The scheduled entity as described in claim 8, wherein, The paging control information includes a first paging control section and a second paging control section that are both in the same paging situation.

11. The scheduled entity as claimed in claim 10, wherein, The first paging control section and the second paging control section include different control information.

12. The scheduled entity as described in claim 10, wherein, The first paging control unit and the second paging control unit are configured with the same quasi-coexistence (QCL) information.

13. The scheduled entity as described in claim 10, wherein, The first paging control section includes a first time-domain resource assignment for the first paging data in the first time slot, and the second paging control section includes a second time-domain resource assignment for the second paging data in the offset time slot.

14. The scheduled entity as described in claim 8, wherein, The processor and the memory are configured to receive paging control information based on whether the scheduled entity is in an idle or inactive mode.

15. A method for sharing paging messages among scheduled entities, comprising: The first paging control information of the paging message is received in the first time slot in the first downlink control information (DCI) of the first physical downlink control channel (PDCCH); The second paging control information of the paging message is received in the offset time slot in the second downlink control information (DCI) of the second physical downlink control channel (PDCCH); Process the time-domain resource allocation in the first paging control information and the second paging control information; as well as Paging data assigned to receive the paging message in the offset time slot based on the time domain resources in the Physical Downlink Shared Channel (PDSCH).

16. The method of claim 15, wherein, The first paging control information and the second paging control information are different.

17. The method of claim 15, wherein, Receiving the paging data includes: receiving a first portion of the paging data in a first physical downlink shared channel (PDSCH) in the first time slot and receiving a second portion of the paging data in a second PDSCH in the offset time slot.

18. The method of claim 15, wherein, The first paging control information and the second paging control information of the paging data are received based on the fact that the scheduled entity is in idle mode or inactive mode.

19. The method of claim 15, wherein, The time-domain resource assignments in the first paging control information and the second paging control information are processed simultaneously.

20. A scheduled entity for processing paging messages, comprising: Memory; transceiver; as well as Processor, wherein the processor and the memory are configured to: The first paging control information of the paging message is received in the first time slot in the first downlink control information (DCI) of the first physical downlink control channel (PDCCH); The second paging control information of the paging message is received in the offset time slot in the second downlink control information (DCI) of the second physical downlink control channel (PDCCH); Process the time-domain resource allocation in the first paging control information and the second paging control information; as well as Paging data assigned to receive the paging message in the offset time slot based on the time domain resources in the Physical Downlink Shared Channel (PDSCH).

21. The scheduled entity as described in claim 20, wherein, The first paging control information and the second paging control information are different.

22. The scheduled entity as described in claim 20, wherein, The processor and the memory are configured to receive a first portion of the paging data in a first physical downlink shared channel (PDSCH) in the first time slot and a second portion of the paging data in a second PDSCH in the offset time slot.

Images