Method and apparatus for random access in wireless communication system

Abstract

A method and apparatus for random access in a wireless communication system are disclosed. In one embodiment, a user equipment determines whether to initiate a random access procedure on a cell to request SIB1 from a base station based on information related to access barring.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Patent Application Nos. 63 / 622,705 and 63 / 622,720, filed on January 19, 2024, the entire disclosures of which are incorporated herein by reference in their entireties. Field of the Invention

[0003] This disclosure generally relates to wireless communication networks, and more particularly, to methods and devices for random access in a wireless communication system. Background Art

[0004] With the rapid growth in the demand for transferring large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This IP packet communication can provide IP - bearer voice, multimedia, multicast, and on - demand communication services to users of mobile communication devices.

[0005] An exemplary network structure is the Evolved Universal Terrestrial Radio Access Network (E - UTRAN). The E - UTRAN system can provide high data throughput to enable the above - mentioned IP - bearer voice and multimedia services. Currently, the 3GPP standards organization is discussing new next - generation (e.g., 5G) new radio technologies. Thus, changes to the current body of the 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the Invention

[0006] The present invention discloses a method and apparatus for a User Equipment (UE). In one embodiment, the UE determines whether to initiate a random access procedure on a cell to request SIB1 based on information related to access prohibition. Brief Description of the Drawings

[0007] Figure 1 Drawings showing a wireless communication system in accordance with an exemplary embodiment are presented.

[0008] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) in accordance with an exemplary embodiment.

[0009] Figure 3 is a functional block diagram of a communication system in accordance with an exemplary embodiment.

[0010] Figure 4 is the functional block diagram of the Figure 3 program code according to an exemplary embodiment.

[0011] Figure 5 is the reproduction of Figure 5 .3.3.1-1 in 3GPP TS 38.331 V17.6.0.

[0012] Figure 6 is the reproduction of Figure 5 .3.3.1-2 in 3GPP TS 38.331 V17.6.0..

[0013] Figure 7 is the reproduction of Figure 5 .3.13.1-1 in 3GPP TS 38.331 V17.6.0.

[0014] Figure 8 is the reproduction of Figure 5 .3.13.1-2 in 3GPP TS 38.331 V17.6.0.

[0015] Figure 9 is the reproduction of Figure 5 .3.13.1-3 in 3GPP TS 38.331 V17.6.0.

[0016] Figure 10 is the reproduction of Figure 5 .3.13.1-4 in 3GPP TS 38.331 V17.6.0.

[0017] Figure 11 is the reproduction of Figure 5 .3.13.1-5 in 3GPP TS 38.331 V17.6.0.

[0018] Figure 12 is the flowchart according to an exemplary embodiment.

[0019] Figure 13 is the flowchart according to an exemplary embodiment.

[0020] Figure 14 is the flowchart according to an exemplary embodiment.

[0021] Figure 15 is the flowchart according to an exemplary embodiment. Detailed implementation

[0022] The exemplary wireless communication systems and devices described below employ a wireless communication system that supports broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A or LTE-Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation techniques.

[0023] Specifically, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by an alliance named "Third Generation Partnership Project" and referred to herein as 3GPP, including: TS38.211 V15.7.0, "NR; Physical Channels and Modulation (Release 15)"; TS 38.213 V18.0.0, "NR; Physical Layer Procedures for Control (Release 18)"; TS 38.321 V17.6.0, "NR; Medium Access Control (MAC) Protocol Specification (Release 17)"; TS38.331 V17.6.0, "NR; Radio Resource Control (RRC) Protocol Specification (Release 17)"; and RP-234065, "New WID: Enhancements for Network Energy Savings in NR", Ericsson. The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

[0024] Figure 1 FIG. shows a multi-access wireless communication system in accordance with an embodiment of the present invention. The access network 100 (access network, AN) includes a plurality of antenna groups, one including 104 and 106, another including 108 and 110, and still another including 112 and 114. In Figure 1In this case, only two antennas are shown for each antenna group. However, each antenna group may utilize more or fewer antennas. The access terminal 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to the access terminal 116 via the forward link 120 and receive information from the access terminal 116 via the reverse link 118. The access terminal 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to the access terminal 122 via the forward link 126 and receive information from the access terminal 122 via the reverse link 124. In an FDD system, the communication links 118, 120, 124, and 126 can communicate using different frequencies. For example, the forward link 120 can use a frequency different from the frequency used by the reverse link 118.

[0025] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0026] In the communication via the forward links 120 and 126, the transmit antennas of the access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Also, compared to an access network that transmits to all of its access terminals via a single antenna, an access network that uses beamforming to transmit to access terminals randomly scattered throughout the coverage area of the access network causes less interference to access terminals in adjacent cells.

[0027] The access network (AN) can be a fixed station or a base station for communicating with terminals and can also be referred to as an access point, Node B, base station, enhanced base station, evolved Node B (eNB), network node, network, or some other term. The access terminal (AT) can also be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0028] Figure 22 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a plurality of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0029] In one embodiment, each data stream is transmitted through a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0030] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by processor 230.

[0031] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0032] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and up-converts) the analog signals to provide a modulated signal suitable for transmission via a MIMO channel. T The antennas 224a to 224t transmit N signals from transmitters 222a to 222t. T a modulated signal.

[0033] At the receiver system 250, N RAntennas 252a through 252r receive the transmitted modulated signals and provide the signals received from each antenna 252 to corresponding receivers (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and down-converts) the respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0034] The RX data processor 260 then receives and processes N R received symbol streams from the N R receivers 254 based on specific receiver processing techniques to provide N T "detected" symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0035] The processor 270 periodically determines which precoding matrix (discussed below) to use. The processor 270 formulates a reverse link message that includes a matrix index portion and a rank value portion.

[0036] The reverse link message may include various types of information regarding the communication link and / or the received data streams. The reverse link message is then processed by the TX data processor 238, which also receives several data streams of traffic data from the data source 236, modulated by the modulator 280, conditioned by the transmitters 254a through 254r, and transmitted back to the transmitter system 210.

[0037] At the transmitter system 210, the modulated signals from the receiver system 250 are received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0038] Turning Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device in accordance with an embodiment of the present invention. As Figure 3 shown, the UE (or AT) 116 and 122 in Figure 1 or Figure 1The base station (or AN) 100 in it, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 may receive signals input by a user through the input device 302 (e.g., a keyboard or keypad), and may output images and sounds through the output device 304 (e.g., a display or speaker). The transceiver 314 is used to receive and transmit wireless signals, deliver the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306. The AN 100 in Figure 1 can also be implemented by using the communication device 300 in the wireless communication system.

[0039] Figure 4 is a simplified block diagram of the program code 312 shown in Figure 3 according to an embodiment of the present invention. In this embodiment, the program code 312 includes an application layer 400, a layer 3 part 402, and a layer 2 part 404, and is coupled to a layer 1 part 406. The layer 3 part 402 generally performs radio resource control. The layer 2 part 404 generally performs link control. The layer 1 part 406 generally performs physical connection.

[0040] The random access procedure is introduced for several purposes, such as obtaining UL synchronization (e.g., UL TA), requesting UL grant resources, recovering beamforming failures, etc. The random access procedure can be classified into a contention-based random access procedure and a non-contention-based random access procedure. For the non-contention-based random access procedure, a dedicated preamble (and dedicated PRACH resources) is allocated to the UE, such that the gNB can identify the UE transmitting the preamble via preamble detection / reception. To request system information, a dedicated preamble can be allocated for requesting (specific) SI / SIB (e.g., SIB2). The dedicated preamble can be utilized by all UEs requesting the SI / SIB. (e.g., To request system information, it is not necessary to identify the UE) The UE will then monitor the random access response from the base station. When / if a random access response to the transmitted preamble is received, the non-contention-based random access procedure will be considered successfully completed. On the other hand, for the contention-based random access procedure, the preamble is randomly selected from a set of available preambles (e.g., which can depend on the purpose or scenario or the UE initiating the random access procedure). After transmitting the random access preamble, the UE can monitor the corresponding random access response. After successfully receiving the random access response, the UE will transmit Msg 3 (which can be used to identify the UE). After transmitting Msg 3, the UE will monitor contention resolution (e.g., Msg 4). If a contention resolution for the UE is successfully received, the UE will consider the random access procedure successfully completed.

[0041] More details related to the random access procedure are discussed and provided in 3GPP TS 38.213, TS 38.321, and TS 38.331 below. Specifically, 3GPP TS 38.213 states:

[0042] 8 Random access procedure

[0043] […]

[0044] 8.1 Random access preamble

[0045] […]

[0046] The UE uses the selected PRACH format on the cell to transmit the power P PRACH，b , f, c(i) at In the case of preamble repetition, on the indicated PRACH resources or on the determined resources to transmit the PRACH.

[0047] For the type 1 random access procedure, the UE is provided with N SS / PBCH block indices associated with one PRACH occasion and R contention-based preambles per SS / PBCH block index per valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0048] For the type 1 random access procedure, or for the type 2 random access procedure with a separate configuration of PRACH occasions from the type 1 random access procedure, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH occasions, and R contention-based preambles with consecutive indices associated with the SS / PBCH block index per valid PRACH occasion start from preamble index 0. If N ≥ 1, R contention-based preambles with consecutive indices associated with the SS / PBCH block index n (0 ≤ n ≤ N - 1) per valid PRACH occasion start from the preamble index starting, where is provided by totalNumberOfRA-Preambles for the type 1 random access procedure, or by msgA-TotalNumberOfRA-Preambles for the type 2 random access procedure with a configuration of PRACH occasions separate from the type 1 random access procedure, and is an integer multiple of N.

[0049] 8.2 Random access response - Type 1 random access procedure

[0050] […]

[0051] If the UE detects DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI and the LSB of the SFN field in DCI format 1_0 (if included and applicable) is the same as the corresponding LSB of the SFN in which the UE transmits the PRACH, and the UE receives the transport block in the corresponding PDSCH within the window, the UE passes the transport block to the higher layer. The higher layer resolves the transport block for the random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layer identifies the RAPID in the RAR message of the transport block, the higher layer indicates an uplink grant to the physical layer. This is called the random access response (RAR) UL grant in the physical layer.

[0052] […]

[0053] The RAR UL grant authorizes the scheduling of PUSCH transmissions from the UE. The content of the RAR UL grant, starting with the MSB and ending with the LSB, is given in Table 8.2-1.

[0054] […]

[0055] 8.3 PUSCH Scheduled by RAR UL Grant

[0056] As described in Clause 12 and [4, TS 38.211], for PUSCH transmissions scheduled by the RAR UL grant, the active UL BWP with SCS configuration μ is indicated by the higher layers.

[0057] […]

[0058] The Msg3 PUSCH retransmission of the transport block (if any) is scheduled by DCI format 0_0, which has a CRC scrambled with the TC-RNTI provided in the corresponding RAR message [11, TS 38.321].

[0059] 8.4 PDSCH with UE Contention Resolution Identity

[0060] In response to PUSCH transmissions scheduled by the RAR UL grant when the UE is not provided with a C-RNTI, the UE attempts to detect DCI format 1_0 [11, TS 38.321] with a CRC scrambled with the corresponding TC-RNTI that schedules the PDSCH containing the UE contention resolution identity. In response to the reception of the PDSCH with the UE contention resolution identity, the UE transmits HARQ-ACK information in the PUCCH.

[0061] […]

[0062] Furthermore, 3GPP 38.321 states:

[0063] 5.1.2 Random Access Resource Selection

[0064] If the selected RA_TYPE is set to 4-stepRA, the MAC entity will:

[0065] […]

[0066] 1> Otherwise, if a random access procedure is initiated for an SI request (as specified in TS 38.331 [5]); and

[0067] 1> If the random access resources for the SI request have been explicitly provided by the RRC:

[0068] 2> If at least one SSB with an SS-RSRP higher than rsrp-ThresholdSSB is available:

[0069] 3> Select the SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0070] 2> Otherwise:

[0071] 3> Select any SSB.

[0072] 2> Select the random access preamble corresponding to the selected SSB from the random access preambles determined according to ra-PreambleStartIndex as specified in TS 38.331 [5];

[0073] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0074] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0075] 2> If at least one SSB with SS-RSRP higher than rsrp-ThresholdSSB is available:

[0076] 3> Select the SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0077] 2> Otherwise:

[0078] 3> Select any SSB.

[0079] […]

[0080] 3> If random access preamble group B is configured:

[0081] 4> If the potential Msg3 size (e.g., UL data available for transmission plus MAC sub-header and MAC CE if needed) is greater than ra-Msg3SizeGroupA and the path loss is less than PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB (of the serving cell where the random access procedure is performed); or

