User equipment (UE), network node and methods for providing system information

Abstract

Example embodiments of the present disclosure relate to a user equipment (UE), a network node and a method for providing system information. Embodiments herein disclose a user equipment (UE) (110), a network node (120) and a method. The method comprises: receiving, from a second apparatus (120), a message comprising a contention resolution message, the contention resolution message comprising an offset value for a decoding window for the first apparatus (110); and estimating, based on the information received in the contention resolution message and a starting slot index for a system information (SI) window, an arrival time of a requested on-demand system information block (SIB), the on-demand SIB being transmitted by the second apparatus (120) during the system information (SI) window.

Description

Technical Field

[0001] The exemplary embodiments of this disclosure relate to the field of wireless communication, and more specifically to user equipment (UE), network nodes, and methods for providing system information. Background Technology

[0002] Some abbreviations that can be found in the instruction manual and / or accompanying drawings are defined here as follows.

[0003] MAC Media Access Control MAC-CE MAC control element MIB (Master Information Block) PosSI Positioning SI SIB System Information Block SI System Information SI-WindowNumSI window number SI-WindowStarSI window start time In 5G wireless communication systems, certain System Information Blocks (SIBs) are not broadcast periodically, but are provided on demand in response to specific requests from User Equipment (UE). To acquire these on-demand SIBs, the UE can initiate a Contention-Based Random Access (CBRA) procedure and subsequently continuously monitor and decode the Physical Downlink Shared Channel (PDSCH) across the entire SI window, starting from the beginning of the SI window. Since the actual arrival time of the requested SIB is unknown, this can lead to blind decoding across multiple SI windows, significantly increasing the UE's power consumption. Summary of the Invention

[0004] The following describes aspects relating to the exemplary embodiments disclosed herein. It should be understood that these aspects are not intended to limit the scope of this disclosure. In fact, this disclosure may cover aspects that may not be set forth below.

[0005] In a first aspect of this disclosure, a first apparatus is disclosed. The first apparatus includes at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the first apparatus to at least: receive from a second apparatus a message including a contention resolution message, the contention resolution message including an offset value for a decoding window for the first apparatus; and estimate the arrival time of a requested on-demand system information block (SIB) based on information received in the contention resolution message and a start slot index for a system information (SI) window, during which the on-demand SIB is transmitted by the second apparatus.

[0006] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the second apparatus to at least: transmit a message including a contention resolution message to at least one first apparatus, the contention resolution message including an offset value for a decoding window for the first apparatus. Information received in the contention resolution message is used to estimate the arrival time of a requested on-demand System Information Block (SIB) and a start time slot index for a System Information (SI) window during which the on-demand SIB is transmitted by the second apparatus.

[0007] In a third aspect of this disclosure, a method for a first apparatus is provided. The method includes: receiving from a second apparatus a message including a contention resolution message, the contention resolution message including an offset value for a decoding window for the first apparatus; and estimating the arrival time of a requested on-demand system information block (SIB) based on information received in the contention resolution message and a start slot index for a system information (SI) window, during which the on-demand SIB is transmitted by the second apparatus.

[0008] In a fourth aspect of this disclosure, a method for a second apparatus is provided. The method includes transmitting to at least one first apparatus a message including a contention resolution message, the contention resolution message including an offset value for a decoding window for the first apparatus. Information received in the contention resolution message is used to estimate the arrival time of a requested on-demand System Information Block (SIB) and the start slot index of a System Information (SI) window during which the on-demand SIB is transmitted by the second apparatus.

[0009] In a fifth aspect, a first device is provided. The first device includes components for causing the first device to perform the method of the third aspect.

[0010] In a sixth aspect, a second apparatus is provided. The second apparatus includes components for performing the method of the fourth aspect.

[0011] The components for the fifth and sixth aspects can be implemented in hardware and / or software. They include, for example, at least one processor for executing computer program code / instructions for causing the corresponding device (e.g., UE or network node) to perform the corresponding method, and at least one memory for storing the computer program code / instructions. The component may also include circuitry (as defined herein) for causing the corresponding device to perform the corresponding method.

[0012] According to the seventh aspect, a computer-readable medium (e.g., a non-transitory computer-readable medium) is provided. The computer-readable medium includes instructions that, when executed by a UE, cause the UE to perform the method of the third aspect.

[0013] According to the eighth aspect, a computer-readable medium (e.g., a non-transitory computer-readable medium) is provided. The computer-readable medium includes instructions that, when executed by a network node, cause the network node to perform the method of the fourth aspect.

