Method and apparatus for energy saving in a wireless communication system

Abstract

The invention discloses a method and device for user equipment. In one embodiment, a user equipment receives an indication on a synchronization signal block having a synchronization signal block index indicating whether to provide or broadcast first system information. The user equipment also determines whether to initiate a random access procedure on the serving cell to request the first system information based on the indication.

Description

[0001] Cross - reference to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 617,474, filed on January 4, 2024, the entire disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to wireless communication networks, and more particularly to a method and apparatus for energy saving 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-borne voice, multimedia, multicast, and on-demand communication services for users of mobile communication devices.

[0005] An exemplary network architecture 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-borne voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) new radio technologies. Therefore, 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] A method and apparatus for a user equipment (UE) are disclosed. In one embodiment, the UE receives an indication on a Synchronization Signal Block (SSB) having an SSB index indicating whether to provide or broadcast first system information. The UE also determines whether to initiate a random access procedure on a serving cell to request the first system information based on the indication. Brief Description of the Drawings

[0007] Figure 1 A diagram showing a wireless communication system according to an exemplary embodiment.

[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) according to an exemplary embodiment.

[0009] Figure 3 Is a functional block diagram of a communication system according to an exemplary embodiment.

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

[0011] Figure 5 is the reproduction of 3GPP TS 38.211 V15.7.0 Figure 4 .3.1 - 1.

[0012] Figure 6 is the reproduction of Table 8.2 - 1 of 3GPP TS 38.213 V18.0.0.

[0013] Figure 7 is the reproduction of Table 8.2 - 2 of 3GPP TS 38.213 V18.0.0.

[0014] Figure 8 is the reproduction of Table 13 - 16 of 3GPP TS 38.213 V18.0.0.

[0015] Figure 9 is the reproduction of Table 13 - 17 of 3GPP TS 38.213 V18.0.0.

[0016] Figure 10 is a flowchart according to an exemplary embodiment.

[0017] Figure 11 is a flowchart according to an exemplary embodiment.

[0018] Figure 12 is a flowchart according to an exemplary embodiment. Detailed implementation manner

[0019] 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 can 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.

[0020] Specifically, the exemplary wireless communication systems and devices described below can be designed to support one or more standards, such as those provided by an alliance called the "Third Generation Partnership Project" herein referred to as 3GPP, including: TS38.211V15.7.0, "NR; Physical Channels and Modulation (Release 15)"; TS 38.213V18.0.0, "NR; Physical Layer Procedures for Control (Release 18)"; TS 38.321V17.6.0, "NR; Medium Access Control (MAC) Protocol Specification (Release 17)"; TS38.331V17.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 herein by reference in their entirety.

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

[0022] Each antenna group and / or the antenna groups are designed to communicate in an area that 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.

[0023] In the communications on the forward links 120 and 126, the transmitting antennas of the access network 100 may utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Additionally, 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 dispersed in its coverage area causes less interference to access terminals in adjacent cells.

[0024] The access network (AN) may be a fixed station or a base station for communicating with terminals and may 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) may also be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0025] Figure 2 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 number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0026] In one embodiment, each data stream is transmitted via a respective transmit antenna. The TX data processor 214 formats, encodes, and interleaves the traffic data of the data stream based on a specific decoding scheme selected for each data stream to provide encoded data.

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

[0028] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then provides N T streams of modulation symbols to N T transmitters (TMTR) 222a through 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and the antennas from which the symbols are transmitted.

[0029] Each transmitter 222 receives and processes the respective symbol stream to provide one or more analog signals and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via the MIMO channel. The N T modulated signals from transmitters 222a through 222t are then transmitted from N T antennas 224a through 224t, respectively.

[0030] At the receiver system 250, the transmitted modulated signals are received by N R antennas 252a through 252r, and the signals received from each antenna 252 are provided to respective receivers (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) the respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a respective "received" symbol stream.

[0031] The RX data processor 260 then receives and processes the N R received symbol streams from the N R receivers 254 based on specific receiver processing techniques to provide NT A "detected" symbol stream. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data of 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.

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

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

[0034] At the transmitter system 210, the modulated signal from the receiver system 250 is 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.

[0035] Steering Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As Figure 3 shown, the UE (or AT) 116 and 122 in Figure 1 or the base station (or AN) 100 in Figure 1 can be implemented using the communication device 300 in a wireless communication system, 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 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (such as a keyboard or keypad), and can output images and sounds via the output device 304 (such as a monitor 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 UE (or AT) 116 and 122 in Figure 1AN 100 in

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

[0037] The frame structure is used in the new radio access technology (NR) for 5G to accommodate various types of requirements for time and frequency resources (as discussed in 3GPP TS 38.211 V15.7.0), such as from ultra-low latency (~0.5 ms) to delay-tolerant services for machine type communication (MTC), from high peak rates for enhanced mobile broadband (eMBB) to very low data rates for MTC. The focus of this study is on the low-latency aspect, such as short transmission time intervals (TTIs), while other aspects of hybrid / adapting different TTIs can also be considered in the study. In addition to different services and requirements, forward compatibility is also an important consideration in the initial NR frame structure design because not all features of NR are included in the initial stage / releases.

[0038] More details on NR frame structure, channels, and basic parameter design are discussed and provided in 3GPP TS 38.211 below:

[0039] 4.3 Frame Structure

[0040] 4.3.1 Frames and Subframes

[0041] Downlink and uplink transmissions are organized into frames with a duration of T f =(Δf max N f / 100)×T c =10 ms, and each frame is composed of ten subframes with a duration of T sf =(Δf max N f / 1000)·T c =1 ms. The number of consecutive OFDM symbols per subframe is Each frame is divided into two equal-sized half-frames of five subframes, each with a half-frame 0 composed of subframes 0 - 4 and a half-frame 1 composed of subframes 5 - 9.

[0042] On a carrier, there is a set of frames in the uplink and a set of frames in the downlink.

[0043] The uplink frame number i transmitted from the UE will start T before the start of the corresponding downlink frame at the UE TA =(N TA +N TA,偏移 )T c where N TA,偏移 is given by [5, TS 38.213].

[0044] [Reproduced from 3GPP TS

[0045] 38.211 V15.7.0, section 3.1-1, entitled "Uplink-downlink timing relation" Figure 4 .3.1-1 as Figure 5

[0046] 4.3.2 Time slots

[0047] For a subcarrier spacing configuration μ, time slots are numbered in increasing order within a subframe as and in increasing order within a frame as There are consecutive OFDM symbols in a time slot, where depends on the cyclic prefix given in Tables 4.3.2-1 and 4.3.2-2. The start of a time slot in a subframe is aligned in time with the start of the OFDM symbols in the same subframe .

[0048] The OFDM symbols in a time slot can be classified as 'downlink', 'flexible' or 'uplink'. Signalling of the time slot format is described in subclause 11.1 of [5, TS 38.213].

[0049] In the time slots in a downlink frame, the UE will assume that downlink transmissions occur only in 'downlink' or 'flexible' symbols.

[0050] In the time slots in an uplink frame, the UE will transmit only in 'uplink' or 'flexible' symbols.

[0051] ​UEs that are not capable of full-duplex communication and do not support simultaneous transmission and reception as defined by the parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306] between all cells within a cell group are not expected to transmit in an uplink in a cell within the cell group earlier than N after the end of the last received downlink symbol in the same or a different cell within the cell group Rx-Tx T c where N Rx-Tx is given by Table 4.3.2-3

[0052] UEs that are not capable of full-duplex communication and do not support simultaneous transmission and reception as defined by the parameters simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCA, or simultaneousRxTxSUL [10, TS 38.306] between all cells within a cell group are not expected to receive in a downlink in a cell within the cell group earlier than N after the end of the last transmitted uplink symbol in the same or a different cell within the cell group Tx-Rx T c where N Tx-Rx is given by Table 4.3.2-3

[0053] UEs that are not capable of full-duplex communication are not expected to transmit in an uplink earlier than N after the end of the last received downlink symbol in the same cell Rx-Tx T c where N Rx-Tx is given by Table 4.3.2-3

[0054] UEs that are not capable of full-duplex communication are not expected to receive in a downlink earlier than N after the end of the last transmitted uplink symbol in the same cell Tx-Rx T c where N Tx-Rx is given by Table 4.3.2-3

[0055] 4.4.4 Resource blocks

[0056] 4.4.4.1 General description

[0057] A resource block is defined as consecutive subcarriers in the frequency domain

[0058] 4.4.4.2 Point A

[0059] Point A serves as a common reference point for the resource block grid and is obtained from the following:

[0060] - offsetToPointA for the PCell downlink, where offsetToPointA represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, the lowest subcarrier having a subcarrier spacing provided by the higher layer parameter subCarrierSpacingCommon and overlapping with the SS / PBCH block used by the UE for initial cell selection, expressed in terms of resource blocks, assuming a subcarrier spacing of 15 kHz for FR1 and 60 kHz for FR2;

[0061] - absoluteFrequencyPointA for all other cases, where absoluteFrequencyPointA represents the frequency position of point A, expressed in ARFCN.

[0062] 4.4.4.3 Common resource blocks

[0063] For the subcarrier spacing configuration μ, the common resource blocks are numbered upwards from 0 in the frequency domain. The center of subcarrier 0 of common resource block 0 for the subcarrier spacing configuration μ coincides with "point A".

[0064] Numbering of common resource blocks in the frequency domain for the subcarrier spacing configuration μ The relationship with the resource element (k, l) is given by the following formula

[0065]

[0066] where k is defined relative to point A such that k = 0 corresponds to the subcarrier centered at point A.

[0067] 4.4.4.4 Physical resource blocks

[0068] The physical resource blocks for the subcarrier configuration μ are defined and numbered from 0 to where i is the number of the bandwidth part. The physical resource blocks in bandwidth part i and the common resource blocks The relationship between them is given by the following formula

[0069]

[0070] where is the common resource block, where the bandwidth part starts relative to common resource block 0. When there is no risk of confusion, the index μ can be omitted.

[0071] 4.4.4.5 Virtual resource blocks

[0072] The virtual resource blocks are defined and numbered from 0 to within the bandwidth part where i is the number of the bandwidth part.

[0073] 4.4.5 Bandwidth part

[0074] A bandwidth part is a subset of contiguous common resource blocks for a given base parameter μ in bandwidth part i on a given carrier. The starting position i and the resource block number in a bandwidth part shall satisfy and The configuration of the bandwidth part is described in clause 12 of [5, TS 38.213].

[0075] The UE may be configured with up to four bandwidth parts in the downlink, with a single downlink bandwidth part active at a given time. The UE is not expected to receive PDSCH, PDCCH or CSI-RS (except for RRM) outside the active bandwidth part.

[0076] The UE may be configured with up to four bandwidth parts in the uplink, with a single uplink bandwidth part active at a given time. If the UE is configured with supplementary uplink, the UE may additionally be configured with up to four bandwidth parts in the supplementary uplink, with a single supplementary uplink bandwidth part active at a given time. The UE shall not transmit PUSCH or PUCCH outside the active bandwidth part. For an active cell, the UE shall not transmit SRS outside the active bandwidth part.

[0077] Unless otherwise indicated, the descriptions in this specification apply to each of the bandwidth parts. When there is no risk of confusion, the index μ may be omitted from and omitted.

[0078] Random access procedures are introduced for several purposes, e.g., to obtain uplink (UL) synchronization (e.g., timing advance (UL TA)), to request UL grant resources, to recover from beamforming failures, etc. Random access procedures can be classified as contention-based random access procedures and non-contention-based random access procedures. For non-contention-based random access procedures, a dedicated preamble (and dedicated physical random access channel (PRACH) resources) is assigned 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., for requesting system information, it is not necessary to identify the UE). The UE will then listen for a random access response from the base station. When a random access response to the transmitted preamble is received / if a random access response to the transmitted preamble is received, the non-contention-based random access procedure is considered to be successfully completed. On the other hand, for contention-based random access procedures, 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 listen for 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 Msg3, the UE will listen for contention resolution (e.g., Msg 4). If a contention resolution for the UE is successfully received, the UE will consider the random access procedure to be successfully completed.

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

