Method and apparatus for handling paging problem of ue in poor coverage

Abstract

Systems and methods for providing paging of a user equipment (UE) in poor network coverage are disclosed. In one embodiment, a method performed by a UE includes monitoring for a notification alert of a page during a time window having a configured length T_nw, the time window starting a time offset T_o before a periodically recurring page opportunity in which the UE is configured to monitor for an incoming page, and as a result of the monitoring, detecting the notification alert during the time window. As a result of the notification alert, the UE can be moved to a location having improved signal strength or quality (e.g., from a user's pocket), thereby enabling the UE to receive a page message.

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application serial number 63 / 613,648, filed on December 21, 2023, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to paging in cellular communication systems. Background Technology

[0004] In 3GPP Release 8, the Evolved Packet System (EPS) was specified. EPS is based on the Long Term Evolution (LTE) radio network and the Evolved Packet Core (EPC). It was initially designed to provide voice and mobile broadband (MBB) services but has been continuously developed to broaden its capabilities. Since Release 13, Narrowband Internet of Things (NB-IoT) and LTE for Machine-Type Communications (LTE-M) have been part of the LTE specification, and connectivity to Massive Machine-Type Communications (mMTC) services is provided.

[0005] Release 15 of 3GPP specified the first version of the 5G System (5GS). This is a next-generation radio access technology designed to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and mMTC. 5G includes a new radio (NR) access layer interface and a 5G core network (5GC). The NR physical layer and higher layers reuse parts of the LTE specification and add necessary components as needed for new use cases. One such component is the introduction of a complex framework for beamforming and beam management to extend support for 3GPP technologies to frequency ranges exceeding 6 GHz.

[0006] In Release 15, 3GPP initiated work to prepare NR for operation in Non-Land Networks (NTNs). This work was carried out within the research project "Supporting NR for Non-Land Networks". In Release 16, work to prepare NR for operation in NTN networks continued through the research project "Solutions for Supporting NR for Non-Land Networks". Meanwhile, interest in adapting NB-IoT and LTE-M for operation in NTNs grew. Therefore, 3GPP Release 17 specified support for operating NB-IoT, LTE-M, and NR on NTNs, and Release 18 continued with further enhancements.

[0007] The following sections provide brief background descriptions on some of the relevant topics covered in this disclosure.

[0008] In 3GPP, NTN includes both satellite communications and communications using High Altitude Platforms (HAPS). This section focuses on satellite communications, but the descriptions provided can also be applied to HAPS networks. Satellite radio access networks typically include the following components:

[0009] Satellite, referring to a spaceborne platform;

[0010] Ground gateways, depending on the architecture chosen, connect satellites to base stations or the core network;

[0011] Feeder link, which refers to the link between the gateway and the satellite; and

[0012] Access link refers to the link between a satellite and a user equipment (UE).

[0013] Depending on their orbital altitude, satellites can be classified as low Earth orbit (LEO), medium Earth orbit (MEO), or geostationary Earth orbit (GEO) satellites:

[0014] LEO: Typical altitude range is 250 - 1,500 km, and orbital period range is 90 - 120 minutes;

[0015] MEO: Typical altitude range is 5,000 - 25,000 km, and orbital period range is 3 - 15 hours;

[0016] GEO: The altitude is approximately 35,786 km, and the orbital period is 24 hours.

[0017] Communication satellites typically generate multiple beams over a given area. The coverage area (footprint) of a beam is usually elliptical and is traditionally considered a small cell. The coverage area is often also referred to as a spot beam. The coverage area can move across the Earth's surface as the satellite moves, or it can be fixed to the ground using some beam pointing mechanism that the satellite uses to compensate for its motion. The size of a spot beam depends on the system design and can range from tens of kilometers to thousands of kilometers.

[0018] Figure 1 An example architecture of a satellite network with a bend transponder is shown. The elevation angle of the service link shown is important because it affects the distance between the satellite and the device, as well as the satellite's speed relative to the device.

[0019] In 5G, NR NTN coverage presents a challenge due to the significant distance between the satellite carrying the 5G gNodeB (gNB) and the UE receiving gNB transmissions on the ground. One suggestion to overcome this coverage issue is to introduce a robust notification channel, designed to support extended coverage and operate at low signal-to-noise ratio (SNR). This channel can be sent before downlink paging to alert the UE user that an incoming paging is expected soon. Upon receiving this alert, the user moves their UE to a better location (e.g., removes it from their pocket) to ensure the UE is in a better SNR condition sufficient to support paging reception.

[0020] exist Figure 2 The diagram illustrates the overall 5G Radio Access Network (RAN) (also known as Next Generation RAN (NG-RAN)) architecture. As shown, NG-RAN includes gNBs connected to the 5GC. gNBs may also have connections (Xn-C) with other gNBs. A gNB may include a gNB Central Unit (CU) and one or more gNB Distributed Units (gNB-DUs) connected to the gNB-CU via corresponding F1 interfaces.

[0021] exist Figure 3 The diagram illustrates a gNB with a separated user plane (UP) / control plane (CP) architecture. As shown, the gNB CU is divided into gNB-CU-CP and one or more gNB-CU-UPs. The gNB-CU hosts the control plane portion of the Radio Resource Control (RRC) layer and the Packet Data Convergence Protocol (PDCP) layer, while the gNB-DU hosts the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical (PHY) layer.

[0022] For UEs in RRC idle mode, a paging procedure exists. This paging procedure is used to notify the UE in RRC idle mode of incoming data or calls in order to initiate RRC connection establishment. For UEs in RRC inactive mode, a RAN paging procedure exists, which triggers the UE to reactivate its temporarily suspended connection. This is typically used to optimize latency and save power. Summary of the Invention

[0023] A system and method for providing paging for a user equipment (UE) in poor network coverage are disclosed. In one embodiment, a method performed by the UE includes: monitoring a paging notification alarm during a time window of configured length T_nw, the time window initiating a time offset T_o before the UE is configured to monitor periodically recurring paging opportunities for incoming paging; and detecting a notification alarm during the time window as a result of the monitoring. As a result of the notification alarm, the UE can be moved to a location with improved signal strength or quality (e.g., removed from the user's pocket), thereby enabling the UE to receive paging messages.

[0024] In one embodiment, monitoring paging notification alarms during the time window includes monitoring paging notification alarms on a notification channel using one or more robust physical layer transmission parameters during the time window. In one embodiment, the one or more robust physical layer transmission parameters include a modulation order not greater than a specific modulation order threshold, a code rate not greater than a specific code rate threshold, and / or a transmission power higher than a specific power threshold. In one embodiment, the UE obtains the information based on predefined information or by receiving information about time and frequency resources used for monitoring the notification channel in a broadcast channel.

[0025] In one embodiment, the method further includes sending a receipt acknowledgment of the notification alarm to a network node. In one embodiment, sending the receipt acknowledgment of the notification alarm includes sending the receipt acknowledgment of the notification alarm upon receiving user input from the UE confirming that the user has received the notification alarm. In another embodiment, sending the receipt acknowledgment of the notification alarm includes sending the receipt acknowledgment of the notification alarm when the UE autonomously detects that the UE has moved to a location with improved signal strength or quality. In one embodiment, sending the receipt acknowledgment of the notification alarm includes sending a configured Physical Random Access Channel (PRACH) preamble or transmission indication during or after the connection establishment process.

[0026] In one embodiment, the method further includes: monitoring paging messages in the paging opportunity after receiving the notification alarm.

[0027] In one embodiment, during a paging transmission window of length T_pw, after the expiration of T_o, periodically recurring paging opportunities are repeated with a shortened period.

[0028] In one embodiment, the method further includes sending a notification alarm to a network node indicating that the UE supports paging.

[0029] In one embodiment, the method further includes sending information to the network node suggesting the length T_nw of the configuration for the time window and the value of the time offset T_o.

[0030] In one embodiment, the method further includes: receiving information from a network node about the length T_nw of the configuration for the time window and the time offset T_o.

[0031] A corresponding embodiment of the UE is also disclosed. In one embodiment, a UE is adapted to: monitor paging notification alarms during a time window of configured length T_nw, the time window initiating a time offset T_o before the UE is configured to monitor periodically recurring paging opportunities of incoming paging; and, as a result of the monitoring, detect notification alarms during the time window.

[0032] In another embodiment, a UE includes: a communication interface including a transmitter and a receiver; and processing circuitry associated with the communication interface. The processing circuitry is configured such that the UE: monitors for paging notification alarms during a time window of configured length T_nw, the time window initiating a time offset T_o before the UE is configured to monitor periodically recurring paging opportunities of incoming paging; and, as a result of the monitoring, detects notification alarms during the time window.

[0033] Embodiments of network nodes and their operating methods are also disclosed. In one embodiment, a method performed by a first network node includes: sending a paging notification alarm to a user equipment (UE) during a time window of configured length T_nw, the time window initiating a time offset T_o before the UE is configured to monitor periodically recurring paging opportunities for incoming paging. The method further includes: sending a paging message to the UE during a paging opportunity after sending the notification alarm.

[0034] In one embodiment, sending the notification alarm during the time window includes sending the notification alarm on a notification channel using one or more robust physical layer transmission parameters during the time window. In one embodiment, the one or more robust physical layer transmission parameters include a modulation order not greater than a specific modulation order threshold, a code rate not greater than a specific code rate threshold, and / or a transmission power higher than a specific power threshold. In one embodiment, information regarding the time and frequency resources of the notification channel that the UE wants to monitor is predefined or sent by the first network node in a broadcast channel.

[0035] In one embodiment, the method further includes: receiving a reception acknowledgment of the notification alarm from the UE before sending the paging message. In one embodiment, receiving the reception acknowledgment of the notification alarm includes: receiving a configured PRACH preamble or reception indication from the UE during or after the connection establishment process.

[0036] In one embodiment, sending the paging message includes: after sending the notification alarm and receiving the acceptance confirmation of the notification alarm from the UE, sending the paging message to the UE during the paging opportunity.

[0037] In one embodiment, during a paging transmission window of length T_pw, after the expiration of T_o, periodically recurring paging opportunities are repeated with a shortened period.

[0038] In one embodiment, the method further includes: receiving information from the UE indicating that the UE supports paging.

[0039] In one embodiment, the first network node is a central unit (CU) of a radio access network (RAN) node, and sending the paging notification alarm to the UE includes: sending a notification alarm message about the notification alarm to be sent to the UE to a distributed unit (DU) of the RAN node, and sending the paging message to the UE includes: sending the paging message to the UE via the DU of the RAN node. In one embodiment, the method further includes: receiving information from another network node indicating that the UE supports paging. In one embodiment, the other network node is a core network node, and receiving the information indicating that the UE supports paging includes: receiving a paging-related message including the information indicating that the UE supports paging. In one embodiment, the method further includes: sending an initial paging message to the UE via the DU of the RAN node; detecting a paging failure related to the initial paging message for the UE; and determining, in response to detecting the paging failure, that the notification alarm should be sent to the UE.

[0040] In one embodiment, the first network node is a DU of the RAN node.

[0041] In one embodiment, the first network node is a RAN node or a CU of the RAN node. In one embodiment, the method further includes: receiving a notification alarm from a core network node, the notification alarm indicating that the notification alarm is to be sent to the UE.

[0042] In one embodiment, the method further includes: receiving from the UE information about the length T_nw of the configuration proposed for the time window and the value of the time offset T_o.

[0043] In one embodiment, the method further includes sending information to the UE about the length T_nw of the configuration for the time window and the time offset T_o.

[0044] A corresponding embodiment of the first network node is also disclosed. In one embodiment, a first network node is adapted to: send a paging notification alarm to the UE, the notification alarm being sent during a time window having a configured length T_nw, the time window starting with a time offset T_o before the UE is configured to monitor periodically recurring paging opportunities of incoming paging. The first network node is further adapted to: after sending the notification alarm, send a paging message to the UE during a paging opportunity.

[0045] In one embodiment, a first network node includes processing circuitry configured to cause the first network node to: send a paging notification alarm to a UE, the notification alarm being sent during a time window having a configured length T_nw, the time window initiating a time offset T_o before the UE is configured to monitor periodically recurring paging opportunities for incoming paging. The processing circuitry is further configured to cause the first network node to: after sending the notification alarm, send a paging message to the UE during a paging opportunity.

[0046] In one embodiment, a method performed by a second network node includes sending information to a first network node regarding a notification alarm for paging of the UE.

[0047] In one embodiment, the method further includes: determining a notification alarm procedure to be applied to the UE before sending a paging message. In one embodiment, determining to apply the notification alarm procedure to the UE includes: determining that the UE is in poor network coverage.

[0048] In one embodiment, the first network node is the DU of the RAN node, and the second network node is the CU of the RAN node.

[0049] In one embodiment, the first network node is a RAN node and the second network node is a CN node.

[0050] In one embodiment, the first network node is a first RAN node, and the second network node is a second RAN node.

[0051] A corresponding embodiment of the second network node is also disclosed. In one embodiment, a second network node is adapted to send information about a notification alarm for paging of the UE to a first network node.

[0052] In one embodiment, a second network node includes processing circuitry configured to cause the second network node to send information about a notification alarm for paging of the UE to the first network node. Attached Figure Description

[0053] Several aspects of this disclosure are illustrated in conjunction with the accompanying drawings, which form a part of this specification, and together with the specification serve to explain the principles of this disclosure.

[0054] Figure 1 An example architecture of a satellite network with a bend transponder is shown;

[0055] Figure 2 The overall fifth-generation (5G) radio access network (RAN) (also known as next-generation RAN (NG-RAN)) architecture is shown;

[0056] Figure 3 The separate gNodeB (gNB) architecture is shown;

[0057] Figure 4 The temporal relationship between paging and the new notification alerts disclosed herein is shown;

[0058] Figure 5 A paging message is shown that is sent after the user confirms receipt of a downlink notification alarm, according to an embodiment of the present disclosure;

[0059] Figure 6 A paging message is shown according to an embodiment of the present disclosure after a user equipment (UE) detects improved signal strength or quality and autonomously acknowledges receipt of a downlink notification alarm.

[0060] Figure 7 Example processes according to embodiments of the present disclosure are shown;

[0061] Figure 8 A new F1AP procedure for “notifying alarms” according to an embodiment of the present disclosure is shown. In one example, the procedure is a new procedure added to 3GPP TS 38.473.

[0062] Figure 9 An embodiment according to this disclosure is shown in Figure 8 An example of a "Notification Alarm" message on F1AP;

[0063] Figure 10An example is shown of reusing paging messages according to embodiments of this disclosure to instruct the gNB-DU to send a notification alarm to the UE. This could be used for sending Figure 8 The mechanism for issuing notification and alarm messages;

[0064] Figure 11 Example processes according to embodiments of the present disclosure are shown;

[0065] Figure 12 An example of a new notification alarm message in TS 38.413 according to an embodiment of this disclosure is shown, wherein the CN (e.g., AMF) includes the number of attempts that the NG-RAN node should use to send a notification alarm to the UE, other auxiliary information, UE capabilities, etc.

[0066] Figure 13 Example processes according to embodiments of the present disclosure are shown;

[0067] Figure 14A An example of a novel notification alarm procedure according to an embodiment of the present disclosure is shown, which may, for example, be added to 3GPP TS 38.423;

[0068] Figure 14B It shows Figure 14A Example implementation of RAN notification alarm messages;

[0069] Figure 15 Examples of using existing procedures (e.g., RAN paging) in TS 38.423s according to embodiments of this disclosure are shown;

[0070] Figure 16 Processes according to at least some embodiments of the present disclosure are illustrated;

[0071] Figure 17 Examples of communication systems according to some embodiments of this disclosure are shown;

[0072] Figure 18 A UE according to some embodiments of this disclosure is shown;

[0073] Figure 19 Network nodes according to some embodiments of this disclosure are shown;

[0074] Figure 20 This is a block diagram illustrating a virtualized environment in which the functionality implemented by some embodiments of the present disclosure can be virtualized; and

[0075] Figure 21 Examples of the ability to instruct the network to process notification alarms are shown, with alternative 1: via RRC, alternative 2: via NAS, and alternative 3: via UDM / subscription. Detailed Implementation

[0076] The embodiments described below illustrate information that enables those skilled in the art to practice the embodiments and demonstrate the best mode for practicing the embodiments. By reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and recognize the application of these concepts not specifically mentioned herein. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0077] Some embodiments conceived herein will now be described more fully with reference to the accompanying drawings. These embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0078] Summary

