Enhanced paging procedure for random access or small data transmission

Abstract

An apparatus supporting an enhanced paging procedure for random access or small data transmission is disclosed. An example UE may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, together with the at least one processor, to cause the UE to receive a paging message from a network device and to send a signal to the network device using an UL grant. The paging message may include an identity of the UE (UE ID) and the UL grant. Related methods, apparatus, and computer program products are also disclosed.

Description

Technical Field

[0001] Various example embodiments described herein relate generally to communication technology, and more particularly, to methods and apparatuses supporting an enhanced paging procedure for random access or small data transmission for Industrial Internet of Things (IIoT) User Equipment (UE). Background Art

[0002] Certain abbreviations that may be found in the specification and / or drawings are hereby defined as follows:

[0003] AMF Access and Mobility Management Function

[0004] BS Base Station

[0005] C-RNTI Cell-Radio Network Temporary Identifier

[0006] CN Core Network

[0007] eNB 4G base station

[0008] gNB 5G base station

[0009] IoT

[0010] LTE Long Term Evolution

[0011] Msg

[0012] NB-IoT Narrowband IoT

[0013] NR New Radio

[0014] RACH Random Access Channel

[0015] PRACH Physical Random Access Channel

[0016] PUSCH Physical Uplink Shared Channel

[0017] RAR Random Access Response

[0018] RRC Radio Resource Control

[0019] TA Timing Advance

[0020] UE User Equipment

[0021] Mobile communications will be a key enabler in achieving the goals of the Fourth Industrial Revolution (Industry 4.0). It comes with the need for coherent integration and migration strategies to transform existing industrial production, which is mainly based on fixed-line networks, to the next level of industrial production, which will utilize ubiquitous, highly reliable and ultra-low latency wireless communication networks. A key enabler of Industry 4.0 is the scalable and pervasive connectivity between machines, people and objects, which is known as the Industrial Internet of Things (IIoT), in which wireless connectivity will play a key role. Mobile and wireless communication systems also offer the benefit of removing cables from fixed, rotating or other equipment with limited mobility. Ubiquitous connectivity is a key feature of mobile communication systems, which enables flexible manufacturing setup and reconfiguration without being limited by available wiring. This means that devices in the factory that were previously connected by cables will be connected via wireless communication systems and follow wireless system protocols. Summary of the invention

[0022] The following provides a brief summary of exemplary embodiments to provide a basic understanding of some aspects of various embodiments. It should be noted that this summary is not intended to identify key features of essential elements or define the scope of the embodiments, and its sole purpose is to introduce some concepts in a simplified form as a prelude to the more detailed description provided below.

[0023] In a first aspect, an example embodiment of a UE is provided. The UE may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the UE to receive a paging message from a network device and to send a signal to the network device using a UL grant. The paging message may include an identity of the UE and the UL grant.

[0024] In a second aspect, an example embodiment of a network device is provided. The network device may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the network device to allocate an UL grant to a UE, send a paging message to the UE, and receive a signal sent from the UE using the UL grant. The paging message may include an identity of the UE and the UL grant.

[0025] In a third aspect, an example embodiment of a method implemented at a UE is provided. The method may include receiving a paging message from a network device and sending a signal to the network device using a UL grant. The paging message may include an identity of the UE and the UL grant.

[0026] In a fourth aspect, an example embodiment of a method implemented at a network device is provided. The method may include allocating an UL grant to a UE, sending a paging message to the UE, and receiving a signal sent from the UE using the UL grant. The paging message may include an identity of the UE and the UL grant.

[0027] In a fifth aspect, an example embodiment of an apparatus implemented at a UE is provided. The apparatus may include: means for receiving a paging message from a network device, and means for sending a signal to the network device using a UL grant. The paging message may include an identity of the UE and the UL grant.

[0028] In a sixth aspect, an example embodiment of an apparatus implemented at a network device is provided. The apparatus may include: means for allocating an UL grant to a UE, means for sending a paging message to the UE, and means for receiving a signal sent from the UE using the UL grant. The paging message may include an identity of the UE and the UL grant.

[0029] In a seventh aspect, an example embodiment of a computer program product is provided. The computer program product may be contained in at least one computer-readable medium and include instructions. When these instructions are executed by at least one processor of a UE, the UE may receive a paging message from a network device and send a signal to the network device using a UL grant. The paging message may include an identity of the UE and the UL grant.