[0080] 8 Random access procedures

[0081] Before initiating a physical random access procedure, layer 1 receives a set of SS / PBCH block indices from a higher layer and provides the corresponding set of RSRP measurements to the higher layer.

[0082] Before initiating a physical random access procedure, layer 1 may receive an indication from a higher layer to perform a type 1 random access procedure as described in clauses 8.1 to 8.4 or a type 2 random access procedure as described in clauses 8.1 to 8.2A.

[0083] Before initiating a physical random access procedure, layer 1 receives the following information from a higher layer:

[0084] - Configuration of physical random access channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission).

[0085] - Parameters for determining the root sequence and its cyclic shift in the PRACH preamble sequence set (index of the logical root sequence list, cyclic shift (N CS ) and set type (unrestricted, restricted set A, or restricted set B)).

[0086] From the perspective of the physical layer, the type 1 L1 random access procedure includes the transmission of a random access preamble (Msg1) in the PRACH, the transmission of a random access response (RAR) message (Msg2) with PDCCH / PDSCH, and, when applicable, the transmission of PUSCH scheduled by the RAR UL grant and PDSCH for contention resolution.

[0087] From the perspective of the physical layer, the type 2 L1 random access procedure includes the transmission of a random access preamble and PUSCH (MsgA) in the PRACH and the reception of an RAR message (MsgB) with PDCCH / PDSCH, and, when applicable, the transmission of PUSCH scheduled by the fallback RAR UL grant and PDSCH for contention resolution.

[0088] If the random access procedure is initiated by a PDCCH command to the UE, the PRACH transmission has the same SCS as the PRACH transmission initiated by the higher layer.

[0089] If the UE is configured with two UL carriers for the serving cell and the UE detects a PDCCH command, the UE uses the UL / SUL indicator field value from the detected PDCCH command to determine the UL carrier for the corresponding PRACH transmission.

[0090] 8.1 Random access preamble

[0091] After a request for PRACH transmission from the higher layer or a PDCCH command for the cell, a physical random access procedure for the UE is triggered. The configuration by the higher layer for PRACH transmission includes the following:

[0092] - Configuration for PRACH transmission on the cell [4, TS 38.211].[[]END]]

[0093] - Preamble index, preamble SCS, P PRACH,目标 , the corresponding RA-RNTI when applicable [11, TS 38.321], and the PRACH resources for the cell.

[0094] - Number of PRACH transmissions in the case where the UE will repeat the PRACH transmission The preamble is repeated.

[0095] The UE uses the selected PRACH format with the transmitted power P on the indicated PRACH resource or on the determined resource in the case of the preamble being repeated. PRACH,b,f,c (i) Transmits the PRACH in the cell as described in Clause 7.4.

[0096] For a Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with a PRACH occasion and the number R of contention-based preambles of each SS / PBCH block index for each valid PRACH occasion according to ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0097] For a Type 2 random access procedure having the same PRACH occasion configuration as the Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with a PRACH occasion and the number Q of contention-based preambles of each SS / PBCH block index for each valid PRACH occasion according to msgA-CB-PreamblesPerSSB-PerSharedRO. For the UE provided with a PRACH mask index according to [11, TS 38.321] based on msgA-SSB-SharedRO-MaskIndex, the PRACH transmission can be on a subset of the PRACH occasions associated with the same SS / PBCH block index within the SSB-RO mapping cycle.

[0098] For a Type 2 random access procedure having a separate PRACH occasion configuration from the Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with a PRACH occasion and the number R of contention-based preambles of each SS / PBCH block index for each valid PRACH occasion according to msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB (when provided; otherwise, according to ssb-perRACH-OccasionAndCB-PreamblesPerSSB).

[0099] For a Type 1 random access procedure, or for a Type 2 random access procedure with a PRACH occasion configuration separate from that of the Type 1 random access procedure, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH occasions, and each valid PRACH occasion has R contention-based preambles with consecutive indices associated with the SS / PBCH block index starting from preamble index 0. If N ≥ 1, each valid PRACH occasion has R contention-based preambles with consecutive indices associated with the SS / PBCH block index n (0 ≤ n ≤ N - 1) starting from 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 PRACH occasion configuration separate from that of the Type 1 random access procedure, and is an integer multiple of N.

[0100] For a Type 2 random access procedure with a PRACH occasion configuration common to that of the Type 1 random access procedure, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH occasions, and each valid PRACH occasion has Q contention-based preambles with consecutive indices associated with the SS / PBCH block index starting from preamble index R. If N ≥ 1, each valid PRACH occasion has Q contention-based preambles with consecutive indices associated with the SS / PBCH block index n (0 ≤ n ≤ N - 1) starting from preamble index starting, where is provided by totalNumberOfRA-Preambles for the Type 1 random access procedure.

[0101] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon are mapped to valid PRACH occasions in the following order, where the parameters are described in [4, TS 38.211].

[0102] - First, in ascending order of preamble indices within a single PRACH occasion

[0103] - Second, in ascending order of frequency resource indices for frequency-multiplexed PRACH occasions

[0104] - Third, in ascending order of time resource indices for time-multiplexed PRACH occasions within a PRACH slot

[0105] - Fourth, in ascending order of the index for the PRACH time slot

[0106] The association period for mapping the SS / PBCH block index to the PRACH occasion starting from frame 0 is the smallest integer in the set determined by the PRACH configuration period according to Table 8.1-1 such that the number of SS / PBCH block indices are mapped to the PRACH occasion at least once within the association period, where the UE obtains the value of ssb-PositionsInBurst from SIB1 or ServingCellConfigCommon If, after an integer number of SS / PBCH block indices in the PRACH occasion mapping cycle within the association period, there is a set of PRACH occasions or preambles that are not mapped to the number of SS / PBCH block indices, then no SS / PBCH block index is mapped to the set of PRACH occasions or preambles. The association pattern period contains one or more association periods and is determined such that the pattern between the PRACH occasion and the SS / PBCH block index repeats at most every 160 msec. PRACH occasions that are not associated with the SS / PBCH block index after an integer number of association periods (if any) are not used for PRACH transmission.

[0107] For PRACH transmission triggered by the higher layers, if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH occasion for PRACH transmission, where the PRACH occasion is associated with the selected SS / PBCH block index.

[0108] […]

[0109] For PRACH transmission triggered after a request from the higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList [12, TS 38.331] indicates a list of PRACH occasions for PRACH transmission, where the PRACH occasion is associated with the selected CSI-RS index indicated by csi-RS. The index of the PRACH occasion indicated by ra-OccasionList is reset every association pattern period.

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

