Preconfigured dual-purpose random access procedure

Abstract

Methods, apparatuses, and systems are provided for a user equipment (UE). The UE is in a radio resource control (RRC) idle or inactive mode during a random access procedure with a cell operating in an on-demand system information block 1 (SIB1) mode. The UE transmits a random access message to the cell. The random access message indicates dual usage purposes, including a request for an on-demand SIB1 and a request for data communication with the cell. In response to transmitting the random access message, the UE receives a response message from the cell, the response message including a scheduling indication of the requested on-demand SIB1 information. The UE also receives the SIB1 information according to the scheduling indication and performs data communication with the cell according to a pre-configuration, which can be related to a pre-configured PUSCH resource, indicated in the on-demand SIB1 configuration, or together with the SIB1 transmission, etc. Similar methods, apparatuses, and systems are also provided for a network entity.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more particularly to the System Information Block 1 (SIB1) procedure or its enabling means. More specifically, this disclosure provides methods and apparatus for requesting SIB1 information via a dual-purpose random access procedure. Background Technology

[0002] Wireless telecommunications systems (also known as mobile communication systems) are constantly evolving. A key aspect of these mobile communication systems is energy efficiency. For user equipment (UE), several technologies have been developed, such as discontinuous transmission and reception (DRT, DRX) and energy efficiency in inactive and idle modes, but many technologies for network energy efficiency (NES) are still in the early stages of development.

[0003] Typically, for example in 3GPP Long Term Evolution (LTE) mobile communication systems, System Information (SI) is broadcast periodically over the entire cell area to continuously inform the UE of network parameters. The main drawback of this continuous broadcasting is low energy efficiency, especially if the cell is under low load or there is no load in the cell (i.e., few or no UEs benefit from the transmitted SI).

[0004] In 3GPP 5G / NR mobile communication systems, system information transmission for SIs other than the minimum SI can be omitted. The minimum SI involves information related to the Master Information Block (MIB) and System Information Block 1 (SIB1). Information from SIB2 to SIB19 can be provided as needed, supplementing or replacing broadcasts. Currently, MIBs and SIB1 are still periodically broadcast in NR to carry basic information required for initial UE access.

[0005] A further enhancement to NES could be providing SIB1 information only on demand. Since SIB1 includes the necessary system information for cell communication, procedures for on-demand SIB2 through SIB19 may not be applicable. One option discussed in the development of the NR specification is to use a random access message during the random access procedure to transmit an on-demand SIB1 request to the network, which interprets this random access message as an SIB1 request only, not a data connection request. This means that a UE requiring on-demand SIB1 information and subsequent data connection to the cell would need to initiate two random access procedures and send two different preambles to the network. This would also be time-consuming and resource-intensive.

[0006] Therefore, there is a need for methods and apparatus that support efficient acquisition of on-demand SIB1 information and initiation of data connections with cells. Summary of the Invention

[0007] According to a first aspect disclosed in this subject matter, a method is provided for a user equipment (UE) to perform in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell, wherein the cell operates in On-Demand System Information Block 1 (SIB1) mode. The method includes: transmitting a random access message to the cell, wherein the random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell; and, in response to transmitting the random access message, receiving from the cell the response message including a scheduling indication of the requested on-demand SIB1 information, and receiving data communication configuration information for implementing data communication with the cell. The method further includes receiving SIB1 information according to the scheduling indication of the SIB1 information, and performing data communication with the cell according to the data communication configuration information.

[0008] According to a second aspect, a method is provided, executed by a network entity, for supporting a random access procedure between a cell and a user equipment (UE) operating in Radio Resource Control (RRC) idle or inactive mode, wherein the cell operates in on-demand SIB1 mode. The method includes: receiving a random access message from the UE, wherein the random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell; and, in response to receiving the random access message, transmitting to the UE the response message including a scheduling indication of the requested on-demand SIB1 information, and transmitting data communication configuration information for implementing data communication with the UE. The method further includes transmitting SIB1 information according to the scheduling indication of the SIB1 information, and performing data communication with the UE according to the data communication configuration information.

[0009] According to a third aspect, an apparatus is provided for a user equipment (UE) in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode. The apparatus is configured to: transmit a random access message to the cell, wherein the random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell; and, in response to transmitting the random access message, receive from the cell a response message including a scheduling indication of the requested on-demand SIB1 information, and receive data communication configuration information for implementing data communication with the cell. The apparatus is further configured to receive SIB1 information according to the scheduling indication of the SIB1 information and to perform data communication with the cell according to the data communication configuration information.

[0010] According to a fourth aspect, an apparatus is provided for supporting a random access procedure between a cell and a user equipment (UE) operating in a Radio Resource Control (RRC) idle or inactive mode, wherein the cell operates in on-demand SIB1 mode. The apparatus is configured to: receive a random access message from the UE, wherein the random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell; and, in response to receiving the random access message, transmit to the UE a response message including a scheduling indication of the requested on-demand SIB1 information, and transmit data communication configuration information for implementing data communication with the UE. The apparatus is further configured to transmit SIB1 information according to the scheduling indication of the SIB1 information and to perform data communication with the UE according to the data communication configuration information.

[0011] According to all the embodiments described above, the random access message is, for example, the first message MSG1 or MSGA or the third message MSG3 in the random access process.

[0012] According to embodiments of the first and second aspects, the method further includes: receiving / transmitting another response message in response to transmitting / receiving a random access message, wherein data communication configuration information is included in the other response message. According to embodiments of the third and fourth aspects, the apparatus is further configured to receive / transmit another response message in response to transmitting / receiving a random access message, wherein data communication configuration information is included in the other response message. According to further embodiments of all aspects, an indication of a time window for transmitting / receiving the other response message is received / transmitted together with the response message, together with on-demand SIB1 configuration information, and / or predefined.

[0013] According to embodiments of all the above aspects, data communication configuration information is included, for example, by a response message.

[0014] According to embodiments of the first and third aspects, the method further includes / the apparatus is further configured to receive / receive preamble configuration information from the cell, wherein the preamble configuration information indicates one or more preamble indices, one or more transmission resources, or a combination thereof, for indicating a dual-use purpose. According to embodiments of the second and fourth aspects, the method further includes / the apparatus is further configured to transmit / transmit preamble configuration information from the cell, wherein the preamble configuration information indicates one or more preamble indices, one or more transmission resources, or a combination thereof, for indicating a dual-use purpose.

[0015] According to embodiments of the first and third aspects, the method further includes / the apparatus is further configured to select / select a random access preamble for transmission with the random access message and / or transmission resources for transmission of the random access message, so as to indicate a dual-use purpose using the random access message. According to embodiments of the second and fourth aspects, the method further includes / the apparatus is further configured to determine / determine an indication of a dual-use purpose based on the selected random access preamble for transmission with the random access message and / or transmission resources for transmission of the random access message.

[0016] In embodiments of all the above aspects, the random access procedure is, for example, a four-message random access procedure, wherein the data communication configuration information includes uplink scheduling information for the uplink random access message. In embodiments of all the above aspects, the random access procedure is a two-message random access procedure, wherein the random access message indicates a dual-use purpose by adding an SIB1 request to the data portion of the random access message.

[0017] According to the fifth aspect, a method performed by a user equipment (UE) is provided. The UE is in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell, wherein the cell operates in On-Demand System Information Block 1 (SIB1) mode.

[0018] The UE is receiving configuration for the on-demand SIB1 request, which includes information related to at least one pre-configured physical random access channel (PRACH) timing and at least one pre-configured physical uplink shared channel (PUSCH) resource for transmitting RRC messages.

[0019] The UE also transmits a random access message to the cell using at least one of the pre-configured PRACH timings, wherein the random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell.

[0020] In response to transmitting random access messages: The UE receives a response message from the cell including a scheduling instruction for the requested on-demand SIB1 information; and receives SIB1 information according to the scheduling instruction for the SIB1 information; and It also uses at least one of the pre-configured PUSCH resources to transmit RRC messages.