[0014] Details of exemplary embodiments are set forth in the accompanying drawings and the following description. Other features, objects, and advantages of this disclosure will be apparent from the specification, drawings, and claims. Attached Figure Description

[0015] The specific embodiments are described with reference to the accompanying drawings. The same numerals are used throughout the drawings to refer to the same features and components.

[0016] Figure 1 A wireless communication system in which example embodiments of the present disclosure may be implemented is shown; Figure 2 A conventional signaling diagram for user equipment (UE) and network nodes is shown for the System Information Block (SIB) procedure. Figure 3 This illustrates the traditional timescale of the on-demand SIB process; Figure 4 A method performed by a first device according to an example embodiment of the present disclosure is shown; Figure 5 A method performed by a first device according to an example embodiment of the present disclosure is shown; Figure 6 A method performed by a second apparatus according to an example embodiment of the present disclosure is shown; Figure 7 A method performed by a second apparatus according to an example embodiment of the present disclosure is shown; Figure 8 A first signaling diagram for a first device and a second device according to an example embodiment of the present disclosure is shown; Figure 9 A second signaling diagram for a first device and a second device according to an example embodiment of the present disclosure is shown; Figure 10 The on-demand SIB process timescale is shown according to an example embodiment of this disclosure; Figure 11 A block diagram of a first apparatus according to an exemplary embodiment of the present disclosure is shown; and Figure 12 A block diagram of a second apparatus according to an exemplary embodiment of the present disclosure is shown. Detailed Implementation

[0017] Example embodiments will now be described with reference to the accompanying drawings. The terminology used in this disclosure of the example embodiments shown in the drawings is not intended to be limiting. In the drawings, the same numerals denote the same elements.

[0018] It should be understood that although the terms "first," "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0019] This specification may refer to "a," "an," or "some" (or more) embodiments in several places. This does not necessarily mean that each such reference is for the same (or more) embodiments, or that the feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments.

[0020] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless otherwise expressly stated. It will also be understood that, when used in this specification, the terms “comprising” and / or “including” specify the presence of the stated feature, integer, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0021] As used herein, whenever the phrase “at least one” or “one or more” precedes a list of elements connected by “and” or “or”, it means that at least any one of the elements, or at least some of the elements, or all of the elements are present. Whenever the phrase “one” precedes a list of elements connected by “and” or “or”, it means that only one of the elements is present at a given moment, unless the context allows for the inclusion of more than one element. Unless the relevant context otherwise indicates, the use of the term “or” should be understood as “inclusive or” rather than “exclusive or”. Unless otherwise specifically stated, or otherwise understood in the context in which it is used, conditional language, such as “may” or “can”, is generally intended to convey that certain embodiments may include certain features, elements, and / or steps, while other embodiments may not. Therefore, such conditional language is generally not intended to imply that one or more embodiments require features, elements, and / or steps in any way. It should be understood that when an element is referred to as “connected” or “coupled” to another element, it may be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, as used herein, “connected” or “coupled” can include wireless connections or couplings. As used herein, the term “and / or” includes any and all combinations and arrangements of one or more of the associated listed items. As used herein, the terms “at least one” and “one or more” mean “any one of at least one” and “any one of one or more”, respectively.

[0022] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will also be understood that terms such as those defined in common dictionaries shall be interpreted as having a meaning consistent with their meaning in the context of the relevant field, and shall not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0023] The accompanying drawings depict a simplified structure showing only some elements and functional entities; all of these can be implemented in ways different from the different logical units shown. The connections shown are logical connections; actual physical connections may differ. Furthermore, all logical units described and depicted in the drawings include the software and / or hardware components required for the unit's operation. Additionally, each unit itself may include one or more components, as implicitly understood. These components may be operatively coupled to each other and configured to communicate with each other to perform the unit's functions.

[0024] As used herein, the term "circuit" may refer to at least one of the following: a) Hardware circuit implementation only (such as implementations in analog, digital and / or quantum circuits); b) A combination of (multiple) hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog, digital, and / or quantum hardware circuits with software / firmware, and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) having software and (multiple) memories that work together to enable a device such as a mobile device, computing device, or server to perform various functions; or c) Any or all parts of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors and / or (multiple) quantum processors, that require software (e.g., firmware) to operate, but may not exist when the software is not required to operate.