[0111] In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI during a window controlled by the higher layers [11, TS 38.321]. The window starts at the first symbol of the earliest CORESET in which the UE is configured to receive the PDCCH for the Type1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set as defined in clause 10.1. If as defined in [4, TS 38.211] or is non-zero, the window starts after an additional T TA +k mac msec, where T TA is defined in [4, TS 38.211], and k mac is provided by kmac or k mac = 0 if kmac is not provided. Based on the SCS for the Type1-PDCCH CSS set, the length of the window in a number of time slots is provided by ra-ResponseWindow.

[0112] If the UE detects DCI format 1_0 with a 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 a transport block in the corresponding PDSCH within the window, the UE passes the transport block to the higher layers. The higher layers parse the transport block to obtain the random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in the RAR message of the transport block, the higher layers indicate an uplink grant to the physical layer. This is called the random access response (RAR) UL grant in the physical layer.

[0113] If the UE does not detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window and the LSB of the SFN field in DCI format 1_0 (if included and applicable) is not the same as the corresponding LSB of the SFN in which the UE transmits the PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH, or if the higher layer does not identify the RAPID associated with the PRACH transmission from the UE, the higher layer may instruct the physical layer to transmit the PRACH. If requested by the higher layer, the UE shall be prepared to transmit the PRACH no later than N T，1 +0.75 msec after the last symbol of the window or the last symbol of the PDSCH reception, where N T,1 is the duration of N1 symbols corresponding to the PDSCH processing time for UE processing capability 1, assuming that μ corresponds to the minimum SCS configuration among the SCS configurations of the PDCCH carrying DCI format 10, the corresponding PDSCH when additional PDSCH DM-RS is configured, and the corresponding PRACH. For μ = 0, the UE assumes N 1,0 = 14 [6, TS 38.214]. For PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines N1, assuming SCS configuration μ = 0.

[0114] 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, then as described in [6, TS 38.214], the UE may assume the same DM-RS antenna port quasi-co-location property for the SS / PBCH block or CSI-RS resource associated with the PRACH by the UE, as described in clause 8.1, regardless of whether the UE is provided with the TCI-State of the CORESET in which the UE receives the PDCCH with DCI format 1_0.

[0115] If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a contention-free random access procedure for the SpCell [11, TS 38.321], the UE may assume that the PDCCH contains DCI format 1_0 and that the PDCCH command has the same DM-RS antenna port quasi-co-location property. If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH command that triggers a contention-free random access procedure for a secondary cell, or if the PDCCH command is from a cell other than the serving cell, the UE may assume the DM-RS antenna port quasi-co-location property of the CORESET associated with the Type1-PDCCH CSS set used for receiving the PDCCH containing DCI format 1_0 and the PDSCH scheduled by DCI format 1_0.

[0116] The RAR UL grant schedules 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.

[0117] If the value of the hopping flag is 0, the UE transmits the PUSCH without hopping; otherwise, the UE transmits the PUSCH with hopping.

[0118] The UE determines the MCS for the PUSCH transmission from the first sixteen indices of the applicable MCS index table for the PUSCH as described in [6, TS 38.214].

[0119] TPC command value δ msg2,b,f，c For setting the power of the PUSCH transmission, as described in Clause 7.1.1 and interpreted according to Table 8.2-2.

[0120] The CSI request field is reserved.

[0121] The ChannelAccess-CPext field indicates the channel access type and CP extension for operations with shared spectrum channel access in FR1 [15, TS37.213], as defined in Table 7.3.1.1.1-4 of [5, TS 38.212] or Table 7.3.1.1.1-4A of [5, TS38.212], provided that channelAccessMode = "semiStatic". The ChannelAccess-CPext field indicates the channel access type for operations with shared spectrum channel access in FR2-2 [15, TS 37.213], as defined in Table 7.3.1.1.1-4B of [5, TS 38.212], provided that ChannelAccessMode2-r17 is provided.