[0021] According to a sixth aspect, a method performed by a user equipment (UE) is provided. The UE is in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell, wherein the cell operates in On-Demand System Information Block 1 (SIB1) mode.

[0022] The UE is transmitting a random access message to the cell, which indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell.

[0023] In response to transmitting random access messages: The UE receives a response message from the cell, including a scheduling indication of the requested on-demand SIB1 information; and SIB1 information is received according to the scheduling instructions of the SIB1 information, wherein the SIB1 information includes at least one pre-configured Physical Uplink Shared Channel (PUSCH) resource for transmitting RRC messages; and It also uses at least one of the pre-configured PUSCH resources to transmit RRC messages.

[0024] In other embodiments of all the above aspects, portions of an aspect may be combined with portions of other aspects to form new combinations.

[0025] Depending on the desired configuration, the above aspects and features can be implemented in systems, apparatuses, methods, articles, and non-transitory computer-readable media. This subject matter can be implemented in and used with a wide variety of different types of devices, including, but not limited to, any of cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0026] The present invention is intended to provide a brief overview of some aspects and features disclosed under this subject matter. Therefore, it should be understood that the above features are merely examples and should not be construed as limiting the scope of the subject matter disclosure in any way. Other features, aspects, and advantages disclosed under this subject matter will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0027] A better understanding of the subject matter disclosure can be obtained by considering the following detailed description of various embodiments in conjunction with the accompanying drawings, in which: Figure 1 A schematic diagram of an example wireless network is shown.

[0028] Figure 2A A schematic diagram of an example wireless device is shown.

[0029] Figure 2B A schematic diagram of an example network node is shown.

[0030] Figure 3 This is an overview of two possible scenarios for applying the methods described in this disclosure.

[0031] Figure 4A flowchart of a method performed by a user equipment according to this disclosure is presented.

[0032] Figure 5 A flowchart of a method performed by a network entity according to this disclosure is presented.

[0033] Figure 6 A message flow diagram for efficient SIB1 request and data connection establishment according to an embodiment is shown.

[0034] Figure 7 A message flow diagram for efficient SIB1 request and data connection establishment according to another embodiment is shown.

[0035] Figure 8 This is a detailed overview of the possible procedures to be performed in accordance with this disclosure. Detailed Implementation

[0036] The examples and embodiments described below illustrate how those skilled in the art can practice the information disclosed herein. When reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the described concepts and recognize the application of these concepts not specifically set forth herein. It should be understood that these concepts and applications fall within the scope of this description.

[0037] Numerous specific details are set forth in the following description. However, it should be understood that embodiments can be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail so as not to obscure the understanding of the description. With the inclusion of the description, those skilled in the art will be able to implement appropriate functionality without excessive experimentation.

[0038] References to "an embodiment," "an embodiment," "an example embodiment," etc., in the specification indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that implementing such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art, whether explicitly described or not.

[0039] As used herein, “multiple” means two or more. As used herein, a “group” of items may include one or more such items. As used herein, whether in this disclosure or in the claims, the terms “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” etc., shall be understood as open-ended, meaning including but not limited to. Only the transitional phrases “consisting of…” and “consisting substantially of…” are closed or semi-closed transitional phrases with respect to the claims, respectively. The use of ordinal terms such as “first,” “second,” “third,” etc., in the claims or this subject matter disclosure to modify an element itself does not imply any priority, precedence, or order of one element relative to another, or the chronological order of actions of the method, but is merely used as a label to distinguish one element having a particular name from another element having the same name (but using ordinal terms), to differentiate the elements. As used herein, “and / or” and “at least one of” mean that the listed items are alternatives, but alternatives also include any combination of the listed items.

[0040] Before explaining in detail the examples according to this disclosure, refer to Figures 1 to 3 A brief explanation of some general principles of wireless communication systems is provided to help understand the underlying technology of the described example.

[0041] Figure 1 An example of a wireless network 100 that can be used for wireless communication is shown. The wireless network 100 includes wireless devices (such as UEs 110 (e.g., 110A-110B)) and network nodes (such as radio access nodes 120 (e.g., 120A-120B) (e.g., eNB, gNB, etc.)) connected to one or more network nodes 130 via an interconnection network 125. The network 100 can be used in any suitable deployment scenario. UEs 110 within the coverage area 115 can each be able to communicate directly with radio access nodes 120 via a wireless or air interface. In some embodiments, UEs 110 can also communicate with each other via D2D communication.

[0042] As an example, UE 110A can communicate with radio access node 120A via a wireless or air interface. That is, UE 110A can transmit and / or receive wireless signals from radio access node 120A. The wireless signals may contain voice services, data services, control signals, and / or any other suitable information.

[0043] As used herein, the term "User Equipment" (UE) has the full range of its common meaning and can refer to any type of wireless device capable of communicating with network nodes and / or with another UE in a cellular or mobile or wireless communication system. Examples of UEs are target devices, D2D UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, personal digital assistants, tablets, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, ProSe UEs, vehicle-to-vehicle (V2V) UEs, V2X UEs, MTC UEs, eMTC UEs, FeMTC UEs, UECat 0, UE Cat M1, narrowband IoT (NB-IoT) UEs, UE Cat NB1, etc. References below. Figure 2A A sample implementation of the UE is described in more detail.

[0044] In some embodiments, the radio signal coverage area 115 associated with radio access node 120 may be referred to as a cell. However, particularly regarding fifth-generation (5G) / New Radio (NR) mobile communication concepts, beams such as the Multicast Radio Beam (MRB) described herein may be used for communication within a cell. In some embodiments described herein, UE 110 may be in RRC inactive or idle mode and camped on the cell of radio access node 120A, which may be represented as an anchor cell or a coverage cell, and UE 110 may be located within the coverage area 115 of radio access nodes 120A and 120B. The cell of radio access node 120B may be represented as a non-anchor cell or a capacity cell. Although Figure 1 Not shown, but there may be more than one non-anchor cell provided by more than one other radio access node 120. In some embodiments, the UE 100 may wish to switch cells, i.e., switch to camping on a non-anchor cell.

[0045] Regarding a beam-based mobile communication system, a radio access node 120 (base station) can transmit beamforming signals to a UE 110 in one or more transmission directions (transmit beam, Tx beam). The UE 110 can receive beamforming signals from the base station 120 in one or more reception directions (receive beam, Rx beam). The UE 110 can also transmit beamforming signals to the base station 120 in one or more directions, and the base station 120 can receive beamforming signals from the UE 110 in one or more directions. For each base station / UE pair, the base station 120 and the UE 110 can determine the optimal reception and transmission directions, for example, the optimal directions in terms of providing the highest link quality or satisfying other quality conditions in the most suitable manner.

[0046] Interconnection network 125 can refer to any interconnection system capable of transmitting audio, video, signals, data, messages, or any combination thereof. Interconnection network 125 may include all or part of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communications or computer network (such as the Internet), a wired or wireless network, a corporate intranet, or any other suitable communications link (including combinations thereof).

[0047] In some embodiments, network node 130 may be a core network node that manages the establishment of communication sessions and various other functions of UE 110. Examples of network node 130 may include a Mobile Switching Center (MSC), MME, Serving Gateway (SGW), Packet Data Network Gateway (PGW), Operation and Maintenance (O&M), Operation Support System (OSS), SON, location node (e.g., Enhanced Serving Mobile Location Center E-SMLC), location server node, MDT node, etc. UE 110 may exchange certain signals with network node 130 using Non-Access Stratum (NAS). In NAS signaling, signals between UE 110 and network node 130 can be transparently transmitted through the radio access network. In some embodiments, radio access node 120 may interface with one or more network nodes 130 via an inter-node interface.