[0082] 4> If the random access procedure is initiated for the CCCH logical channel and the CCCH SDU size plus MAC sub-header is greater than ra-Msg3SizeGroupA:

[0083] 5> Select random access preamble group B.

[0084] 4> Otherwise:

[0085] 5> Select random access preamble group A.

[0086] 3> Otherwise:

[0087] 4> Select random access preamble group A.

[0088] […]

[0089] 2> Randomly select a random access preamble from the random access preambles associated with the selected SSB and the selected random access preamble group with equal probability;

[0090] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0091] […]

[0092] 1> Execute the random access preamble transmission procedure (see item 5.1.3).

[0093] […]

[0094] 5.1.4 Random access response reception

[0095] Once the random access preamble is transmitted and regardless of whether a measurement gap may occur, the MAC entity will:

[0096] […]

[0097] 1> Otherwise:

[0098] 2> If the random access preamble is transmitted over a non-terrestrial network:

[0099] 3> Start the ra-ResponseWindow configured in RACH-ConfigCommon at a PDCCH occasion as specified in TS 38.213 [6].

[0100] […]

[0101] 1> Otherwise, if a valid (as specified in TS 38.213 [6]) downlink allocation has been received on the PDCCH for the RA-RNTI and the received TB has been successfully decoded:

[0102] […]

[0103] 2> If the random access response contains a MAC sub-PDU with a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX (see item 5.1.3):

[0104] 3> Consider the random access response reception successful.

[0105] 2> If the random access response reception is considered successful:

[0106] 3> If the random access response contains a MAC sub-PDU with only the RAPID:

[0107] 4> Consider this random access procedure successfully completed;

[0108] 4> Indicate to the upper layer that an acknowledgement for the SI request has been received.

[0109] 3> Otherwise:

[0110] […]

[0111] 6> Process the received UL grant value and indicate the value to the lower layer.

[0112] 4> If the MAC entity did not select a random access preamble among the contention-based random access preambles:

[0113] 5> Consider the random access procedure successfully completed.

[0114] 4> Otherwise:

[0115] […]

[0116] 5> If this is the first successfully received random access response within this random access procedure:

[0117] […]

[0118] 6> Obtain the MAC PDU for transmission from the multiplexing and assembly entity and store it in the Msg3 buffer.

[0119] 5.1.5 Contention resolution

[0120] Once Msg3 is transmitted, the MAC entity shall:

[0121] […]

[0122] 1> If a reception notification of PDCCH transmission for the SpCell is received from the lower layer:

[0123] […]

[0124] 2> Otherwise, if a CCCH SDU is included in Msg3 and the PDCCH transmission is addressed to its TEMPORARY_C-RNTI:

[0125] 3> If the MAC PDU is successfully decoded:

[0126] 4> Stop the ra-ContentionResolutionTimer;

[0127] 4> If the MAC PDU contains a UE contention resolution identity MAC CE; and

[0128] 4> If the UE contention resolution identity in the MAC CE matches the CCCH SDU transmitted in Msg3:

[0129] 5> Consider this contention resolution successful and end the disassembly and demultiplexing of the MAC PDU;

[0130] 5> If this random access procedure is initiated for an SI request:

[0131] 6> Indicate to the upper layer that an acknowledgement for the SI request has been received.

[0132] 5> Otherwise:

[0133] 6> Set the C-RNTI to the value of TEMPORARY_C-RNTI;

[0134] 5> Discard TEMPORARY_C-RNTI;

[0135] 5> Consider this random access procedure successfully completed.

[0136] In addition, 3GPP TS 38.331 states:

[0137] 5.2.2.3.3 Request for on-demand system information

[0138] When the SDT procedure is not in progress, the UE shall:

[0139] 1> If SIB1 contains si-RequestConfigSUL in si-SchedulingInfo and the criteria for selecting the supplementary uplink as defined in TS38.321 [3], then item 5.1.1 is satisfied:

[0140] 2> Use the PRACH preamble and PRACH resources in si-RequestConfigSUL corresponding to the SI message that the UE needs to operate in the cell, and trigger the lower layer to initiate a random access procedure on the supplementary uplink according to TS 38.321 [3], and where si-BroadcastStatus is set to notBroadcasting;

[0141] 2> If an acknowledgement for the SI request is received from the lower layer:

[0142] 3> Immediately obtain the requested SI message as defined in item 5.2.2.3.2;

[0143] 1> Otherwise, if the UE is a RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 contains si-SchedulingInfo with si-RequestConfigRedCap and the criteria for selecting the normal uplink as defined in TS 38.321 [3], then item 5.1.1 is satisfied:

[0144] 2> Use the PRACH preamble and PRACH resources in si-RequestConfigRedcap corresponding to the SI message that the UE needs to operate within the cell, and trigger the lower layer to initiate a random access procedure on the normal uplink according to TS 38.321 [3], and where si-BroadcastStatus is set to notBroadcasting;

[0145] 2> If an acknowledgement for the SI request is received from the lower layer:

[0146] 3> Immediately obtain the requested SI message as defined in item 5.2.2.3.2;

[0147] 1> Otherwise:

[0148] 2> If the UE is not a RedCap UE and if SIB1 contains si-SchedulingInfo with si-RequestConfig and the criteria for selecting the normal uplink as defined in TS 38.321 [3], then item 5.1.1 is satisfied; or

[0149] 2> If the UE is a RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 contains si-SchedulingInfo with si-RequestConfig and the criteria for selecting the normal uplink as defined in TS 38.321 [3], then item 5.1.1 is satisfied:

[0150] 3> Use the PRACH preamble and PRACH resources in si-RequestConfig corresponding to the SI message that the UE needs to operate within the cell, and trigger the lower layer to initiate a random access procedure on the normal uplink according to TS 38.321 [3], and where si-BroadcastStatus is set to notBroadcasting;

[0151] 3> If an acknowledgement for the SI request is received from the lower layer:

[0152] 4> Immediately obtain the requested SI message as defined in Clause 5.2.2.3.2;

[0153] […]

[0154] Note: After a RACH failure for an SI request, it is up to the UE implementation to decide when to retry the SI request.

[0155] […]

[0156] 5.3.3 RRC Connection Establishment

[0157] 5.3.3.1 General