[0122] [Table 8.2-1 of 3GPP TS 38.213 V18.0.0, entitled "Random Access Response Grant Content Field Sizes", is reproduced as Figure 6

[0123] [Table 8.2-2 of 3GPP TS 38.213 V18.0.0, entitled "TPC Command δ for PUSCH msg2,b，f，c ", is reproduced as Figure 7

[0124] Unless the UE is configured with an SCS, the UE receives subsequent PDSCHs using the same SCS as the PDSCH reception that provided the RAR message.

[0125] If the UE does not detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window and the LSB of the SFN field in DCI format 1_0 (if included and applicable) is not the same as the corresponding LSB of the SFN in which the UE transmitted the PRACH, or the UE does not correctly receive the corresponding transport block within the window, the UE procedure is as described in [11, TS 38.321]. [...]

[0127] 13 UE procedures for monitoring Type0-PDCCH CSS sets

[0128] ​​If during cell search the UE determines that a CORESET for a Type0-PDCCH CSS set exists from the MIB, as described in clause 4.1, the UE determines the number of consecutive resource blocks and the number of consecutive symbols of the CORESET for the Type0-PDCCH CSS set from controlResourceSetZero in pdcch-ConfigSIB1, as described in Tables 13-0 to 13-10 for operation without shared spectrum channel access in FR1 and FR2-1, or as described in Tables 13-1A and 13-4A for operation with shared spectrum channel access in FR1, or as described in Table 13-10A for FR2-2, and determines the PDCCH monitoring occasion from searchSpaceZero in pdcch-ConfigSIB1 included in the MIB, as described in Tables 13-11 to 13-15A. SFN c and n c are the SFN and slot index within the frame of the CORESET based on the CORESET's SCS, and SFN SSB,i and n SSB，i are the SFN and slot index based on the CORESET's SCS respectively, where the SS / PBCH block with index i overlaps in time with system frame SFN SSB,i and slot n SSB,i The symbols of the CORESET associated with searchSpaceSIB1 in pdcch-ConfigSIB1 or PDCCH-ConfigCommon in the MIB have a normal cyclic prefix. In Table 13-0, the configurations with indices 0 to 9 apply when locating the associated SS / PBCH block according to Table 5.4.3.3-2 in [8-1, TS 38.101-1], the configurations with indices 10 to 11 apply when locating the associated SS / PBCH block according to Note 12 of Table 5.4.3.3-1 in [8-1, TS 38.101-1], and non-interleaved CCE to REG mapping applies to the configurations with indices 6 to 9. In Table 13-1, the associated SS / PBCH block is not located according to Note 12 of Table 5.4.3.3-1 in [8-1, TS 38.101-1].

[0129] For operations with shared spectrum channel access in FR2-2 and for operations without shared spectrum channel access, the UE assumes that the offsets in Tables 13-0 to 13-10A are defined relative to the SCS of the CORESET for the Type0-PDCCH CSS set, from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB that overlaps with the first RB of the corresponding SS / PBCH block, which is after puncturing (if any) [4, TS 38.211]. The SCS of the CORESET for the Type0-PDCCH CSS set is provided by subCarrierSpacingCommon for FR1 and FR2-1 and is the same as the SCS of the corresponding SS / PBCH block in FR2-2. In Tables 13-7, 13-8, and 13-10, k SSB is defined in [4, TS 38.211].

[0130] For operations with shared spectrum channel access in FR1, the UE determines the offset from the minimum RB index of the CORESET for the Type0-PDCCH CSS set to the minimum RB index of the common RB that overlaps with the first RB of the corresponding SS / PBCH block as follows

[0131] - If the frequency position of the SS / PBCH block corresponds to the GSCN of a synchronization grid entry as defined in [8-1, TS 38.101-1], then according to the offset in Table 13-1A or Table 13-4A, and

[0132] - If the frequency position of the SS / PBCH block is provided by ssbFrequency in a measurement configuration associated with the reporting configuration that provides reportCGI and does not correspond to the GSCN of a synchronization grid entry as defined in [8-1, TS 38.101-1], then according to the sum of a first offset and a second offset, where

[0133] - The first offset is provided in Table 13-1A or Table 13-4A, and

[0134] - The second offset is determined as the offset from the minimum RB index of the common RB that overlaps with the first RB of the SS / PBCH block indicated in the measurement configuration to the minimum RB index of the common RB that overlaps with the first RB of the SS / PBCH block assumed to be located at the GSCN of a synchronization grid entry, where a single synchronization grid entry is in the same channel as the SS / PBCH block used for the shared spectrum channel access procedure, as described in [15, TS 37.213]

[0135] The offset is defined relative to the SCS of the CORESET for the Type0-PDCCH CSS set that is the same as the SCS of the corresponding SS / PBCH block.

[0136] For operation without shared spectrum channel access and for SS / PBCH block and CORESET multiplexing pattern 1, the UE listens for PDCCHs in the Type0-PDCCH CSS set on two time slots. For an SS / PBCH block with index i, the UE determines, based on the SCS [4, TS 38.211] used for PDCCH reception in the CORESET, the index n0 of the time slot in the frame with a system frame number (SFN) SFN c mod2 = 0 (if ) or in the frame with an SFN with SFN C mod2 = 1 (if c ) to be where μ ∈ {0, 1, 2, 3, 5, 6}.

[0137] - For μ ∈ {0, 1, 2, 3} and for an SS / PBCH block index i, the two time slots containing the associated Type0-PDCCH monitoring occasion are time slots n0 and n0 + 1. The indices of M, O, and the first symbol of the CORESET in time slots n0 and n0 + 1 are provided in Tables 13-11 and 13-12.

[0138] - For μ = 5 and for an SS / PBCH block index i, the two time slots containing the associated Type0-PDCCH monitoring occasion are time slots n0 and n0 + 4. The indices of M, O, and the first symbol of the CORESET in time slots n0 and n0 + 4 are provided in Table 13-12A, where X = 1.25.

[0139] - For μ = 6 and for an SS / PBCH block index i, the two time slots containing the associated Type0-PDCCH monitoring occasion are time slots n0 and n0 + 8. The indices of M, O, and the first symbol of the CORESET in time slots n0 and n0 + 8 are provided in Table 13-12A, where X = 0.625.

[0140] ​For operations with shared spectrum channel access and for SS / PBCH block and CORESET multiplexing pattern 1, the UE monitors the PDCCH in the Type0-PDCCH CSS set on the slot containing the Type0-PDCCH monitoring occasion associated with the SS / PBCH block, where the SS / PBCH block is quasi-co-located with the SS / PBCH block that provides the CORESET for the Type0-PDCCH CSS set with respect to the average gain, quasi-co-location 'type A' and 'type D' properties (when applicable) [6, TS 38.214]. For the candidate SS / PBCH block index where two slots contain the associated Type0-PDCCH monitoring occasion. The UE determines, based on the SCS used for PDCCH reception in the CORESET [4, TS 38.211], that the index n0 of the slot in the frame with a system frame number (SFN) SFN that satisfies C mod 2 = 0 (if ) or in the frame with an SFN that satisfies C mod2 = 1 (if C ) is ) where μ ∈ {0, 1, 3, 5, 6}. where μ ∈ {0, 1, 3, 5, 6}.

[0141] - For μ ∈ {0, 1} and for the candidate SS / PBCH block index the two slots containing the associated Type0-PDCCH monitoring occasion are slot n0 and n0 + 1. The values of M, O, and the index of the first symbol of the CORESET in slots n0 and n0 + 1 are provided in Table 13-11. When the UE does not expect to be configured with M = 1 / 2 or M = 2.

[0142] - For μ = 3 and for the candidate SS / PBCH block index the two slots containing the associated Type0-PDCCH monitoring occasion are slot n0 and n0 + 1. The values of M, O, and the index of the first symbol of the CORESET in slots n0 and n0 + 1 are provided in Table 13-12.

[0143] - For μ = 5 and for the candidate SS / PBCH block index the two slots containing the associated Type0-PDCCH monitoring occasion are slot n0 and n0 + 4. The values of M, O, and the index of the first symbol of the CORESET in slots n0 and n0 + 4 are provided in Table 13-12A, where X = 1.25.

[0144] - For μ = 6 and for the candidate SS / PBCH block index The two time slots that contain the associated Type0-PDCCH monitoring occasions are time slot n0 and n0 + 8. The indexes of M, O, and the first symbol of the CORESET in time slots n0 and n0 + 8 are provided in Table 13-12A, where X = 0.625.

[0145] For operation without shared spectrum channel access and for SS / PBCH blocks and CORESET multiplexing modes 2 and 3, the UE monitors the PDCCH in the Type0-PDCCH CSS set on one time slot with a Type0-PDCCH CSS set periodicity equal to the periodicity of the SS / PBCH block. For an SS / PBCH block with index i, the UE determines the time slot index n c and SFN c .

[0146] For operation with shared spectrum channel access and for SS / PBCH blocks and CORESET multiplexing mode 3, the UE monitors the PDCCH in the Type0-PDCCH CSS set on the time slot that contains the Type0-PDCCH monitoring occasion associated with the SS / PBCH block, where the SS / PBCH block is quasi-co-located with the SS / PBCH block that provides the CORESET for the Type0-PDCCH CSS set with respect to the average gain, quasi-co-location 'type A' and 'type D' properties (when applicable). For a candidate SS / PBCH block index where the periodicity of the time slot that contains the associated Type0-PDCCH monitoring occasion is the same as the periodicity of the candidate SS / PBCH block, and the UE determines the time slot index n c and SFN c , where for operation with shared spectrum channel access in FR2-2, i is replaced by .

[0147] For SS / PBCH blocks and CORESET multiplexing modes 2 and 3, if the active DL BWP is the initial DL BWP, the UE is expected to be able to perform radio link monitoring as described in Clause 5, and measurements for radio resource management using the SS / PBCH block that provides the CORESET for the Type0-PDCCH CSS set [10, TS 38.133]. [...]

[0149] If the UE detects the first SS / PBCH block and determines that the CORESET for the Type0-PDCCH CSS set does not exist, and for 24 ≤ kSSB ≤29 for FR1 or for 12 ≤ k SSB ≤13 for FR2, the UE may determine the closest (in the respective frequency direction) global synchronization channel number (GSCN) of the second SS / PBCH block having a CORESET for the associated Type0-PDCCH CSS set as is the GSCN of the first SS / PBCH block, in FR1 and FR2-1 in FR2-2 and is the GSCN offset provided by Table 13-16 for FR1 and Table 13-17 for FR2. If the UE detects the second SS / PBCH block and the second SS / PBCH block does not provide a CORESET for the Type0-PDCCH CSS set, as described in Clause 4.1, the UE may ignore the information related to the GSCN of the SS / PBCH block location for performing cell search.

[0150] If the UE detects an SS / PBCH block and determines that there is no CORESET for the Type0-PDCCH CSS set, and for k SSB = 31 for FR1 or for k SSB = 15 for FR2, the UE determines that there is no SS / PBCH block within the GSCN range with an associated Type0-PDCCH CSS set. and are determined by controlResourceSetZero and searchSpaceZero in pdcch-ConfigSIB1 respectively. If the GSCN range is then the UE determines that there is no information on the second SS / PBCH block having a CORESET for the associated Type0-PDCCH CSS set on the detected SS / PBCH block.

[0151] If the UE does not detect any SS / PBCH block providing a CORESET for the Type0-PDCCH CSS set within the time period determined by the UE, as described in Clause 4.1, the UE may ignore the information related to the GSCN of the SS / PBCH location during the process of performing cell search.

[0152] [The title of 3GPP TS 38.213 V18.0.0 is "k SSB Combination of controlResourceSetZero and searchSpaceZero in pdcch-ConfigSIB1 to Table 13 - 16 of "Mapping between" is reproduced as Figure 8

[0153] [The title of 3GPP TS 38.213 V18.0.0 is "k SSB Combination of controlResourceSetZero and searchSpaceZero in pdcch - ConfigSIB1 to Table 13 - 17 of "Mapping between" is reproduced as Figure 9

[0154] In addition, 3GPP 38.321 states:

[0155] 5.1.2 Random access resource selection

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

[0157] […]

[0158] 1> Otherwise, if starting a random access procedure for SI request (as specified in TS 38.331 [5]); and 1> if the random access resources for SI request have been explicitly provided by RRC:

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

[0160] 3> Select an SSB with SS - RSRP higher than rsrp - ThresholdSSB.

[0161] 2> Otherwise:

[0162] 3> Select any SSB.

[0163] 2> Select a 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];

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

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

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

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

[0168] 2> Otherwise:

[0169] 3> Select any SSB.

[0170] […]

[0171] 1> If the initial random access procedure is requested for SI (as specified in TS 38.331 [5]); and

[0172] 1> If ra-AssociationPeriodIndex and si-RequestPeriod are configured:

[0173] 2> Determine the next available PRACH occasion corresponding to the selected SSB permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) from the PRACH occasions in the association period given by ra-AssociationPeriodIndex in si-RequestPeriod (the MAC entity will randomly select, with equal probability among consecutive PRACH occasions, the PRACH occasion corresponding to the selected SSB according to clause 8.1 of TS 38.213 [6]).

[0174] 1> Otherwise, if the SSB is selected as above:

[0175] 2> Determine the next available PRACH occasion corresponding to the selected SSB permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) or ssb-

[0176] SharedRO-MaskIndex (if configured) or indicated by the PDCCH (the MAC entity will randomly select, with equal probability among consecutive PRACH occasions, the PRACH occasion corresponding to the selected SSB according to clause 8.1 of TS 38.213 [6], regardless of the FR2 UL gap; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB).

[0177] 1> Otherwise, if CSI-RS is selected as above:

[0178] 2> If there is no contention-free random access resource associated with the selected CSI-RS:

[0179] 3> Determine the next available PRACH occasion corresponding to the SSB in the candidateBeamRSList that is quasi - co - located with the selected CSI - RS as permitted by the restrictions given by ra - ssb - OccasionMaskIndex (if configured), from the PRACH occasions. (The MAC entity will randomly select, with equal probability, among consecutive PRACH occasions, the PRACH occasion corresponding to the SSB that is quasi - co - located with the selected CSI - RS in accordance with clause 8.1 of TS 38.213 [6], regardless of the FR2 UL gap;

[0180] The MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the SSB that is quasi - co - located with the selected CSI - RS).

[0181] 2> Otherwise:

[0182] 3> Determine the next available PRACH occasion corresponding to the selected CSI - RS in the ra - OccasionList from the PRACH occasions. (The MAC entity will randomly select, with equal probability, among PRACH occasions that occur simultaneously but on different sub - carriers, the PRACH occasion corresponding to the selected CSI - RS, regardless of the FR2

[0183] UL gap; The MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected CSI - RS).

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

