Preconfigured dual purpose random access procedure

Abstract

Methods, apparatuses, and systems are provided for a user equipment, UE, in 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 towards the cell. The random access message indicates a dual use purpose including a request for 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 comprising 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 preconfiguration, which could e.g. be a related to a preconfigured PUSCH resource indicated in an on-demand SIB1 configuration, or together with the SIB1 transmission, or else. Similar methods, apparatuses, and systems are provided for a network entity as well.

Description

PRECONFIGURED DUAL PURPOSE RANDOM ACCESS PROCEDURETECHNICAL FIELD

[0001] The subject disclosure generally relates to wireless communication systems and, in particular, to on-demand system information block 1 (SIB1) procedures or to enablers thereof. Yet more particularly, the subject disclosure provides methods and apparatuses for requesting SIB1 information by a dual purpose random access procedures.BACKGROUND

[0002] Wireless telecommunication systems, also referred to mobile communication systems, are under constant development. One crucial aspect in these mobile communication systems is energy saving. For user equipments (UEs), several techniques have been developed, such as discontinuous transmission and reception (DRT, DRX), energy saving in inactive and idle modes, etc., but many techniques for network energy savings (NES) are still in early phases of their development.

[0003] Usually, for example in the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) mobile communication system, system information (SI) is broadcasted periodically over the entire cell area to inform UEs about parameters of the network in a continuous manner. The main drawback of this continuous broadcasting is a low energy efficiency, in particular, if a cell is faced with a low load or with no load in the cell (i.e., there are few or no UEs to benefit from the transmitted SI).

[0004] In the 3GPP 5th generation (5G) / New Radio (NR) mobile communication system, transmission of system information of other SI than minimum SI may be omitted. Minimum SI relates to information relating to master information block (MIB) and system information block 1 (SIB 1). The information of SIB2 to SIB19 may, additionally or alternatively to broadcasting, provided on demand. MIB and SIB1 are currently still broadcasted regularly in NR to carry basic information required for initial access of the UEs.

[0005] A further enhancement of NES could be to also provide SIB1 information only on demand. Since SIB1 comprises essential system information for communicating with a cell, the procedures for on-demand SIB2 to SIB 19 may not be applied. One option being discussed in the development of the technical specifications for NR is to transmit an on-demand SIB1 request with a random access message in a random access procedure to the network, which understands that the random access message is only a SIB1 request and no request for data connection. This means that a UE, which requires the on-demand SIB1 information andsubsequent data connection with the cell, needs to start two random access procedures and sends to different preambles to the network. This is again a waste of time and resources.

[0006] Hence, methods and apparatuses supporting efficient acquisition of on-demand SIB1 information and initiation of data connected with a cell are required.SUMMARY

[0007] According to a first aspect of the subject disclosure, a method performed by a user equipment, UE, in 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, is provided. The method comprises transmitting a random access message towards the cell, wherein the random access message indicates a dual use 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 a response message from the cell comprising scheduling indication of the requested on-demand SIB1 information and receiving data communication configuration information for enabling data communication with the cell. The method further comprises receiving the 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 performed by a network entity for supporting a random access procedure of a cell with a user equipment, UE, in radio resource control, RRC, idle or inactive mode, wherein the cell operates in an on-demand SIB1 mode, is provided. The method comprises receiving a random access message from the UE, wherein the random access message indicates a dual use 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 a response message to the UE comprising scheduling indication of the requested on-demand SIB1 information and transmitting data communication configuration information for enabling data communication with the UE. The method further comprises transmitting the 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 of a user equipment, UE, in 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, is provided. The apparatus is configured to transmit a random access message towards the cell, wherein the random accessmessage indicates a dual use 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 a response message from the cell comprising scheduling indication of the requested on-demand SIB1 information and receive data communication configuration information for enabling data communication with the cell. The apparatus is further configured to receive the SIB 1 information according to the scheduling indication of the SIB1 information and perform data communication with the cell according to the data communication configuration information.

[0010] According to a fourth aspect, an apparatus of a network entity for supporting a random access procedure of a cell with a user equipment, UE, in radio resource control, RRC, idle or inactive mode, wherein the cell operates in an on-demand SIB1 mode, is provided. The apparatus is configured to receive a random access message from the UE, wherein the random access message indicates a dual use 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 a response message to the UE comprising scheduling indication of the requested on-demand SIB1 information and transmit data communication configuration information for enabling data communication with the UE. The apparatus is further configured to transmit the SIB1 information according to the scheduling indication of the SIB 1 information and perform data communication with the UE according to the data communication configuration information.

[0011] According to embodiment of all aspects above, the random access message is e.g. a first message, MSG1 or MSGA, or a third message, MSG3, in a random access procedure.

[0012] According to embodiments of the first and second aspects, the method further comprises, in response to transmitting / receiving the random access message, receiving / transmitting another response message, wherein the data communication configuration information is comprised by the another response message. According to embodiments of the third and fourth aspects, the apparatuses are further configured to, in response to transmitting / receiving the random access message, receive / transmit another response message, wherein the data communication configuration information is comprised by the another response message. According to further embodiments of all aspects, an indication of a time window for transmitting / receiving the another response message is received / transmitted with the response message, is received / transmitted with on-demand SIB1 configuration information, and / or is pre-defined.

[0013] According to embodiments of all aspects above, the data communication configuration information is e.g. comprised by the response message.

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

[0015] According to embodiments of the first and third aspect, the method further comprises / the apparatus is further configured to selecting / select a random access preamble for transmission with the random access message and / or transmission resources for transmitting the random access message to indicate dual use purpose with the random access message. According to embodiments of the second and fourth aspect, the method further comprises / the apparatus is further configured to determining / determine the indication of dual use purpose according to a selected a random access preamble for transmission with the random access message and / or transmission resources for transmitting the random access message.

[0016] In embodiments of all aspects above, the random access procedure is e.g. a four message random access procedure, wherein the data communication configuration information comprises uplink scheduling information for an uplink random access message. In embodiments of all aspects, the random access procedure is a two message random access procedure, wherein the random access message indicates dual use purpose by adding a SIB 1 request in a data part of the random access message.

[0017] According to a fifth aspect, a method performed by a user equipment, UE, is provided. The UE is in 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 is receiving a configuration for an on-demand SIB1 request including information related to at least one preconfigured physical random access channel, PRACH, occasion and at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message.The UE is further transmitting a random access message towards the cell using at least one of the preconfigured PRACH occasions, wherein the random access message indicates a dual use 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: the UE is receiving a response message from the cell comprising scheduling indication of the requested on-demand SIB1 information; and receiving the SIB1 information according to the scheduling indication of the SIB 1 information; and further transmitting an RRC message using at least one of the preconfigured PUSCH resources.

