Paging messages for forwarding by network node

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node can receive a paging message. The network node can send a paging repetition request for a parent network node to send a repetition of the paging message when sending a page to the network node. The network node can forward the paging message on one or more beams of the network node. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 934,162, filed on September 21, 2022, entitled “PAGING MESSAGES FORFORWARDING BY A NETWORK NODE” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for paging messages forwarded by a network node. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving a paging message. The method may include sending a paging repeat request for a parent network node to send a repeat of the paging message when sending a paging to the network node. The method may include forwarding the paging message on one or more beams of the network node.

[0008] Some aspects described herein relate to a method of wireless communication performed by a parent network node. The method may include sending a paging message to the network node. The method may include receiving a paging repeat request for repetition of the parent network node sending the paging message when sending the paging to the network node.

[0009] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a paging message. The one or more processors may be configured to: send a paging repeat request for a parent network node to send a paging message when sending a paging to the network node. The one or more processors may be configured to forward the paging message on one or more beams of the network node.

[0010] Some aspects described herein relate to a parent network node for wireless communication. The parent network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a paging message to the network node. The one or more processors may be configured to receive a paging repeat request for the parent network node to send a paging message repeatedly when sending a paging to the network node.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive a paging message. The set of instructions, when executed by one or more processors of the network node, may cause the network node to: send a paging repeat request for a parent network node to send a repeat of the paging message when sending a paging to the network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to: forward the paging message on one or more beams of the network node.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a parent network node. The instruction set, when executed by one or more processors of the parent network node, can cause the parent network node to send a paging message to a network node. The instruction set, when executed by one or more processors of the parent network node, can cause the parent network node to: receive a paging repeat request for repetition of the parent network node sending the paging message when sending a page to the network node.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a paging message. The apparatus may include components for sending a paging repeat request for a parent network node to send a repeat of the paging message when sending a paging to a network node. The apparatus may include components for forwarding the paging message on one or more beams of the network node.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a paging message to a network node. The apparatus may include means for receiving a paging repeat request for a parent network node to send a paging message repeatedly when sending a paging message to the network node.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a paging message procedure according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a paging message procedure according to the present disclosure.

[0024] Figure 6 is a diagram of an example associated with mapping time resources and frequency resources to beams of a network node according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of a paging message procedure according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process performed, for example, by a parent network node according to the present disclosure.

[0028] Fig.10 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0029] Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0030] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality other than the various aspects of the disclosure set forth herein or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claim.

[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or 5G and beyond (e.g., 6G) RATs.

[0033] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0034] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0035] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile network node 110 (e.g., a mobile network node).

[0036] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0037] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0038] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0039] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0040] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0041] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0042] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0044] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0045] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz), and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0046] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0047] In some aspects, the network node 110 (e.g., a forwarding node) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receive a paging message; send a paging repetition request for a parent network node to send a paging message when sending a page to the network node; and forward the paging message on one or more beams of the network node. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] In some aspects, the parent network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: send a paging message to a network node; and receive a paging repetition request for repetition of the parent network node sending the paging message when sending a paging message to the network node; Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0049] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0050] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0051] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing.

[0053] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0054] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as antennas). Figure 2 One or more antenna elements of one or more components in.

[0055] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 6 to 11 ) or any aspects of any of the methods described herein.

[0056] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 6 to 11 ) or any aspects of any of the methods described herein.

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with paging messages forwarded by a network node, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the network node includes: a component for receiving a paging message; a component for sending a paging repetition request for a parent network node to send a paging message when sending a paging to the network node; and / or a component for forwarding the paging message on one or more beams of the network node. The components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0059] In some aspects, the parent network node includes a component for sending a paging message to the network node. And / or a component for receiving a paging repetition request for repetition of the parent network node sending the paging message when sending the paging to the network node. The components for the parent network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0060] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0061] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0062] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NRBS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0063] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0064] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed independently. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of the decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0065] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0066] Each of these units (including CU 310, DU 330, RU 340) and near-RT RIC 325, non-RTRIC 315 and SMO framework 305) may include or be coupled to one or more interfaces, which are configured to receive or send signals, data or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0067] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0068] Each DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0069] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming or PRACH extraction and filtering, etc.) based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0070] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 335) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0071] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0072] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received at the SMO framework 305 or the non-RT RIC 315 from a non-network data source or from a network function. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0073] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0074] Figure 4 4 is a diagram illustrating an example 400 of a paging message process according to the present disclosure. Figure 4 , a network node may send a paging message to a mobile station (e.g., UE 120). The network node may send the paging message based at least in part on the mobile station being in an idle (e.g., RRC idle) mode or an inactive (e.g., RRC inactive) mode, etc. For example, the network node may have previously indicated that the mobile station was to be in an idle or inactive mode based at least in part on an amount of data communicated between the network node and the mobile station satisfying a threshold.

[0075] Based at least in part on being in an idle or inactive mode, the mobile station may conserve power resources based at least in part on having a reduced amount of resources for communicating with the network node. For example, the mobile station may not have uplink resources scheduled for communicating with the network node and may have periodic downlink resources to monitor for paging messages. The paging message may instruct the mobile station to wake up and send a random access channel (RACH) response to change to a connected mode for receiving communications from the network node.

[0076] The network node may operate multiple beams on which the network node sends paging messages. For example, the network node may send paging messages on a set of beams 405A, 405B, 405C, and 405D. In some networks, the network node may send paging messages on all operating beams, a subset of operating beams, or a single beam, etc. For example, the network node may send paging messages on one beam or on multiple beams based at least in part on knowledge of the location of the mobile station. The paging message may include one or more mobile stations to wake up to communicate with the network node (e.g., enter a connected mode).

