System and method for system information request in a cell supporting multiple uplink carriers
By selecting the appropriate carrier between the terminal and the base station for SI request, the problem of inefficiency of the SI request process in the next generation of wireless communication systems is solved, and more efficient SI request transmission is achieved.
Patent Information
- Application Number
- CN201980078282.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-11-27
- Filing Date
- 2019-11-27
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-11-27
AI Technical Summary
In the next generation of wireless communication systems, there is a need to develop a system information (SI) request process, especially in cells that support multiple uplink carriers, and the prior art is difficult to effectively process the SI request process, resulting in inefficiency.
By implementing the configuration and request of the random access process between the terminal and the base station, using the SI request configuration in the Supplementary Uplink (SUL) and Normal Uplink (NUL), selecting the appropriate carrier for SI requests to ensure SI requests effective transmission. The specific method includes when the terminal and the base station receive the system information block (SIB 1), select a suitable carrier according to the configuration standard for SI request transmission, and use PRACH preamble and PRACH resources for a random access process in the SI request configuration.
It effectively enhances the SI request process in the next generation of wireless communication systems, improves the efficiency and reliability of SI requests, and is suitable for cell environments that support multiple uplink carriers.
Smart Images

Figure CN113170380B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a wireless communication system. More particularly, the present disclosure relates to an apparatus, method and system for system information (SI) request in a cell supporting multiple uplink carriers in a wireless communication system. Background Art
[0002] In order to meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems."
[0003] Typically, 5G communication systems are implemented in higher frequency (millimeter wave, mmWave) bands, such as the 60GHz band, to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are proposed in 5G communication systems. In addition, in 5G communication systems, development of system network improvements is underway based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, collaborative multi-point (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) have been developed, as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.
[0004] The Internet is a human-centered interconnected network in which humans generate and consume information, and is now developing towards the Internet of Things (IoT), in which distributed entities (such as devices) exchange and process information without human intervention. The Internet of Things (IoE) is a technology that combines IoT technology and big data processing technology by connecting cloud servers. Since IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", further research has been conducted on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). Such an IoT environment can provide intelligent Internet technology services to create new value for human life by collecting and analyzing data generated between connected objects. IoT can be applied to smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, advanced medical services and other fields through the integration and integration of existing information technology (IT) with various industries.
[0005] In view of this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.
[0006] Recently, in the next generation wireless communication system, there is a need to enhance a system information (SI) request procedure. Summary of the invention
[0007] Technical issues
[0008] There is a need to develop a SI request procedure in next generation wireless communication systems.
[0009] Technical Solution
[0010] Various aspects of the present invention can at least solve the above problems and / or disadvantages and provide at least the advantages described below. Therefore, one aspect of the present invention is to provide a communication method and system for integrating a 5th generation (5G) communication system to support a higher data rate beyond the 4th generation (4G) communication system.
[0011] According to one aspect of the present invention, a method performed by a terminal is provided, comprising: if it is determined that a system information block 1 (SIB 1) received from a base station includes a first system information (SI) request configuration for a supplementary uplink (SUL) and meets a first criterion for selecting the SUL, sending a preamble of a random access procedure to the base station on the SUL to request SI based on the first SI request configuration of the SUL; and if it is determined that SIB 1 includes a second SI request configuration for a normal uplink (NUL) and meets a second criterion for selecting the NUL, sending a preamble of a random access procedure to the base station on the NUL to request SI based on the second SI request configuration for the NUL.
[0012] According to one aspect of the present invention, a method performed by a base station is provided, comprising: based on the terminal determining that a system information block 1 (SIB 1) sent to the terminal includes a first system information (SI) request configuration for a supplementary uplink (SUL) and meets a first criterion for selecting the SUL, receiving a preamble of a random access procedure from the terminal on the SUL to request SI based on the first SI request configuration of the SUL; and if it is determined that SIB 1 includes a second SI request configuration for a normal uplink (NUL) and meets a second criterion for selecting the NUL, receiving a preamble of a random access procedure from the terminal on the NUL to request SI based on the second SI request configuration for the NUL.
[0013] According to one aspect of the present invention, a terminal is provided, comprising: a transceiver configured to send and receive signals; and a controller configured to: if it is determined that a system information block 1 (SIB 1) received from a base station includes a first system information (SI) request configuration for a supplementary uplink (SUL) and meets a first criterion for selecting the SUL, send a preamble of a random access procedure to the base station on the SUL to request SI based on the first SI request configuration of the SUL; and if it is determined that SIB 1 includes a second SI request configuration for a normal uplink (NUL) and meets a second criterion for selecting the NUL, send a preamble of a random access procedure to the base station on the NUL to request SI based on the second SI request configuration for the NUL.
[0014] According to another aspect of the present invention, a base station is provided, comprising: a transceiver configured to send and receive signals; and a controller configured to: if it is determined that a system information block 1 (SIB 1) sent to a terminal includes a first system information (SI) request configuration for a supplementary uplink (SUL) and satisfies a first criterion for selecting the SUL, receive a preamble of a random access procedure from the terminal on the SUL to request SI based on the first SI request configuration of the SUL; and if it is determined that SIB 1 includes a second SI request configuration for a normal uplink (NUL) and satisfies a second criterion for selecting the NUL, receive a preamble of a random access procedure from the terminal on the NUL to request SI based on the second SI request configuration for the NUL.
[0015] Beneficial Effects
[0016] According to various embodiments of the present invention, the SI request process in the next generation wireless communication system can be effectively enhanced. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The above and other aspects, features and advantages of certain embodiments of the present invention will become more apparent through the following description in conjunction with the accompanying drawings, in which:
[0018] Figure 1 A flowchart showing a method for SI request transmission process of a terminal and a base station according to an embodiment of the present invention;
[0019] Figure 2 A flowchart showing a method for SI request transmission process of a terminal and a base station according to an embodiment of the present invention;
[0020] Figure 3 A flowchart showing a method for SI request transmission process of a terminal and a base station according to an embodiment of the present invention is shown;
[0021] Figure 4 A flowchart showing a method for SI request transmission process of a terminal and a base station according to an embodiment of the present invention;
[0022] Figure 5 A flowchart showing a method for SI request transmission process of a terminal and a base station according to an embodiment of the present invention;
[0023] Figure 6 The beam failure recovery process of a terminal and a base station according to an embodiment of the present invention is shown;
[0024] Figure 7 A flowchart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention;
[0025] Figure 8 A flowchart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention;
[0026] Fig. 9 A flowchart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention;
[0027] Fig.10 A flowchart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention;
[0028] Fig.11 A flowchart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention;
[0029] Fig.12 is a block diagram of a terminal according to an embodiment of the present invention; and
[0030] Fig.13 is a block diagram of a base station according to an embodiment of the present invention.
[0031] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION
[0032] The following description is provided with reference to the accompanying drawings to assist in a comprehensive understanding of the various embodiments of the present invention as defined by the claims and their equivalents. The description includes various specific details to assist in understanding, but the embodiments are to be considered as exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present invention. In addition, descriptions of known functions and configurations may be omitted for clarity and brevity.
[0033] The terms and words used in the following specification and claims are not limited to the bibliographic meanings, but are selected only to enable a clear and consistent understanding of the present invention. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present invention is provided only for illustration, and not for limiting the present invention defined by the attached claims and their equivalents.
[0034] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
[0035] The term "substantially" means that the recited characteristic, parameter or value need not be achieved precisely, but deviations or changes, including, for example, tolerances, measurement errors, measurement precision limitations and other factors known to those skilled in the art, may occur in amounts that do not negate the effect that the characteristic is intended to provide.
[0036] Those skilled in the art will appreciate that the blocks of a flowchart (or sequence diagram) and the combination of the flowchart can be represented and executed by computer program instructions. These computer program instructions can be loaded from a memory and executed by a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the loaded program instructions are executed by a processor, the program instructions provide the realization of the functions described in the execution flowchart. Because computer program instructions can be stored in a computer-readable memory that can be used in a special-purpose computer or a programmable data processing device, products that perform the functions described in the flowchart can also be used. Because computer program instructions can be loaded on a computer or a programmable data processing device, when executed as a process, a computer or other programmable processing device can perform the operations of the functions described in the flowchart.
[0037] The blocks of the flowchart may correspond to a module, segment or code containing one or more executable instructions that implement one or more logical functions, or may correspond to a portion thereof. In some cases, the functions described by the blocks may be performed in an order different from the order listed. For example, two blocks listed in order may be executed simultaneously or in reverse order.
[0038] In this description, the words "unit", "module", etc. may refer to software components or hardware components, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) capable of performing a function or operation. However, "unit", etc. are not limited to hardware or software. Units, etc. may be configured to reside in an addressable storage medium executed by one or more processors. Units, etc. may refer to software components, object-oriented software components, class components, task components, processes, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by components and units may be combinations of smaller components and units, and may be combined with other components and units to form larger components and units. Components and units may be configured to drive devices or one or more processors in a secure multimedia card.
[0039] Before the detailed description, terms or definitions that are helpful for understanding the present invention are described. However, these terms should be interpreted in a non-limiting manner.
[0040] A “base station (BS)” is an entity that communicates with a user equipment (UE) and may be referred to as a BS, base transceiver station (BTS), Node B (NB), evolved NB (eNB), access point (AP), 5G NB (5GNB), or gNB.
[0041] A “UE” is an entity communicating with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.
[0042] In recent years, several broadband wireless technologies have been developed to meet the growing broadband user base and to provide more and improved applications and services. The 2nd generation (2G) wireless communication systems have been developed to provide voice services while ensuring user mobility. The 3rd generation (3G) wireless communication systems support both voice services and data services. In recent years, 4G wireless communication systems have been developed to provide high-speed data services. However, the current 4G wireless communication systems lack the resources to meet the further growing demand for high-speed data services. Therefore, the 5th generation (5G) wireless communication systems are being developed to meet the growing demand for high-speed data services and support ultra-reliability and low-latency applications.
[0043] The 5th generation wireless communication system will be implemented not only in lower frequency bands but also in higher frequency (mmWave) bands (e.g., 10 GHz to 100 GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, massive antennas, etc. are considered in the design of the 5th generation wireless communication system. In addition, the 5th generation wireless communication system is expected to handle different use cases with completely different requirements in terms of data rate, latency, reliability, mobility, etc. However, the design of the air interface of the 5th generation wireless communication system is expected to be flexible enough to serve various UEs with completely different capabilities according to the use cases and market segments of the end customers. For example, the use cases of the 5th generation wireless communication system are expected to address enhanced mobile broadband (eMBB), massive machine type communication (m-MTC), ultra-reliable low latency communication (URLLC), etc. The eMBB requirements, such as data rates of tens of Gbps, low latency, high mobility, etc., are targeted at the market segments representing traditional wireless broadband users who need Internet connectivity anytime and anywhere. m-MTC requirements, such as very high connection density, infrequent data transfer, very long battery life, low mobility addresses, etc., target the market segments representing the Internet of Things (IoT) / Internet of Everything (IoE) that envision connectivity of billions of devices. URLLC requirements, such as extremely low latency, very high reliability, and variable mobility, target the market segments representing industrial automation applications that foresee vehicle-to-vehicle / vehicle-to-infrastructure communications as one of the necessary prerequisites for autonomous vehicles.
[0044] In the 4th generation wireless communication system, the enhanced Node B (eNB) or base station in the cell broadcasts system information. The system information is structured into a set of master information blocks (MIBs) and system information blocks (SIBs). The MIB includes the system frame number (SFN), downlink system bandwidth, and physical hybrid ARQ feedback indicator channel (PHICH) configuration. The MIB is sent every 40ms. The transmission of the MIB can be repeated every 10ms, and the first transmission may occur in subframe #0 when SFM mod 4 is equal to 0. The MIB is sent on the physical broadcast channel. System information block type 1 carries the cell identity, tracking area number, cell restriction information, value tag (common to all scheduling units), and scheduling information of other SIBs. When SFN mod 8 is equal to 0, SIB 1 is sent every 80ms in subframe #5. When SFNmod 2 is equal to 0, SIB 1 is repeated in subframe #5. SIB 1 is sent on the physical downlink shared channel. Other SIBs (SIB 2 to SIB 19) are sent in system information (SI) messages, with scheduling information for these SIBs indicated in SIB 1.
[0045] The UE acquires system information after cell selection, cell reselection, handover completion, entering E-UTRA from another radio access technology (RAT), re-entering the service area, receiving a notification (paging), and after exceeding the maximum validity duration (e.g., 3 hours). In the radio resource control (RRC) idle and inactive state, the UE needs to acquire MIB, SIB1, SIB 2 to SIB 5, SIB 6 to SIB 8 (depending on the supported RAT), SIB 17 (if LTE and wireless LAN interworking (LTE-WLAN IWK) are supported) and SIB 18 to SIB 19 (if device-to-device (D2D) is supported). In the RRC connected state, the UE needs to acquire MIB, SIB 1, SIB 2, SIB 8 (depending on the supported RAT), SIB 17 (if LTE-WLAN IWK is supported) and SIB 18 to SIB 19 (if D2D is supported).
[0046] In the 5th generation wireless communication system (also known as Next Generation Radio or New Radio (NR)), system information (SI) is divided into a MIB and a plurality of SIBs, where:
[0047] -SI can be divided into MIB and multiple SIBs. In this configuration, MIB is always transmitted on the broadcast channel (BCH) with a periodicity of 80ms and repetition within 80ms, and includes the parameters required to obtain SIB 1 from the cell.
[0048] -SI can be divided into MIB and multiple SIBs. In this configuration, SIB 1 is transmitted on the downlink shared channel (DL-SCH) with a periodicity of 160ms and variable transmission repetition. The default transmission repetition period of SIB 1 is 20ms, but the actual transmission repetition period depends on the network implementation. The scheduling information in SIB 1 includes the mapping between SIBs and SI messages, the periodicity of each SI message, and the SI window length. The scheduling information in SIB 1 includes an indicator for each SI message, which indicates whether the SI message of interest is being broadcast. If at least one SI message is not broadcast, SIB 1 may include random access resources (physical random access channel (PRACH) preamble (or multiple) and PRACH resource (or multiple)) for requesting the gNB to broadcast one or more SI messages.
[0049] -SIBs other than SIB 1 are carried in System Information (SI) messages, which are sent on DL-SCH. Only SIBs with the same periodicity can be mapped to the same SI message. Each SI message is sent within a time domain window that appears periodically (for all SI messages, it is called an SI window with 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, within an SI window, only the corresponding SI message is sent. Using the indication in SIB 1, any SIB except SIB 1 can be configured as cell-specific or area-specific. Cell-specific SIBs are only applicable to the cell where the SIB is provided, while area-specific SIBs are applicable to the area called the SI area, which consists of one or more cells and is identified by systemInformationAreaID.
[0050] - If the UE requires SI messages to operate in a cell and SI messages are not broadcast, the UE shall:
[0051] -If SIB 1 includes random access resources (PRACH preamble (or multiple) and PRACH resources (or multiple)) for requesting SI, the UE initiates a random access procedure using the PRACH preamble (or multiple) and PRACH resources (or multiple) corresponding to the SI message. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message. This SI request method is also called Msg1-based SI request.
[0052] -If SIB 1 does not include random access resources (PRACH preamble (or multiple) and PRACH resources (or multiple)) for requesting SI, the UE initiates the transmission of the RRCSystemInfoRequest message. This process will trigger a random access process, in which the UE sends Msg1 (i.e., random access preamble) and waits for a random access response. Based on the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for confirmation of the SI request (i.e., RRCSystemInfoRequest message). If confirmation of the SI request (i.e., RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message. This SI request method is also called an SI request based on Msg3.
[0053] In NR, multiple UL carriers (called normal uplink carrier (NUL) and supplementary uplink carrier (SUL)) can be supported in the serving cell. In case a supplementary uplink carrier is configured in addition to the normal uplink carrier in the serving cell, the following SI request configurations in SIB 1 are possible:
[0054] - Configuration 1: SI request random access resources (PRACH preamble (or multiple) and PRACH opportunity (or multiple)) are configured in the supplementary uplink carrier, but not in the normal uplink carrier;
[0055] - Configuration 2: SI request random access resources (PRACH preamble (or multiple) and PRACH opportunity (or multiple)) are configured in the normal uplink carrier, but not in the supplementary uplink carrier;
[0056] -Configuration 3: SI request random access resources (PRACH preamble (or multiple) and PRACH opportunity (or multiple)) are configured for both the supplementary uplink carrier and the normal uplink carrier; and -Configuration 4: SI request random access resources (PRACH preamble (or multiple) and PRACH opportunity (or multiple)) are not configured for both the supplementary uplink carrier and the normal uplink carrier.
[0057] The current design addresses configuration 2 and configuration 4, where the UE selects a Msg1-based SI request for configuration 2, and the UE selects a Msg3-based SI request for configuration 4. When SUL is configured, configuration 1 and configuration 3 also need to be addressed. When SUL is configured in addition to NUL in the serving cell, a method is needed to address the selection of Msg1-based SI request and Msg3-based SI request.
[0058] [Example 1-SI request transmission: SUL aspect]
[0059] [Example 1-1]
[0060] Figure 1 A flow chart showing a method for sending an SI request by a terminal and a base station according to an embodiment of the present invention.
[0061] according to Figure 1 In the embodiment, the UE operates as follows.
[0062] The UE obtains SIB 1 from the camped cell or serving cell. The UE checks the BroadcastStatus bit in SIB 1 to obtain the SI message that the UE needs to obtain.
[0063] If the SI message that the UE needs to obtain is not broadcast (i.e., BroadcastStatus is set to zero), the UE initiates the transmission of an SI request. The process of SI request transmission is as follows.
[0064] 1. The UE determines whether a supplementary uplink carrier (SUL) is configured in the resident or serving cell (110). If the obtained SIB 1 includes the common uplink configuration of the SUL, the UE determines that the SUL is configured in the serving cell. The common uplink configuration of the SUL is indicated by the supplementaryUplink field in the ServingCellConfigCommonSIB information element of SIB 1.
[0065] 2. If the SUL is configured in the resident or serving cell:
[0066] * The UE selects a UL carrier for SI request transmission (120) from the normal uplink carrier (NUL) and the SUL. The UE selects the NUL or the SUL as follows (130):
[0067] - If the reference signal received power (RSRP) derived from the measurement of the synchronization signal block (SSB) of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in broadcast signaling such as SIB 1), then the SUL is the selected UL carrier for the SI request.
[0068] - If the RSRP derived from the measurement of the SSB of the resident or serving cell >= rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in broadcast signaling such as SIB 1), then the NUL is the selected UL carrier for the SI request.
[0069] *If the gNB signals the SI request configuration for the selected UL carrier, the UE initiates transmission of the SI request based on the Msg1 based SI request on the selected UL carrier (140, 150, 160, 170). The SI request configuration for SUL is signaled by the gNB using si-RequestConfigSUL in SIB 1. If there is no IE si-RequestConfigSUL in SIB 1, the UE considers that the gNB has not signaled the SI request configuration for SUL. The SI request configuration for NUL is signaled by the gNB using IEsi-RequestConfig in SIB 1. If there is no IE si-RequestConfig in SIB 1, the UE considers that the gNB has not signaled the SI request configuration for NUL. In other words, the UE initiates the random access procedure using the PRACH preamble(s) and PRACH resource(s) in the SI request configuration for the selected UL carrier.
[0070] -UE sends Msg1 (i.e., random access preamble) and waits for confirmation of SI request. Random access resources (PRACH preamble and PRACH opportunity) indicated in SI request configuration of selected UL carrier are used for Msg1. Msg1 is sent on selected UL carrier. If confirmation of SI request is received, UE monitors SI window of the requested SI message in one or more SI periods of the SI message.
[0071] *If the gNB does not signal the SI request configuration for the selected UL carrier, the UE initiates the transmission of the SI request based on the Msg3-based SI request on the selected UL carrier. In other words, the UE initiates the transmission of the RRCSystemInfoRequest message (140, 145, 160, 165).
[0072] -UE sends Msg1 (i.e., random access preamble) and waits for random access response. Common random access resources (PRACH preamble and PRACH opportunity) of the selected UL carrier are used for Msg1. Msg1 is sent on the selected UL carrier. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for confirmation of the SI request (i.e., RRCSystemInfoRequest message). If confirmation of the SI request (i.e., RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message.
[0073] 3. Otherwise, if the SUL is not configured in the camping or serving cell (110):
[0074] *If the gNB signals the SI request configuration for NUL, the UE shall initiate the transmission of the SI request based on the SI request based on Msg1. In other words, the UE initiates the random access procedure using the PRACH preamble and PRACH resources in the SI request configuration of NUL (160, 170).
[0075] -UE sends Msg1 (i.e. random access preamble) and waits for confirmation of SI request. Random access resources (PRACH preamble and PRACH opportunity) indicated in SI request configuration of NUL are used for Msg1. Msg1 is sent on NUL. If confirmation of SI request is received, UE monitors SI window of the requested SI message in one or more SI periods of the SI message.
[0076] *If the gNB does not signal the SI request configuration for NUL, the UE initiates the transmission of the SI request according to the SI request based on Msg3. In other words, the UE initiates the transmission of the RRCSystemInfoRequest message (160, 165).
[0077] -UE sends Msg1 (i.e., random access preamble) and waits for random access response. The common random access resources (PRACH preamble and PRACH opportunity) of NUL are used for Msg1. Msg1 is sent on NUL. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for confirmation of the SI request (i.e., RRCSystemInfoRequest message). If confirmation of the SI request (i.e., RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message.
[0078] In one embodiment of the above method, the “RSRP derived from SSB measurements of the camped or serving cell” is determined as follows:
[0079] 1> If nrofSS-BlocksToAverage is not configured in the resident or serving cell; or
[0080] 1> If absThreshSS-BlocksConsolidation is not configured in the resident or serving cell; or
[0081] 1> If the SS-RSRP of the SSB with the highest SS-RSRP is lower than or equal to absThreshSS-BlocksConsolidation:
[0082] 2> RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0083] 1> Otherwise:
[0084] 2>RSRP is the linear power scaled average of the SS-RSRP of the SSB(s) above absThreshSS-BlocksConsolidation, where the total number of averaged SSBs should not exceed nrofSS-BlocksToAverage.
[0085] The parameters nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation may be signaled by the gNB (e.g., in broadcast signaling such as SIB).
[0086] In another embodiment of the above method, the RSRP derived from the SSB measurement of the camped or serving cell is determined as follows: The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0087] [Example 1-2]
[0088] Figure 2 A flowchart illustrating a method for SI request transmission process of a terminal and a base station according to another embodiment of the present disclosure.
[0089] according to Figure 2 In the embodiment, the UE operates as follows.
[0090] The UE obtains SIB 1 from the camping or serving cell. The UE checks the BroadcastStatus bit in SIB 1 to obtain the SI message that the UE needs to obtain.
[0091] If the SI message that the UE needs to obtain is not broadcast (ie, the BroadcastStatus bit is set to zero), the UE initiates the transmission of the SI request.
[0092] The process of SI request transmission is as follows.
[0093] 1. The UE determines whether a supplementary uplink carrier (SUL) is configured in the camping or serving cell (210). If the acquired SIB 1 includes a common uplink configuration for the SUL, the UE determines that the SUL is configured in the serving cell. The common uplink configuration of the SUL is indicated by the supplementaryUplink field in the ServingCellConfigCommonSIB information element of SIB 1.
[0094] 2. If the SUL is configured in the resident or serving cell, the UE selects a UL carrier for SI request transmission (220) from among the uplink carrier (NUL) and the SUL. The UE selects the NUL or the SUL as follows:
[0095] * If the RSRP derived from the SSB measurement of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then the SUL is the UL carrier for the SI request.
[0096] * If the RSRP derived from the SSB measurement of the resident or serving cell >= rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then the NUL is the UL carrier for the SI request.
[0097] 3. If the SUL is not configured in the resident or serving cell, the UE selects the NUL for SI request transmission (210, 225).
[0098] 4. The UE determines whether the SIB 1 obtained from the resident or serving cell includes an SI request configuration for the selected UL carrier (230).
[0099] 5. If there is no SI request configuration for the selected UL carrier:
[0100] * The UE initiates the transmission of an SI request on the selected UL carrier based on a Msg3-based SI request. In other words, the UE initiates the transmission of an RRCSystemInfoRequest message on the selected UL carrier (235).
[0101] - The UE sends Msg1 (i.e., a random access preamble) and waits for a random access response. The common random access resources (PRACH preambles and PRACH occasions) of the selected UL carrier are used for Msg1. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for an acknowledgement of the SI request (i.e., the RRCSystemInfoRequest message). If an acknowledgement of the SI request (i.e., the RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message.
[0102] 6. If there is an SI request configuration for the selected UL carrier,
[0103] *The UE initiates transmission of an SI request based on the SI request based on Msg1 on the selected UL carrier (240). In other words, the UE initiates a random access procedure using the PRACH preamble (or multiple) and PRACH resource (or multiple) in the SI request configuration of the selected UL carrier. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. The random access resources (PRACH preamble and PRACH opportunity) indicated in the SI request configuration of the selected UL carrier are used for Msg1. Msg1 is sent on the selected UL carrier. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the SI request message.
[0104] In one embodiment of the above method, the RSRP derived from the SSB measurement of the camped or serving cell is determined as follows:
[0105] 1> If nrofSS-BlocksToAverage is not configured in the resident or serving cell; or
[0106] 1> If absThreshSS-BlocksConsolidation is not configured in the resident or serving cell; or
[0107] 1> If the SS-RSRP of the SSB with the highest SS-RSRP is lower than or equal to absThreshSS-BlocksConsolidation:
[0108] 2> RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0109] 1> Otherwise:
[0110] 2>RSRP is the linear power scaled average of the SS-RSRP of the SSB(s) above absThreshSS-BlocksConsolidation, where the total number of averaged SSBs should not exceed nrofSS-BlocksToAverage.
[0111] The parameters nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation are signaled by the gNB (e.g., in a broadcast signal such as SIB).
[0112] In another embodiment, the RSRP derived from the SSB measurement of the camped or serving cell is determined as follows: The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0113] [Examples 1-3]
[0114] Figure 3 A flowchart showing a method for the SI request transmission process of a terminal and a base station according to an embodiment of the present invention.
[0115] According to Figure 3 the embodiment of, the UE operates as follows.
[0116] The UE obtains SIB 1 from the resident or serving cell. The UE can check the BroadcastStatus bit in SIB 1 to obtain the SI messages that the UE needs to obtain. The SI request configuration for SUL is signaled by the gNB using the IE si-RequestConfigSUL in SIB 1. If the IE si-RequestConfigSUL does not exist in SIB 1, the UE considers that the SI request configuration for SUL has not been signaled by the gNB. The SI request configuration for NUL is signaled by the gNB using the IE si-RequestConfig in SIB 1. If si-RequestConfig does not exist in SIB 1, the UE considers that the gNB has not signaled the SI request configuration for NUL.
[0117] If the SI messages that the UE needs to obtain are not broadcast (i.e., the BroadcastStatus bit is set to zero), the UE initiates the transmission of an SI request. The process of SI request transmission is as follows.
[0118] 1. If the SI request configuration for SUL is signaled by the gNB (310), and the criteria for selecting SUL are met (i.e., RSRP derived from the SSB measurement of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1) (320):
[0119] * The UE initiates the transmission of an SI request based on the Msg1-based SI request on SUL (330). In other words, the UE initiates a random access procedure using the PRACH preamble(s) and PRACH resource(s) in the SI request configuration for SUL. The UE sends Msg1 (i.e., the random access preamble) and waits for an acknowledgement of the SI request. The random access resources (PRACH preamble and PRACH occasion) indicated in the SI request configuration for SUL are used for Msg1. Msg1 is sent on SUL. If an acknowledgement of the SI request is received, the UE monitors the SI window of the SI message for one or more SI cycles in which the SI message is requested.
[0120] 2. Otherwise, if the gNB signals an SI request configuration (340) for the NUL and the criteria for selecting the NUL are met (i.e., if SUL is supported in the resident or serving cell and the RSRP derived from the SSB measurement of the resident or serving cell >= rsrp-ThresholdSSB-SUL, then the NUL is selected; or if SUL is not supported in the serving cell, then the NUL is selected):
[0121] * The UE initiates the transmission of an SI request (350) based on the Msg1-based SI request on the NUL. In other words, the UE uses the PRACH preamble(s) and PRACH resource(s) in the SI request configuration of the NUL to initiate a random access procedure. The UE sends Msg1 (i.e., the random access preamble) and waits for an acknowledgement of the SI request. The random access resources (PRACH preamble and PRACH occasion) indicated in the SI request configuration of the NUL are used for Msg1. Msg1 is sent on the NUL. If an acknowledgement of the SI request is received, the UE monitors the SI window for the SI message in one or more SI cycles of the requested SI message.
[0122] 3. Otherwise, the UE initiates the transmission of an SI request based on the Msg3-based SI request. In other words, the UE initiates the transmission of an RRCSystemInfoRequest message (345).
[0123] * The UE sends Msg1 (i.e., the random access preamble) and waits for a random access response. The common random access resources (PRACH preamble and PRACH occasion) are used for Msg1. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for an acknowledgement of the SI request (i.e., the RRCSystemInfoRequest message). If an acknowledgement of the SI request (i.e., the RRCSystemInfoRequest message) is received, the UE monitors the SI window for the SI message in one or more SI periods of the requested SI message.
[0124] * Note that if SUL is configured, the UE will select the UL carrier for Msg1 transmission in a manner similar to the way the UE selects for the Msg1-based SI request.
[0125] - If the RSRP derived from the SSB measurement of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then the SUL is the selected UL carrier.
[0126] -If RSRP derived from SSB measurement of the camped or serving cell>=rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then NUL is the selected UL carrier.
[0127] In one embodiment of the above method, the RSRP derived from the SSB measurement of the camped or serving cell is determined as follows:
[0128] 1> If nrofSS-BlocksToAverage is not configured in the resident or serving cell; or
[0129] 1> If absThreshSS-BlocksConsolidation is not configured in the resident or serving cell; or
[0130] 1> If the SS-RSRP of the SSB with the highest SS-RSRP is lower than or equal to absThreshSS-BlocksConsolidation:
[0131] 2> RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0132] 1> Otherwise:
[0133] 2>RSRP is the linear power scaled average of the SS-RSRP of the SSB(s) above absThreshSS-BlocksConsolidation, where the total number of averaged SSBs should not exceed nrofSS-BlocksToAverage.
[0134] The parameters nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation are signaled by the gNB (e.g., in a broadcast signal such as SIB).
[0135] In one embodiment of the above method, the RSRP derived from the SSB measurement of the camped or serving cell may be determined as follows: The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0136] [Examples 1-4]
[0137] Figure 4 A flow chart showing a method for sending an SI request by a terminal and a base station according to an embodiment of the present invention.
[0138] In this embodiment, if SUL is configured in the serving cell, then if an SI request configuration is configured for NUL, an SI request configuration is configured for SUL. According to Figure 4 the embodiment of
[0139] the UE operates as follows. The UE obtains SIB 1 from the resident or serving cell. The UE may check the BroadcastStatus bit in SIB 1 to obtain the SI messages that the UE needs to obtain.
[0140] If the SI messages that the UE needs to obtain are not broadcast (i.e., the BroadcastStatus bit is set to zero), the UE initiates the transmission of an SI request. The process of SI request transmission is as follows.
[0141] 1. The UE determines whether the SIB 1 obtained from the resident or serving cell includes an SI request configuration (410).
[0142] 2. If the SI request configuration is not included:
[0143] * The UE initiates the transmission of an SI request based on the Msg3-based SI request. In other words, the UE initiates the transmission of an RRCSystemInfoRequest message (415).
[0144] - The UE sends Msg1 (i.e., a random access preamble) and waits for a random access response. The public random access resource (PRACH preamble and PRACH occasion) is used for Msg1. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for an acknowledgement of the SI request (i.e., an RRCSystemInfoRequest message). If an acknowledgement of the SI request (i.e., an RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message.
[0145] - Note that if SUL is configured, the UE will select the UL carrier for Msg1 transmission in a manner similar to the manner in which the UE selects for a Msg1-based SI request.
[0146] ** If the RSRP derived from the SSB measurement of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then SUL is the selected UL carrier.
[0147] **If RSRP derived from the SSB measurement of the serving or resident cell >= rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then NUL is the selected UL carrier.
[0148] 3. If SI request configuration is included, the UE determines whether a supplementary uplink carrier (SUL) is configured in the serving or resident cell (420, 430). If the obtained SIB 1 includes the common uplink configuration of the SUL, the SUL is determined to be configured in the serving cell. The common uplink configuration of the SUL is indicated by the supplementaryUplink field in the ServingCellConfigCommonSIB information element of SIB 1. The SI request configuration of the SUL is signaled by the gNB using the IE si-RequestConfigSUL in SIB 1. If the IE si-RequestConfigSUL does not exist in SIB 1, the UE considers that the gNB has not signaled the SI request configuration of the SUL. The SI request configuration of NUL is signaled by the gNB using the IE si-RequestConfig in SIB 1. If the IE si-RequestConfig does not exist in SIB 1, the UE considers that the gNB has not signaled the SI request configuration for NUL.
[0149] *If the SUL is configured in the serving or resident area:
[0150] - The UE selects a UL carrier for SI request transmission in the uplink carrier (NUL) and the SUL (430).
[0151] **If RSRP derived from the SSB measurement of the serving or resident cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then the SUL is the selected UL carrier for the SI request.
[0152] **If RSRP derived from the SSB measurement of the serving or resident cell >= rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), then NUL is the selected UL carrier for the SI request.
[0153] -The UE initiates transmission of an SI request based on the SI request based on Msg1 on the selected UL carrier (440). In other words, the UE initiates a random access procedure using the PRACH preamble (or multiple) and PRACH resource (or multiple) in the SI request configuration of the selected UL carrier. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. The random access resources (PRACH preamble and PRACH opportunity) indicated in the SI request configuration are used for Msg1. Msg1 is sent on the selected UL carrier. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the SI request message.
[0154] * Otherwise, if SUL is not configured in the camping or serving cell: The UE initiates transmission of the SI request based on the Msg1 based SI request on NUL. In other words, the UE initiates the random access procedure using the PRACH preamble (or multiple) and PRACH resource (or multiple) in the SI request configuration of NUL.
[0155] -UE sends Msg1 (i.e., random access preamble) and waits for confirmation of SI request (450). Random access resources (PRACH preamble and PRACH opportunity) indicated in SI request configuration are used for Msg1. Msg1 is sent on NUL. If confirmation of SI request is received, UE monitors SI window of SI message in one or more SI periods of SI request message.
[0156] In one embodiment of the above method, the RSRP derived from the SSB measurement of the camped or serving cell is determined as follows:
[0157] 1> If nrofSS-BlocksToAverage is not configured in the resident or serving cell; or
[0158] 1> If absThreshSS-BlocksConsolidation is not configured in the resident or serving cell; or
[0159] 1> If the SS-RSRP of the SSB with the highest SS-RSRP is lower than or equal to absThreshSS-BlocksConsolidation:
[0160] 2> RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0161] 1> Otherwise:
[0162] 2>RSRP is the linear power scaled average of the SS-RSRP of the SSB(s) above absThreshSS-BlocksConsolidation, where the total number of averaged SSBs should not exceed nrofSS-BlocksToAverage.
[0163] The parameters nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation may be signaled by the gNB (e.g., in broadcast signaling such as SIB).
[0164] In another embodiment of the method, the RSRP derived from the SSB measurement of the camped or serving cell may be determined as follows: The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0165] [Examples 1-5]
[0166] Figure 5 A flowchart illustrating a method for SI request transmission process of a terminal and a base station according to another embodiment of the present disclosure.
[0167] In this embodiment, if SI request configuration is provided for both SUL and NUL, SUL takes precedence over NUL. Figure 5 In the embodiment, the UE operates as follows.
[0168] The UE obtains SIB 1 from the camping or serving cell. The UE can check the BroadcastStatus bit in SIB 1 to obtain the SI message that the UE needs to obtain.
[0169] If the SI message that the UE needs to obtain is not broadcast (ie, the BroadcastStatus bit is set to zero), the UE initiates the transmission of the SI request. The process of SI request transmission is as follows.
[0170] 1. If the SI request configuration of the SUL is included in the acquired SIB 1 (510):
[0171] *The UE initiates transmission of an SI request based on the SI request based on Msg1 on the SUL (520). In other words, the UE initiates a random access procedure using the PRACH preamble (or multiple) and the PRACH resource (or multiple) in the SI request configuration of the SUL. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. The random access resources (PRACH preamble and PRACH opportunity) indicated in the SI request configuration of the SUL are used for Msg1. Msg1 is sent on the SUL. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the SI request message.
[0172] 2. Otherwise, if the SI request configuration of NUL is included in the acquired SIB 1 (530):
[0173] *The UE initiates transmission of an SI request based on the SI request based on Msg1 on NUL (540). In other words, the UE initiates a random access procedure using the PRACH preamble (or multiple) and PRACH resource (or multiple) in the SI request configuration of the NUL. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. The random access resources (PRACH preamble and PRACH opportunity) indicated in the SI request configuration of the NUL are used for Msg1. Msg1 is sent on NUL. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the SI request message.
[0174] 3. Otherwise, the UE initiates transmission of an SI request based on the SI request based on Msg3. In other words, the UE initiates transmission of an RRCSystemInfoRequest message (535).
[0175] *UE sends Msg1 (i.e., random access preamble) and waits for random access response. Common random access resources (PRACH preamble and PRACH opportunity) are used for Msg1. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for confirmation of the SI request (i.e., RRCSystemInfoRequest message). If confirmation of the SI request (i.e., RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message.
[0176] *Note that if SUL is configured, the UE will select the UL carrier for Msg1 transmission. If the RSRP derived from the SSB measurement of the resident or serving cell is < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), the UL carrier selected for the SI request is SUL. If the RSRP derived from the SSB measurement of the resident or serving cell is >= rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), the UL carrier selected for the SI request is NUL.
[0177] In an embodiment of the above method, the RSRP derived from the SSB measurement of the resident or serving cell is determined as follows:
[0178] 1> If nrofSS-BlocksToAverage is not configured in the resident or serving cell; or
[0179] 1> If absThreshSS-BlocksConsolidation is not configured in the resident or serving cell; or
[0180] 1> If the SS-RSRP of the SSB with the highest SS-RSRP is less than or equal to absThreshSS-BlocksConsolidation:
[0181] 2> The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0182] 1> Otherwise:
[0183] 2> The RSRP is the linear power scaled average of the SS-RSRP of the SSB(s) above absThreshSS-BlocksConsolidation, where the total number of averaged SSBs should not exceed nrofSS-BlocksToAverage..
[0184] The parameters nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation can be signaled by the gNB (e.g., in a broadcast signal such as SIB).
[0185] In another embodiment of the method, the RSRP derived from the SSB measurement of the resident or serving cell is determined as follows: The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0186]
Embodiment 1-6
[0187] According to the embodiment, the UE operates as follows.
[0188] The UE obtains SIB 1 from the resident or serving cell. The UE may check the BroadcastStatus bit in SIB 1 to obtain the SI messages that the UE needs to acquire.
[0189] If the SI messages that the UE needs to acquire are not broadcast (i.e., the BroadcastStatus bit is set to zero), the UE initiates the transmission of an SI request. The process of SI request transmission is as follows.
[0190] 1. If the SI request configuration for SUL is included in the acquired SIB 1, and the SI request configuration for NUL is not included in the acquired SIB 1:
[0191] * The UE initiates the transmission of an SI request on SUL based on the Msg1-based SI request. In other words, the UE uses the PRACH preamble(s) and PRACH resource(s) in the SI request configuration for SUL to initiate a random access procedure. The UE sends Msg1 (i.e., the random access preamble) and waits for an acknowledgement of the SI request. The random access resources (PRACH preamble and PRACH occasion) indicated in the SI request configuration for SUL are used for Msg1. Msg1 is sent on SUL. If an acknowledgement of the SI request is received, the UE monitors the SI window of the SI message in one or more SI cycles for which the SI message is requested.
[0192] 2. Otherwise, if the SI request configuration for SUL is included in the acquired SIB 1, and the SI request configuration for NUL is included in the acquired SIB 1:
[0193] * If the RSRP derived from the SSB measurement of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1):
[0194] -The UE initiates transmission of an SI request on the SUL based on the SI request based on Msg1. In other words, the UE initiates a random access procedure using the PRACH preamble (or multiple) and PRACH resource (or multiple) in the SI request configuration of the SUL. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. The random access resources (PRACH preamble and PRACH opportunity) indicated in the SI request configuration of the SUL are used for Msg1. Msg1 is sent on the SUL. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the SI request message.
[0195] *otherwise,
[0196] The UE initiates transmission of an SI request based on the SI request based on Msg1 on NUL. In other words, the UE initiates a random access procedure using the PRACH preamble (or multiple) and PRACH resource (or multiple) in the SI request configuration of the NUL. The UE sends Msg1 (i.e., random access preamble) and waits for confirmation of the SI request. The random access resources (PRACH preamble and PRACH opportunity) indicated in the SI request configuration of the NUL are used for Msg1. Msg1 is sent on NUL. If confirmation of the SI request is received, the UE monitors the SI window of the SI message in one or more SI periods of the SI request message.
[0197] 3. Otherwise, the UE initiates the transmission of the SI request based on the SI request based on Msg3. In other words, the UE initiates the transmission of the RRCSystemInfoRequest message.
[0198] *UE sends Msg1 (i.e., random access preamble) and waits for random access response. Common random access resources (PRACH preamble and PRACH opportunity) are used for Msg1. In the UL grant received in the random access response, the UE sends an RRCSystemInfoRequest message and waits for confirmation of the SI request (i.e., RRCSystemInfoRequest message). If confirmation of the SI request (i.e., RRCSystemInfoRequest message) is received, the UE monitors the SI window of the SI message in one or more SI periods of the requested SI message.
[0199] *Note that if SUL is configured, the UE will select the UL carrier for Msg1 transmission. If the RSRP derived from the SSB measurement of the resident or serving cell < rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signal such as SIB 1), the UL carrier selected for the SI request is SUL. If the RSRP measured from the SSB of the resident or serving cell >= rsrp-ThresholdSSB-SUL, where rsrp-ThresholdSSB-SUL is signaled by the gNB (e.g., in a broadcast signaling such as SIB 1), the UL carrier selected for the SI request is NUL.
[0200] In an embodiment of the above method, the RSRP derived from the SSB measurement of the resident or serving cell is determined as follows:
[0201] 1> If nrofSS-BlocksToAverage is not configured in the resident or serving cell; or
[0202] 1> If absThreshSS-BlocksConsolidation is not configured in the resident or serving cell; or
[0203] 1> If the SS-RSRP of the SSB with the highest SS-RSRP is less than or equal to absThreshSS-BlocksConsolidation:
[0204] 2> The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0205] 1> Otherwise:
[0206] 2> The RSRP is the linear power-scaled average of the SS-RSRP of the SSB(s) above absThreshSS-BlocksConsolidation, where the total number of averaged SSBs should not exceed nrofSS-BlocksToAverage.
[0207] The parameters nrofSS-BlocksToAverage and absThreshSS-BlocksConsolidation can be signaled by the gNB (e.g., in a broadcast signaling such as SIB).
[0208] In another embodiment of the method, the RSRP derived from the SSB measurement of the resident or serving cell is determined as follows: The RSRP is the SS-RSRP of the SSB with the highest SS-RSRP.
[0209] [Example 2-Beam Failure Recovery and C-DRX]
[0210] Figure 6 The beam failure recovery process of the terminal and the base station according to the embodiment of the present invention is shown.
[0211] Considering the current frequency distribution strategy, the bands where broadband communication of 1 GHz or higher can be performed may be limited, and the actual selectable frequency bands are only the millimeter wave bands of 28 GHz or higher. Compared with the signals transmitted at the 2 GHz or lower frequency bands used by the conventional cellular system, the signals transmitted at the higher frequency bands suffer from huge path loss and propagation loss. This significantly reduces the coverage of the base station using the same power as the conventional cellular system.
[0212] Beamforming technology is used to reduce propagation path loss and increase communication distance at higher frequency bands. Beamforming uses high-gain antennas to improve transmission and reception performance. Beamforming can be divided into transmit (TX) beamforming performed at the transmitting end and receive (RX) beamforming performed at the receiving end.
[0213] Typically, TX beamforming increases directivity by allowing the area reached by propagation to be densely located in a specific direction using multiple antennas. The use of TX beamforming results in an increase in the directivity of the signal, thereby increasing the propagation distance. In addition, since the signal is rarely sent in directions other than the directional direction, the signal interference acting on the other receiving end is significantly reduced. The receiving end can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the strength of the RX signal sent in a specific direction by allowing concentrated propagation in a specific direction, and excludes signals sent in directions other than the specific direction from the RX signal, thereby providing the effect of blocking interference signals. By using beamforming technology, the transmitter can make multiple transmit beam patterns in different directions. Each of these transmit beam patterns may also be referred to as a TX beam.
[0214] Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals in a cell, as each narrow TX beam provides coverage for a portion of the cell. The narrower the TX beam, the higher the antenna gain, and thus the greater the propagation distance of the signal transmitted using beamforming. The receiver can also make multiple RX beam patterns in different directions. Each of these receive patterns can also be referred to as an RX beam.
[0215] For data communication, the gNB shall transmit using TX beams (in multiple TX beams) from which the UE can receive signals. For beam failure detection, the gNB configures the UE with a beam failure detection reference signal and the UE declares a beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold within a configured period. When a beam failure is detected on the serving SSB / CSI-RS, the beam failure recovery request procedure is used to indicate a new SSB or CSI-RS to the serving gNB. Beam failure is detected by lower layers and indicated to the MAC entity. The beam failure recovery procedure for the UE is defined as follows.
[0216] 1> If a beam failure indication is received from the lower layer (i.e. the physical layer):
[0217] 2> Start or restart beamFailureRecoveryTimer;
[0218] 2>Increase BFI_COUNTER by 1;
[0219] 2> if BFI_COUNTER>= beamFailureInstanceMaxCount:
[0220] 3> If beamFailureRecoveryConfig is configured for the active UL BWP:
[0221] 4> If configured, start beamFailureRecoveryTimer;
[0222] 4> Start the random access procedure on SpCell by applying the parameters powerRampingStep, preambleReceivedTargetPower and preambleTransMax configured in beamFailureRecoveryConfig.
[0223] 3> Otherwise:
[0224] 4> Initiate a random access process on SpCell;
[0225] 1> if beamFailureRecoveryTimer expires; or
[0226] 1> If beamFailureDetectionTimer, beamFailureInstanceMaxCount or any reference signal used for beam failure detection is reconfigured by upper layers:
[0227] 2> Set BFI_COUNTER to 0;
[0228] 1> If the random access procedure initiated for beam failure recovery is completed successfully:
[0229] 3> Stop beamFailureRecoveryTimer if configured;
[0230] 3> Set BFI_COUNTER to 0;
[0231] 3> Consider the beam failure recovery request process to be completed successfully;
[0232] According to the current procedure, when a beam failure is detected (i.e. when BFI_COUNTER>=beamFailureInstanceMaxCount), the UE immediately initiates a random access procedure for beam failure recovery. In the RRC connected state, the UE can configure C-DRX. If DRX (discontinuous reception) is configured, the MAC entity monitors the PDCCH discontinuously using DRX operation. During the off duration of the DRX cycle (i.e. when the UE does not monitor the PDCCH), it can Figure 6 Multiple beam failure detections are shown. Performing a beam failure recovery procedure for each beam failure detection during inactive time may severely drain the UE's battery.
[0233] [Example 2-1]
[0234] Figure 7 A flow chart showing a method for beam failure recovery process of a terminal and a base station according to an embodiment of the present invention. Figure 7 In an embodiment, if C-DRX is configured and the UE detects a beam failure during the inactive time (710, 720), the following process is performed.
[0235] If the UE has configured at least one logical channel for the URLLC service (730):
[0236] -The UE performs beam failure recovery (BFR) (715) upon beam failure detection (BFD).
[0237] Others(730)
[0238] - In one embodiment, the UE delays BFR until the next active time (740). That is, the UE waits for the next active time to perform BFR instead of performing BFR immediately.
[0239] - In another embodiment, if contention-free random access resources are configured for BFR, the UE delays BFR until the next active time.
[0240] - In an alternative embodiment, if T>0, the UE delays BFR for a time "T", where T=T2-T1, T2=time until the next configured UL / DL grant from the time the beam failure is detected; T1=time required for the BFR process; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until the next on-duration.
[0241] - In an alternative embodiment, if T>0 and if contention-free random access resources are configured for BFR, the UE delays BFR by time "T"; where T=T2-T1, T2=time from detection of beam failure until next configured UL / DL grant; T1=time required for BFR process; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until next on-duration.
[0242] - In an alternative embodiment, if T>0, the UE delays BFR for a time "T", where T=T2-T1, T2=time until the next configured UL / DL grant from the time beam failure is detected; T1=predefined or signaled by the gNB; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until the next on-duration.
[0243] - In an alternative embodiment, if T>0 and if contention-free random access resources are configured for BFR, the UE delays BFR by time "T"; where T=T2-T1, T2=time from detection of beam failure until next configured UL / DL grant; T1=predefined or signaled by gNB; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until next on-duration.
[0244] In the above operation, the logical channel or radio bearer configured for the URLCC service may be determined as follows.
[0245] In one embodiment, a logical channel or radio bearer mapped to one or more Quality of Service (QoS) Flow Identifiers (QFI) in a QFI set is considered to be mapped to URLCC services. The QFI set may be predefined or signaled to the UE by the gNB. The QFI set may include one or more QFIs.
[0246] In another embodiment, a logical channel or radio bearer mapped to a specific subcarrier spacing (SCS) or an SCS in a SCS set is considered to be mapped to a URLCC service. The SCS set may be predefined or signaled to the UE by the gNB. The SCS set may include one or more SCSs.
[0247] In another embodiment, a logical channel or radio bearer mapped to an SCS greater than a specified SCS index is considered to be mapped to URLCC service. The specified SCS index may be predefined or signaled to the UE by the gNB.
[0248] In another embodiment, a logical channel or radio bearer mapped to a logical channel priority in a logical channel priority set is considered to be mapped to a URLCC service. The logical channel priority set may be predefined or signaled to the UE by the gNB. The logical channel priority set may include one or more logical channel priorities.
[0249] In another embodiment, a logical channel or radio bearer mapped to a logical channel priority greater than a specified logical channel priority is considered to be mapped to URLCC traffic. The specified logical channel priority may be predefined or signaled to the UE by the gNB.
[0250] In another embodiment, a logical channel or radio bearer mapped to a physical downlink shared channel (PDSCH) duration that is less than a specified PDSCH duration is considered to be mapped to URLCC traffic. The specified PDSCH duration may be predefined or signaled to the UE by the gNB.
[0251] In another embodiment, a logical channel or radio bearer mapped to a specified PDSCH duration is considered to be mapped to URLCC traffic. The specified PDSCH duration may be predefined or signaled to the UE by the gNB.
[0252] [Example 2-2]
[0253] Figure 8 A flow chart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention.
[0254] according to Figure 8 In an embodiment, if C-DRX is configured and the UE detects a beam failure during the inactive time (810, 820), the following operations are performed.
[0255] If drx-ShortCycleTimer is running (830),
[0256] - The UE performs BFR on the BFD (815).
[0257] Otherwise (830) - in one embodiment, the UE delays BFR until the next active time (840).
[0258] - In another embodiment, if contention-free random access resources are configured for BFR, the UE delays BFR until the next active time.
[0259] - In an alternative embodiment, if T>0, the UE delays BFR for a time "T", where T=T2-T1, T2=time until the next configured UL / DL grant from the time the beam failure is detected; T1=time required for the BFR process; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until the next on-duration.
[0260] - In an alternative embodiment, if T>0 and if contention-free random access resources are configured for BFR, the UE delays BFR by time "T"; where T=T2-T1, T2=time from detection of beam failure until next configured UL / DL grant; T1=time required for BFR process; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until next on-duration.
[0261] - In an alternative embodiment, if T>0, the UE delays BFR for a time "T", where T=T2-T1, T2=time until the next configured UL / DL grant from the time beam failure is detected; T1=predefined or signaled by the gNB; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until the next on-duration.
[0262] - In an alternative embodiment, if T>0 and if contention-free random access resources are configured for BFR, the UE delays BFR by time "T"; where T=T2-T1, T2=time from detection of beam failure until next configured UL / DL grant; T1=predefined or signaled by gNB; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until next on-duration.
[0263] Therefore, BFR can be delayed during the inactive time of a long DRX cycle.
[0264] [Example 2-3]
[0265] Fig. 9 A flow chart showing a method for a beam failure recovery process of a terminal and a base station according to an embodiment of the present invention.
[0266] according to Fig. 9 In an embodiment, if C-DRX is configured and the UE detects a beam failure during the inactive time (910, 920), the following operations are performed.
[0267] If the drx-ShortCycleTimer is running and / or if the UE has configured at least one logical channel for URLLC service (930, 940):
[0268] - The UE performs BFR on the BFD (915).
[0269] Others (930, 940)
[0270] - In one embodiment, the UE delays BFR until the next active time (950).
[0271] - In another embodiment, if contention-free random access resources are configured for BFR, the UE delays BFR until the next active time.
[0272] - In an alternative embodiment, if T>0, the UE delays BFR for a time "T", where T=T2-T1, T2=time until the next configured UL / DL grant from the time the beam failure is detected; T1=time required for the BFR process; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until the next on-duration.
[0273] - In an alternative embodiment, if T>0 and if contention-free random access resources are configured for BFR, the UE delays BFR by time "T"; where T=T2-T1, T2=time from detection of beam failure until next configured UL / DL grant; T1=time required for BFR process; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until next on-duration.
[0274] - In an alternative embodiment, if T>0, the UE delays BFR for a time "T", where T=T2-T1, T2=time until the next configured UL / DL grant from the time beam failure is detected; T1=predefined or signaled by the gNB; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until the next on-duration.
[0275] - In an alternative embodiment, if T>0 and if contention-free random access resources are configured for BFR, the UE delays BFR by time "T"; where T=T2-T1, T2=time from detection of beam failure until next configured UL / DL grant; T1=predefined or signaled by gNB; otherwise, the UE performs BFR for BFD. In one embodiment, T2 is the time until next on-duration.
[0276] In the above operation, the logical channel or radio bearer configured for the URLCC service may be determined as follows.
[0277] In one embodiment, a logical channel or radio bearer mapped to one or more QFIs of a QFI set is considered to be mapped to a URLCC service. The QFI set may be predefined or signaled to the UE by the gNB. The QFI set may include one or more QFIs.
[0278] In another embodiment, a logical channel or radio bearer of an SCS mapped to a specific SCS or SCS set is considered to be mapped to a URLCC service. The SCS set may be predefined or signaled to the UE by the gNB. The SCS set may include one or more SCSs.
[0279] In another embodiment, a logical channel or radio bearer mapped to an SCS greater than a specified SCS index is considered to be mapped to URLCC service. The specified SCS index may be predefined or signaled to the UE by the gNB.
[0280] In another embodiment, a logical channel or radio bearer mapped to a logical channel priority of a logical channel priority set is considered to be mapped to a URLCC service. The logical channel priority set may be predefined or signaled to the UE by the gNB. The set of logical channel priorities may include one or more logical channel priorities.
[0281] In another embodiment, a logical channel or radio bearer mapped to a logical channel priority greater than a specified logical channel priority is considered to be mapped to URLCC traffic. The specified logical channel priority may be predefined or signaled to the UE by the gNB.
[0282] In another embodiment, a logical channel or radio bearer mapped to a PDSCH duration that is less than a specified PDSCH duration is considered to be mapped to URLCC traffic. The specified PDSCH duration may be predefined or signaled to the UE by the gNB.
[0283] In another embodiment, a logical channel or radio bearer mapped to a specified PDSCH duration is considered to be mapped to URLCC traffic. The specified PDSCH duration may be predefined or signaled to the UE by the gNB.
[0284] [Example 2-4]
[0285] Fig.10 A flowchart showing a method of a beam failure recovery process of a terminal and a base station according to another embodiment of the present disclosure.
[0286] according to Fig.10 In an embodiment, if C-DRX is configured and the UE detects beam failure (1010, 1020) during inactive time, the following operations may be performed.
[0287] - The UE delays BFR for time "T" or until the next active time, whichever is earlier, if T>0, where T=T2-T1, T2=time until the next configured UL / DL grant from the time the beam failure was detected; T1=time required for the BFR process (1030, 1040);
[0288] *In one embodiment, T1 may be predefined or signaled by the gNB.
[0289] *In one embodiment, T2 is the time until the next on-duration.
[0290] - If T<0, the UE performs BFR for BFD (1030, 1015).
[0291] In one embodiment, the above process is applied only when the UE is in a long DRX cycle.
[0292] [Example 2-5]
[0293] Fig.11 A beam failure recovery process of a terminal and a base station according to another embodiment of the present disclosure is shown.
[0294] according to Fig.11 In an embodiment, it is suggested that if C-DRX is configured and the UE detects a beam failure during an inactive time (1110, 1120):
[0295] -If contention-free random access resources are configured for BFR, the UE delays BFR (1130, 1140);
[0296] - Otherwise, perform BFR on BFD (1130, 1115).
[0297] In one embodiment, the above process is applied only when the UE is in a long DRX cycle.
[0298] Fig.12 is a block diagram of a terminal according to an embodiment of the present invention.
[0299] Reference Fig.12 The terminal includes a transceiver 1210, a controller 1220, and a memory 1230. The controller 1220 may refer to a circuit, an application specific integrated circuit (ASIC), or at least one processor. The transceiver 1210, the controller 1220, and the memory 1230 are configured to implement Figures 1 to 11 1. Although the transceiver 1210, the controller 1220, and the memory 1230 are shown as separate entities, they may be implemented as a single entity, such as a single chip or a system on a chip (SoC). The transceiver 1210, the controller 1220, and the memory 1230 may be electrically connected or coupled to each other.
[0300] The transceiver 1210 may send signals to other network entities (eg, base stations or other UEs) and receive signals therefrom. The controller 1220 may control the UE to perform functions according to one or more of the above embodiments. The controller 1220 may refer to a circuit, an ASIC, or at least one processor.
[0301] In one embodiment, the operation of the terminal may be implemented using a memory 1230 storing corresponding program codes, software programs, firmware or other computer executable instructions. Specifically, the terminal may be equipped with a memory 1230 to store the information affecting the operation of the terminal. Figures 1 to 11 To perform these operations, the controller 1220 may read, load, and execute program codes stored in the memory 1230, for example, by using a processor or a central processing unit (CPU).
[0302] Fig.13 is a block diagram of a base station according to an embodiment of the present invention.
[0303] Reference Fig.13 , the base station includes a transceiver 1310, a controller 1320 and a memory 1330. The transceiver 1310, the controller 1320 and the memory 1330 are configured to implement FIG. Figures 1 to 11 ) or as described above. Although transceiver 1310, controller 1320, and memory 1330 are shown as separate entities, they may be implemented as a single entity, such as a single chip or system on chip (SoC). Transceiver 1310, controller 1320, and memory 1330 may be electrically connected or coupled to each other.
[0304] The transceiver 1310 may send signals to other network entities (eg, terminals or other base stations) and receive signals therefrom. The controller 1320 may control the base station to perform functions according to one of the above embodiments. The controller 1320 may refer to a circuit, an ASIC, or at least one processor.
[0305] In one embodiment, the operation of the base station can be implemented using a memory 1330 storing corresponding program codes, software programs, firmware or other computer executable instructions. Specifically, the base station can be equipped with a memory 1330 to store program codes that implement the desired operation. In order to perform the desired operation, the controller 1320 can read, load and execute the program code stored in the memory 1330 by using a processor or CPU.
[0306] While the invention has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the invention as defined by the appended claims and their equivalents.
[0307] As described above, the embodiments disclosed in the specification and the drawings are only used to present specific examples to easily explain the content of the present disclosure and help understanding, but are not intended to limit the scope of the present disclosure. Therefore, in addition to the embodiments disclosed herein, the scope of the present disclosure should also be analyzed to include all changes or modifications based on the technical concept of the present disclosure.
Claims
1. A method performed by a terminal in a wireless communication system, the method include: receiving a system information block 1 SIB1 from a base station, the SIB1 comprising a reference signal received power RSRP threshold associated with a supplementary uplink SUL carrier; Identify the RSRP of the serving cell for the random access procedure; If no SUL carrier is configured or the RSRP of the serving cell is greater than or equal to the RSRP threshold, a normal uplink NUL carrier is selected; If the SUL carrier is configured and the RSRP of the serving cell is less than the RSRP threshold, the SUL carrier is selected; In case S1B1 includes a system information request configuration of a SUL carrier and a SUL carrier is selected: initiating a random access procedure on the SUL carrier; and Based on the system information request configuration of the SUL carrier, a physical random access channel PRACH for system information request is sent to the base station on the SUL carrier; In case S1B1 includes a system information request configuration of a NUL carrier and a NUL carrier is selected: Initiate a random access procedure on the NUL carrier; and Based on the system information request configuration of the NUL carrier, a PRACH for the system information request is sent to the base station on the NUL carrier; In case S1B1 does not include a system information request configuration for a SUL carrier and a SUL carrier is selected: Sending a radio resource control RRC system information request message for system information request to the base station on the SUL carrier; In case S1B1 does not include a system information request configuration for a NUL carrier and a NUL carrier is selected: Sending an RRC system information request message for system information request to the base station on the NUL carrier; receiving an acknowledgement of the system information request from the base station; and Based on the confirmation, the message for the requested system information is obtained from the base station by monitoring a system information window for the message for the requested system information.
2. The method according to claim 1, in, The system information request configuration of the SUL carrier includes information about the PRACH preamble of the SUL carrier and information about the PRACH resources of the SUL carrier. The system information request configuration of the NUL carrier includes information about the PRACH preamble code of the NUL carrier and information about the PRACH resource of the NUL carrier. wherein, based on the PRACH preamble of the SUL carrier and the PRACH resources of the SUL carrier, the PRACH is sent on the SUL carrier, and Wherein, based on the PRACH preamble code of the NUL carrier and the PRACH resources of the NUL carrier, the PRACH is sent on the NUL carrier.
3. The method according to claim 1, in, The RSRP threshold is used for the synchronization signal block SSB of the serving cell.
4. The method according to claim 1, in, receiving the acknowledgement in a random access response in case a PRACH was sent for a system information request, and In which, when an RRC system information request message is sent for the system information request, the confirmation is received in message 4MSG4.
5. A method performed by a base station in a wireless communication system, the method include: Sending a system information block 1 SIB1 to the terminal, wherein the SIB1 includes a reference signal received power RSRP threshold associated with a supplementary uplink SUL carrier; receiving a physical random access channel PRACH for a system information request from a terminal on a SUL carrier in the following cases: (i) the SUL carrier is configured and the RSRP of the serving cell is less than an RSRP threshold, and (ii) S1B1 includes a system information request configuration of the SUL carrier, wherein the PRACH on the SUL carrier corresponds to a random access procedure initiated on the SUL carrier; receiving a PRACH for a system information request from a terminal on a normal uplink NUL carrier when: (i) no SUL carrier is configured or the RSRP of the serving cell is greater than or equal to an RSRP threshold, and (ii) S1B1 includes a system information request configuration for a NUL carrier, wherein the PRACH on the NUL carrier corresponds to a random access procedure initiated on the NUL carrier; receiving a radio resource control RRC system information request message for a system information request from the terminal on the SUL carrier in the following cases: (i) the RSRP of the serving cell is less than the RSRP threshold, and (ii) S1B1 does not include a system information request configuration of the SUL carrier; receiving an RRC system information request message for a system information request from the terminal on the NUL carrier in the following cases: (i) the SUL carrier is not configured or the RSRP of the serving cell is greater than or equal to the RSRP threshold and (ii) S1B1 does not include a system information request configuration of the NUL carrier; sending a confirmation of the system information request to the terminal; and The message for the requested system information is sent to the terminal based on a system information window of the message for the requested system information.
6. The method according to claim 5, in, The system information request configuration of the SUL carrier includes information about the PRACH preamble of the SUL carrier and information about the PRACH resources of the SUL carrier. The system information request configuration of the NUL carrier includes information about the PRACH preamble code of the NUL carrier and information about the PRACH resource of the NUL carrier. wherein, based on the PRACH preamble of the SUL carrier and the PRACH resources of the SUL carrier, the PRACH is sent on the SUL carrier, and Wherein, based on the PRACH preamble code of the NUL carrier and the PRACH resources of the NUL carrier, the PRACH is sent on the NUL carrier.
7. The method according to claim 5, in, The RSRP threshold is used for a synchronization signal block SSB of the serving cell, wherein, in the case where a PRACH is sent in response to a system information request, receiving the acknowledgement in a random access response, and In which, when an RRC system information request message is sent for the system information request, the confirmation is received in message 4MSG4.
8. A terminal in a wireless communication system, the terminal include: Transceiver; and A controller is coupled to the transceiver and is configured to: receiving a system information block 1 SIB1 from a base station, the SIB1 comprising a reference signal received power RSRP threshold associated with a supplementary uplink SUL carrier; Identify the RSRP of the serving cell for the random access procedure; If no SUL carrier is configured or the RSRP of the serving cell is greater than or equal to the RSRP threshold, a normal uplink NUL carrier is selected; If the SUL carrier is configured and the RSRP of the serving cell is less than the RSRP threshold, the SUL carrier is selected; In case S1B1 includes a system information request configuration of a SUL carrier and a SUL carrier is selected: initiating a random access procedure on the SUL carrier; and Based on the system information request configuration of the SUL carrier, a physical random access channel PRACH for system information request is sent to the base station on the SUL carrier; In case S1B1 includes a system information request configuration of a NUL carrier and a NUL carrier is selected: Initiate a random access procedure on the NUL carrier; and Based on the system information request configuration of the NUL carrier, a PRACH for the system information request is sent to the base station on the NUL carrier; In case S1B1 does not include a system information request configuration for a SUL carrier and a SUL carrier is selected: Sending a radio resource control RRC system information request message for system information request to the base station on the SUL carrier; In case S1B1 does not include a system information request configuration for a NUL carrier and a NUL carrier is selected: Sending an RRC system information request message for system information request to the base station on the NUL carrier; receiving an acknowledgement of the system information request from the base station; and Based on the confirmation, the message for the requested system information is obtained from the base station by monitoring a system information window for the message for the requested system information.
9. The terminal according to claim 8, in, The system information request configuration of the SUL carrier includes information about the PRACH preamble of the SUL carrier and information about the PRACH resources of the SUL carrier. The system information request configuration of the NUL carrier includes information about the PRACH preamble code of the NUL carrier and information about the PRACH resource of the NUL carrier. wherein, based on the PRACH preamble of the SUL carrier and the PRACH resources of the SUL carrier, the PRACH is sent on the SUL carrier, and Wherein, based on the PRACH preamble code of the NUL carrier and the PRACH resources of the NUL carrier, the PRACH is sent on the NUL carrier.
10. The terminal according to claim 8, in, The RSRP threshold is used for the synchronization signal block SSB of the serving cell.
11. The terminal according to claim 8, in, receiving the acknowledgement in a random access response in case a PRACH was sent for a system information request, and In which, when an RRC system information request message is sent for the system information request, the confirmation is received in message 4MSG4.
12. A base station in a wireless communication system, the base station include: Transceiver; and A controller is coupled with the transceiver and is configured to: Sending a system information block 1 SIB1 to the terminal, wherein the SIB1 includes a reference signal received power RSRP threshold associated with a supplementary uplink SUL carrier; receiving a physical random access channel PRACH for a system information request from a terminal on a SUL carrier in the following cases: (i) the SUL carrier is configured and the RSRP of the serving cell is less than an RSRP threshold, and (ii) S1B1 includes a system information request configuration of the SUL carrier, wherein the PRACH on the SUL carrier corresponds to a random access procedure initiated on the SUL carrier; receiving a PRACH for a system information request from a terminal on a normal uplink NUL carrier in the following cases: (i) no SUL carrier is configured or the RSRP of the serving cell is greater than or equal to an RSRP threshold, and (ii) S1B1 includes a system information request configuration for the NUL carrier, wherein the PRACH on the NUL carrier corresponds to a random access procedure initiated on the NUL carrier; receiving a radio resource control RRC system information request message for a system information request from the terminal on the SUL carrier in the following cases: (i) the RSRP of the serving cell is less than the RSRP threshold, and (ii) S1B1 does not include a system information request configuration of the SUL carrier; receiving an RRC system information request message for a system information request from the terminal on the NUL carrier in the following cases: (i) the SUL carrier is not configured or the RSRP of the serving cell is greater than or equal to the RSRP threshold and (ii) S1B1 does not include a system information request configuration of the NUL carrier; sending a confirmation of the system information request to the terminal; and The message for the requested system information is sent to the terminal based on a system information window of the message for the requested system information.
13. The base station according to claim 12, in, The system information request configuration of the SUL carrier includes information about the PRACH preamble of the SUL carrier and information about the PRACH resources of the SUL carrier. The system information request configuration of the NUL carrier includes information about the PRACH preamble code of the NUL carrier and information about the PRACH resource of the NUL carrier. wherein, based on the PRACH preamble of the SUL carrier and the PRACH resources of the SUL carrier, the PRACH is sent on the SUL carrier, and Wherein, based on the PRACH preamble code of the NUL carrier and the PRACH resources of the NUL carrier, the PRACH is sent on the NUL carrier.
14. The base station according to claim 12, in, The RSRP threshold is used for the synchronization signal block SSB of the serving cell.
15. The base station according to claim 12, in, receiving the acknowledgement in a random access response in case a PRACH was sent for a system information request, and In which, when an RRC system information request message is sent for the system information request, the confirmation is received in message 4MSG4.