[0048] As used herein, the term "network node" has the full range of its general meaning and can correspond to any type of radio access node (or radio network node) or any network node that can communicate with a UE and / or with another network node in a cellular or mobile or wireless communication system. Examples of network nodes are NodeB, MeNB, SeNB, and network nodes can belong to MCG or SCG, base station (BS), multi-standard radio (MSR) radio access node (such as MSR BS), eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node of control relay, base transceiver station (BTS), access point (AP), transmission point, transmission node, RRU, RRH, node in distributed antenna system (DAS), core network node (e.g., MSC, MME, etc.), O&M, OSS, ad hoc network (SON), location node (e.g., E-SMLC), MDT, test equipment, etc. References are provided below. Figure 5 , 6 Examples of network node implementations are described in more detail in sections 7 and 8.

[0049] In some embodiments, radio access node 120 may be a distributed radio access node. The components of radio access node 120 and their associated functions may be divided into two main units (or sub-radio network nodes), which may be referred to as a centralized unit (CU) and a distributed unit (DU). Different distributed radio network node architectures may be employed. For example, in some architectures, the DU may be connected to the CU via a dedicated wired or wireless link (e.g., fiber optic cable), while in other architectures, the DU may be connected to the CU via a transport network. Furthermore, how the various functions of radio access node 120 are divided among the CU(multiple) and DU(multiple) may vary depending on the chosen architecture.

[0050] In some embodiments, the radio access nodes 120 can communicate with each other via terrestrial or other connections. Communication between the radio access nodes 120 can be achieved, for example, in a 5G / NR communication system by using the Xn interface connecting the radio access nodes 120.

[0051] Exemplary wireless communication systems are based on architectures standardized by the 3rd Generation Partnership Project (3GPP). The latest 3GPP-based developments are often referred to as Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) Radio Access Technology (RAT). The various development phases of the 3GPP specifications are referred to as releases. Newer developments in LTE are often referred to as Advanced Long Term Evolution (LTE-A). LTE (LTE-A) employs a radio mobility architecture called Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network called Evolved Packet Core Network (EPC). Base stations in such systems are called evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features to communication devices, such as user plane packet data aggregation / radio link control / media access control / physical layer protocols (PDCP / RLC / MAC / PHY) and control plane radio resource control (RRC) protocol termination for communication devices. Other examples of RATs include those provided by base stations in systems based on technologies such as WLAN and / or Global Microwave Access Interoperability (WiMax). Base stations can provide coverage for an entire cell or similar radio service area. The core network components include the Mobility Management Entity (MME), the Serving Gateway (S-GW), and the Packet Gateway (P-GW).

[0052] An example of a suitable communication system is the 5G or NR concept. The network architecture in NR can be similar to that of LTE-A. Base stations in an NR system can be referred to as next-generation Node Bs (gNBs). Changes in network architecture may depend on the need to support various radio technologies and more granular Quality of Service (QoS) support, as well as certain on-demand QoS level requirements to support Quality of Experience (QoE) from the user's perspective. Furthermore, network-aware services and applications, and service- and application-aware networks, may also cause architectural changes. These relate to Information Center Network (ICN) and User Center Content Delivery Network (UC-CDN) approaches. NR can use multiple-input multiple-output (MIMO) antennas, significantly more base stations or nodes than LTE (the so-called small cell concept), including macro sites cooperating with smaller sites, and may also employ a variety of radio technologies to achieve better coverage and enhanced data rates.

[0053] Future networks can leverage Network Functions Virtualization (NFV), a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that are operatively connected or linked together to provide services. Virtualized network functions (VNFs) can include one or more virtual machines running computer program code using standard or general-purpose type servers instead of custom hardware. Cloud computing or data storage can also be utilized. In radio communications, this might mean performing node operations, at least partially, within servers, hosts, or nodes operatively coupled to a remote radio head. Node operations may also be distributed across multiple servers, nodes, or hosts. It should also be understood that the division of labor between core network operations and base station operations may differ from, or even not exist at all, in LTE.

[0054] An example 5G core network (CN) includes functional entities. The CN connects to the UE via the radio access network (RAN). The UPF (User Plane Function), whose role is called PSA (PDU Session Anchor), is responsible for forwarding frames back and forth between the DN (Data Network) and the tunnel established via 5G to the UE that exchanges services with the data network (DN). The UPF is controlled by the SMF (Session Management Function), which receives policies from the PCF (Policy Control Function). The CN may also include AMF (Access and Mobility Function).

[0055] Generally, all concepts disclosed herein can be applied to different communication networks, including but not limited to LTE, LTE-A, 5G, 5G Advanced, 6G and other future or already implemented networks.

[0056] Figure 2AThis is a schematic diagram of an apparatus for a UE. In one embodiment, the apparatus may include a UE; in another embodiment, the apparatus is included within a UE; and in yet another embodiment, the apparatus is a UE. The apparatus may include a wireless device. The apparatus may include at least one processor 220 and at least one memory 230 storing computer program instructions that, when executed by at least one processor 220, cause the apparatus to perform an embodiment of the UE 110 described herein. The UE 110 includes a transceiver 210, a processor 220, a memory 230, and a network interface 240. In some embodiments, the transceiver 210 facilitates the transmission of wireless signals to and from a radio access node 120 (e.g., via a plurality of transmitters (Tx), a plurality of receivers (Rx), and a plurality of antennas). The processor 220 executes instructions to provide some or all of the functions provided by the UE 110 described herein, and the memory 230 stores instructions executed by the processor 220. In some embodiments, the processor 220 and the memory 230 form a processing circuit.

[0057] Processor 220 may include any suitable combination of hardware for executing instructions and manipulating data to perform some or all of the functions of UE 110 described herein. In some embodiments, processor 220 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application-specific integrated circuits (ASICs), one or more field-programmable gate arrays (FPGAs), and / or other logic.