[0077] The mobile station may receive via beam 405B and the network node may send a paging message via the beam, as shown by reference numeral 410. In some networks, the paging message may indicate that the mobile station is to wake up.

[0078] The mobile station may decode a physical downlink shared channel (PDSCH) or other types of information to find an identifier associated with the mobile station. For example, the mobile station may look for an inactive radio network temporary identifier (I-RNTI) or a 5G S temporary mobile subscriber identity (5G-S-TMSI) associated with the mobile station.

[0079] As indicated by reference numeral 415, the mobile station may send a RACH response (eg, to initiate a RACH procedure) based at least in part on receiving the paging message. For example, the mobile station may send a RACH response based at least in part on finding an identifier associated with the mobile station within the paging message.

[0080] Based at least in part on sending the RACH acknowledgement, the mobile station may transition to a connected mode.In the connected mode, the mobile station may receive communications for which the network node sent the paging message.

[0081] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0082] Figure 5 5 is a diagram illustrating an example 500 of a paging message process according to the present disclosure. Figure 5 , a parent network node may attempt to send a paging message to a mobile station (e.g., UE 120) via a network node (e.g., a relay, repeater, and / or forwarding node, etc.). The parent network node may send the paging message based at least in part on the mobile station being in an idle (e.g., RRC idle) mode or an inactive (e.g., RRC inactive) mode, etc. For example, the parent network node may have previously indicated that the mobile station was to be in an idle or inactive mode based at least in part on an amount of data communicated between the network node and the mobile station satisfying a threshold.

[0083] The parent network node may operate multiple beams on which the parent network node sends paging messages. For example, the parent network node may send paging messages on a set of beams 505A, 505B, 505C, and 505D. In some networks, the network node may send paging messages on all operating beams, a subset of operating beams, or a single beam, etc. For example, the parent network node may send paging messages on one beam or on multiple beams based at least in part on knowledge of the location of the mobile station. The paging message may include one or more mobile stations to wake up to communicate with the parent network node (e.g., enter a connected mode).

[0084] As indicated by reference numeral 510, a network node may receive a paging message from a parent network node. The network node may determine whether the paging message identifies a mobile station in coverage of the network node before attempting to forward the paging message, or may simply forward the paging message based at least in part on receiving the paging message from the parent network node.

[0085] The network node may operate multiple beams on which the network node sends paging messages. For example, the network node may support a mobile station, operate a mobile station, and / or communicate with a mobile station via a set of beams 515A, 515B, and 515C. However, the network node may not know which beam to use to forward the paging message to the mobile station. For example, the mobile station may be in an idle or inactive mode, where the mobile station does not provide uplink communication with the network node (e.g., via the network node with a parent network node), so the network node does not know which beam will reach the mobile station.

[0086] Based at least in part on having only one paging message to forward, the network node may select a beam from a set of beams 515A, 515B, and 515C to attempt to reach the mobile station with the paging message. As shown by reference numeral 520A, the network node may attempt to reach the mobile station by forwarding the paging message on beam 515A. As shown by reference numeral 520B, the network node may attempt to reach the mobile station by forwarding the paging message on beam 515B. As shown by reference numeral 520C, the network node may attempt to reach the mobile station by forwarding the paging message on beam 515C. In this example, the network node may have a 1 / 3 chance of reaching the mobile station and causing the mobile station to initiate a RACH procedure to connect with the parent network node, thereby receiving the communication for which the parent network node sent the paging message.

[0087] Based at least in part on the network node having a relatively low probability of correctly selecting a beam for forwarding the paging message, communications associated with the paging message may fail (e.g., based at least in part on failure to meet latency requirements) and / or the parent network node and / or the network node may consume network and power resources to repeat paging operations until the mobile station is successfully reached.

[0088] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0089] In some aspects described herein, a network node (e.g., a forwarding node, a relay, and / or a repeater) may send a paging repeat request to a parent node. The paging repeat request may indicate that a single paging message may not be sufficient for a network node (e.g., a network node transparent to a mobile station) to forward on all beams (e.g., downlink transmit beams) of the network node.

[0090] Based at least in part on the receipt of a paging repetition request by a parent network node (e.g., a gNB, CU, DU, or RU), the parent network node may comply with the paging repetition request and direct multiple paging signals (e.g., repetitions of a paging message) toward the network node. The network node may then forward the multiple paging signals via multiple beams of the network node.

[0091] Based at least in part on the network node receiving repetitions of paging messages for forwarding on multiple transmit beams, the network node has an increased likelihood of reaching the mobile station with the paging message. Based at least in part on reaching the mobile station with the paging message, communications associated with the paging message may be successful (e.g., based at least in part on meeting latency requirements and finding the mobile station being paged), and / or the parent network node and / or the network node may save network and power resources that may have been used to repeat paging operations until the mobile station is successfully reached.

[0092] Additionally or alternatively, the parent network node may increase a timer for paging failures based at least in part on receiving a paging repeat request. For example, based at least in part on receiving a paging repeat request, the parent network node may allow additional paging frames, for example to receive a reply from the paged mobile station based at least in part on a delay between sending a paging message and sending a repetition of the paging message. Based at least in part on increasing the timer for paging failures, the network node and the parent network node may save network resources that may have been used to provide paging messages to additional parent network nodes (e.g., gNB groups and / or tracking areas, among other examples) for sending paging messages in an increased coverage area.

