Methods and apparatuses for paging and random access

Abstract

The present disclosure is related to a terminal device, a network node, and methods for paging and random access A method at a terminal device comprises: receiving, from a network node, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and receiving a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

Description

METHODS AND APPARATUSES FOR PAGING AND RANDOM ACCESSTechnical Field

[0001] The present disclosure is related to the field of telecommunication, and in particular, to a terminal device, a network node, and methods for paging and random access.Background

[0002] With the development of the electronic and telecommunication technologies, mobile devices, such as mobile phones, smart phones, laptops, tablets, vehicle mounted devices, become an important part of our daily lives. To support a numerous number of mobile devices, a highly efficient Radio Access Network (RAN), such as a fifth generation (5G) New Radio (NR) RAN, will be required.

[0003] In the 5G system, connection may be established either due to user equipment (UE) data becoming available on the Core Network (CN) side or at the UE side itself. How the connection is established is very similar in both cases, the main difference is that in the former case, before the actual connection establishment begins, the network initiates a procedure called Paging.

[0004] In NR the UE may be configured by the network to transmit random access (RA) in a cell (e.g. serving cell or a neighbor cell) using 4-step RA procedure and / or using 2-step RA procedure.Summary

[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0006] In the upcoming 3rd Generation Partnership Project (3GPP) release (i.e., 3GPP Rel-19), network energy saving / enhancement is likely to be further optimized on top of the features introduced in 3 GPP Rel-18.

[0007] In 3GPP Rel-18, cell Discontinuous Reception (DRX) and DRX feature has been introduced so that the (next) generation NodeB (gNB) only transmits certain cell control signaling or reference signal during occasions when the gNB is active (i.e., so called on-duration) to save energy.

[0008] One of the downlink (DL) signaling is expected to be affected is paging message. The gNB will not transmit paging message towards those intended UEs on every paging occasion. The paging occasion would be limited to not only paging DRX cycles of each intended UE, but alsocell Discontinous Transmission (DTX) configurations and any other conditional off-occasions. In this way, the gNB would not transmit a paging on an occasion where the gNB is supposed to be inactive for paging. Thus, the consequence is that a paging message may be delayed to reach the UE (since the gNB would delay the paging message to the next paging occasion which is overlap with the gNB’s cell DTX on-duration ) and the UE would therefore suffer from degradation of Quality of Service (QoS) for services.

[0009] Random Access (RACH) procedure is another example of uplink (UL) control signaling that may be affected due to cell DTX and DRX operation. Some RACH occasions / transmissions may be missed by the gNB due to that the gNB is inactive according to its cell DRX configurations. Similarly, additional delay would be caused for the access procedure of the UE.

[0010] It is necessary to study the above issues and develop corresponding options to enhance paging procedure and / or RACH procedure to combat the additional delay caused by cell DTX and DRX operations. Therefore, to address or at least partially alleviate one or more of the above issues, some embodiments of the present disclosure are provided.

[0011] According to a first aspect of the present disclosure, a method at a terminal device is provided. The method comprises: receiving, from a network node, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and receiving a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

[0012] According to a second aspect of the present disclosure, an apparatus implemented in a terminal device is provided. The apparatus comprises: a processor; a memory storing instructions which, when executed by the processor, cause the processor to perform any of the methods of the first aspect.

[0013] According to a third aspect of the present disclosure, a method at a network node is provided. The method comprises: transmitting, to a terminal device, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and transmitting a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

[0014] According to a fourth aspect of the present disclosure, an apparatus implemented in a network node is provided. The apparatus comprises: a processor; a memory storing instructions which, when executed by the processor, cause the processor to perform any of the methods of the third aspect.

[0015] According to a fifth aspect of the present disclosure, a method at a terminal device is provided. The method comprises: receiving, from a network node, a message indicating aconfiguration of Random Access Channel (RACH) occasion and / or RACH resource; and performing random access based on the configuration of the RACH occasion and / or RACH resource.

[0016] According to a sixth aspect of the present disclosure, an apparatus implemented in a terminal device is provided. The apparatus comprises: a processor; a memory storing instructions which, when executed by the processor, cause the processor to perform any of the methods of the fifth aspect.

[0017] According to a seventh aspect of the present disclosure, a method at a network node is provided. The method comprises: transmitting, to a terminal device, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource; and receiving an access request from the terminal device.

[0018] According to an eighth aspect of the present disclosure, an apparatus implemented in a network node is provided. The apparatus comprises: a processor; a memory storing instructions which, when executed by the processor, cause the processor to perform any of the methods of the seventh aspect.

[0019] According to a nineth aspect of the present disclosure, a computer program comprising instructions is provided. The instructions, when executed by at least one processor, cause the at least one processor to carry out the methods of any of the first, third, fifth, or seventh aspect.

[0020] According to a tenth aspect of the present disclosure, a carrier containing the computer program of the first, third, fifth, or seventh aspect is provided. The carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0021] According to an eleventh aspect of the present disclosure, a telecommunication system is provided. The telecommunication system comprises: one or more terminal devices and at least one network node. The at least one of the terminal devices may perform any of the methods of the first or fifth aspect, and the at least one network node may perform any of the methods of the third or seventh aspect.

[0022] With some embodiments of the present disclosure, network energy may be saved due to the enhancements on paging and / or RACH.Brief Description of the Drawings

[0023] Fig. 1 is a diagram illustrating two NR Cells on different sector carriers (left) and two NR Cells sharing the same sector carrier (right).

[0024] Fig. 2 is a flow chart illustrating 4-step RACH procedure.

[0025] Fig. 3 is a flow chart illustrating 2-step RACH procedure.

[0026] Fig. 4 is a diagram illustrating an example of DL / UL resources for UE in IDLE / INACTIVE mode.

[0027] Fig. 5 is a flow chart illustrating an exemplary method at a terminal device according to an embodiment of the present disclosure.

[0028] Fig. 6 is a flow chart illustrating an exemplary method at a network node according to an embodiment of the present disclosure.

[0029] Fig. 7 is a flow chart illustrating another exemplary method at a terminal device according to an embodiment of the present disclosure.

[0030] Fig. 8 is a flow chart illustrating an exemplary method at a network node according to an embodiment of the present disclosure.

[0031] Fig. 9 schematically shows an embodiment of an arrangement which may be used in a terminal device or a network node according to an embodiment of the present disclosure.

[0032] Fig. 10 shows an example of a communication system in accordance with some embodiments of the present disclosure.

[0033] Fig. 11 shows an exemplary UE in accordance with some embodiments of the present disclosure.

[0034] Fig. 12 shows an exemplary network node in accordance with some embodiments of the present disclosure.

[0035] Fig. 13 is a block diagram illustrating an exemplary virtualization environment in which functions implemented by some embodiments may be virtualized.Detailed Description

[0036] Hereinafter, the present disclosure is described with reference to embodiments shown in the attached drawings. However, it is to be understood that those descriptions are just provided for illustrative purpose, rather than limiting the present disclosure. Further, in the following, descriptions of known structures and techniques are omitted so as not to unnecessarily obscure the concept of the present disclosure.