[0185] […]

[0186] 5.1.4 Random access response reception

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

[0188] […]

[0189] 2> Otherwise:

[0190] 3> Start the ra - ResponseWindow configured in RACH - ConfigCommon at the first PDCCH occasion as specified in TS 38.213 [6] from the end of the random access preamble transmission.

[0191] 2> While the ra - ResponseWindow is running, listen for the PDCCH of the SpCell for the random access response identified by the RA - RNTI.

[0192] […]

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

[0194] 2> If the random access response contains a MAC sub-PDU with a backoff indicator:

[0195] 3> Set PREAMBLE_BACKOFF to the value of the BI field of the MAC sub-PDU, multiplied by SCALING_FACTOR_BI, using Table 7.2-1.

[0196] 2> Otherwise:

[0197] 3> Set PREAMBLE_BACKOFF to 0 ms.

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

[0199] 3> Consider this random access response reception successful.

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

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

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

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

[0204] 3> Otherwise:

[0205] 4> Execute the random access resource selection procedure (see Clause 5.1.2) after the backoff time. Additionally, 3GPP TS38.331 states:

[0206] 5.2.2.3.3 Request for on-demand system information

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

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

[0209] 2> Trigger the lower layer to initiate a random access procedure on the supplementary uplink using the PRACH preamble and PRACH resources in si-RequestConfigSUL corresponding to the SI message that the UE needs to operate within the cell, and where si-BroadcastStatus is set to notBroadcasting;

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

[0211] 3> Immediately obtain the requested SI message as defined in clause 5.2.2.3.2;

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

[0213] 2> Use the PRACH preamble and PRACH resources in si-

[0214] RequestConfigRedcap corresponding to the SI message that the UE needs to operate within the cell, according to TS 38.321 [3]

[0215] Trigger the lower layer to initiate a random access procedure on the normal uplink, and where si-BroadcastStatus is set to notBroadcasting;

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

[0217] 3> Immediately obtain the requested SI message as defined in clause 5.2.2.3.2;

[0218] 1> Otherwise:

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

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

[0221] 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 to 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;

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

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

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

[0225] 2> Otherwise:

[0226] 3> Apply the preset L1 parameter values as specified in the corresponding physical layer specification, except for the parameters provided in SIB1;

[0227] 3> Apply the preset MAC cell group configuration as specified in 9.2.2;

[0228] 3> Apply the timeAlignmentTimerCommon included in SIB1;

[0229] 3> Apply the CCCH configuration as specified in 9.1.1.2;

[0230] 3> Initiate the transmission of an RRCSystemInfoRequest message with rrcSystemInfoRequest according to 5.2.2.3.4;

[0231] 3> If an acknowledgement of the RRCSystemInfoRequest message with rrcSystemInfoRequest is received from the lower layer:

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

[0233] 1> If cell reselection occurs while waiting for an acknowledgement of the SI request from the lower layer:

[0234] 2> Reset MAC;

[0235] 2> If the SI request is based on an RRCSystemInfoRequest message with rrcSystemInfoRequest:

[0236] 3> Release the RLC entity for SRB0.

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

[0238] […]

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

[0240] SI-RequestConfig information element

[0241]

[0242]

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

[0244] 3 Explanation

[0245] Network energy savings are very important for environmental sustainability, reducing environmental impact (greenhouse gas emissions), and operational cost savings. As 5G is becoming widespread across industries and geographical regions, handling more advanced services and applications that require extremely high data rates (e.g., XR), the network becomes more dense, using more antennas, larger bandwidths, and more frequency bands. The environmental impact of 5G needs to be kept under control, and novel solutions need to be developed to improve network energy savings.

[0246] Energy consumption has become a key part of the operator's OPEX. According to a report from GSMA [1], the energy cost on mobile networks accounts for ~23% of the operator's total cost. Most of the energy consumption comes from the radio access network and specifically from the active antenna unit (AAU), where the data center and fiber optic transmission account for a smaller share. The power consumption of radio access can be split into two parts: the dynamic part, which consumes only when data transmission / reception is in progress; and the static part, which always consumes to maintain the necessary operation of the radio access device, even when data transmission / reception is not in progress.

[0247] During the research in the SI phase [2], a network energy consumption model of the base station (BS) was defined, which includes reference configurations for FR1 TDD / FDD and FR2, deep / mild / micro-dormant power states with corresponding relative powers, transition times and energy consumption between different power states based on two types of BS categories, and scaling rules for active DL / UL power states considering the BS power split by the static power part and the dynamic power part, where the dynamic power part reflects the dynamic power consumption relative to the transmission / reception resource configuration in the time, frequency, space, and power domains. Additionally, evaluation methods and assumptions were implemented to study and evaluate the network energy savings gain of potential technologies relative to other KPIs including UPT, access delay, UE power consumption, etc.

[0248] Based on the agreed BS energy consumption model, as well as the evaluation methods and assumptions, potential network energy saving techniques in various domains are evaluated in terms of the energy saving gain and the corresponding performance impact considering the above KPIs. The studied techniques are classified into time, frequency, space, and power domains, and the technique descriptions as well as the legacy UE and specification impacts are outlined in the technical report [2]. The techniques in the time and frequency domains mainly aim to reduce the power consumption of the dynamic part by attempting to turn off more symbols on one or more carriers to achieve BS micro-dormancy, and even reduce the power consumption of the static power part by increasing the interval between the transmit / receive opportunities in adjacent active states to achieve BS light / deep dormancy. The techniques in the space and power domains mainly aim to reduce the power consumption of the TRX chain and PA by attempting to turn off more spatial elements and / or reduce the transmit power / power spectral density or increase the PA efficiency. As shown in section 7 of TR 38.864 [2], some of the studied techniques are beneficial for network energy saving.

[0249] The Rel-18 work item on network energy saving for NR resulted in the specification of some techniques found beneficial in the study, mainly for RRC connection, user-specific signals and channels, and low-load scenarios. The techniques specified in Rel-18 include SSB-less SCell operation for inter-band CA in FR1 and co-located cells, enhancement of the cell DTX / DRX mechanism including alignment of cell DTX / DRX and UE DRX in RRC_CONNECTED mode, inter-node information exchange on cell DTX / DRX, techniques in the space and power domains to achieve effective adaptation of spatial elements and the power offset value between PDSCH and CSI-RS, and mechanisms to avoid legacy UE camping on cells by adopting Rel-18 NES techniques, CHO procedure enhancement, and inter-node beam activation as well as enhancement of paging in restricted areas, and the corresponding RRM / RF core requirements.

[0250] Some other techniques found beneficial in the study have not been specified in Rel-18. This Rel-19 work item aims to specify further network energy saving targeting the beneficial techniques studied but not specified in Rel-18, including on-demand SSB and on-demand SIB1 transmission, and adaptation of common signal / channel transmission.

[0251] [1] GSMA, 5G Energy Efficiency: Green is the New Black, https: / / data.gsmaintelligence.com / api - web / v2 / research - file - download?id=54165956&file =241120 - 5G - energy.pdf

[0252] [2] 3GPP TR 38.864 V18.1.0, Study on Network Energy Saving for NR.

[0253] 4 Objectives

[0254] 4.1 Objectives of SI or Core Part WI or Test Part WI

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

[0256] 1. For both 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]

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

[0258] ● 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.

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

[0260] ● Triggering method via uplink wake-up signal using existing signals / channels.

[0261] ● Provide wake-up signal configuration to the UE

[0262] - Note: Modification of SSB will not be addressed under this objective

[0263] ● Information exchange between gNBs for at least the configuration of wake-up signals if necessary.

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

[0265] 3. Specify the adaptation of common signal / channel transmission. [RAN1 / 2 / 3 / 4]

[0266] ● Adaptation of SSB in the time domain, e.g., adapt the periodicity

[0267] ● Adaptation of PRACH in the time domain

[0268] ● Study the adaptation of PRACH in the spatial domain, e.g., non-uniform PRACH resources per SSB, and specify if found beneficial

[0269] - This study will be completed only in 2Q'2024

[0270] ● Adaptation of paging occasions, including restricting paging occasions in the time domain

[0271] - Note: There should be no increase in paging latency.

[0272] ● Note: There should be no negative impact on legacy UEs unless significant benefits are demonstrated.

[0273] 4. For the above features, specify the corresponding core requirements [RAN4].

[0274] As discussed above, the 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, to request OSI, the corresponding RAR (random access response) is used to confirm the reception of the corresponding preamble. After sending the confirmation for the preamble, the base station can further decide whether to provide OSI and / or how to provide OSI. For example, the base station can provide OSI via a broadcast message. The base station can decide not to provide OSI. The UE will listen for OSI at the corresponding occasion and obtain the corresponding OSI (if provided). Since OSI does not affect the connection between the base station and the UE, the UE will behave the same as in the case where OSI is not provided (e.g., after requesting OSI). On the other hand, the UE needs SIB 1 to connect to the serving cell and / or base station. If SIB 1 is not provided and / or the base station is in a low power consumption state, the UE cannot access the serving cell (e.g., and decides to remain so even if the UE requests SIB1). Therefore, the random access for requesting SIB1 may require some different designs.