[0058] Memory 230 is generally operable to store instructions, such as computer programs, software, applications including logic, rules, algorithms, code, tables, etc., and / or other instructions executable by processor 220. Examples of memory 230 include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processor 220 of UE 110. For example, memory 230 includes methods that enable processor 220 to perform operations according to the methods described herein (e.g., Figure 4 , Figure 6 , Figure 7 and Figure 8 The method is to execute the computer program code that processes the data.

[0059] Network interface 240 is communicatively coupled to processor 220 and can refer to any suitable device operable to receive input from UE 110, send output from UE 110, perform appropriate processing of input or output or both, communicate with other devices or any combination thereof. Network interface 240 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, for communication over a network.

[0060] Other embodiments of UE 110 may include, in addition to Figure 2A Additional components, other than those shown, may be responsible for providing certain aspects of the functionality of the wireless device, including any functions described herein and / or any additional functions (including any functions required to support the mechanisms disclosed under this subject matter). As an example, UE 110 may include input devices and circuitry, output devices, and one or more synchronization units or circuits, which may be part of processor 220. Input devices include mechanisms for inputting data into UE 110. For example, input devices may include input mechanisms such as microphones, input elements, displays, etc. Output devices may include mechanisms for outputting data in audio, video, and / or hardcopy formats. For example, output devices may include speakers, displays, etc.

[0061] In some embodiments, the wireless device UE 110 may include a series of modules configured to implement the functions of the wireless device described herein. Furthermore, in some embodiments, the UE 110 may also include components for the functions described herein.

[0062] It should be understood that various modules can be implemented as a combination of hardware and software, for example, Figure 2A The UE 110 shown includes a processor, memory, and (multiple) transceivers. Some embodiments may also include additional modules to support additional and / or optional functions.

[0063] Figure 2BThis is an example schematic diagram of an apparatus for a radio access node 120 or a network node 130. The apparatus may include at least one processor 220 and at least one memory 230 storing computer program instructions that, when executed by at least one processor 220, cause the apparatus to perform the embodiments of the network node 130 or radio access node 120 described herein. The example radio access node 120 or network node 130 may include one or more of a transceiver 310, a processor 320, a memory 330, and a network interface 340. In some embodiments, the transceiver 310 facilitates the transmission of wireless signals to and from a wireless device, such as a UE 110, and the reception of wireless signals from the wireless device (e.g., via multiple transmitters (Tx), multiple receivers (Rx), and multiple antennas). The processor 320 executes instructions to provide some or all of the functions described herein as provided by the radio access node 120 or network node 130, and the memory 330 stores the instructions executed by the processor 320. In some embodiments, the processor 320 and the memory 330 form a processing circuit. Network interface 340 can transmit signals to backend network components such as gateways, switches, routers, the Internet, the Public Switched Telephone Network (PSTN), core network nodes, or radio network controllers.

[0064] Processor 320 may include any suitable combination of hardware for executing instructions and manipulating data to perform some or all of the functions described in the radio access node 120 or network node 130 (such as those described herein). In some embodiments, processor 320 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application-specific integrated circuits (ASICs), one or more field-programmable gate arrays (FPGAs), and / or other logic.

[0065] Memory 330 is generally operable to store instructions, such as computer programs, software, applications including logic, rules, algorithms, code, tables, etc., and / or other instructions executable by processor 320. Examples of memory 330 include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)) and / or any other volatile or non-volatile, non-transitory computer-readable and / or computer-executable memory device for storing information. For example, memory 330 includes methods that enable processor 320 to perform operations according to the methods described herein (e.g., Figure 5 , Figure 6 , Figure 7 and Figure 8 The method is to execute the computer program code that processes the data.

[0066] In some embodiments, network interface 340 is communicatively coupled to processor 320 and may refer to any suitable device operable to receive input for radio access node 120 or network node 130, send output from radio access node 120 or network node 130, perform appropriate processing of input or output or both, communicate with other devices, or any combination thereof. Network interface 340 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, for communication over a network.

[0067] Other embodiments of radio access node 120 or network node 130 may include, in addition to Figure 2B Additional components beyond those shown may be responsible for providing certain aspects of node functionality, including any of the functions described herein and / or any additional functions (including any functions required to support the solutions described herein). Various different types of radio access nodes or network nodes may include components having the same physical hardware but configured (e.g., via programming) to support different radio access technologies, or may represent partially or completely different physical components.

[0068] Similar to about Figure 2B The processors, interfaces, and memory described may be included in other nodes (such as UE 110, radio access node 120, etc.). Other nodes may optionally include or exclude wireless interfaces (such as...). Figure 2B (The transceiver described in the text).

[0069] In some embodiments, radio access node 120 or network node 130 may include a series of modules configured to implement the functions of radio access node 120 or network node 130 described herein. Furthermore, in some embodiments, radio access node 120 or network node 130 may also include components for the functions described herein.

[0070] It should be understood that various modules can be implemented as a combination of hardware and software, for example, Figure 2B The radio access node 120 or network node 130 shown includes a processor, memory, and transceiver(s). Some embodiments may also include additional modules to support additional and / or optional functions.

[0071] Reference Figures 4 to 1Before describing the method of processing in the dynamic on-demand SIB1 transmission mode according to this disclosure, some background information and aspects related to this subject matter disclosure will be provided. It should be noted that although a description is given for example, for one communication direction (e.g., for downlink communication), all concepts described herein also apply to another direction, such as uplink (UL) communication. Furthermore, it will be apparent to those skilled in the art that concepts described for one entity (e.g., UE 110) apply to another entity (e.g., base station or network node 120) when considering, for example, another communication direction or another network setup.

[0072] Network energy conservation plays a crucial role in modern communication networks. One energy-saving method involves the transmission or omission of System Information (SI), which is typically broadcast periodically across the entire cell area to continuously inform the UE of network parameters. A major drawback of this periodic broadcasting is low energy efficiency, especially if the cell faces low load or no load (i.e., few or no UEs benefit from the transmitted SI). In 3GPP 5G / NR mobile communication systems, the transmission of system information for SIs other than the minimum SI can be omitted. The minimum SI involves information from the Master Information Block (MIB) and System Information Block 1 (SIB1). As a supplement or replacement to the broadcast, information from SIB2 to SIB19, carrying non-essential SIs, can be provided on demand. Currently, the MIB and SIB1 are still periodically broadcast in NR to carry the basic information required for the UE's initial access.

[0073] Further enhancements to NES could also provide SIB1 on demand only. However, since SIB1 is essential system information for cell communication, the procedures for on-demand SIB2 through SIB19 may not be applied. Further information flows may be required, such as providing the UE with on-demand SIB1 configuration information carrying information needed to receive / request SIB1 information and / or for the interaction of two different cells.

[0074] Therefore, in some embodiments described herein, the on-demand SIB1 cell is a non-anchor cell (also referred to herein as a capacity cell, CapCell, or first cell), where SIB1 is provided only on demand. Another cell, the anchor cell (also referred to herein as a coverage cell, CovCell, or second cell), periodically broadcasts the anchor cell's SIB1 according to conventional operation. Furthermore, the UE can be considered to be in idle or inactive mode (RRC_IDLE, RRC_INACTIVE) and camped on the anchor cell. A non-anchor cell refers to a cell that supports on-demand SIB or is also represented as having SIB1-less functionality (not transmitting SIB1) in addition to conventional SIB1 operation, where, according to the different embodiments described herein, the SIB1 information of the non-anchor cell can be transmitted via either the anchor cell or the non-anchor cell. Note that a scenario can also be considered where the UE is not camped on the anchor cell but is active and now intended to establish a data connection with the capacity cell. Therefore, non-anchor cells or capacity cells are not considered limiting in the following disclosure and can be any cell that provides SIB1 information on demand.

[0075] In embodiments of this disclosure, on-demand SIB1 transmission is triggered by a wake-up signal (WUS) from the UE, or more generally referred to as an on-demand SIB1 request, which may be similar to or different from on-demand SIB requests for other SIBs based on the Physical Random Access Channel (PRACH) in conventional specifications, such as those defined in 3GPP TS 38.331 Release 17 or 18. Configuration information for the WUS / on-demand SIB1 request, configuration information for the WUS / on-demand SIB1 response, and / or configuration information for receiving SIB1 information is provided to the UE by the network (NW).

[0076] Regarding on-demand SIB1 transmission from gNB to RRC_IDLE / INACTIVE UE, two deployment scenarios can generally be considered: Scenario A: Co-located anchor cells and non-anchor cells within the same gNB, where information exchange between the two cells is via an internal interface. The RUs of the anchor cell and non-anchor cells are physically located in the same location.

[0077] Case B: Non-co-located anchor cells and non-anchor cells in different gNBs, for example, as regarding Figure 1 The described gNB120A and gNB 120B involve information exchange between two cells via a backhaul interface, namely the Xn interface. The RUs of the anchor cell and the non-anchor cell are physically not located in the same location.

[0078] In the embodiments described herein, the UL-on-demand SIB1 request (also known as the wake-up signal (WUS)) is assumed to be received by a non-anchor cell. Different scenarios can be conceived for the message flow, such as... Figure 3 As shown.

[0079] Scenario 1: Anchor cell 120-2 only handles on-demand configuration for RRC_IDLE / RRC_INACTIVE UEs. For example, in non-co-located cases, the information for on-demand SIB1 request configuration can be pre-exchanged via backhaul. Non-anchor cell 120-1 can then handle on-demand reception from RRC_IDLE / RRC_INACTIVE UEs and transmit on-demand SIB1 itself. This scenario requires non-anchor cell 120-1 to monitor on-demand SIB1 requests / WUS reception, which increases the energy consumption of non-anchor cell 120-1 compared to scenarios 1 and 2. This scenario requires UE 110 to switch between anchor cell 120-2 and non-anchor cell 120-1 to obtain on-demand SIB1.

[0080] Scenario 2: On-Demand SIB1 operation is independent of anchor cell 120-2. Non-anchor cell 120-1 can handle on-demand SIB1 request configuration for RRC_IDLE / RRC_INACTIVE UEs and the reception of on-demand SIB1 requests from RRC_IDLE / RRC_INACTIVE UEs. Simultaneously, non-anchor cell 120-1 will also handle the delivery of on-demand SIB1 requests to RRC_IDLE / RRC_INACTIVE UEs. This scenario requires a mechanism to indicate the on-demand SIB1 request / WUS to UE 110. This scenario requires UE 110 to handover between anchor cell 120-2 and non-anchor cell 120-1 to obtain on-demand SIB1.

[0081] As mentioned above, there are two options for transmitting WUS configurations.

[0082] Option 1: The anchor cell transmits WUS configuration as in Scenario 1. In practice, it can be assumed that the anchor cell provides IDLE mode functionality for camping and initial access. Common signals / channels, including the Synchronization Signal Block (SSB), SIB, paging, and Random Access Channel (RACH), can be transmitted to or received from RRC_IDLE / RRC_INACTIVE UEs camped on this cell. Therefore, the anchor cell can also be used to transmit on-demand SIB1 WUS configuration to UEs. On-demand SIB1 configuration requests can be added as part of system information to any of the MIBs, SIB1, SIB2 through SIB19, or any other potentially newly defined SIBs in the anchor cell.

[0083] Option 2: Transmitting WUS configuration in a non-anchor cell. As explained for scenario 2, a non-anchor cell can provide SSB transmission and on-demand SIB1 transmission itself. In this case, the on-demand SIB1 WUS configuration must be delivered by the non-anchor cell itself to the RRC_IDLE / RRC_INACTIVE UE.

[0084] Typically, in conventional operation, the first message used for communication between the RRC_IDLE / RRC_INACTIVE UE and the NW is the transmission of the ULPRACH signal. Additionally, in conventional operation where the RRC_IDLE / RRC_INACTIVE UE requests on-demand (multiple) SIBs besides SIB1 information, the RRC_IDLE / RRC_INACTIVE UE is also required to perform a PRACH transmission as an indication of a request to receive multiple on-demand SIBs. To maintain consistency with conventional on-demand SIB operation, PRACH can be used as an on-demand SIB1 request to trigger an on-demand SIB1 transmission for the RRC_IDLE / RRC_INACTIVE UE.

[0085] In the example considered in this paper, the UL on-demand SIB1 request is transmitted to and received by the non-anchor cell. In practice, monitoring the on-demand SIB1 request may result in additional network power consumption due to network reception. However, this allows the non-anchor cell to process the on-demand SIB1 request independently of the anchor cell, i.e., without requiring backhaul signaling. As shown in Scenario 1 / 2 above, the on-demand SIB1 is also delivered to the RRC_IDLE / RRC_INACTIVE UE via the non-anchor cell.

[0086] On-demand SIB1 requests can use existing channels, such as PRACH, to transmit random access (RA) preambles. Therefore, conventional PRACH preambles can be used as WUS. For energy-saving purposes, this document discloses how a UE can continue using the same RA procedure initiated to request SIB1 transmission after already acquiring SIB1, i.e., without initiating a new RA procedure to request UL / DL data transmission and / or switch to RRC_CONNECTED mode.

[0087] Currently, the RA procedure (4 messages or 2 messages) has a single purpose, such as requesting on-demand SIBs (SIB2 to SIB19) or initiating RRC connection restoration or establishment to transmit UL / DL data. Therefore, if the UE needs on-demand SIB1 information and data connection with the cell, the UE will in principle execute two independent RA procedures: one to request SIB1 transmission, followed by another to request RRC connection restoration or establishment after obtaining SIB1.

[0088] The inventors have identified a process to overcome this problem, allowing the UE to continue the same RA procedure after transmitting an on-demand SIB1 request (using a PRACH preamble) to the network for SIB1 transmission from the network. Therefore, the same RA procedure can be used for SIB1 requests and RRC connection establishment / recovery, instead of initiating a new RA procedure after SIB1 acquisition. Furthermore, the UE can indicate different purposes, such as whether it intends to continue RA to establish an RRC connection, perform an SDT procedure, or remain camped on the cell after acquiring SIB1.

[0089] Assume the UE receives a WUS / PRACH configuration that defines how the RA preamble is transmitted to trigger SIB1 transmission. Therefore, the UE knows which PRACH preambles and / or which transmission resources (in time / frequency) indicate the intended purpose of the RA procedure. The UE transmits a WUS / PRACH preamble to the capacity cell to request on-demand SIB1 transmission. The on-demand SIB1 request can be based on the PRACH preamble and PRACH resources as configured in the WUS / PRACH configuration above.

[0090] In one embodiment, the UE indicates whether it intends to acquire SIB1 to establish / restore an RRC connection, perform an SDT procedure, or remain camped on the cell (i.e., the UE remains in an RRC idle / inactive state). If the UE intends to establish / restore an RRC connection or perform an SDT, the network will schedule a random access response (RAR, MSG2) and an uplink random access message (MSG3) to allow the traditional RA procedure to continue. If the UE is indicating that it will camp on the cell, the network will only respond with an indication of how SIB1 can be acquired / scheduled, after which the ongoing RA procedure will be canceled / stopped (i.e., without MSG3 or MSG4). The purpose can be indicated using a subset of the RA preamble or in specific time-domain and / or frequency-domain resources.

[0091] The network can configure information for the UE to transmit on-demand SIB1 requests. This information may include indications related to a preamble group or set that can be used to select preambles for the on-demand SIB1 request. The preamble group or set used to request SIB1 may differ from preamble groups or sets known in the art that can be used to select preambles for SIB2 through SIB19 requests. Furthermore, the preamble group or set used to request SIB1 and request data communication with the cell may be another different preamble group. For example, in the current 3GPP TS 38.321 specification (e.g., version 17 or 18), the information element ra-PreambleStartIndex is defined to indicate the starting index for requesting preambles from SIB2 to SIB19. To further indicate the starting index for the preamble used to request SIB1, two information elements ra-PreambleStartIndex1 and ra-PreambleStartIndex2 may be defined for requesting SIB2 through SIB19 and SIB1, respectively. Finally, the third (or fourth, fifth, etc.) information element ra-PreambleStartIndex3 can define the starting index of the preamble used to request SIB1 and request data communication with the cell (e.g., requesting (re)establishment of RRC connection or small data transfer (SDT)).

[0092] The cell, in response to the WUS / PRACH preamble reception (i.e., in the RAR), indicates that SIB1 is scheduled and the UE subsequently acquires it. If the UE also intends to (re)establish a data connection (or SDT) with the cell and has already indicated this purpose in the random access message, the cell has two main options: The cell can define a second (RAR) window, in addition to the first (traditional) RAR window, which should be monitored by the UE to receive the scheduling DCI for message 3 for the 4-step RACH procedure. This can be indicated as part of the (first) RAR message provided in response to the WUS / PRACH preamble request for SIB1, or as part of the WUS / PRACH configuration, or defined (e.g., in the technical specification) as an offset for the SIB1 time-domain scheduling. Alternatively, the cell can indicate both DL grant (scheduling SIB1 transmission) and UL grant (scheduling MSG3) in the (first) RAR message (e.g., in the RAR MAC control element (CE)). UL authorization can be configured with a large time offset, such as K2, which allows the UE to receive SIB1 before transmitting MSG3.

[0093] When the UE has already transmitted MSG3 of the RA procedure (4 messages), the RA procedure can continue according to the traditional specification.

[0094] In one embodiment, the UE does not indicate its request for on-demand SIB1 in the Random Access Message (MSG1), but only indicates its request for a data connection to the cell. In this example, the UE may indicate whether it requests on-demand SIB1 in the MSG3. This is useful, for example, if the UE recently connected to the cell and obtained a still valid SIB1. Furthermore, MSG3 may also indicate whether the UE (actually) intends to establish / restore an RRC connection. If so, the process continues in a manner similar to a traditional procedure via MSG4 – SIB1 can be scheduled before / after MSG4.

[0095] Similarly, if a two-message RA procedure is configured, the UE can indicate whether it requests SIB1 in the PRACH or as part of the PUSCH data in the Random Access Message (MSGA). The network can then schedule SIB1 before / after the response message (MSGB), also taking into account whether the UE wants to establish / restore an RRC connection or remain camped on the cell.

[0096] The methods and systems described herein enable UEs to request on-demand SIB1 transmissions from capacity cells while facilitating the establishment / recovery of RRC connections. The procedures described herein enable the reuse of RA procedures while facilitating SIB1 transmissions when needed.

[0097] Figure 4 A flowchart of a method for implementing a dual-purpose RA process, performed by a user equipment (UE) according to this disclosure, is now presented. Figure 1 , Figure 2A and Figure 3 UE 110 is in Radio Resource Control (RRC) idle or inactive mode and performs a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode. In block 410, the UE transmits a random access message to the cell. This cell is capacity cell 120-1 (e.g., Figure 1 (A gNB 120A or 120B capacity cell) and operates in on-demand SIB1 mode. Random access messages indicate dual-purpose uses, including requests for on-demand SIB1 information from the cell and requests for data communication with the cell.

[0098] In the sense of this disclosure, data communication may include, for example, establishing a data connection (including transitioning from the RRC_IDLE state to the RRC_CONNECTED state), restoring a data connection (including transitioning from the RRC_INACTIVE state to the RRC_CONNECTED state), and / or requesting small data transfers (including remaining in the RRC_INACTIVE state).

[0099] In response to the transmission of the random access message, the UE receives a scheduling indication for the requested on-demand SIB1 information. This is illustrated in block 420. The response message from the cell may include the scheduling indication for the on-demand SIB1 information. Furthermore, in block 430, the UE receives data communication configuration information for implementing data communication with the cell. Such data communication information may be the scheduling of MSG3 in the 4-message RA procedure and / or additional configuration data required for data connection with the cell, such as the UE's identifier (RA-RNTI, C-RNTI, etc.), timing advance indication, etc.

[0100] In block 440, the UE then receives the SIB1 information according to the scheduling instruction of the SIB1 information. In block 450, the UE performs data communication with the cell according to the data communication configuration information, such as receiving MSG3, receiving further messages, or transmitting further messages to the cell.

[0101] In some embodiments, in response to transmitting a random access message, the UE also receives another response message, wherein data communication configuration information is included in the other response message. Therefore, the UE transmits a single random access message (e.g., a preamble on PRACH) to the network and receives two subsequent random access responses. The first random access response carries an SIB1 scheduling indication (i.e., how to obtain SIB1), and the second random access response carries data communication configuration information.

[0102] In some further embodiments, an indication of a time window for receiving another response message from the cell is received along with the (first) response message, along with on-demand SIB1 configuration information, and / or predefined. The time window for the first response message is typically pre-configured in the technical specifications, but may also be received in broadcast information (such as MIB). The configuration of the time window for receiving the other (i.e., second) response message ensures that the UE has sufficient time to receive SIB1.

[0103] In an alternative embodiment, data communication configuration information is included in the response message; that is, only one random access response is transmitted in response to the random access message. This random access response carries data communication configuration information and an SIB1 scheduling indication. Note that the SIB1 scheduling information may also be indicated in the on-demand SIB1 configuration information, and the response message is merely an indication of whether SIB1 is currently scheduled (based on the scheduling information received in the SIB configuration information).

[0104] In some embodiments, the UE may receive preamble configuration information from the cell, wherein the preamble configuration information indicates one or more preamble indices, one or more transport resources, or a combination thereof, for indicating a dual-use purpose. The preamble configuration information may be transmitted in the MIB or other broadcast information of the cell. Alternatively or additionally, the UE may select the random access preamble to be transmitted with the random access message and / or the transport resources to be used to indicate a dual-use purpose using the random access message. Thus, some preambles may be dedicated to indicating a dual-use purpose, some time / frequency resources of the PRACH may be dedicated to indicating a dual-use purpose, or a combination of specific preambles transmitted on specific time / frequency resources may indicate a dual-use purpose.

[0105] In embodiments where the random access procedure is a four-message random access procedure, the data communication configuration information may include uplink scheduling information for the uplink random access message (i.e., MSG3). In embodiments where the random access procedure is a two-message random access procedure, the random access message may indicate a dual-use purpose by adding an SIB1 request to the data portion (i.e., MSGA) of the random access message. Therefore, in a two-message random access procedure, the dual-use purpose may be indicated by the selected preamble, the selected transport resources, and / or the indication in the UL data portion of the MSGA.

[0106] Figure 5 A flowchart is presented illustrating a method performed by a network entity to implement a dual-purpose RA process according to this disclosure. The network entity (e.g., Figure 1 gNB 120A or 120B) supports cells (e.g., capacity cell 120-1) and user equipment UEs (such as those in Radio Resource Control RRC idle or inactive mode) in radio resource control RRC idle or inactive mode. Figure 1 , 2A The random access procedure is performed for UE 110 of cell 3, where the cell operates in on-demand SIB1 mode.

[0107] In box 510, the network entity receives a random access message from the UE. The random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell.

[0108] In response to the transmission of the random access message, the network entity transmits a scheduling instruction for the requested on-demand SIB1 information. This is illustrated in box 520. The response message from the cell may include the scheduling instruction for the on-demand SIB1 information. Furthermore, in box 530, the network entity transmits data communication configuration information for implementing data communication with the cell. Such data communication information may be the scheduling of MSG3 in the 4-message RA procedure and / or additional configuration data required for data connection with the cell, such as the UE identifier (RA-RNTI, C-RNTI, etc.), timing advance indication, etc.

[0109] In block 540, the network entity transmits SIB1 information according to the scheduling instructions of the SIB1 information. In block 550, the network entity performs data communication with the UE according to the data communication configuration information, such as transmitting MSG3, receiving further messages, or transmitting further messages to the UE.

[0110] In some embodiments, in response to receiving a random access message, the network entity also transmits another response message, wherein data communication configuration information is included in the other response message. Therefore, the network entity receives a single random access message from the UE (e.g., a preamble on PRACH) and transmits two subsequent random access responses. The first random access response carries an SIB1 scheduling indication (i.e., how to obtain SIB1), and the second random access response carries data communication configuration information.

[0111] In some further embodiments, an indication of a time window for transmitting another response message is transmitted along with the (first) response message, along with on-demand SIB1 configuration information, and / or predefined. The time window for the first response message is typically pre-configured in the technical specifications, but may also be received in broadcast information (such as MIBs). The configuration of a time window for receiving another (i.e., second) random access message ensures that the UE has sufficient time to receive SIB1.

[0112] In an alternative embodiment, data communication configuration information is included in the response message; that is, only one random access response is transmitted in response to the random access message. This random access response carries data communication configuration information and an SIB1 scheduling indication. Note that the SIB1 scheduling information may also be indicated in the on-demand SIB1 configuration information, and the response message is merely an indication of whether SIB1 is currently scheduled (based on the scheduling information transmitted in the SIB configuration information).

[0113] In some embodiments, a network entity may transmit preamble configuration information, wherein the preamble configuration information indicates one or more preamble indices, one or more transport resources, or a combination thereof, for indicating a dual-use purpose. The preamble configuration information may be transmitted in the MIB or other broadcast information of the cell. Alternatively or additionally, the network entity may determine the indication of a dual-use purpose based on the selected random access preamble and / or transport resources used to transmit the random access message; it may also select the random access preamble and / or transport resources used to transmit the random access message to utilize the random access message to indicate a dual-use purpose. Thus, some preambles may be dedicated to indicating a dual-use purpose, some time / frequency resources of the PRACH may be dedicated to indicating a dual-use purpose, or a combination of specific preambles transmitted on specific time / frequency resources may indicate a dual-use purpose.

[0114] In embodiments where the random access procedure is a four-message random access procedure, the data communication configuration information may include uplink scheduling information for the uplink random access message (i.e., MSG3). In embodiments where the random access procedure is a two-message random access procedure, the random access message may indicate a dual-use purpose by adding an SIB1 request to the data portion (i.e., MSGA) of the random access message. Therefore, in a two-message random access procedure, the dual-use purpose may be indicated by the selected preamble, the selected transport resources, and / or the indication in the UL data portion of the MSGA.

[0115] Figure 6 A message flow diagram illustrating the efficient SIB1 request and data connection establishment according to an embodiment is shown. UE 110 transmits a random access message to gNB 120 (e.g., via capacity cell 120-1 of gNB 120), as indicated by arrow 601. In this example, the random access message is MSG1 of the four-message RA procedure. The random access message also carries an indication of the dual purpose of the RA procedure, namely, that it indicates UE 110 requires both on-demand SIB1 and a data connection with gNB 120.

[0116] Then, UE 110 monitors and receives a random access response from gNB 110, and thus receives the random access response as indicated by arrow 602. In this example, the random access response is MSG2 (RAR) in the RA procedure. The (first) time window and / or resources used to monitor and receive this first random access response can be predefined in the technical specifications and / or broadcast by cell 120-1 of gNB 120. In this example, the first random access response includes an SIB1 scheduling indication and a second random access window. The second random access window defines when UE 110 will receive the second response message.

[0117] UE 110 first receives SIB1 information according to the SIB1 scheduling instruction, as shown by arrow 603, and waits for the second time window to begin. Then, it begins monitoring to receive the second response message, as shown by arrow 604. This second response message carries the scheduling DCI for MSG3, i.e., data communication configuration information, such as the time / frequency resources that UE 110 can transmit for MSG3, and UE 110's Random Access Identifier (RA-RNTI). Afterward, the method continues to transmit MSG3 and MSG4 in the conventional manner and completes the RA procedure to establish a data connection with cell 120-1 of gNB 120.

[0118] Figure 7 A message flow diagram for efficient SIB1 request and data connection establishment according to another embodiment is shown. UE 110 also transmits a random access message to gNB 120 (e.g., via capacity cell 120-1 of gNB 120), as indicated by arrow 701. In this example, the random access message is MSG1 of the four-message RA procedure. The random access message also carries an indication of the dual purpose of the RA procedure, i.e., it indicates that UE 110 requires both on-demand SIB1 and a data connection with gNB 120.

[0119] Then, UE 110 monitors the random access response received from gNB 110 and thus receives the random access response, as indicated by arrow 702. In this example, the random access response is MSG2 (RAR) in the RA procedure. The time window and / or resources used to monitor and receive this random access response can be predefined in the technical specifications and / or broadcast by cell 120-1 of gNB 120.

[0120] In this example, the random access response includes an SIB1 scheduling indication and a scheduling DCI for MSG3, i.e., data communication configuration information, such as time / frequency resources when UE 110 can transmit MSG3 and UE 110's random access identifier (RA-RNTI).

[0121] Then, UE 110 receives SIB1 information according to the SIB1 scheduling instruction, as shown by arrow 703. Afterwards, the method continues to transmit MSG3 and MSG4 in the conventional manner and completes the RA procedure to establish a data connection with cell 120-1 of gNB 120. Although Figure 6 and Figure 7 The message flow of a four-message RA process is described, but the same concept also applies to a two-message RA process as described above.

[0122] Figure 8This is a detailed overview of possible alternative or additional procedures performed according to this disclosure. All procedures begin with the UE indicating the reason for the SIB1 request (box 800), i.e., the reason for transmitting MSG1 during the RA procedure. If the UE indicates that there is data to transmit (box 801), the UE begins monitoring the DCI to schedule a random access response, i.e., a RAR (box 802). The UE receives the RAR. In one example, the RAR may include on-demand SIB1 scheduling information, which also serves as an SIB1 scheduling indication (box 803). The scheduling information may be an indication of the search space used to receive SIB1. In this example, the UE directly knows how to acquire SIB1 and does not require further information.

[0123] In another embodiment, the RAR may consist only of an acknowledgment, which serves as an SIB1 scheduling indication (box 804). Therefore, the RAR can instruct the UE that it should monitor SIB scheduling information (box 805). The scheduling information may be included in the SIB1 request configuration, such as on-demand SIB1 configuration information (box 806), or included in the MIB (box 807). In all cases, the UE has received the SIB1 scheduling information and can accordingly acquire SIB1 (box 808).

[0124] Then, the UE also needs to obtain MSG3 to enable data communication with the cell. Different options exist for receiving the scheduling information of MSG3 (box 809). The UE can be instructed to monitor the scheduling DCI in the Physical Downlink Control Channel (PDCCH) within a time window following the reception of SIB1 (box 810). The PDCCH monitoring configuration can be indicated to the UE in the RAR (box 811), SIB1 information (box 812), or SIB1 request configuration (e.g., on-demand SIB1 configuration information (box 813)), and / or can be predefined in the technical specifications, i.e., standardized (box 814).

[0125] The UE may also alternatively receive a direct UL grant (box 815). The UL grant may be part of the RAR, for example, defining a time offset such as K2 in the NR (box 816); may be configured via SIB1 information (box 817); and / or may be predefined in the technical specifications, i.e., standardized (box 818). In all cases, the UE then has the scheduling information for MSG3 and may transmit MSG3, i.e., continue the RA procedure as usual to (re)establish a data connection with the cell (box 819).

[0126] Exemplary implementations of UL licensing are described below, and are, for example, in part with boxes 815, 816, 817, 818, and 819: A method is provided performed by a User Equipment (UE) wherein the UE is in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode. In this operating state, the UE is receiving configuration for an On-Demand SIB1 request, which includes information related to at least one pre-configured Physical Random Access Channel (PRACH) timing and at least one pre-configured Physical Uplink Shared Channel (PUSCH) resource for transmitting RRC messages. The pre-allocation or reservation of PRACH and PUSCH resources has the advantage that when the UE has uplink (UL) data to transmit, the pre-configured resources can be used to transmit UL data faster because it eliminates the need to perform two consecutive RACH procedures—one for acquiring SIB1 information and the other for accessing the cell. Therefore, the UE is able to… At least one of the pre-configured PRACH timings is used to transmit a random access message to the cell, wherein the random access message indicates a dual purpose, including a request for on-demand SIB1 information from the cell and a request for data communication with the cell.

[0127] In response to transmitting random access messages: The UE receives a response message from the cell, which includes a scheduling instruction for the requested on-demand SIB1 information; receives SIB1 information according to the scheduling instruction for the SIB1 information; and also transmits at least one RRC message using pre-configured PUSCH resources.

[0128] RRC messages may include requests for data communication, wherein such requests are related to at least one of the following: RRC establishment request, RRC recovery request, and uplink data. In this way, various connections are supported in a single step using pre-configured UL grants (multiple PUSCH resources).

[0129] The scheduling indication for the requested on-demand SIB1 information can indicate the start of SIB1 transmission. The start indication can be an acknowledgment (ACK) signal indicating that the network has received the preamble and will begin SIB1 transmission, or an indication of the start time of the SIB transmission, etc. Therefore, the ACK signal is a dual-use message indicating that the preamble has been received. Thus, the UE does not need to retransmit the preamble. Additionally, the UE is notified that SIB1 transmission has started, and therefore the UE subsequently monitors the reception of SIB1. This reduces signaling load. The scheduling indication for the requested on-demand SIB1 information can also indicate the resources for SIB1 transmission. The resource indication can be associated with one or more physical resource blocks (PRBs) and / or symbols (e.g., time and frequency resources) used for transmitting SIB1 information.

[0130] Information associated with at least one pre-configured PUSCH resource may include configuration authorization settings. This is a direct indication of the specific time slots that the UE can use, for example, UL data. Information associated with at least one pre-configured PUSCH resource may include a time-based PUSCH resource offset, where the offset is relative to either the PRACH timing or the response message. This is an indirect indication of the specific time slots that the UE can use. This may require less signaling. Furthermore, this provides the possibility of dynamically changing or adjusting the time offset between PRACH and PUSCH, thereby changing the time delay between PRACH signals and UL data transmission, thus allowing, for example, sufficient processing time to receive and process SIB1 information while reducing the time delay in transmitting UL data.

[0131] As an alternative to transmitting PUSCH resources along with PRACH resources, PUSCH resource indications can also be included in the SIB1 information. For example, the UE may be receiving SIB1 information according to a scheduling instruction, where the SIB1 information includes at least one pre-configured Physical Uplink Shared Channel (PUSCH) resource for transmitting RRC messages. In this case, pre-coordination between PUSCH and PRACH is not required, but direct or indirect PUSCH indications similar to those described above can still be used. In both cases, the UE does not need to first acquire the SIB1 information and then monitor the DCI with UL authorization information. This reduces the time required to begin transmitting UL data.

[0132] Perform appropriate steps on the network side to enable the UE to perform the operations implemented as described above.

[0133] Alternatively, the UE can indicate that it does not need a data connection and only wants to camp on the cell (box 820). Then, a reduced RA procedure is applied, ending with a RAR transmission, where the RAR's MAC header indicates acknowledgment of the SIB1 request (box 821). SIB1 scheduling information can be included in the SIB1 request configuration, for example, in the on-demand SIB1 configuration information, or by the MIB (box 822). Finally, the UE has received the SIB1 scheduling information and can acquire SIB1 accordingly. The RA procedure then ends.

[0134] The processes described herein can be applied by model or by functional level (identified by identifiers) or across models or functions of a given entity, for example, as UE features. It should be understood that the apparatus described herein may include or be coupled to other units or modules, such as radio sections or radio heads, used in or for transmission and / or reception. Although the apparatus has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0135] Note that while embodiments have been described with respect to LTE and 5G NR, similar principles can be applied to other networks and communication systems that require rapid connection re-establishment. Therefore, although certain embodiments have been described above by way of example with reference to certain example architectures of wireless networks, technologies, and standards, these embodiments can be applied to any other suitable form of communication system beyond those shown and described herein.

[0136] It should also be noted that although exemplary embodiments have been described above, several changes and modifications may be made to the disclosed solutions without departing from the scope of this disclosure.

[0137] Generally, various exemplary embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects disclosed in this subject matter can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this subject matter disclosure is not limited thereto. Although the aspects disclosed in this subject matter may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, these blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0138] The exemplary embodiments disclosed in this subject matter can be implemented by computer software executable by a data processor of a mobile device (such as in a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets, and / or macros) can be stored in any device-readable data storage medium, and they include program instructions for performing a specific task. A computer program product may include one or more computer-executable components that are configured to perform the embodiments when the program is run. The one or more computer-executable components may be at least one piece of software code or a portion thereof.