[0079] As used herein, the term "gNodeB (gNB)" or "evolved NodeB (eNB)" can refer to any type of logical or physical radio network node, radio access node, or radio access network (RAN) node. Radio network nodes can communicate with user equipment (UE) using radio signals. Examples of radio network nodes are base stations, access points, transmit and receive points (TRPs), integrated access and backhaul (IAB) nodes, etc. Examples of radio signals are physical signals that do not contain higher-layer information and physical channels that do contain higher-layer information. Examples of physical signals are synchronization signal blocks (SSBs), channel state information reference signals (CSI-RS), positioning reference signals (PRS), sounding reference signals (SRS), demodulation reference signals (DMRS), etc. Examples of physical channels are physical broadcast channels (PBCHs), physical downlink shared channels (PDSCHs), physical downlink control channels (PDCCHs), physical uplink shared channels (PUSCHs), physical uplink control channels (PUCHs), random access channels (RACHs), etc.

[0080] As used herein, the terms “gNB-Central Unit (CU)” or “eNB-CU” can refer to any type of logical or physical radio network node or radio access node or RAN node that contains a Central Unit (CU) (which may also be referred to herein as a Control Unit). The CU of a radio access node hosts or manages higher-level protocols such as Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), etc.

[0081] As used herein, the terms "gNB-Distributed Unit (DU)" or "eNB-DU" can refer to any type of logical or physical radio network node, radio access node, or RAN node that contains a Distributed Unit (DU). The DU of a radio access node hosts or manages low-level protocols such as Radio Link Control (RLC), Media Access Control (MAC), physical layer, etc.

[0082] As used herein, the term "core network (CN)" can refer to any type of logical or physical radio network node or radio access node that manages or performs core network functions. Examples of CNs (or CN nodes) are Access and Mobility Management Functions (AMFs), Mobility Management Entities (MMEs), etc.

[0083] There are specific challenges in receiving paging for UEs in poor coverage. As discussed in the "Background Technology" section above, one proposal to overcome the coverage problem of New Radio (NR) Non-Terrestrial Networks (NTNs) is to introduce a robust notification channel that can be sent before downlink paging to alert the UE user that an incoming paging is expected soon. The first problem with the proposed robust notification channel is that the time between receiving the notification channel and the subsequent paging transmission is unknown. This means that the user could be notified to move their UE to a location with a better signal-to-noise ratio (SNR), but the subsequent paging might be missed because the user reacts too slowly. The second problem is that paging is a core network control function, and the solutions outlined for the proposed robust notification channel require RAN-CN signaling that is not currently defined. Paging is used in many use cases, and it is possible, for example, that the notification channel is only applicable to a subset of these use cases.