[0275] The first general concept of the present invention is to indicate whether the base station will provide SIB1 and / or whether the base station will wake up in the RAR. For example, there can be 1 bit in the RAR to indicate whether SIB1 will be provided (e.g., subsequently or in the near future) and / or whether the base station will wake up. The random access procedure can be successfully completed regardless of whether the base station will provide the RAR. If / when the RAR indicates that SIB1 will be provided, the UE will attempt to receive / listen for SIB1. If / when the RAR indicates that SIB1 will be provided in the serving cell, the UE will attempt to access the serving cell. If / when the RAR indicates that SIB1 will be provided in the serving cell, the UE will initiate another random access procedure (e.g., a second random access procedure) to access the serving cell. If / when the RAR indicates that SIB1 will not be provided in the serving cell, the UE can determine to access another serving cell. If / when the RAR indicates that SIB1 will not be provided in the serving cell, the UE can perform cell reselection to camp on / access the serving cell that provides SIB1.

[0276] A second general concept of the present invention is to indicate whether the base station will provide SIB1 and / or whether the base station will wake up in the SSB (e.g., SS / PBCH block). For example, there may be 1 bit in the MIB of the SSB to indicate whether SIB1 will be provided (e.g., subsequently or in the near future) and / or whether the base station will wake up. The UE may initiate a random access procedure to request SIB1. If / when the SSB indicates that SIB1 is not provided (currently) and / or the base station is in a dormant state (e.g., not woken up), the UE may initiate a random access procedure to request SIB1. After receiving the RAR for the random access procedure, the UE will acquire the SSB (synchronization signal block) to check whether the base station will provide SIB1 and / or whether the base station will wake up. The SSB may be the SSB in the next SSB occasion or the SSB in the SSB occasion indicated by the RAR. The SSB may be the SSB selected during the random access procedure.

[0277] If / when the SSB indicates that SIB1 will be provided, the UE will attempt to receive / monitor SIB1. If / when the SSB indicates that SIB1 will be provided in the serving cell, the UE will attempt to access the serving cell. If / when the SSB indicates that SIB1 will be provided in the serving cell, the UE will initiate another random access procedure (e.g., a second random access procedure) to access the serving cell. If / when the SSB indicates that SIB1 will not be provided in the serving cell, the UE may determine to access another serving cell. If / when the SSB indicates that SIB1 will not be provided in the serving cell, the UE may perform cell reselection to camp on / access the serving cell that provides SIB1.

[0278] A third general concept of the present invention is that the base station indicates on which beam and / or which SSB is used to provide SIB1. The indication can be indicated together with an indication of whether the base station will provide SIB1, for example, in the RAR or SSB. The indication can also be indicated separately from an indication of whether the base station will provide SIB1, for example, in the RAR or SSB. Each SSB can indicate, for example, in the MIB whether SIB1 associated with the SSB is provided. Each SSB can indicate, for example, in the MIB whether SIB1 associated with other SSBs is provided. Each SSB can indicate, for example, in the MIB whether SIB1 is provided for all SSBs. For example, there can be a bitmap indicating whether SIB1 associated with each SSB is provided. Before starting a random access procedure to request SIB1, the UE will determine whether SIB1 is provided by the corresponding SSB. The corresponding SSB can be the SSB with the best quality or the strongest received power. The corresponding SSB can be the SSB that can be received by the UE. The corresponding SSB can be the SSB to be selected for the random access procedure. When / if SIB1 associated with the corresponding SSB is provided, the UE does not start a random access procedure to request SIB1. When / if SIB1 associated with the corresponding SSB is not provided, the UE starts a random access procedure to request SIB1.

[0279] A fourth general concept of the present invention is to indicate to the UE a time domain mode for listening to SIB1. There can be multiple time domain modes configured for SIB1, and the base station indicates which one to apply. One of the time domain modes can be the time domain mode used when on-demand SIB1 is disabled. One of the time domain modes can be provided or configured or indicated by the MIB. Other time domain modes can be provided or indicated or configured by SIB (e.g., SIB1) or a dedicated RRC message. The indication can be indicated together with an indication of whether the base station will provide SIB1, for example, in the RAR or SSB. The indication can be indicated separately from an indication of whether the base station will provide SIB1, for example, in the RAR or SSB. The time domain mode can be a search space. The UE can be configured with multiple search spaces for SIB1. One of the search spaces is indicated or configured by the SSB. Another one of the search spaces can be configured or indicated by SIB (e.g., SIB1) or a dedicated RRC message.

[0280] After the request for SIB1 at the start, the UE will receive an indication of which time domain pattern and / or which search space in the time domain to apply to SIB1. The indication may indicate whether to use the search space and / or time domain pattern indicated in the SSB. The indication of which time domain pattern and / or which search space to apply may be indicated in the RAR. The indication of which time domain pattern and / or which search space to apply may be indicated in the RAR in response to a preamble requesting SIB1. The indication of which time domain pattern and / or which search space to apply may be indicated in the SSB. When / if the base station will provide SIB1, the indication of which time domain pattern and / or which search space may be present. The indication of which time domain pattern and / or which search space may be coded jointly with the indication of whether the base station will provide SIB1.

[0281] After receiving the indication of which time domain pattern and / or which search space, the UE receives or monitors SIB1 and / or the PDCCH indicating SIB1 according to the indicated time domain pattern and / or search space. The time domain pattern may be periodic and / or offset. The time domain pattern may be the periodicity and / or offset of SIB1. The periodicity and / or offset of SIB1 may be indicated relative to the SSB. The periodicity of SIB1 may be different from the periodicity of the SSB. The periodicity of SIB1 may be a multiple (e.g., two times or four times or eight times) of the periodicity of the SSB. The indication may indicate the multiple.

[0282] For example, if the periodicity of the SSB is X, the indication may indicate 1, 2, 4, 8, which indicate that the periodicity of SIB1 is X, 2*X, 4*X, 8*X respectively. The offset value may be used to indicate for which SSB period SIB1 exists. When the SIB1 periodicity is 4*X, there is (one) SIB1 occasion associated with one of the four periodic SSBs or four SSB periods. And the offset value may indicate which one of the four SSBs SIB1 is available for, e.g., the first, the second, or the fourth. It should be noted that the first may be determined based on the SSB in a predefined time occasion, e.g., the SSB in SFN 0 or the SSB closest to SFN0. For example, the first may be the SSB whose time domain distance to the SSB in the predefined time occasion is a multiple of 4*X. The first may be the SSB in SFN Y, and the SSB in the predefined time occasion is in SFN Z, where Y mod 4*X is equal to Z mod 4*X. The offset value may be a predefined value, e.g., 0 or the first (which means no indication of the offset value is required). The time domain pattern may be a bitmap indicating SIB1 associated with the SSB providing the SSB period.

[0283] In one embodiment, the UE initiates a random access procedure to request the first system information. 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 (e.g., SCell). When / if (e.g., currently) the first system information is not provided (e.g., in the serving cell and / or the PCell of the base station), the UE initiates a random access procedure to request the first system information. After initiating the random access procedure, the UE transmits a preamble on the serving cell to the base station. 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.

[0284] The UE determines whether to obtain / receive / monitor the first system information (or the PDCCH scheduling the first system information) based on the indication in the random access response. When / if 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). When / if 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). When / if 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).

[0285] When / if 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). When / if 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). When / if 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).

[0286] 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). The UE accesses the serving cell when / if the random access response indicates that the first system information will be provided. The UE accesses the serving cell when / if the random access response indicates that the request is accepted. The UE accesses the serving cell when / if the random access response indicates that the base station or the serving cell will wake up. The UE does not access the serving cell when / if the random access response indicates that the first system information will not be provided (subsequently). The UE does not access the serving cell when / if the random access response indicates that the request is rejected or not accepted. The UE does not access the serving cell when / if the random access response indicates that the base station or the serving cell will remain dormant or will not wake up.

[0287] The UE accesses another serving cell (different from the serving cell) when / if 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) when / if the random access response indicates that the request is rejected or not accepted. The UE accesses another serving cell (different from the serving cell) when / if the random access response indicates that the base station or the serving cell will remain dormant or will not wake up.

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

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

[0290] 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 the 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.

[0291] 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.

[0292] In another embodiment, the base station receives or detects a preamble from the UE. The preamble is used to request the first system information. The first system information may be SIB1. When / if (e.g., currently) the first system information is not provided (e.g., in the serving cell and / or the PCell of the base station), the base station receives or detects the preamble from the UE.

[0293] The base station transmits a random access response to the UE. 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. The indication in the random access response is used by the UE to determine whether to acquire / receive / listens for the first system information (or the PDCCH scheduling the first system information). The indication in the random access response is used by the UE to determine whether to perform cell selection / reselection.

[0294] The base station receives or detects a second preamble from the UE. The preamble is used to request the second system information. The second system information is system information other than SIB1. The second system information is the OSI. The second system information is the system information scheduled by SIB1. The base station transmits a (second) random access response to the UE 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.

[0295] In another embodiment, the UE initiates a random access procedure to request the first system information. The first system information may be SIB1. When / if (e.g., currently) the first system information is not provided (e.g., in the serving cell and / or the PCell of the base station), the UE initiates a random access procedure to request the first system information. The UE camps on or selects a serving cell. When / if the SSB / MIB indicates (e.g., currently) that the first system information is not provided (e.g., in the serving cell and / or the PCell of the base station), the UE initiates a random access procedure to request the first system information. The SSB / MIB indicating (e.g., currently) that the first system information is not provided is used for the search space for SIB1.