[0030] In an eighth aspect, an example embodiment of a computer program product is provided. The computer program product may be contained in at least one computer-readable medium and include instructions. These instructions, when executed by at least one processor of a network device, may cause the network device to allocate an UL grant to a UE, send a paging message to the UE, and receive a signal sent from the UE using the UL grant. The paging message may include an identity of the UE and the UL grant.

[0031] Other features and advantages of the exemplary embodiments of the present application will also be apparent when the following description of specific embodiments is read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the exemplary embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Some example embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings.

[0033] Figure 1 An example four-step random access procedure is illustrated.

[0034] Figure 2An example two-step random access procedure for NR is illustrated.

[0035] Figure 3 An example scenario is illustrated to which embodiments of the present application may be applied.

[0036] Figure 4 An interaction diagram illustrating example operations for enhancing a paging procedure in accordance with some example embodiments.

[0037] Figure 5 An interaction diagram illustrating example operations for enhancing a paging procedure in accordance with some example embodiments.

[0038] Figure 6 An interaction diagram illustrating example operations for random access based on an enhanced paging procedure in accordance with some example embodiments.

[0039] Figure 7 A flow chart of an enhanced paging process is illustrated in accordance with some example embodiments.

[0040] Figure 8 A block diagram of an example device is illustrated according to some example embodiments.

[0041] Fig. 9 A flow chart of an enhanced paging process is illustrated in accordance with some example embodiments.

[0042] Fig.10 A block diagram of an example device is illustrated according to some example embodiments.

[0043] Fig.11 A block diagram of an example communication system is illustrated in which embodiments of the present application may be implemented.

[0044] In all drawings, the same or similar reference numerals indicate the same or similar elements, and repeated description of the same elements will be omitted. DETAILED DESCRIPTION

[0045] Hereinafter, some example embodiments will be described in detail with reference to the accompanying drawings. In order to provide a thorough understanding of various concepts, the following description includes specific details. However, it is obvious to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known circuits, techniques, and components are shown in block diagram form to avoid obfuscation of the concepts and features described.

[0046] In 5G / 4G and earlier mobile communication systems, when the network wants to connect to the UE, the network will send a paging message to the UE. After receiving the paging message, the UE will perform a random access procedure to initially access the network.

[0047] Figure 1The figure shows the four-step random access process. Figure 1 As shown, in step 1, UE 120 sends Msg1 including a preamble to BS 140 on PRACH. In step 2, BS 140 sends RAR as Msg2 to UE 120, which includes a time alignment command for adjusting the uplink transmission timing of UE 120 based on the timing of the received preamble, and UL grant. The following steps 3 and 4 will resolve the contention caused by simultaneous transmission with the same preamble from multiple UEs 120 within the cell. In step 3, UE 120 sends an RRC connection request as Msg3 to BS 140 using the UL grant allocated in Msg2. In step 4, BS 140 sends Msg4 including C-RNTI or the identity of the successfully connected UE 120 for contention resolution. And there may be an additional step 5 for sending Msg5 of the RRC response from the successfully connected UE 120 to BS 140. In this process, a collision occurs when multiple UEs 120 use the same preamble and start a random access procedure at the same time due to the limited number of preambles (64 or less) and PRACH frequency domain and timing domain resources. Only one UE 120 among the conflicting UEs 120 can connect to the BS 140, and the other UEs need to perform a random access procedure again.

[0048] In order to shorten the random access time, a two-step random access procedure is proposed for NR. Figure 2 Reference Figure 2 UE 120 sends MsgA combining Msg1 and Msg3 to BS 140 in step A, and BS 140 sends MsgB combining Msg2 and Msg4 to UE 120 in step B. Figure 1 Compared with the four-step process shown in , the two-step process can reduce the time length of the entire random access process, but because step A requires both PUSCH resources and RACH resources, the possibility of conflict is increased.

[0049] Figure 3The illustrated example is a scenario of a factory 300, where a large number of IIoT devices 120, such as UEs 120-1, 120-2, and 120-3, are wirelessly connected to a BS 140. In the factory 300, the network (control center) triggers a large number of devices 120 to start and start or prepare to work at substantially the same time every day, which means that all devices 120 start the random access process with the BS 140 at substantially the same time. In a traditional system where the devices 120 are connected to a cable, there is no problem for the devices 120 to be connected to the network at the same time. However, in a wireless system, many devices 120 may fail the contention-based random access process due to limited RACH and PUSCH resources, and they need to perform the random access process again and again. Devices that cannot be connected to the network in time will also cause other devices that rely on it to operate to not work and must wait. It takes a long time to get all devices 120 connected and ready to work. This is a waste of time and money for the factory.