[0139] Furthermore, it should be noted in this regard that any block in the logical flow shown in the accompanying drawings may represent a program process, or interconnected logical circuits, blocks and functions, or a combination of program processes and logical circuits, blocks and functions. Software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, CDs. Physical media are non-transitory media.

[0140] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. As a non-limiting example, the data processor can be of any type suitable for the local technical environment and can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, gate-level circuits, and processors based on multi-core processor architectures.

[0141] The exemplary embodiments disclosed in this subject can be practiced in various components such as integrated circuit modules. The design of integrated circuits is primarily a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready for etching and formation on semiconductor substrates.

[0142] The foregoing description has provided a complete and informative description of exemplary embodiments of the subject matter disclosed by way of non-limiting example. However, various modifications and adjustments may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such and similar modifications to the teachings of this disclosure will still fall within the scope of this disclosure as defined in the appended claims. Indeed, there are other embodiments that include combinations of one or more embodiments with any other embodiments discussed above.

Claims

1. A method performed by a user equipment (UE) wherein the UE is in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode, the method comprising: Receive configuration for on-demand SIB1 requests, the configuration including information related to at least one pre-configured Physical Random Access Channel (PRACH) timing and at least one pre-configured Physical Uplink Shared Channel (PUSCH) resource for transmitting RRC messages. At least one of the pre-configured PRACH timings is used to transmit a random access message to the cell, wherein the random access message indicates a dual purpose, the dual purpose including a request for on-demand SIB1 information from the cell and a request for data communication with the cell. In response to transmitting the random access message: Receive a response message from the cell, the response message including a scheduling instruction for the requested on-demand SIB1 information; and Receive the SIB1 information according to the scheduling instruction of the SIB1 information; and Use at least one of the pre-configured PUSCH resources to transmit RRC messages.