[0158] [The content of Subclause 3.3.1-1 of 3GPP TS 38.331 V17.6.0 named "RRC connection establishment successful" is reproduced as Figure 5 .3.3.1-1 Figure 5

[0159] [The content of Subclause 3.3.1-2 of 3GPP TS 38.331 V17.6.0 named "Network rejects RRC connection establishment" is reproduced as Figure 5 .3.3.1-2 Figure 6

[0160] The purpose of this procedure is to establish an RRC connection. The RRC connection establishment involves the establishment of SRB1. This procedure is also used to transfer the initial NAS dedicated information / message from the UE to the network.

[0161] The network applies this procedure, for example, as follows:

[0162] - When establishing an RRC connection;

[0163] - When the UE is resuming or re-establishing an RRC connection and the network is unable to retrieve or verify the UE context. In this case, the UE receives RRCSetup and responds with RRCSetupComplete.

[0164] 5.3.3.2 Initiation

[0165] When the upper layer requests the establishment of an RRC connection while the UE is in RRC_IDLE and it has obtained the basic system information, or for sidelink communication as specified in Clause 5.3.3.1a, the UE initiates the procedure.

[0166] Before initiating this procedure, the UE shall ensure that it has valid and up-to-date basic system information as specified in Clause 5.2.2.2.

[0167] After initiating the procedure, the UE shall:

[0168] ​​1> If the upper layer provides an access category and one or more access identifiers after requesting the establishment of an RRC connection:

[0169] 2> Use the access category and access identifiers provided by the upper layer to perform the unified access control procedure as specified in 5.3.14;

[0170] 3> If the access attempt is prohibited, the procedure ends;

[0171] 1> If the upper layer provides NSAG information and one or more S-NSSAIs that trigger the access attempt (TS23.501

[32] and TS24.501

[23] ):

[0172] 2> Apply, in the random access procedure, the NSAG with the highest NSAG priority among the NSAGs included in SIB1 (i.e., in FeatureCombination and / or in RA-PrioritizationSliceInfo) and associated with the S-NSSAI that triggers the access attempt (TS 38.321[3], clause 5.1):

[0173] […]

[0174] 1> Initiate the transmission of the RRCSetupRequest message according to 5.3.3.3;

[0175] 5.3.3.3 Actions related to the transmission of the RRCSetupRequest message

[0176] The UE shall set the content of the RRCSetupRequest message as follows:

[0177] […]

[0178] 1> If the establishment of the RRC connection is the result of a redirection release by mpsPriorityIndication (in NR or E-UTRAN):

[0179] 2> Set the establishmentCause to mps-PriorityAccess;

[0180] 1> Otherwise:

[0181] […]

[0182] The UE shall submit the RRCSetupRequest message to the lower layer for transmission.

[0183] If the UE is a RedCap UE and the RedCap-specific initial downlink BWP is not associated with a CD-SSB, the UE may continue cell reselection-related measurements and cell reselection evaluation; otherwise, the UE shall continue cell reselection-related measurements and cell reselection evaluation. If the conditions for cell reselection are met, the UE shall perform cell reselection as specified in 5.3.3.6.

[0184] […]

[0185] 5.3.3.4 UE Reception of RRCSetup

[0186] The UE shall perform the following actions upon receiving RRCSetup:

[0187] 1> If RRCSetup is received in response to RRCReestablishmentRequest; or

[0188] 1> If RRCSetup is received in response to RRCResumeRequest or RRCResumeRequest1:

[0189] […]

[0190] 2> Release the RRC configuration, except for the preset L1 parameter values, the preset MAC cell group configuration, the CCCH configuration, and the broadcast MRB;

[0191] 2> Indicate to the upper layer the fallback of the RRC connection;

[0192] […]

[0193] 1> Perform the cell group configuration procedure according to the received masterCellGroup and as specified in 5.3.5.5;

[0194] 1> Perform the radio bearer configuration procedure according to the received radioBearerConfig and as specified in 5.3.5.6;

[0195] 1> If stored, discard the cell reselection priority information provided by cellReselectionPriorities or inherited from another RAT;

[0196] […]

[0197] 1> If RRCSetup is received in response to RRCResumeRequest, RRCResumeRequest1, or RRCSetupRequest:

[0198] […]

[0199] 2> Enter RRC_CONNECTED;

[0200] 2> Stop the cell reselection procedure;

[0201] […]

[0202] 1> Consider the current cell as the PCell;

[0203] […]

[0204] 1> Set the content of the RRCSetupComplete message as follows:

[0205] […]

[0206] 1> Submit the RRCSetupComplete message to the lower layer for transmission, after which the procedure ends.

[0207] 5.3.3.5 UE's Reception of RRCReject

[0208] The UE shall:

[0209] 1> Perform the actions specified in 5.3.15;

[0210] […]

[0211] 5.3.13 RRC Connection Reestablishment

[0212] 5.3.13.1 General

[0213] [The [name of 3GPP TS 38.331 V17.6.0 "RRC Connection Reestablishment Success"] Figure 5 .3.13.1-1 is reproduced as Figure 7

[0214] [The [name of 3GPP TS 38.331 V17.6.0 "RRC Connection Reestablishment Fallback to RRC Connection Establishment, Success"] Figure 5 .3.13.1-2 is reproduced as Figure 8

[0215] [The [name of 3GPP TS 38.331 V17.6.0 "RRC Connection Reestablishment Success Followed by Network Release"] Figure 5 .3.13.1-3 is reproduced as Figure 9

[0216] [The [name of 3GPP TS 38.331 V17.6.0 "RRC Connection Reestablishment Success Followed by Network Suspension"] Figure 5 .3.13.1-4 is reproduced as Figure 10

[0217] ​​​​Figure 5 .3.13.1-5 reproduced as Figure 11

[0218] The purpose of this procedure is to resume a suspended RRC connection, including resuming SRBs, DRBs, and multicast MRBs, or performing RNA updates. This procedure is also used to initiate SDT in RRC_INACTIVE.

[0219] […]

[0220] 5.3.13.2 Initiation

[0221] […]

[0222] Before initiating this procedure, the UE shall ensure that it has valid and up-to-date basic system information as specified in Subclause 5.2.2.2.

[0223] After initiating the procedure, the UE shall:

[0224] 1> If the RRC connection resume is triggered by responding to an NG-RAN paging:

[0225] 2> Select '0' as the access category;

[0226] 2> Perform the unified access control procedure as specified in 5.3.14 using the selected access category and one or more access identifiers provided by the upper layer;

[0227] 3> If the access attempt is prohibited, the procedure ends;

[0228] 1> Otherwise, if the RRC connection resume is triggered by the upper layer:

[0229] 2> If the upper layer provides an access category and one or more access identifiers:

[0230] 3> Perform the unified access control procedure as specified in 5.3.14 using the access category and access identifiers provided by the upper layer;

[0231] 4> If the access attempt is prohibited, the procedure ends;

[0232] 2> If the upper layer provides NSAG information and one or more S-NSSAIs that trigger the access attempt (TS23.501

[32] and TS24.501

[23] ):

[0233] ​​3> Apply the NSAG with the highest NSAG priority among the NSAGs included in SIB1 (i.e., in FeatureCombination and / or in RA-PrioritizationSliceInfo) and associated with the S-NSSAI that triggered the access attempt (TS 38.321 [3], item 5.1):

[0234] […]

[0235] 2> If the resume occurs after the redirection release by mpsPriorityIndication:

[0236] 3> Set resumeCause to mps-PriorityAccess;

[0237] 2> Otherwise:

[0238] 3> Set resumeCause according to the information received from the upper layer;

[0239] 1> Otherwise, if the RRC connection resume is triggered due to RNA update, as specified in 5.3.13.8:

[0240] 2> If the emergency service is in progress:

[0241] […]

[0242] 3> Select '2' as the access category;

[0243] 3> Set resumeCause to emergency;

[0244] 2> Otherwise:

[0245] 3> Select '8' as the access category;

[0246] 2> Execute the unified access control procedure as specified in 5.3.14 using the selected access category and one or more access identifiers to be applied as specified in TS24.501

[23] ;

[0247] 3> If the access attempt is prohibited:

[0248] 4> Set the variable pendingRNA-Update to true;

[0249] 4> The procedure ends;

[0250] […]

[0251] 1> Initiate the transmission of the RRC Resume Request message or RRC Resume Request1 according to 5.3.13.3.

[0252] […]

[0253] 5.3.13.4 UE's reception of RRC Resume

[0254] The UE shall:

[0255] […]

[0256] 1> If the RRC Resume contains the master Cell Group:

[0257] 2> Perform cell group configuration for the received master Cell Group according to 5.3.5.5;

[0258] […]

[0259] 1> Enter RRC_CONNECTED;

[0260] 1> Indicate to the upper layer that the suspended RRC connection has been resumed;

[0261] 1> Stop the cell reselection procedure;

[0262] 1> Consider the current cell as the PCell;

[0263] 1> Set the content of the RRC Resume Complete message as follows:

[0264] […]

[0265] 1> Submit the RRC Resume Complete message to the lower layer for transmission;

[0266] 1> The procedure ends.

[0267] […]

[0268] 5.2.2.4.2 Actions after receiving SIB1

[0269] After receiving SIB1, the UE shall:

[0270] 1> Store the obtained SIB1;

[0271] 1> If the access is for NTN and cellBarredNTN in the obtained SIB1 is set to barred or cellBarredNTN is not included in the obtained SIB1:

[0272] 2> Consider the cell as barred according to TS 38.304

[20] ;

[0273] 2>Perform cell reselection for other cells operating on the same frequency as the prohibited cell, as specified in TS 38.304

[20] ;

[0274] 1>If the UE is a RedCap UE and it is in RRC_IDLE or RRC_INACTIVE, or if the RedCap UE is in RRC_CONNECTED and T311 is running:

[0275] 2>If intraFreqReselectionRedCap does not exist in SIB1:

[0276] 3>Consider the cell prohibited according to TS 38.304

[20] ;

[0277] 3>Perform the prohibition as if intraFreqReselectionRedCap were set to allowed;

[0278] 2>Otherwise:

[0279] 3>If cellBarredRedCap1Rx exists in the retrieved SIB1 and is set to barred, and the UE is equipped with a 1Rx branch; or

[0280] 3>If cellBarredRedCap2Rx exists in the retrieved SIB1 and is set to barred, and the UE is equipped with a 2Rx branch; or

[0281] 3>If halfDuplexRedCapAllowed does not exist in the retrieved SIB1 and the UE only supports half-duplex FDD operation:

[0282] 4>Consider the cell prohibited according to TS 38.304

[20] ;

[0283] 4>Perform the prohibition based on intraFreqReselectionRedCap as specified in TS 38.304

[20] ;

[0284] 1>If cellAccessRelatedInfo contains an entry for the selected SNPN or PLMN, and in the case of a PLMN, the UE is allowed or instructed to access the PLMN via a cell that broadcasts at least one CAG ID:

[0285] 2> In the remainder of the procedure, use the npn-IdentityList, trackingAreaCode, and cellIdentity for the cell as received in the corresponding entry of the npn-IdentityInfoList containing the selected PLMN or SNPN;

[0286] 1> Otherwise, if cellAccessRelatedInfo contains an entry with the PLMN-Identity of the selected PLMN:

[0287] 2> In the remainder of the procedure, use the plmn-IdentityList, trackingAreaCode, trackingAreaList, and cellIdentity for the cell as received in the corresponding PLMN-IdentityInfo containing the selected PLMN;

[0288] 1> If the UE in RRC_INACTIVE is configured for a feature that it does not support in the current serving cell:

[0289] 2> The corresponding configuration is not used in the current serving cell;

[0290] […]

[0291] 1> Otherwise:

[0292] 2> If the UE supports one or more of the frequency bands indicated in the frequencyBandList for the downlink of TDD, or one or more of the frequency bands indicated in the frequencyBandList for the uplink of FDD, and they are not downlink-only frequency bands, and

[0293] 2> If the UE is an IAB-MT or supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for the supported frequency bands in the downlink of TDD or the supported frequency bands in the uplink of FDD, and

[0294] 2> If the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1

[15] , TS 38.101-2

[39] , and TS 38.101-5

[75] ), which

[0295] - Less than or equal to carrierBandwidth (indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or for the RedCap UE (if configured) of the RedCap-specific initial uplink BWP), and

[0296] - Wider than or equal to the bandwidth of the initial uplink BWP or the RedCap UE (if configured) of the RedCap-specific initial uplink BWP, and

[0297] 2> If the UE supports the downlink channel bandwidth with the maximum transmission bandwidth configuration (see TS 38.101-1

[15] , TS 38.101-2

[39] and TS 38.101-5

[75] ),

[0298] - Less than or equal to carrierBandwidth (indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or for the RedCap UE (if configured) of the RedCap-specific initial downlink BWP), and

[0299] - Wider than or equal to the bandwidth of the initial downlink BWP or the RedCap UE (if configured) of the RedCap-specific initial downlink BWP, and

[0300] 2> If there is frequencyShift7p5khz and the UE supports the corresponding 7.5 kHz frequency shift on this band; or if there is no frequencyShift7p5khz:

[0301] 3> If the trackingAreaCode or trackingAreaList is not provided for the PLMN of the selected PLMN or registered PLMN or equivalent PLMN list:

[0302] 4> Consider the cell as prohibited according to TS 38.304

[20] ;

[0303] 4> Perform cell reselection for other cells on the same frequency as the prohibited cell, as specified in TS 38.304

[20] ;

[0304] 3> Otherwise, if the UE is an IAB-MT, and if the iab-Support is not provided for the PLMN of the selected PLMN or registered PLMN or equivalent PLMN list or the selected SNPN or registered SNPN:

[0305] 4> Consider the cell as prohibited according to TS 38.304

[20] ;

[0306] 3> Otherwise:

[0307] 4> Apply the supported uplink channel bandwidth with the maximum transmission bandwidth, which

[0308] - is included within the carrierBandwidth indicated in the uplinkConfigCommon for the SCS of the initial uplink BWP or for the RedCap UE (if configured) of the RedCap-specific initial uplink BWP, and which

[0309] - is wider than or equal to the bandwidth of the initial BWP for the uplink or the RedCap UE (if configured) of the RedCap-specific initial uplink BWP;

[0310] 4> Apply the supported downlink channel bandwidth with the maximum transmission bandwidth, which

[0311] - is included within the carrierBandwidth indicated in the downlinkConfigCommon for the SCS of the initial downlink BWP or for the RedCap UE (if configured) of the RedCap-specific initial downlink BWP, and which

[0312] - is wider than or equal to the bandwidth of the initial BWP for the downlink or the RedCap UE (if configured) of the RedCap-specific initial downlink BWP;

[0313] 4> Select the first frequency band in the frequencyBandList for FDD from the frequencyBandList for the uplink or for TDD from the frequencyBandList for the downlink, where the UE supports the frequencyBandList and the UE supports at least one of the additionalSpectrumEmission values in the nr-NS-PmaxList (if present);

[0314] […]

[0315] 4> If the UE supports the uplink channel bandwidth with the maximum transmission bandwidth configuration (see TS 38.101-1

[15] and TS 38.101-2

[39] ), which

[0316] - is less than or equal to the carrierBandwidth (indicated in the supplementaryUplink of the SCS of the initial uplink BWP), and which

[0317] - Bandwidth of the initial uplink BWP that is wider than or equal to SUL:

[0318] […]

[0319] 2> Otherwise:

[0320] 3> Consider the cell as prohibited according to TS 38.304

[20] ; and

[0321] 3> Perform the prohibition as if intraFreqReselection or intraFreqReselectionRedCap for RedCap UE was set to notAllowed;

[0322] […]

[0323] - SIB1

[0324] SIB1 contains information relevant when evaluating whether to allow a UE to access the cell and defines the scheduling of other system information. It also contains radio resource configuration information common to all UEs and prohibition information applied to unified access control.

[0325] […]

[0326] Direction: Network to UE

[0327] SIB1 message

[0328] --ASN1START

[0329] --TAG-SIB1-START

[0330] SIB1::=SEQUENCE{

[0331] …

[0332] OPTIONAL, --Cond Standalone

[0333] cellAccessRelatedInfo CellAccessRelatedInfo,

[0334] connEstFailureControl ConnEstFailureControl

[0335] OPTIONAL, --Need R

[0336] si-SchedulingInfo SI-SchedulingInfo

[0337] OPTIONAL, --Need R

[0338] servingCellConfigCommon ServingCellConfigCommonSIB

[0339] OPTIONAL, --Need R

[0340] ims-EmergencySupport ENUMERATED{true}

[0341] OPTIONAL, --Need R

[0342] eCallOverIMS-Support ENUMERATED{true}

[0343] OPTIONAL, --Need R

[0344] ue-TimersAndConstants UE-TimersAndConstants

[0345] OPTIONAL, --Need R

[0346] uac-BarringInfo SEQUENCE{

[0347] uac-BarringForCommon UAC-BarringPerCatList

[0348] OPTIONAL, --Need S

[0349] uac-BarringPerPLMN-List UAC-BarringPerPLMN-List

[0350] OPTIONAL, --Need S

[0351] uac-BarringInfoSetList UAC-BarringInfoSetList,

[0352] uac-AccessCategory1-SelectionAssistanceInfo CHOICE{

[0353] plmnCommon UAC-AccessCategory1-SelectionAssistanceInfo,

[0354] individualPLMNList SEQUENCE(SIZE(2..maxPLMN))OF UAC-AccessCategory1-SelectionAssistanceInfo

[0355] }

[0356] OPTIONAL--Need S

[0357] }

[0358] OPTIONAL,--Need R

[0359] }

[0360] …

[0361] SIB1-v1630-IEs::= SEQUENCE{

[0362] uac-BarringInfo-v1630 SEQUENCE{

[0363] uac-AC1-SelectAssistInfo-r16 SEQUENCE(SIZE(2..maxPLMN))OF UAC-AC1-SelectAssistInfo-r16

[0364] }

[0365] OPTIONAL,--Need R

[0366] nonCriticalExtension SIB1-v1700-IEs

[0367] OPTIONAL

[0368] }

[0369] SIB1-v1700-IEs::= SEQUENCE{

[0370] hsdn-Cell-r17 ENUMERATED{true}

[0371] OPTIONAL,--Need R

[0372] uac-BarringInfo-v1700 SEQUENCE{

[0373] uac-BarringInfoSetList-v1700 UAC-BarringInfoSetList-v1700

[0374] }

[0375] OPTIONAL, --Cond MINT

[0376] sdt-ConfigCommon-r17 SDT-ConfigCommonSIB-r17

[0377] OPTIONAL, --Need R

[0378] redCap-ConfigCommon-r17 RedCap-ConfigCommonSIB-r17

[0379] OPTIONAL, --Need R

[0380] featurePriorities-r17 SEQUENCE {

[0381] redCapPriority-r17 FeaturePriority-r17

[0382] OPTIONAL, --Need R

[0383] slicingPriority-r17 FeaturePriority-r17

[0384] OPTIONAL, --Need R

[0385] msg3-Repetitions-Priority-r17 FeaturePriority-r17

[0386] OPTIONAL, --Need R

[0387] sdt-Priority-r17 FeaturePriority-r17

[0388] OPTIONAL--Need R

[0389] }

[0390] OPTIONAL, --Need R

[0391] si-SchedulingInfo-v1700 SI-SchedulingInfo-v1700

[0392] OPTIONAL, --Need R

[0393] hyperSFN-r17 BIT STRING(SIZE(10))

[0394] OPTIONAL, --Need R

[0395] eDRX-AllowedIdle-r17 ENUMERATED{true}

[0396] OPTIONAL, --Need R

[0397] eDRX-AllowedInactive-r17 ENUMERATED{true}

[0398] OPTIONAL, --Cond EDRX-RC

[0399] intraFreqReselectionRedCap-r17 ENUMERATED{allowed, notAllowed}

[0400] OPTIONAL, --Need S

[0401] cellBarredNTN-r17 ENUMERATED{barred, notBarred}

[0402] OPTIONAL, --Need S

[0403] …

[0404] UAC-AccessCategory1-SelectionAssistanceInfo::=ENUMERATED{a, b, c}

[0405] UAC-AC1-SelectAssistInfo-r16::=ENUMERATED{a, b, c, notConfigured}

[0406] SDT-ConfigCommonSIB-r17::= SEQUENCE{

[0407] sdt-RSRP-Threshold-r17 RSRP-Range

[0408] OPTIONAL, --Need R

[0409] sdt-LogicalChannelSR-DelayTimer-r17 ENUMERATED{sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, --Need R sdt-DataVolumeThreshold-r17 ENUMERATED{byte32, byte100, byte200, byte400, byte600, byte800, byte1000, byte2000, byte4000,

[0410] byte8000, byte9000, byte10000, byte12000, byte24000, byte48000, byte96000},

[0411] t319a-r17 ENUMERATED{ms100, ms200, ms300, ms400, ms600, ms1000, ms2000,

[0412] ms3000, ms4000, spare7, spare6, spare5, spare4, spare3, spare2, spare1}

[0413] }

[0414] RedCap-ConfigCommonSIB-r17 ::= SEQUENCE{

[0415] halfDuplexRedCapAllowed-r17 ENUMERATED{true}

[0416] OPTIONAL, --Need R

[0417] cellBarredRedCap-r17 SEQUENCE{

[0418] cellBarredRedCap1Rx-r17 ENUMERATED{barred, notBarred}, cellBarredRedCap2Rx-r17 ENUMERATED{barred, notBarred}

[0419] }

[0420] OPTIONAL, --Need R ...

[0422] }

[0423] FeaturePriority-r17::=INTEGER(0..7)

[0424] --TAG-SIB1-STOP

[0425] --ASN1STOP

[0426]

[0427]

[0428]

[0429] […]

[0430] -SI-RequestConfig

[0431] The IE SI-RequestConfig contains the configuration for SI requests based on Msg1.

[0432] SI-RequestConfig information element

[0433] --ASN1START

[0434] --TAG-SI-REQUESTCONFIG-START

[0435] SI-RequestConfig::= SEQUENCE{

[0436] rach-OccasionsSI SEQUENCE{

[0437] rach-ConfigSI RACH-ConfigGeneric,

[0438] ssb-perRACH-Occasion ENUMERATED{oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}

[0439] }

[0440] OPTIONAL, --Need R

[0441] si-RequestPeriod ENUMERATED{one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, --Need R

[0442] si-RequestResources SEQUENCE(SIZE(1..maxSI-Message)) OF SI-RequestResources

[0443] }

[0444] SI-RequestResources ::= SEQUENCE {

[0445] ra-PreambleStartIndex INTEGER(0..63),

[0446] ra-AssociationPeriodIndex INTEGER(0..15)

[0447] OPTIONAL, -- Need R

[0448] ra-ssb-OccasionMaskIndex INTEGER(0..15)

[0449] OPTIONAL -- Need R

[0450] }

[0451] --TAG-SI-REQUESTCONFIG-STOP

[0452] --ASN1STOP

[0453] Network energy savings are introduced from the perspective of the base station to save power. Energy can be saved by reducing the transmission / reception opportunities in the time domain. For example, during periods when transmission / reception is not performed, the corresponding hardware components can be completely disconnected (e.g., to reach deep sleep) so as to reduce power consumption. Therefore, from the perspective of power savings, it would be more preferable to perform / complete transmission / reception within a specific period (e.g., a compressed period) and disconnect transmission / reception outside the specific period (e.g., for a longer period). There may be a trade-off that will cause a relatively large delay because the opportunities for transmission / reception are reduced. The common signal can be the source of the always-on signal, regardless of whether there is ongoing traffic. For example, common signals (e.g., Synchronization Signal Block (SSB), Solution Set (SS) / Physical Broadcast Channel (PBCH) block, SIB1, System Information Block (SIB), paging, Physical Random Access Channel (PRACH)) are broadcast and / or can be used for all UEs in the cell, e.g., including UEs that have not yet accessed the cell. Therefore, reducing the transmission / reception of common signals will become an attractive network energy-saving solution. More details on network energy savings are discussed and provided below in 3GPP RP-234065:

[0454] The objectives of the work item are as follows:

[0455] 1. For intra-band / inter-band CA, specify procedures and signaling methods to support on-demand SSB SCell operation for connected-mode UEs configured with CA. [RAN1 / 2 / 3 / 4]

[0456] ● Specify the triggering method (selected from UE uplink wake-up signals using existing signals / channels, cell on / off indication via the backhaul, Scell activation / deactivation signaling)

[0457] ● Note 1: On-demand SSB transmission can be used by the UE for at least SCell time / frequency synchronization, L1 / L3 measurements, and SCell activation, and is supported in non-shared spectrum for FR1 and FR2.

[0458] 2. Study procedures and signaling methods to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]

[0459] ● Triggering method by using the uplink wake-up signal of existing signals / channels.

[0460] ● Wake-up signal configuration provided to the UE

[0461] - Note: Modifications to the SSB will not be discussed under this objective

[0462] ● Information exchange between gNBs, at least for the configuration of wake-up signals, when necessary.

[0463] ● Checkpoints for the normative work in RAN#105

[0464] As shown and discussed above, the non-competition-based random access procedure can be used to obtain some system information, such as other system information (OSI). OSI is SI other than the minimum SI. In other words, OSI can be SI that is not essential or not necessary or not urgent for connecting to the serving cell / base station. Therefore, for a request for OSI, the corresponding Random Access Response (RAR) is used to confirm the reception of the corresponding preamble and the random access can be successfully completed after receiving the RAR.

[0465] The base station does not need to identify the UE and / or distinguish the reason why the UE requests OSI during this random access procedure (this is because the PRACH / preamble for this non-competition-based random access procedure is shared among (all) UEs). On the other hand, when receiving a request for on-demand SIB1, more consideration needs to be given to how the base station decides whether to provide on-demand SIB1, for example, to turn on the cell or move to the normal state (e.g., higher power consumption), or not to provide on-demand SIB1, for example, to keep the cell disconnected or keep in the power saving state. For example, the base station may not want to provide on-demand SIB1 for some situations (e.g., lower priority / lower necessity / non-critical / non-urgent).

[0466] A first general concept of the present invention is to transmit information related to the purpose / reason / necessity of requesting SIB1 to a base station. The information may be a trigger for requesting SIB1. The information may be a trigger for a Radio Resource Control (RRC) procedure (e.g., an RRC connection establishment / resumption procedure) that causes the request for SIB1. The information may be an access category and / or an access identifier. The information may be the reason for an RRC procedure (e.g., an RRC connection establishment / resumption procedure) that causes the request for SIB1. The information may be establishmentCause or resumeCause. The information may be the priority (level) of requesting the first system information. The information may be the service (type) and / or traffic (type) (QoS) that triggers an RRC procedure (e.g., an RRC connection establishment / resumption procedure) that causes the request for SIB1. The information may be indicated via a preamble and / or a PRACH. The information may be indicated via a (dedicated) preamble and / or a (dedicated) PRACH in a contention-free random access procedure. The contention-free random access procedure is initiated to obtain SIB1. Different information (e.g., different purposes / reasons / triggers) may be associated with different preambles and / or different PRACHs. By detecting / receiving the preamble and / or the PRACH, the base station can obtain / receive the information and make a corresponding decision, such as whether (e.g., subsequently) to provide SIB1.

[0467] The base station may indicate the decision in the RAR. The UE may decide whether to obtain SIB1 on the serving cell based on the RAR. After obtaining SIB1, the UE may initiate another random access procedure, e.g., to establish an RRC connection or resume an RRC connection. The information may be indicated via Msg3 in a contention-based random access procedure. The contention-based random access procedure is initiated to request SIB1. The contention-based random access procedure is not initiated for RRC connection establishment or RRC connection resumption. After receiving Msg3, the base station can obtain / receive the information and make a corresponding decision, such as whether (e.g., subsequently) to provide SIB1. The base station may indicate the decision in Msg4. The UE may decide whether to obtain SIB1 on the serving cell based on Msg4. After obtaining SIB1, the UE may initiate another random access procedure, e.g., to establish an RRC connection or resume an RRC connection.

[0468] The second general concept of the present invention is to determine whether the UE is allowed to request SIB1 (e.g., on the current (residing) serving cell) based on rules / criteria (e.g., the subject purpose / reason / necessity / priority of requesting SIB1). The rules / criteria may be predefined. The UE may be notified of the rules / criteria (e.g., from a base station). The base station may inform the UE whether it is allowed to request SIB1 (e.g., on the current (residing) serving cell), for example depending on the purpose / reason / necessity / priority of requesting SIB1. The base station may inform the UE of the criteria or rules on whether to allow requesting SIB1.

[0469] The UE determines whether to request SIB1 based on a criterion / rule. The mechanism may be similar to access barring. For example, the UE may request SIB1 for some access attempts, but may not (or be prohibited from) requesting SIB1 for some other access attempts. The UE may request SIB1 for some access categories and / or some access identities, but may not (or be prohibited from) requesting SIB1 for some other access categories and / or some other access identities. The UE may request SIB1 for a purpose / reason / necessity / priority of requesting SIB1, but may not (or be prohibited from) requesting SIB1 for some other purpose / reason / necessity / priority of requesting SIB1. The UE may request SIB1 for a reason (e.g., establishmentCause or resumeCause) of an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes SIB1 to be requested, but may not (or be prohibited from) requesting SIB1 for some other reason of an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes SIB1 to be requested.

[0470] The UE determines whether to request SIB1 based on the access category and / or access identity. The UE determines whether to request SIB1 based on the purpose / reason / necessity / priority of requesting SIB1. The UE determines whether to request SIB1 based on the cause of the RRC procedure (causing the request for SIB1). The information (e.g., criterion / rule) may be information related to access barring.

[0471] The base station may provide access barring information and / or information related to access barring. The UE may determine whether to request SIB1 based on the information. The information (e.g., criteria / rules) may be indicated in the MIB / SSB. The information (e.g., criteria / rules) may be indicated in a dedicated RRC configuration or a dedicated RRC message. The information (e.g., criteria / rules) may be indicated in a release message (e.g., to release an RRC connection). The information (e.g., criteria / rules) may be indicated in a SIB1 previously acquired for a serving cell.

[0472] The base station may notify the UE of the circumstances / purpose / reason / necessity / priority when requesting SIB1 is allowed and / or the circumstances / purpose / reason / necessity / priority when requesting SIB1 is not allowed (e.g., prohibited). Since some circumstances / purpose / reason / necessity / priority prohibit requesting SIB1 (e.g., due to being less urgent / critical), the base station does not unnecessarily send on-demand SIB1. When requesting SIB1 is not allowed (e.g., on the current (staying) serving cell), the UE may select or access another serving cell. The UE may select or access another serving cell for the circumstances / purpose / reason / necessity / priority when requesting SIB1 is not allowed (e.g., on the current (staying) serving cell).

[0473] When requesting SIB1 is not allowed (e.g., on the current (staying) serving cell), the UE may perform cell selection / reselection. The UE may perform cell selection / reselection for the circumstances / purpose / reason / necessity / priority when requesting SIB1 is not allowed (e.g., on the current (staying) serving cell). For example, if the on-demand SIB1 is requested due to an access attempt, after receiving the on-demand SIB1, the access attempt may be prohibited by the on-demand SIB1, such that the UE cannot establish an RRC connection for the access attempt. Then, the on-demand SIB1 is unnecessarily triggered / transmitted, since the UE cannot access the serving cell anyway. Some additional delay is also introduced, since the UE will wait until receiving the on-demand SIB1 and realizing that it is prohibited. (e.g., and then may attempt to access another serving cell, e.g., via cell selection / reselection). With this concept, if / when an access attempt to request on-demand SIB1 is not allowed, the UE may directly access another serving cell / perform cell reselection, e.g., instead of waiting until receiving the on-demand SIB1.

[0474] A third general concept of the present invention is to request SIB1 with a randomly selected preamble and / or PRACH. The UE may randomly select a preamble and / or PRACH among a set of candidates. The UE may initiate a non-competition-based random access procedure to request SIB1. The UE may initiate a competition-based random access procedure to request SIB1. It should be noted that by detecting multiple candidates, e.g., even for a non-competition-based random access procedure, the base station is allowed to detect / estimate / determine the amount / number of UEs requesting SIB1. The base station may decide / determine whether to provide on-demand SIB1 based on the amount / number of UEs requesting SIB1.

[0475] In one embodiment, the UE transmits information to the base station. The UE transmits the information during a request for the first system information. When / If / After / Before the UE requests the first system information, the UE transmits the information to the base station. The information is related to the purpose / reason / necessity of requesting the first system information. The information may be or include a trigger for the request for the first system information. The information may be or include a trigger for an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes the request for the first system information. The information may be or include an access category and / or an access identifier. The information may be or include an access category and / or an access identifier related to an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes or triggers the request for the first system information. The information may be or include an access category and / or an access identifier provided by an upper layer to an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes or triggers the request for the first system information. The information may be or include the reason for an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes or triggers the request for the first system information. The information may be or include an establishmentCause or a resumeCause. The information may be or include the priority (level) of the request for the first system information. The information may be or include (e.g., available) data / traffic. The information may be or include (e.g., available) data / traffic of a service that causes or triggers the request for the first system information.

[0476] The information may be or include QoS (related) information. The information may be or include QoS (related) information of a service that causes or triggers the request for the first system information. The information may be or include the service (type) and / or traffic (type) (of QoS) that triggers an RRC procedure (e.g., RRC connection establishment / resumption procedure) that causes or triggers the request for the first system information. The information may be indicated via a preamble and / or a PRACH. The information may be indicated via a (dedicated) preamble and / or a (dedicated) PRACH in a non-competition-based random access procedure. The non-competition-based random access procedure is initiated to obtain SIB1. Different information (e.g., different purposes / reasons / triggers) may be associated with different preambles and / or different PRACHs.

[0477] The UE determines a preamble and / or a PRACH based on the information. The UE determines a preamble and / or a PRACH based on the information to be provided. The UE determines a preamble and / or a PRACH based on a purpose / reason / trigger / priority. The UE receives a RAR from the base station. The RAR may indicate whether the first system information is (to be) provided. The UE may decide whether to acquire the first system information on the serving cell based on the RAR. If / when the RAR indicates that the first system information is (to be) provided, the UE decides to acquire the first system information on the serving cell. If / when the RAR indicates that the first system information is not (to be) provided, the UE decides not to acquire the first system information on the serving cell.

[0478] If / when the RAR indicates that the first system information is not (to be) provided, the UE accesses another serving cell. If / when the RAR indicates that the first system information is not (to be) provided, the UE performs cell selection / reselection. The UE may acquire the first system information via the RAR. The UE may acquire the first system information via a broadcast message after receiving the RAR. After acquiring the first system information, the UE may initiate a second (e.g., another) random access procedure, e.g., to establish an RRC connection or resume an RRC connection. The information may be indicated via Msg3 in a contention-based random access procedure.

[0479] The UE transmits a preamble randomly selected from a set of preamble candidates. The UE receives a RAR in response to the transmission of the preamble. The RAR indicates a UL grant. The UE transmits information with the UL grant. The UE includes the information in the transmission based on the UL grant. The contention-based random access procedure is initiated to request the first system information. The contention-based random access procedure is only initiated to request the first system information. The contention-based random access procedure is not initiated for RRC connection establishment or RRC connection resume.

[0480] The base station may determine whether (e.g., subsequently) to provide the first system information based on the information. The base station may indicate whether the first system information is (to be) provided in Msg4 (e.g., subsequently). The UE may determine whether to acquire SIB1 on the serving cell based on Msg4. If / when Msg4 indicates that the first system information is (to be) (e.g., subsequently) provided, the UE determines to acquire the first system information on the serving cell.

[0481] If / When Msg4 indicates (e.g., subsequently) that the first system information will not be provided, the UE determines not to acquire the first system information on the serving cell. If / When Msg4 indicates (e.g., subsequently) that the first system information will not be provided, the UE accesses another serving cell. If / When Msg4 indicates (e.g., subsequently) that the first system information will not be provided, the UE performs cell selection / reselection.

[0482] The UE may acquire the first system information via Msg4. The UE may acquire the first system information via a broadcast message after receiving Msg4. After acquiring the first system information, the UE may initiate a second (e.g., another) random access procedure, e.g., to establish an RRC connection or resume an RRC connection. The first system information may be SIB1. The first system information may be basic system information. The first system information may be SSB / MIB. The first system information may be SSB / MIB on another serving cell.

[0483] In another embodiment, the UE determines whether to (be allowed to) request the first information on a cell / request the first information for a cell based on rules / criteria. The rules / criteria may be related to the purpose / reason / necessity / priority / trigger for requesting the first information or may be the purpose / reason / necessity / priority / trigger. The UE determines whether to (be allowed to) request the first information based on the purpose / reason / necessity / priority / trigger for requesting the first information. The UE determines to request the first information based on the first purpose / reason / necessity / priority / trigger. The UE determines not to request the first information based on the second purpose / reason / necessity / priority / trigger. The UE determines to access the second cell based on the second purpose / reason / necessity / priority / trigger. The UE determines to perform cell selection / reselection based on the second purpose / reason / necessity / priority / trigger. The rules / criteria may be related to access prohibition (related) information or may be access prohibition (related) information.

[0484] The UE determines whether to request the first information based on access prohibition (related) information. The UE determines to request the first information based on the first access prohibition (related) information. The UE determines not to request the first information based on the second access prohibition (related) information. The UE determines to access the second cell based on the second access prohibition (related) information. The UE determines to perform cell selection / reselection based on the second access prohibition (related) information. The access prohibition (related) information may be one or more of the following: cellBarredNTN, intraFreqReselectionRedCap, cellBarredRedCap1Rx, cellBarredRedCap2Rx, halfDuplexRedCapAllowed, cellAccessRelatedInfo, carrierBandwidth, frequencyBandList, uac-BarringInfo, uac-BarringForCommon, uac-BarringPerPLMN-List, uac-BarringInfoSetList, and / or the type of the UE, such as RedCap or NTN.

[0485] The UE determines whether to request the first information based on the access category and / or access identifier. The UE determines to request the first information based on the first access category and / or the first access identifier. The UE determines not to request the first information based on the second access category and / or the second access identifier. The UE determines to access the second cell based on the second access category and / or the second access identifier. The UE determines to perform cell selection / reselection based on the second access category and / or the second access identifier. The UE determines whether to request the first information based on the reason for the RRC procedure (e.g., the RRC connection establishment / resumption procedure). The UE determines to request the first information based on the first reason for the RRC procedure. The UE determines not to request the first information based on the second reason for the RRC procedure. The UE determines to access the second cell based on the second reason for the RRC procedure. The UE determines to perform cell selection / reselection based on the second reason for the RRC procedure. The UE determines whether to request the first information based on establishmentCause or resumeCause. The UE determines to request the first information based on the first establishmentCause (value) or the first resumeCause (value).

[0486] The UE determines not to request the first information based on the second establishmentCause (value) or the second resumeCause (value). The UE determines to access the second cell based on the second establishmentCause (value) or the second resumeCause (value). The UE determines to perform cell selection / reselection based on the second establishmentCause (value) or the second resumeCause (value).

[0487] The RRC procedure may trigger or initiate a request for the first system information. The rules or criteria may be predefined. The rules or criteria may be provided by the base station / network to the UE. The rules or criteria may be provided or indicated by a signal from the base station to the UE. The signal may be an SSB. The signal may be an MIB. The signal may be SIB1 (e.g., previously obtained). The signal may be a (dedicated) RRC message (e.g., last received in the RRC connected state). The signal may be an RRC release message. The signal may be an RRC reconfiguration message.

[0488] The UE receives information related to the rules or criteria from the base station / network. The first system information may be SIB1. The first system information may be basic system information. The first system information may be a Synchronization Signal Block (SSB) / Master Information Block (MIB). The first system information may be an SSB / MIB on another serving cell.

[0489] In another embodiment, the UE initiates a random access procedure on the serving cell to request the first system information. The random access procedure is a contention-based random access procedure. The UE selects a preamble from a set of preamble candidates. The UE randomly selects a preamble from a set of preamble candidates.

[0490] The base station detects a set of preambles. The base station can, for example, estimate / determine the number of UEs requesting the first system information based on the detection of a set of preambles. The base station can determine whether (e.g., subsequently) to provide the first system information based on the detection of a set of preambles. If / when a large number (e.g., greater than a threshold) of preambles are detected, the base station can determine (e.g., subsequently) to provide the first system information. If / when a small number (e.g., less than a threshold) of preambles are detected, the base station can determine (e.g., subsequently) not to provide the first system information. The base station can determine whether (e.g., subsequently) to provide the first system information based on the number of UEs requesting the first system information. If / when a large number (e.g., greater than a threshold) of UEs are requesting the first system information, the base station can determine (e.g., subsequently) to provide the first system information. If / when a small number (e.g., less than a threshold) of UEs are requesting the first system information, the base station can determine (e.g., subsequently) not to provide the first system information. The base station can indicate whether (e.g., subsequently) the first system information is provided in the RAR.

[0491] The UE receives a random access response to the preamble. If / when the RAR is received, the UE considers the contention-based random access procedure to be successfully completed. The RAR provides a UL grant. The RAR does not provide a UL grant. The UE transmits based on the UL grant. The UE does not transmit based on the UL grant. The RAR can indicate whether (will) the first system information is provided.

[0492] The UE can decide whether to obtain the first system information on the serving cell based on the RAR. If / when the RAR indicates (will) provide the first system information, the UE decides to obtain the first system information on the serving cell. If / when the RAR indicates (will) not provide the first system information, the UE decides not to obtain the first system information on the serving cell. If / when the RAR indicates (will) not provide the first system information, the UE accesses another serving cell. If / when the RAR indicates (will) not provide the first system information, the UE performs cell selection / reselection.

[0493] The UE can obtain the first system information via the RAR. The UE can obtain the first system information via a broadcast message after receiving the RAR. After obtaining the first system information, the UE can initiate a second (e.g., another) random access procedure, e.g., to establish an RRC connection or resume an RRC connection. The first system information can be SIB1. The first system information can be basic system information. The first system information can be SSB / MIB. The first system information can be SSB / MIB on another serving cell.

[0494] The first system information may be SIB1. The first system information may be MIB. The first system information may be the MIB for another serving cell, such as a secondary cell (SCell). If / when (e.g., currently) the first system information is not provided (e.g., in the serving cell and / or in the primary cell (PCell) of the base station), the UE initiates a random access procedure to request the first system information.

[0495] After initiating the random access procedure, the UE transmits a preamble on the serving cell. The UE receives a random access response from the base station. The random access response indicates whether the first system information will be provided (e.g., subsequently). The random access response indicates whether the request is accepted or rejected. The random access response indicates whether the request is accepted. The random access response indicates whether the base station or the serving cell will wake up. The random access response indicates whether the base station or the serving cell will wake up or remain dormant.

[0496] The UE determines whether to obtain / receive / monitor the first system information (or the physical downlink control channel (PDCCH) scheduling the first system information) based on the indication in the random access response. If / when the random access response indicates that the first system information will be provided, the UE obtains or attempts to receive the first system information (e.g., on the serving cell). If / when the random access response indicates that the request is accepted, the UE obtains or attempts to receive the first system information (e.g., on the serving cell). If / when the random access response indicates that the base station or the serving cell will wake up, the UE obtains or attempts to receive the first system information (e.g., on the serving cell).

[0497] If / when the random access response indicates that the first system information will not be provided (subsequently), the UE does not obtain or attempt to receive the first system information (e.g., on the serving cell). If / when the random access response indicates that the request is rejected or not accepted, the UE does not obtain or attempt to receive the first system information (e.g., on the serving cell). If / when the random access response indicates that the base station or the serving cell will remain dormant or will not wake up, the UE does not obtain or attempt to receive the first system information (e.g., on the serving cell).

[0498] The UE determines whether to access the serving cell based on the indication in the random access response. (Accessing the serving cell may mean establishing an (RRC) connection to the serving cell). If / when the random access response indicates that the first system information will be provided, the UE accesses the serving cell. If / when the random access response indicates that the request is accepted, the UE accesses the serving cell. If / when the random access response indicates that the base station or the serving cell will wake up, the UE accesses the serving cell. If / when the random access response indicates that the first system information will not be provided (subsequently), the UE does not access the serving cell. If / when the random access response indicates that the request is rejected or not accepted, the UE does not access the serving cell. If / when the random access response indicates that the base station or the serving cell will remain dormant or will not wake up, the UE does not access the serving cell.

[0499] If / when the random access response indicates that the first system information will not be provided (subsequently), the UE accesses another serving cell (different from the serving cell). If / when the random access response indicates that the request is rejected or not accepted, the UE accesses another serving cell (different from the serving cell). If / when the random access response indicates that the base station or the serving cell will remain dormant or will not wake up, the UE accesses another serving cell (different from the serving cell).

[0500] If / when the random access response indicates that the first system information will not be provided (subsequently), the UE performs cell selection or cell reselection. If / when the random access response indicates that the request is rejected or not accepted, the UE performs cell selection or cell reselection. If / when the random access response indicates that the base station or the serving cell will remain dormant or will not wake up, the UE performs cell selection or cell reselection.

[0501] The UE initiates a second random access procedure to request the second system information. The second system information is system information other than SIB1. The second system information is OSI. The second system information is system information scheduled by SIB1.

[0502] The UE transmits a (second) preamble to request the second system information. The UE receives a (second) random access response from the base station in response to the (second) preamble. The second random access response indicates that the (second) preamble or request has been successfully received. The second random access response does not indicate whether the second system information will be provided (e.g., subsequently). The second random access response does not indicate whether the request is accepted or rejected. The second random access response does not indicate whether the request is accepted. The second random access response does not indicate whether the base station or the serving cell will wake up. The second random access response does not indicate whether the base station or the serving cell will wake up or remain dormant. It should be noted that "does not indicate" may mean that the corresponding indication does not exist.

[0503] Upon receiving the second random access response, the UE acquires / receives / listens for the second system information (or the PDCCH scheduling the second system information). The UE does not determine whether to acquire / receive / listen for the second system information (or the PDCCH scheduling the second system information) based on the indication in the second random access response. The UE does not determine whether to access the serving cell based on the indication in the second random access response. The UE does not determine whether to access another serving cell based on the indication in the second random access response. The UE does not determine whether to perform cell reselection based on the indication in the second random access response.

[0504] The UE receives an indication of on which beam the first system information is provided and / or of which SSB (index) (e.g., SSB 0, SSB1...) the first system information is associated with. The first system information may be SIB1. The first system information may be MIB. The first system information may be the MIB of another serving cell (e.g., SCell).

[0505] The UE receives an indication of on which beam the first system information is provided and / or of which SSB (index) the first system information is associated with after requesting the first system information. The indication is indicated in the RAR. The indication is indicated in the SSB. The indication may be indicated together with and / or jointly with the indication of whether the first system information will be provided. The indication may be indicated together with and / or jointly with the indication of whether the base station will wake up. The indication may be indicated together with and / or jointly with the indication of whether the request is accepted. The indication may indicate whether the first system information is provided on a (specific / corresponding) beam and / or whether the first system information associated with a (specific / corresponding) SSB is provided. The (specific / corresponding) beam and / or the (specific / corresponding) SSB may be the beam and / or the SSB utilized and / or selected during the random access procedure (e.g., for requesting the first system information). The (specific / corresponding) beam and / or the (specific / corresponding) SSB may be the beam and / or the SSB associated with the PRACH utilized / selected in the random access procedure (e.g., for requesting the first system information).

[0506] The indication may indicate whether the first system information is provided on each of a plurality of beams and / or whether the first system information associated with each of a plurality of SSBs is provided. For example, the indication may be a bitmap in which each bit is associated with a beam and / or an SSB. The indication may be a bitmap in which each bit is associated with a set of one or more beams and / or a set of one or more SSBs.

[0507] The indication may indicate whether the first system information is provided on multiple beams and / or whether the first system information associated with multiple SSBs is provided. The multiple beams and / or the multiple SSBs may be all the beams and / or all the SSBs of a cell. The multiple beams and / or the multiple SSBs may be a subset of the beams and / or a subset of the SSBs of a cell.

[0508] Before initiating a random access procedure to request the first information, the UE may determine whether the first system information is provided by a corresponding SSB. The corresponding SSB may be the SSB with the best quality or the strongest received power. The corresponding SSB may be an SSB that can be received by the UE. The corresponding SSB may be the SSB to be selected for the random access procedure. If / when the first system information associated with the corresponding SSB is provided, the UE does not initiate a random access procedure to request the first system information. If / when the first system information associated with the corresponding SSB is not provided, the UE initiates a random access procedure to request the first system information.

[0509] The UE receives an indication of on which time occasion(s) the first system information is provided and / or what periodicity and / or what offset the first system information has and / or by which search space the first system information is scheduled. The periodicity of the first system information may be different from the periodicity of the SSB. The periodicity of the first system information may be greater than the periodicity of the SSB. The periodicity of the first system information may be a multiple of the periodicity of the SSB. For example, the indication may indicate the multiple.

[0510] The periodicity and / or offset may be relative to the time occasion of the SSB. The SSB (e.g., SSB 0 or SSB1) will be transmitted periodically if it has a periodicity. SIB1 is provided in some SSB occasion(s) of the SSB (e.g., SSB 0 or SSB1) and not in some other SSB occasion(s). For example, when the periodicity of the first system information is 4 times that of the SSB, the first system information associated with only one SSB occasion among four consecutive periodic SSB occasions (e.g., each separated by the SSB periodicity) is provided, and the first system information associated with the other three SSB occasions among the four consecutive periodic SSB occasions is not provided.

[0511] The periodicity and / or offset may indicate in which SSB period of the SSB (e.g., SSB 0 or SSB1) the first system information is provided. The periodicity and / or offset may indicate in which SSB period of the SSB (e.g., SSB 0 or SSB1) the first system information is not provided. The first system information may be SIB1.

[0512] The first system information may be the MIB. The first system information may be the MIB of another serving cell (e.g., SCell). The indication may be provided in the RAR. The indication may be provided in the RAR in response to a preamble requesting SIB1. The indication may be provided in the SSB. There may be multiple occasions / periodicity / offsets / search spaces configured, for example, by an RRC message. The indication indicates one of multiple values.

[0513] The indication may be indicated together with an indication of whether the base station will provide the first system information. The indication may be indicated separately from an indication of whether the base station will provide the first system information. The indication may be indicated together with and / or jointly with an indication of whether the first system information will be provided. The indication may be indicated together with and / or jointly with an indication of whether the base station will wake up. The indication may be indicated together with and / or jointly with an indication of whether the request is accepted. The indication may indicate that another time occasion and / or another search space (e.g., the current one) provided in the SSB / MIB is not applicable. The indication may indicate a time occasion and / or a search space that overrides another time occasion and / or another search space provided in the SSB / MIB. The UE listens / receives / obtains the first system information based on the indicated time occasion and / or search space and / or periodicity and / or offset.

[0514] It should be noted that the present invention is described based on a 4-step random access procedure, and can be adopted or extended to a 2-step random access procedure by combining Msg1 and Msg3 to form Msg A and by combining Msg2 (e.g., RAR) and Msg4 (e.g., contention resolution) to form Msg B (with some possible extensions / adjustments).

[0515] Throughout the present invention, unless otherwise indicated, the present invention describes the behavior or operation of a single serving cell.

[0516] Throughout the present invention, unless otherwise indicated, the present invention describes the behavior or operation of multiple serving cells.

[0517] Throughout the present invention, unless otherwise indicated, the present invention describes the behavior or operation of a single bandwidth part.

[0518] Throughout the present invention, unless otherwise indicated, the base station configures multiple bandwidth parts for the UE.

[0519] Throughout the present invention, unless otherwise indicated, the base station configures a single bandwidth part for the UE.

[0520] Figure 12It is a flowchart 1200 of a user equipment (UE). In step 1205, the UE initiates a random access procedure on a cell to request the first system information. In step 1210, the UE transmits information related to the reason or priority for requesting the first system information to the base station.

[0521] In one embodiment, the first system information may be SIB1. The information may be used by the base station to determine whether to provide the first system information. The information may be transmitted via Msg 1 or a preamble. The information may be transmitted via Msg 3. The information may be an access category and / or an access identifier. Specifically, the information may be the access category and / or the access identifier of the access attempt that triggers the request for the first system information. The information may be the reason for the RRC procedure. The reason may be establishmentCause or resumeCause.

[0522] In one embodiment, the RRC procedure may be an RRC connection establishment procedure or an RRC connection resume procedure. Due to the initiation of the RRC procedure, the first system information may be requested.

[0523] In one embodiment, the UE may receive an indication of whether to provide the first system information. The UE may determine whether to obtain the first system information based on the first system information. The UE may determine whether to perform cell selection / reselection based on the first system information.

[0524] Return to refer Figure 3 and 4 , in an exemplary embodiment, from the perspective of the UE. The UE 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the UE to (i) initiate a random access procedure on a cell to request the first system information, and (ii) transmit information related to the reason or priority for requesting the first system information to the base station. In addition, the CPU 308 may execute the program code 312 to perform all the above actions and steps or other actions and steps described herein.

[0525] Figure 13 It is a flowchart 1300 of a user equipment (UE). In step 1305, the UE initiates an RRC procedure, where the RRC procedure triggers a request for the first system information on a cell of the base station. In step 1310, the UE determines whether to request the first system information based on a rule.

[0526] In one embodiment, the rule may be predefined or fixed. The rule may be indicated by the base station to the UE. The rule may be based on the cause of the RRC procedure. The rule may be based on the access category and / or access identifier. The rule may be based on the priority of the request for the first system information. The rule may be based on the data or traffic volume of the service initiating the RRC procedure. The rule may be based on the QoS of the service initiating the RRC procedure.

[0527] Return for reference Figure 3 and 4 , in an exemplary embodiment, from the perspective of the UE. The UE 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the UE to (i) initiate an RRC procedure, where the RRC procedure triggers a request for the first system information on the cell of the base station, and (ii) determine whether to request the first system information based on the rule. In addition, the CPU 308 may execute the program code 312 to perform all the above actions and steps or other actions and steps described herein.

[0528] As shown and discussed above, the non-competition-based random access procedure can be used to obtain some system information, such as other system information (OSI). OSI is SI other than the minimum SI. In other words, OSI may be SI that is not essential or not necessary or not urgent for connecting to the serving cell / base station. Therefore, for requesting OSI, the corresponding RAR is used to confirm the reception of the corresponding preamble and the random access can be successfully completed after receiving the RAR. The base station does not need to identify the UE during this random access procedure (since the PRACH / preamble used for this non-competition-based random access procedure is shared among (all) UEs). On the other hand, when requesting on-demand SIB1, the UE may want to establish a connection to the cell / base station. Therefore, the UE may need to first initiate a random access procedure to request SIB1.

[0529] After completing the request, the UE will obtain SIB1 by listening for the System Information Radio Network Temporary Identifier (SI-RNTI) and receiving the corresponding scheduled SIB1. After obtaining SIB1, the UE initiates another random access procedure to establish / resume a Radio Resource Control (RRC) connection between the cell and the UE. Since two random access procedures and one System Information Block (SIB) (e.g., SIB1) acquisition procedure will be involved, there will be a significant delay.

[0530] A first general concept of the present invention is to use a single random access procedure to request SIB1 and establish / resume an RRC connection. The random access procedure can be a contention-based random access procedure. There are more than one preamble and / or PRACH resource associated with the request for system information. More than one preamble and / or PRACH resource can be associated with RRC connection establishment / resumption. These preambles and / or PRACH can indicate that the UE is requesting SIB1 and / or establishing / resuming an RRC connection.

[0531] The UE selects a preamble (e.g., among several / all candidates) and transmits the preamble to the base station. The UE receives a random access response in response to transmitting the preamble. The random access response can indicate an acknowledgement of the receipt of the SI request. The random access response can indicate that SIB1 will be provided (e.g., subsequently). The random access response can indicate an uplink (UL) grant for Msg3. The UL grant is used for the UE to transmit its identity. The UL grant is used for the UE to transmit a message for requesting RRC connection establishment or a message for requesting RRC connection resume (e.g., RRCSetupRequest / RRCResumeRequest / RRCResumeRequest1).

[0532] The UE transmits a message for requesting RRC connection establishment or a message for requesting RRC connection resume to the base station (e.g., in Msg3 and / or using the UL grant and / or within the random access procedure). The UE receives a response to the request message (e.g., RRCSetup / RRCResume / RRC Reject, e.g., in Msg4 and / or in contention resolution).

[0533] The UE transmits a completion message, such as RRCSetupComplete / RRCResumeComplete, after the (single) random access procedure. The UE completes the RRC establishment procedure / RRC resume procedure after the (single) random access procedure. The UE enters the RRC connected state after the (single) random access procedure. The UE obtains SIB1 via a broadcast message (e.g., scheduled by downlink control information (DCI) scrambled by SI-RNTI). The UE obtains SIB1 via a broadcast message after the (single) random access procedure. The UE obtains SIB1 via a dedicated RRC message (e.g., scheduled by DCI scrambled by C-RNTI / TC-RNTI). The UE obtains SIB1 via a dedicated RRC message during or after the (single) random access procedure. The UE obtains SIB1 via RAR. The UE obtains SIB1 via Msg4. The UE obtains SIB1 during the (single) random access procedure. The UE obtains SIB1 after the (single) random access procedure.

[0534] If / when SIB1 is provided, more than one preamble and / or PRACH resource may be different from the preamble / PRACH used for initiating the random access procedure. When SIB1 is provided, the first (set of) PRACH is configured for / used for initiating the random access procedure. When the random access procedure is for RRC connection establishment and / or RRC connection resume, the first (set of) PRACH is configured for / used for initiating the random access procedure. When the random access procedure is for RRC connection establishment and / or RRC connection resume and not for requesting SIB1, the first (set of) PRACH is configured for / used for initiating the random access procedure. When the random access procedure is only for RRC connection establishment and / or RRC connection resume, the first (set of) PRACH is configured for / used for initiating the random access procedure. When SIB1 is not provided, the second (set of) PRACH is configured for / used for initiating the random access procedure. When SIB1 is not provided, the second (set of) PRACH is configured for / used for initiating the random access procedure. When the random access procedure is for RRC connection establishment (and / or RRC connection resume) and for requesting SIB1, the second (set of) PRACH is configured for / used for initiating the random access procedure. When the random access procedure is for RRC connection establishment (and / or RRC connection resume) and for requesting SIB1, the second (set of) PRACH is configured for / used for initiating the random access procedure. Since a single random access procedure can achieve the purpose of requesting SIB1 and establishing / resuming the connection, the latency can be reduced, for example, compared to initiating two separate random access procedures.

[0535] A second general concept of the present invention is to provide (on demand) SIB1 to a UE in a message related to a random access procedure (or Physical Downlink Shared Channel (PDSCH)) (e.g., RAR or Msg4) or a dedicated RRC message. The UE initiates a random access procedure to request SIB1. SIB1 is provided in response to a request from the UE. SIB1 can be provided on more than one message / occasion to reduce the latency of accessing the cell.

[0536] In response to a SIB1 request, the base station provides SIB1 in the RAR or Msg4 or a dedicated RRC message. The base station provides SIB1 during the random access procedure. The base station provides SIB1 after the random access procedure. In response to a SIB1 request, the base station provides SIB1 in a broadcast message (or PDSCH) (e.g., scheduled by DCI scrambled with SI-RNTI). In response to a SIB1 request, the base station provides SIB1 in a broadcast message after the random access procedure. The base station provides SIB1 in a message related to the random access procedure (or PDSCH) and in a broadcast message (or PDSCH). The base station provides SIB1 in a message related to the random access procedure (or PDSCH) or in a broadcast message (or PDSCH). The base station indicates that SIB1 is provided in a message related to the random access procedure (or PDSCH) and / or in a broadcast message (or PDSCH). The base station provides SIB1 in a dedicated RRC message and in a broadcast message (or PDSCH). The base station provides SIB1 in a dedicated RRC message related to the random access procedure or in a broadcast message (or PDSCH). The base station indicates that SIB1 is provided in a dedicated RRC message and / or in a broadcast message (or PDSCH). Since SIB1 can be provided at multiple / different timings, the latency of obtaining SIB1 and establishing / resuming a connection can be reduced.

[0537] In one embodiment, the UE initiates a random access procedure on the serving cell to request the first system information. The UE initiates the random access procedure to establish or resume an (RRC) connection. The first system information may be the basic system information. The UE initiates the random access procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date first system information. The UE initiates the random access procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date basic system information. The UE initiates an RRC procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date first system information. The UE initiates an RRC procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date basic system information. If / when the first system information is on demand, the UE initiates an RRC procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date first system information. If / when the basic system information is on demand, the UE initiates an RRC procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date basic system information.

[0538] If / when the first system information is not on demand (e.g., the first system information is provided periodically or normally), the UE does not initiate an RRC procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date first system information. If / when the basic system information is not on demand (e.g., the basic system information is provided periodically or normally), the UE does not initiate an RRC procedure to establish or resume an (RRC) connection in the absence of valid or up-to-date basic system information.

[0539] If / when the first system information is not on demand (e.g., the first system information is provided periodically or normally), the UE initiates an RRC procedure to establish or resume an (RRC) connection after / when / upon the availability of valid or up-to-date first system information. If / when the basic system information is not on demand (e.g., the basic system information is provided periodically or normally), the UE initiates an RRC procedure to establish or resume an (RRC) connection after / when / upon the availability of valid or up-to-date basic system information. The UE initiates a random access to request the first system information and to establish or resume an (RRC) connection. The random access procedure is or may be a contention-based random access procedure. The random access procedure is not allowed to be or cannot be a non-contention-based random access procedure.

[0540] The UE selects a preamble and / or a PRACH (e.g., among several / all candidates) and transmits the preamble to the base station. The preamble and / or PRACH may indicate that the UE is requesting the first system information and / or establishing / resuming an RRC connection. The indication in the Master Information Block (MIB) / Synchronization Signal Block (SSB) indicates whether and / or how the UE may request the first system information.

[0541] The UE determines whether to initiate a random access procedure based on the indication. The UE determines whether to access / select another cell based on the indication. The UE determines whether to perform cell selection / reselection based on the indication. The UE receives a random access response in response to the transmission of the (selected) preamble and / or (selected) PRACH. The random access response may indicate an acknowledgement of the receipt of the request for the first system information. The random access response may indicate whether to accept (e.g., reject) the request (for the first system information). The random access response may include all or part of the first system information. The random access response may include information contained in or provided in the first system information.

[0542] If / when the request is accepted, the UE may continue to access the serving cell. If / when the request is not accepted or is rejected, the UE may access another serving cell. If / when the request is not accepted or is rejected, the UE may perform cell selection / reselection. The random access response may indicate whether (e.g., subsequently) the first system information will be provided. The random access response may provide the first system information. The random access response may indicate a UL grant for Msg3.

[0543] The UL grant is used for the UE to transmit its identity or identification. The UL grant is used for the UE to transmit a message for requesting RRC connection establishment or a message for requesting RRC connection resume (e.g., RRCSetupRequest / RRCResumeRequest / RRCResumeRequest1). The UL grant is used for the UE to transmit information related to the reason / purpose of the request. The UL grant is used for the UE to transmit information for the base station to determine whether to connect to the serving cell. The UL grant is used for the UE to transmit information for the base station to determine whether to provide the first system information to the serving cell. The UL grant is used for the UE to transmit information for the base station to determine whether to broadcast the first system information to the serving cell.

[0544] The UE transmits a message for requesting RRC connection establishment or a message for requesting RRC connection resume to a base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure). The UE transmits information related to the reason / purpose of the request (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure). The UE transmits information related to the QoS requirements of the (upcoming) service (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure). The UE transmits information for the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure) to determine whether to connect to the serving cell. The UE transmits information for the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure) to determine whether to provide the first system information to the serving cell. The UE transmits information for the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure) to determine whether to broadcast the first system information to the serving cell.

[0545] The UE receives a response to the request message (e.g., RRCSetup / RRCResume / RRC Reject, e.g., in Msg4 and / or in contention resolution). The response may include all or part of the first system information (e.g., in Msg4 and / or in contention resolution). The response may include information included in or provided in the first system information (e.g., in Msg4 and / or in contention resolution).

[0546] The UE transmits a completion message, such as RRCSetupComplete / RRCResumeComplete, after a (single) random access procedure. The UE completes the RRC establishment procedure / RRC resume procedure after a (single) random access procedure. The UE enters the RRC connected state after a (single) random access procedure. The UE obtains the first system information via a broadcast message (e.g., scheduled by DCI scrambled with SI-RNTI). The UE obtains the first system information via a broadcast message after a (single) random access procedure. The UE obtains the first system information via a dedicated RRC message (e.g., scheduled by DCI scrambled with C-RNTI / TC-RNTI). The UE obtains the first system information via a dedicated RRC message during or after a (single) random access procedure. The UE obtains the first system information via the RAR. The UE obtains the first system information via Msg4. The UE obtains the first system information during a (single) random access procedure. The UE obtains the first system information after a (single) random access procedure. The UE obtains the first system information and / or establishes / resumes an RRC connection during a (single) random access procedure. The UE obtains the first system information and / or establishes / resumes an RRC connection after a (single) random access procedure. The first system information may be SIB1. The first system information may be the information carried by SIB1. The first system information may be the MIB. The first system information may be the MIB on / of / for another serving cell.

[0547] In another embodiment, the base station receives / detects a preamble (e.g., on the PRACH) from the UE. The preamble and / or the PRACH are used for the UE to initiate a random access procedure to establish or resume an (RRC) connection. The preamble and / or the PRACH are used for the UE to initiate a random access to request the first system information and to establish or resume an (RRC) connection. The random access procedure is or may be a contention-based random access procedure. The random access procedure is not allowed to be or cannot be a non-contention-based random access procedure. The preamble and / or the PRACH are selected by the UE (e.g., among several / all candidates). The preamble and / or the PRACH may indicate that the UE is requesting the first system information and / or establishing / resuming an RRC connection.

[0548] The base station provides / transmits an indication in the MIB / SSB, which indicates whether and / or how the UE may request the first system information. The indication in the MIB / SSB is used for the UE to determine whether to initiate a random access procedure. The indication in the MIB / SSB is used for the UE to determine whether to access / select another cell. The indication in the MIB / SSB is used for the UE to determine whether to perform cell selection / reselection.

[0549] The base station transmits a random access response in response to the reception / detection of a (selected) preamble and / or a (selected) PRACH. The random access response may indicate an acknowledgement of the reception of a request for the first system information. The random access response may indicate whether to accept (e.g., reject) the request for the first system information. The random access response may include all or part of the first system information. The random access response may include information contained in or provided in the first system information. If / when the request is accepted, the base station may provide the first system information to the serving cell. If / when the request is accepted, the base station may broadcast the first system information to the serving cell.

[0550] If / when the request is accepted, the UE may continue to access the serving cell. If / when the request is not accepted or is rejected, the UE may access another serving cell. If / when the request is not accepted or is rejected, the UE may perform cell selection / reselection. The random access response may indicate whether the first system information will be (e.g., subsequently) provided. The random access response may provide the first system information. The random access response may indicate a UL grant for Msg3.

[0551] The UL grant is used for the UE to transmit its identity or identification. The UL grant is used for the UE to transmit a message for requesting RRC connection establishment or a message for requesting RRC connection resume (e.g., RRCSetupRequest / RRCResumeRequest / RRCResumeRequest1). The UL grant is used for the UE to transmit information related to the reason / purpose of the request. The UL grant is used for the UE to transmit information for the base station to determine whether to connect to the serving cell. The UL grant is used for the UE to transmit information for the base station to determine whether to provide the first system information to the serving cell. The UL grant is used for the UE to transmit information for the base station to determine whether to broadcast the first system information to the serving cell.

[0552] The base station receives from the UE a message for requesting RRC connection establishment or a message for requesting RRC connection resume to the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure). The base station receives information related to the reason / purpose of the request (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure). The base station receives information related to the QoS requirements of the (upcoming) service (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure). The base station receives information for the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure) to determine whether to connect to the serving cell. The base station receives information for the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure) to determine whether to provide the first system information to the serving cell. The base station receives information for the base station (e.g., in Msg3 and / or by using UL grant and / or within a random access procedure) to determine whether to broadcast the first system information to the serving cell.

