Method and apparatus for executing system information requests

By selecting the initial UL BWP and initiating N Msg1 repeating RA processes in the 5G mobile communication system, the problem of insufficient timing in system information requests under high frequency bands is solved, and the success rate and efficiency of system information acquisition are improved.

CN123126014APending Publication Date: 2026-11-17SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580028959.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-03-27
Filing Date
2025-04-17
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In 5G mobile communication systems, during the system information request process, especially in high-frequency bands, existing technologies struggle to effectively support efficient acquisition of system information. In particular, under the initial uplink bandwidth portion (UL BWP) configuration, the repeated SI requests of Msg1 during the RA process suffer from insufficient timing.

Method used

A method and apparatus are provided, which receive an uplink configuration message, select an initial UL BWP, and initiate a random access (RA) procedure with N Msg1 repetitions on the BWP, determine whether the RA configuration includes the RACH timing of SI parameters, and if not, apply the corresponding parameters of the RA configuration to determine the RACH timing and implement the SI request.

Benefits of technology

It improves the success rate and efficiency of system information requests, especially in the high-frequency band, ensuring that SI requests can be effectively sent on the initial UL BWP, thus meeting the communication requirements in the high-frequency band.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123126014A_ABST
    Figure CN123126014A_ABST
Patent Text Reader

Abstract

A method performed by a UE includes: receiving an uplink configuration message including at least one configuration for an initial UL BWP; and initiating a RA procedure on the selected initial UL BWP for an SI request with N Msg1 repetitions. The method further includes: selecting an RA configuration; determining whether the SI request configuration for the SI request with N Msg1 repetitions includes a RACH timing for SI parameters; and if the SI request configuration for the SI request with N Msg1 repetitions does not include the RACH timing for SI parameters, applying a configuration of corresponding parameters from the selected RA configuration to determine a RACH timing for transmitting the SI request with N Msg1 repetitions on the selected initial UL BWP. The configuration of the corresponding parameters comes from the RACH common configuration IE of the selected RA configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to wireless networks. More specifically, this disclosure relates to requests for system information. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, known as millimeter wave (mmWave), including 28GHz and 39GHz. Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been continuously carried out in the following areas: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves; parameter set support for efficient utilization of millimeter wave resources and dynamic operation of time slot formats (e.g., operating multiple subcarrier spacings); initial access technologies to support multi-beam transmission and broadband; definition and operation of BWP (bandwidth portion); new channel coding methods such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for high-reliability transmission control information; L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, there is ongoing discussion about improvements and performance enhancements to the initial 5G mobile communication technology, and the following physical layer standards have been implemented: V2X (Vehicle-to-Everything), used to assist autonomous vehicles in making driving decisions and improve user convenience based on information sent by the vehicle about its location and status; NR-U (Unlicensed New Radio), designed to enable system operation that complies with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Network (NTN), which enables direct communication between the UE and satellites to provide coverage in areas where communication with terrestrial networks is not possible; and positioning.

[0005] In addition, standardization is ongoing for the following technologies in terms of air interface architecture / protocols: Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; IAB (Integrated Access and Backhaul) to provide nodes for extending network service areas by supporting radio backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access (two-step RACH for NR) to simplify the random access process. Standardization is also ongoing for the following in terms of system architecture / services: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) that combine Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and mobile edge computing (MEC) for UE location-based reception services.

[0006] With the commercialization of 5G mobile communication systems, an exponential increase in connected devices will be linked to these networks. Therefore, enhanced functionality and performance of 5G mobile communication systems, as well as integrated operation of connected devices, are anticipated. To this end, new research is planned in the following areas: Extended Reality (XR) for efficient support of AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; improving 5G performance and reducing complexity by leveraging Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve as the foundation for the development of technologies including: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum); and RIS (reconfigurable smart surfaces); as well as full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for system optimization by leveraging satellites and AI (artificial intelligence) from the design phase and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for enabling services with complexity levels exceeding the operational limits of UEs by utilizing ultra-high-performance communication and computing resources. With the increasing prevalence of smartphones and other mobile data devices such as tablets, notebook computers, netbooks, e-book readers, and machine-type devices among consumers and businesses, the demand for wireless data traffic is rapidly increasing. To meet the rapid growth of mobile data traffic and support new applications and deployments, improving radio interface efficiency and coverage is crucial.

[0008] To meet the ever-increasing demand for wireless data traffic since the deployment of 4G communication systems and to enable various vertical applications, 5G communication systems have been developed and are currently being deployed. Enabling technologies for 5G / NR mobile communications include: massive MIMO technologies, ranging from traditional cellular bands to higher frequencies, for providing beamforming gain and supporting increased capacity; new waveforms for flexible adaptation to various services / applications with different requirements (e.g., new radio access technologies [RAT]); and new multiple access schemes for supporting massive connectivity. Summary of the Invention

[0009] Solution

[0010] This disclosure provides apparatus and methods for requesting system information.

[0011] In one embodiment, a method performed by a UE is provided. The method includes: receiving an uplink configuration message including at least one configuration for a ULBWP; and initiating a Redirect Assist (RA) procedure on a selected initial UL BWP for an SI request with N Msg1 repetitions based on at least one configuration for an initial UL BWP. The method further includes: selecting an RA configuration for the selected initial UL BWP from the at least one configuration for the initial UL BWP; determining whether the SI request configuration for the SI request with N Msg1 repetitions includes a RACH timing for SI parameters; and if the SI request configuration for the SI request with N Msg1 repetitions does not include a RACH timing for SI parameters, applying a configuration of corresponding parameters from the selected RA configuration to determine a RACH timing for sending the SI request on the selected initial UL BWP. The configuration of the corresponding parameters comes from the RACH common configuration IE of the selected RA configuration.

[0012] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver and at least one processor operatively coupled to the transceiver. The at least one processor is configured to receive an uplink configuration message including at least one configuration for an initial uplink bandwidth portion. The at least one processor is configured to: initiate a random access (RA) procedure on a selected initial UL BWP for a System Information (SI) request with N Msg1 repetitions, based on at least one configuration for the initial UL BWP. N is an integer greater than 1. The at least one processor is further configured to: select an RA configuration for the selected initial UL BWP from the at least one configuration for the initial UL BWP; determine whether the SI request configuration for the SI request with N Msg1 repetitions includes an RA channel (RACH) timing for SI parameters; and, if the SI request configuration for the SI request with N Msg1 repetitions does not include an RACH timing for SI parameters, apply a configuration of corresponding parameters from the selected RA configuration to determine the RACH timing for transmitting the SI request on the selected initial UL BWP. The corresponding parameter configurations are derived from the RACH common configuration IE of the selected RA configuration.

[0013] In another embodiment, a non-transitory computer-readable medium comprising a computer program is provided. The computer program includes program code that, when executed by a processor of a device, causes the device to receive a message including at least one configuration for a UL BWP, select an initial UL BWP based on the at least one configuration for an initial UL BWP, and initiate a RA procedure on the selected initial UL BWP for an SI request with N Msg1 repetitions. N is an integer greater than 1. When executed by the processor of the device, the program code further causes the device to:, when initiating the RA procedure, select an RA configuration for the selected initial UL BWP from at least one RA configuration for the initial UL BWP; determine whether the SI request configuration for the SI request with N Msg1 repetitions includes a RACH timing IE for the SI; and, in response to determining that the SI request configuration for the SI request with N Msg1 repetitions does not include a RACH timing IE for the SI, apply a configuration of the corresponding parameters expected in the RACH timing IE for the SI to determine a RACH timing for sending the SI request with N Msg1 repetitions on the selected initial UL BWP. The corresponding parameter configurations are derived from the RACH common configuration IE of the selected RA configuration. Attached Figure Description

[0014] To gain a more complete understanding of this disclosure and its advantages, the following description is now taken in conjunction with the accompanying drawings, in which:

[0015] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0016] Figure 2A and Figure 2B An example wireless transmission path and a reception path are shown according to an embodiment of the present disclosure;

[0017] Figure 3A An example UE is shown according to an embodiment of this disclosure;

[0018] Figure 3B An example gNB is shown according to an embodiment of this disclosure;

[0019] Figure 4 An example flow for a UE to execute an SI request with repeated Msg1, according to an embodiment of this disclosure, is shown; and

[0020] Figure 5 An example method for requesting system information is shown according to an embodiment of this disclosure. Detailed Implementation

[0021] Other technical features will be readily apparent to those skilled in the art from the following figures, description and claims.

[0022] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives cover both direct and indirect communication. The terms “include” and “comprise,” and their derivatives, mean including but not limited to. The term “or” is inclusive, indicating and / or. The phrase “associated with” and its derivatives mean containing, being included within, interconnected with, accommodating, being contained within, connected to or connected with, coupled to or coupled with, capable of communicating with, cooperating with, intertwined, juxtaposed, proximate, bound to or bound with, having, possessing the properties of, having a relationship with, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether local or remote. When the phrase “at least one of…” is used with a list of items, it indicates that different combinations of one or more of the listed items may be used, and it is possible that only one item from the list is required. For example, “at least one of A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0023] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and subsequently overwrite it, such as rewritable optical discs or erasable memory devices.