[0093] In some aspects, the parent network node may send a paging message on multiple beams (e.g., one paging occasion and / or one paging message per beam). The network node receives the paging message on one of the multiple beams and forwards the paging message on one of the beams of the network node (e.g., a downlink transmit beam of the network node). If the network node reaches the associated mobile station via one of the beams of the network node, the mobile station may send a RACH response to the parent network node via the network node (e.g., a forwarding node) at the next available RACH occasion.

[0094] In some aspects, the network node may decode the paging message (e.g., before or after forwarding via a beam). Based at least in part on detecting that the paging message is a paging message (e.g., identifying characteristics of the paging message within the received signal), the network node may send a paging repeat request to the parent network node. Additionally or alternatively, based at least in part on detecting that the paging message is paging a mobile station that is expected to be within the coverage of the network node, the network node may send a paging repeat request to the parent network node. For example, the network node may decode the paging message to identify a list of mobile stations being paged. If (e.g., only if) at least one of the mobile stations being paged is expected to be within the coverage of the network node, the network node may then send the paging repeat request. The mobile station may be expected to be within the coverage of the network node based at least in part on the network node receiving communications from the mobile station within a recent time period and / or based at least in part on the network node forwarding an indication for the mobile station to enter an idle or inactive mode to the mobile station.

[0095] A paging repetition request may indicate a request to send multiple paging occasions (e.g., repetitions of a paging message) to a network node at a subsequent paging frame. The network node may send the paging repetition request via uplink control information (UCI) and / or a medium access control (MAC) control element (CE) based at least in part on receiving a paging message. The network node may send the paging repetition request via RRC signaling based at least in part on providing the paging repetition request in an initial configuration or providing an update to the initial configuration to a parent network node (e.g., before receiving a paging message). In some aspects, the parent network node may allocate resources (e.g., uplink grant) to the network node to send the paging repetition request. For example, a control channel (e.g., a physical downlink control channel (PDCCH)) carrying the paging message may indicate an allocation of resources for the network node to provide the paging repetition request to the parent network node.

[0096] In some aspects, the network node may ignore the paging repeat request based at least in part on receiving a RACH response from the mobile station (e.g., where the network node forwards the original paging message on a beam with coverage to reach the mobile station). The network node may ignore the paging repeat request by refraining from sending a repetition of the paging message on a subsequent paging frame.

[0097] In some aspects, the paging repeat request may indicate a number of requested paging occasions (e.g., repetitions of a paging message). For example, the paging repeat request may indicate that the number of paging occasions is equal to the number of active beams operated by the network node or one less than that number (e.g., N_repeater_beams-1, because one beam was used when forwarding the original paging message).

[0098] In some aspects, the paging repetition request may indicate a requested time between repetitions and / or paging occasions to allow the network node to switch between beams. The indication of the requested time may include an explicit indication of the requested time, capabilities of the network node associated with beam switching, and / or a time required by the network node to perform beam switching, etc.

[0099] In some aspects, the paging repetition request may indicate a request to suppress multiplexing of repetitions of a paging message with communications for other mobile stations within the coverage area of ​​the network node. For example, this may be based at least in part on a network node that does not support simultaneous transmission on multiple beams (e.g., multiple downlink transmit beams).

[0100] In some aspects, the network node may register with a parent network node. In this way, the parent network node may know that transmissions in the direction of the network node may be forwarded to the mobile station. Based at least in part on registering the network node with the parent network node, the network node may not need to send a paging repeat request after each paging message. For example, the network node may send a paging repeat request with registration information. In this way, the parent network node may send multiple repetitions of a paging message without first sending a single paging message and waiting to receive a paging repeat request for the paging message. In this way, the latency of the paging process may be improved.

[0101] In some aspects, a registration may be refreshed and / or updated (e.g., based at least in part on a changed configuration and / or setting of the network node, such as the number of active transmit beams, etc.). In some aspects, a network node may send a paging repeat request (e.g., a refresh and / or update of a registration) only by request from a parent network node (e.g., as part of a network-wide refresh announced by a system information block (SIB), etc.) after receiving any paging message, after a paging message that is a configured amount of time after the most recent paging repeat request (e.g., N radio frames from the most recent paging repeat request).

[0102] Figure 6 6 is a diagram of an example 600 associated with mapping time resources and frequency resources to beams of a network node according to the present disclosure. Figure 6 As shown in FIG, a network node (e.g., network node 110, IAB node, relay, forwarding node, relay, DU, and / or RU) may communicate with a parent network node (e.g., network node 110, IAB node, relay, forwarding node, relay, CU, DU, and / or RU) and a mobile station (e.g., UE 120). In some aspects, the network node, parent network node, and / or mobile station may be part of a wireless network (e.g., wireless network 100). The network node, parent network node, and / or mobile station may be in a Figure 6 The operations shown in have previously established a wireless connection. In some aspects, the parent network node may have sent an indication for the mobile station to enter an idle or inactive mode.

[0103] As indicated by reference numeral 605, the parent network node may send, and the network node may receive, configuration information. In some aspects, the network node may receive the configuration information via one or more of RRC signaling, one or more MAC CEs, and / or downlink control information (DCI), etc. In some aspects, the configuration information may include, among other things, an indication of one or more configuration parameters for selection by the network node (e.g., known to the network node and / or previously indicated by a parent network node or other network device) and / or explicit configuration information for the network node to use to configure the network node.

[0104] In some aspects, the configuration information may indicate that the network node is to send an indication of support for forwarding paging. In some aspects, the configuration information may indicate that the network node is to send information for a paging repetition request. In some aspects, the configuration information may indicate the type and / or amount of information to be provided to the parent network node.