[0050] IIoT devices 120 can be set to idle or inactive states to save power. When a device 120 in an idle or inactive state has UL or DL ​​data to send or receive, it needs to establish or resume an RRC connection with the network. Connection establishment / recovery and subsequent release / pause to idle / inactive state occurs for every data transmission, no matter how small and infrequent the data packets are. This results in unnecessary latency, power consumption, and signaling overhead.

[0051] An embodiment of an enhanced paging process is discussed below. The enhanced paging process can be used for random access procedures or small data transmissions, etc., which can shorten the time length and improve the efficiency of the process, especially for IIoT devices.

[0052] Figure 4 An interaction diagram illustrating example operations between a network device such as BS 140 and a terminal device such as UE 120 in an enhanced paging procedure according to some example embodiments. The enhanced paging procedure may be applied in a scenario such as a factory, where UE 120 does not move or moves only within a limited area when UE 120 is in an idle or inactive state. If UE 120 keeps moving when it is in an idle or inactive state, a conventional paging procedure may be applied. The enhanced paging procedure may be triggered by an access and mobility management function (AMF) sending a conventional paging for UE 120 to BS 140, or may be triggered by BS 140 when BS 140 has DL data for UE 120 or requires UL data from UE 120.

[0053] like Figure 4As shown, in operation 152, BS 140 may allocate an UL grant for UE 120. It is assumed that UE 120 is in RRC_IDLE or RRC_INACTIVE state, and BS 140 knows that UE 120 does not move or moves only within a limited area when in idle or inactive state, for example, by receiving a mode or capability indicator from UE 120. The allocated UL grant schedules PUSCH resources for UE 120 to send UL signals to BS 140. In operation 154, BS 140 may send an enhanced paging message to UE 120. Compared to a conventional paging message that includes only a UE identity, the enhanced paging message transmitted in operation 154 further includes a UL grant allocated to UE 120. Then in operation 156, UE 120 may send a signal to BS 140 using the UL grant.

[0054] Signal 156 may include any control signaling or data that UE 120 needs to send to BS 140. In some embodiments, signal 156 may include small and infrequent data for BS 140. Therefore, UL small data transmission is completed while UE 120 does not need to enter the RRC_CONNECTED state. It improves communication efficiency and saves power consumption and signaling overhead caused by the random access process.

[0055] In some embodiments, before sending the signal 156, the UE 120 adjusts its uplink transmission timing based on the timing advance (TA) in operation 155 to compensate for the propagation delay when the signal propagates between the UE 120 and the BS 140. When the UE 120 enters the RRC_IDLE or RRC_INACTIVE state, the TA may be stored at the BS 140 and / or the UE 120, and it has a value depending on the transmission delay between the UE 120 and the BS 140. Since the UE 120 does not move or moves only within a limited area when it is in the idle or inactive state, the TA stored when the UE 120 enters the idle or inactive state is still applicable throughout the period of time that the UE 120 is in the idle or inactive state, and a random access (RA) process is not required. In addition, the network knows which cell the UE 120 has camped on recently. In some embodiments, when UE 120 enters an idle or inactive state, the cell where UE 120 camps will store the UE's ID and TA, and the UE's ID and TA will be included in the paging message 154 along with the UL grant for UE 120. In some embodiments, UE 120 may also store its TA when it enters an idle or inactive state, and thus the paging message 154 need not include the TA for UE 120.

[0056] Figure 5 Another embodiment of an enhanced paging procedure is illustrated. Figure 5 Zhongyu Figure 4 The same or similar operations are indicated by the same or similar labels, and repeated descriptions will be omitted. Figure 4-5 The difference between the processes.

[0057] refer to Figure 5 In addition to the ID and UL authorization of the UE, the enhanced paging message 154' sent from the BS 140 to the UE 120 also includes DL data, RRC signaling or NAS signaling for the UE 120. The DL data can be any data for the UE 120 and it can originate from the BS 140, the core network or other networks or terminal devices. The signal 156' sent from the UE 120 to the BS 140 using the UL authorization may include a response to the confirmation reception of the paging message 154', the UL data, the RRC message or the NAS signaling. Therefore, the DL small data transmission is completed while the UE 120 does not need to enter the RRC_CONNECTED state. It improves communication efficiency and saves power consumption and signaling overhead caused by the random access process.