[0024] This patent document also provides definitions for certain other words and phrases. Those skilled in the art will understand that in many (if not most) cases, these definitions apply to both prior and subsequent use of the words and phrases defined in this way.

[0025] The following discussion Figures 1 to 5 The various embodiments described in this patent document to illustrate the principles of this disclosure are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged wireless communication system.

[0026] To meet the ever-increasing demand for wireless data traffic since the deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The implementation of 5G / NR communication systems in higher frequency (millimeter wave) bands (e.g., 28 GHz or 60 GHz bands) is considered for higher data rates, or in lower frequency bands such as 6 GHz for robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.

[0027] In addition, in 5G / NR communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.

[0028] The discussion of 5G systems and their associated frequency bands is for reference only, as some embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be utilized in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, or even later versions that may use terahertz (THz) frequency bands.

[0029] The following Figures 1 to 3B Various embodiments of communication technologies, such as orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), are described in wireless communication systems. Figures 1 to 3B The description is not intended to imply any physical or architectural limitation on the ways in which different embodiments may be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0030] Figure 1An example wireless network 100 according to an embodiment of the present disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0031] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., a base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0032] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes: UE 111, which may be located in a small business; UE 112, which may be located in an enterprise; UE 113, which may be a WiFi hotspot; UE 114, which may be located in a first residence; UE 115, which may be located in a second residence; and UE 116, which may be a mobile device, such as a cellular phone, wireless laptop computer, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In one embodiment, one or more of gNBs 101 to 103 may communicate with each other and with UEs 111 to 116 using 5G / NR, Long Term Evolution (LTE), LTE-A Advanced, WiMAX, WiFi, or other wireless communication technologies.

[0033] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmitting point (TP), a transmitting and receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other equipment supporting wireless functionality. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3rd Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE-Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component such as a "mobile station," "user station," "remote terminal," "wireless terminal," "receiving point," or "user device." For convenience, the terms “user equipment” and “UE” are used in this patent document to refer to a remote wireless device for wireless access to a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (such as a desktop computer or vending machine).

[0034] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the gNB (such as coverage areas 120 and 125) may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0035] As described in more detail below, one or more of UEs 111 to 116 include circuitry, programming, or a combination thereof for system information requests. In some embodiments, one or more of gNBs 101 to 103 include circuitry, programming, or a combination thereof to support system information requests in a wireless communication system.

[0036] Although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1Various modifications can be made. For example, the wireless network can include any number of gNBs and any number of UEs configured in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each of gNBs 102 to 103 can communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0037] Figure 2A and Figure 2B An example wireless transmit and receive path is illustrated according to one embodiment of this disclosure. In the following description, transmit path 200 may be described as being implemented in a gNB (such as gNB 102), and receive path 250 may be described as being implemented in a UE (such as UE 116). However, it will be understood that receive path 250 may be implemented in the gNB, and transmit path 200 may be implemented in the UE. In one embodiment, transmit path 200 and / or receive path 250 are configured to implement and / or support system information requests as described in one embodiment of this disclosure.

[0038] The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) conversion block 210, an N-point inverse fast Fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) conversion block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a serial-to-parallel (S-to-P) conversion block 265, an N-point fast Fourier transform (FFT) block 270, a parallel-to-serial (P-to-S) conversion block 275, and a channel decoding and demodulation block 280.

[0039] In transmission path 200, channel coding and modulation block 205 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. Serial-to-parallel conversion block 210 converts (such as demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the number of IFFT / FFT points used in gNB 102 and UE 116. N-point IFFT block 215 performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial conversion block 220 converts (such as multiplexes) the parallel time-domain output symbols from N-point IFFT block 215 to generate a serial time-domain signal. Cyclic prefix addition block 225 inserts a cyclic prefix into the time-domain signal. Upconverter 230 modulates (such as upconverts) the output of cyclic prefix addition block 225 to an RF frequency for transmission via the radio channel. The signal can also be filtered at the baseband before being switched to the RF frequency.

[0040] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the opposite operation to that at gNB 102. Downconverter 255 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel conversion block 265 converts the time-domain baseband signal into a parallel time-domain signal. N-point FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial conversion block 275 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

[0041] Each of gNBs 101 to 103 can implement a transmission path 200 corresponding to transmission to UEs 111 to 116 in the downlink, and a reception path 250 corresponding to reception from UEs 111 to 116 in the uplink. Similarly, each of UEs 111 to 116 can implement a transmission path 200 for transmission to gNBs 101 to 103 in the uplink, and a reception path 250 for reception from gNBs 101 to 103 in the downlink.

[0042] Figure 2A and Figure 2B Each component can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 2A and Figure 2BAt least some components can be implemented in software, while others can be implemented in configurable hardware or a hybrid of software and configurable hardware. For example, FFT block 270 and IFFT block 215 can be implemented as configurable software algorithms, where the value of the number of points N can be modified depending on the implementation.

[0043] Furthermore, although the description uses FFT and IFFT, this is for illustrative purposes only and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (such as 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of two (such as 1, 2, 4, 8, 16, etc.).

[0044] Although Figure 2A and Figure 2B An example of a wireless transmit and receive path is shown, but it is possible to modify... Figure 2A and Figure 2B Make various changes. For example, Figure 2A and Figure 2B The various components can be combined, further subdivided, or omitted according to specific needs, and additional components can be added. Furthermore, Figure 2A and Figure 2B This is intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0045] Figure 3A An example UE 116 is shown according to one embodiment of the present disclosure. Figure 3A The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111 to 115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3A This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0046] like Figure 3A As shown, UE 116 includes one or more antennas 305, one or more transceivers 310, and a microphone 320. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0047] One or more transceivers 310 receive incoming RF signals transmitted by a gNB of network 100 from antenna 305. The transceivers 310 down-convert the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signals are processed by RX processing circuitry in one or more transceivers 310 and / or processor 340, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The RX processing circuitry sends the processed baseband signals to speaker 330 (e.g., for voice data) or to processor 340 (e.g., for web browsing data).

[0048] One or more transceivers 310 and / or processor 340 receive analog or digital voice data from microphone 320, or other outbound baseband data (such as web page data, email, or interactive video game data) from processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outbound baseband data to generate a processed baseband or IF signal. One or more transceivers 310 up-convert the baseband or IF signal into an RF signal transmitted via one or more antennas 305.

[0049] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control one or more transceivers 310 to receive DL channel signals and transmit UL channel signals according to known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0050] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as processes for requesting system information, as discussed in more detail below. Processor 340 can move data into or out of memory 360 as needed by the executing process. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from the gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptops and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0051] The processor 340 is also coupled to an input 350 (which includes, for example, a touchscreen, a keyboard, etc.) and a display 355. The operator of the UE 116 can use the input 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics from a website.

[0052] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), while another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0053] Although Figure 3A An example of UE 116 is shown, but it is possible to see... Figure 3A Make various changes. For example, Figure 3A The various components can be combined, further subdivided, or omitted according to specific needs, and additional components can be added. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, one or more transceivers 310 can include any number of transceivers and signal processing chains and can be connected to any number of antennas. Furthermore, although... Figure 3A The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0054] Figure 3B An example gNB 102 is shown according to one embodiment of the present disclosure. Figure 3B The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 3B This disclosure is not intended to limit the scope to any particular implementation of gNB.

[0055] like Figure 3B As shown, gNB 102 includes multiple antennas 370a to 370n, multiple transceivers 372a to 372n, a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0056] Transceivers 372a to 372n receive incoming RF signals from antennas 370a to 370n, such as signals transmitted by a UE in network 100. Transceivers 372a to 372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in transceivers 372a to 372n and / or controller / processor 378, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. Controller / processor 378 may further process the baseband signals.

[0057] Transmit (TX) processing circuitry in transceivers 372a to 372n and / or controller / processor 378 receives analog or digital data (such as voice data, web page data, email, or interactive video game data) from controller / processor 378. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. Transceivers 372a to 372n up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a to 370n.

[0058] The controller / processor 378 may include one or more processors or other processing devices for controlling the overall operation of the gNB 102. For example, the controller / processor 378 may, based on known principles, control the transceivers 372a to 372n to receive uplink (UL) channel signals and transmit downlink (DL) channel signals. The controller / processor 378 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 378 may support beamforming or directional routing operations, wherein outgoing / incoming signals from / to multiple antennas 370a to 370n are weighted differently to effectively guide outgoing signals to a desired direction. The controller / processor 378 may support any of a wide variety of other functions within the gNB 102.

[0059] The controller / processor 378 is also capable of executing programs and other processes residing in memory 380, such as the OS and processes for supporting system information requests, as discussed in more detail below. The controller / processor 378 can move data into or out of memory 380 as needed by the executing process.

[0060] The controller / processor 378 is also coupled to a backhaul or network interface 382. The backhaul or network interface 382 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 382 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 382 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 382 can allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). Interface 382 includes any suitable architecture supporting communication via wired or wireless connections, such as Ethernet or a transceiver.

[0061] The memory 380 is coupled to the controller / processor 378. A portion of the memory 380 may include RAM, while another portion of the memory 380 may include flash memory or other ROM.