[0105] The network node may configure itself based at least in part on the configuration information.In some aspects, the network node may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0106] As indicated by reference numeral 610, the network node may send and the parent network node may receive information for a paging repeat request. For example, the information for a paging repeat request may be a paging repeat request and / or may include one or more parameters for sending a subsequent paging repeat request.

[0107] As shown by reference numeral 615, the network node may receive a paging message. In some networks, the paging message may indicate that the mobile station is about to wake up. For example, a parent network node may receive or generate data for transmission to the mobile station. However, the mobile station is not in connected mode, so the parent network node sends a paging message to indicate that the mobile station is about to initiate a RACH procedure.

[0108] In some aspects, the network node may decode the paging message. For example, the network node may decode the paging message to identify the paging message as a paging message. Additionally or alternatively, the network node may decode the paging message to identify the UE being paged with the paging message. The network node may determine whether any of the UEs being paged with the paging message are expected to be within the coverage of the network node.

[0109] In some aspects, a paging message may include an allocation of resources for sending a paging repeat request.

[0110] As shown by reference numeral 620, the network node may forward the paging message. In some aspects, the network node may forward the paging message on one or more beams of the network node. For example, the network node may attempt to forward the paging message via one beam of the network node. Figure 6 As shown in , a paging message may not reach a mobile station based at least in part on a network node forwarding the paging message using a beam different from a beam directed to the mobile station.

[0111] As shown by reference numeral 625, the network node may send, and the parent network node may receive, a paging repeat request. For example, the network node may send a paging repeat request (e.g., for each received paging message) based at least in part on receiving a paging message prior to sending the paging repeat request. Alternatively, the network node may periodically send a paging repeat request based at least in part on receiving a paging message only after a certain amount of time has elapsed since the most recent paging repeat request (e.g., only after a timer has expired to allow a paging repeat request to be refreshed), or based at least in part on a request from a parent network node, etc. In some aspects, the network node may send a paging repeat request prior to receiving a paging message (e.g., in a periodic transmission and / or during configuration and / or an update to the configuration, such as using the information for paging repeat requests described in conjunction with reference numeral 610). In some examples, the paging repeat request may apply to multiple paging messages (e.g., to a configured number and / or an indicated number) for a certain period of time and / or until an update is sent, etc.

[0112] In some aspects, the network node may send a paging repeat request based at least in part on decoding a paging message. For example, the network node may send a paging repeat request based at least in part on identifying the paging message as a paging message. Additionally or alternatively, the network node may send a paging repeat request based at least in part on identifying mobile stations to be paged with the paging message to include mobile stations expected to be within a coverage area of ​​the network node. For example, the paging message may indicate paging to mobile stations within a coverage area of ​​the network node.

[0113] In some aspects, a paging repeat request may indicate a request for a parent network node to send a paging message repetition (e.g., paging occasion) when sending a paging to a network node. The paging repeat request may indicate the number of beams operated by the network node and / or the number of repetitions required for the network node to forward the paging message on a network node beam (e.g., all network node beams in the network node beam), etc. Additionally or alternatively, the paging repeat request may indicate a requested time gap between paging occasions or repetitions and / or a capability for beam switching, etc.

[0114] In some aspects, the network node may send a paging repeat request using resources allocated via a paging message and / or configured in another message. In some aspects, the network node may send a paging repeat request prior to forwarding a paging message, as described in conjunction with reference numeral 620.

[0115] In some aspects, the paging repeat request may indicate that the network node does not support one or more mobile stations for which the paging message is multiplexed. For example, the paging repeat request may indicate a request to suppress multiplexing communications with any mobile station within the coverage of the network node during resources used to forward the paging message. The network node may indicate the mobile stations within the coverage of the network node based at least in part on identifiers of the mobile stations within the coverage and / or based at least in part on a transmit beam of a parent network node used for communicating via the network node.

[0116] In some aspects, the parent network node may adjust a timer for a paging failure based at least in part on receiving a paging repeat request. For example, the parent network node may increase a timer (e.g., a duration of the timer) based at least in part on receiving a paging repeat request. In this way, the parent network node may increase the amount of time allowed before the network layer reports a paging failure. This may prevent escalation that may include multiple parent network nodes (e.g., RUs, CUs, and / or DUs) sending paging messages to increase coverage areas in an attempt to reach a mobile station.

[0117] The network node may receive, and the mobile station may send, a RACH acknowledgement, as indicated by reference numeral 630. For example, the network node may receive the RACH acknowledgement based at least in part on selecting a correct beam for forwarding the paging message.

[0118] As indicated by reference numeral 635, the network node may forward the RACH response to the parent network node. In some aspects, the network node may forward the RACH response after sending the paging repeat request. In some aspects, the network node may send the paging repeat request before receiving the RACH response.

[0119] As indicated by reference numeral 640, the network node may ignore the paging repetition request. In some aspects, the network node may ignore the paging repetition request based at least in part on receiving the RACH acknowledgement. For example, ignoring the paging request may include refraining from sending repetitions of the paging request after receiving the RACH acknowledgement.

[0120] As indicated by reference numeral 645, the network node may receive, and the parent network node may send, repetitions of the paging message (e.g., within a single paging frame). For example, the parent network node may send repetitions of the paging message based at least in part on failure to receive a RACH reply (e.g., based at least in part on the network node selecting an incorrect beam to forward the paging message) and / or based at least in part on receiving a paging repeat request.