[0037] Those skilled in the art will appreciate that the term “exemplary” is used herein to mean “illustrative,” or “serving as an example,” and is not intended to imply that a particular embodiment is preferred over another or that a particular feature is essential. Likewise, the terms “first”, “second”, “third”, “fourth,” and similar terms, are used simply to distinguish one particular instance of an item or feature from another, and do not indicate a particular order or arrangement, unless the context clearly indicates otherwise. Further, the term “step,” as used herein, is meant to be synonymous with “operation” or “action.” Any description herein of a sequence of steps doesnot imply that these operations must be carried out in a particular order, or even that these operations are carried out in any order at all, unless the context or the details of the described operation clearly indicates otherwise.

[0038] Conditional language used herein, such as "can," "might," "may," "e.g.," and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and / or states. Thus, such conditional language is not generally intended to imply that features, elements and / or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and / or states are included or are to be performed in any particular embodiment. Also, the term "or" is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term "or" means one, some, or all of the elements in the list. Further, the term "each," as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term "each" is applied.

[0039] The term “based on” is to be read as “based at least in part on.” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment.” The term “another embodiment” is to be read as “at least one other embodiment.” Other definitions, explicit and implicit, may be included below. In addition, language such as the phrase "at least one of X, Y and Z," unless specifically stated otherwise, is to be understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z, or a combination thereof.

[0040] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limitation of example embodiments. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. It will be also understood that the terms “connect(s),” “connecting”, “connected”, etc. when used herein, just mean that there is an electrical or communicative connection between two elements and they can be connected either directly or indirectly, unless explicitly stated to the contrary.

[0041] Of course, the present disclosure may be carried out in other specific ways than those set forth herein without departing from the scope and essential characteristics of the disclosure. One or more of the specific processes discussed below may be carried out in any electronic devicecomprising one or more appropriately configured processing circuits, which may in some embodiments be embodied in one or more application-specific integrated circuits (ASICs). In some embodiments, these processing circuits may comprise one or more microprocessors, microcontrollers, and / or digital signal processors programmed with appropriate software and / or firmware to carry out one or more of the operations described above, or variants thereof. In some embodiments, these processing circuits may comprise customized hardware to carry out one or more of the functions described above. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

[0042] Although multiple embodiments of the present disclosure will be illustrated in the accompanying Drawings and described in the following Detailed Description, it should be understood that the disclosure is not limited to the disclosed embodiments, but instead is also capable of numerous rearrangements, modifications, and substitutions without departing from the present disclosure that as will be set forth and defined within the claims.

[0043] Further, please note that although the following description of some embodiments of the present disclosure is given in the context of 5G NR, the present disclosure is not limited thereto. In fact, as long as selection of cell for network access in a cell delegation scenario is involved, the inventive concept of the present disclosure may be applicable to any appropriate communication architecture, for example, to Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS), Enhanced Data Rates for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Time Division - Synchronous CDMA (TD- SCDMA), CDMA2000, Worldwide Interoperability for Microwave Access (WiMAX), Wireless Fidelity (Wi-Fi), 4th Generation Long Term Evolution (LTE), LTE -Advance (LTE-A), 5GNR, or 6G, etc. Therefore, one skilled in the arts could readily understand that the terms used herein may also refer to their equivalents in any other infrastructure. For example, the term “terminal device” used herein may refer to a UE, a mobile device, a mobile terminal, a mobile station, a user device, a user terminal, a wireless device, a wireless terminal, or any other equivalents. For another example, the term “network node” used herein may refer to a transmission reception point (TRP), a base station (BS), a base transceiver station, an access point, a hot spot, a NodeB, an Evolved NodeB (eNB), a gNB, a network element, or any other equivalents.

[0044] Synchronization Signal Block (SSB)

[0045] The SSB consist of Primary / Secondary Synchronization Signal (SS) and Physical Broadcast Channel (PBCH). SS is used for the user equipment (UE) to blind search or via SSB Measurement Timing Configuration (SMTC) support to find a reference signal (time & frequency) and be able to measure on. For blind search detection, the SSBs need to be allocated on the GlobalSynchronization Raster Channel (GSCN) position, see TS 38.101.1 version 18.3.0 subclause 5.4.2. PBCH has the Master Information Block (MIB). The MIB contains information like: Pdcch- ConfigSIBl, which defines the common search space for the so called Remaining Minimum System Information (RMSI). Basically, it defines how to find and receive a SIB1. The MIB also contains information like: CellBarred information, Etc.

[0046] If the SSB is not associated with a RMSI, then the SSB is not a cell defining SSB. So SSB can be Cell defining or non-Cell defining.

[0047] The SSB is not a cell, it is only a signal which has the capability to point out a NR Cell.

[0048] The size of the SSB is 240 subcarriers wide (3.6 MHz with 15 kHz subcarrier spacing) and 4 symbols in length. Accordingly, the SSB does not necessarily cover the whole carrier. Neither is the SSB is to one position at the carrier, it can be located at one of multiple different 3rd Generation Partnership Project (3GPP) defined positions per carrier, both in frequency and time, position of preference. There are 1008 different PCI possible for the same time / frequency allocation. If two SSBs use same SSB frequency and same Subcarrier spacing, then the relation between the 2 SSB transmissions are from UE measurement perspective an intra frequency relation. If either SSB frequency or SSB subcarrier spacing differs, it is a inter frequency relation and may require measurement gap to be configured.

[0049] The SSB is only a signal, and there can be multiple SSBs on the same carrier, each a cell defining and pointing to a corresponding System Information Block 1 (SIB 1) or a mix that some added SSBs are not cell defining, but only added as a UE measurement reference (time, frequency & reporting).

[0050] NR Cell

[0051] As pointed out in the previous section of SSB, the SSB is only a signal which the UE can easily blind or via SMTC support detect, measure, use as a reference at and optionally get additional information about the SIB1. The SSB by itself does not automatically say anything about a NR cell, it points to additionally (Remaining Minimum System Information (RMSI), SIB1..N ) system information that defines a cell. A NR cell is not a predefined entity, the SIBs define the NR Cell. It defines things like: where and how the signals are broadcasted; spectrum that is used; Control Resource Set (CORESET) configuration; the random-access resources existence; etc.

[0052] The key in NR, is that carriers used for this is just an available resource, it is not exclusively for one NR Cell. If a NR Cell is allocated to a sector carrier, it does not prevent additional NR Cells on this same sector carrier. If a UE is connected to a NR cell (pointed out by SSB and configured by SIBs), the UE knows how to communicate with the system via this configuration. Another UE connected to another NR Cell (pointed out by another SSB and its SIB configuration)on the same sector carrier is communicating with the system via its NR Cell configuration. That these different communication configurations occur on the same sector carrier is no difference compared to in LTE where two UEs at a cell border are connected to different cells, see Fig. 1, which shows two NR Cells on different sector carriers by the left plot and two NR Cells sharing the same sector carrier by the right plot.

[0053] Further, from a measurement perspective, each SSB is also equal. The UEs will measure and report, e.g. via Radio Resource Control (RRC), to the system any SSB measurement fulfilling the conditions. The UEs in Fig. 1 shows no difference between the cells in the left plot vs. the right plot. An SSB is in this case only a signal reference to measure and report, independently of it is using the same sector carrier or not, or if it is cell defining or not.

[0054] Paging

[0055] In the 5G system, connection may be established either due to UE data becoming available on the Core Network(CN) side or at the UE side itself. How the connection is established is very similar in both cases, the main difference is that in the former case, before the actual connection establishment begins, the network initiates a procedure called Paging.