[0084] Specific aspects and embodiments of this disclosure can provide solutions to these or other challenges. Embodiments of the systems and methods disclosed herein provide solutions to support paging for UEs in poor coverage.

[0085] Embodiments of solutions for UE monitoring and detecting notification alarms for upcoming paging (e.g., on a robust notification channel) are disclosed. Embodiments relating to the signaling effects of network-sent notification alarms and subsequent paging are also disclosed. These solutions are applicable to UEs in idle states (e.g., RRC idle) and inactive states (e.g., RRC inactive).

[0086] In one embodiment, a process is provided for exchanging new signaling messages between a CN node (e.g., an AMF) and a RAN node (e.g., a gNB, gNB-CU). For example, when a CN node detects that a UE has not received a paging message, it sends a request or indication to a RAN node (e.g., an NG-RAN node, such as a gNB, gNB-CU in a split RAN architecture) to send a "notification alarm" message to the UE.

[0087] In another embodiment, a process is provided for exchanging new signaling messages between NG-RAN node-CUs (e.g., RAN paging) and between gNB-CUs and gNB-DUs in a separate RAN architecture. For example, when a gNB-CU detects that a particular UE is in poor network coverage (e.g., the UE has not established a connection after sending at least a certain number of paging messages), it requests the gNB-DU to send a "notification alarm" message to the UE on a notification channel before sending a normal paging message.

[0088] In embodiments of this disclosure, the CN node and / or RAN node detect, based on one or more criteria, that the UE has not received or is unable to receive paging messages. Based on this detection, the CN node and / or RAN node initiates a process that enables the transmission of a notification alarm message to the UE. For example, receiving a notification alarm message at the UE may request the subscriber (i.e., the UE's user) to move to a location where the UE can receive paging (e.g., in an open area). Further details are provided below.

[0089] Specific embodiments can provide one or more of the following technical advantages. Embodiments of the solutions described herein enable a UE in poor coverage to be paged, for example, using an NTN. Embodiments of this disclosure enable a UE in poor coverage to establish a call.

[0090] A description of a notification process for channel transmission according to embodiments of this disclosure will now be provided. The UE monitors downlink (DL) frequency resources (e.g., one or more physical resource blocks) to detect the presence of a notification alarm channel. Paging opportunities can be enhanced.

[0091] In one embodiment, the network waits for the UE to acknowledge receipt of the notification alarm channel before sending a paging message.

[0092] UE confirmation may include, for example, transmitting a Physical Random Access Channel (PRACH) preamble configured to the network, or sending an indication during or after the connection establishment process, such as in Msg3 or Msg5 of the Random Access (RA) procedure.

[0093] The UE can obtain this information based on predefined information or by receiving information about the time and frequency resources / locations used for monitoring notification alarm channels in a broadcast channel (e.g., System Information Block (SIB), such as SIB1). The same applies to acknowledgment configurations (e.g., on which preamble to send the acknowledgment).

[0094] In one embodiment, the UE monitors DL frequency resources (e.g., one or more physical resource blocks) to detect the presence of a notification alarm channel. The UE is configured to perform this monitoring during a time window of configured length T_nw, which is initiated by an offset T_o before the UE is configured to monitor periodically recurring paging opportunities for incoming paging.

[0095] In an additional embodiment, during a paging transmission window of length T_pw, after the expiration of T_o, the paging opportunity can be repeated with a shortened period T_p.

[0096] The network (NW) (e.g., a network node) is designed to configure these timers of appropriate length to allow the user to move their UE to better coverage after receiving a notification alarm channel transmission. To support accurate configuration, the UE can signal to the network and suggest a suitable set of timer values. The UE can also request the mobile user to input appropriate values ​​to instruct the network.

[0097] Figure 4 The time relationship between paging (paging opportunity) and notification alarm channel is shown (i.e., T_nw, T_o, T_p and T_pw).

[0098] In one embodiment, the NW (e.g., a network node) waits for the UE to acknowledge receipt of the notification channel before sending a paging message. The UE user will then need to confirm, via an explicit action (e.g., pressing an acknowledgment button on the UE screen), that he / she has received the notification alarm channel on his / her UE. This user action will trigger the UE to send an acknowledgment to the network, which can then respond either by sending a corresponding paging message to the UE or by configuring uplink and downlink resources for direct communication with the UE. Figure 5 The image shows an example of a paging message sent after the user confirms receipt of the downlink notification channel / message.

[0099] In an alternative embodiment, the UE autonomously detects that it has been moved to better SNR conditions by measuring the DL reference signal transmission (e.g., SSB) during a configured measurement period. Once the signal quality (e.g., SNR) or reference signal received power (RSRP) exceeds a configured threshold, the UE autonomously sends an acknowledgment to the network, which can respond by sending a paging message to establish a connection with the user. Figure 6 An example of a paging message sent after the UE detects improved signal strength or quality and autonomously acknowledges receipt of a downlink notification channel or message is shown.

[0100] In one embodiment, UE confirmation may include transmitting a PRACH preamble to the network for configuration, or sending an indication during or after the connection establishment process, such as in Msg3 or Msg5 of the RA process.

[0101] In one embodiment, the UE may obtain this information based on predefined information or by receiving information about the time and frequency resources / locations used to monitor the notification and alarm channels in a broadcast channel (e.g., a System Information Block (SIB), such as SIB1). The same applies to the configuration of acknowledgments (e.g., on which preamble to send the acknowledgment).

[0102] The following embodiments will now be described in relation to network detection of UEs under poor coverage and subsequent paging processing.

[0103] Group 1: This group of embodiments involves RAN detection of UEs with poor coverage and requires the use of enhanced "notification alarm" messages.

[0104] The gNB-CU detects and determines which UEs to apply the "notification alarm" (also referred to as "notification" or "alarm") process in this document.

[0105] Figure 7 An example is shown below. The steps of this example procedure involve the UE, gNB-DU, gNB-CU, and AMF, and are as follows:

[0106] Step 700 (optional): The UE indicates its ability to receive notification alarms via the Non-Access Stratum (NAS) or Access Stratum (AS). The AMF stores this capability information in the UE's UE context or along with the UE's UE ID (e.g., a 5G shortened temporary mobile subscription identifier (5G-S-TMSI)).

[0107] Step 702: The AMF determines that the UE needs to be paged.

[0108] Step 704: The AMF sends a paging message to the gNB-CU and an indication that the UE has the ability to receive notification alarms (e.g., in the paging message or as a separate message).

[0109] Step 706: gNB-CU pages UE via gNB-DU.

[0110] Step 708: The gNB-CU detects a paging failure and therefore determines that a notification alarm should be sent to the UE.

[0111] Step 710: gNB-CU sends a notification alarm message to gNB-DU, and gNB-DU then sends a notification alarm to UE.

[0112] Step 712: The gNB-CU sends a paging message to the gNB-DU, and the gNB-DU sends the paging message to the UE. Note that steps 710 and 712 can be performed according to any of the embodiments described above for the procedure for notifying channel transmission.

[0113] In one embodiment, when the gNB-CU determines that a UE is in poor network coverage (e.g., unfavorable radio conditions), it detects and determines which UEs to apply a "notification alarm".

[0114] When the gNB-CU pages a UE, under normal circumstances (e.g., when signal quality (e.g., SNR, signal-to-interference-plus-noise ratio (SINR)) is above a threshold), the UE initiates a PRACH procedure upon receiving the paging. At Msg3 and Msg5 of the PRACH procedure, the UE sends its UE identifier to a network node, such as the serving base station (e.g., the serving gNB-CU). Upon receiving Msg5, the gNB-CU initiates a first message with an "Initial UE Message" to the CN (e.g., AMF), carrying the 5G-S-TMSI and an uplink (UL) NAS Protocol Data Unit (PDU). By tracking the UEs being paged and those that have successfully established an RRC connection, the gNB-CU assesses whether paging to the UE has failed. The gNB-CU uses other paging assistance information and UE paging capabilities to determine which UEs to use "notification alarms" for.

[0115] The gNB-CU can determine that a specific UE is in poor network coverage based on one or more of the following mechanisms. Note that these mechanisms are just examples. Other mechanisms may be used.

[0116] The UE failed to receive any paging within the last specific time period (e.g., T11 seconds, N11 paging cycles, N12 System Frame Number (SFN) cycles, N13 Super SFN (H-SFN) cycles, etc.). As an example, one H-SFN cycle corresponds to 10 SFN cycles, and one SFN cycle corresponds to 1024 radio frames (e.g., one radio frame = 10 milliseconds (ms)). For example, if the UE does not initiate a Random Access Channel (RACH) transmission after being paged by the gNB-DU, the gNB-CU can assume that the UE did not receive the paging.

[0117] Only after the gNB-DU has sent the same paging message to the UE at least N17 times, and the UE successfully receives the paging within the last specific time period (e.g., T12 seconds, N14 paging cycles, N15 SFN cycles, N16 H-SFN cycles, etc.).

[0118] The UE has successfully received the paging within the last specific time period (e.g., T13 seconds, N18 paging cycles, N19 SFN cycles, N20 H-SFN cycles, etc.), provided that the gNB-DU has sent at least one paging message to the UE with a transmit power higher than a specific threshold (e.g., at least 3 dB higher than the power under favorable radio conditions (i.e., when the UE is not in poor network coverage)).

[0119] gNB-CU detects that the UE is in poor radio coverage based on RRC messages (e.g., random access related messages such as Msg3 or Msg5).

[0120] CN (e.g., AMF) includes information for NG-RAN nodes (i.e., ...) in the paging message. Figure 7 The gNB-CU in the NG-RAN node determines whether to send notification alarm information, such as whether the UE can receive notification alarms. When the NG-RAN node receives a certain number of paging attempts, the NG-RAN node understands that the UE has failed to be paged and therefore determines to send a "notification alarm" message to the UE.

[0121] In one embodiment, the gNB-CU determines that a particular UE is in poor network coverage (e.g., unfavorable radio conditions) (see, for example, see...). Figure 7 Step 708) initiates the "Notification Alarm" procedure. As part of the "Notification Alarm" procedure, the gNB-CU requests the gNB-DU serving the UE to send a "Notification Alarm" message to the UE (e.g., on a new notification channel) (e.g., see [link to relevant documentation]). Figure 7 (Step 710). For example, the gNB-DU transmits notification alarm messages (i.e., signals representing notification alarm messages) on the notification channel using robust physical layer transmission parameters (e.g., robust modulation and coding schemes (MCS) and / or transmission power above a certain threshold). Examples of robust MCS include modulation order not exceeding a certain threshold (e.g., quadrature phase shift keying (QPSK)), code rate not exceeding a certain threshold (e.g., 1 / 3), etc. The robustness of the physical layer transmission parameters enables the UE to successfully receive notification alarm messages on the notification channel, even when the UE is in poor coverage.