2. The method of claim 1, wherein, The RRC message includes a request for data communication, wherein the request for data communication is related to at least one of the following: RRC establishment request, RRC recovery request, uplink data, and downlink data.

3. The method according to claim 1, wherein, The scheduling instruction for the requested on-demand SIB1 information indicates the start of the SIB1 transmission and / or a resource.

4. The method according to claim 1, wherein, The information associated with the at least one pre-configured PUSCH resource includes configuration authorization settings.

5. The method according to claim 1, wherein, The information associated with the at least one pre-configured PUSCH resource includes a time-varying PUSCH resource offset, wherein the offset is relative to either the PRACH timing or the response message.

6. The method according to claim 1, further comprising: The cell receives preamble configuration information, wherein the preamble configuration information indicates one or more preamble indices, one or more transmission resources, or a combination thereof, for indicating the dual-use purpose.

7. The method according to claim 1, further comprising: Select a random access preamble and / or transmission resources for transmitting the random access message to indicate a dual-use purpose using the random access message.

8. The method according to any one of claims 1 to 7, wherein, The random access procedure is a four-message random access procedure, wherein the RRC message is located in the third message MSG3 of the random access procedure.

9. The method according to any one of claims 1 to 5, wherein, The random access procedure is a two-message random access procedure, wherein the random access message indicates a dual-use purpose by adding an SIB1 request indication to the data portion of the random access message.