[0018] According to a sixth aspect, a method performed by a user equipment, UE, is provided. The UE is in 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 is transmitting a random access message towards the cell, wherein the random access message indicates a dual use 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:The UE is receiving a response message from the cell comprising scheduling indication of the requested on-demand SIB1 information; and receiving the SIB1 information according to the scheduling indication of the SIB1 information, wherein the SIB1 information includes at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message; and further transmitting an RRC message using at least one of the preconfigured PUSCH resources.

[0019] In further embodiments of all aspects above, parts of aspects may be combined with parts of other aspects to form new combinations.

[0020] The above-noted aspects and features may be implemented in systems, apparatuses, methods, articles and non-transitory computer-readable media depending on the desired configuration. The subject disclosure may be implemented in and used with a number of different types of devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

[0021] This summary is intended to provide a brief overview of some of the aspects and features according to the subject disclosure. Accordingly, it will be appreciated that the abovedescribed features are merely examples and should not be construed to narrow the scope of thesubject disclosure in any way. Other features, aspects, and advantages of the subject disclosure will become apparent from the following detailed description, drawings and claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0022] A better understanding of the subject disclosure may be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0023] FIG. 1 shows a schematic diagram of an example wireless network.

[0024] FIG. 2A shows a schematic diagram of an example wireless device.

[0025] FIG. 2B shows a schematic diagram of an example network node.

[0026] FIG. 3 is an overview on two possible scenarios for applying the methods described in this disclosure.

[0027] FIG. 4 presents a flow chart of a method performed by a user equipment according to the disclosure.

[0028] FIG. 5 presents a flow chart of a method performed by a network entity according to the disclosure.

[0029] FIG. 6 shows a message flow diagram of efficient SIB1 request and data connection establishment according to an embodiment.

[0030] FIG. 7 shows a message flow diagram of efficient SIB1 request and data connection establishment according to another embodiment.

[0031] FIG. 8 is a detailed overview on possible processes performed according to the disclosure.DETAILED DESCRIPTION

[0032] The examples and embodiments set forth below represent information to enable those skilled in the art to practice the subject disclosure. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description.

[0033] In the following description, numerous specific details are set forth. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not to obscure the understanding of the description. Those of ordinary skill in the art, with theincluded description, will be able to implement appropriate functionality without undue experimentation.

[0034] References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0035] As used herein, "plurality" means two or more. As used herein, a "set" of items may include one or more of such items. As used herein, whether in the subject disclosure or the claims, the terms "comprising", "including", "carrying", "having", "containing", "involving", and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases "consisting of and "consisting essentially of, respectively, are closed or semi-closed transitional phrases with respect to claims. Use of ordinal terms such as "first", "second", "third", etc., in the claims or the subject disclosure to modify an element does not by itself connote any priority, precedence, or order of one element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one element having a certain name from another element having a same name (but for use of the ordinal term) to distinguish the elements. As used herein, "and / or" and "at least one of means that the listed items are alternatives, but the alternatives also include any combination of the listed items.

[0036] Before explaining the examples according to the subject disclosure in detail, certain general principles of a wireless communication system are briefly explained with reference to FIGS. 1 to 3 to assist in understanding the technology underlying the described examples.

[0037] FIG. 1 illustrates an example of a wireless network 100 that may be used for wireless communications. 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., eNBs, gNBs, etc.), connected to one or more network nodes 130 over an interconnecting network 125. The network 100 may use any suitable deployment scenarios. UEs 110 within coverage area 115 may each be capable of communicating directly with radio access nodes 120 over a wireless or air interface. In some embodiments, UEs 110 may also be capable of communicating with each other via D2D communication.

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

[0039] As used herein, the term "user equipment" (UE) has the full breadth of its ordinary meaning and may refer to any type of wireless device which may communicate with a network node and / or with another UE in a cellular or mobile or wireless communication system. Examples of UE are target device, D2D UE, machine type UE or UE capable of machine-to- machine (M2M) communication, personal digital assistant, tablet, mobile terminal, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, ProSe UE, vehicle-to-vehicle (V2V) UE, V2X UE, MTC UE, eMTC UE, FeMTC UE, UE Cat 0, UE Cat Ml, narrow band loT (NB-IoT) UE, UE Cat NB1, etc. Example embodiments of a UE are described in more detail below with respect to FIG. 2A.

[0040] In some embodiments, an area of wireless signal coverage 115 associated with a radio access node 120 may be referred to as a cell. However, particularly with respect to the 5thgeneration (5G) / New Radio (NR) mobile communication concepts, beams, such as the herein described multicast radio beams (MRBs) may be used within cells for communication. In some embodiments described herein, the UE 110 may be in an RRC inactive or idle mode and camp on a cell of radio access node 120 A, which be denoted as anchor or coverage cell, and may be in the coverage area 115 of radio access nodes 120A and 120B. The cell of radio access node 120B may be denoted as non-anchor or capacity cell. Although not shown in FIG. 1, there may be more than one non-anchor cell provided by more than one other radio access node 120. The UE 100 may, in some embodiments, may want to switch the cells, i.e., transition to camp on an non-anchor cell.

[0041] With respect to a beam-based mobile communication system, the radio access node 120 (base station) may transmit a beamformed signal to the UE 110 in one or more transmit directions (transmission beam, Tx beam). The UE 110 may receive the beamformed signal from the base station 120 in one or more receive directions (reception beam, Rx beam). The UE 110 may also transmit a beamformed signal to the base station 120 in one or more directions and the base station 120 may receive the beamformed signal from the UE 110 in one or more directions. The base station 120 and the UE 110 may determine the best receive and transmit directions, e.g., best in the sense of these directions leading to the highest link quality or fulfilling other quality conditions in the most suitable manner, for each of the base station / UE pairs.

[0042] The interconnecting network 125 may refer to any interconnecting system capable of transmitting audio, video, signals, data, messages, etc., or any combination of the preceding. The interconnecting network 125 may include all or a portion 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 communication or computer network such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof.

[0043] In some embodiments, the network node 130 may be a core network node, managing the establishment of communication sessions and other various other functionalities for UEs 110. Examples of network node 130 may include mobile switching center (MSC), MME, serving gateway (SGW), packet data network gateway (PGW), operation and maintenance (O&M), operations support system (OSS), SON, positioning node (e.g., Enhanced Serving Mobile Location Center, E-SMLC), location server node, MDT node, etc. UEs 110 may exchange certain signals with the network node 130 using the non-access stratum (NAS) layer. In non-access stratum signaling, signals between UEs 110 and the network node 130 may be transparently passed through the radio access network. In some embodiments, radio access nodes 120 may interface with one or more network nodes 130 over an internode interface.