[0062] Although Figure 3B An example of gNB 102 is shown, but it is possible to see more. Figure 3B Various changes can be made. For example, gNB 102 can include any number of Figure 3B Each component is shown. Furthermore... Figure 3B The various components can be combined, further subdivided, or omitted according to specific needs, and additional components can be added.

[0063] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G) operating in higher frequency (millimeter wave) bands, UEs and gNBs use beamforming to communicate with each other. Beamforming technology is used to mitigate propagation path loss and increase the propagation distance of communication in higher frequency bands. Beamforming uses high-gain antennas to enhance transmit and receive performance. Beamforming can be divided into transmit (TX) beamforming performed at the transmitting end and receive (RX) beamforming performed at the receiving end. Typically, TX beamforming increases directivity by using multiple antennas to densely distribute the area of ​​propagation in a specific direction. In this case, the aggregation of multiple antennas can be called an antenna array, and each antenna included in the array can be called an element. Antenna arrays can be configured in various forms such as linear arrays, planar arrays, etc. Using TX beamforming increases the directivity of the signal, thereby increasing the propagation distance. Furthermore, since the signal is transmitted almost entirely outside the direction of directivity, signal interference acting on the other receiver is significantly reduced. The receiver can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the strength of the RX signal transmitted in a specific direction by focusing propagation in that direction and excludes signals transmitted in other directions from the RX signal, thus providing a blocking effect against interfering signals. By using beamforming technology, a transmitter can generate multiple transmission beammaps in different directions. Each of these transmission beammaps can also be referred to as a TX beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals within a cell because each narrow TX beam provides coverage for a portion of the cell. The narrower the TX beam, the higher the antenna gain, and therefore the greater the propagation distance of the signal transmitted using beamforming. Receivers can also generate multiple RX beammaps in different directions. Each of these receive beammaps can also be referred to as an RX beam.

[0064] Next-generation wireless communication systems (e.g., 5G, 5G+, 6G) support standalone operation mode and dual connectivity (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or NBs) via a non-ideal backhaul connection. One node acts as the primary node (MN), while the other acts as secondary nodes (SNs). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports multiple RAT dual connectivity (MR-DC) operation, where a UE in the RRC_CONNECTED state is configured to utilize radio resources provided by two different schedulers located in two different nodes providing E-UTRA access (i.e., if the node is an ng-eNB) or NR access (i.e., if the node is a gNB) via a non-ideal backhaul connection. In NR, for a UE in the RRC_CONNECTED state without carrier aggregation (CA) / DC configured, only one serving cell, including the primary cell, exists. For a UE in the RRC_CONNECTED state and configured with CA / DC, the term "serving cell" refers to a set of cells including one or more special cells (SpCells) and all secondary cells (SCells). In NR, the term Primary Cell Group (MCG) refers to a group of serving cells associated with the primary node, including the primary cell (PCell) and optionally one or more SCells. In NR, the term Secondary Cell Group (SCG) refers to a group of serving cells associated with the secondary node, including the primary SCG cell (PSCell) and optionally one or more SCells. In NR, a PCell is a serving cell in the MCG that operates on the primary frequency, in which the UE performs the initial connection establishment procedure or initiates a connection re-establishment procedure. In NR, for a UE configured with CA, an SCell is a cell that provides additional radio resources outside of the SpCell. A PSCell is a serving cell in the SCG in which the UE performs random access during the synchronization reconfiguration procedure. For dual connectivity operation, the term SpCell refers to either the PCell of the MCG or the PSCell of the SCG; otherwise, the term SpCell refers to the PCell.

[0065] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), the next-generation node B (gNB) or base station in a cell broadcasts synchronization signals and PBCH blocks (SSBs), which include primary synchronization signals and secondary synchronization signals (PSS, SSS) as well as system information (SI). SIs include common parameters required for communication within the cell. In fifth-generation wireless communication systems (also known as next-generation radio or NR), SIs are divided into primary information blocks (MIBs) and several system information blocks (SIBs). MIBs are always transmitted on the broadcast channel (BCH) at a period of 80ms and are repeated within 80ms. MIBs include parameters used to obtain SIB1 from the cell. SIB1 is transmitted on the downlink shared channel (DL-SCH) at a period of 160ms with variable transmission repetition. The default transmission repetition period for SIB1 is 20ms, but the actual transmission repetition period depends on the network implementation. For SSBs and CORESET multiplexing mode 1, the repetition transmission period for SIB1 is 20ms. For SSB and CORESET multiplexing modes 2 / 3, the transmission repetition period of SIB1 is the same as that of SSB. SIB1 includes information about the availability and scheduling of other SIBs (e.g., SIB-to-SI message mapping, period, SI window size), and an indication of whether one or more SIBs are provided only on demand, and in this case, the configuration required for the UE to perform an SI request. SIB1 is a cell-specific SIB. SIBs other than SIB1, as well as posSIBs, are carried in a SystemInformation (SI) message, which is transmitted on the DL-SCH. Only SIBs or posSIBs with the same period can be mapped to the same SI message. SIBs and location SIBs (posSIBs) are mapped to different SI messages. Each SI message is transmitted within a periodically occurring time-domain window (called the SI window, and all SI messages have SI windows of the same length). Each SI message is associated with an SI window, and the SI windows of different SI messages do not overlap. That is, only the corresponding SI message is transmitted within an SI window. SI messages can be transmitted multiple times within an SI window. Any SIB or posSIB other than SIB1 can be configured as cell-specific or area-specific using the indications in SIB1. Cell-specific SIBs apply only within the cell providing the SIB, while area-specific SIBs apply to an area called an SI area, which includes one or more cells and is identified by the systemInformationAreaID. The mapping from SIB to SI messages is configured in schedulingInfoList, while the mapping from posSIB to SI messages is configured in pos-SchedulingInfoList.Each SIB is contained in a single SI message, and each SIB and posSIB is included at most once in that SI message. For a UE in the RRC_CONNECTED state, the network can provide system information via dedicated signaling (e.g., if the UE has an active BWP that is not configured for monitoring system information in a common search space), paging, or upon UE request using the RRCReconfiguration message. In the RRC_CONNECTED state, the UE only obtains one or more required SIBs from the PCell. For PSCells and SCells, the network provides the required SIs via dedicated signaling (i.e., within the RRCReconfiguration message). However, the UE must obtain the MIB for the PSCell to obtain the SFN timing of the SCG (which may differ from the MCG). When the relevant SI of an SCell changes, the network releases and adds the relevant SCell. For PSCells, the required SIs can only be changed through synchronous reconfiguration.

[0066] The UE obtains SIB1 from its camping cell or serving cell. The UE checks the BroadcastStatus bit in SIB1 for the SI message obtained by the UE. The gNB uses the IE si-RequestConfigSUL in SIB1 to signal the SI request configuration for SanUL. If the IE si-RequestConfigSUL is not present in SIB1, the UE assumes the gNB has not signaled the SI request configuration for Supplemental Uplink (SUL). The gNB uses the IE si-RequestConfig in SIB1 to signal the SI request configuration for Normal Uplink (NUL). If the IE si-RequestConfig is not present in SIB1, the UE assumes the gNB has not signaled the SI request configuration for NUL. If the SI message the UE needs is not broadcast (i.e., the BroadcastStatus bit is set to zero), the UE initiates the transmission of an SI request. The SI request transmission process is as follows:

[0067] If the gNB notifies the SI request configuration for the SUL via signaling and the criteria for selecting the SUL are met (i.e., RSRP based on the SSB measurement of the camped cell or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is notified by the gNB via signaling [e.g., in broadcast signaling such as SIB1]), then the UE initiates the transmission of an SI request based on a message 1 (Msg1) SI request on the SUL. In other words, the UE uses one or more PRACH preambles and one or more PRACH resources in the SI request configuration of the SUL to initiate a random access (RA) procedure. The UE sends Msg1 (i.e., the random access preamble) and waits for acknowledgment for the SI request. The random access resources (one or more PRACH preambles and one or more PRACH opportunities) indicated in the SI request configuration of the SUL are used for Msg1. Msg1 is transmitted on the SUL. If an acknowledgment is received for the SI request, the UE monitors the SI window of the SI message during one or more SI cycles of the requested SI message.

[0068] Otherwise, if the gNB notifies the SI request configuration for NUL via signaling and meets the criteria for selecting NUL (i.e., if SUL is supported in the camping cell or serving cell, and the RSRP calculated based on the SSB of the camping cell or serving cell is >= rsrp-ThresholdSSB-SUL, then NUL is selected; or if SUL is not supported in the serving cell, then NUL is selected), the UE initiates an SI request based on a Msg1-based SI request on the NUL. In other words, the UE uses one or more PRACH preambles and one or more PRACH resources in the NUL's SI request configuration to initiate a random access procedure. The UE sends Msg1 (i.e., the random access preamble) and waits for acknowledgment for the SI request. The random access resources (one or more PRACH preambles and one or more PRACH opportunities) indicated in the NUL's SI request configuration are used for Msg1. Msg1 is sent on the NUL. If acknowledgment for the SI request is received, the UE monitors the SI window of the requested SI message for one or more SI cycles.