[0025] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers implementations of hardware circuitry or processors (or processors in general) and their accompanying software and / or firmware. The term "circuit" also covers, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0026] However, in the following text, different example embodiments will be described using communication network architectures based on 3GPP standards for communication networks (such as 5G NR or 6G (sixth generation)) as examples of communication networks to which example embodiments can be applied, without limiting the example embodiments to such architectures.

[0027] Figure 1 An example of a wireless communication network 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The network 100 may include at least a first device 110 and a second device 120 (the first device 110 is also referred to as a terminal device, and the second device 120 is also referred to as a network device).

[0028] In some example embodiments, the first device 110 may include a user equipment (UE) and may be any wireless communication device capable of transmitting and receiving radio signals. The first device 110 may be used to communicate with a radio access network (RAN) via an uplink channel. Non-limiting examples of the first device 110 include smartphones, tablets, laptops, etc. The first device 110 may include and / or be referred to as a "terminal device," "user equipment," "wireless transmit / receive unit," or another name.

[0029] In some example embodiments, the second device 120 may include a network node in a communication network (e.g., network 100) through which the first device 110 can access the network and receive services. The second device 120 may include and / or be referred to as a “base station,” “radio access network node,” “radio unit,” or another name. The second device 120 may operate according to one of several radio access technologies (RATs) in communication with the first device 110 and may be part of a RAN. The second device 120 may communicate with the first device 110 via a downlink channel.

[0030] In the wireless communication network 100, there may be radio coverage areas (referred to as "cells"). Cell 130 may be supported by the second device 120.

[0031] There may be a situation where the first device 110 initiates beam management, wherein the first device 110 may be configured with at least one event / condition, and if the at least one event / condition occurs or is met, the first device 110 may start beam reporting.

[0032] Figure 2 Signaling diagram 200 for first device 110 and second device 120 is shown, illustrating the conventional process for obtaining on-demand SIBs.

[0033] In step 201, the second device 120 is configured to always broadcast the minimum SIB (i.e., MIB), and in step 202, the second device forcibly broadcasts the remaining minimum SIBs (i.e., SIBs). SIB1->SI scheduling information (SI-SchedulingInfo) and SI request configuration (SI-RequestConfig) provide the first device 110 with the necessary configuration for on-demand SIB acquisition. The first device 110 uses the CBRA procedure to acquire the required SIB(s) not broadcast by the second device 120.

[0034] Step 203 illustrates the CBRA RACH process for obtaining on-demand SIBs, briefly explained below: At step 204, the first device 110 sends message 1 (Msg1) (preamble) to the second device 120 via PRACH and waits for RAR (response) in (multiple) random access response (RAR) windows.

[0035] In step 205, the first device 110 receives a RAR with allocated TA, PwrCtl steps and PUSCH resources to send Msg3.

[0036] In step 206, the first device 110 sends a Msg3 RRC System Info Request (rrcSystemInfoRequest) with the required (on-demand) SIB details on the allocated PUSCH resource.

[0037] In step 207, the first device 110 receives the contention resolution MAC CE within a specified window and begins decoding the PDSCH scrambled using SI-RNTI at an appropriate SI window length / slot.

[0038] In step 208, it is shown that the first device 110 begins decoding the PDSCH using SI-RNTI after receiving the contention resolution MAC CE (step 207).

[0039] In step 209, the first device 110 receives (multiple) SIBs within (multiple) SI window lengths. If the first device does not receive any SIBs, the first device 110 may repeat the process according to the configuration provided by the second device 120.

[0040] Figure 3 The conventional SI process timescale 300 is shown when the first device 110 can receive on-demand SIBs. t1 to t4 illustrate the CBRA based on the on-demand SIB process: In phase 302, at t1: the first device 110 may send CBRA-Msg1 (preamble) to the second device 120.

[0041] At t2: The first device 110 can receive CBRA-Msg2 (RAR) from the second device. The RAR contains PUSCH authorization and other information.

[0042] At t3: The first device can send CBRA-Msg3 (rrcSystemInfoRequest) to the first device via the authorized PUSCH.

[0043] At t4: the second device 120 can send CBRA-Msg4 (contention resolution MAC-CE).

[0044] The first device 110 can calculate the SI window start time slot, ts1 (based on the information provided in SIB1->SI-SchedulingInfo->SI-RequestConfig), and decode the PDSCH scrambled with SI-RNTI starting from the start time of the first SI window, as shown in stage 304.