[0553] The base station transmits a response to the request message (e.g., RRCSetup / RRCResume / RRC Reject) e.g., in Msg4 and / or in contention resolution. The response may include all or part of the first system information (e.g., in Msg4 and / or in contention resolution). The response may include information contained in or provided in the first system information (e.g., in Msg4 and / or in contention resolution). The base station receives a completion message, e.g., RRCSetupComplete / RRCResumeComplete, after a (single) random access procedure.

[0554] The UE completes the RRC establishment procedure / RRC resume procedure after a (single) random access procedure. The UE enters the RRC connected state after a (single) random access procedure.

[0555] The base station provides the first system information via a broadcast message (e.g., scheduled by DCI scrambled with SI-RNTI). The base station provides the first system information via a broadcast message after a (single) random access procedure. The base station provides the first system information via a dedicated RRC message (e.g., scheduled by DCI scrambled with C-RNTI / TC-RNTI). The base station provides the first system information via a dedicated RRC message during and / or after a (single) random access procedure. The base station provides the first system information via a RAR. The base station provides the first system information via Msg4. The base station provides the first system information during a (single) random access procedure. The base station provides the first system information after a (single) random access procedure. The base station provides the first system information and / or establishes / resumes an RRC connection for the UE during a (single) random access procedure. The base station provides the first system information and / or establishes / resumes an RRC connection for the UE after a (single) random access procedure. The first system information may be SIB1. The first system information may be the information carried by SIB1. The first system information may be MIB. The first system information may be the MIB on / of / for another serving cell.