10. A method performed by a network entity for supporting a random access procedure between a cell and a user equipment (UE), wherein the UE is in a Radio Resource Control (RRC) idle or inactive mode, wherein, The cell operates in on-demand SIB1 mode, and the method includes: The configuration for on-demand SIB1 requests is transmitted to the UE. This configuration includes information related to at least one pre-configured Physical Random Access Channel (PRACH) timing and at least one pre-configured Physical Uplink Shared Channel (PUSCH) resource for transmitting RRC messages. On one of the pre-configured PRACH timings, a random access message is received from the UE, wherein the random access message indicates a dual purpose, the dual purpose including a request for on-demand SIB1 information from the cell and a request for data communication with the cell; In response to receiving the random access message: A response message is transmitted to the UE, the response message including a scheduling indication of the requested on-demand SIB1 information; and Transmit the SIB1 information to the UE according to the scheduling instruction of the SIB1 information; and Receive RRC messages from the UE on at least one of the pre-configured PUSCH resources.

11. A user equipment (UE) configured to support operation in Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode, and configured to perform the method steps of claim 1.

12. An apparatus for a network entity, configured to support a random access procedure between a cell and a user equipment (UE), wherein the UE is in a Radio Resource Control (RRC) idle or inactive mode, wherein, The cell operates in on-demand SIB1 mode, and the device is configured to perform the method steps of claim 10.