[0058] The enhanced paging procedure may also be used for random access in a scenario such as the factory 300 , where a large number of IIoT devices such as the UE 120 need to connect to the BS 140 at the same time. Figure 6 An interaction diagram illustrating example operations of a random access procedure with enhanced paging in accordance with some example embodiments.

[0059] refer to Figure 6 , when UE 120 first connects to the network of factory 300, the network does not have any information about UE 120, and a conventional initial random access procedure may be performed at operation 210 for UE 120 to access the network at BS 140. The conventional initial random access procedure may be Figure 1 The four-step process shown or Figure 2 The two-step process is shown.

[0060] Then, UE 120 may send a mode indicator or a capability indicator to BS 140 in operation 212. The mode / capability indicator indicates that UE 120 is in factory working mode and that it supports a customized random access procedure based on an enhanced paging message including UL grant and possible TA value. For example, UE 120 may set an information element (IE) such as factory working mode (factoryWorkingMode) to ON and send it to BS 140 as a mode / capability indicator. UE 120 may send the mode / capability indicator to BS 140 at any time before it enters an idle or inactive state. For example, the mode / capability indicator may be included in an RRC setup complete message (Msg5) sent to BS 140, or it may be sent to BS 140 when UE 120 reports its capabilities to BS 140. When BS 140 receives the mode / capability indicator from UE 120, it stores the mode / capability indicator in operation 214.

[0061] It is assumed that the UE 120 enters an idle or inactive state by releasing or suspending the RRC connection in operation 216. In operation 218, the BS 140 may store the ID and TA of the UE 120 when the UE 120 enters the idle or inactive state.

[0062] In operation 220, BS 140 may receive conventional paging for UE 120 from AMF (not shown). For example, AMF pages all UE 120 of factory 300 to trigger the random access process and prepare UE 120. Upon receiving the paging message for UE 120, BS 140 checks the mode / capability indicator of UE 120 in operation 222 to determine whether UE 120 supports enhanced paging messages. If so, BS 140 will initiate enhanced paging as described below for customized random access. Otherwise, BS 140 will initiate conventional paging to trigger conventional two-step or four-step random access.

[0063] It is further assumed that the mode / capability indicator (e.g., factory operation mode) is ON. In operation 224, BS 140 may allocate UL authorization and RRC resources for UE 120. If UE 120 is in an idle state, BS 140 may also allocate a cell-specific radio network temporary identifier (C-RNTI) for UE 120. If UE 120 is in an inactive state, it still maintains its C-RNTI for the cell in which it resides, and may use the maintained C-RNTI. In some embodiments, in operation 216, if the TA is stored at BS 140 when UE 120 enters an idle or inactive state, BS 140 also retrieves the TA of UE 120. The UL authorization, TA, and C-RNTI for UE 120 may be encapsulated in a random access response (RAR). If UE 120 is in an idle state, the allocated RRC resources may be encapsulated in an RRC setup message, or if UE 120 is in an inactive state, may be encapsulated in an RRC recovery message. In operation 226, BS 140 may send an enhanced paging message including an RAR payload (including UL grant and optional TA and C-RNTI) and an RRC setup or recovery message to UE 120. Therefore, the enhanced paging message sent in operation 226 combines Msg2 and Msg4 of the conventional random access procedure and does not require a PRACH preamble.

[0064] In operation 228, UE 120 may adjust its transmission timing based on the TA received in the paging message from BS 140 or stored at UE 120. In scenario factory 300, when the UE stops working and remains in an idle or inactive state, the IIoT UE does not move or can only move within a very limited area, so the TA state stored when UE 120 enters the idle or inactive state may still be used in operation 228. Then, UE 120 may send an RRC response to BS 140 using the UL grant in operation 230, and enter the RRC_CONNECTED state in operation 232. The RRC response may include, for example, an RRC setup or recovery complete message.

[0065] Compared with the traditional four-step or two-step random access process, the above-mentioned customized random access process based on the enhanced paging message only includes one step of sending the enhanced paging message. It greatly shortens the time length of the random access process. Because the PRACH preamble code is not used, the customized random access based on the enhanced paging process also avoids contention between multiple UEs. Therefore, a large number of UEs can be connected to the network at the same time. This is particularly beneficial for scenarios such as factory 300 where a large number of IIoT devices need to be connected to the network at the same time.