[0069] Otherwise, if the UE initiates an SI request based on a message 3 (Msg3)-based SI request, in other words, the UE initiates the transmission of an RRCSystemInfoRequest message. The UE transmits Msg1 (i.e., the random access preamble) and waits for a random access response. Common random access resources (one or more PRACH preambles and one or more PRACH timings) are used for Msg1. In the UL grant received in the random access response, the UE transmits an RRCSystemInfoRequest message and waits for acknowledgment for the SI request (i.e., the RRCSystemInfoRequest message). If acknowledgment for the SI request (i.e., the RRCSystemInfoRequest message) is received, the UE monitors the SI window of the requested SI message for one or more SI periods. Note that if SUL is configured, the UE will select the UL carrier for transmission of Msg1 in a similar manner to how the UE selects the carrier for a Msg1-based SI request. If RSRP, calculated based on the SSB of the camping cell or serving cell, is less than rsrp-ThresholdSSB-SUL, then SUL is the selected UL carrier, where rsrp-ThresholdSSB-SUL is notified by the gNB via signaling (e.g., in broadcast signaling such as SIB1). If RSRP, calculated based on the SSB of the camping cell or serving cell, is greater than or equal to rsrp-ThresholdSSB-SUL, then NUL is the selected UL carrier, where rsrp-ThresholdSSB-SUL is notified by the gNB via signaling (e.g., in broadcast signaling such as SIB1).

[0070] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), the Physical Downlink Control Channel (PDCCH) is used to schedule DL transmissions on the Physical Downlink Shared Channel (PDSCH) and UL transmissions on the Physical Uplink Shared Channel (PUSCH). The downlink control information (DCI) on the PDCCH includes: downlink assignment, which contains at least modulation and coding formats, resource allocation, and hybrid ARQ information related to the DL-SCH; and uplink scheduling authorization, which contains at least modulation and coding formats, resource allocation, and hybrid ARQ information related to the UL-SCH. In addition to scheduling, PDCCH can also be used for: activating and deactivating configured PUSCH transmissions with configuration authorization; activating and deactivating PDSCH semi-persistent transmissions; notifying one or more UEs of the slot format; notifying one or more UEs of one or more PRBs and one or more OFDM symbols that they can assume there are no transmissions for that UE; sending transmit power control (TPC) commands for the Physical Uplink Control Channel (PUCCH) and PUSCH; sending one or more TPC commands for the Sounding Reference Signal (SRS) transmissions for one or more UEs; switching the active bandwidth portion of a UE; and initiating a random access procedure. The UE monitors a set of PDCCH candidates in one or more configured control resource sets (CORESETs) at configured monitoring times, according to the corresponding search space configuration. A CORESET includes a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource elements—Resource Element Groups (REGs) and Control Channel Elements (CCEs)—are defined within a CORESET, where each CCE includes a set of REGs. Control channels are formed by the aggregation of CCEs. Different code rates for control channels are achieved by aggregating different numbers of CCEs. CORESET supports interleaved and non-interleaved CCE-to-REG mapping. Polar coding is used for PDCCH. Each resource element group carrying PDCCH carries its own demodulation reference signal (DMRS). Quadrature phase shift keying (QPSK) modulation is used for PDCCH.

[0071] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), the gNB signals a list of search space configurations for each configured BWP of the serving cell, where each search configuration is uniquely identified by a search space identifier. Each search space identifier is unique within the BWP of the serving cell. For each configured BWP, the gNB explicitly signals the identifier of the search space configuration to be used for specific purposes such as paging reception, SI reception, and random access response reception. In NR, the search space configuration includes the parameters Monitoring-periodicity-PDCCH-slot, Monitoring-offset-PDCCH-slot, Monitoring-symbols-PDCCH-within-slot, and duration. The UE uses the parameters Monitoring-periodicity-PDCCH-slot, Monitoring-offset-PDCCH-slot, and Monitoring-symbols-PDCCH-within-slot to determine one or more PDCCH monitoring opportunities within a time slot. PDCCH monitoring opportunities are located in time slots "x" to x+duration, where time slot "x" in radio frame numbered "y" satisfies the following equation:

[0072] (y (Number of time slots in a radio frame) + x - Monitoring-offset-PDCCH-slot) mod(Monitoring-periodicity-PDCCH-slot) = 0

[0073] The start symbol of the PDCCH monitoring opportunity in each slot with PDCCH monitoring opportunities is given by Monitoring-symbols-PDCCH-within-slot. The length of the PDCCH monitoring opportunity (in symbols) is given in the CORESET associated with the search space. The search space configuration includes an identifier for the CORESET configuration associated with it. The gNB notifies the list of CORESET configurations via signaling for each configured BWP of the serving cell, where each CORESET configuration is uniquely identified by a CORESET identifier. The CORESET identifier is unique within the BWP of the serving cell. Note that the duration of each radio frame is 10 ms. Radio frames are identified by either a radio frame number or a system frame number. Each radio frame consists of several slots, where the number of slots and the slot duration in a radio frame depend on the subcarrier spacing (SC). The number of slots and the slot duration in a radio frame, depending on the radio frame, are predefined in the NR for each supported SCS. Each CORESET configuration is associated with a list of Transport Configuration Indicator (TCI) states. Each TCI state configuration has a DL RSID (SSB or CSI RS). The list of TCI states corresponding to the CORESET configuration is notified by the gNB via Radio Resource Control (RRC) signaling. One of the TCI states in the TCI state list is activated by the gNB and indicated to the UE. The TCI state indicates the DL TX beam that the gNB uses to transmit the PDCCH during PDCCH monitoring in the search space (this DL TX beam has a QCL relationship with the SSB / CSIRS of the TCI state).

[0074] In next-generation wireless communication systems (e.g., 5G, beyond 5G, 6G), bandwidth adaptation (BA) is supported. Using BA, the UE's receive and transmit bandwidth does not need to be as large as the cell's bandwidth and can be adjusted: bandwidth changes can be indicated (e.g., reducing bandwidth during periods of low activity to save power); location can be moved in the frequency domain (e.g., to increase scheduling flexibility); and subcarrier spacing changes can be indicated (e.g., to allow different services). A subset of the cell's total cell bandwidth is called a bandwidth portion (BWP). BA is implemented by configuring one or more BWPs for a UE with RRC connectivity and informing the UE which of the configured BWPs is currently active. When BA is configured, the UE can monitor the PDCCH on only one active BWP (i.e., it does not have to monitor the PDCCH on the entire DL frequency of the serving cell). In RRC connectivity, one or more DL and UL BWPs are configured for the UE for each configured serving cell (i.e., PCell or SCell). For an active serving cell, there is always one active UL BWP and one active DL BWP at any given time. Serving cell BWP handover is used to activate inactive BWPs and deactivate active BWPs at specific times. BWP handover is controlled by the PDCCH indicating downlink assignment or uplink grant, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself when initiating a random access procedure. When adding a SpCell or activating an SCell, the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, respectively, are active without receiving the PDCCH indicating downlink assignment or uplink grant. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DLBWP is paired with the UL BWP, and BWP handover is common to both UL and DL. When the BWP inactivity timer expires, the UE switches the active DL BWP to the default DL BWP or the initial DL BWP (if the default DL BWP is not configured). In RRC IDLE and RRCINACTIVE states, the UE transmits to / receives from the gNB on the initial uplink BWP and initial DL BWP, respectively. For RedCap UEs, the initial uplink BWP and initial DL BWP can be optionally configured for RedCap UEs, and if configured, they are used by the RedCap UE.

[0075] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), random access (RA) is supported. RA is used to achieve UL time synchronization. RA is used during initial access, handover, RRC connection reconstruction procedures, scheduling request transmission, SCG addition / modification, beam failure recovery, and data or control information transmission by asynchronous UEs in the UL while in the RRC CONNECTED state. Several types of RA procedures are supported.

[0076] In Contention-Based Random Access (CBRA), also known as four-step CBRA, the UE first sends a random access preamble (also known as Msg1) and then waits for a random access response (RAR) within the RAR window. The RAR is also known as Msg2. The gNB sends the RAR on the PDSCH. The PDCCH carrying the RAR is addressed to the RA Radio Network Temporary Identifier (RA-RNTI). The RA-RNTI identifies the time-frequency resource in which the gNB detected the RA preamble (also known as the Physical RA Channel [PRACH] timing, PRACH TX timing, or RA Channel [RACH] timing). The RA-RNTI is calculated as follows: RA-RNTI = 1 + s_id + 14 t_id + 14 80 f_id + 14 80 8 `ul_carrier_id`, where `s_id` is the index of the first OFDM symbol in which the UE has transmitted Msg1 (i.e., the RA preamble); 0 ≤ `s_id` < 14; `t_id` is the index of the first time slot of the PRACH timing (0 ≤ `t_id` < 80); `f_id` is the index of the PRACH timing within the time slot in the frequency domain (0 ≤ `f_id` < 8), and `ul_carrier_id` is the UL carrier used for Msg1 transmission (0 for NUL carriers, 1 for SUL carriers). The gNB can multiplex several RARs for various random access preambles detected by the gNB into the same RAR Media Access Control (MAC) Protocol Data Unit (PDU). If the RAR in the MAC PDU includes the RA preamble identifier (RAPID) of the RA preamble transmitted by the UE, then the RAR corresponds to the UE's RA preamble transmission. If no RAR corresponding to the RA preamble sent by the UE is received during the RAR window, and the UE has not sent the RA preamble a configurable number of times (configured by the gNB in ​​the RACH configuration), the UE returns to the first step (i.e., the UE selects random access resources [preamble / RACH timing] and sends the RA preamble). Backoff can be applied before returning to the first step.