[0045] The first device can start from the SI window start time slot ts1 and continuously search for PDSCH using SI-RNTI until the SI window length ends. SI-WindowLength is an enumeration type {s5, s10, s20, s40, s80, s160, s320, s640, s1280, s2560-v1710, s5120-v1710}, that is, s5=5 time slots, s10=10 time slots, etc. (TS38.331 IESI-SchedulingInfo).

[0046] After receiving the contention resolution MAC-CE from the second device 120, the first device 110 can continue decoding the PDSCH scrambled with S-RNTI from time ts1 up to the SI window length up to ts1e. If the first device 110 does not receive the requested SIB, the first device 110 can continue decoding the PDSCH in the next SI window from ts2 to ts2e, and so on, as shown in stage 306.

[0047] In traditional on-demand SIB processes, there may be uncertainty regarding the arrival of the on-demand SIB. This would cause the first device 110 to guess and maintain the PDSCH using SI-RNTI for decoding over the SI window length. This uncertainty and blind decoding (searching across several time intervals) in on-demand SIB acquisition could deplete the battery of the first device 110.

[0048] In an embodiment, the specification provides that the network or second device (120) can provide an offset value in the contention-resolved MAC-CE (Msg4) representing the offset from the SI window start slot, such that the first device 120 can estimate the most likely area for on-demand SIB arrival with the help of the provided offset, instead of decoding the PDSCH for the entire SI window length starting from the SI window start and repeating it in the next(s) SI window(s) (if not received in the previous SI window). This offset in the contention-resolved message can reduce the blind search area of ​​the first device 110 without any risk of missing on-demand SIB arrival, and thus improve the power consumption of the first device 110.

[0049] Figure 4 A flowchart of method 400 performed by first device 110 is shown. In step 402, method 400 provides receiving a message including a contention resolution message, which includes an offset value for the decoding window used by first device 110. The contention resolution message is received from second device 120.

[0050] In step 404, method 400 provides an estimate of the arrival time of the requested on-demand system information block (SIB) based on the offset value and the starting slot index for the system information (SI) window, during which the on-demand SIB is transmitted by the second device 120.

[0051] In one example, the contention resolution message includes a contention resolution MAC control element (MAC-CE).

[0052] In one example, the offset value indicates the number of time-domain offsets from the start of the SI window.

[0053] In one example, method 400 includes receiving a Master Information Block (MIB) and System Information Block Type 1 (SIB1) from a second device 120, and initiating a Contention-Based Random Access (CBRA) procedure to request one or more on-demand SIBs by transmitting a first message to the second device on the Physical Random Access Channel (PRACH) and receiving a second message from the second device including timing advance and uplink grant. Method 400 further includes transmitting an on-demand SIB message to the second device 120 indicating the requested on-demand SIB(s).

[0054] In the example, method 400 includes decoding a Physical Downlink Shared Channel (PDSCH) scrambled with System Information RNTI (SI-RNTI) starting from the estimated arrival time, and receiving the requested on-demand SIB within the corresponding SI window. The PDSCH is decoded for a time slot indicated by the sum of the starting time slot and the offset value relative to the time-domain time slot offset of the SI window.

[0055] Figure 5 A flowchart of method 500 performed by first device 110 is shown. In step 502, method 500 provides receiving a message from second device 120 including a contention resolution message, the contention resolution message including an offset value for the decoding window for first device 110.

[0056] At step 504, method 500 provides an estimate of the arrival time of the requested on-demand system information block (SIB) based on information received in the contention resolution message and the start slot index for the system information (SI) window, during which the on-demand SIB is transmitted by the second device 120.

[0057] In one example, the contention resolution message includes a contention resolution MAC control element (MAC-CE).

[0058] In one example, the offset value indicates the number of time-domain offsets from the start of the SI window.

[0059] In one example, method 500 provides receiving a Master Information Block (MIB) and System Information Block Type 1 (SIB1) from a second device 120, and initiating a Contention-Based Random Access (CBRA) procedure to request one or more on-demand SIBs by: transmitting a first message to the second device on the Physical Random Access Channel (PRACH), and receiving a second message from the second device 120 including timing advance and uplink grant. Method 500 further includes transmitting an on-demand SIB message to the second device 120 indicating the requested on-demand SIB.