[0066] Figure 7A flow chart of an example method 300 for enhancing a paging process according to some example embodiments is illustrated. Figure 3-6 Let's read the following description of method 300. Method 300 can be performed at an IIoT UE such as UE 120, for example.

[0067] like Figure 7 As shown, the example method 300 may include a step 310 of receiving a paging message from a network device, and a step 320 of sending a signal to the network device. The paging message may include the identity of the UE and the UL grant allocated to the UE, and the signal may be sent using the UL grant. The network device may be, for example, a BS such as BS 140, and the signal may include any control signaling or uplink data for BS 140.

[0068] In some embodiments, the paging message may also include downlink data for the UE.The signal sent in step 320 may include a response to an acknowledgement of receipt of the downlink data at the UE.

[0069] In some embodiments, the paging message may also include an RRC setup or recovery message, and the example method 300 may also include a step 340 of entering a connected state from an idle or inactive state in response to the RRC setup or recovery message. In this case, the signal sent to the network device using the UL grant may include an RRC setup or recovery complete message sent when the UE enters the connected state.

[0070] In some embodiments, the paging message may also include a C-RNTI for the UE. For example, if the UE 120 is in an idle state and is about to enter a connected or inactive state, the C-RNTI for the UE 120 may be included in the paging message.

[0071] In some embodiments, the example method 300 may further include a step 330 of adjusting the transmission timing based on the TA of the UE before sending the signal 320. The TA may be stored at the network device when the UE enters an idle or inactive state and received in a paging message from the network device, or stored at the UE when the UE enters an idle or inactive state.

[0072] In some embodiments, the example method 300 may further include a step 350 of sending a mode indicator to the network device. The mode indicator may indicate whether the UE is in a mode that supports paging messages including UL grants. When the network device checks the mode / capability indicator and determines that the UE supports paging messages including UL grants, the network device will send a paging message in operation 310.

[0073] Figure 8A block diagram of an example device 400 is shown according to some example embodiments. The device 400 may be implemented in, for example, a UE 120 to perform Figure 7 The method 300 is shown. Figure 8 , the device 400 may include a first device (or module) 410 for performing step 310, and a second device 420 for performing step 320. The device 400 may also include a third device 430 for performing step 330, a fourth device 440 for performing step 340, and a fifth device 450 for performing step 350.

[0074] Fig. 9 A flow chart of an example method 500 for enhancing a paging process according to some example embodiments is illustrated. Figure 3-8 Please read the following description of method 500. Method 500 may be performed at a network device such as BS 140, for example.

[0075] Refer to the figure as shown Fig. 9 , the example method 500 may include a step 510 of allocating a UL grant to a UE, a step 520 of sending a paging message to the UE, and a step 530 of receiving a signal sent from the UE using the UL grant. The paging message may include the identity of the UE and the UL grant.

[0076] In some embodiments, BS 140 may allocate an UL grant to UE 120 in response to a conventional paging message including the ID of UE 120 from, for example, an AMF function in the core network.

[0077] In some embodiments, the example method 500 may further include a step 540 of storing the identity and TA of the UE when the UE enters an idle or inactive state. In this case, the paging message sent in step 520 may also include the TA of the UE. In some embodiments, the TA may be stored at the UE 120, and the paging message sent in step 520 may not include the TA for the UE.

[0078] In some embodiments, the paging message may also include downlink data for the UE, and the signal received from the UE on the UL grant may include a response to the downlink data confirmation reception. Thus, downlink small data transmission is completed without the UE 120 needing to transition from an idle or inactive state to a connected state.

[0079] In some embodiments, the signal received from the UE on the UL grant may include uplink data for the network device.Thus, the uplink small data transmission is accomplished without the UE 120 needing to transition from an idle or inactive state to a connected state.

[0080] In some embodiments, the paging message may also include an RRC setup or recovery message, and the signal received from the UE on the UL grant may include an RRC setup or recovery complete message.

[0081] In some embodiments, the paging message may also include a C-RNTI for the UE.

[0082] In some embodiments, the example method 500 may further include checking a mode indicator stored at the network device to determine whether the UE is in a mode that supports paging messages including UL grants at step 550. When it is determined at step 550 that the UE is in a mode that supports such paging messages, a paging message including UL grants is sent at step 520.

[0083] Steps 510-550 of method 500 are performed in coordination with steps 310-350 of method 300 to implement the enhanced paging process described above. Therefore, various features and aspects described above with respect to example method 300 are also applicable to or included in example method 500.