[0044] As used herein, the term "network node" has the full breadth of its ordinary meaning and may correspond to any type of radio access node (or radio network node) or any network node, which may 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, a network node may belonging 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 controlling 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, Self-organizing Network (SON), positioning node (e.g., E-SMLC), MDT, test equipment, etc. Example embodiments of a network node are described in more detail below with respect to FIG. 5, 6, 7, and 8.

[0045] In some embodiments, radio access node 120 may be a distributed radio access node. The components of the radio access node 120, and their associated functions, may be separated into two main units (or sub-radio network nodes) which may be referred to as the central unit (CU) and the distributed unit (DU). Different distributed radio network node architectures are possible. For instance, in some architectures, a DU may be connected to a CUvia dedicated wired or wireless link (e.g., an optical fiber cable) while in other architectures, a DU may be connected a CU via a transport network. Also, how the various functions of the radio access node 120 are separated between the CU(s) and DU(s) may vary depending on the chosen architecture.

[0046] In some embodiments, radio access nodes 120 may communicate with each other over terrestrial or other connections. The communication between the radio access nodes 120 may, e.g., in a 5G / NR communication system may be achieved by using an Xn interface connecting the radio access nodes 120.

[0047] Exemplary wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). A latest 3GPP based development is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology (RAT). The various development stages of the 3GPP specifications are referred to as releases. More recent developments of the LTE are often referred to as LTE Advanced (LTE-A). The LTE (LTE-A) employs a radio mobile architecture known as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network known as the Evolved Packet Core (EPC). Base stations of such systems are known as evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane Packet Data Convergence / Radio Link Control / Medium Access Control / Physical layer protocol (PDCP / RLC / MAC / PHY) and control plane Radio Resource Control (RRC) protocol terminations towards the communication devices. Other RAT examples comprise those provided by base stations of systems that are based on technologies such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). A base station may provide coverage for an entire cell or similar radio service area. Core network elements include Mobility Management Entity (MME), Serving Gateway (S-GW) and Packet Gateway (P-GW).

[0048] An example of a suitable communications system is the 5G or NR concept. Network architecture in NR may be similar to that of LTE-A. Base stations of NR systems may be known as next generation Node Bs (gNBs). Changes to the network architecture may depend on the need to support various radio technologies and finer Quality of Service (QoS) support, and some on-demand requirements for QoS levels to support Quality of Experience (QoE) of user point of view. Also network aware services and applications, and service and application aware networks may bring changes to the architecture. Those are related to Information Centric Network (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR may use multiple input-multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation withsmaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[0049] Future networks may utilize network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes, or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.

[0050] An example 5G core network (CN) comprises functional entities. The CN is connected to a UE via the radio access network (RAN). An UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) may be responsible for forwarding frames back and forth between the DN (data network) and the tunnels established over the 5G towards the UEs exchanging traffic with the data network (DN). The UPF is controlled by an SMF (Session Management Function) that receives policies from a PCF (Policy Control Function). The CN may also include an AMF (Access & Mobility Function).

[0051] Generally, all concepts disclosed herein may be applicable to different communication networks, comprising but not limited to LTE, LTE-A, 5G, 5G advanced, 6G, and other future or already implemented networks.

[0052] FIG. 2A is a schematic diagram of an apparatus for the UE. In an embodiment, the apparatus may comprise the UE, in yet another embodiment the apparatus is comprised in the UE, and in another embodiment the apparatus is the UE. The apparatus may comprise a wireless device. The apparatus may comprise at least one processor 220 and at least memory 230 storing computer program instructions that, when executed by the at least one processor 220, cause the apparatus to carry out the embodiments of the UE 110 described herein. UE 110 includes a transceiver 210, processor 220, memory 230, and a network interface 240. In some embodiments, the transceiver 210 facilitates transmitting wireless signals to and receiving wireless signals from radio access node 120 (e.g., via transmitter(s) (Tx), receiver(s) (Rx) and antenna(s)). The processor 220 executes instructions to provide some or all of the functionalities described herein as being provided by UE 110, and the memory 230 stores the instructionsexecuted by the processor 220. In some embodiments, the processor 220 and the memory 230 form processing circuitry.

[0053] The processor 220 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the described functions of UE 110 described herein. In some embodiments, the 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.

[0054] The memory 230 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and / or other instructions capable of being executed by a processor 220. Examples of memory 230 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or or any other volatile or non-volatile, non- transitory computer-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processor 220 of UE 110. For example, the memory 230 includes computer program code causing the processor 220 to perform processing according to the methods described herein, e.g., the methods of FIG. 4, 6, 7, and 8.

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

[0056] Other embodiments of UE 110 may include additional components beyond those shown in FIG. 2 A that may be responsible for providing certain aspects of the wireless device’s functionalities, including any of the functionalities described herein and / or any additional functionalities (including any functionality necessary to support the mechanisms according to the subject disclosure). As an example, UE 110 may include input devices and circuits, output devices, and one or more synchronization units or circuits, which may be part of the processor 220. Input devices include mechanisms for entry of data into UE 110. For example, input devices may include input mechanisms, such as a microphone, input elements, a display, etc.Output devices may include mechanisms for outputting data in audio, video and / or hard copy format. For example, output devices may include a speaker, a display, etc.

[0057] In some embodiments, the wireless device UE 110 may comprise a series of modules configured to implement the functionalities of the wireless device described herein. Moreover, in some embodiments, the UE 110 may also comprise means for the functionalities described herein.

[0058] It will be appreciated that the various modules may be implemented as combination of hardware and software, for instance, the processor, memory, and transceiver(s) of UE 110 shown in FIG. 2A. Some embodiments may also include additional modules to support additional and / or optional functionalities.

[0059] FIG. 2B is a schematic diagram of an example of an apparatus for a radio access node 120 or network node 130. The apparatus may comprise at least one processor 220 and at least memory 230 storing computer program instructions that, when executed by the at least one processor 220, cause the apparatus to carry out 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, processor 320, memory 330, and network interface 340. In some embodiments, the transceiver 310 facilitates transmitting wireless signals to and receiving wireless signals from wireless devices, such as UE 110 (e.g., via transmitter(s) (Tx), receiver(s) (Rx), and antenna(s)). The processor 320 executes instructions to provide some or all of the functionalities described herein as being provided by the radio access node 120 or the network node 130, the memory 330 stores the instructions executed by the processor 320. In some embodiments, the processor 320 and the memory 330 form processing circuitry. The network interface 340 may communicate signals to backend network components, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), core network nodes or radio network controllers, etc.

[0060] The processor 320 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all of the described functions of the radio access node 120 or the network node 130, such as those described herein. In some embodiments, the 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.

[0061] The memory 330 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables,etc. and / or other instructions capable of being executed by a processor 320. Examples of memory 330 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or or any other volatile or non-volatile, non- transitory computer-readable and / or computer-executable memory devices that store information. For example, the memory 330 includes computer program code causing the processor 320 to perform processing according to the methods described herein, e.g., the method of FIG. 5, 6, 7, and 8.

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