[0060] In one example, method 500 further includes decoding the Physical Downlink Shared Channel (PDSCH) scrambled with System Information RNTI (SI-RNTI) starting from the estimated arrival time, and receiving the requested on-demand SIB within the corresponding SI window. The PDSCH is decoded for a time slot indicated by the sum of the following: the starting time slot and the offset value relative to the time-domain time slot offset of the SI window.

[0061] Figure 6 A flowchart of method 600 performed by second device 120 is shown. In step 602, method 600 provides to transmit a message including a contention resolution message to at least one first device 110, the contention resolution message including an offset value for a decoding window for the first device 110. The offset value is used to estimate the arrival time of the requested on-demand system information block (SIB) and the start time slot index for the system information (SI) window during which the on-demand SIB is transmitted by the second device 120.

[0062] In one example, method 600 provides transmitting a Master Information Block (MIB) and System Information Block Type 1 (SIB1) to at least one first device 110 to initiate a Contention-Based Random Access (CBRA) procedure, and receiving a first message from at least one first device 110 on the Physical Random Access Channel (PRACH) for the requested one or more on-demand SIBs. Method 600 further includes transmitting a second message to at least one first device 110 including timing advance and uplink grant, and receiving an on-demand SIB message from at least one first device 110 indicating the requested on-demand SIB(s).

[0063] Figure 7A flowchart of method 700 performed by second device 120 is shown. In step 702, method 700 includes transmitting a message including a contention resolution message to at least one first device 110, the contention resolution message including an offset value for a decoding window for the at least one first device 110. Information received in the contention resolution message is used to estimate the arrival time of the requested on-demand system information block (SIB) and the start slot index for the system information (SI) window during which the on-demand SIB is transmitted by the second device 120.

[0064] In one example, method 700 provides transmitting a Master Information Block (MIB) and System Information Block Type 1 (SIB1) to at least one first device 110 to initiate a Contention-Based Random Access (CBRA) procedure, and receiving a first message from at least one first device 110 on the Physical Random Access Channel (PRACH) for the requested one or more on-demand SIBs. Method 700 further includes transmitting a second message to at least one first device 110 including timing advance and uplink grant, and receiving an on-demand SIB message from at least one first device 110 indicating the requested on-demand SIB(s).

[0065] Figure 8 A first signaling diagram 800 of the first device 110 and the second device 120 is shown.

[0066] Steps 801 to 806 are similar to... Figure 2 Steps 201 to 206 are shown, and therefore will not be repeated for the sake of brevity.

[0067] In step 807, Msg4 (i.e., Contention Resolution Message (MAC-CE)) is enhanced to carry the offset value.

[0068] In step 808, since the second device 120 (DU) is responsible for broadcasting SIBs and the MAC scheduler is responsible for scheduling on-demand SIBs, the contention resolution message is highly feasible for determining the broadcast instance of the on-demand SIB and can therefore be used to calculate the offset based on the applicable SI window. Thus, the second device 120 can allocate the offset value based on the real-time MAC opportunities available for broadcasting the on-demand SIB to the first device 110.

[0069] After receiving a contention resolution (enhanced) MAC-CE with an offset, the first device 110 can estimate the on-demand SIB arrival at the instance within an appropriate SI window length.

[0070] In step 809, the first device 110 may wait for (multiple) SI windows to receive the requested SIB at step 810.

[0071] In one example, since the second device 120 may find that the first SI window is not available for scheduling on-demand SIBs, the second device 120 may also provide an SI window in the contention-resolving MAC CE.

[0072] The first device 110 can receive the offset and SI window number in the contention-solving MAC CE and can estimate the arrival time of the on-demand SIB within an appropriate SI window length. The first device uses the offset and SI window number to estimate the precise arrival time of the on-demand SIB as follows: New (Precise Arrival Time) for On-Demand SIB = SI Window Start Slot + Offset + (Optional) SI Window Number

[0073] The inclusion of the SI window number in the contention resolution message is not a simple addition algorithm, but rather an indication of which SI window period the on-demand SIB will be received in. If the first device 110 does not receive the on-demand SIB within the SI window length starting from the SI window start slot, the first device 110 may attempt to receive the on-demand SIB in the next repetition period of the SI window length.

[0074] Figure 9 A second signaling diagram 900 is shown for the first device 110 and the second device 120.

[0075] Steps 901 to 906 are similar to... Figure 2 Steps 201 to 206 are shown, and therefore will not be repeated for the sake of brevity.

[0076] At step 907, the second device 120 may send a Msg4 (Content Resolution Message) carrying a MAC CE, which includes an offset value indicating how many slots the SIB can be available after the SI-WindowStartSlot.