[0056] Since in the RRC IDLE state, UE’s position is known at maximum with Tracking Area granularity, the Core Network does not know to which Radio Access Network (RAN) node to route the UE's data. It firstly needs to identify the exact (next) generation NodeB (gNB) under the coverage of which UE currently is and this is done by using CN-initiated Paging procedure. In RRC_INACTIVE state, UE's position is known by the network on a RAN Notification Area level (RNA), which may cover multiple gNBs. Since from CN perspective the UE is still in a connected state, the CN does not send Paging, but simply forwards user data to the last known gNB that has served the UE, which initiates RAN-initiated Paging procedure. RAN paging may require forwarding Paging message also to other gNBs within the RNA of the UE.

[0057] Paging procedure is also used to notify the UEs about the modifications of the System Information and about presence of Earthquake and Tsunami Warning System (ETWS) / Commercial Mobile Alert System (CMAS) indications. From the perspective of radio interface, the procedures are virtually the same and can be realized either with Paging messages sent over Paging Control Channel (PCCH) or with so called Short Messages sent directly over Physical Downlink Control Channel (PDCCH) with physical layer signaling message called Downlink Control Information (DCI). In RRC IDLE and RRC INACTIVE states, the UE is monitoring for these notifications in paging channels. To save the UE battery, the UE is required to monitor for paging in only a single Paging Occasion (PO) per its Idle mode Discontinuous Reception (DRX) cycle. A PO is a set of PDCCH monitoring occasions, which can consist of multiple time slotswhere paging DCI can be sent. The PO is determined by the UE based on UE's identity (e.g. 5G S- Temporary Mobile Subscriber Identity (5G-S-TMSI)) and additional parameters signaled by the network such as, e.g. DRX configuration. In case of multi-beam operation, the same paging message should be repeated over all of the beams, so that the UE may choose any beam it prefers for its reception.

[0058] When UE is in IDLE / INACTIVE state, UE monitors PDCCH whose transmission occasions are configured by gNB every DRX cycle. DRX cycle can be 320ms, 640ms, 1280ms, and 2560ms. 3GPP Release (Rel)-17 extends the DRX to enable longer DRX period, called extended DRX (eDRX). With eDRX, it is possible to extend DRX cycle up to 2.91 hours.

[0059] In NR, the paging occasions are associated with SS burst. There are two possible ways to multiplex SSB and paging occasion (PO): SSB FDMed with PO or SSB TDMed with PO.

[0060] Random access procedure in NR

[0061] In NR the UE may be configured by the network to transmit random access (RA) in a cell (e.g. serving cell or a neighbor cell) using 4-step RA procedure and / or using 2-step RA procedure.

[0062] 4-step RA type

[0063] The principle of this procedure in NR is shown in Fig. 2. It involves 4 steps each comprising one message (uplink (UL) or downlink (DL)).

[0064] Step 1: Preamble transmission: The UE randomly selects a RA preamble (PREAMBLE INDEX) corresponding to a selected SS / PBCH block, transmits the preamble on the PRACH occasion mapped by the selected SS / PBCH block. When the base station (BS) (e.g. gNB) detects the preamble, it estimates the Timing advance (TA) the UE should use in order to obtain UL synchronization at the BS (e.g. gNB). The “RA preamble transmission” by the UE is also called as Message # 1 (Msgl).

[0065] Step 2: RA response (RAR): The BS (e.g. gNB) sends a RA response (RAR) including the TA, the Temporary Cell Radio Network Temporary Identifier (TC-RNTI) to be used by the UE, a Random Access Preamble identifier that matches the transmitted PREAMBLE INDEX and a grant for message 3 (Msg3). The UE expects the RAR and thus, monitors PDCCH addressed to RA- RNTI to receive the RAR message from the BS (e.g. gNB) until the configured RAR window (ra- ResponseWindow) has expired or until the RAR has been successfully received.

[0066] Step 3: “Msg3” (UE identity (ID) or UE-specific Cell RNTI (C-RNTI)): In Message 3 (Msg3), the UE transmits its identifier (UE ID) for initial access or if it is already in RRC CONNECTED or RRC INACTIVE mode and needs to e.g. re-synchronize, its UE-specific RNTI.

[0067] If the BS (e.g. gNB) cannot decode Msg3 at the granted UL resources, it may send a DCI addressed to TC-RNTI for retransmission of Msg3. Hybrid Automatic Repeat Request (HARQ) retransmission is requested until the UE restarts the random access procedure from step 1 after reaching the maximum number of HARQ retransmissions or until Msg3 can be successfully received by the BS (e.g. gNB). The “UE ID transmission” by the UE is also called as Message 3 (Msg3).

[0068] Step 4: “Msg4” (contention resolution): In Message 4 (Msg4) the BS (e.g. gNB) responds by acknowledging the UE ID or C-RNTI. The Msg4 gives contention resolution, i.e. only one UE ID or C-RNTI will be sent even if several UEs have used the same preamble (and the same grant for Msg3 transmission) simultaneously. For Msg4 reception, the UE monitors TC-RNTI (if it transmitted its UE ID in Msg3) or C-RNTI (if it transmitted its C-RNTI in Msg3). The “UE ID transmission” by BS for contention resolution is also called as Message 4 (Msg4).

[0069] 2-step RA type

[0070] The 2-step RA type gives much shorter latency than the ordinary 4-step RA. In the 2-step RA, the RA preamble (Msgl) and a message corresponding to Msg3 (Message A (msgA) Physical Uplink Shared Channel (PUSCH)) in the 4-step RA can, depending on configuration, be transmitted in two subsequent slots. The msgA PUSCH is sent on a resource dedicated to the specific RA preamble. This means that both the preamble and the Msg3 face contention but contention resolution in this case means that either both preamble and Msg 3 are sent without collision or both collide. The 2-step RA procedure is depicted in Fig. 3. Upon successful reception msgA, the gNB will respond with a Message B (msgB). The msgB may be either a “successRAR”, “fallbackRAR or “Back off’. In particular that fallbackRAR provides a grant for a Msg3 PUSCH that identifies resources in which the UE should transmit the PUSCH, as well as other information.

[0071] If both the 4-step and 2-step RA are configured in a cell on shared Physical Random Access Channel (PRACH) resources (and for the UE), the UE will choose its preamble from one specific set if it wants to do a 4-step RA, and from another set if it wants to do a 2-step RA. Hence a preamble partition is done to distinguish between 4-step and 2-step RA when shared PRACH resources are used. Alternatively, the PRACH configurations are different for the 2-step and 4-step RA procedure, in which case it can be deduced from where the preamble transmission is done if the UE is doing a 2-step or 4-step procedure.

[0072] Each PRACH preamble maps to a PUSCH occasion and a DeModulation Reference Signal (DMRS) port and / or a DMRS port-scrambling sequence combination according to a procedure given in 3GPP TS 38.213 V17.0.0, which is incorporated herein by reference in its entirety. This mapping allows a BS (e.g. gNB) to uniquely determine the location of the associated PUSCH intime and frequency as well as the DMRS port and / or scrambling from the preamble selected by the UE.

[0073] The PRACH preambles also map to associated SSBs. The SSB to preamble association combined with the preamble to PUSCH association allow a PO to be associated with a RACH preamble. This indirect preamble to PUSCH mapping may be used to allow a gNB using analog beamforming to receive a MsgA PUSCH with the same beam that it uses to receive the MsgA RACH preamble.