[0556] In another embodiment, the UE initiates a random access procedure on a serving cell to request the first system information. An indication in the MIB / SSB indicates whether and / or how the UE may request the first system information. The UE determines whether to initiate a random access procedure based on the indication. The UE determines whether to access / select another cell based on the indication. The UE determines whether to perform cell selection / reselection based on the indication.

[0557] The UE transmits a preamble and / or receives a random access response in the PRACH. The random access response may indicate an acknowledgement of the receipt of the request for the first system information. The random access response indicates how the first system information is provided. The random access response indicates which one or more of the following provides the first system information: RAR, Msg4, broadcast message / PDSCH, and / or dedicated RRC message. The random access response indicates how the first system information is provided. The random access response indicates which one or some or all of the following provides the first system information: RAR, Msg4, broadcast message / PDSCH, and / or dedicated RRC message. The random access response indicates that the first system information is provided by RAR or broadcast message / PDSCH.

[0558] The random access response may indicate whether to accept (e.g., reject) a request (for the first system information). The random access response may include all or part of the first system information. The random access response may include information contained in or provided in the first system information. The random access response may indicate whether the first system information will be (e.g., subsequently) provided. The random access response may provide the first system information. The random access response may indicate a UL grant for Msg3. The random access response may not indicate a UL grant for Msg3. The random access procedure may be a contention-based random access procedure. The random access procedure may be a non-contention-based random access procedure.