[0077] At step 908, the first device 110 can use the SI window start time slot and offset to estimate the time slot (e.g., tr1) for receiving the SIB. The first device 110 can decode the SI-RTI scrambled PDCCH / PDSCH starting only from this time slot, and the first device 110 can receive the requested SIB without decoding the entire SI window, resulting in power savings.

[0078] In step 909, if the SIB may not be scheduled in the current SI window instance, the second device 120 may also transmit the SI window number along with an offset (relative to the slot offset of the start of the SI window) to the first device 110 in a contention resolution message, which indicates which instance (e.g., the next or subsequent SI window) can carry the SIB.

[0079] In step 910, the first device 110 can calculate the estimated time slot by using SI window start time slot + (SI window number × SI window length) + offset.

[0080] The first device 110 can begin decoding the PDCCH / PDSCH using SI-RNTI at the estimated time slot without needing to monitor an earlier SI window, thus saving power.

[0081] In step 911, the first device 110 receives the requested SIB.

[0082] Figure 10 An enhanced on-demand SIB process, implemented through methods 400, 500, 600, and 700, is shown to decode the arrival of on-demand SIBs.

[0083] In one embodiment (case 1), the first device 110 may receive a contention resolution (enhanced) MAC CE at t4, where the offset is as shown in stage 1002.

[0084] As shown in stage 1004, the first device 110 can estimate the arrival time of the on-demand SIB appearing at tr1, and the first device 110 can decode the PDSCH scrambled using SI-RNTI and tr1 itself, and the first device 110 can receive the required (multiple) SIBs. This reduces the decoding workload of the first device 110 from (tr1) ts1) is reduced, and helps the UE save power.

[0085] In another embodiment (case 2), the first device 110 can receive a contention-resolved message (enhanced) MAC CE with an offset and SI window number at t4. As shown in stage 1006, the first device 110 can estimate the arrival time of the on-demand SIB as t21, and the first device can decode the PDSCH scrambled with SI-RNTI at t21 itself to receive the required (multiple) SIBs. This reduces the decoding workload of the first device 110 from (t1e) ts1)+(tr2 ts2) reduces and helps the first device save power.

[0086] Figure 11 and 12 Block diagrams are shown for a first device 110 and a second device 120 for implementing one or more exemplary embodiments of the present disclosure. The first device 110 may be or include a terminal device, etc. The second device 120 may be or include a base station, a next-generation B-node (gNB), etc.

[0087] The first device 110 and the second device 120 may each include a processor 1104 and a processor 1204, respectively, for controlling the corresponding operations of the first device 110 and the second device 120. The processor 1104 / 1204 may also be referred to as a central processing unit (CPU). The processor 1104 / 1204 may be embodied in various ways, including circuitry, at least one processing core, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, other processing elements including integrated circuits (e.g., application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.), or some combination thereof.

[0088] The first device 110 and the second device 120 may each include a memory 1102 and a memory 1202, respectively. Memory 1102 / 1202 may include both read-only memory (ROM) and random access memory (RAM), and may provide instructions and data to processor 1104 / 1204, respectively. The memory 1102 and processor 1104 of the first device 110 may be operatively coupled. Similarly, the memory 1202 and processor 1204 of the second device 120 may be operatively coupled.

[0089] Memory 1102 / 1202 may store instructions, such as computer-readable instructions / computer program code. The computer-readable instructions / computer program code may be pre-stored in memory 1102 / 1202, alternatively or additionally, and may be received by the first device 110 and the second device 120 via electromagnetic carrier signals and / or copied from a physical entity such as a computer program product. Execution of the computer-readable instructions by processor 1104 / 1204 may cause the first device 110 or the second device 120 to perform the example embodiments described herein, such as... Figures 2 to 5 The steps outlined in the document.

[0090] First device 110 and first device 120 may each include transmitter / receiver (TX / RX) circuits 1106 / 1206, and may further include transmitters 1108 / 1208 and receivers 1110 / 1210. The TX / RX circuits 1106 of first device 110 and 1206 of second device 120 may enable them to transmit or receive data, respectively. First device 110 and second device 120 may include (not shown) multiple antennas, transmitters, and receivers.