[0296] After initiating the random access procedure, the UE transmits a preamble on the serving cell to the base station. The UE receives a random access response from the base station. The random access response indicates that the preamble or the request has been successfully received. After receiving the random access response, the UE will receive or acquire the SSB / MIB. The UE will receive or acquire the SSB / MIB in response to receiving the random access response. The SSB may be the next SSB. The SSB may have the same index as the index selected in the random access response. The SSB may be indicated by the random access response. The SSB occasion may be indicated by the random access response. The SSB and / or the MIB indicate whether the first system information will be provided (e.g., subsequently). The SSB and / or the MIB indicate whether the request is accepted or rejected. The SSB and / or the MIB indicate whether the request is accepted. The SSB and / or the MIB indicate whether the base station or the serving cell will wake up. The SSB and / or the MIB indicate whether the base station or the serving cell will wake up or remain dormant.

[0297] The UE determines whether to acquire / receive / monitor the first system information (or the PDCCH scheduling the first system information) based on the indication in the SSB and / or the MIB. When / if the SSB and / or the MIB indicate that the first system information will be provided, the UE acquires or attempts to receive the first system information (e.g., on the serving cell). When / if the SSB and / or the MIB indicate that the request is accepted, the UE acquires or attempts to receive the first system information (e.g., on the serving cell). When / if the SSB and / or the MIB indicate that the base station or the serving cell will wake up, the UE acquires or attempts to receive the first system information (e.g., on the serving cell). When / if the SSB and / or the MIB indicate that the first system information will not be provided (e.g., subsequently), the UE does not acquire or attempt to receive the first system information (e.g., on the serving cell). When / if the SSB and / or the MIB indicate that the request is rejected or not accepted, the UE does not acquire or attempt to receive the first system information (e.g., on the serving cell). When / if the SSB and / or the MIB indicate that the base station or the serving cell will remain dormant or will not wake up, the UE does not acquire or attempt to receive the first system information (e.g., on the serving cell).

[0298] The UE determines whether to access the serving cell based on the indication in the SSB and / or MIB. (Accessing the serving cell may mean establishing an (RRC) connection to the serving cell). When / if the SSB and / or MIB indicate that the first system information will be provided, the UE accesses the serving cell. When / if the SSB and / or MIB indicate that the request is accepted, the UE accesses the serving cell. When / if the SSB and / or MIB indicate that the base station or the serving cell will wake up, the UE accesses the serving cell. When / if the SSB and / or MIB indicate that the first system information will not be provided (subsequently), the UE does not access the serving cell. When / if the SSB and / or MIB indicate that the request is rejected or not accepted, the UE does not access the serving cell. When / if the SSB and / or MIB indicate that the base station or the serving cell will remain in a dormant state or will not wake up, the UE does not access the serving cell. When / if the SSB and / or MIB indicate that the first system information will not be provided (subsequently), the UE accesses another serving cell (different from the serving cell). When / if the SSB and / or MIB indicate that the request is rejected or not accepted, the UE accesses another serving cell (different from the serving cell). When / if the SSB and / or MIB indicate that the base station or the serving cell will remain in a dormant state or will not wake up, the UE accesses another serving cell (different from the serving cell).

[0299] When / if the SSB and / or MIB indicate that the first system information will not be provided (subsequently), the UE performs cell selection or cell reselection. When / if the SSB and / or MIB indicate that the request is rejected or not accepted, the UE performs cell selection or cell reselection. When / if the SSB and / or MIB indicate that the base station or the serving cell will remain in a dormant state or will not wake up, the UE performs cell selection or cell reselection. The SSB and / or MIB indicate the search space for SIB1.

[0300] The UE initiates a second random access procedure to request the second system information. The second system information is the system information other than SIB1. The second system information is the OSI. The second system information is the system information scheduled by SIB1. As long as the second random access response is received, the UE obtains / receives / listens to the second system information (or the PDCCH (Physical Downlink Control Channel) scheduling the second system information). The UE does not obtain / receive the SSB / MIB in response to receiving the second random access response. The UE does not determine whether to obtain / receive / listen to the second system information (or the PDCCH scheduling the second system information) based on the indication in the SSB / MIB. The UE does not determine whether to access the serving cell based on the indication in the SSB / MIB. The UE does not determine whether to access another serving cell based on the indication in the SSB / MIB. The UE does not determine whether to perform cell reselection based on the indication in the SSB / MIB.

[0301] In another embodiment, the base station receives or detects a preamble from the UE. The preamble is used to request the first system information. The first system information may be SIB1. When / if (e.g., currently) the first system information is not provided (e.g., in the serving cell and / or the PCell of the base station), the base station receives or detects the preamble from the UE. When / if the SSB / MIB indicates (e.g., currently) that the first system information is not provided (e.g., in the serving cell and / or the PCell of the base station), the base station receives or detects the preamble from the UE. The SSB / MIB indication that indicates (e.g., currently) that the first system information is not provided is for the search space of SIB1.

[0302] After transmitting the random access response, the base station transmits the SSB / MIB. The SSB may be the next SSB. The SSB may have the same index associated with the PRACH resource. The SSB may be indicated by the random access response. The SSB occasion may be indicated by the random access response. The SSB and / or MIB indicate whether the first system information will be provided (e.g., subsequently). The SSB and / or MIB indicate whether the request is accepted or rejected. The SSB and / or MIB indicate whether the request is accepted. The SSB and / or MIB indicate whether the base station or the serving cell will wake up. The SSB and / or MIB indicate whether the base station or the serving cell will wake up or remain dormant. The indication is used by the UE to determine whether to obtain / receive / monitor the first system information (or the PDCCH scheduling the first system information). The indication is used by the UE to determine whether to access the serving cell. The indication is used by the UE to determine whether to access the serving cell or another serving cell. The indication is used by the UE to determine whether to perform cell selection / reselection.

[0303] The base station receives or detects a second preamble from the UE for requesting 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. As long as the second random access response is received, the UE obtains / receives / monitors the second system information (or the PDCCH scheduling the second system information). The UE does not obtain / receive the SSB / MIB in response to receiving the second random access response. The SSB and / or MIB indicate whether the second system information will be provided (e.g., subsequently).

[0304] The UE receives an indication of on which beam the first system information is provided and / or an indication of the SSB (index) (e.g., SSB 0, SSB 1, …) associated with which the first system information is provided. The UE receives an indication of on which beam the first system information is provided and / or an indication of the SSB (index) (e.g., SSB 0, SSB 1, …) associated with which the first system information is provided. 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).

[0305] After requesting the first system information, the UE receives an indication of on which beam the first system information is provided and / or an indication of the SSB (index) associated with which the first system information is provided. 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 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 whether the first system information is provided on the (specific / corresponding) beam and / or whether the first system information associated with the (specific / corresponding) SSB is provided.

[0306] (The specific / corresponding) beam and / or (the specific / corresponding) SSB may be the beam and / or SSB utilized and / or selected during a 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 SSB associated with the PRACH utilized / selected in the random access procedure (e.g., for requesting the first system information).

[0307] 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. The indication may indicate whether the first system information is provided on a plurality of beams and / or whether the first system information associated with a plurality of SSBs is provided.

[0308] The plurality of beams and / or the plurality of SSBs may be all the beams and / or all the SSBs of a cell. The plurality of beams and / or the plurality of SSBs may be a subset of the beams and / or a subset of the SSBs of a cell. Before starting a random access procedure to request 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. When / if the first system information associated with the corresponding SSB is provided, the UE does not start a random access procedure to request the first system information. When / if the first system information associated with the corresponding SSB is not provided, the UE starts a random access procedure to request the first system information.

[0309] The base station transmits an indication about on which beam the first system information is provided and / or about which SSB (index) (e.g., SSB 0, SSB 1, …) the first system information associated with is provided. The base station transmits an indication indicating on which beam the first system information is provided and / or indicating which SSB (index) (e.g., SSB 0, SSB 1, …) the first system information associated with is provided. 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).

[0310] The base station transmits an indication about on which beam the first system information is provided and / or about which SSB (index) the first system information associated with is provided for the UE to determine whether to request 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 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 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.

[0311] (Specific / corresponding) beams and / or (specific / corresponding) SSBs may be the beams and / or SSBs utilized and / or selected during a random access procedure (e.g., to request the first system information). (Specific / corresponding) beams and / or (specific / corresponding) SSBs may be the beams and / or SSBs associated with the PRACH utilized / selected in a random access procedure (e.g., to request the first system information).

[0312] 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. The indication may indicate whether the first system information is provided on a plurality of beams and / or whether the first system information associated with a plurality of SSBs is provided. The plurality of beams and / or the plurality of SSBs may be all the beams and / or all the SSBs of a cell. The plurality of beams and / or the plurality of SSBs may be a subset of the beams and / or a subset of the SSBs of a cell. 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.

[0313] 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 which search space schedules the first system information. 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.

[0314] The periodicity and / or the offset may be relative to the time occasion of the SSB. The SSB (e.g., SSB 0 or SSB 1) will be transmitted periodically with a certain periodicity. SIB1 is provided in some SSB occasion(s) of the SSB (e.g., SSB 0 or SSB 1) 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. The periodicity and / or the 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 the 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. The first system information may be 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.