[0559] The UE obtains the first information based on the RAR. The UE obtains the first system information via a broadcast message (e.g., scheduled by DCI scrambled with SI-RNTI). If / when the RAR indicates that the first information is provided via a broadcast message (e.g., scheduled by DCI scrambled with SI-RNTI) / PDSCH, the UE obtains the first system information via a broadcast message. The UE obtains the first system information via a broadcast message after the random access procedure. The UE obtains the first system information via a dedicated RRC message (e.g., scheduled by DCI scrambled with C-RNTI / TC-RNTI). If / when the RAR indicates that the first information is provided via a dedicated RRC message (e.g., scheduled by DCI scrambled with C-RNTI / TC-RNTI), the UE obtains the first system information via a dedicated RRC message. The UE obtains the first system information via a dedicated RRC message during or after the random access procedure. The UE obtains the first system information via the RAR. If / when the RAR indicates that the first information is provided via the RAR, the UE obtains the first system information via the RAR. The UE obtains the first system information via Msg4. If / when the RAR indicates that the first information is provided via Msg4, the UE obtains the first system information via Msg4. The UE obtains the first system information during the random access procedure. The UE obtains the first system information after the random access procedure. The first system information may be SIB1. The first system information may be the information carried by SIB1. The first system information may be MIB. The first system information may be the MIB on / of / for another serving cell.