[0063] Other embodiments of the radio access node 120 or the network node 130 may include additional components beyond those shown in FIG. 2B that may be responsible for providing certain aspects of the node’s functionalities, including any of the functionalities described herein and / or any additional functionalities (including any functionality necessary to support the solutions described herein). The 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 partly or entirely different physical components.

[0064] Processors, interfaces, and memory similar to those described with respect to FIG. 2B may be included in other nodes (such as UE 110, radio access node 120, etc.). Other nodes may optionally include or not include a wireless interface (such as the transceiver described in FIG. 2B).

[0065] In some embodiments, the radio access node 120 or the network node 130 may comprise a series of modules configured to implement the functionalities of the radio access node 120 or the network node 130 described herein. Moreover, in some embodiments, the radio access node 120 or the network node 130 may also comprise means for the functionalities described herein.

[0066] It will be appreciated that the various modules may be implemented as combination of hardware and software, for instance, the processor, memory, and transceiver(s) of the radioaccess node 120 or the network node 130 shown in FIG. 2B. Some embodiments may also include additional modules to support additional and / or optional functionalities.

[0067] Before referring to FIGs. 4 to 10 and describing methods of dynamic on-demand SIB1 transmission mode handling according to the disclosure, some background information and aspects related to the subject disclosure will be provided. It should be noted that all concepts described herein, although described, e.g., for one communication direction, e.g., for downlink communication, are applicable for the other direction as well, e.g., in the uplink (UL) communication. Moreover, concepts described for one entity, e.g., a UE 110, are applicable to another entity, e.g., a base station or network node 120, when considering for example another communication direction or another network setting as will be apparent to the skilled person.

[0068] Network energy saving plays an important role in modem communication networks. One approach to save energy is directed to transmission or non-transmission of system information (SI), which is usually broadcasted periodically over an entire cell area to inform UEs about parameters of the network in a continuous manner. The main drawback of this periodic broadcasting is a low energy efficiency, in particular, if a cell is faced with a low load or with no load in the cell (i.e., there are few or no UEs to benefit from the transmitted SI). In the 3 GPP 5th generation (5G) / New Radio (NR) mobile communication system, transmission of system information of other SI than minimum SI may be omitted. Minimum SI relates to information of master information block (MIB) and system information block 1 (SIB 1). The information of SIB2 to SIB19, which carry non-essential SI, may, additionally or alternatively to broadcasting, be provided on demand. MIB and SIB1 are currently still broadcasted regularly in NR to carry basic information required for initial access of the UEs.

[0069] A further enhancement of NES could be to also provide SIB1 only on demand. However, since SIB1 is essential system information for communicating with a cell, the procedures for on-demand SIB2 to SIB 19 may not be applied. Further information flow may be required, such as providing the UE with on-demand SIB1 configuration information carrying information required to receive / request SIB1 information and / or interplay of two different cells.

[0070] Therefore, in some embodiments described herein, the on-demand SIB1 cell is a non-anchor cell (also denoted in this disclosure as capacity cell or CapCell or first cell), in which SIB1 is only provided on-demand. Another cell, namely, an anchor cell (also denoted in this disclosure as coverage cell or CovCell or second cell) is regularly broadcasting the anchor cell’s SIB1, as per legacy operations. Moreover, the UE may be considered to be in an idle or inactive mode (RRC IDLE, RRC IN ACTIVE) and camping on the anchor cell. The nonanchor cell refers to a cell that supports on-demand SIB or also denoted as SIBl-less function(without transmitting SIB1) apart from legacy SIB1 operation, where the SIB1 information of the non-anchor cell may be transmitted either via anchor cell or non-anchor cell according to different embodiments described herein. It is noted that also scenarios can be considered in which the UE is not camping on an anchor cell but it turned on and now aims at establishing data connection with the capacity cell. Therefore, an non-anchor cell or capacity cell is not to be considered limiting in the following disclosure and can be any cell that provides SIB1 information on demand.

[0071] In embodiments of the disclosure, the on-demand SIB1 transmission is triggered by a wake-up signal (WUS) or, more generally referred to as on-demand SIB1 request, from the UE, which may be similar to or different from the on-demand SIB request for other SIBs based on physical random access channel (PRACH) in legacy specifications, e.g., as defined in 3GPP TS 38.331 Release 17 or 18. The configuration information of the WUS / on-demand SIB1 request, of the WUS / on-demand SIB1 response and / or for receiving the SIB1 information is provided by the network (NW) to the UEs.

[0072] Regarding on-demand SIB1 transmission from gNBs to RRC IDLE / INACTIVE UEs, two deployment cases may generally be considered:• Case-A: Co-located anchor and non-anchor cell in the same gNB, where the information exchange between the two cells is via internal interface. The RUs of anchor and non-anchor cells are physically located.• Case-B: Non-co-located anchor and non-anchor cell in different gNBs, e.g., in gNB 120 A and gNB 120B as described with respect to FIG. 1, where the information exchange between the two cells is via a backhaul interface, i.e. an Xn interface. The RUs of anchor and non-anchor cells are physically non-located.

[0073] In the embodiments described herein, the UL on-demand SIB1 request, also called wake-up-signal (WUS), is considered to be received the non-anchor cell. Different scenarios are conceivable for message flow, which are shown in FIG. 3.

[0074] Scenario- 1 : The anchor cell 120-2 only handles the on-demand configuration to the RRC IDLE / RRC INACTIVE UEs, e.g., the information of on-demand SIB1 request configuration may be exchanged via backhauling beforehand for non-collocated case. And the non-anchor cell 120-1 may then handle the on-demand reception from the RRC IDLE / RRC INACTIVE UEs as well as the transmission of on-demand SIB1 by itself. This case requires the non-anchor cell 120-1 to monitor for on-demand SIB1 request / WUS reception, which increases the energy consumption for non-anchor cell 120-1 compared toscenarios 1 and 2. This case requires UE 110 switching between anchor cell 120-2 and nonanchor cell 120-1 for acquiring the on-demand SIB1.

[0075] Scenario-2: The operation of on-demand SIB1 is independent from the anchor cell 120-2. The non-anchor cell 120-1 may handle the on-demand SIB1 request configuration to the R.R.C IDLE / R.R.C IN ACTIVE UEs as well as the on-demand SIB1 request reception from the RRC IDLE / RRC INACTIVE UEs. In the meanwhile, the non-anchor cell 120-1 will also handle the delivery of on-demand SIB1 to the RRC IDLE / RRC INACTIVE UEs. This case requires a mechanism to point to UE 110 the on-demand SIB1 request / WUS. This case requires UE 110 switching between anchor cell 120-2 and non-anchor cell 120-1 for acquiring the on- demand SIB 1.