[0121] In some aspects, repetitions of the paging message may include a number of repetitions requested by the network node, a number of times equal to the number of beams operated by the network node, or a number less than the number of beams operated by the network node (e.g., based at least in part on the network node having forwarded the paging request on the beam prior to sending the paging repetition request), etc.

[0122] In some aspects, the network node may receive the paging message during a paging frame subsequent to the paging message described in conjunction with reference numeral 615 (eg, a paging frame including the paging message).

[0123] In some aspects, the parent network node may send repetitions of a paging message without first sending the paging message described in conjunction with reference numeral 615. For example, the parent network node may receive information for a paging repetition request (e.g., the paging request itself), as well as an indication of the number of beams operated by the network node and / or the number of repetitions required for the network node to forward the paging message on the network node beams (e.g., all of the network node beams in the network node beams), etc. In this example, the repetition of the paging message may be referred to as a paging message.

[0124] As shown by reference numeral 650, the network node may forward a paging message (e.g., with duplication). In some aspects, the network node may forward a paging message on all beams operated by the network node (e.g., all transmit beams and / or all downlink beams). In some aspects, the network node may forward a paging message on all beams operated by the network node except one beam (e.g., excluding a beam that has been used to forward a paging message described in conjunction with reference numeral 620). In some aspects, the network node may forward a paging message on one or more beams of the network node during a subsequent paging frame (e.g., a frame subsequent to a frame that includes forwarding a paging message described in conjunction with reference numeral 620 and / or includes receiving a paging message described in conjunction with reference numeral 615).

[0125] As shown by reference numeral 655, the network node may receive and the mobile station may send a RACH response. For example, the network node may receive the RACH response based at least in part on reaching the mobile station via a beam of the network node. In some aspects, the RACH response may initiate a RACH procedure. In some aspects, the RACH response may include MSG1 or MSGA of the RACH procedure.

[0126] As indicated by reference numeral 660, the network node may forward, and the parent network node may receive, the RACH response.

[0127] Based at least in part on the network node receiving repetitions of the paging message for forwarding on multiple transmit beams, the network node has an increased likelihood of reaching the mobile station with the paging message. Based at least in part on reaching the mobile station with the paging message, communications associated with the paging message may be successful (e.g., based at least in part on meeting latency requirements), and / or the parent network node and / or the network node may save network and power resources that may have been used to repeat paging operations until successfully reaching the mobile station.

[0128] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0129] Figure 7 7 is a diagram illustrating an example 700 of a paging message process according to the present disclosure. Figure 7, a parent network node (e.g., a parent network node) may attempt to send a paging message to a mobile station (e.g., UE 120) via a network node (e.g., a relay, repeater, and / or forwarding node, etc.). The parent network node may send the paging message based at least in part on the mobile station being in an idle (e.g., RRC idle) mode or an inactive (e.g., RRC inactive) mode, etc. For example, the parent network node may have previously indicated that the mobile station was to be in an idle or inactive mode based at least in part on an amount of data communicated between the network node and the mobile station satisfying a threshold.

[0130] The parent network node may operate multiple beams on which the parent network node sends paging messages. For example, the parent network node may send paging messages on a set of beams 705A, 705B, 705C, and 705D. In some networks, the network node may send paging messages on all operating beams, a subset of operating beams, or a single beam, etc. For example, the parent network node may send paging messages on one beam or on multiple beams based at least in part on knowledge of the location of the mobile station. The paging message may include one or more mobile stations to wake up to communicate with the parent network node (e.g., enter a connected mode).

[0131] As shown by reference numeral 710, the network node may receive repetitions of a paging message from a parent network node. For example, the network node may receive multiple repetitions during multiple paging occasions of a single paging frame. The network node may determine whether the paging message identifies a mobile station in the coverage of the network node before attempting to forward the paging message, or may simply forward the paging message based at least in part on receiving the paging message from the parent network node.

[0132] The network node may operate multiple beams on which the network node sends paging messages. For example, the network node may support a mobile station, operate a mobile station, and / or communicate with a mobile station via a set of beams 715A, 715B, and 715C. However, the network node may not know which beam to use to forward the paging message to the mobile station. For example, the mobile station may be in an idle or inactive mode, where the mobile station does not provide uplink communication with the network node (e.g., via the network node and a parent network node), so the network node does not know which beam will reach the mobile station.

[0133] Based at least in part on multiple repetitions of the paging message having to be forwarded, the network node may forward the paging message on all active beams or a subset of the active beams of the network node. For example, the network node may forward the paging message on each beam in a set of beams 715A, 715B, and 715C in an attempt to reach the mobile station with the paging message. As shown by reference numeral 720A, the network node may attempt to reach the mobile station by forwarding the paging message on beam 715A. As shown by reference numeral 720B, the network node may attempt to reach the mobile station by forwarding the paging message on beam 715B. As shown by reference numeral 720C, the network node may attempt to reach the mobile station by forwarding the paging message on beam 715C. In this example, the network node reaches the mobile station, which may then initiate a RACH process to connect with the parent network node, thereby receiving the communication for which the parent network node sent the paging message.

[0134] Based at least in part on the network node receiving repetitions of the paging message for forwarding on multiple transmit beams, the network node has an increased likelihood of reaching the mobile station with the paging message. Based at least in part on reaching the mobile station with the paging message, communications associated with the paging message may be successful (e.g., based at least in part on meeting latency requirements), and / or the parent network node and / or the network node may save network and power resources that may have been used to repeat paging operations until successfully reaching the mobile station.

[0135] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0136] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a network node in accordance with the present disclosure. The example process 800 is an example in which a network node (eg, network node 110) performs operations associated with a paging message for forwarding by the network node.