[0315] There can be multiple occasions / periodicity / offsets / search spaces configured, for example, by RRC messages. The indication indicates one of multiple values. The indication can be indicated together with an indication of whether the base station will provide the first system information. The indication can be indicated separately from an indication of whether the base station will provide the first system information. The indication can be indicated together with and / or jointly with an indication of whether the first system information will be provided. The indication can be indicated together with and / or jointly with an indication of whether the base station will wake up. The indication can be indicated together with and / or jointly with an indication of whether a request is accepted. The indication can 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 can 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 for / receives / obtains the first system information based on the indicated time occasion and / or search space and / or periodicity and / or offset.

[0316] Throughout the present invention, "C-DRX" can be replaced by "DRX" or "DRX for the UE" or "UE DRX".

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

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

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

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

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

[0322] Figure 10 It is a flowchart 1000 of a user equipment (UE). In step 1005, the UE receives, on a synchronization signal block (SSB) with one SSB index, an indication of whether the first system information is provided or broadcast. In step 1010, the UE determines, based on the indication, whether to initiate a random access procedure on the serving cell to request the first system information.

[0323] In one embodiment, the UE can receive, on the SSB with the one SSB index, an indication of whether the first system information is provided or broadcast for the SSB and / or beam with the one SSB index.

[0324] In one embodiment, when providing or broadcasting the first system information for the SSB that the UE can receive, obtain, or detect, the UE may not initiate a random access procedure on the serving cell to request the first system information. When not providing or broadcasting the first system information for the SSB that the UE can receive, obtain, or detect, the UE may initiate a random access procedure on the serving cell to request the first system information.

[0325] In one embodiment, the indication may be indicated by the SSB or carried on the SSB. The indication may indicate whether to provide or broadcast the first system information for the SSB. The indication may not indicate whether to provide or broadcast the first system information for another SSB different from the SSB. The indication may indicate whether to provide or broadcast the first system information for each of multiple SSBs of the serving cell.

[0326] In one embodiment, the SSB may be the SSB selected during the random access procedure. The first system information may be SIB1.

[0327] Return to reference Figure 3 and 4 and, 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) receive, on an SSB having one SSB index, an indication indicating whether to provide or broadcast the first system information, and (ii) determine, based on the indication, whether to initiate a random access procedure on the serving cell to request the first system information. In addition, the CPU 308 may execute the program code 312 to perform all the actions and steps described above or other actions and steps described herein.

[0328] Figure 11 is a flowchart 1100 of a base station. In step 1105, the base station transmits, on an SSB having one SSB index, an indication indicating whether to provide or broadcast the first system information, where the indication is used by the UE to determine, based on the indication, whether to initiate a random access procedure on the serving cell to request the first system information.

[0329] In one embodiment, the base station may transmit, on the SSB having the one SSB index, an indication indicating whether to provide or broadcast the first system information for the SSB and / or beam having the one SSB index.

[0330] In one embodiment, if the first system information is provided or broadcast for the SSB that can be received or acquired or detected by the UE, the random access procedure on the serving cell may not be initiated to request the first system information. If the first system information is not provided or broadcast for the SSB that can be received or acquired or detected by the UE, the random access procedure on the serving cell may be initiated to request the first system information.

[0331] In one embodiment, the indication may be indicated by the SSB or may be carried on the SSB. The indication may indicate whether the first system information is provided or broadcast for the SSB. The indication may not indicate whether the first system information is provided or broadcast for another SSB different from the SSB. The indication may indicate whether the first system information is provided or broadcast for each of multiple SSBs of the serving cell.

[0332] In one embodiment, the SSB may be the SSB selected during the random access procedure. The first system information may be SIB1.

[0333] Return for reference Figure 3 and 4 , in an exemplary embodiment, from the perspective of the base station. The UE 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the base station to transmit, on an SSB having one SSB index, an indication indicating whether the first system information is provided or broadcast, where the indication is used by the UE to determine, based on the indication, whether to initiate a random access procedure on the serving cell to request the first system information. In addition, the CPU 308 may execute the program code 312 to perform all the actions and steps described above or other actions and steps described herein.

[0334] Figure 12 is a flowchart 1200 of a user equipment (UE). At 1205, the UE initiates a random access procedure on the serving cell to request the first system information. At 1210, the UE receives an indication of whether the first system information will be provided. At step 1215, the UE determines, based on the indication, whether to obtain the first system information on the serving cell.

[0335] In one embodiment, the first system information may be SIB1. The indication may be indicated by the random access response of the random access procedure or may be carried on the random access response. The indication may be indicated by the SSB or may be carried on the SSB.

[0336] In one embodiment, if / when the indication indicates that the first system information will be provided, the UE may obtain the first system information on the serving cell. If / when the indication indicates that the first system information will not be provided, the UE may not obtain the first system information on the serving cell.

[0337] In one embodiment, the UE may determine whether to perform cell selection / reselection based on the indication. If / when the indication indicates that the first system information will be provided, the UE may perform a connection to the serving cell. If / when the indication indicates that the first system information will not be provided, the UE may select / reselect another serving cell.

[0338] Return to 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 on the serving cell to request the first system information, (ii) receive an indication as to whether the first system information will be provided, and (iii) determine whether to obtain the first system information on the serving cell based on the indication. In addition, the CPU 308 may execute the program code 312 to perform all of the actions and steps described above or other actions and steps described herein.

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

[0340] Those skilled in the art will understand that any of a variety of different technologies and techniques may 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 may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0341] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or combinations thereof, which can be designed using source decoding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as "software" or "software modules"), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functionality above. Whether this functionality is implemented as hardware or software depends upon the particular application and the 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.

[0342] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented within or performed by an integrated circuit ("IC"), access terminal, or 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, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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

[0344] The steps of a method or algorithm described in connection with aspects disclosed herein may be embodied 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 related data) and other data may 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 may be coupled to a machine such as a computer / processor (which may conveniently be referred to herein as "processor") such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The example storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and the storage medium may reside as discrete components in the user device. Further, in some aspects, any suitable computer program product may 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 may include packaging material.

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

Claims

1. A method for a user equipment, characterized in that, Comprising: The user equipment receives an indication on a synchronization signal block having a synchronization signal block index indicating whether to provide or broadcast first system information; The user equipment determines whether to initiate a random access procedure on a serving cell to request the first system information based on the indication.

2. The method according to claim 1, wherein The user equipment receives, on the synchronization signal block having the one synchronization signal block index, the indication indicating whether to provide or broadcast the first system information for the synchronization signal block and / or beam having the one synchronization signal block index.

3. The method according to claim 1, characterized in that, When the first system information is provided or broadcast for a synchronization signal block that the user equipment can receive or acquire or detect, the user equipment does not initiate the random access procedure on the serving cell to request the first system information.

4. The method according to claim 1, characterized in that When the first system information is not provided or broadcast for a synchronization signal block that the user equipment can receive or acquire or detect, the user equipment initiates the random access procedure on the serving cell to request the first system information.

5. The method according to claim 1, characterized in that, The indication is indicated by or carried on the synchronization signal block.

6. The method according to claim 5, wherein The indication indicates whether to provide or broadcast the first system information for the synchronization signal block.

7. The method according to claim 6, wherein The indication does not indicate whether to provide or broadcast the first system information for another synchronization signal block different from the synchronization signal block.

8. The method according to claim 1, wherein The indication indicates whether to provide or broadcast the first system information for each synchronization signal block among a plurality of synchronization signal blocks of the serving cell.

9. The method according to claim 1, characterized in that The synchronization signal block is a synchronization signal block selected during the random access procedure.

10. The method according to claim 1, wherein The first system information is SIB1.

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 operatively coupled to the processor; Wherein the processor is configured to execute program code stored in the memory to: Receive an indication on a synchronization signal block having a synchronization signal block index indicating whether to provide or broadcast first system information; Determine whether to initiate a random access procedure on a serving cell to request the first system information based on the indication.

12. The user equipment according to claim 11, characterized in that, The user equipment receives, on the synchronization signal block having the one synchronization signal block index, the indication indicating whether to provide or broadcast the first system information for the synchronization signal block and / or beam having the one synchronization signal block index.

13. The user equipment according to claim 11, characterized in that, When the first system information is provided or broadcast for a synchronization signal block that the user equipment can receive or acquire or detect, the user equipment does not initiate the random access procedure on the serving cell to request the first system information.

14. A method for a base station, characterized in that, Comprising: The base station transmits, on a synchronization signal block having a synchronization signal block index, an indication indicating whether to provide or broadcast first system information, wherein the indication is used by the user equipment to determine whether to initiate a random access procedure on a serving cell to request the first system information.

15. The method according to claim 14, wherein The base station transmits, on the synchronization signal block having the one synchronization signal block index, the indication indicating whether to provide or broadcast the first system information for the synchronization signal block and / or beam having the one synchronization signal block index.

16. The method according to claim 14, characterized in that, The indication is indicated by or carried on the synchronization signal block.

17. The method according to claim 14, wherein The indication indicates whether to provide or broadcast the first system information for the synchronization signal block.

18. The method according to claim 16, wherein The indication does not indicate whether to provide or broadcast the first system information for another synchronization signal block different from the synchronization signal block.

19. The method according to claim 14, wherein The synchronization signal block is the synchronization signal block selected during the random access procedure.

20. The method according to claim 14, wherein The first system information is SIB1.

Images