[0122] like Figure 8As shown, in one embodiment, the gNB-CU instructs the gNB-DU that a "notification alarm" should be sent to the determined UE. This corresponds to... Figure 7 Step 706. In this example, the "Notify Alarm" procedure is defined as a new procedure on F1AP. In one embodiment, gNB-CU determines the number of attempts / repetitions of the notification alarm message that gNB-DU should send. Figure 9 It shows Figure 8 An example of a notification / alarm message. Note that... Figure 8 and 9 It is shown as an example addition to the 3GPP specification (specifically, it is shown as an addition to 3GPP TS 38.473).

[0123] In one embodiment, the CN (e.g., AMF) is included in the paging message (e.g., see [link to paging message]). Figure 7 Step 704) provides auxiliary information for the NG-RAN node (e.g., gNB-CU) to determine whether to send a notification alarm. This auxiliary information includes information indicating, for example, that the UE can receive notification alarms. When the NG-RAN node receives a certain number of paging attempts, the NG-RAN node understands that the UE has failed to be paged and therefore determines to send a "notification alarm" message to the UE.

[0124] Figure 10 An example embodiment is shown in which a paging message sent from the gNB-CU to the gNB-DU for an existing paging procedure is used to transmit a notification alarm message from the gNB-CU to the gNB-DU. In other words, in Figure 10 In the example, an existing process (e.g., a paging process) is reused to deliver notification and alarm information.

[0125] Group 2: This group of embodiments involves the CN detecting a UE in poor coverage and indicating it to the RAN.

[0126] When the CN (e.g., AMF) detects that the UE cannot be paged through the existing paging process, it initiates a "notification alarm".

[0127] Figure 11 An example is shown below. The steps of this example procedure involve the UE, gNB-DU, gNB-CU, and AMF, and are as follows:

[0128] Step 1100 (optional): The UE indicates its ability to receive notifications and alarms via NAS or AS. The AMF stores this capability information in the UE's UE context or along with the UE's UE ID (e.g., 5G-S-TMSI).