[0560] Figure 14It is a flowchart 1400 of a User Equipment (UE). In step 1405, the UE initiates a random access procedure to request the first system information, where the random access procedure is a contention-based random access procedure. In step 1410, the UE transmits Msg3 in the random access procedure, where the Msg3 includes a message for requesting RRC connection establishment or a message for requesting RRC connection resume.

[0561] In one embodiment, the first system information may be SIB1. The UE may initiate a random access procedure to establish or resume an RRC connection. The UE may request the first system information and request to establish or resume an RRC connection within a single random access procedure. The UE may select a preamble and / or PRACH for the random access procedure. The UE may select, among the preamble and / or PRACH, a preamble and / or PRACH that can be used to request the first system information and can be used for RRC connection establishment or resume.

[0562] In one embodiment, the RAR of the random access procedure may indicate or include an uplink grant for a message for requesting RRC connection establishment or a message for requesting RRC connection resume. The RAR of the random access procedure may indicate whether and / or how the first system information will be provided.

[0563] In one embodiment, the UE may receive RRCSetup / RRCResume / RRC Reject in Msg4 of the random access procedure. The UE may transmit a completion message after the random access procedure. The UE may obtain the first information during the random access procedure. The UE may obtain the first information in the RAR or Msg4 of the random access procedure. The UE may obtain the first information in a broadcast message. The UE may obtain the first information after the random access procedure. The UE may obtain the first information after establishing or resuming an RRC connection.