[0077] If a RAR corresponding to the UE's RA preamble is received, the UE sends Msg3 in the UL grant received in the RAR. Msg3 includes messages such as RRC connection request, RRC connection re-establishment request, RRC handover confirmation, scheduling request, and SI request. Msg3 may include the UE identifier (i.e., Cell Radio Network Temporary Identifier [C-RNTI], System Architecture Evolution [SAE] Temporary Mobile Subscriber Identifier [S-TMSI], or a random number). After sending Msg3, the UE starts a contention resolution timer. During the contention resolution timer's operation, if the UE receives a PDCCH addressed to the C-RNTI included in Msg3, the contention resolution is considered successful, the contention resolution timer is stopped, and the RA procedure is completed. During the contention resolution timer's operation, if the UE receives a contention resolution MAC control element (CE) including the UE's contention resolution identifier (the first X bits of the Common Control Channel [CCCH] Service Data Unit [SDU] sent in Msg3), the contention resolution is considered successful, the contention resolution timer is stopped, and the RA procedure is completed. If the contention resolution timer expires and the UE has not sent the RA preamble a configurable number of times, the UE returns to step one (i.e., the UE selects random access resources [preamble / RACH timing] and sends the RA preamble). Backoff can be applied before returning to step one.

[0078] Contention-Free Random Access (CFRA), also known as Traditional CFRA or Four-Step CFRA, is used in scenarios such as handover requiring low latency and for early timing establishment of secondary cells (Scells). The Evolved Node B (eNB) assigns a dedicated random access preamble to the UE. The UE sends the dedicated RA preamble. The eNB sends a Receiving Argument (RAR) on the PDSCH addressed to the RA-RNTI. The RAR conveys the RA preamble identifier and timing alignment information. The RAR may also include UL authorization. Similar to the Contention-Based RA (CBRA) procedure, the RAR is sent within the RAR window. CFRA is considered successfully completed upon receiving the RAR containing the RA preamble identifier (RAPID) and the RA preamble sent by the UE. In the case of RA initiated for beam failure recovery, CFRA is considered successfully completed if a PDCCH addressed to the C-RNTI is received in the search space for beam failure recovery. If the RAR window expires and the RA is not successfully completed, and the UE has not sent the RA preamble a configurable number of times (configured by the gNB in ​​the RACH configuration), then the UE will retransmit the RA preamble.

[0079] For certain events such as handover and beam failure recovery, if one or more dedicated preambles are assigned to the UE, the UE determines whether to send a dedicated or non-dedicated preamble during the first step of random access (i.e., during random access resource selection for Msg1 transmission). Dedicated preambles are typically provided for a subset of SSB / CSI RSs. If, among the SSB / CSI RSs for which the gNB provides contention-free random access resources (i.e., dedicated preambles / ROs), there are no SSB / CSI RSs with a DLRSRP higher than a threshold, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. During the RA procedure, one random access attempt can be a CFRA, while other random access attempts can be CBRAs.

[0080] For two-step contention-based random access (two-step CBRA), in the first step, the UE transmits a random access preamble on the PRACH and a payload (i.e., MAC PDU) on the PUSCH. The transmission of the random access preamble and payload is also referred to as message A (MsgA). In the second step, after the transmission of MsgA, the UE monitors for a response from the network (i.e., gNB) within a configured window. This response is also referred to as message B (MsgB). The gNB transmits MsgB on the PDSCH. The PDCCH of the PDSCH carrying MsgB is addressed to the MsgB radio network temporary identifier (MSGB-RNTI). The MSGB-RNTI identifies the time-frequency resource in which the gNB detected the RA preamble (also referred to as the PRACH timing, PRACH TX timing, or RACH timing). The MSGB-RNTI is calculated as follows: RA-RNTI = 1 + s_id + 14 t_id + 14 80 f_id + 14 80 8 ul_carrier_id + 14 Х 80 Х 8 Х 2, where s_id is the index of the first OFDM symbol of the PRACH timing in which the UE has transmitted MsgA (i.e., RA preamble); 0 ≤ s_id < 14; t_id is the index of the first slot of the PRACH timing (0 ≤ t_id < 80); f_id is the index of the PRACH timing within the slot in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for NUL carriers and 1 for SUL carriers).

[0081] If a CCCH SDU is sent in the MsgA payload, the UE uses the contention resolution information in MsgB to perform contention resolution. Contention resolution is successful if the contention resolution identifier received in MsgB matches the first 48 bits of the CCCH SDU sent in MsgA. If a C-RNTI is sent in the MsgA payload, contention resolution is successful if the UE receives a PDCCH addressed to the C-RNTI. If contention resolution is successful, the random access procedure is considered to have completed successfully. MsgB may include backoff information corresponding to the random access preamble sent in MsgA, instead of contention resolution information corresponding to the sent MsgA. If backoff information is received, the UE sends Msg3 and performs contention resolution using Msg4, as in the CBRA procedure. If contention resolution is successful, the random access procedure is considered to have completed successfully. If contention resolution fails during backoff (i.e., when sending Msg3), the UE retransmits MsgA. If the configured window period for monitoring the network response after sending MsgA expires, and the UE has not yet received MsgB including the contention resolution information or fallback information as described above, the UE retransmits MsgA. If the random access procedure fails to complete successfully even after sending MsgA a configurable number of times, the UE falls back to the four-step RACH procedure (i.e., the UE only sends the PRACH preamble).

[0082] The MsgA payload may include one or more of the following: CCCH SDU, Dedicated Control Channel (DCCH) SDU, Dedicated Traffic Channel (DTCH) SDU, Buffer Status Report (BSR) MAC Control Element (CE), Power Headroom Report (PHR) MAC CE, SSB information, C-RNTI MAC CE, or padding. The MsgA may include the UE ID (e.g., random ID, S-TMSI, C-RNTI, recovery ID, etc.) and a preamble in the first step. The UE ID may be included in the MAC PDU of the MsgA. UE IDs such as C-RNTI may be carried in the MAC CE, which is included in the MAC PDU. Other UE IDs (such as random ID, S-TMSI, C-RNTI, recovery ID, etc.) may be carried in the CCCH SDU. The UE ID may be one of the following: random ID, S-TMSI, C-RNTI, recovery ID, IMSI, idle mode ID, inactive mode ID, etc. The UE ID may differ in different scenarios in which the UE performs the RA procedure. When a UE performs a Re-Activation (RA) after power-on (before attaching to the network), the UE ID is a random ID. When a UE performs an RA in IDLE state after attaching to the network, the UE ID is the S-TMSI. If the UE has an assigned C-RNTI (e.g., in connected state), the UE ID is the C-RNTI. When the UE is in INACTIVE state, the UE ID is the recovery ID. In addition to the UE ID, some additional control information can be sent in the MsgA. The control information can be included in the MAC PDU of the MsgA. The control information may include one or more of the following: connection request indication, connection recovery request indication, SI request indication, buffer status indication, beam information (e.g., one or more DL TX beam IDs or SSB IDs), beam failure recovery indication / information, data indicator, cell / BS / TRP handover indication, connection re-establishment indication, reconfiguration complete or handover complete message, etc.

[0083] In the case of two-step contention-free random access (two-step CFRA), the gNB assigns the UE one or more dedicated random access preambles and one or more PUSCH resources for MsgA transmission. It can also indicate the RACH timing (RO) to be used for preamble transmission. In the first step, the UE uses the contention-free random access resources (i.e., dedicated preamble / PUSCH resources / RO) to transmit the random access preamble on the PRACH and the payload on the PUSCH. In the second step, after MsgA transmission, the UE monitors for a response from the network (i.e., the gNB) within a configured window. This response is also referred to as MsgB.

[0084] The gNB transmits MsgB on the PDSCH. The PDCCH that schedules the PDSCH carrying MsgB addresses the MsgB radio network temporary identifier (MSGB-RNTI). The MSGB-RNTI identifies the time-frequency resource in which the gNB detected the RA preamble (also known as the PRACH timing, PRACH TX timing, or RACH timing). The MSGB-RNTI is calculated as follows: RA-RNTI = 1 + s_id + 14 t_id + 14 80 f_id + 14 80 8 ul_carrier_id + 14 Х 80 Х 8 Х 2, where s_id is the index of the first OFDM symbol of the PRACH timing in which the UE has transmitted Msg1 (i.e., the RA preamble); 0 ≤ s_id < 14; t_id is the index of the first slot of the PRACH timing (0 ≤ t_id < 80); f_id is the index of the PRACH timing within the slot in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for NUL carriers and 1 for SUL carriers).

[0085] If the UE receives a PDCCH addressed to C-RNTI, the random access procedure is considered to have completed successfully. If the UE receives a backoff message corresponding to the preamble it sent, the random access procedure is considered to have completed successfully.