[0091] In some example embodiments, the first device 110 and the second device 120 may each include components that enable them to perform... Figures 2 to 5A component for the steps / operations (if applicable). This component can be implemented in any suitable form. For example, the component can be implemented at least in a circuit, a combination of memory 1102 / 1202, processor 1104 / 1204, TX / RX circuit 1106 / 1206, or software module.

[0092] Example embodiments of the present disclosure have been disclosed in the accompanying drawings and description. Although specific terminology has been used, it is used in a general and descriptive sense only and not for limiting purposes. It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments disclosed herein that are consistent with the present disclosure without departing from the spirit and scope of the present disclosure. Other embodiments consistent with the present disclosure will become apparent upon consideration of the description in the specification and the present disclosure.

Claims

1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: Receive a message from the second device including a contention resolution message, the contention resolution message including an offset value for the decoding window used by the first device; as well as Based on the information received in the contention resolution message and the estimated arrival time of the requested on-demand system information block (SIB) for the start slot index of the system information (SI) window, the on-demand SIB is transmitted by the second device during the SI window.

2. The first apparatus according to claim 1, wherein the contention resolution message includes a contention resolution MAC control element (MAC-CE). The contention resolution message further includes an SI window number indicating a future instance of the SI window, in which the second device transmits the requested on-demand SIB.

3. The first apparatus of claim 1, wherein the offset value indicates the number of time-domain offsets from the start of the SI window.

4. The first apparatus according to claim 1, wherein the at least one processor is configured to: Receive the Master Information Block (MIB) and System Information Block Type 1 (SIB1) from the second device; To request one or more On-Demand SIBs, initiate the contention-based random access CBRA procedure as follows: Transmit the first message to the second device on the Physical Random Access Channel (PRACH); and Receive a second message from the second device, including timing advance and uplink authorization; and Transmit an on-demand SIB message to the second device, indicating the requested one or more on-demand SIBs.

5. The first apparatus according to claim 1, wherein the at least one processor is configured to: Decoding begins from the estimated arrival time of the Physical Downlink Shared Channel (PDSCH) scrambled using System Information RNTI SI-RNTI; and The requested on-demand SIB is received in the indicated SI window instance based on the SI window number in the contention resolution message. The PDSCH is decoded for a time slot indicated by the sum of the following: the starting time slot of the time-domain time slot offset relative to the SI window, the product of the SI window number and the SI window length, and the offset value.

6. A second means for communication, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the second device to at least: A message including a contention resolution message is transmitted to at least one first device, the contention resolution message including an offset value for a decoding window used by the first device. The information received in the contention resolution message is used to estimate the arrival time of the requested on-demand system information block (SIB) and the starting time slot index for the system information SI window, during which the on-demand SIB is transmitted by the second device.

7. The second apparatus according to claim 6, wherein the at least one processor is configured to: Transmit the Master Information Block (MIB) and System Information Block Type 1 (SIB1) to the at least one first device to initiate a contention-based random access (CBRA) procedure; Receive a first message from the at least one first device on the Physical Random Access Channel (PRACH) for the requested one or more on-demand SIBs; Transmit a second message including timing advance and uplink authorization to the at least one first device; as well as Receive an on-demand SIB message from the at least one first device, indicating the requested one or more on-demand SIBs.

8. A communication method for a first device, comprising: Receive a message from the second device including a contention resolution message, the contention resolution message including an offset value for the decoding window used by the first device; as well as Based on the information received in the contention resolution message and the estimated arrival time of the requested on-demand system information block (SIB) for the start slot index of the system information (SI) window, the on-demand SIB is transmitted by the second device during the SI window.

9. The communication method according to claim 8, comprising: Decoding begins from the estimated arrival time of the Physical Downlink Shared Channel (PDSCH) scrambled using System Information RNTI SI-RNTI; as well as The requested on-demand SIB is received in the indicated SI window instance based on the SI window number in the contention resolution message. The PDSCH is decoded for a time slot indicated by the sum of the following: the starting time slot of the time-domain time slot offset relative to the SI window, the product of the SI window number and the SI window length, and the offset value.

10. A communication method for a second device, comprising: A message including a contention resolution message is transmitted to at least one first device, the contention resolution message including an offset value for a decoding window used by the first device. The information received in the contention resolution message is used to estimate the arrival time of the requested on-demand system information block (SIB) and the starting time slot index for the system information SI window, during which the on-demand SIB is transmitted by the second device.

11. A terminal device, comprising: Components for performing the method according to any one of claims 8-9.

12. A network device, comprising: Components for performing the method according to claim 10.

Images