[0074] RACH occasion

[0075] In NR, since BS (e.g. gNB) controls the UL transmission to avoid the collision among UEs, the BS (e.g. gNB) assigns the dedicated UL resources in frequency and time domain. One exception is the case when UE will make an initial access to gNB from IDLE / INACTIVE states. Random access is the procedure used when the UE initiates a connection with the BS (e.g. gNB). In both 4- step RA type and 2-step RA type procedures, the UE transmits random access preamble using PRACH at the beginning of random access attempts. Since BS (e.g. gNB) does not know when the UE initiates the random access, therefore the BS (e.g. gNB) allocates the UL resources for PRACH periodically, called RACH periodicity. RACH periodicity is configurable, e.g., 10ms. 20ms, 40ms, 80ms, and 160ms. Fig. 4 illustrates the relation between RACH occasion and paging period (or DRX cycle).

[0076] The proposed solution is a mechanism for a terminal device (e.g. UE) served by a cell, which in turn is served or managed or operated by a first network, e.g. gNB, node, monitoring paging (DCI) and initiating RACH procedure with respect to the solutions proposed in the invention, especially for purpose of the network energy saving.

[0077] The core essence of the solution is to define sets of rules on monitoring paging and initiating RACH procedure, for the sake of flexibility to support network energy saving.

[0078] Fig. 5 is a flow chart of an exemplary method 500 at a terminal device according to an embodiment of the present disclosure. The method 500 may be performed at a terminal device (e.g., the UE). The method 500 may comprise steps S502 and S504. However, the present disclosure is not limited thereto. In some other embodiments, the method 500 may comprise more steps, less steps, different steps, or any combination thereof. Further the steps of the method 500 may be performed in a different order than that described herein when multiple steps are involved. Further, in some embodiments, a step in the method 500 may be split into multiple sub-steps and performed by different entities, and / or multiple steps in the method 500 may be combined into a single step.

[0079] The method 500 may begin with step S502.

[0080] At step S502, the terminal device receives, from a network node, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device.

[0081] At step S504, the terminal device receives a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

[0082] In some embodiments, the configuration comprises a first identity (ID) of the terminal device and / or a second identity (ID) of the group of terminal devices.

[0083] In some embodiments, for the normal paging scheme, the terminal device is associated with a paging occasion (PO), and / or for the power-saving paging scheme, the group of terminal devices is associated with a PO.

[0084] In some embodiments, the group of terminal devices are associated with a same area.

[0085] In some embodiments, the group of terminal devices are determined based on at least one of: subscription of the terminal devices, service, or application.

[0086] In some embodiments, the terminal device may further receive indication of a paging scheme to be applied or changed and / or time to apply or change the paging scheme.

[0087] In some embodiments, the indication is received via at least one of: a Radio Resource Control (RRC) signaling; a broadcasted system information (SI); or a paging message.

[0088] In some embodiments, the terminal device may further determine a paging scheme to be applied or changed based on the indication and / or a rule.

[0089] In some embodiments, the terminal device may further determine a PO which the terminal device shall monitor based on at least one of: the configuration, the indication, the rule, the first identity of the terminal device, or the second identity (ID) of the group of terminal devices.

[0090] In some embodiments, the indication of the paging scheme is associated with a serving cell of the terminal device, or one or more cells other than the serving cell.

[0091] In some embodiments, the terminal device may further transmit a signal, to the network node, to trigger the network node to transmit a scheduling message for the paging message or to transmit the paging message.

[0092] In some embodiments, the signal comprises the paging mechanism expected or recommended by the terminal device.

[0093] In some embodiments, the paging message is associated with a direction.

[0094] In some embodiments, the terminal device may further determining the power-saving paging scheme to be applied or changed to, when the network node is in an energy saving state.

[0095] In some embodiments, the terminal device may further obtain a paging change window for transition between different paging mechanisms, wherein in the paging change window, the terminal device is not expected to receive paging message from the network node.

[0096] In some embodiments, the change window is related to a Start time and / or a Duration.

[0097] In some embodiments, the terminal device may further receive, in a first PO or first multiple POs after changing between different paging mechanisms, a same paging message, as the paging message received in a last PO or last multiple POs before changing between different paging mechanisms.

[0098] Fig. 6 is a flow chart of an exemplary method 600 at a network node according to an embodiment of the present disclosure. The method 600 may be performed at a network node (e.g., the gNB). The method 600 may comprise a step S602 and S604. However, the present disclosure is not limited thereto. In some other embodiments, the method 600 may comprise more steps, less steps, different steps, or any combination thereof. Further the steps of the method 600 may be performed in a different order than that described herein when multiple steps are involved. Further, in some embodiments, a step in the method 600 may be split into multiple sub-steps and performed by different entities, and / or multiple steps in the method 600 may be combined into a single step.

[0099] The method 600 may begin with step S602.

[0100] At step S602, the network node transmits, to a terminal device, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device.

[0101] At step S604, the network node transmits a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

[0102] In some embodiments, the configuration comprises a first identity (ID) of the terminal device and / or a second identity (ID) of the group of terminal devices.

[0103] In some embodiments, for the normal paging scheme, the terminal device is associated with a paging occasion (PO), and / or for the power-saving paging scheme, the group of terminal devices is associated with a PO.

[0104] In some embodiments, the group of terminal devices are associated with a same area.

[0105] In some embodiments, the group of terminal devices are determined based on at least one of: subscription of the terminal devices, service, or application.

[0106] In some embodiments, the network node may further transmit indication of a paging scheme to be applied or changed and / or time to apply or change the paging scheme.

[0107] In some embodiments, the indication is transmitted via at least one of: a Radio Resource Control (RRC) signaling; a broadcasted system information (SI); or a paging message.

[0108] In some embodiments, the indication of the paging scheme is associated with a serving cell of the terminal device, or one or more cells other than the serving cell.

[0109] In some embodiments, the network node may further receive a signal, from the terminal device, to trigger the network node to transmit a scheduling message for the paging message or to transmit the paging message.

[0110] In some embodiments, the signal comprises the paging mechanism expected or recommended by the terminal device.

[0111] In some embodiments, the paging message is associated with a direction.

[0112] In some embodiments, the network node may further transmit a message indicating a paging change window for transition between different paging mechanisms, wherein in the paging change window, the terminal device is not expected to receive paging message from the network node.

[0113] In some embodiments, the change window is related to a Start time and / or a Duration.

[0114] In some embodiments, the network node may further transmit, in a first PO or first multiple POs after changing between different paging mechanisms, a same paging message, as the paging message received in a last PO or last multiple POs before changing between different paging mechanisms.

[0115] The above embodiments provide enhancements on monitoring paging that shall be solved in the work item: network energy saving.

[0116] Fig. 7 is a flow chart of an exemplary method 700 at a terminal device according to an embodiment of the present disclosure. The method 700 may be performed at a terminal device (e.g., the UE). The method 700 may comprise steps S702 and S704. However, the present disclosure is not limited thereto. In some other embodiments, the method 700 may comprise more steps, less steps, different steps, or any combination thereof. Further the steps of the method 700 may be performed in a different order than that described herein when multiple steps are involved. Further, in some embodiments, a step in the method 700 may be split into multiple sub-steps and performed by different entities, and / or multiple steps in the method 700 may be combined into a single step.

[0117] The method 700 may begin with step S702.