[0086] For certain events such as handover and beam failure recovery, if one or more dedicated preambles and one or more PUSCH resources are assigned to the UE, the UE determines whether to transmit a dedicated preamble or a non-dedicated preamble during the first step of random access (i.e., during random access resource selection for MsgA transmission). Dedicated preambles are typically provided for a subset of SSB / CSI RSs. If, among the SSB / CSI RSs for which the gNB provides contention-free random access resources (i.e., dedicated preamble / RO / PUSCH resources), there are no SSB / CSI RSs with a DL RSRP higher than a threshold, the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. During the RA procedure, a single random access attempt can be a two-step CFRA, while other random access attempts can be two-step CBRAs.

[0087] When initiating a random access procedure, the UE first selects an uplink carrier (SUL or NUL). If the gNB explicitly notifies via signaling of the carrier to be used for the random access procedure, the UE selects the signaled carrier to perform the random access procedure. If (i) the gNB does not explicitly notify via signaling of the carrier to be used for the random access procedure, and (ii) the serving cell used for the random access procedure has a supplementary uplink configured, and (iii) the downlink path loss reference RSRP is less than rsrp-ThresholdSSB-SUL, the UE selects an SUL carrier to perform the random access procedure. Otherwise, the UE selects an NUL carrier to perform the random access procedure. When selecting the UL carrier, the UE determines the UL BWP and DL BWP to be used for the random access procedure. Then, the UE determines whether to perform a two-step RACH or a four-step RACH for this random access procedure as follows:

[0088] If (i) the random access procedure is initiated by a PDCCH command, and (ii) if the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, the UE selects a four-step RACH. Otherwise, if the gNB signals two contention-free random access resources for the random access procedure, the UE selects a two-step RACH. Otherwise, if the gNB signals four contention-free random access resources for the random access procedure, the UE selects a four-step RACH. Otherwise, if the UL BWP selected for the random access procedure is configured with only two-step RACH resources, the UE selects a two-step RACH. Otherwise, if the UL BWP selected for the random access procedure is configured with only four-step RACH resources, the UE selects a four-step RACH. Otherwise, if the UL BWP selected for the random access procedure is configured with both two-step and four-step RACH resources, the UE selects a four-step RACH if the downlink path loss reference RSRP is lower than the configured threshold. Otherwise, the UE selects a two-step RACH.

[0089] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), support for UEs with reduced capabilities is required.

[0090] RedCap UE refers to a UE with the following reduction capabilities:

[0091] - For FR1 (i.e., the frequency range of 410MHz to 7125MHz), the maximum bandwidth is 20MHz, and for FR2 (i.e., the frequency range of 24250MHz to 52600MHz), the maximum bandwidth is 100MHz. RedCap UEs do not support UE features and corresponding capabilities associated with UE bandwidths wider than 20MHz in FR1 or wider than 100MHz in FR2;

[0092] - The maximum number of data radio bearers (DRBs) that are mandatory to support is 8;

[0093] - The mandatory supported Packet Data Convergence Protocol (PDCP) sequence number (SN) length is 12 bits, and an 18-bit PDCP SN length is optional;

[0094] - The mandatory supported Radio Link Control (RLC) Acknowledgment Mode (AM) SN length is 12 bits, and the 18-bit RLCAM SN length is optional;

[0095] - For FR1, if one Rx branch is supported, it is one DL MIMO layer; if two Rx branches are supported, it is two DL MIMO layers. For FR2, one or two DL MIMO layers can be supported, while two Rx branches are always supported. For FR1 and FR2, RedCap UEs do not support UE features and corresponding capabilities associated with more than two UE Rx branches or more than two DL MIMO layers, nor do they support UE features and capabilities associated with more than one UE Tx branch or more than one UL MIMO layer.

[0096] - RedCap UEs do not support UE features and corresponding capabilities related to CA, MR-DC, DAPS, CPAC, and IAB (i.e., RedCap UEs are not expected to act as IAB nodes). Unless otherwise indicated, all other feature groups or components of feature groups and capabilities specified in this specification still apply to RedCap UEs as well as non-RedCap UEs.

[0097] Enhanced RedCap (eRedCap) UE refers to a UE that, in addition to the reduction capabilities defined for RedCap UEs above, also possesses one or more of the following reduction capabilities:

[0098] The UE baseband (BB) bandwidth is reduced;

[0099] 5MHz BB bandwidth for PDSCH (for both unicast and broadcast) and PUSCH only, and 20MHz RF bandwidth for UL and DL;

[0100] Other physical channels and signals are still allowed to use BWP up to 20MHz of maximum RF+BB bandwidth for the UE.

[0101] The peak data rate of the UE decreased.

[0102] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), to enhance UL coverage, repeated PRACH transmissions within a single random access attempt (or PRACH attempt) are considered. For multiple PRACH transmissions within a single PRACH attempt, the PRACH transmissions are sent only on the RO associated with the same SSB / CSI-RS. For multiple PRACH transmissions with the same Tx beam within a single PRACH attempt, transmit power ramping is not applied within the single PRACH attempt. For multiple PRACH transmissions with the same Tx beam, only one RAR window for RAR monitoring is supported for a single PRACH attempt. For multiple PRACH transmissions with the same Tx beam, to distinguish multiple PRACH transmissions from single PRACH transmissions, it is supported to send multiple PRACH transmissions on separate ROs. For multiple PRACH transmissions with the same Tx beam, to distinguish multiple PRACH transmissions from single PRACH transmissions, it is supported to send multiple PRACH transmissions on a shared RO using separate preambles. For multiple PRACH transmissions with the same Tx beam, the gNB can configure one or more values ​​for the number of PRACH transmissions. If multiple values ​​are configured, PRACH resource differentiation is supported between multiple PRACH transmissions with different numbers of PRACH transmissions.

[0103] In next-generation wireless communication systems (e.g., 5G, 5G+, 6G), a UE in the RRC IDLE / RRC_INACTIVE state can camp on a cell. An initial uplink BWP for NUL (configured by the initialUplinkBWP field) can be configured for the cell in SIB1, and / or an initial uplink BWP for SUL (configured by the initialUplinkBWP field) can be configured for the cell in SIB1, and / or a RedCap-specific initial uplink BWP for NUL (configured by the initialUplinkBWP-Redcap field) can be configured for the cell in SIB1. Each of these BWPs can be configured with one or more random access resource configurations or one or more random access resource sets. A random access resource configuration or a random access resource set can be associated with a feature or a combination of features, or not associated with any feature. For example, the feature can be one of SDT, Msg1 repeat, slicing, Msg3 repeat, redcap, etc. The random access resource configuration includes (at least) a RACH common configuration IE (RACH-ConfigCommon). RACH-ConfigCommon can look something like the following:

[0104] RACH-ConfigCommon ::= SEQUENCE {

[0105] rach-ConfigGeneric RACH-ConfigGeneric,

[0106] totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, -- Need S

[0107] ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE {

[0108] oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

[0109] oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

[0110] oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

[0111] one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},

[0112] two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32},

[0113] four INTEGER (1..16),

[0114] eight INTEGER (1..8),

[0115] sixteen INTEGER (1..4)

[0116] } OPTIONAL, -- Need M

[0117] groupBconfigured SEQUENCE {

[0118] ra-Msg3SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480,b640,

[0119] b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1},

[0120] messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8,dB10, dB12, dB15, dB18},

[0121] numberOfRA-PreamblesGroupA INTEGER (1..64)

[0122] } OPTIONAL, -- Need R

[0123] ra-ContentionResolutionTimer ENUMERATED { sf8, sf16, sf24, sf32,sf40, sf48, sf56, sf64},

[0124] rsrp-ThresholdSSB RSRP-Range OPTIONAL, -- Need R

[0125] rsrp-ThresholdSSB-SUL RSRP-Range OPTIONAL, -- Cond SUL

[0126] prach-RootSequenceIndex CHOICE {

[0127] l839 INTEGER (0..837),

[0128] l139 INTEGER (0..137)

[0129] },

[0130] msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond L139

[0131] restrictedSetConfig ENUMERATED {unrestrictedSet, restrictedSetTypeA,restrictedSetTypeB},

[0132] msg3-transformPrecoder ENUMERATED {enabled} OPTIONAL, -- Need R

[0133] ..., [[

[0135] ra-PrioritizationForAccessIdentity-r16 SEQUENCE {

[0136] ra-Prioritization-r16 RA-Prioritization,

[0137] ra-PrioritizationForAI-r16 BIT STRING (SIZE (2))

[0138] } OPTIONAL, -- Cond InitialBWP-Only

[0139] prach-RootSequenceIndex-r16 CHOICE {

[0140] l571 INTEGER (0..569),

[0141] l1151 INTEGER (0..1149)

[0142] } OPTIONAL -- Need R

[0143] ]], [[

[0145] ra-PrioritizationForSlicing-r17 RA-PrioritizationForSlicing-r17OPTIONAL, -- Cond InitialBWP-Only

[0146] featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL --Cond AdditionalRACH ]]

[0148] }

[0149] As described above, a UE can be either an (e)RedCap UE or a non-(e)rRedCap UE. A non-RedCap UE is a UE that is neither a RedCap UE nor an eRedCap UE.