[0084] Fig.10 A block diagram of an example device 600 is shown in accordance with some example embodiments. The device 600 may be implemented, for example, in the BS 140 to perform Fig. 9 The method 500 is shown. Fig.10 , the device 600 may include a first device (or module) 610 for performing step 510, a second device 620 for performing step 520, and a third device 630 for performing step 530. Optionally, the device 600 may also include a fourth device 640 for performing step 540 and a fifth device 650 for performing step 550.

[0085] Fig.11 8 is a block diagram of an example communication system 700 in which embodiments of the present application may be implemented. Fig.11 As shown, the communication system 700 may include a user equipment (UE) 710 which may be implemented as the above-mentioned IIoT UE 120, and a network device 720 which may be implemented as the above-mentioned BS 140. Fig.11 Only one UE 710 is shown, but it should be understood that the communication system 700 may include multiple UEs 710 wirelessly connected to the network device 720.

[0086] refer to Fig.11, UE 710 may include one or more processors 711, one or more memories 712, and one or more transceivers 713 interconnected by one or more buses 714. The one or more buses 714 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber, optical device, or other optical communication device, etc. Each of the one or more transceivers 713 may include a receiver and a transmitter connected to one or more antennas 716. UE 710 may wirelessly communicate with network device 720 via one or more antennas 716. The one or more memories 712 may include computer program code 715. The one or more memories 712 and computer program code 715 may be configured to, when executed by the one or more processors 711, cause the user equipment 710 to perform the processes and steps related to UE 120 as described above.

[0087] The network device 720 may include one or more processors 721, one or more memories 722, one or more transceivers 723, and one or more network interfaces 727 interconnected by one or more buses 724. The one or more buses 724 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber, optical device, or other optical communication device, etc. Each of the one or more transceivers 723 may include a receiver and a transmitter connected to one or more antennas 726. The network device 720 may be used as a base station for the UE 710 and communicate wirelessly with the UE 710 through one or more antennas 726. The one or more network interfaces 727 may provide a wired or wireless communication link, and the network device 720 may communicate with other network devices, entities, or functions through a wired or wireless communication link. The one or more memories 722 may include a computer program code 725. The one or more memories 722 and the computer program code 725 may be configured to cause the network device 720 to perform the processes and steps related to the BS 140 as described above when executed by the one or more processors 721.

[0088] The one or more processors 711, 721 discussed above may be any suitable type for a local technology network, and may include a general purpose processor, a dedicated processor, a microprocessor, a digital signal processor (DSP), one or more processors in a processor-based multi-core processor architecture, and one or more of dedicated processors such as those developed based on a field programmable gate array (FPGA) and an application specific integrated circuit (ASIC). The one or more processors 711, 721 may be configured to control other elements of the UE / network device and operate in cooperation with them to implement the above process.

[0089] The one or more memories 712, 722 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM) or cache. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, the one or more memories 712, 722 may include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment or any combination thereof.

[0090] The network device 170 may be implemented as a single network node, or broken down / distributed across two or more network nodes, such as a central unit (CU), a distributed unit (DU), a remote radio head (RRH), using different functional split architectures and different interfaces.

[0091] It should be understood that the blocks in the drawings can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more blocks can be implemented using software and / or firmware (e.g., machine executable instructions stored in a storage medium). Additionally or alternatively, machine executable instructions, some or all of the blocks in the drawings can be implemented at least in part by one or more hardware logic components. For example, but not limited to, illustrative types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), etc.

[0092] Some exemplary embodiments further provide computer program codes or instructions, which, when executed by one or more processors, can enable a device or apparatus to perform the above-mentioned process. Computer program codes for performing the processes of exemplary embodiments can be written in any combination of one or more programming languages. Computer program codes can be provided to one or more processors or controllers of general-purpose computers, special-purpose computers, or other programmable data processing devices, so that the program code causes the functions / operations specified in the flow chart and / or block diagram to be implemented when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0093] Some exemplary embodiments further provide a computer program product or computer readable medium having a computer program code or instruction stored therein. A computer readable medium may be any tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. A machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine readable storage medium will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0094] In addition, although the operations are described in a specific order, this should not be understood as requiring the specific order shown or performing these operations in order, or requiring the execution of all illustrated operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be understood as limitations on the scope of the present application, but should be understood as descriptions of features that may be specific embodiments. Certain features described in the case of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the case of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0095] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims.