[0076] As explained above, there may be two options regarding transmission of WUS configuration.• Option 1 : The anchor cell transmits WUS configuration as in scenario- 1. Practically, it may be assumed that the anchor cell provides the IDLE mode functions for camping and initial access. The common signals / channels including synchronization signal block (SSB / SIB / paging / random access channel (RACH) may be transmitted to or received from the RRC IDLE / RRC INACTIVE UEs camping on this cell. Thus, the anchor cell may be used also to transmit the on- demand SIB1 WUS configuration to UE. The on-demand SIB1 request configuration may be added as part of system information, in MIB, SIB1, any of SIB 2 to SIB 19, or any other, possibly newly defined SIB of the anchor cell.• Option 2: The non-anchor cell transmits WUS configuration. As explained for scenario-2, the non-anchor cell may provide SSB transmission, as well as on- demand SIB1 transmission, by itself. In this case, the on-demand SIB1 WUS configuration must be delivered to the RRC IDLE / RRC INACTIVE UEs by the non-anchor cell itself.

[0077] Generally, in legacy operations, a first message for RRC IDLE / INACTIVE UEs to communicate with NW is sending of UL PRACH signal. In addition, in legacy operations for RRC IDLE / RRC INACTIVE UEs requesting the on-demand SIB(s) other than SIB1 information, it is also required for the RRC IDLE / RRC INACTIVE UEs to perform PRACH transmission as requesting indication to receive on-demand SIBs. To align with the legacy operation for on-demand SIB operation, PRACH may be used as on-demand SIB 1 request for triggering of on-demand SIB1 transmission for RRC IDLE / RRC INACTIVE UEs.

[0078] The UL on-demand SIB1 request is in the examples considered herein transmitted towards and received from the non-anchor cell. Practically, monitoring of on-demand SIB1 request may cause extra network energy consumption with network reception. But on the other hand, it allows the non-anchor cell to operate the on-demand SIB 1 request independently from the anchor cell, i.e., without the need of backhaul signaling back and forth. The on-demand SIB1 is also delivered to the RRC IDLE / RRC INACTIVE UE via the non-anchor cell as shown in scenarios-1 / 2 above.

[0079] The on-demand SIB1 request may use an existing channel, e.g., the PRACH for transmitting a Random Access (RA) preamble. Thus, the legacy PRACH preambles may be used as WUS. For energy-saving purposes, the disclosure herein relates to how the UE can continue the same RA procedure initiated to request SIB1 transmission after it has acquired the SIB 1, i.e., without having to initiate a new RA procedure to request UL / DL data transmission and / or transition to RRC CONNECTED mode.

[0080] Currently, a RA procedure (4-message or 2-message) has a single purpose, such as to request on-demand SIBs (SIB2 to SIB 19) or to initiate RRC connection resume or setup to transmit UL / DL data. Therefore, the UE would have in principle to perform two independent RA procedures if it requires the on-demand SIB1 information and a data connection with the cell, namely, one for requesting SIB1 transmission and subsequently one for requesting RRC connection resume or setup after having acquired SIB1.

[0081] The inventors have identified a procedure to overcome this issue so that the UE, after transmitting the on-demand SIB1 request (using a PRACH preamble) to the network for the SIB1 transmission from the network, can continue the same RA procedure. Thus, the same RA procedure can be used for SIB1 requesting and RRC connection setup / resume instead of initiating a new RA procedure after the SIB1 acquisition. Furthermore, the UE may indicate different purposes, e.g., whether it intends to continue the RA to setup a RRC connection, to perform SDT procedure, or to camp on the cell after acquiring the SIB 1.

[0082] It is assumed that the UE receives a WUS / PRACH configuration defining how to transmit the RA preamble to trigger the SIB1 transmission. Hence, the UE knows which preambles and / or which transmission resources (in time / frequency) of the PRACH indicate which purpose the RA procedure is intended to have. The UE transmits to a capacity cell a WUS / PRACH preamble to request on-demand SIB1 transmission. The on-demand SIB1 request may be based on the PRACH preamble and PRACH resources according to the WUS / PRACH configuration as indicated before.

[0083] In one embodiment, the UE indicates whether it intends to acquire the SIB1 to setup / resume a RRC connection, to perform an SDT procedure, or to camp on the cell (i.e. UE remains in RRC Idle / Inactive state). If the UE intends to setup / resume the RRC connection or perform SDT, the network will schedule the random access response (RAR, MSG2) and an uplink random access message (MSG3) to allow the legacy RA procedure to continue, while, if the UE is indicating it will camp on the cell, the network will only respond with an indication of how SIB1 can be acquired / is scheduled after which the ongoing RA procedure will be cancelled / stopped (i.e., no MSG3 or MSG4). The indication of which purpose is intended may be made using a subset of the RA preambles or in specific time- and / or frequency-domain resources.

[0084] The network may configure the UE with information for transmitting the on- demand SIB1 request. Information for transmitting the on-demand SIB1 request may include an indication related to a preamble group or set usable to select a preamble for the on-demand SIB1 request. The preamble group or set for requesting SIB1 may be different from a preamble group or set useable to select a preamble for a SIB2 to SIB 19 request as known in the art. Moreover, the preamble group or set for requesting SIB1 and requesting data communication with the cell may be another different preamble group. For example, in current 3GPP TS 38.321 specification (e.g., Release 17 or 18), an information element ra-PreambleStartlndex is defined for indicating the start index of preambles for requesting SIB2 to SIB 19. For further indicating the start index of preambles for requesting SIB1, two information elements ra- PreambleStartlndexl and ra-PreambleStartIndex2 may be defined for requesting SIB2 to SIB 19 and SIB1, respectively. Finally, a third (or fourth, fifth, et.c) information element ra- PreambleStartIndex3 may define the start index of preambles for requesting SIB1 and requesting data communication with the cell, e.g., requesting (re-)establi shing of RRC connection or a small data transmission (SDT).

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

[0086] When the UE has transmitted the MSG3 of the 4-message RA procedure, the RA procedure may continue according to legacy specification.

[0087] In an embodiment, the UE does not indicate in the random access message (MSG1) that it requests on-demand SIB1 but only that it requests data connection with the cell. In this example, the UE may indicate in MSG3 whether it requests on-demand SIB1. This is, e.g., useful if the UE was connected with the cell a short while ago and acquired a SIB1, which is still valid. Furthermore, the MSG3 may then also indicate whether the UE (really) intends to setup / resume the RRC connection. If that is the case, the procedure continues similar to the legacy with MSG4 transmission - the SIB1 may be scheduled before / after the MSG4.

[0088] Likewise, if 2-message RA procedure is configured, the UE may indicate whether it requests SIB1 in the PRACH or as part of the PUSCH data of the random access message (MSGA). The network can then schedule SIB1 before / after the response message (MSGB) and also take into account whether the UE wants to setup / resume the RRC connection or to camp on the cell.

[0089] The herein described methods and systems enable the UE to request the on-demand SIB1 transmission from a capacity cell while at the same time facilitating to setup / resume a RRC connection by the UE. The herein described procedures enables the reuse of the RA procedure while at the same time facilitating SIB1 transmission when needed.

[0090] FIG. 4 now presents a flow chart of a method performed by a user equipment according to the disclosure for enabling dual purpose RA procedures. The user equipment (UE) (such as UE 110 of Figs, 1, 2A, and 3) is in radio resource control, RRC, idle or inactive mode and performs a random access procedure with a cell operating in an on-demand system information block 1, SIB1, mode. In box 410, the UE transmits a random access message towards the cell. The cell is a capacity cell 120-1 (e.g., of gNB 120A or 120B of Fig. 1) and operates in on-demand SIB1 mode. The random access message indicates a dual use purpose including a request for on-demand SIB1 information from the cell and a request for data communicationcommunication with the cell.

[0091] Data communication in the sense of this disclosure may include, e.g., establishing a data connection, which includes transitioning from RRC IDLE state to RRC CONNECTED state, resuming a data connection, which includes transitioning from RRC INACTIVE state toRRC CONNECTED state, and / or requesting a small data transmission, which includes staying in RRC INACTIVE state.

[0092] In response to transmitting the random access message, the UE receives scheduling indication of the requested on-demand SIB1 information. This is shown in box 420. The scheduling indication of the on-demand SIB1 information may be comprised by a response message from the cell. Moreover, the UE receives data communication configuration information for enabling data communication with the cell in box 430. Such data communication information may be a scheduling of MSG3 in a 4-message RA procedure and / or further configuration data required for data connection with the cell, e.g., identifiers for the UE (RA-RNTI, C-RNTI, etc.), timing advance indication, and the like.

[0093] In box 440, the UE then receives the SIB1 information according to the scheduling indication of the SIB1 information. In box 450, the UE performs data communication with the cell according to the data communication configuration information, e.g., , e.g. receives MSG3, receives or transmits further messages to the cell, and the like.

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

[0095] In some further embodiments, an indication of a time window for receiving the another response message from the cell is received with the (first) response message, is received with on-demand SIB1 configuration information, and / or is pre-defined. The time window of the first response message is usually pre-configured in technical specifications but may also be received in broadcasting information, such as MIB. The configuration of the time window for the receiving the another (i.e., second) response message may ensure that the UE has enough time to receive the SIB 1.

[0096] In alternative embodiments, the data communication configuration information is comprised by the response message, i.e., only one random access response is transmitted in response to the random access message. This one random access response carries the data communication configuration information and the SIB 1 scheduling indication. It is noted that SIB1 scheduling information may also be indicated in on-demand SIB1 configurationinformation and the response message is only an indication that the SIB1 is now scheduled (according to the scheduling information received in the SIB configuration information).

[0097] In some embodiments, the UE may receive preamble configuration information from the cell, wherein the preamble configuration information indicates one or more preamble indexes, one or more transmission resources, or a combination thereof indicating the dual use purpose. The preamble configuration information may be transmitted in MIB or other broadcasted information of the cell. The UE may, additionally or alternatively, select a random access preamble for transmission with the random access message and / or transmission resources for transmitting the random access message to indicate dual use purpose with the random access message. Hence, some preambles may be dedicated to indicate dual use purpose, some time / frequency resources of PRACH may be dedicated to indicate dual use purpose, or a combination of specific preambles sent on specific time / frequency resource may indicate dual use purpose.

[0098] In embodiments, in which the random access procedure is a four message random access procedure, the data communication configuration information may comprise uplink scheduling information for an uplink random access message (i.e., MSG3). In embodiments, in which the random access procedure is a two message random access procedure, the random access message may indicate dual use purpose by adding a SIB1 request in a data part of the random access message (i.e., MSGA). Hence, in two message random access procedures, the dual use purpose may be indicated by the selected preamble, the selected transmission resources, and / or an indication in the UL data part of MSGA.

[0099] FIG. 5 presents a flow chart of a method performed by a network entity according to the disclosure for enabling dual purpose RA procedures. The network entity (e.g., gNB 120A or 120B of Fig. 1) supports a random access procedure of a cell (e.g., capacity cell 120-1) with a user equipment, UE (such as UE 110 of Figs. 1, 2A, and 3), in radio resource control, RRC, idle or inactive mode, wherein the cell operates in an on-demand SIB1 mode.

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

[0101] In response to transmitting the random access message, the network entity transmits scheduling indication of the requested on-demand SIB1 information. This is shown in box 520. The scheduling indication of the on-demand SIB1 information may be comprised by a response message from the cell. Moreover, the network entity transmits data communication configuration information for enabling data communication with the cell in box 530. Such datacommunication information may be a scheduling of MSG3 in a 4-message RA procedure and / or further configuration data required for data connection with the cell, e.g., identifiers for the UE (RA-RNTI, C-RNTI, etc.), timing advance indication, and the like.

[0102] In box 540, the network entity transmits the SIB1 information according to the scheduling indication of the SIB1 information. In box 550, the network entity performs data communication with the UE according to the data communication configuration information, e.g., , e.g. transmits MSG3, receives or transmits further messages to the UE, and the like.

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

[0104] In some further embodiments, an indication of a time window for transmitting the another response message is transmitted with the (first) response message, is transmitted with on-demand SIB1 configuration information, and / or is pre-defined. The time window of the first response message is usually pre-configured in technical specifications but may also be received in broadcasting information, such as MIB. The configuration of the time window for the receiving the another (i.e., second) random access message may ensure that the UE has enough time to receive the SIB 1.

[0105] In alternative embodiments, the data communication configuration information is comprised by the response message, i.e., only one random access response is transmitted in response to the random access message. This one random access response carries the data communication configuration information and the SIB 1 scheduling indication. It is noted that SIB1 scheduling information may also be indicated in on-demand SIB1 configuration information and the response message is only an indication that the SIB1 is now scheduled (according to the scheduling information transmitted in the SIB configuration information).

[0106] In some embodiments, the network entity may transmit preamble configuration information, wherein the preamble configuration information indicates one or more preamble indexes, one or more transmission resources, or a combination thereof indicating the dual use purpose. The preamble configuration information may be transmitted in MIB or other broadcasted information of the cell. The network entity may, additionally or alternatively, determine the indication of dual use purpose according to a selected a random access preamblefor transmission with the random access message and / or transmission resources for transmitting the random access message may select a random access preamble for transmission with the random access message and / or transmission resources for transmitting the random access message to indicate dual use purpose with the random access message. Hence, some preambles may be dedicated to indicate dual use purpose, some time / frequency resources of PRACH may be dedicated to indicate dual use purpose, or a combination of specific preambles sent on specific time / frequency resource may indicate dual use purpose.

[0107] In embodiments, in which the random access procedure is a four message random access procedure, the data communication configuration information may comprise uplink scheduling information for an uplink random access message (i.e., MSG3). In embodiments, in which the random access procedure is a two message random access procedure, the random access message may indicate dual use purpose by adding a SIB1 request in a data part of the random access message (i.e., MSGA). Hence, in two message random access procedures, the dual use purpose may be indicated by the selected preamble, the selected transmission resources, and / or an indication in the UL data part of MSGA.

[0108] FIG. 6 shows a message flow diagram of efficient SIB1 request and data connection establishment according to an embodiment. The UE 110 transmits a random access message to the gNB 120 (e.g., via a capacity cell 120-1 of the gNB 120) as depicted with arrow 601. This random access message is in this example a MSG1 of a four message RA procedure. The random access message also carries indication of dual use purpose of this RA procedure, i.e., it indicates that the UE 110 requires on-demand SIB1 and data connection with the gNB 120.

[0109] The UE 110 then monitors for receiving the random access response from the gNB 110 and, thus, receives the random access response as shown with arrow 602. The random access response is in this example a MSG2 (RAR) in the RA procedure. The (first) time window and / or resources for monitoring and receiving this first random access response may be predefined in technical specifications and / or broadcasted by the cell 120-1 of the gNB 120. In this example, the first random access response comprises a SIB1 scheduling indication and a second random access window. This second random access window defines when the UE 110 will receive a second response message.

[0110] The UE 110 first receives the SIB1 information according to the SIB1 scheduling indication as depicted with arrow 603 and waits for the start of the second time window to start monitoring for receiving the second response message, which is shown with arrow 604. In this second response message carries a scheduling DCI for MSG3, i.e., data communication configuration information, such as time / frequency resources when the UE 110 may transmitMSG3 and a random access identifier (RA-RNTI) of the UE 110. Thereafter, the method proceeds as in legacy with transmitting MSG3 and MSG4 and finalizing the RA procedure in order to enable data connection with the cell 120-1 of the gNB 120.[OHl] FIG. 7 shows a message flow diagram of efficient SIB1 request and data connection establishment according to another embodiment. The UE 110 also transmits a random access message to the gNB 120 (e.g., via a capacity cell 120-1 of the gNB 120) as depicted with arrow 701. This random access message is in this example a MSG1 of a four message RA procedure. The random access message also carries indication of dual use purpose of this RA procedure, i.e., it indicates that the UE 110 requires on-demand SIB1 and data connection with the gNB 120.

[0112] The UE 110 then monitors for receiving the random access response from the gNB 110 and, thus, receives the random access response as shown with arrow 702. The random access response is in this example a MSG2 (RAR) in the RA procedure. The time window and / or resources for monitoring and receiving this random access response may be pre-defined in technical specifications and / or broadcasted by the cell 120-1 of the gNB 120.

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

[0114] The UE 110 then receives the SIB1 information according to the SIB1 scheduling indication as depicted with arrow 703. Thereafter, the method proceeds as in legacy with transmitting MSG3 and MSG4 and finalizing the RA procedure in order to enable data connection with the cell 120-1 of the gNB 120. Although FIG. 6 and FIG. 7 depict message flows for four message RA procedures, the same concept also applies for two message RA procedures as explained above.

[0115] FIG. 8 is a detailed overview on possible alternative or additional processes performed according to the disclosure. All processes start with the UE indicating a cause for SIB1 request (box 800), i.e., a cause for transmitting the MSG1 in a RA procedure. If the UE indicates that is has data to transmit (box 801), the UE starts to monitor for a DCI to schedule the random access response, i.e., the RAR (box 802). The UE receives the RAR. In one example, the RAR may include on-demand SIB1 scheduling information, which also serves as SIB1 scheduling indication (box 803). The scheduling information may be an indication of a search space for receiving SIB1. In this example, the UE directly knows how to acquire SIB1 and does not need further information.

[0116] In another embodiment, the RAR may include only an acknowledgement, which serves as SIB1 scheduling indication (box 804). The RAR may, thus, indicate to the UE that it shall monitor for SIB scheduling information (box 805). Scheduling information may be comprised by a SIB1 request configuration, e.g., in on-demand SIB1 configuration information (box 806) or by MIB (box 807). In all cases, the UE has obtained SIB1 scheduling information and can acquire SIB1 accordingly (box 808).

[0117] The UE then further needs to obtain MSG3 to enable data communication with the cell. For receiving scheduling information of MSG3, there also exist different options (box 809). The UE may be instructed to monitor for scheduling DCI in the physical downlink control channel (PDCCH) in a time window located after reception of SIB1 (box 810). The PDCCH monitoring configuration may be indicated to the UE in the RAR (box 811), in the SIB1 information (box 812), in the SIB1 request configuration, e.g., on-demand SIB1 configuration information (box 813), and / or pre-defined in technical specifications, i.e., standardized (box 814).

[0118] The UE may alternatively also receive a direct UL grant (box 815). The UL grant may be part of RAR, e.g., defining a time offset like K2 of NR (box 816), may be configured via SIB1 information (box 817), and / or pre-defined in technical specifications, i.e., standardized (box 818). In all cases, the UE then has the scheduling information for MSG3 and can transmit MSG3, i.e., continues with the RA procedure as usual for (re-)establi shing data connection with the cell (box 819).

[0119] Exemplary implemenations regarding UL grant are described in the following, e.g. partly related to boxes 815, 816, 817, 818, 819:A method performed by a user equipment, UE, is provided, in which the UE is in 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. In this operation state the UE is receiving a configuration for an on-demand SIB1 request including information related to at least one preconfigured physical random access channel, PRACH, occasion and at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message. The pre-assignment or pre-reservation of both PRACH And PUSCH resources has the advantage that in case the UE has uplink (UL) data to send, it can use the preconfigured resources to more quickly transmit the UL data as no two consecutive RACH procedures, one for acquiring SIB1 info, and another for accessing the cell, need to be performed. The UE is thus enabled totransmit a random access message towards the cell using at least one of the preconfigured PRACH occasions, wherein the random access message indicates a dual use 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: the UE is receiving a response message from the cell comprising scheduling indication of the requested on-demand SIB1 information; and receiving the SIB1 information according to the scheduling indication of the SIB 1 information; and further transmitting an RRC message using at least one of the preconfigured PUSCH resources.The RRC message may include a request for data communication, wherein the request for data communication is related to at least one of: RRC Setup request, RRC Resume request, uplink data. In this way various connections are supported in a single step using preconfigured UL grant(s) (PUSCH resource(s)).The scheduling indication of the requested on-demand SIB 1 information may indicate the start of the SIB1 transmission. The start indication may be an acknowledgement (ACK) signal indicating that the network received the preamble and will start SIB1 transmission, or indicating a start time for the transmission of the SIB, or else. The ACK signal is thus a kind of dual use message indicating that the preamble has been received. Thus, the UE does not need to resend it. And, in addition, the UE is informed that SIB1 transmission starts and thus UE is subsequently monitoring the reception of SIB1. This way amount of signaling is reduced. The scheduling indication of the requested on-demand SIB 1 information may indicate a resource of the SIB1 transmission. The resource indication may be related to one or more Physical Resource Blocks (PRBs) and / or symbols, e.g. time & frequency resources, which are used for the transmission of the SIB1 information.The information related to the at least one preconfigured PUSCH resource may comprises a configured grant configuration. This is a direct indication to a specific timeslot the UE is enabled to use for e.g. UL data. The information related to the at least one preconfigured PUSCH resource may comprise a PUSCH resource offset in time, wherein the offset is relative to one of the PRACH occasion or the response message. This is an indirect indication of a specific timeslot the UE is enabled to use. This may require less signaling. And offers the opportunity to eventually dynamically vary or adjust the time offset between PRACH and PUSCH and thus the time delay between the PRACH signal and the UL data transfer to allow e.g. enough processing time in between, e.g. for receiving and processing the SIB1 info, and on the other side to reduce the time delay for transmitting the UL data.Alternatively to e.g. transmitting the PUSCH resources together with the PRACH resources, the PUSCH resource indication may also be included in the SIB1 info, e.g. the UE is receiving the SIB1 information according to the scheduling indication of the SIB1 information, wherein the SIB1 information includes at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message. In this case there is no pre-coordination between PUSCH and PRACH required, but may still be used, e.g. PUSCH indication may be direct or indirect similar to the above. In both cases the UE is not required to first acquire the SIB1 info and afterwards monitor for a DCI with UL grant info. This reduces the time for starting the transmission of the UL data.Appropriate steps are performed on the network side to enable the UE to perform the operations according to the above implementations.

[0120] The UE may alternatively also indicate that no data connection is required and that is only wants to camp on the cell (box 820). Then, a reduced RA procedure is applied which ends with transmission of RAR, wherein the MAC header of the RAR indicates acknowledgement of the SIB1 request (box 821). SIB1 scheduling information may be comprised by a SIB1 request configuration, e.g., in on-demand SIB1 configuration information or by MIB (box 822). At the end, the UE has obtained SIB1 scheduling information and can acquire SIB1 accordingly. The RA procedure then finishes.

[0121] The herein described procedures may be applied per model or per functionality level (identified by an identifier) or across models or functionalities of a given entity, e.g., as a UE feature. It should be understood that the apparatuses described herein may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and / or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.

[0122] It is noted that whilst embodiments have been described in relation to LTE and 5G NR, similar principles may be applied in relation to other networks and communication systems where enforcing fast connection re-establishment is required. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

[0123] It is also noted herein that while the above describes exemplary embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the subject disclosure.

[0124] In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the subject disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the subject disclosure is not limited thereto. While various aspects of the subject disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0125] Example embodiments of the subject disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computerexecutable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.