[0150] SI request configuration for Msg1 repetitions can be configured in SIB1 for the initial uplink BWP on the NUL. SI request configuration for Msg1 repetitions can also be configured in SIB1 for the initial uplink BWP on the SUL. SI request configuration for Msg1 repetitions can also be configured in SIB1 for RedCap-specific initial uplink BWPs on the NUL. SI request configuration for Msg1 repetitions can include SI request resources for 2 and / or 4 and / or 8 repetitions.

[0151] The configuration for repeated SI requests for Msg1 can include the rach-OccasionsSI IE. The rach-OccasionsSI IE can be defined as follows:

[0152] rach-OccasionsSI-r18 SEQUENCE {

[0153] rach-ConfigSI-r18 RACH-ConfigGeneric,

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

[0155] }

[0156] RACH-ConfigGeneric ::= SEQUENCE {

[0157] prach-ConfigurationIndex INTEGER (0..255),

[0158] msg1-FDM ENUMERATED {one, two, four, eight},

[0159] msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1),

[0160] zeroCorrelationZoneConfig INTEGER(0..15),

[0161] preambleReceivedTargetPower INTEGER (-202..-60),

[0162] preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50,n100, n200},

[0163] powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},

[0164] ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40,sl80},

[0165] ..., [[

[0167] prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need R

[0168] prach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, --Need R

[0169] prach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- NeedR

[0170] ra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need R

[0171] prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R

[0172] ]], [[

[0174] ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960,sl1280, sl1920, sl2560} OPTIONAL -- Need R ]]

[0176] }

[0177] For an SI request with Msg1 repetition on a BWP (which can be an initial uplink BWP on an SUL, an initial uplink BWP on an NUL, or a RedCap-specific initial uplink BWP), the UE applies the configuration in the `rach-OccasionsSI IE` included in the "SI request configuration for Msg1 repetition" of that BWP to determine the RACH timing for sending the SI request. However, it is not defined which configuration of the BWP should be applied when the `rach-OccasionsSI IE` is not included in the `SI request configuration for Msg1 repetition`. To overcome this problem, various embodiments of this disclosure provide a mechanism for the UE to determine which BWP configuration to apply when the `SI request configuration for Msg1 repetition` does not include the `rach-OccasionsSI IE`.

[0178] Figure 4 An example process 400 for a UE to execute an SI request with Msg1 repeated is shown according to an embodiment of the present disclosure. Figure 4 The illustrated embodiments of the process are for illustrative purposes only. Figure 4 The one or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Other embodiments for a UE to perform a process with repeated Msg1 SI requests may be used without departing from the scope of this disclosure.

[0179] exist Figure 4In the example, process 400 is performed by a UE in the RRC IDLE / RRC_INACTIVE state (such as...). Figure 1 The UE (116) performs this operation. The UE camps on the cell. An initial uplink BWP for NUL (configured by the initialUplinkBWP field), an initial uplink BWP for SUL (configured by the initialUplinkBWP field), and a RedCap-specific initial uplink BWP for NUL (configured by the initialUplinkBWP-Redcap field) can be configured for this cell in SIB1. Each of these BWPs can be configured with one or more random access resource configurations. In some embodiments, a random access resource configuration may be associated with a feature or a combination of features, or not associated with any feature. In some embodiments, the feature may be one of Small Data Transmission (SDT), Msg1 repeat, slicing, Msg3 repeat, RedCap, etc. The random access resource configuration includes at least the RACH Common Configuration (RACH-ConfigCommon) IE.

[0180] In some embodiments, the UE can be an (e)RedCap UE or a non-(e)RedCap UE. A non-RedCap UE is a UE that is neither a RedCap UE nor an eRedCap UE.

[0181] In some embodiments, an SI request configuration for Msg1 repetition can be configured in SIB1 for the initial uplink BWP on the NUL. In some embodiments, an SI request configuration for Msg1 repetition can be configured in SIB1 for the initial uplink BWP on the SUL. In some embodiments, an SI request configuration for Msg1 repetition can be configured in SIB1 for the RedCap-specific initial uplink BWP on the NUL. In some embodiments, the SI request configuration for Msg1 repetition may include SI request resources for 2 and / or 4 and / or 8 repetitions.

[0182] In some embodiments, the SI request configuration for Msg1 repetition may include a rach-OccasionsSI IE.

[0183] exist Figure 4 In the example, procedure 400 begins with operation 410. At operation 410, the UE initiates an RA procedure on the BWP for an SI request with N Msg1 repetitions. For example, in some embodiments, N can be 2, 4, or 8. The BWP is one of the initial uplink BWP on the SUL, the initial uplink BWP on the NUL, and the RedCap-specific initial uplink BWP on the NUL.

[0184] At operation 420, the UE determines whether to perform an SI request with N Msg1 repetitions on the RedCap-specific initial uplink BWP (initialUplinkBWP-Redcap) on the NUL. If an SI request with N Msg1 repetitions is performed on initialUplinkBWP-Redcap, or if the UE is an (e)RedCap UE and performs an SI request with N Msg1 repetitions on initialUplinkBWP-Redcap, the method proceeds to operation 440. Otherwise (e.g., performing an SI request with N Msg1 repetitions on the initialUplinkBWP on the SUL or the initialUplinkBWP on the NUL), the method proceeds to operation 430.

[0185] At operation 430, the UE selects a random access resource configuration / set for the BWP (i.e., initialUplinkBWP), wherein the selected random access resource configuration / set is configured only with Msg1 repeat indication and is associated with N Msg1 repeats.

[0186] At operation 440, the UE selects a random access resource configuration / set for the BWP (i.e., initialUplinkBWP-Redcap), wherein the selected random access resource configuration / set is configured only with RedCap indication and Msg1 repeat indication, and is associated with N Msg1 repeats.

[0187] At step 450, the UE determines whether the `rach-OccasionsSIIE` is configured in the SI request configuration for Msg1 repetition in the BWP. If `rach-OccasionsSIIE` is configured in the SI request configuration for Msg1 repetition in the BWP, then procedure 400 proceeds to operation 470. Otherwise, procedure 400 proceeds to operation 460.

[0188] At operation 460, the UE applies the corresponding parameters from the selected random access resource configuration / set (expected in the rach-OccasionsSI IE) and determines the RACH timing for sending the SI request. The UE can apply the configurations of the RACH-ConfigGeneric IE and ssb-perRACH-Occasion from the RACH-ConfigCommon IE of the selected random access resource configuration / set.

[0189] At operation 470, the UE applies the configuration in the `rach-OccasionsSI` IE included in the SI request configuration for Msg1 repetition in the BWP to determine the RACH timing for sending the SI request. For example, the UE can apply the configurations of the `RACH-ConfigGeneric` IE and `ssb-perRACH-Occasion` from the `rach-OccasionsSI` IE.

[0190] At operation 480, the UE applies additional random access configurations / parameters from the selected random access resource configuration / set (e.g., RACH-ConfigCommon IE from the selected random access resource configuration / set) (i.e., configurations / parameters other than those included in the rach-OccasionsSI IE) and sends an SI request in one of the RACH times.

[0191] Although Figure 4 An example procedure 400 is shown for a UE to execute an SI request with Msg1 repeated, but it is possible to modify the procedure 400. Figure 4 Make various changes. For example, although it is shown as a series of operations, Figure 4 Various operations in the process can overlap, occur in parallel, occur in different orders, occur any number of times, be omitted, or be replaced by other steps.

[0192] Figure 5 An example method 500 for requesting system information is shown according to an embodiment of the present disclosure. Figure 5 The embodiments of the methods shown are for illustrative purposes only. Figure 5 The one or more components shown may be implemented in dedicated circuitry configured to perform the function, or one or more of the components may be implemented by one or more processors that execute instructions to perform the function. Other embodiments of the method for requesting system information may be used without departing from the scope of this disclosure.