[0118] At step S702, the terminal device receives, from a network node, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource.

[0119] At step S704, the terminal device performs random access based on the configuration of the RACH occasion and / or RACH resource.

[0120] In some embodiments, the message is a paging message or a scheduling message for the paging message.

[0121] In some embodiments, the message comprises at least one of:• a field to indicate the RACH occasion and / or RACH resource;• an indicator or index for the beam and / or direction where the network node expects the terminal device to initiate RACH procedure using the RACH occasion and / or RACH resource;• an index of the RACH occasion and / or RACH resource which is in a RACH resource pool common to a group of terminal devices;• an index of the RACH occasion and / or RACH resource of a plurality of configured / preconfigured RACH occasions and / or RACH resources.

[0122] In some embodiments, the number of RACH resources depends on a number of terminal devices intended to be paged in a same paging message.

[0123] In some embodiments, the terminal device may further receive a signaling indicating whether the terminal device shall use the RACH occasion and / or RACH resource to initiate a RACH procedure.

[0124] In some embodiments, the signaling is at least one of: system information (SI), a Radio Resource Control (RRC) signaling; a paging message, a Media Access Control (MAC) Control Element (CE), a layer 1(L1) signaling.

[0125] In some embodiments, wherein the RACH occasion and / or RACH resource is for a latency-critical service.

[0126] In some embodiments, before the step of receiving the message, the terminal device may further transmit a wakeup signaling to the network node.

[0127] In some embodiments, the wakeup signaling comprises at least one of: an identity of the terminal device, a type / reason why the RACH procedure is triggered for the terminal device, or a time when the terminal device is expected to initiate the RACH procedure.

[0128] Fig. 8 is a flow chart of an exemplary method 800 at a network node according to an embodiment of the present disclosure. The method 800 may be performed at a network node (e.g., the gNB). The method 800 may comprise a step S802 and S804. However, the present disclosure is not limited thereto. In some other embodiments, the method 800 may comprise more steps, less steps, different steps, or any combination thereof. Further the steps of the method 800 may be performed in a different order than that described herein when multiple steps are involved.Further, in some embodiments, a step in the method 800 may be split into multiple sub-steps and performed by different entities, and / or multiple steps in the method 800 may be combined into a single step.

[0129] The method 800 may begin with step S802.

[0130] At step S802, the network node transmits, to a terminal device, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource.

[0131] At step S804, the network node receives an access request from the terminal device.

[0132] In some embodiments, the message is a paging message or a scheduling message for the paging message.

[0133] In some embodiments, the message comprises at least one of:• a field to indicate the RACH occasion and / or RACH resource;• an indicator or index for the beam and / or direction where the network node expects the terminal device to initiate RACH procedure using the RACH occasion and / or RACH resource;• an index of the RACH occasion and / or RACH resource which is in a RACH resource pool common to a group of terminal devices;• an index of the RACH occasion and / or RACH resource of a plurality of configured / preconfigured RACH occasions and / or RACH resources.

[0134] In some embodiments, the number of RACH resources depends on a number of terminal devices intended to be paged in a same paging message.

[0135] In some embodiments, the network node may further transmit a signaling indicating whether the terminal device shall use the RACH occasion and / or RACH resource to initiate a RACH procedure.

[0136] In some embodiments, the signaling is at least one of: system information (SI), a Radio Resource Control (RRC) signaling; a paging message, a Media Access Control (MAC) Control Element (CE), a layer 1(L1) signaling.

[0137] In some embodiments, wherein the RACH occasion and / or RACH resource is for a latency-critical service.

[0138] In some embodiments, before the step of transmitting the message, the network node may further receive a wakeup signaling from the terminal device.

[0139] In some embodiments, the wakeup signaling comprises at least one of: an identity of the terminal device, a type / reason why the RACH procedure is triggered for the terminal device, or a time when the terminal device is expected to initiate the RACH procedure.

[0140] The various blocks shown in Figs.5-8 may be viewed as method steps, and / or as operations that result from operation of computer program code, and / or as a plurality of coupled logic circuit elements constructed to carry out the associated function(s). The schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

[0141] Fig. 9 schematically shows an embodiment of an arrangement which may be used in a terminal device or a network node according to an embodiment of the present disclosure. As shown in Fig. 9, the apparatus 900 may comprise one or more processors such as processor 901, and one or more memories such as memory 902, storing computer program codes 903. The memory 902 may be non-transitory machine / processor / computer readable storage medium. In accordance with some exemplary embodiments, the apparatus 900 may be implemented as an integrated circuit chip or module that can be plugged or installed into a terminal device as described with respect to Fig.5 or Fig.7, and anetwork node as described with respect to Fig.6 or Fig.8. In such cases, the apparatus 900 may be implemented as terminal device as described with respect to Fig.5 or Fig.7, or a network node as described with respect to Fig.6 or Fig.8.

[0142] In some implementations, the one or more memories 902, and the computer program codes 903, may be configured to, with the one or more processors 901, cause the apparatus 900 at least to perform any operation of the method as described in connection with Fig.5 or Fig.7. In other implementations, the one or more memories 902, and the computer program codes 903, may be configured to, with the one or more processors 901, cause the apparatus 900 at least to perform any operation of the method as described in connection with Fig.6 or Fig.8. Alternatively or additionally, the one or more memories 902 and the computer program codes 903 may be configured to, with the one or more processors 901, cause the apparatus 900 at least to perform more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

[0143] Hereinafter, the solutions will be further described as follows.

[0144] Embodiments on paging

[0145] To address the delay issue due to application of cell DTX, a straightforward approach is designing the concept and mechanism of ‘power-saving paging’ that groups more than one UEs to same paging occasions, i.e., one paging occasion is mapped to more than one UE, e.g.reformulating paging occasions, defining a new group UE ID, e.g., Temporary Mobile Subscriber Identity (TMSI) for the UEs in a paging group. With this mechanism, the network will always attempt to ping multiple UEs on the same paging occasion. UEs which are distributed on different Pos according to their own ID e.g., TMSI, would be rearranged to the same set of POs. The followed shortcomings are the extra delay and less capability to serve numerous UEs. To serve the purpose, the solution dealing with the purpose issue and mitigating the drawbacks of the current method is described in the following.

[0146] In the power-saving paging mechanism, one or multiple power-saving paging groups are configured / preconfigured to UEs in the same area (e.g., the same registration area or the same RAN paging area). The configuration / information on the paging groups are provisioned to the UE (e.g., the configuration / information on the paging groups may be associated with the UE’s subscription, or one or multiple services / applications).

[0147] In one embodiment, a UE, if the UE has capability to support the power-saving paging and the normal paging mechanism, applies / changes the normal / legacy paging scheme or the power-saving paging according to the gNB configurations and information (e.g., UE ID and group UE ID) on the normal paging and / or the power-saving paging. Additionally, the UE is provided of the indication of the paging mechanism, i.e. which paging configuration shall be applied by the UE via indication in RRC signaling or broadcasted system information (SI) or paging message. In the latest one, the paging message shall be extended to contain at least an indication of the time when the paging scheme changes / starts to apply.• In one example, the last received paging message indicates that the next paging occasion shall be changed to the different paging mechanism, either from normal paging to powersaving paging or from power-saving paging to normal paging.• In another example, the last received paging message indicates the reference time, e.g. System Frame Number (SFN) that paging scheme changes from, either from normal paging to power-saving paging or from power-saving paging to normal paging.