[0129] Step 1102: The AMF detects a paging failure for the UE and determines that a notification alarm should be sent to the UE (e.g., based on the paging failure and other optional information, such as the UE's ability to receive notification alarms).

[0130] Step 1104: AMF sends a notification alarm to gNB-CU.

[0131] Step 1106: gNB-CU sends the notification alarm to gNB-DU, and gNB-DU then sends the notification alarm to UE.

[0132] Step 1108: The AMF sends a paging message for the UE to the gNB-CU.

[0133] Step 1110: The gNB-CU sends the paging message to the gNB-DU, which in turn sends the paging message to the UE. Note that the transmission of notification alarm and paging messages to the UE can be performed according to any of the embodiments described above for the procedure for notification channel transmission.

[0134] In one embodiment, when the CN (e.g., AMF) detects that the UE cannot be paged by the existing paging process (e.g., in step 1102), the CN thereby determines that the UE is in poor coverage and indicates it to the RAN.

[0135] For example, if the CN detects that the UE cannot receive a paging message after a certain number of paging attempts / transmissions, the CN determines that the UE cannot be paged through the existing paging process. If the UE does not initiate RRC connection establishment (e.g., within a specific period of time since the last paging transmission), the CN may determine that the UE has not successfully received the paging message. The CN may determine that the UE did not initiate RRC connection establishment autonomously (e.g., upon timer expiration) and / or based on an indication / message received from the gNB or gNB-C (in a separate RAN architecture).

[0136] In one embodiment, the CN (e.g., AMF) uses a new procedure to send a notification alarm to the NG-RAN node (e.g., to the gNB-CU in step 1104).

[0137] In one embodiment, the CN (e.g., AMF) instructs the NG-RAN node (e.g., gNB-CU) to send a notification alarm to the UE during an existing paging process (e.g., in step 1104), and the paging process follows the notification alarm. The CN (e.g., AMF) may instruct the NG-RAN node on the number of attempts to send the notification alarm. Figure 12An example of this notification alert is shown in the image.

[0138] The CN can be configured to selectively provide "notification alarms" to the RAN for specific services, with voice calls being one such service.

[0139] In one embodiment, for a separate RAN architecture, when the gNB-CU receives a "notification alarm" from the CN (e.g., AMF), it instructs the gNB-DU (e.g., in step 1106) that the "notification alarm" has been sent to a specific UE. For example embodiments of how the gNB-CU sends such a notification to the gNB-DU, refer to Group 1.

[0140] The transmission of "notification alarms" can be signaled or configured to notify the CN (e.g., AMF) that the NG-RAN node or some areas / cells within the NG-RAN node support such transmission.

[0141] Applicable to both Group 1 and Group 2: In a separate RAN architecture, the gNB-CU instructs the gNB-DU that a "notification alarm" is sent to a specific UE. Figure 13 An example is shown where the gNB-CU sends a notification alarm message to the gNB-DU, which includes the UE ID of the specific UE and optional additional information (e.g., notification area).

[0142] Group 3: Solutions for Xn Interfaces Used in RRC Inactivity

[0143] For UEs with inactive RRC, RAN paging can be used to paging the UE. This is common to both Group 1 and Group 2 solutions. Anchored / old-service NG-RAN nodes are required to notify neighboring NG-RAN nodes that an alarm should be sent to the UE when paging fails.

[0144] When RAN paging is used, the neighboring NG-RAN node is notified by the anchored / old serving NG-RAN node that it should notify the UE of the "notification alarm", and the UE is subsequently paged via the "paging" message.

[0145] Adjacent NG-RAN nodes (receivers) are designated to store paging information for later use; that is, "partial paging UE contexts can be created".

[0146] Adjacent NG-RAN nodes are designated to send a notification alarm upon receiving an indicator.

[0147] For RRC inactive UEs, RAN paging is used to paging UEs.

[0148] In one embodiment, for both Group 1 and Group 2 solutions, the anchored / legacy serving NG-RAN node notifies neighboring NG-RAN nodes that an "alarm notification" should be sent to the UE in the event of paging failure. This information is sent to neighboring NG-RAN nodes via the Xn interface using a new procedure (see, for example, [link to relevant documentation]). Figure 14A and 14B Figure 14 illustrates an example of this process. In this process, the anchored / old serving NG-RAN node sends a RAN notification alarm to a neighboring NG-RAN node, which informs the NG-RAN node that it should notify the UE of a "notification alarm" in the event of paging failure. Figure 14B An example implementation of RAN notification alarms is shown.

[0149] In one embodiment, the anchored / legacy serving NG-RAN node (e.g., gNB1-CU) can also notify neighboring NG-RAN nodes (e.g., gNB2-CU) that an "alarm notification" should be sent to the UE using an existing procedure (e.g., RAN paging), referencing Figure 15 . Figure 15 An example of a RAN paging message is shown, in which an anchored / old serving NG-RAN node (e.g., gNB1-CU) may also notify a neighboring NG-RAN node (e.g., gNB2-CU) that an "alarm notification" should be sent to the UE using an existing procedure (e.g., RAN paging).

[0150] In one embodiment, if a RAN paging message has already been sent, NG-RAN node 2 (the recipient of the RAN paging message) is designated to store the paging information for later use; that is, "partial paging UE contexts can be created".

[0151] In one embodiment, NG-RAN node 2 (the recipient of the RAN paging message) is designated to send a notification alarm upon receiving an indicator. In another embodiment, NG-RAN node 2 (the recipient of the RAN paging message) is designated to send a notification alarm followed by a RAN paging message.

[0152] So far, the description has focused on network operation. Now, the UE-side implementation will be discussed. In one embodiment, the UE indicates its ability to handle “enhanced paging” functions, such as “alarm notification,” via NAS signaling or a subscription (e.g., stored on a Subscriber Identity Module (SIM), Universal SIM (USIM), or Embedded SIM (eSIM)). The CN indicates this UE capability to the NG-RAN node via signaling messages (e.g., messages sent during paging or alarm notification) on the interface between the CN and the NG-RAN (e.g., Ng).

[0153] In one embodiment, the UE explicitly indicates its "notification alarm" capability via RRC. Upon receipt, the NG-RAN node includes this capability in the initial UE message (example) destined for the CN, which stores this information along with the UE identifier (e.g., 5G-S-TMSI) in the initial UE message for use in the next paging.

[0154] Figure 21 Three alternative processes are illustrated for providing the network with the UE capability for handling notification alarms according to an example embodiment of this disclosure. In Alternative 1, the UE sends an indication that it supports notification alarms to the RAN node, for example via RRC (step 2100). The RAN node sends a message (e.g., an N2 message, such as an initial UE message) to the CN node (e.g., AMF) that includes information indicating that the UE supports notification alarms (step 2102). The CN node stores the information indicating that the UE supports notification alarms (step 2104).

[0155] In Alternative Solution 2, the UE sends information to the CN node (e.g., AMF) instructing the UE to support alarm notification (e.g., via a PDU, such as a UL NAS PDU) (step 2106). The CN node stores the information instructing the UE to support alarm notification (step 2108).

[0156] In alternative 3, the CN node (e.g., AMF) obtains information from, for example, Unified Data Management (UDM) instructing the UE to support alarm notifications (step 2110). This information may, for example, be included in the UE's subscription information.

[0157] In one embodiment, the UE acknowledges the alarm message.

[0158] Figure 16 An example of a paging and alarm notification process according to an exemplary embodiment of this disclosure is shown. Optional steps are indicated by dashed lines / boxes. Figure 16The process involves UE 1600, a first network node 1601 (e.g., a gNB or gNB-DU), and an optional second network node 1602 (e.g., a gNB-CU (if the first network node 1601 is a gNB-DU), a CN node, or a second gNB). As shown, UE 1600 may send information indicating that UE 1600 supports alarm notification to the first network node 1601 (or via the first network node 1601 to another network node (e.g., gNB-CU)), as described herein (step 1603). UE 1600 may send information suggesting values ​​for timers T_nw, T_o, T_p, and / or T_pw to the first network node 1601 (or via the first network node 1601 to another network node (e.g., gNB-CU)) (step 1604). The first network node 1601 may send information to the UE 1600 (via broadcast or unicast) configuring the values ​​for T_nw, T_o, T_p and / or T_pw (step 1606).

[0159] The second network node 1602 can send a notification alarm for UE 1600 to the first network node 1601 (step 1607). The notification alarm can be sent according to any of the embodiments in group 1, group 2 or group 3 described above.

[0160] During the time window in which UE 1600 is configured to monitor notification alarms, the first network node 1601 sends notification alarms to UE 1600 (e.g., on the notification channel) (step 1608). The UE monitors notification alarms during a time window with a configured length T_nw (e.g., on a new notification channel), which begins with a time offset T_o before the periodically recurring paging opportunity of UE 1600 being configured to monitor incoming paging (step 1610). Details regarding the configured timers and the transmission of notification alarms on the notification channel have been described above and are equally applicable here. Figure 16 .

[0161] Optionally, UE 1600 sends a receipt acknowledgment of the notification alarm to network node 1600 (or via a first network node 1601 to another network node (e.g., gNB-CU)) (step 1612). As described above, in one embodiment, UE 1600 sends a notification when it receives user input from the user of UE 1600, wherein the user input acknowledges that the user has received the notification alarm (and, for example, has moved UE 1600 to a location with better signal strength or quality, such as removing it from the user's pocket). Also as described above, in another embodiment, UE 1600 sends an acknowledgment in step 1612 when it autonomously detects that UE 1600 has been moved to a location with improved radio coverage conditions (e.g., signal strength or quality above a certain threshold).

[0162] Optionally, upon receiving the confirmation from step 1612, the first network node 1601 sends a paging message in a paging opportunity (e.g., the next paging opportunity after sending a notification alarm, or the next paging opportunity after receiving the confirmation from step 1612) (step 1614). The UE 1600 monitors and detects the paging message in the associated paging opportunity (step 1616). The UE 1600 is then able to respond to the detected paging message in a normal manner. Note that in one embodiment, during a paging transmission window of length T_pw, after the expiration of T_o, the paging opportunity can appear with a shorter period T_p, as described above.

[0163] Figure 17 An example of a communication system 1700 according to some embodiments is shown.

[0164] In this example, the communication system 1700 includes a telecommunications network 1702, which includes an access network 1704 (e.g., a radio access network (RAN)) and a core network 1706 (which includes one or more core network nodes 1708). The access network 1704 includes one or more access network nodes, such as network nodes 1710A and 1710B (one or more of which may generally be referred to as network node 1710), or any other similar 3GPP access node or non-3GPP access point (AP). Furthermore, as those skilled in the art will understand, network nodes are not necessarily limited to implementations in which the radio and baseband portions are provided and integrated by a single vendor. Therefore, it will be understood that network nodes include decomposed implementations or portions thereof. For example, in some embodiments, the telecommunications network 1702 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunications network 1702 that supports ORAN specifications (such as those published by the O-RAN Alliance or any similar organization) and can operate alone or together with other nodes to perform one or more functions of any node in the telecommunications network 1702 (including one or more network nodes 1710 and / or core network node 1708).

[0165] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs) (including O-CU control planes (O-CU-CPs) or O-CU user planes (O-CU-UPs)), RAN Intelligent Controllers (near real-time or non-real-time) with managed software or software plugins (e.g., near real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps)), or any combination thereof (the adjective "open" specifies support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, Open Fronthaul User Plane interfaces, or Open Fronthaul Management Plane interfaces. Furthermore, ORAN access nodes can be logical nodes within physical nodes. Additionally, ORAN network nodes can be implemented in a virtualized environment (described further below) in which one or more network functions are virtualized. For example, the virtualized environment can include an O-Cloud computing platform orchestrated by a service management and orchestration framework via the O-2 interface or similar technologies defined by the O-RAN Consortium. Network node 1710 facilitates direct or indirect connections of user equipment (UE), such as connecting UE 1712A, 1712B, 1712C and 1712D (one or more of which may generally be referred to as UE 1712) to core network 1706 via one or more wireless connections.

[0166] Examples of wireless communication via a wireless connection include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, the communication system 1700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired or wireless connection). The communication system 1700 may include and interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar type of system.

[0167] UE 1712 can be any of a variety of communication devices, including wireless devices that are deployed, configured, and / or operable to communicate wirelessly with network node 1710 and other communication devices. Similarly, network node 1710 is deployed, capable of, configured, and / or operable to communicate directly or indirectly with UE 1712 and / or other network nodes or devices in telecommunication network 1702 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management) in telecommunication network 1702.

[0168] In the depicted example, core network 1706 connects network node 1710 to one or more hosts, such as host 1716. These connections can be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 1706 includes one or more core network nodes (e.g., core network node 1708) comprised of hardware and software components. The characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node 1708. Example core network nodes include one or more of the following functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Dehiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0169] Host 1716 may be under the ownership or control of a service provider other than the operator or provider of access network 1704 and / or telecommunications network 1702, and may be operated by or on behalf of the service provider. Host 1716 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., retrieving and editing data detected by multiple UEs regarding various environmental conditions), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0170] Overall, Figure 17 The communication system 1700 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system 1700 can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable second-, third-, fourth-, or fifth-generation (2G, 3G, 4G, or 5G) standards, or any applicable future-generation standard (e.g., sixth-generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0171] In some examples, telecommunications network 1702 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 1702 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 1702 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive Internet of Things (IoT) services to yet another set of UEs.

[0172] In some examples, UE 1712 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1704 according to a predetermined schedule when triggered by an internal or external event or in response to a request from access network 1704. Additionally, the UE may be configured to operate in a single radio access technology (RAT) or multiple RAT or multiple standards mode. For example, the UE may operate using any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., configured for multiple radio dual connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR-Dual Connectivity (EN-DC).

[0173] In this example, hub 1714 communicates with access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712C and / or 1712D) and network nodes (e.g., network node 1710B). In some examples, hub 1714 may be a controller, router, content source and analytics, or any other communication device described herein relating to the UE. For example, hub 1714 may be a broadband router that enables the UE to access core network 1706. As another example, hub 1714 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node 1710, or via executable code, scripts, procedures, or other instructions in hub 1714. As another example, hub 1714 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, data analytics or other processing may be performed. As another example, hub 1714 may be a content source. For example, for a UE acting as a virtual reality (VR) headset, display, speaker, or other media delivery device, hub 1714 can retrieve VR assets, video, audio, or other media or data related to sensed information via a network node, and then provide them to the UE directly, after performing local processing, and / or after adding additional local content. In yet another example, hub 1714 acts as a proxy server or orchestrator for the UE, particularly when one or more UEs are low-power IoT devices.

[0174] Hub 1714 may have a constant / persistent or intermittent connection to network node 1710B. Hub 1714 may also allow different communication schemes and / or scheduling between hub 1714 and UEs (e.g., UEs 1712C and / or 1712D) and between hub 1714 and core network 1706. In other examples, hub 1714 is connected to core network 1706 and / or one or more UEs via a wired connection. Furthermore, hub 1714 may be configured to connect to a machine-to-machine (M2M) service provider via access network 1704 and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 1710 while still being connected via hub 1714 via a wired or wireless connection. In some embodiments, hub 1714 may be a dedicated hub, that is, a hub whose primary function is to route communication from network node 1710B to UE / from UE to network node 1710B. In other embodiments, hub 1714 may be a non-dedicated hub, that is, a device capable of operating to route communication between the UE and network node 1710B, but also capable of operating as a communication start and / or end point for a specific data channel.