[0137] like Figure 8 As shown in FIG. 8 , in some aspects, process 800 may include receiving a paging message (block 810). For example, a network node (e.g., using Fig.10 The communication manager 150 and / or receiving component 1002 depicted in FIG. 1004 may receive a paging message as described above.

[0138] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending a page repeat request for a parent network node to send a repeat of a paging message when sending a page to a network node (block 820). For example, a network node (e.g., using Fig.10The communication manager 150 and / or sending component 1004 depicted in FIG. 1004 may send a paging repeat request for a parent network node to send a repetition of a paging message when sending a page to the network node, as described above.

[0139] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include forwarding a paging message on one or more beams of a network node (block 830). For example, a network node (e.g., using Fig.10 The communication manager 150 and / or the sending component 1004 depicted in FIG. 1004 may forward the paging message on one or more beams of the network node, as described above.

[0140] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0141] In a first aspect, a network node comprises a repeater.

[0142] In a second aspect, alone or in combination with the first aspect, sending the paging repeat request is based at least in part on receiving a paging message prior to sending the paging repeat request.

[0143] In a third aspect, alone or in combination with one or more of the first and second aspects, sending a paging repeat request is based at least in part on a paging message indicating paging to a mobile station within coverage of the network node.

[0144] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 800 includes receiving a paging message with repetitions during a paging frame subsequent to the paging message, wherein forwarding the paging message on one or more beams of the network node includes sending the paging message with repetitions on multiple beams of the network node during a subsequent paging frame.

[0145] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a timer for paging failure associated with a paging message has a duration that is increased based at least in part on sending a paging repeat request.

[0146] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, receiving the paging message includes receiving the paging message and an uplink grant allocating resources for sending a paging repeat request.

[0147] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 800 includes receiving RACH responses from one or more mobile stations within coverage of a network node, and forwarding the RACH responses to a parent network node.

[0148] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, a paging repeat request indicates one or more of: the number of paging occasions or the number of repetitions of a paging message requested to be forwarded, the requested time gaps between paging occasions or repetitions, or the capability for beam switching.

[0149] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the paging repeat request indicates that the network node does not support one or more mobile stations for which the paging message is multiplexed.

[0150] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, sending a paging repeat request includes: sending a paging repeat request before receiving a paging message; sending a paging repeat request periodically; sending a paging repeat request for each received paging message; or sending a paging repeat request based at least in part on receiving a request for a paging repeat request.

[0151] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the paging repeat request is applied to a plurality of paging messages or to a certain period of time.

[0152] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0153] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a parent network node in accordance with the present disclosure. Example process 900 is an example in which a parent network node (eg, network node 110) performs operations associated with a paging message for forwarding by a network node.

[0154] like Fig. 9 As shown in FIG. 9 , in some aspects, process 900 may include sending a paging message to a network node (block 910). For example, a parent network node (e.g., using Fig.11 The communication manager 150 and / or the sending component 1104 depicted in FIG. 10A may send a paging message to a network node as described above.

[0155] like Fig. 9As further shown in FIG. 9 , in some aspects, process 900 may include receiving a paging repeat request for a parent network node to send a paging message repeatedly when sending a paging message to a network node (block 920). For example, a parent network node (e.g., using Fig.11 The communications manager 150 and / or receiving component 1102 depicted in FIG. 10A may receive a paging repeat request for a parent network node to send a repetition of a paging message when sending a page to the network node, as described above.

[0156] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0157] In a first aspect, a network node comprises a repeater.

[0158] In a second aspect, alone or in combination with the first aspect, receiving a paging repeat request is based at least in part on sending a paging message prior to receiving the paging repeat request.

[0159] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving a paging repeat request is based at least in part on a paging message indicating paging to a mobile station within a coverage area of ​​the network node.

[0160] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes sending a paging message with repetition during a paging frame following the paging message.

[0161] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a timer for paging failure associated with a paging message has a duration that is increased based at least in part on receiving a paging repeat request.

[0162] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, sending a paging message includes sending a paging message and an uplink grant allocating resources for sending a paging repeat request.

[0163] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 900 includes receiving, via the network node, a RACH response from one or more mobile stations within coverage of the network node.

[0164] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, a paging repetition request indicates one or more of: the number of paging occasions or the number of repetitions of a paging message requested to be forwarded, the requested time gaps between paging occasions or repetitions, or the capability for beam switching by a network node.

[0165] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the paging repeat request indicates that the network node does not support one or more mobile stations for which the paging message is multiplexed.

[0166] In a tenth aspect, alone or in combination with one or more of aspects one to nine, receiving a paging repeat request comprises: receiving a paging repeat request before sending a paging message; periodically receiving a paging repeat request; receiving a paging repeat request for each received paging message; or receiving a paging repeat request based at least in part on sending a request for a paging repeat request.

[0167] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the paging repeat request is applied to a plurality of paging messages or to a certain period of time.

[0168] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted in the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks of the blocks of the process 900 may be performed in parallel.

[0169] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a network node, or a network node may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1000 may include a communication manager 1008 (e.g., communication manager 150).

[0170] In some aspects, the apparatus 1000 may be configured to perform the Figure 6 to Figure 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The apparatus 1000 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0171] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0172] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0173] Receiving component 1002 can receive a paging message. Sending component 1004 can send a paging repetition request for repetitions of a parent network node sending a paging message when sending a paging to a network node. Sending component 1004 can forward the paging message on one or more beams of the network node.

[0174] The receiving component 1002 can receive a paging message with repetitions during a paging frame subsequent to the paging message, wherein forwarding the paging message on one or more beams of the network node includes sending the paging message with repetitions on multiple beams of the network node during the subsequent paging frame.