Claims

1. A user equipment (UE), comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the UE to: sending a mode indicator to a network device, the mode indicator indicating that the UE is in a factory working mode and that the UE is in a mode supporting paging messages including an uplink (UL) grant, the UE setting an information element of the factory working mode to on, and the UE sending the mode indicator to the network device before entering an idle or inactive state, the mode indicator being carried in a radio resource control (RRC) setup complete message sent to the network device; receiving a paging message from a network device, the paging message including an identity of the UE, the UL grant, and an RRC establishment or recovery message; adjusting transmission timing based on a timing advance (TA) stored at the UE, wherein the TA is stored when the UE enters an idle or inactive state and the TA is not included in the paging message; sending an RRC response to the network device using the UL grant; as well as Entering a connected state from an idle or inactive state in response to the RRC setup or resume message, wherein the RRC response sent to the network device using the UL grant comprises an RRC setup or resume complete message sent when the UE enters the connected state.

2. The UE according to claim 1, wherein: The paging message further includes downlink (DL) data for the UE.

3. The UE according to claim 2, wherein: The signal sent to the network device using the UL grant includes a response to the DL data confirmation receipt.

4. The UE according to claim 1, wherein: The paging message further includes a Cell Specific Network Radio Temporary Identifier (C-RNTI) for the UE.

5. A network device, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the network device to: receiving a mode indicator sent by a user equipment (UE), the mode indicator indicating that the UE is in a factory working mode and that the UE is in a mode supporting paging messages including uplink (UL) grants, wherein the UE sets an information element of the factory working mode to on, and before the UE enters an idle or inactive state, the network device receives the mode indicator from the UE, the mode indicator being carried in a radio resource control (RRC) setup complete message received by the network device; storing the mode indicator received from the UE; Receive traditional paging messages sent from the Access and Mobility Management Function (AMF); checking a mode indicator stored at the network device to determine whether the UE is in a mode that supports paging messages including the UL grant, When it is determined that the UE is in a mode supporting the paging message including the UL grant, allocating the UL grant to the UE; sending a paging message to the UE, the paging message including the identity of the UE, the UL grant, and an RRC establishment or recovery message; and receiving an RRC response sent from the UE using the UL grant, the RRC response comprising an RRC setup or recovery complete message; When the UE enters an idle or inactive state, the identity of the UE and the TA of the UE are stored, wherein the TA of the UE is stored at the UE when the UE enters an idle or inactive state, and the TA of the UE is not included in the paging message.

6. The network device according to claim 5, wherein: The paging message further includes downlink (DL) data for the UE.

7. The network device according to claim 6, wherein: The signal received from the UE on the UL grant includes a response to the DL data confirmation receipt.

8. The network device according to claim 5, wherein: The paging message further includes a Cell Specific Network Radio Temporary Identifier (C-RNTI) for the UE.

9. A method implemented at a user equipment (UE), comprising: sending a mode indicator to a network device, the mode indicator indicating that the UE is in a factory working mode and that the UE is in a mode supporting paging messages including an uplink (UL) grant, the UE setting an information element of the factory working mode to on, and the UE sending the mode indicator to the network device before entering an idle or inactive state, the mode indicator being carried in a radio resource control (RRC) setup complete message sent to the network device; receiving a paging message from a network device, the paging message including the identity of the UE, the UL grant and an RRC establishment or recovery message; adjusting transmission timing based on a time advance (TA) stored in the UE, wherein the TA is stored when the UE enters an idle or inactive state and the TA is not included in the paging message; sending an RRC response to the network device using a UL grant; as well as Entering a connected state from an idle or inactive state in response to the RRC setup or resume message, wherein the RRC response sent to the network device using the UL grant comprises an RRC setup or resume complete message sent when the UE enters the connected state.

10. The method of claim 9, wherein: The paging message further includes downlink (DL) data for the UE.

11. The method of claim 10, wherein: The signal sent to the network device using the UL grant includes a response to the DL data confirmation receipt.

12. The method of claim 9, wherein: The paging message further includes a cell-specific network radio temporary identifier (C-RNTI) for the UE.