[0193] exist Figure 5 In the example, method 500 begins with step 510. At step 510, the UE (such as...) Figure 1 UE 116) receives (e.g., from such as Figure 1 The gNB 102 BS includes at least one configuration message for the initial UL BWP.

[0194] At step 520, the UE selects the initial UL BWP based on at least one configuration for the initial UL BWP.

[0195] At step 530, the UE initiates an RA procedure on the selected initial UL BWP for an SI request with N Msg1 repetitions. N is an integer greater than 1.

[0196] At step 540, when initiating the RA procedure, the UE selects an RA configuration for the selected initial UL BWP from at least one RA configuration for the initial UL BWP.

[0197] At step 550, the UE determines whether the SI request configuration for a SI request with N Msg1 repetitions includes a RACH timing IE for the SI.

[0198] At step 560, in response to determining that the SI request configuration for a SI request with N Msg1 repetitions does not include the RACH timing IE for SI, the UE application expects the configuration of the corresponding parameter in the RACH timing IE for SI to determine the RACH timing for transmitting the SI request with N Msg1 repetitions on the selected initial UL BWP. For example, the configuration of the corresponding parameter can come from the RACH common configuration IE of the selected RA configuration.

[0199] In some embodiments, in response to determining the SI request configuration for a SI request with N Msg1 repetitions, including the RACH timing IE for SI, the UE may apply the configuration in the RACH timing IE for SI to determine the RACH timing for sending the SI request on the selected initial UL BWP.

[0200] In some embodiments, the UE may apply RA configuration parameters from the selected RA configuration that are not configured in the RACH timing IE used for SI.

[0201] In some embodiments, at least one configuration for the initial UL BWP may include configuration for at least one of the initial uplink BWP on the NUL, the initial uplink BWP on the SUL, and the RedCap-specific initial uplink BWP on the NUL.

[0202] In some embodiments, the UE can be a RedCap UE. In some embodiments, the UE can be an eRedCap UE.

[0203] In some embodiments, the UE can determine whether to perform an SI request with N Msg1 repetitions on a RedCap-specific initial UL BWP. When it is determined that an SI request with N Msg1 repetitions should be performed on a RedCap-specific initial UL BWP, the selected RA configuration may be an RA configuration that only configures the RedCap indication and the Msg1 repetition indication and is associated with N Msg1 repetitions. When it is determined that an SI request with N Msg1 repetitions should not be performed on a RedCap-specific initial UL BWP, the selected RA configuration may be an RA configuration that only configures the Msg1 repetition indication and is associated with N Msg1 repetitions.

[0204] Although Figure 5 An example method 500 for system information requests is shown, but it is possible to use other methods. Figure 5 Various changes were made. For example, although it was shown as a series of steps, Figure 5 The various steps in the process can overlap, occur in parallel, occur in different orders, occur any number of times, be omitted, or be replaced by other steps.

[0205] In one embodiment, a method performed by a UE is provided. The method includes: receiving an uplink configuration message including at least one configuration for a ULBWP; and initiating a Redirect Assist (RA) procedure on a selected initial UL BWP for an SI request with N Msg1 repetitions based on at least one configuration for an initial UL BWP. The method further includes: selecting an RA configuration for the selected initial UL BWP from the at least one configuration for the initial UL BWP; determining whether the SI request configuration for the SI request with N Msg1 repetitions includes a RACH timing for SI parameters; and if the SI request configuration for the SI request with N Msg1 repetitions does not include a RACH timing for SI parameters, applying a configuration of corresponding parameters from the selected RA configuration to determine a RACH timing for sending the SI request on the selected initial UL BWP. The configuration of the corresponding parameters comes from the RACH common configuration IE of the selected RA configuration.

[0206] In one embodiment, where the SI request configuration for an SI request with N Msg1 repetitions includes RACH timing for the SI parameters, the method includes applying the configuration in the RACH timing for the SI parameters to determine the RACH timing for sending the SI request on a selected initial UL BWP.

[0207] In one embodiment, the method further includes determining whether to perform an SI request with N Msg1 repetitions on a RedCap-specific initial ULBWP. If it is determined that the SI request with N Msg1 repetitions should be performed on a RedCap-specific initial ULBWP, the selected RA configuration is an RA configuration configured only with a RedCap indication and a Msg1 repetition indication and associated with the N Msg1 repetitions.

[0208] In one embodiment, if it is determined that an SI request with N Msg1 repetitions will not be executed on a specific initial UL BWP of RedCap, the selected RA configuration is an RA configuration that is configured only with Msg1 repetition indication and associated with the N Msg1 repetitions.

[0209] In one embodiment, the UE is a RedCap UE or an enhanced RedCap (eRedCap) UE.

[0210] In one embodiment, the method further includes applying RA configuration parameters from the selected RA configuration that were not configured in the RACH timing IE for SI.

[0211] In one embodiment, at least one configuration for the initial UL BWP includes a configuration for at least one of the initial uplink BWP on the normal uplink (NUL), the initial uplink BWP on the supplementary uplink (SUL), or the RedCap-specific initial uplink BWP on the normal uplink (NUL).

[0212] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver and at least one processor operatively coupled to the transceiver. The at least one processor is configured to receive an uplink configuration message including at least one configuration for an initial uplink bandwidth portion. The at least one processor is configured to: initiate a random access (RA) procedure on a selected initial UL BWP for a System Information (SI) request with N Msg1 repetitions, based on at least one configuration for the initial UL BWP. N is an integer greater than 1. The at least one processor is further configured to: select an RA configuration for the selected initial UL BWP from the at least one configuration for the initial UL BWP; determine whether the SI request configuration for the SI request with N Msg1 repetitions includes an RA channel (RACH) timing parameter for the SI; and, if the SI request configuration for the SI request with N Msg1 repetitions does not include an RACH timing parameter for the SI parameter, apply a configuration of corresponding parameters from the selected RA configuration to determine the RACH timing for transmitting the SI request on the selected initial UL BWP. The corresponding parameter configurations are derived from the RACH common configuration IE of the selected RA configuration.

[0213] Any of the above-described variant embodiments can be used independently or in combination with at least one other variant embodiment. The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0214] While this disclosure has been described with reference to exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. Nothing described herein should be construed as implying that any particular element, step, or function is essential and must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receive an uplink configuration message that includes at least one configuration for the initial uplink (UL) bandwidth portion (BWP); Based on at least one configuration for the initial UL BWP, a random access (RA) procedure is initiated on the selected initial UL BWP for a system information (SI) request with N repetitions of message 1 (Msg1). Select the RA configuration for the selected initial UL BWP from at least one configuration for the initial UL BWP; Determine whether the SI request configuration for an SI request with N Msg1 repetitions includes the RA channel (RACH) timing for the SI parameters; as well as In cases where the SI request configuration for an SI request with N Msg1 repetitions does not include the RACH timing for the SI parameters, the configuration of the corresponding parameters from the selected RA configuration is applied to determine the RACH timing for sending the SI request on the selected initial UL BWP.

2. The method of claim 1, wherein, in the case that the SI request configuration for an SI request with N Msg1 repetitions includes RACH timing for SI parameters, the configuration in the RACH timing for SI parameters is applied to determine the RACH timing for sending the SI request on the selected initial UL BWP.

3. The method according to claim 1, further comprising: Determine whether to execute an SI request with N Msg1 repetitions on a specific initial UL BWP for Capability Reduction (RedCap). Specifically, when it is determined that an SI request with N Msg1 repetitions will be executed on a specific initial UL BWP of RedCap, the selected RA configuration is an RA configuration that is configured only with RedCap indication and Msg1 repetition indication and associated with N Msg1 repetitions.

4. The method according to claim 3, wherein, If it is determined that an SI request with N Msg1 repetitions will not be executed on a specific initial UL BWP of RedCap, the selected RA configuration is an RA configuration that is only configured with Msg1 repetition indication and associated with N Msg1 repetitions.

5. The method according to claim 3, wherein, The UE is a RedCap UE or an enhanced RedCap (eRedCap) UE.

6. The method of claim 1, further comprising applying RA configuration parameters from the selected RA configuration that are not configured in the RACH timing IE for SI.

7. The method according to claim 1, wherein, At least one configuration for the initial UL BWP includes configurations for at least one of the following: Initial uplink BWP on Normal Uplink (NUL); Supplement the initial uplink BWP on the uplink (SUL); and RedCap-specific initial uplink BWP on normal uplink (NUL).

8. A user equipment (UE), comprising: transceiver; as well as At least one processor, operatively coupled to the transceiver, is configured to: Receive an uplink configuration message that includes at least one configuration for the initial uplink (UL) bandwidth portion (BWP); Based on at least one configuration for the initial UL BWP, a random access (RA) procedure is initiated on the selected initial UL BWP for a system information (SI) request with N repetitions of message 1 (Msg1). Select the RA configuration for the selected initial UL BWP from at least one configuration for the initial UL BWP; Determine whether the SI request configuration for an SI request with N Msg1 repetitions includes the RA channel (RACH) timing for the SI parameters; as well as In cases where the SI request configuration for an SI request with N Msg1 repetitions does not include the RACH timing for the SI parameters, the configuration of the corresponding parameters from the selected RA configuration is applied to determine the RACH timing for sending the SI request on the selected initial UL BWP.

9. The UE according to claim 8, wherein, The at least one processor is further configured to: when the SI request configuration for the SI request having N Msg1 repetitions includes the RACH timing for the SI parameters, apply the configuration in the RACH timing for the SI parameters to determine the RACH timing for sending the SI request on the selected initial UL BWP.

10. The UE according to claim 8, wherein, The at least one processor is also configured to determine whether to execute an SI request with N Msg1 repetitions on a specific initial UL BWP for Capability Reduction (RedCap). Specifically, when it is determined that an SI request with N Msg1 repetitions will be executed on a specific initial UL BWP of RedCap, the selected RA configuration is an RA configuration that is configured only with RedCap indication and Msg1 repetition indication and associated with N Msg1 repetitions.

11. The UE according to claim 10, wherein, If it is determined that an SI request with N Msg1 repetitions will not be executed on a specific initial UL BWP of RedCap, the selected RA configuration is an RA configuration that is only configured with Msg1 repetition indication and associated with N Msg1 repetitions.

12. The UE according to claim 10, wherein, The UE is a RedCap UE or an enhanced RedCap (eRedCap) UE.

13. The UE according to claim 8, wherein, The at least one processor is configured to apply RA configuration parameters from the selected RA configuration that are not configured in the RACH timing IE for SI.

14. The UE according to claim 8, wherein, At least one configuration for the initial UL BWP includes configurations for at least one of the following: Initial uplink BWP on Normal Uplink (NUL); Supplement the initial uplink BWP on the uplink (SUL); and RedCap-specific initial uplink BWP on NUL.