[0148] To the end, the UE is able to determine the paging occasions which the UE shall monitor with respect to the received paging configuration, the indication of paging configuration (normal paging scheme or power-saving paging) and the UE ID / group UE ID.

[0149] In one variant of the embodiment, the indication of a paging scheme may be applied by the serving cell serving the UE, or the indication indicates the paging scheme applied by a or more than one cell other than serving cell, e.g., the cells (intra-frequency, inter-frequency or both) in the neighbor cell lists. In the latter one, the gNB may provide the association or mapping between the paging scheme and identity of the cell (s), e.g., cell ID.

[0150] In another variant of the embodiment, the UE may send a signal to the gNB, besides of the above approaches, which triggers the gNB to transmit paging (paging DCI and paging message), for example when the gNB is in sleeping mode. The signal may contain the indication of paging mechanism, either normal paging or power-saving paging, expected or recommended by the UE.

[0151] In another variant of embodiment, the paging transmitted by the gNB is spatial- wise different, e.g. the gNB may apply different paging mechanism at different directions. One example is that the gNB provides set of association between SSB (index) and paging scheme to the UE, the UE accordingly shall adopt the paging scheme with respect to received SSB (index), e.g. the strongest received SSB (index), and the information of the association between SSB (index) and paging scheme.

[0152] In another embodiment, the gNB doesn’t indicate the paging scheme that UE shall apply, instead, the UE shall apply a predefined rule to find the paging occasions, some examples of the rule are presented as follows:• In one example, the UE shall by default detect the paging occasions set according to the power-saving paging configuration. If the UE cannot detect any paging message successfully, then the UE shall secondly detect the paging occasions set by normal paging configuration. o In an example, a timer with a given timer value may be defined for the UE to try the first paging mechanism. The UE falls back to the second paging mechanism when the timer is expired if the UE cannot detect any paging message using the first paging mechanism while the timer is running.• In another example, the UE shall by default detect the paging occasions set according to the normal paging configuration. If the UE cannot detect any paging occasion successfully, then the UE shall secondly detect the paging occasions set by power-saving paging configuration. o In an example, a timer with a given timer value may be defined for the UE to try the first paging mechanism. The UE falls back to the second paging mechanism when the timer is expired if the UE cannot detect any paging message using the first paging mechanism while the timer is running.• In another example, the UE shall by default apply the normal paging scheme if the gNB doesn’t provide group UE ID. By contrast, the UE shall by default apply the normal paging scheme if the gNB provides group UE ID.

[0153] In another embodiment, if the UE is provided of the information on the network energy saving state of the gNB, the UE shall apply paging scheme accordingly. In one example, if the gNB serving the UE is in a power saving state applying various features including, e.g. SSB less, cell DTX / DRX, sleep mode, etc., then the UE shall apply power-saving paging configuration. Otherwise, the UE applies normal paging configuration. Furthermore, if the gNB changes the network energy saving state, the UE shall update the paging scheme accordingly with respect to determination by the UE or the received signaling (RRC signaling, MAC CE or LI signaling) indicating network energy saving state by the gNB.

[0154] Once the gNB changes the paging mechanism for the UE by indication as described in above embodiments, the change between different paging mechanisms may cause paging interruption resulting by process change in UE implementation. Robustness in the change between different paging mechanisms is an issue are addressed by the following embodiments.

[0155] In one embodiment, a UE shall be provided with a paging change window for transition between different paging mechanisms. In the paging change window, the UE is not expected to receive paging message from the gNB serving the UE, the paging change window shall at the least consider the follow parameters:• Start time: it may start from the time that UE receives the paging change command from the gNB.• Duration: it may be pre-defined (e.g. XI ms, wherein XI is a time length, or X2 number of SSB periodicities / SMTC periodicities / DRX cycles, wherein X2 is a integer number) or configurable by the gNB.

[0156] A particular example of the embodiment is that a UE is not expected to monitor downlink channels of the serving cell for paging reception during XI ms or X2 SSB periodicities / SMTC periodicities / DRX cycles after the UE receives the indication / message to change paging mechanism.

[0157] Yet in another embodiment, in the first paging occasion or first multiple paging occasions after change between different paging mechanisms, the gNB shall repeat transmitting or retransmit the same content as in the last paging message before changing paging mechanism. The UE that receives the repeated paging message before and after changing paging scheme may be aware of the paging scheme change and doesn’t miss any information contained in paging occasions during the change between different paging mechanisms.

[0158] Embodiments on PRACH

[0159] Embodiments have elaborated how a UE triggers a RACH procedure using a scheduled RACH resource. It means that the UE obtains a scheduled RACH resource when theRACH procedure is triggered. Such RACH procedure may be also referred to as a scheduled RACH procedure. In case there is no scheduled RACH resource available, the UE can use the legacy manner to obtain a RACH resource, i.e., using a contention based manner to obtain a RACH resource among the common RACH resources.

[0160] In one of the embodiments, additional RACH occasions / resources are provisioned to a UE. The UE is triggered to initiate RACH procedures using these additional RACH occasions / resources upon reception of a specific paging message (the paging message may be also referred to as a paging message carrying scheduling info for RACH). These additional RACH occasions / resources may be also referred to as “scheduled RACH resources”.

[0161] The gNB applies one of the below options to schedule / indicate RACH resources for UEs which are being paged in a paging message.

[0162] Option 1: the paging message carries RACH occasions and / or RACH resources (i.e., PRACH preambles, PUSCH grants etc) in an explicit fashion. The paging message may also carry indicators / indices for the beams / directions where the gNB expects the UEs to initiate RACH procedures using these indicated RACH resources.

[0163] Option 2: the paging message doesn’t carry / indicate the additional PRACH resources / occasions explicitly. Instead, the paging message carries indices of RACH occasions and / resources which are in a RACH resource pool common to a group of UEs. In one of the examples, a set of RACH resources are configured for a group of UEs in the cell. This set of RACH resources is only valid for the group of UEs. Another set of RACH resources may be configured for another group of UEs in the cell. In one of the examples, a set of RACH resources are configured for all UEs in the same cell or in the same area (e.g., RAN paging area or registration area). Since the resources are common to the group of UEs, each resource may be associated with a resource index. It is sufficient to include indices of RACH resources and / or occasions in the paging message.

[0164] As an alternative option, a UE in a cell may be configured / preconfigured with multiple dedicated RACH resources and / occasions for scheduled RACH purpose, in case the gNB transmits a paging message only intended for this UE, the paging message can just carry an index of a RACH resource and / or occasion out of these dedicated RACH resources and / occasions.

[0165] Option 3: the DCI scheduling the paging message carries additional RACH resources and / or occasions in an explicit or an implicit fashion.

[0166] For any one of the above options, the number of additional RACH resources depends on the number of UEs intended to be paged in the same paging message. In other words, more UEs to be paged in the same paging message, more additional RACH resources arescheduled. Few UEs to be paged in the same paging message, few additional RACH resources are scheduled. In an example, the number of additional RACH resources equals to the number of UEs intended to be paged in the same paging message. Therefore, each UE can be scheduled with a different RACH resource. In another example, the number of additional RACH resources is lower than the number of UEs intended to be paged in the same paging message, in this case, each UE may attempt to obtain a RACH resource among all scheduled RACH resources in a contention based manner. A UE which fails to obtain a scheduled RACH resource, may attempt to obtain a RACH resource in a common RACH resource pool / set instead.