[0175] Figure 18 A UE 1800 according to some embodiments is illustrated. As used herein, a UE refers to a device capable of, configured, arranged, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, devices with built-in laptops (LEEs), devices with integrated laptops (LMEs), smart devices, wireless client devices (CPEs), vehicles, in-vehicle or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by 3GPP, including Narrowband Internet of Things (NB-IoT) UEs, Machine-Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0176] The UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for secondary link communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Instead, the UE may represent a device intended for sale to or operated by a human user but which may not, or initially may not, be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended for sale to or operated by an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0177] UE 1800 includes processing circuitry 1802, which is operatively coupled via bus 1804 to input / output interface 1806, power supply 1808, memory 1810, communication interface 1812, and / or any other component or any combination thereof. A particular UE may utilize... Figure 18 All components or subsets of components are shown. The level of integration between components can vary from UE to UE. Furthermore, a particular UE may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0178] Processing circuitry 1802 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions of a machine-readable computer program stored in memory 1810. Processing circuitry 1802 can be implemented as one or more hardware-implemented state machines (e.g., using discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and appropriate software; or any combination thereof. For example, processing circuitry 1802 may include multiple central processing units (CPUs).

[0179] In this example, the input / output interface 1806 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. Input devices can allow users to capture information into the UE 1800. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, steering wheels, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0180] In some embodiments, power supply 1808 is configured as a battery or battery pack. Other types of power sources may be used, such as external power sources (e.g., power outlets), photovoltaic devices, or batteries. Power supply 1808 may also include power circuitry for delivering power from power supply 1808 itself and / or external power sources to various parts of UE 1800 via input circuitry or interfaces (e.g., power cords). The delivery of power may, for example, be used to charge power supply 1808. The power circuitry may perform any formatting, conversion, or other modifications to the power from power supply 1808 to suit the appropriate components of UE 1800 to which power is supplied.

[0181] Memory 1810 may be, or may be configured to include, memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable ROM (EPROM), electrically EPROM (EEPROM), disk, optical disk, hard disk, removable magnetic tape, flash drive, etc. In one example, memory 1810 includes one or more applications 1814 (e.g., operating system, web browser application, widget, utility engine, or other application) and corresponding data 1816. Memory 1810 may store any one or a combination of various operating systems for use by UE 1800.

[0182] The memory 1810 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic RAM (SDRAM), external micro DIMM SDRAM, a smart card memory (such as a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), such as a universal SIM (USIM) and / or an Internet Protocol Multimedia Service Identifier (ISIM)), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly referred to as a "SIM card." The memory 1810 can allow the UE 1800 to access instructions, applications, etc., stored on transient or non-transient storage media to offload or upload data. Articles manufactured using communication systems may be tangibly embodied in or contained in memory 1810, which may be or include a device-readable storage medium.

[0183] Processing circuitry 1802 can be configured to communicate with an access network or other network using communication interface 1812. Communication interface 1812 may include one or more communication subsystems and may include or be communicatively coupled to antenna 1822. Communication interface 1812 may include one or more transceivers for communication (e.g., via one or more remote transceivers capable of wireless communication with another device (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter 1818 and / or a receiver 1820 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 1818 and receiver 1820 may be coupled to one or more antennas (e.g., antenna 1822) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0184] In the illustrated embodiment, the communication functions of the communication interface 1812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, NFC, location-based communication such as using the Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), Fast User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), etc.

[0185] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface 1812 through a wireless connection with a network node. Data captured by the UE's sensors can be transmitted via another UE through the wireless connection with the network node. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the reporting load from multiple sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0186] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or control a robotic arm performing a medical procedure based on the received input.

[0187] When taking the form of an IoT device, the UE can be a device for one or more application areas, including but not limited to urban wearable technology, extended industry applications, and healthcare. Non-limiting examples of such IoT devices include devices that are or are embedded in: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as heart rate monitors or remote-controlled surgical robots. The UE in the form of an IoT device includes the circuitry and / or software associated with the intended application of the IoT device and for... Figure 18 Other components described in UE 1800 shown.

[0188] As another specific example, in IoT scenarios, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, a UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle (e.g., a car, bus, truck), ship, aircraft, or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0189] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be or be integrated into the drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller for operating the drone. When the user makes changes from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling the actuators) to increase or decrease the drone's speed. The first UE and / or the second UE may also include multiple functions described above. For example, the UE may include sensors and actuators and handle data communication between both the speed sensor and the actuators.

[0190] Figure 19A network node 1900 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, node Bs, evolved Node Bs (eNBs), NR node Bs (gNBs)), and O-RAN nodes or components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0191] Base stations can be classified based on the coverage they provide (or in other words, their transmit power level), and therefore, depending on the coverage provided, they can be called femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station (e.g., centralized digital units, distributed units (e.g., in O-RAN access nodes), and / or remote radio units (RRUs) (sometimes referred to as remote radio heads (RRHs)). Such RRUs may or may not be integrated with an antenna as antenna-integrated radios. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0192] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment (such as MSR BS), network controllers such as radio network controllers (RNC) or BS controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved serving mobile location center (E-SMLC)), and / or minimized drive test (MDT).

[0193] Network node 1900 includes processing circuitry 1902, memory 1904, communication interface 1906, and power supply 1908. Network node 1900 may include multiple physically separate components (e.g., node B components and RNC components, or BTS components and BSC components, etc.), each component may have its own corresponding components. In a specific scenario where network node 1900 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among multiple network nodes. For example, a single RNC can control multiple node Bs. In such scenarios, under certain circumstances, each unique node B and RNC pair may be considered a single, separate network node. In some embodiments, network node 1900 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., a separate memory 1904 for different RATs), while some components may be reused (e.g., the same antenna 1910 may be shared by different RATs). Network node 1900 may also include a variety of example components for integrating different wireless technologies (such as GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies) into network node 1900. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1900.

[0194] Processing circuitry 1902 may include one or more of the following, operable to provide network node 1900 functionality individually or in combination with other network node 1900 components (e.g., memory 1904): microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software and / or coding logic.

[0195] In some embodiments, the processing circuitry 1902 includes a system-on-a-chip (SOC). In some embodiments, the processing circuitry 1902 includes one or more of a radio frequency (RF) transceiver circuitry 1912 and a baseband processing circuitry 1914. In some embodiments, the RF transceiver circuitry 1912 and the baseband processing circuitry 1914 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 1912 and the baseband processing circuitry 1914 may be on the same chip or chipset, board, or unit.

[0196] Memory 1904 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by processing circuitry 1902. Memory 1904 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions that can be executed by processing circuitry 1902 and utilized by network node 1900. Memory 1904 may be used to store any calculations performed by processing circuitry 1902 and / or any data received via communication interface 1906. In some embodiments, processing circuitry 1902 and memory 1904 are integrated.

[0197] Communication interface 1906 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 1906 includes a port / terminal 1916 for sending and receiving data to and from the network, for example, via a wired connection. Communication interface 1906 also includes radio front-end circuitry 1918 that can be coupled to antenna 1910 or, in a particular embodiment, is part of antenna 1910. Radio front-end circuitry 1918 includes a filter 1920 and an amplifier 1922. Radio front-end circuitry 1918 can be connected to antenna 1910 and processing circuitry 1902. Radio front-end circuitry 1918 can be configured to modulate the signal transmitted between antenna 1910 and processing circuitry 1902. Radio front-end circuitry 1918 can receive digital data that will be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1918 can use a combination of filter 1920 and / or amplifier 1922 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 1910. Similarly, when receiving data, antenna 1910 can collect radio signals, which are then converted into digital data by radio front-end circuitry 1918. The digital data can then be passed to processing circuitry 1902. In other embodiments, communication interface 1906 may include different components and / or different combinations of components.

[0198] In certain alternative embodiments, network node 1900 does not include a separate radio front-end circuitry 1918; instead, processing circuitry 1902 includes radio front-end circuitry and is connected to antenna 1910. Similarly, in some embodiments, all or part of RF transceiver circuitry 1912 is part of communication interface 1906. In other embodiments, communication interface 1906 includes one or more ports or terminals 1916, radio front-end circuitry 1918, and RF transceiver circuitry 1912 as part of a radio unit (not shown), and communication interface 1906 communicates with baseband processing circuitry 1914, which is part of a digital unit (not shown).

[0199] Antenna 1910 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1910 may be coupled to radio front-end circuitry 1918 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In a particular embodiment, antenna 1910 is decoupled from network node 1900 and may be connected to network node 1900 via an interface or port.

[0200] Antenna 1910, communication interface 1906, and / or processing circuitry 1902 can be configured to perform any receive operation and / or specific acquisition operation described herein as being performed by network node 1900. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 1910, communication interface 1906, and / or processing circuitry 1902 can be configured to perform any transmit operation described herein as being performed by network node 1900. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0201] Power supply 1908 provides power to the various components of network node 1900 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power supply 1908 may also include or be coupled to power management circuitry to provide power to the components of network node 1900 for performing the functions described herein. For example, network node 1900 may be connected to an external power source (e.g., the mains or a power outlet) via input circuitry or an interface (e.g., a cable), whereby the external power source provides power to the power circuitry of power supply 1908. As yet another example, power supply 1908 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0202] Embodiments of network node 1900 may include Figure 19Additional components beyond those shown may be used to provide specific aspects of the functionality of the network node, including any of the functions described herein and / or any functions necessary to support the topics described herein. For example, network node 1900 may include a user interface device to allow information to be input into and output from network node 1900. This can allow users to perform diagnostic, maintenance, repair, and other management functions on network node 1900.