[0175] Receiving component 1002 can receive RACH responses from one or more mobile stations within coverage of the network node.

[0176] Transmitting component 1004 can forward the RACH response to a parent network node.

[0177] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.10 Two or more components shown in the figure may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig.10 Another set of components shown in the figure performs one or more functions.

[0178] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a parent network node, or a parent network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 1108 (e.g., communication manager 150).

[0179] In some aspects, the apparatus 1100 may be configured to perform the Figure 6 to Figure 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The apparatus 1100 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0180] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described parent network nodes.

[0181] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described parent network node. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0182] Transmitting component 1104 can transmit the paging message to the network node. Receiving component 1102 can receive a paging repeat request for repetition of a parent network node transmitting the paging message when transmitting the paging to the network node.

[0183] Transmitting component 1104 can transmit the paging message with repetitions during a paging frame subsequent to the paging message.

[0184] Receiving component 1102 can receive, via the network node, RACH responses from one or more mobile stations within coverage of the network node.

[0185] Fig.11 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set of component(s) may be described as being executable by Fig.11 Another collection of components shown performs one or more functions.

[0186] The following provides an overview of some aspects of the disclosure:

[0187] Aspect 1: A method of wireless communication performed by a network node, comprising: receiving a paging message; sending a paging repetition request for a parent network node to repeat sending the paging message when sending a paging to the network node; and forwarding the paging message on one or more beams of the network node.

[0188] Aspect 2: The method according to aspect 1, wherein the network node comprises a relay.

[0189] Aspect 3: The method according to any one of aspects 1 to 2, wherein sending the paging repeat request is based at least in part on receiving the paging message before sending the paging repeat request.

[0190] Aspect 4: The method according to aspect 3, wherein sending the paging repeat request is based at least in part on the paging message indicating paging to mobile stations within the coverage area of ​​the network node.

[0191] Aspect 5: The method according to any one of Aspects 3 to 4 further includes: receiving the paging message with repetitions during a paging frame following the paging message, wherein forwarding the paging message on the one or more beams of the network node includes sending the paging message with repetitions on multiple beams of the network node during a subsequent paging frame.

[0192] Aspect 6: The method according to any one of aspects 1 to 5, wherein a timer for paging failure associated with the paging message has a duration that is increased based at least in part on sending the paging repeat request.

[0193] Aspect 7: The method according to any one of aspects 1 to 6, wherein receiving the paging message includes: receiving the paging message and an uplink grant allocating resources for sending the paging repeat request.

[0194] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: receiving a random access channel (RACH) response from one or more mobile stations within the coverage of the network node; and forwarding the RACH response to the parent network node.

[0195] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the paging repetition request indicates one or more of the following: the number of paging occasions or repetitions of the paging message requested to be forwarded, the requested time gap between the paging occasions or the repetitions, or the capability for beam switching.

[0196] Aspect 10: The method according to any one of aspects 1 to 9, wherein the paging repetition request indicates that the network node does not support one or more mobile stations for which multiplexing with the paging message is targeted.

[0197] Aspect 11: A method according to any one of Aspects 1 to 10, wherein sending the paging repeat request comprises: sending the paging repeat request before receiving the paging message; sending the paging repeat request periodically; sending the paging repeat request for each received paging message; or sending the paging repeat request based at least in part on receiving a request for the paging repeat request.

[0198] Aspect 12: The method according to any one of aspects 1 to 11, wherein the paging repetition request is applied to multiple paging messages or to a certain time period.

[0199] Aspect 13: A method of wireless communication performed by a parent network node, comprising: sending a paging message to a network node; and receiving a paging repeat request for the parent network node to repeat sending the paging message when sending a paging to the network node.

[0200] Aspect 14: The method according to aspect 13, wherein the network node comprises a relay.

[0201] Aspect 15: The method according to any one of aspects 13 to 14, wherein receiving the paging repeat request is based at least in part on sending the paging message before receiving the paging repeat request.

[0202] Aspect 16: The method of aspect 15, wherein receiving the paging repeat request is based at least in part on the paging message indicating paging to mobile stations within coverage of the network node.

[0203] Aspect 17: The method according to any one of Aspects 15 to 16 further includes: sending the paging message with repetition during a paging frame following the paging message.

[0204] Aspect 18: The method according to any one of aspects 13 to 17, wherein a timer for paging failure associated with the paging message has a duration that is increased based at least in part on receiving the paging repeat request.

[0205] Aspect 19: The method according to any one of aspects 13 to 18, wherein sending the paging message comprises: sending the paging message and an uplink grant allocating resources for sending the paging repeat request.

[0206] Aspect 20: The method according to any one of aspects 13 to 19 further comprises: receiving, via the network node, a random access channel (RACH) response from one or more mobile stations within the coverage of the network node.

[0207] Aspect 21: A method according to any one of Aspects 13 to 20, wherein the paging repetition request indicates one or more of the following: the number of paging occasions or the number of repetitions of the paging message requested to be forwarded, the requested time gaps between the paging occasions or the repetitions, or the capability for beam switching by the network node.

[0208] Aspect 22: The method according to any one of aspects 13 to 21, wherein the paging repetition request indicates that the network node does not support one or more mobile stations for which multiplexing with the paging message is targeted.

[0209] Aspect 23: A method according to any one of Aspects 13 to 22, wherein receiving the paging repeat request includes: receiving the paging repeat request before sending the paging message; periodically receiving the paging repeat request; receiving the paging repeat request for each received paging message; or receiving the paging repeat request based at least in part on sending a request for the paging repeat request.