[0564] Return for reference Figure 3 and 4 , in an exemplary embodiment, from the perspective of the UE. The UE 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the UE to (i) initiate a random access procedure to request the first system information, where the random access procedure is a contention-based random access procedure, and (ii) transmit Msg3 in the random access procedure, where the Msg3 includes a message for requesting RRC connection establishment or a message for requesting RRC connection resume. In addition, the CPU 308 may execute the program code 312 to perform all the above actions and steps or other actions and steps described herein.

[0565] Figure 15 It is the flowchart 1500 of a User Equipment (UE). In step 1505, the UE determines whether to initiate a random access procedure on a cell to request SIB1 based on information related to access prohibition.

[0566] In one embodiment, the information related to access prohibition includes the type of the UE. The type of the UE includes whether the UE is a RedCap UE and / or whether the UE is a Non-terrestrial network (NTN) UE. The information related to access prohibition can be provided by the base station.

[0567] In one embodiment, if a first value of the information related to access prohibition is provided, the UE may initiate a random access procedure to request SIB1. The first value of the information related to access prohibition indicates that the UE may not be prohibited and / or may indicate that the UE is allowed to access the cell. If the information related to access prohibition indicates that the UE may not be prohibited and / or may indicate that the UE is allowed to access the cell, the UE may initiate a random access procedure to request SIB1. If a second value of the information related to access prohibition is provided, the UE may not initiate a random access procedure to request SIB1. The second value of the information related to access prohibition indicates that the UE may be prohibited and / or may indicate that the UE is not allowed to access the cell. If the second value of the information related to access prohibition indicates that the UE may be prohibited and / or may indicate that the UE is not allowed to access the cell, the UE may not initiate a random access procedure to request SIB1.

[0568] In one embodiment, if the UE does not initiate a random access procedure to request SIB1, the UE may perform cell selection. The information related to access prohibition includes one or more of intraFreqReselectionRedCap and / or cellBarredNTN.

[0569] Return to refer Figure 3 and 4 , in an exemplary embodiment, from the perspective of the UE. The UE 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the UE to determine whether to initiate a random access procedure on a cell to request SIB1 based on information related to access prohibition. In addition, the CPU 308 can execute the program code 312 to perform all the above actions and steps or other actions and steps described herein.

[0570] The various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will appreciate that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of the aspects set forth herein can be used to implement an apparatus or practice a method. Additionally, such an apparatus or method can be implemented using other structures, functionality, or a combination of structures and functionality other than or different from one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on a time-hopping sequence. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and a time-hopping sequence.

[0571] Those skilled in the art will understand that any of a variety of different technologies and techniques can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0572] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both designed using source coding or some other technique), various forms of program or design code incorporating instructions (for convenience, which may be referred to herein as "software" or "software modules"), or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have generally been described above in terms of their functionality. Whether this functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0573] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC may include a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or in both cases. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0574] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example instance of a method. It should be understood that, based on design preferences, the specific order or hierarchy of steps in a process may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an example order and are not intended to be limited to the specific order or hierarchy presented.

[0575] The steps of a method or algorithm described in connection with the aspects disclosed herein can be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. Software modules (e.g., including executable instructions and associated data) and other data can reside in a data memory, such as a RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor") such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium can be integral with the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can reside in the user device as discrete components. Additionally, in some aspects, any suitable computer program product can include a computer-readable medium that includes code associated with one or more of the aspects of the present disclosure. In some aspects, the computer program product can include packaging material.

[0576] Although the invention has been described in connection with various aspects, it is understood that the invention is capable of further modification. This application is intended to cover any variations, uses, or adaptations of the invention, which generally follow the principles of the invention and include such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains.

Claims

1. A method for a user equipment, characterized in that, Comprising: The user equipment determines whether to initiate a random access procedure on a cell to request SIB1 based on information related to access prohibition.

2. The method according to claim 1, wherein The information related to access prohibition includes the type of the user equipment.

3. The method according to claim 2, characterized in that The type of the user equipment includes whether the user equipment is a RedCap user equipment and / or whether the user equipment is a non-terrestrial network user equipment.

4. The method according to claim 1, wherein The information related to access prohibition is provided by the base station.

5. The method according to claim 4, characterized in that, If a first value of the information related to access prohibition is provided, the user equipment initiates the random access procedure to request SIB1.

6. The method according to claim 4, characterized in that, If the information related to access prohibition indicates that the user equipment is not prohibited and / or indicates that the user equipment is allowed to access the cell, the user equipment initiates the random access procedure to request SIB1.

7. The method according to claim 4, characterized in that, If a second value of the information related to access prohibition is provided, the user equipment does not initiate the random access procedure to request SIB1.

8. The method according to claim 4, wherein If the information related to access prohibition indicates that the user equipment is prohibited and / or indicates that the user equipment is not allowed to access the cell, the user equipment does not initiate the random access procedure to request SIB1.

9. The method according to claim 7, wherein If the user equipment does not initiate the random access procedure to request SIB1, the user equipment performs cell selection.

10. The method according to claim 1, wherein The information related to access prohibition includes one or more of intraFreqReselectionRedCap and / or cellBarredNTN.

11. A user equipment, characterized in that, Comprising: A control circuit; A processor installed in the control circuit; And A memory installed in the control circuit and operably coupled to the processor; Wherein the processor is configured to execute program code stored in the memory to: Determine whether to initiate a random access procedure on a cell to request SIB1 based on information related to access prohibition.

12. The user equipment according to claim 11, wherein The information related to access prohibition includes the type of the user equipment.

13. The user equipment according to claim 12, characterized in that, The type of the user equipment includes whether the user equipment is a RedCap user equipment and / or whether the user equipment is a non-terrestrial network user equipment.

14. The user equipment according to claim 12, characterized in that, The information related to access prohibition is provided by the base station.

15. The user equipment according to claim 14, characterized in that, The processor is further configured to execute program code stored in the memory to: Initiate the random access procedure to request SIB1 if a first value of the information related to access prohibition is provided.

16. The user equipment according to claim 14, characterized in that, The processor is further configured to execute program code stored in the memory to: Initiate the random access procedure to request SIB1 if the information related to access prohibition indicates that the user equipment is not prohibited and / or indicates that the user equipment is allowed to access the cell.

17. The user equipment according to claim 14, characterized in that, The processor is further configured to execute program code stored in the memory to: Not initiate the random access procedure to request SIB1 if a second value of the information related to access prohibition is provided.

18. The user equipment according to claim 14, characterized in that, The processor is further configured to execute program code stored in the memory to: If the access prohibition-related information indicates that the user equipment is prohibited and / or indicates that the user equipment is not allowed to access the cell, the random access procedure for requesting SIB1 is not initiated.

19. The user equipment according to claim 17, wherein The processor is further configured to execute program code stored in the memory to: If the user equipment does not initiate the random access procedure for requesting SIB1, perform cell selection.

20. The user equipment according to claim 11, wherein The access prohibition-related information includes one or more of intraFreqReselectionRedCap and / or cellBarredNTN.

Images