[0203] Figure 20 This is a block diagram illustrating a virtualized environment 2000 in which functionality implemented by some embodiments can be virtualized. In the current context, virtualization means creating virtual versions of devices or equipment, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments 2000 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments in which virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized. In some embodiments, the virtualized environment 2000 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a service management and orchestration framework via an O-2 interface.

[0204] Application 2002 (which may also be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) runs in virtualization environment 2000 to implement certain features, functions, and / or benefits of some embodiments disclosed herein.

[0205] Hardware 2004 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2006 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide virtual machines 2008A and 2008B (one or more of which may generally be referred to as virtual machine 2008), and / or perform any functionality, features, and / or benefits described for some embodiments described herein. Virtualization layer 2006 may present a virtual operating platform to virtual machine 2008 that appears to be networked hardware.

[0206] Virtual machine 2008 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 2006. Different embodiments of virtual device 2002 instances can be implemented on one or more virtual machines 2008, and can be implemented in different ways. In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard, high-capacity server hardware, physical switches, and physical storage devices that can reside in data centers and client devices.

[0207] In the context of NFV, a virtual machine 2008 can be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each virtual machine 2008, along with the portion of hardware 2004 that executes that virtual machine (hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other virtual machines 2008), forms a separate virtual network unit. Still within the NFV context, virtual network functions are responsible for handling specific network functions running on one or more virtual machines 2008 above hardware 2004, and correspond to application 2002.

[0208] Hardware 2004 can be implemented in a standalone network node with general or specific components. Hardware 2004 can implement some functions via virtualization. Alternatively, hardware 2004 can be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 2010, which, among other things, oversees the lifecycle management of application 2002. In some embodiments, hardware 2004 is coupled to one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be used in combination with virtual components to provide a radio-capable virtual node, such as a RAN or base station. In some embodiments, a control system 2012 can be used to provide signaling, which can alternatively be used for communication between the hardware nodes and the radio units.

[0209] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It will be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry, which may process information, for example, by: converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, while computationally intensive functions may be implemented in hardware.

[0210] In certain embodiments, some or all of the functions described herein may be provided by processing circuitry executing instructions stored in memory, which may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry without requiring, for example, hard-wired execution of instructions stored on a separate or separate device-readable storage medium. In any of these particular embodiments, processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

[0211] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

[0212] Group A Examples

[0213] Example 1: A method performed by a user equipment (UE) (1600) comprising: monitoring (1610) a paging notification alarm during a time window having a configured length T_nw, the time window being initiated with a time offset T_o prior to the UE (1600) being configured to monitor periodically recurring paging opportunities of incoming paging; and detecting (1610) the notification alarm during the time window as a result of the monitoring (1610).

[0214] Example 2: According to the method of Example 1, wherein monitoring (1610) paging notification alarms during the time window includes: monitoring (1610) paging notification alarms on the notification channel during the time window.

[0215] Example 3: According to the method of Example 2, the UE (1600) obtains the information based on predefined information or by receiving information about time and frequency resources for monitoring the notification channel in a broadcast channel (e.g., System Information Block (SIB), such as SIB1).

[0216] Example 4: The method according to any one of Examples 1 to 3 further includes: sending (1612) a receipt confirmation of the notification alarm to the network node.

[0217] Example 5: According to the method described in Example 4, the receipt confirmation of sending (1612) the notification alarm includes: when the user of the UE (1600) receives user input confirming that the user has received the notification alarm, the receipt confirmation of sending (1612) the notification alarm is sent.

[0218] Example 6: According to the method described in Example 4, the receipt confirmation of sending (1612) the notification alarm includes: when the UE (1600) autonomously detects that the UE (1600) has moved to a location with improved signal strength or quality (e.g., signal strength and quality above a specific (e.g., configured or defined) threshold), the receipt confirmation of sending (1612) the notification alarm is sent.

[0219] Example 7: The method according to any one of Examples 4 to 6, wherein sending the receipt confirmation of the notification alarm (1612) includes: sending a configured PRACH preamble or sending indication (e.g., in Msg3 or Msg5) during or after the connection establishment process.

[0220] Example 8: The method according to any one of Examples 1 to 7 further includes: monitoring paging messages in the paging opportunity after receiving the notification alarm.

[0221] Example 9: The method according to any one of Examples 1 to 8, wherein, during a paging transmission window of length T_pw, after the expiration of T_o, the periodically recurring paging opportunity is repeated with a shortened period.

[0222] Example 10: The method according to any one of Examples 1 to 9 further includes: sending (1603) a notification alarm message to the network node indicating that the UE (1600) supports paging.

[0223] Example 11: The method according to any one of Examples 1 to 10 further includes: sending (1604) information suggesting values ​​for T_nw and T_o to the network node.

[0224] Example 12: The method according to any one of Examples 1 to 10 further includes: receiving (1606) information configuring T_nw and T_o from a network node.

[0225] Example 13: The method according to any of the foregoing embodiments further includes: providing user data; and forwarding the user data to the host via transmission to the network node.

[0226] Group B Implementation Examples

[0227] Example 14: A method performed by a first network node (1601), the method comprising: sending a paging notification alarm (1608) to a user equipment (UE) (1600), the notification alarm being sent during a time window having a configured length T_nw, the time window being initiated with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging.

[0228] Example 15: According to the method of Example 14, wherein sending (1608) the notification alarm during the time window includes: sending (1608) the notification alarm on the notification channel during the time window.

[0229] Example 16: According to the method of Example 15, the information about the time and frequency resources of the notification channel that the UE (1600) wants to monitor is predefined or sent by the first network node (1601) in a broadcast channel (e.g., a system information block (SIB), such as SIB1).

[0230] Example 17: The method according to any one of Examples 14 to 16 further includes: receiving (1612) a receipt confirmation of the notification alarm from the UE (1600).

[0231] Example 18: According to the method of Example 17, wherein receiving the reception acknowledgment of the notification alarm (1612) includes receiving a configured PRACH preamble or reception indication (e.g., in Msg3 or Msg5) during or after the connection establishment process.