[0126] Further in this regard it should be noted that any blocks of the logic flow as in the figures may represent program processes, or interconnected logic circuits, blocks and functions, or a combination of program processes and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.

[0127] The memory may be of any type suitable to the local technical environment and may 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. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), FPGA, gate level circuits and processors based on multicore processor architecture, as non-limiting examples.

[0128] Example embodiments of the subject disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0129] The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of the subject disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of the subject disclosure as defined in the appended claims. Indeed, there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed.

Claims

Claims:

1. A method performed by a user equipment, UE, in 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, comprising:- receiving a configuration for an on-demand SIB 1 request including information related to at least one preconfigured physical random access channel, PRACH, occasion and at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message,- transmitting a random access message towards the cell using at least one of the preconfigured PRACH occasions, wherein the random access message indicates a dual use 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:- receiving a response message from the cell comprising scheduling indication of the requested on-demand SIB1 information; and- receiving the SIB1 information according to the scheduling indication of the SIB1 information; and transmitting an RRC message using at least one of the preconfigured PUSCH resources.

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: RRC Setup request, RRC Resume request, uplink data, downlink data.

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

4. The method of claim 1, wherein the information related to the at least one preconfigured PUSCH resource comprises a configured grant configuration.

5. The method of claim 1, wherein the information related to the at least one preconfigured PUSCH resource comprises a PUSCH resource offset in time, wherein the offset is relative to one of the PRACH occasion or the response message.