[0210] Aspect 24: The method according to any one of aspects 13 to 23, wherein the paging repetition request is applied to multiple paging messages or to a certain time period.

[0211] Aspect 25: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 24.

[0212] Aspect 26: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 24.

[0213] Aspect 27: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 24.

[0214] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 24.

[0215] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 24.

[0216] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0217] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to specific software codes herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0218] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0219] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0220] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A network node for wireless communication, comprising: Memory; and one or more processors configured, based at least in part on the information stored in the memory, to: Receive paging messages; sending a paging repeat request for a parent network node to send a repeat of the paging message when sending a paging message to the network node; as well as The paging message is forwarded on one or more beams of the network node. The network node according to claim 1 , wherein the network node comprises a repeater.

3. The network node of claim 1, wherein sending the paging repeat request is based at least in part on receiving the paging message prior to sending the paging repeat request.

4. The network node of claim 3, wherein sending the paging repeat request is based at least in part on the paging message indicating paging to mobile stations within coverage of the network node.

5. The network node of claim 3, wherein the one or more processors are further configured to: receiving the paging message with repetitions during a paging frame following the paging message, Wherein, in order to forward the paging message on the one or more beams of the network node, the one or more processors are configured to send the paging message with repetitions on multiple beams of the network node during a subsequent paging frame.

6. The network node of claim 1, wherein a timer for paging failure associated with the paging message has a duration that is increased based at least in part on sending the paging repeat request.

7. The network node of claim 1 , wherein to receive the paging message, the one or more processors are configured to: The paging message and an uplink grant allocating resources for sending the paging repeat request are received.

8. The network node of claim 1, wherein the one or more processors are further configured to: receiving a random access channel (RACH) response from one or more mobile stations within the coverage area of ​​the network node; and The RACH response is forwarded to the parent network node.

9. The network node of claim 1 , wherein the paging repetition request indicates one or more of: the number of paging occasions or the number of repetitions of the paging message requested to be forwarded, the requested time gap between the paging occasions or the repetitions, or Capability for beam switching.

10. The network node of claim 1, wherein the paging repeat request indicates that the network node does not support one or more mobile stations for which the paging message is multiplexed.

11. The network node of claim 1 , wherein to send the paging repetition request, the one or more processors are configured to: sending the paging repeat request before receiving the paging message; periodically sending the paging repeat request, sending said paging repeat request for each received paging message, or The paging repeat request is sent based at least in part on receiving a request for the paging repeat request.

12. The network node of claim 1, wherein the paging repetition request applies to a plurality of paging messages or to a certain time period.

13. A parent network node for wireless communication, comprising: Memory; and one or more processors configured, based at least in part on the information stored in the memory, to: Sending a paging message to a network node; as well as A paging repeat request is received for a parent network node to send a repetition of the paging message when sending a paging to the network node.

14. The parent network node of claim 13, wherein the network node comprises a repeater.

15. The parent network node of claim 13, wherein receiving the paging repeat request is based at least in part on sending the paging message prior to receiving the paging repeat request.

16. The parent network node of claim 15, wherein receiving the paging repeat request is based at least in part on the paging message indicating paging to mobile stations within a coverage area of ​​the network node.

17. The parent network node of claim 15, wherein the one or more processors are further configured to: The paging message with repetitions is sent during a paging frame following the paging message.

18. The parent network node of claim 13, wherein a timer for paging failure associated with the paging message has a duration that is increased based at least in part on receiving the paging repeat request.

19. The parent network node of claim 13, wherein to send the paging message, the one or more processors are configured to: The paging message and an uplink grant allocating resources for sending the paging repeat request are sent.

20. The parent network node of claim 13, wherein the one or more processors are further configured to: A random access channel (RACH) response is received via the network node from one or more mobile stations within the coverage of the network node.

21. The parent network node of claim 13, wherein the paging repetition request indicates one or more of: the number of paging occasions or the number of repetitions of the paging message requested to be forwarded, the requested time gap between the paging occasions or the repetitions, or A capability for beam switching by the network node.

22. The parent network node of claim 13, wherein the paging repeat request indicates that the network node does not support one or more mobile stations for which the paging message is multiplexed.

23. The parent network node of claim 13, wherein to receive the paging repetition request, the one or more processors are configured to: receiving the paging repeat request before sending the paging message; periodically receiving the paging repeat request, receiving said paging repeat request for each received paging message, or The paging repeat request is received based at least in part on sending a request for the paging repeat request.

24. The parent network node of claim 13, wherein the paging repetition request applies to a plurality of paging messages or to a certain time period.

25. A method of wireless communication performed by a network node, comprising: Receive paging messages; sending a paging repeat request for a parent network node to send a repeat of the paging message when sending a paging message to the network node; as well as The paging message is forwarded on one or more beams of the network node.

26. The method of claim 25, wherein sending the paging repeat request is based at least in part on receiving the paging message prior to sending the paging repeat request.

27. The method of claim 25, wherein receiving the paging message comprises: The paging message and an uplink grant allocating resources for sending the paging repeat request are received.

28. A method of wireless communication performed by a parent network node, comprising: Sending a paging message to a network node; as well as A paging repeat request is received for a parent network node to send a repetition of the paging message when sending a paging to the network node.

29. The method of claim 28, wherein receiving the paging repeat request is based at least in part on sending the paging message prior to receiving the paging repeat request.

30. The method of claim 28, wherein sending the paging message comprises: The paging message and an uplink grant allocating resources for sending the paging repeat request are sent.

Images