[0167] The benefits for a UE to use scheduled RACH resources are:• The probability that multiple UEs choose the same RACH resource is decreased. Therefore, the collision probability of RACH procedures between UEs is also decreased.• the gNB is aware of each scheduled RACH resource and / or RACH occasion. So the gNB will be most likely to keep itself active during the RACH occasion. Therefore, the RACH procedure / message initiated by a UE using a scheduled RACH resource will not be miss detected by the gNB. The overall latency for the RACH procedure can be kept / completed at a low level. This also means that in case the UE uses a non scheduled RACH resource to initiate a RACH procedure, the RACH procedure / message initiated by the UE may be missed by the gNB due to that the gNB is inactive during RACH occasions.

[0168] In one of the embodiments, the gNB sends a signaling to a UE indicating whether the UE shall use scheduled RACH resources to initiate a RACH procedure. The signaling message may be one of the below• system information, in this case, the gNB sends the signaling to all UEs in a cell specific fashion.• RRC signaling, in this case, the gNB may only send the signaling to a specific UE (i.e., in a UE dedicated manner)• Paging message. The paging message carries an indicator indicating whether a UE (which is the UE to be paged) shall use scheduled RACH resources to initiate a RACH procedure• MAC CE• LI signaling (e.g., DCI on PDCCH)

[0169] As an additional embodiment, the gNB may send a signaling (same signaling alternatives as in the above) to a UE indicating whether the UE shall use a RACH resource (obtained via a legacy manner, i.e., obtained using a contention based manner) to initiate a RACH procedure.

[0170] As an additional embodiment, in case a UE is only allowed to use scheduled RACH resources to initiate a RACH procedure, the UE will just wait to be scheduled with RACH resources by the gNB. Before the UE obtains any scheduled RACH resource, the UE will not initiate a RACH procedure even if the RACH procedure has been already triggered.

[0171] As an additional embodiment, in case a UE is allowed to use both scheduled RACH resources and RACH resources obtained in a legacy manner to initiate a RACH procedure, upon trigger of a RACH procedure, the UE will first check if there is any scheduled RACH resource available for the UE (e.g., within X ms period since the RACH procedure is triggered), if the answer is yes, the UE would use the scheduled RACH resource to initiate the RACH procedure, otherwise (i. e. , the UE doesn’t obtain any scheduled RACH resource within X ms period since the RACH procedure is triggered), the UE would attempt to obtain a RACH resource using a legacy manner, after that the UE uses those RACH resources to initiate the RACH procedure, wherein X is a pre-defined time length or configurable by the gNB.

[0172] In one example, given that the gNB sends a signaling to a UE indicating the scheduled RACH resources to initiate a RACH procedure, a signaling (in the same signaling or another new signaling) includes a validity timer for the scheduled RACH procedure. The timer shall be started / restarted once the UE receives the signaling and the UE shall be able to initiate the RACH procedure before the timer reaches the predefined or configurable threshold. If the UE doesn’t initiate the RACH procedure or the gNB doesn’t receive any message from the UE before time out, the gNB may resend the paging message and the signaling including validity timer for the scheduled RACH, with or without the request from the UE. Alternatively, if the UE doesn’t initiate the RACH procedure or the gNB doesn’t receive any message from the UE before time out, the gNB shall fall back and indicate the legacy RACH procedure to the UE.

[0173] In one of the embodiments, a UE may be configured to use scheduled RACH resources for a service with critical latency requirement, since the latency requirement can be ensured using scheduled RACH resources.

[0174] As an additional embodiment, the UE may be configured to use non-scheduled RACH resources, i.e., RACH resources obtained via a legacy manner) for a service without critical latency requirement, since the latency requirement may not be ensured using non-scheduled RACH resources.

[0175] In one of the embodiments, whenever a RACH procedure is triggered for a UE, the UE may first send a wakeup signaling to the gNB to wakeup the gNB, after that, the UE obtains a RACH resource and initiates the RACH procedure using the RACH resource. The wakeup signaling may contain at least one of the information• UE ID• Type / reason why the RACH procedure is triggered for the UE• The time when the UE is expected / wishes to initiate the RACH procedure

[0176] Fig. 10 shows an example of a communication system QQ100 in accordance with some embodiments.

[0177] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQllOb (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0178] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0179] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0180] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directlycoupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a 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 De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0181] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0182] As a whole, the communication system QQ100 of Fig. 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (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.

[0183] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunicationsnetwork QQ102 may 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)ZMassive loT services to yet further UEs.

[0184] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0185] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQllOb). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0186] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQl lOb. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQl lOb. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0187] Fig. 11 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0188] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0189] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may containmultiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0190] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0191] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0192] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0193] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0194] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0195] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0196] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0197] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0198] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0199] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), awearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Fig. 11.

[0200] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0201] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0202] Fig. 12 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0203] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as RemoteRadio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0204] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0205] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0206] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0207] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0208] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0209] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio frontend circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which arethen converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0210] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0211] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0212] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0213] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which isconnected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0214] Embodiments of the network node QQ300 may include additional components for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0215] Fig. 13 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, 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 functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0216] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment QQ500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0217] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0218] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0219] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0220] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0221] The present disclosure is described above with reference to the embodiments thereof. However, those embodiments are provided just for illustrative purpose, rather than limiting the present disclosure. The scope of the disclosure is defined by the attached claims as well as equivalents thereof. Those skilled in the art can make various alternations and modifications without departing from the scope of the disclosure, which all fall into the scope of the disclosure.

Claims

ClaimsWhat is claimed is:

1. A method (500) at a terminal device, comprising: receiving (502), from a network node, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and receiving (504) a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

2. The method according to claim 1, wherein the configuration comprises a first identity (ID) of the terminal device and / or a second identity (ID) of the group of terminal devices.

3. The method according to claim 1 or 2, wherein for the normal paging scheme, the terminal device is associated with a paging occasion (PO), and / or for the power-saving paging scheme, the group of terminal devices is associated with a PO.

4. The method according to any of claims 1-3, wherein the group of terminal devices are associated with a same area; and / or the group of terminal devices are determined based on at least one of: subscription of the terminal devices, service, or application.

5. The method according to any of claims 1-4, further comprising at least one of: receiving indication of a paging scheme to be applied or changed and / or time to apply or change the paging scheme, and / or the indication is received via at least one of: a Radio Resource Control (RRC) signaling; a broadcasted system information (SI); or a paging message; determining a paging scheme to be applied or changed based on the indication and / or a rule; determining a PO which the terminal device shall monitor based on at least one of: the configuration, the indication, the rule, the first identity of the terminal device, or the second identity (ID) of the group of terminal devices; transmitting a signal, to the network node, to trigger the network node to transmit a scheduling message for the paging message or to transmit the paging message; determining the power-saving paging scheme to be applied or changed to, when the network node is in an energy saving state; obtaining a paging change window for transition between different paging mechanisms,wherein in the paging change window, the terminal device is not expected to receive paging message from the network node; receiving, in a first PO or first multiple POs after changing between different paging mechanisms, a same paging message, as the paging message received in a last PO or last multiple POs before changing between different paging mechanisms.