13. A method performed by a user equipment (UE) wherein the UE is in a Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode, the method comprising: Transmit a random access message to the cell, wherein the random access message indicates a dual purpose, the dual purpose including a request for on-demand SIB1 information from the cell and a request for data communication with the cell; In response to transmitting the random access message: Receive a response message from the cell, the response message including a scheduling instruction for the requested on-demand SIB1 information; and The SIB1 information is received according to the scheduling instruction of the SIB1 information, wherein the SIB1 information includes at least one pre-configured Physical Uplink Shared Channel (PUSCH) resource for transmitting RRC messages; and Use at least one of the pre-configured PUSCH resources to transmit RRC messages.

14. The method of claim 13, further comprising: Receive configuration for on-demand SIB1 requests, the configuration including information related to the timing of at least one pre-configured Physical Random Access Channel (PRACH). The random access message is transmitted to the cell using at least one of the pre-configured PRACH timings, wherein the random access message indicates a dual purpose, the dual purpose including a request for on-demand SIB1 information from the cell and a request for data communication with the cell.

15. A user equipment (UE) configured to support operation in Radio Resource Control (RRC) idle or inactive mode during a random access procedure with a cell operating in On-Demand System Information Block 1 (SIB1) mode, and configured to perform the method steps of claim 13.

Images