6. The method of claim 1, further comprising:- receiving preamble configuration information from the cell, wherein the preamble configuration information indicates one or more preamble indexes, one or more transmission resources, or a combination thereof indicating the dual use purpose.

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

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

9. The method of 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 dual use purpose by adding a SIB 1 request indication in a data part of the random access message.

10. A method performed by a network entity for supporting a random access procedure of a cell with a user equipment, UE, in radio resource control, RRC, idle or inactive mode, wherein the cell operates in an on-demand SIB1 mode, comprising:- transmitting, towards the UE, a configuration for an on-demand SIB 1 request including information related to at least one preconfigured physical random access channel, PRACH, occasion and at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message,- receiving, from the UE, a random access message on one of the preconfigured PRACH occasions, wherein the random access message indicates a dual use 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:- transmitting a response message to the UE comprising scheduling indication of the requested on-demand SIB 1 information; and- transmitting, towards the UE, the SIB1 information according to the scheduling indication of the SIB1 information; and- receiving, from the UE, an RRC message on at least one of the preconfigured PUSCH resources.

11. A user equipment, UE, configured to support operating in 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, and configured to perform the method steps of claim 1.

12. An apparatus of a network entity for supporting a random access procedure of a cell with a user equipment, UE, in radio resource control, RRC, idle or inactive mode, wherein the cell operates in an on-demand SIB 1 mode, configured to perform the method steps of claim 10.

13. A method performed by a user equipment, UE, in 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, comprising:- transmitting a random access message towards the cell, wherein the random access message indicates a dual use 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:- receiving a response message from the cell comprising scheduling indication of the requested on-demand SIB 1 information; and- receiving the SIB1 information according to the scheduling indication of the SIB1 information, wherein the SIB 1 information includes at least one preconfigured physical uplink shared channel, PUSCH, resource for transmitting an RRC message; andtransmitting an RRC message using at least one of the preconfigured PUSCH resources.

14. The method of claim 13, further comprising: - receiving a configuration for an on-demand SIB 1 request including information related to at least one preconfigured physical random access channel, PRACH, occasion,- transmitting the random access message towards the cell using at least one of the preconfigured PRACH occasions, wherein the random access message indicates a dual use 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 operating in 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, and configured to perform the method steps of claim 13.

Images