6. The method according to claim 5, wherein the indication of the paging scheme is associated with a serving cell of the terminal device, or one or more cells other than the serving cell; and / or the signal comprises the paging mechanism expected or recommended by the terminal device; and / or the paging message is associated with a direction; and / or the change window is related to a Start time and / or a Duration.

7. A method (600) at a network node, comprising: transmitting (602), to a terminal device, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and transmitting (604) a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

8. The method according to claim 7, wherein the configuration comprises a first identity (ID) of the terminal device and / or a second identity (ID) of the group of terminal devices.

9. The method according to claim 7 or 8, wherein for the normal paging scheme, the terminal device is associated with a paging occasion (PO), and / or for the power-saving paging scheme, the group of terminal devices is associated with a PO.

10. The method according to any of claims 7-9, wherein the group of terminal devices are associated with a same area; and / or the group of terminal devices are determined based on at least one of: subscription of the terminal devices, service, or application.

11. The method according to any of claims 7-10, further comprising at least one of: transmitting indication of a paging scheme to be applied or changed and / or time to apply or change the paging scheme; and / or the indication is transmitted via at least one of: a Radio Resource Control (RRC) signaling; a broadcasted system information (SI); or a paging message.receiving a signal, from the terminal device, to trigger the network node to transmit a scheduling message for the paging message or to transmit the paging message; transmitting a message indicating a paging change window for transition between different paging mechanisms, wherein in the paging change window, the terminal device is not expected to receive paging message from the network node; transmitting, in a first PO or first multiple POs after changing between different paging mechanisms, a same paging message, as the paging message received in a last PO or last multiple POs before changing between different paging mechanisms.

12. The method according to claim 11, wherein the indication of the paging scheme is associated with a serving cell of the terminal device, or one or more cells other than the serving cell; and / or the signal comprises the paging mechanism expected or recommended by the terminal device; and / or the paging message is associated with a direction; and / or the change window is related to a Start time and / or a Duration.

13. An apparatus (900) implemented in a terminal device, comprising: one or more processors (901); and one or more memories (902) comprising computer program codes (903), the one or more memories (902) and the computer program codes (903) configured to, with the one or more processors (901), cause the apparatus (900) at least to: receive (502), from a network node, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and receive (504) a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

14. The apparatus according to claim 13, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus to perform the method according to any one of claims 2-6.

15. An apparatus (900) implemented in a network node, comprising: one or more processors (901); and one or more memories (902) comprising computer program codes (903),the one or more memories (902) and the computer program codes (903) configured to, with the one or more processors (901), cause the apparatus (900) at least to: transmit (602), to a terminal device, a configuration of a normal paging scheme for the terminal device and / or a power-saving paging scheme for a group of terminal devices comprising the terminal device; and transmit (604) a paging message based on the configuration of the normal paging scheme and / or the power-saving paging scheme.

16. The apparatus according to claim 15, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus to perform the method according to any one of claims 8-12.

17. A method (700) at a terminal device, comprising: receiving (702), from a network node, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource; and performing (704) random access based on the configuration of the RACH occasion and / or RACH resource.

18. The method according to claim 17, wherein the message is a paging message or a scheduling message for the paging message.

19. The method according to claim 17 or 18, wherein the message comprises at least one of: a field to indicate the RACH occasion and / or RACH resource; an indicator or index for the beam and / or direction where the network node expects the terminal device to initiate RACH procedure using the RACH occasion and / or RACH resource; an index of the RACH occasion and / or RACH resource which is in a RACH resource pool common to a group of terminal devices; an index of the RACH occasion and / or RACH resource of a plurality of configured / preconfigured RACH occasions and / or RACH resources.

20. The method according to any of claims 17-19, wherein a number of RACH resources depends on a number of terminal devices intended to be paged in a same paging message.

21. The method according to any of claims 17-20, further comprising:receiving a signaling indicating whether the terminal device shall use the RACH occasion and / or RACH resource to initiate a RACH procedure.

22. The method according to claim 21, wherein the signaling is at least one of: system information (SI), a Radio Resource Control (RRC) signaling; a paging message, a Media Access Control (MAC) Control Element (CE), a layer 1(L1) signaling.

23. The method according to any of claims 17-22, wherein the RACH occasion and / or RACH resource is for a latency-critical service.

24. The method according to any of claims 17-23, before receiving the message, the method further comprising: transmitting a wakeup signaling to the network node.

25. The method according to claim 24, wherein the wakeup signaling comprises at least one of: an identity of the terminal device, a type / reason why the RACH procedure is triggered for the terminal device, or a time when the terminal device is expected to initiate the RACH procedure.

26. A method (800) at a network node, comprising: transmitting (802), to a terminal device, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource; and receiving (804) an access request from the terminal device.

27. The method according to claim 26, wherein the message is a paging message or a scheduling message for the paging message.

28. The method according to claim 26 or 27, wherein the message comprises at least one of: a field to indicate the RACH occasion and / or RACH resource; an indicator or index for the beam and / or direction where the network node expects the terminal device to initiate RACH procedure using the RACH occasion and / or RACH resource; an index of the RACH occasion and / or RACH resource which is in a RACH resource pool common to a group of terminal devices; an index of the RACH occasion and / or RACH resource of a plurality of configured / preconfigured RACH occasions and / or RACH resources;29. The method according to any of claims 26-28, wherein a number of RACH resources depends on a number of terminal devices intended to be paged in a same paging message.

30. The method according to any of claims 26-29, further comprising: transmitting a signaling indicating whether the terminal device shall use the RACH occasion and / or RACH resource to initiate a RACH procedure.

31. The method according to claim 30, wherein the signaling is at least one of: system information (SI), a Radio Resource Control (RRC) signaling; a paging message, a Media Access Control (MAC) Control Element (CE), a layer 1(L1) signaling.

32. The method according to any of claims 26-31, wherein the RACH occasion and / or RACH resource is for a latency-critical service.

33. The method according to any of claims 26-32, before transmitting the message, the method further comprising: receiving a wakeup signaling from the terminal device.

34. The method according to claim 33, wherein the wakeup signaling comprises at least one of: an identity of the terminal device, a type / reason why the RACH procedure is triggered for the terminal device, or a time when the terminal device is expected to initiate the RACH procedure.

35. An apparatus (900) implemented in a terminal device, comprising: one or more processors (901); and one or more memories (902) comprising computer program codes (903), the one or more memories (902) and the computer program codes (903) configured to, with the one or more processors (901), cause the apparatus (900) at least to: receive (702), from a network node, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource; and perform (704) random access based on the configuration of the RACH occasion and / or RACH resource.

36. The apparatus according to claim 35, wherein the one or more memories and the computerprogram codes are configured to, with the one or more processors, cause the apparatus to perform the method according to any one of claims 18-25.

37. An apparatus (900) implemented in a network node, comprising: one or more processors (901); and one or more memories (902) comprising computer program codes (903), the one or more memories (902) and the computer program codes (903) configured to, with the one or more processors (901), cause the apparatus (900) at least to: transmit (802), to a terminal device, a message indicating a configuration of Random Access Channel (RACH) occasion and / or RACH resource; and receive (804) an access request from the terminal device.

38. The apparatus according to claim 37, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus to perform the method according to any one of claims 27-34.

39. A computer-readable medium having computer program codes (903) embodied thereon for use with a computer, wherein the computer program codes (903) comprise codes for performing the method according to any one of claims 1-12 and 17-34.

Images