[0232] Example 19: The method according to any one of Examples 14 to 18 further includes: after sending the notification alarm (and for example after receiving the reception acknowledgment of the notification alarm from the UE (1600), sending a paging message (1614) to the UE (1600) during a paging opportunity.

[0233] Example 20: The method according to any one of Examples 14 to 19, wherein, during a paging transmission window of length T_pw, after the expiration of T_o, the periodically recurring paging opportunity is repeated with a shortened period.

[0234] Example 21: The method according to any one of Examples 14 to 20 further includes: receiving (1603) information from the UE (1600) indicating that the UE (1600) supports paging.

[0235] Example 22: The method according to any one of Examples 14 to 21 further includes: receiving (1604) information from the UE (1600) suggesting values ​​for T_nw and T_o.

[0236] Example 23: The method according to any one of Examples 14 to 22 further includes: sending (1606) information configuring T_nw and T_o to the UE (1600).

[0237] Example 24: The method according to any one of Examples 14 to 23 further includes: an indication from the second network node (1602) to be sent to the UE (1600) of the notification alarm.

[0238] Example 25: According to the method described in Example 24, the first network node (1601) is the DU of the RAN node and the second network node (1602) is the CU of the RAN node.

[0239] Example 26: According to the method described in Example 24, the first network node (1601) is a RAN node and the second network node (1602) is a CN node.

[0240] Example 27: According to the method described in Example 24, wherein the first network node (1601) is a first RAN node and the second network node (1602) is a second RAN node.

[0241] Example 28: A method performed by a second network node (1602), the method comprising: sending information to a first network node (1601) regarding a notification alarm for paging of a user equipment (UE).

[0242] Example 29: The method according to Example 28 further includes: determining a notification alarm process for providing a notification alarm to the UE application before sending a paging message.

[0243] Example 30: According to the method described in Example 28, the process of determining to apply the notification alarm to the UE includes: determining that the UE is in poor network coverage.

[0244] Example 31: The method according to any one of Examples 28 to 30, wherein the first network node (1601) is the DU of the RAN node and the second network node (1602) is the CU of the RAN node.

[0245] Example 32: The method according to any one of Examples 28 to 30, wherein the first network node (1601) is a RAN node and the second network node (1602) is a CN node.

[0246] Example 33: The method according to any one of Examples 28 to 30, wherein the first network node (1601) is a first RAN node and the second network node (1602) is a second RAN node.

[0247] Example 34: The method according to any of the foregoing embodiments further includes: obtaining user data; and forwarding the user data to a host or user equipment.

[0248] Group C Implementation Examples

[0249] Example 35: A user equipment includes: processing circuitry configured to perform any step of any of the Group A examples; and power supply circuitry configured to provide power to the processing circuitry.

[0250] Example 36: A network node comprising: processing circuitry configured to perform any step of any of the Group B examples; and power supply circuitry configured to provide power to the processing circuitry.

[0251] Example 37: A user equipment (UE) includes: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit, configured to modulate signals transmitted between the antenna and the processing circuit; the processing circuit configured to perform any step of any of the Group A embodiments; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information already processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to provide power to the UE.

Claims

1. A method performed by a user equipment (UE) (1600), the method comprising: Monitor (1610) paging notification alarms during a time window with a configured length T_nw, the time window starting with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging; and As a result of the monitoring (1610), an alarm is detected (1610) during the time window.

2. The method according to claim 1, wherein, Monitoring (1610) paging notification alarms during the time window includes: monitoring (1610) paging notification alarms during the time window on a notification channel using one or more robust physical layer transmission parameters.

3. The method according to claim 2, wherein, The one or more robust physical layer transmission parameters include a modulation order not greater than a specific modulation order threshold, a code rate not greater than a specific code rate threshold, and / or a transmission power higher than a specific power threshold.

4. The method according to claim 2 or 3, wherein, The UE (1600) obtains the information based on predefined information or by receiving information in the broadcast channel about the time and frequency resources used to monitor the notification channel.

5. The method according to any one of claims 1 to 4, further comprising: Send a confirmation of receipt of the notification alarm described in (1612) to the network node.

6. The method according to claim 5, wherein, The receipt confirmation of the notification alarm (1612) includes: when the user of the UE (1600) receives user input confirming that the user has received the notification alarm, the receipt confirmation of the notification alarm (1612) is sent.

7. The method according to claim 5, wherein, The receipt confirmation of the notification alarm (1612) includes sending the receipt confirmation of the notification alarm (1612) when the UE (1600) autonomously detects that the UE (1600) has moved to a location with improved signal strength or quality.

8. The method according to any one of claims 5 to 7, wherein, The receipt confirmation of the notification alarm (1612) includes sending a configured Physical Random Access Channel (PRACH) preamble or a transmission indication during or after the connection establishment process.

9. The method according to any one of claims 1 to 8, further comprising: Upon receiving the notification alarm, monitor (1616) the paging message in the paging opportunity.

10. The method according to any one of claims 1 to 9, wherein, During a paging transmission window of length T_pw, after the expiration of T_o, periodically recurring paging opportunities are repeated with a shortened period.

11. The method according to any one of claims 1 to 10, further comprising: Send (1603) a notification alarm message to the network node indicating that the UE (1600) supports paging.

12. The method according to any one of claims 1 to 11, further comprising: Send (1604) information to the network node suggesting the length T_nw and the time offset T_o values ​​for the configuration used for the time window.

13. The method according to any one of claims 1 to 11, further comprising: Receive (1606) from the network node information of the configured time window length T_nw and the time offset T_o.

14. A user equipment (UE) (1600), suitable for: Monitor (1610) paging notification alarms during a time window with a configured length T_nw, the time window starting with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging; and As a result of the monitoring (1610), an alarm is detected (1610) during the time window.

15. The UE (1600) according to claim 14 is also adapted to perform the method according to any one of claims 2 to 13.

16. A user equipment (UE) (1600; 1800), comprising: The communication interface (1812) includes a transmitter (1818) and a receiver (1820). as well as A processing circuit (1802), associated with the communication interface (1812), is configured to cause the UE (1600; 1800) to: Monitor (1610) paging notification alarms during a time window with a configured length T_nw, the time window starting with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging; and As a result of the monitoring (1610), an alarm is detected (1610) during the time window.

17. The UE (1600; 1800) according to claim 16 is also adapted to perform the method according to any one of claims 2 to 13.

18. A method performed by a first network node (1601), the method comprising: Send (1608; 710; ) to User Equipment (UE) (1600) 1106) Paging notification alarm, which is sent during a time window with a configured length T_nw, the time window being initiated with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging; as well as After sending the notification alarm (1618), a paging message (1614; 712; 1110) is sent to the UE (1600) during the paging opportunity.

19. The method according to claim 18, wherein, Sending the notification alarm during the time window (1608; 710) includes sending the notification alarm (1608; 710) on a notification channel using one or more robust physical layer transmission parameters during the time window.

20. The method according to claim 19, wherein, The one or more robust physical layer transmission parameters include a modulation order not greater than a specific modulation order threshold, a code rate not greater than a specific code rate threshold, and / or a transmission power higher than a specific power threshold.

21. The method according to claim 19 or 20, wherein, The information regarding the time and frequency resources that the UE (1600) needs to monitor in the notification channel is predefined or sent by the first network node (1601) in the broadcast channel.

22. The method according to any one of claims 18 to 21, further comprising: Before sending the paging message (1614), receive the notification alarm acknowledgment (1612) from the UE (1600).

23. The method according to claim 22, wherein, The receipt confirmation of the notification alarm (1612) includes: receiving a configured Physical Random Access Channel (PRACH) preamble or a receipt indication from the UE during or after the connection establishment process.

24. The method according to any one of claims 18 to 23, wherein: Sending the paging message (1614) includes: after sending the notification alarm and receiving the acceptance confirmation of the notification alarm from the UE (1600), sending the paging message (1614) to the UE during the paging opportunity.

25. The method according to any one of claims 18 to 24, wherein, During a paging transmission window of length T_pw, after the expiration of T_o, periodically recurring paging opportunities are repeated with a shortened period.

26. The method according to any one of claims 18 to 25, further comprising: The UE (1600) receives (1603) a notification alarm message indicating that the UE (1600) supports paging.

27. The method according to any one of claims 18 to 25, wherein: The first network node (1601) is the central unit (CU) of the radio access network (RAN) node; Sending the paging notification alarm to the UE (710) includes: sending (710) a notification alarm message about the notification alarm to be sent to the UE to the Distributed Unit (DU) of the RAN node; and Sending the paging message (712) to the UE includes: sending the paging message (712) to the UE via the DU of the RAN node.

28. The method of claim 27, further comprising: Receive (704) a notification alarm from another network node indicating that the UE (1600) supports paging.

29. The method according to claim 28, wherein, The other network node is a core network node, and the information received (704) indicating that the UE (1600) supports paging includes: receiving (704) a paging-related message including the information indicating that the UE (1600) supports paging.

30. The method according to any one of claims 27 to 29, further comprising: The DU of the RAN node sends an initial paging message (706) to the UE; Detect (708) a paging failure related to the initial paging message used by the UE; as well as In response to the detection of the paging failure (708), it is determined that the notification alarm (708) is to be sent to the UE.

31. The method according to any one of claims 18 to 21, wherein, The first network node (1601) is a distributed unit (DU) of a radio access network (RAN) node.

32. The method according to any one of claims 18 to 25, wherein: The first network node (1601) is a radio access network (RAN) node or the central unit (CU) of the RAN node.

33. The method of claim 32, further comprising: Receive (1607) from core network node (1602); 1104) Notify alarm, the notification alarm indicating that the notification alarm should be sent to the UE (1600).

34. The method according to any one of claims 18 to 33, further comprising: The UE (1600) receives (1604) information suggesting the length T_nw and the time offset T_o values ​​for the configuration used for the time window.

35. The method according to any one of claims 18 to 34, further comprising: Send (1606) information to the UE (1600) configuring the length T_nw of the time window and the time offset T_o.

36. A first network node (1601), suitable for: A notification alarm for paging (1608; 710; 1106) is sent to the user equipment (UE) (1600) during a time window of configured length T_nw, the time window being initiated with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging; and After sending the notification alarm (1618), a paging message (1614; 712; 1110) is sent to the UE (1600) during the paging opportunity.

37. The first network node (1601) according to claim 36 is also adapted to perform the method according to any one of claims 19 to 35.

38. A first network node (1601; 1900) includes processing circuitry (1902), the processing circuitry (1902) being configured to cause the first network node (1601; 1900): A notification alarm for paging (1608; 710; 1106) is sent to the user equipment (UE) (1600) during a time window of configured length T_nw, the time window being initiated with a time offset T_o before the UE (1600) is configured to monitor periodically recurring paging opportunities of incoming paging; and After sending the notification alarm (1618), a paging message (1614; 712; 1110) is sent to the UE (1600) during the paging opportunity.

39. The first network node (1601; 1900) according to claim 38, wherein, The processing circuit (1902) is also configured to cause the first network node (1601; 1900) to perform the method according to any one of claims 19 to 35.

40. A method performed by a second network node (1602), the method comprising: Send (1601; 704;) to the first network node. 1104) Information regarding notification alarms for paging used by user equipment (UE).

41. The method of claim 40, further comprising: Determine (1102) the notification alarm process for providing notification alarms to the UE application before sending paging messages.

42. The method according to claim 41, wherein, The process of determining (1102) to apply the notification alarm to the UE includes: determining that the UE is in poor network coverage.

43. The method according to any one of claims 40 to 42, wherein, The first network node (1601) is a distributed unit DU of a radio access network (RAN) node, and the second network node (1602) is a central unit CU of the RAN node.

44. The method according to any one of claims 40 to 42, wherein, The first network node (1601) is a radio access network (RAN) node, and the second network node (1602) is a core network (CN) node.

45. The method according to any one of claims 40 to 42, wherein, The first network node (1601) is a first radio access network (RAN) node, and the second network node (1602) is a second radio access network (RAN) node.

46. ​​A second network node (1602), suitable for: Send (1601; 704; 1104) notification alarm information to the first network node regarding paging for the user equipment (UE).

47. The second network node (1602) according to claim 46 is also adapted to perform the method according to any one of claims 41 to 45.

48. A second network node (1602; 1900) including processing circuitry (1902), the processing circuitry (1902) being configured to cause the second network node (1602; 1900): Send (1601; 704; 1104) notification alarm information to the first network node regarding paging for the user equipment (UE).

49. The second network node (1602; 1900) according to claim 48, wherein, The processing circuit (1902) is also configured to cause the second network node (1602; 1900) to perform the method according to any one of claims 41 to 45.

Images