13. A method implemented at a network device, comprising: receiving a mode indicator sent by a user equipment (UE), the mode indicator indicating that the UE is in a factory working mode and that the UE is in a mode supporting paging messages including uplink (UL) grants, wherein the UE sets an information element of the factory working mode to on, and before the UE enters an idle or inactive state, the network device receives the mode indicator from the UE, the mode indicator being carried in a radio resource control (RRC) setup complete message received by the network device; storing the mode indicator received from the UE; Receive traditional paging messages sent from the Access and Mobility Management Function (AMF); checking a mode indicator stored at the network device to determine whether the UE is in a mode that supports paging messages including the UL grant, When it is determined that the UE is in a mode supporting the paging message including the UL grant, Allocating an uplink (UL) grant to the UE; sending a paging message to the UE, the paging message including the identity of the UE, the UL grant, and an RRC establishment or recovery message; and receiving an RRC response sent from the UE using the UL grant, the RRC response comprising an RRC setup or recovery complete message; When the UE enters an idle or inactive state, the identity of the UE and the TA of the UE are stored, wherein the TA of the UE is stored at the UE when the UE enters an idle or inactive state, and the TA of the UE is not included in the paging message.

14. The method of claim 13, wherein: The paging message further includes downlink (DL) data for the UE.

15. The method of claim 14, wherein: The signal received from the UE on the UL grant includes a response to the DL data confirmation receipt.

16. The method of claim 14, wherein: The paging message further includes a cell-specific network radio temporary identifier (C-RNTI) for the UE.

17. A device implemented at a user equipment (UE), comprising: means for sending a mode indicator to a network device, the mode indicator indicating that the UE is in a factory working mode and that the UE is in a mode to support paging messages including uplink (UL) grants, the UE setting an information element of the factory working mode to on, and the UE sending the mode indicator to the network device before entering an idle or inactive state, the mode indicator being carried in a radio resource control (RRC) setup complete message sent to the network device; means for receiving a paging message from a network device, the paging message including the identity of the UE, the UL grant and an RRC setup or recovery message; means for adjusting transmission timing based on a timing advance (TA) stored at the UE, wherein the TA is stored when the UE enters an idle or inactive state, the TA not included in the paging message; means for sending an RRC response to the network device using the UL grant; as well as Means for entering a connected state from an idle or inactive state in response to the RRC setup or resume message, wherein the RRC response sent to the network device using the UL grant comprises an RRC setup or resume complete message sent when the UE enters the connected state.

18. A computer program product embodied in at least one computer readable medium and comprising instructions which, when executed by at least one processor of a user equipment (UE), cause the UE to: sending a mode indicator to a network device, the mode indicator indicating that the UE is in a factory working mode and that the UE is in a mode supporting paging messages including an uplink (UL) grant, the UE setting an information element of the factory working mode to on, and the UE sending the mode indicator to the network device before entering an idle or inactive state, the mode indicator being carried in a radio resource control (RRC) setup complete message sent to the network device; receiving a paging message from a network device, the paging message including the identity of the UE, the UL grant and an RRC establishment or recovery message; adjusting transmission timing based on a timing advance (TA) stored at the UE, wherein the TA is stored when the UE enters an idle or inactive state and the TA is not included in the paging message; sending an RRC response to the network device using the UL grant; as well as Entering a connected state from an idle or inactive state in response to the RRC setup or resume message, wherein the RRC response sent to the network device using the UL grant comprises an RRC setup or resume complete message sent when the UE enters the connected state.

19. A computer program product embodied in at least one computer readable medium and comprising instructions which, when executed by at least one processor of a network device, cause the network device to: receiving a mode indicator sent by a user equipment (UE), the mode indicator indicating that the UE is in a factory working mode and whether the UE supports a mode of a paging message including an uplink (UL) grant, wherein the UE sets an information element of the factory working mode to on, and before the UE enters an idle or inactive state, the network device receives the mode indicator from the UE, the mode indicator being carried in a radio resource control (RRC) setup complete message received by the network device; storing the mode indicator received from the UE; Receive traditional paging messages sent from the Access and Mobility Management Function (AMF); checking a mode indicator stored at the network device to determine whether the UE is in a mode that supports paging messages including the UL grant, When it is determined that the UE is in a mode supporting the paging message including the UL grant, allocating the UL grant to the UE; sending a paging message to the UE, the paging message including the identity of the UE, the UL grant, and an RRC establishment or recovery message; and receiving an RRC response sent from the UE using the UL grant, the RRC response comprising an RRC setup or recovery complete message; When the UE enters an idle or inactive state, the identity of the UE and the TA of the UE are stored, wherein the TA of the UE is stored at the UE when the UE enters an idle or inactive state, and the TA of the UE is not included in the paging message.

Images