Method and apparatus for triggering of SIB1 request

Abstract

A method and apparatus for triggering of SIB1 request is provided. The method comprises: receiving, by a wireless device, a configuration related to a SIB1 request; determining, by the wireless device, whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; and transmitting, by the wireless device, a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

Description

METHOD AND APPARATUS FOR TRIGGERING OF SIB1 REQUEST

[0001] The present disclosure relates to a method and apparatus for triggering of SIB1 request.

[0002] 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

[0003] Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

[0004] The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible.

[0005] In cell re-selection procedure, UE is allowed to transmit a wake up signal (WUS) (for example, a SIB1 request) to request system information block type 1 (SIB1) transmission of a neighbor on-demand(OD)-SIB1 Cell, only if the OD-SIB1 Cell satisfies the cell reselection criteria to minimize the SIB1 transmission and the WUS transmission for network energy saving and UE power saving respectively.

[0006] However, when UE performs the cell selection, for example, for RRC connection re-establishment, it has no serving cell and the cell reselection criteria cannot be fulfilled. This means that the UE cannot trigger the WUS transmission based on the cell reselection criteria in this case. To enable UE to request SIB1 transmission for cell selection, a new triggering condition for WUS transmission should be defined, and the UE should select one triggering condition between them, for example, cell reselection criteria and the new triggering condition, based on the UE's condition, for example, whether the UE is performing cell selection or cell reselection.

[0007] Therefore, studies for triggering of SIB1 request are required.

[0008] In an aspect, a method is provided. The method comprises: receiving, by a wireless device, a configuration related to a system information block type 1 (SIB1) request; determining, by the wireless device, whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; and transmitting, by the wireless device, a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0009] In another aspect, an apparatus for implementing the above method is provided.

[0010] The present disclosure can have various advantageous effects.

[0011] According to some embodiments of the present disclosure, the wireless device could efficiently trigger transmission of a SIB1 request of an OD-SIB1 cell.

[0012] For example, a wireless device could avoid incorrect WUS transmission which could delay the SIB1 acquisition, by applying different WUS triggering condition depending on whether the wireless device camps on a suitable cell or not.

[0013] For example, the network could avoid unnecessary SIB1 transmission. Therefore, the network could save energy by allowing the wireless device to request SIB1 transmission based on the appropriate triggering condition which is suitable for the situation of the wireless device.

[0014] For example, the wireless device could efficiently transmit a SIB1 request by configuring a suitable triggering condition based on whether the wireless device is in cell selection situation or cell reselection situation.

[0015] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for triggering of SIB1 request for an OD-SIB1 cell.

[0016] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0017] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0018] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0019] FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

[0020] FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

[0021] FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

[0022] FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0023] FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0024] FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

[0025] FIG. 10 shows an example of System information acquisition.

[0026] FIG. 11 shows an example of RRC_IDLE and RRC_INACTIVE Cell Selection and Reselection.

[0027] FIG. 12 shows an example of a method for triggering of SIB1 request, according to some embodiments of the present disclosure.

[0028] FIG. 13 shows an example of a method for selection of SIB1 request condition.

[0029] FIG. 14 shows an example of a method for selection of SIB1 request condition.

[0030] FIG. 15 shows an example of a method for selection of SIB1 request condition.

[0031] FIG. 16 shows an example of a method for selection of SIB1 request condition.

[0032] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.

[0033] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

[0034] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

[0035] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0036] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

[0037] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".

[0038] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C".

[0039] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0040] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

[0041] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.

[0042] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0043] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0044] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

[0045] Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).

[0046] Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable method.

[0047] eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality. Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application program using data connection provided by a communication system. Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate. A streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet. These many application programs require connectivity of an always turned-on state in order to push real-time information and alarm for users. Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment. The cloud storage is a special use case which accelerates growth of uplink data transmission rate. 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience. Entertainment, for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane. Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.

[0048] In addition, one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.

[0049] URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable / available low-latency link such as a self-driving vehicle. A level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.

[0050] 5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fibre-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. A specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.

[0051] Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds. Another use case of an automotive field is an AR dashboard. The AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behaviour so that a driver may drive more safely drive, thereby lowering the danger of an accident. The next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify. Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.

[0052] A smart city and a smart home / building mentioned as a smart society will be embedded in a high-density wireless sensor network. A distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.

[0053] Consumption and distribution of energy including heat or gas is distributed at a higher level so that automated control of the distribution sensor network is demanded. The smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviours of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation. The smart grid may also be regarded as another sensor network having low latency.

[0054] Mission critical application (e.g., e-health) is one of 5G use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0055] Wireless and mobile communication gradually becomes important in the field of an industrial application. Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with constructible wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.

[0056] Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system. The use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.

[0057] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

[0058] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.

[0059] The wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR / VR / Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smart pad, a wearable device (e.g., a smartwatch or a smart glasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smart meter.

[0060] In the present disclosure, the wireless devices 100a to 100f may be called user equipment's (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

[0061] The UAV may be, for example, an aircraft availed by a wireless control signal without a human being onboard.

[0062] The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.

[0063] The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.

[0064] The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smart meters, vending machines, thermometers, smart bulbs, door locks, or various sensors.

[0065] The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.

[0066] The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

[0067] The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system.

[0068] The weather / environment device may include, for example, a device for monitoring or predicting a weather / environment.

[0069] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0070] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.

[0071] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (mMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.

[0072] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0073] Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 may transmit / receive radio signals to / from an external device through a variety of RATs (e.g., LTE and NR). In FIG. 2, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1.

[0074] The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and / or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and / or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information / signals through the transceiver(s) 106 and then store information obtained by processing the second information / signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and / or a receiver. The transceiver(s) 106 may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0075] The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and / or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and / or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information / signals through the transceiver(s) 106 and then store information obtained by processing the fourth information / signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and / or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0076] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.

[0077] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and / or a set of commands.

[0078] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0079] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0080] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0081] The one or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the transceivers 106 and 206 can up-convert OFDM baseband signals to a carrier frequency by their (analogy) oscillators and / or filters under the control of the processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analogy) oscillators and / or filters under the control of the transceivers 102 and 202.

[0082] In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be configured to perform the UE behaviour according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behaviour according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be configured to perform the BS behaviour according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behaviour according to an implementation of the present disclosure.

[0083] In the present disclosure, a BS is also referred to as a node B (NB), an eNodeB B (eNB), or a gNB.

[0084] FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

[0085] The wireless device may be implemented in various forms according to a use-case / service (refer to FIG. 1).

[0086] Referring to FIG. 3, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units / portions, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and / or the one or more memories 104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG. 2 and / or the one or more antennas 108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric / mechanical operation of each of the wireless devices 100 and 200 based on programs / code / commands / information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface or store, in the memory unit 130, information received through the wireless / wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

[0087] The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, input / output (I / O) unit (e.g., audio I / O port, video I / O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG. 1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate / environment device, the AI server / device (400 of FIG. 1), the BSs (200 of FIG. 1), a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example / service.

[0088] In FIG. 3, the entirety of the various elements, components, units / portions, and / or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit / portion, and / or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0089] FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

[0090] Referring to FIG. 4, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units / portions, and / or modules.

[0091] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, and at least one processing chip, such as a processing chip 101. The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may control the processor 102 to perform one or more protocols. For example, the software code 105 may control the processor 102 may perform one or more layers of the radio interface protocol.

[0092] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, and at least one processing chip, such as a processing chip 201. The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 may perform one or more layers of the radio interface protocol.

[0093] FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

[0094] Referring to FIG. 5, a UE 100 may correspond to the first wireless device 100 of FIG. 2 and / or the first wireless device 100 of FIG. 4.

[0095] A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 1112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.

[0096] The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by Qualcomm®, EXYNOSTMseries of processors made by Samsung®, A series of processors made by Apple®, HELIOTMseries of processors made by MediaTek®, ATOMTMseries of processors made by Intel®or a corresponding next generation processor.

[0097] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

[0098] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.

[0099] The power management module 110 manages power for the processor 102 and / or the transceiver 106. The battery 112 supplies power to the power management module 110.

[0100] The display 114 outputs results processed by the processor 102. The keypad 116 receives inputs to be used by the processor 102. The keypad 16 may be shown on the display 114.

[0101] The SIM card 118 is an　integrated circuit　that is intended to　securely store the　international mobile subscriber identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

[0102] The speaker 120 outputs sound-related results processed by the processor 102. The microphone 122 receives sound-related inputs to be used by the processor 102.

[0103] FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0104] In particular, FIG. 6 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 7 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 6, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 7, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a non-access stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an access stratum (AS).

[0105] In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network quality of service (QoS) flows.

[0106] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / de-multiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

[0107] Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0108] The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and / or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0109] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

[0110] In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.

[0111] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to / from NAS from / to UE.

[0112] FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0113] The frame structure shown in FIG. 8 is purely exemplary and the number of subframes, the number of slots, and / or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

[0114] Referring to FIG. 8, downlink and uplink transmissions are organized into frames. Each frame has Tf= 10ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing △f = 2u*15 kHz.

[0115] Table 1 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the normal CP, according to the subcarrier spacing △f = 2u*15 kHz.

[0116] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

[0117] Table 2 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing △f = 2u*15 kHz.

[0118] uNslotsymbNframe,uslotNsubframe,uslot212404

[0119] A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid ofNsize,ugrid,x*NRBscsubcarriers andNsubframe,usymbOFDM symbols is defined, starting at common resource block (CRB)Nstart,ugridindicated by higher-layer signaling (e.g., RRC signaling), whereNsize,ugrid,xis the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system,NRBscis 12 generally. There is one resource grid for a given antenna portp, subcarrier spacing configurationu, and transmission direction (DL or UL). The carrier bandwidthNsize,ugridfor subcarrier spacing configurationuis given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna portpand the subcarrier spacing configurationuis referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an indexkin the frequency domain and an indexlrepresenting a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

[0120] In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configurationu. The center of subcarrier 0 of CRB 0 for subcarrier spacing configurationucoincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 toNsizeBWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB= nCRB+NsizeBWP,i, whereNsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0121] The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 3 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter wave (mmW).

[0122] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0123] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 4 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

[0124] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0125] In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

[0126] In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment / re-establishment / handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment / handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA / DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

[0127] FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

[0128] Referring to FIG. 9, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted / received using radio resources through the PHY layer to / from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

[0129] In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to PDCCH. A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

[0130] Hereinafter, technical features related to Network Energy Saving (On-demand SSB) are described.

[0131] Network energy saving is of great importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. As 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring very high data rates (e.g. XR), networks are being denser, use more antennas, larger bandwidths and more frequency bands. The environmental impact of 5G needs to stay under control, and novel solutions to improve network energy savings need to be developed.

[0132] Energy consumption has become a key part of the operators' OPEX. According to the report from GSMA, the energy cost on mobile networks accounts for ~23% of the total operator cost. Most of the energy consumption comes from the radio access network and in particular from the Active Antenna Unit (AAU), with data centres and fibre transport accounting for a smaller share. The power consumption of a radio access can be split into two parts: the dynamic part which is only consumed when data transmission / reception is ongoing, and the static part which is consumed all the time to maintain the necessary operation of the radio access devices, even when the data transmission / reception is not on-going.

[0133] During the study in the SI phase, the network energy consumption model for the base station (BS) was defined including the reference configurations for FR1 TDD / FDD and FR2, the deep / light / micro sleep power states with corresponding relative power, transition time and energy consumption among different power states based on two types of BS categories, and the scaling rules for the active DL / UL power states considering BS power split by a static part of power and a dynamic part of power with the latter part reflecting the dynamic power consumption with respect to transmission / reception resource configurations in time, frequency, spatial and power domains. In addition, evaluation methodology and assumptions were achieved to study and evaluate the network energy saving gains for potential techniques with respect to other KPI including UPT, access delay, UE power consumption, etc.

[0134] Based on the agreed BS energy consumption model, and the evaluation methodology and assumptions, potential network energy saving techniques in various domains were evaluated with respect to the energy saving gains and the corresponding performance impact considering the above KPIs. The studied techniques are classified into time, frequency, spatial and power domains, and the technical descriptions as well as the legacy UE and specification impacts are summarized in the technical report. The techniques in time and frequency domains mainly aim to reduce the power consumption for dynamic part by trying to shutdown more symbols on one or more carriers to achieve BS micro sleep, and even the static power part by enlarging the interval between the contiguous active transmission / reception occasions to achieve BS light / deep sleep. The techniques in spatial and power domains mainly aim to reduce the power consumption of the TRX chains and PAs by trying to shutdown more spatial elements and / or reduce transmission power / power spectrum density, or increase the PA efficiency. Some of the studied techniques are beneficial for network energy savings.

[0135] The Rel-18 work item on network energy savings for NR led to the specification of some of the techniques that were found beneficial in the study, primarily for RRC Connected, user specific signals and channels, and low load scenarios. The techniques specified in Rel-18 include SSB-less SCell operation for inter-band CA for FR1 and co-located cells, enhancement on cell DTX / DRX mechanism including the alignment of cell DTX / DRX and UE DRX in RRC_CONNECTED mode, inter-node information exchange on cell DTX / DRX, techniques in spatial and power domains to enable efficient adaptation of spatial elements as well as efficient adaptation of power offset values between PDSCH and CSI-RS, as well as mechanisms to prevent legacy UEs camping on cells adopting the Rel-18 NES techniques, CHO procedure enhancement(s), and inter-node beam activation and enhancements on restricting paging in a limited area, and the corresponding RRM / RF core requirements.

[0136] Some other techniques also found to be beneficial in the study were not yet specified in Rel-18. This Rel-19 work item aims to specify further network energy savings targeting the beneficial techniques studied in Rel-18, but yet unspecified, including on-demand SSB and on-demand SIB1 transmissions, as well as adaptation of common signal / channel transmissions.

[0137] The objectives of the work item are the following:

[0138] 1. Specify procedures and signaling method(s) to support on-demand SSB SCell operation for UEs in connected mode configured with CA, for both intra- / inter-band CA. [RAN1 / 2 / 3 / 4]

[0139] Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Scell activation / deactivation signaling)

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

[0141] 2. Study procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]

[0142] Triggering method by uplink wake-up-signal using an existing signal / channel.

[0143] Wake-up-signal configuration provisioning to UE

[0144] Information exchange between gNBs at least for the configuration of wake-up signal, if necessary.

[0145] Specify adaptation of common signal / channel transmissions. [RAN1 / 2 / 3 / 4]

[0146] Adaptation of SSB in time domain, e.g. adapting periodicity

[0147] Adaptation of PRACH in time domain

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

[0149] Adaptation of paging occasions including confining the paging occasions in the time domain

[0150] 4. Specify the corresponding core requirements, for the above features [RAN4].

[0151] Hereinafter, technical features related to SIB1 acquisition are described. Sections of 3GPP TS 38.331 v17.6.0 may be referred.

[0152] System information

[0153] System Information (SI) is divided into theMIBand a number of SIBs and posSIBs where:

[0154] - theMIBis always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms and it includes parameters that are needed to acquireSIB1from the cell. The first transmission of theMIBis scheduled in subframes and repetitions are scheduled according to the period of SSB;

[0155] - If the period of SSB is larger than 80 ms, the MIB is transmitted with the same periodicity as that of SSB.

[0156] - theSIB1is transmitted on the DL-SCH with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms. The default transmission repetition periodicity ofSIB1is 20 ms but the actual transmission repetition periodicity is up to network implementation. For SSB and CORESET multiplexing pattern 1,SIB1repetition transmission period is 20 ms. For SSB and CORESET multiplexing pattern 2 / 3,SIB1transmission repetition period is the same as the SSB period.SIB1includes information regarding the availability and scheduling (e.g. mapping of SIBs to SI message, periodicity, SI-window size) of other SIBs with an indication whether one or more SIBs are only provided on-demand and, in that case, the configuration needed by the UE to perform the SI request.SIB1is cell-specific SIB;

[0157] - SIBs other thanSIB1and posSIBs are carried inSystemInformation(SI) messages, which are transmitted on the DL-SCH. Only SIBs or posSIBs having the same periodicity can be mapped to the same SI message. SIBs and posSIBs are mapped to different SI messages, i.e. an SI message contains either only SIBs or only posSIBs. Each SI message is transmitted within periodically occurring time domain windows (referred to as SI-windows with same length for all SI messages). Each SI message is associated with an SI-window and the SI-windows of different SI messages do not overlap. That is, within one SI-window only the corresponding SI message is transmitted. An SI message may be repeated with the same content a number of times within the SI-window. Any SIB or posSIB exceptSIB1can be configured to be cell specific or area specific, using an indication inSIB1. The cell specific SIB is applicable only within a cell that provides the SIB while the area specific SIB is applicable within an area referred to as SI area, which consists of one or several cells and is identified by systemInformationAreaID;

[0158] - The mapping of SIBs to SI messages is configured inschedulingInfoListandschedulingInfoList2, while the mapping of posSIBs to SI messages is configured inposSchedulingInfoListandschedulingInfoList2.

[0159] Each SIB and each posSIB is mapped to a single SI message. posSIBs of the sameposSibTypecarrying GNSS Generic Assistance Data for different GNSS / SBAS (identified bygnss-id / sbas-id) are mapped to different SI messages.

[0160] Each SIB and posSIB is contained at most once in an SI message.

[0161] For SIBs and posSIBs with segments, the segments contained in SI messages are transmitted according to the SI message periodicity, with one segment of a particularsibType / posSibTypein each SI message;

[0162] - For a UE in RRC_CONNECTED, the network can provide system information through dedicated signalling using theRRCReconfigurationmessage, e.g. if the UE has an active BWP with no common search space configured to monitor system information, paging, or upon request from the UE.

[0163] - For PSCell and SCells, the network provides the required SI by dedicated signalling, i.e. within anRRCReconfigurationmessage. Nevertheless, the UE shall acquireMIBof the PSCell to get SFN timing of the SCG (which may be different from MCG). Upon change of relevant SI for SCell, the network releases and adds the concerned SCell. For PSCell, the required SI can only be changed with Reconfiguration with Sync.

[0164] - The physical layer imposes a limit to the maximum size a SIB can take. The maximumSIB1orSImessagesize is 2976 bits.

[0165] System information acquisition

[0166] FIG. 10 shows an example of System information acquisition.

[0167] The UE applies the SI acquisition procedure to acquire the AS, NAS- and positioning assistance data information. The procedure applies to UEs in RRC_IDLE, in RRC_INACTIVE and in RRC_CONNECTED.

[0168] The UE in RRC_IDLE and RRC_INACTIVE shall ensure having a valid version of (at least) theMIB,SIB1throughSIB4,SIB5(if the UE supports E-UTRA),SIB11(if the UE is configured for idle / inactive measurements),SIB12(if UE is capable of NR sidelink communication / discovery and is configured by upper layers to receive or transmit NR sidelink communication / discovery), andSIB13,SIB14(if UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit V2X sidelink communication),SIB15(if UE is configured by upper layers to report disaster roaming related information),SIB16(if the UE is capable of slice-based cell reselection and the UE receives NSAG information for cell reselection from upper layer),SIB17(if the UE is using TRS resources for power saving in RRC_IDLE and RRC_INACTIVE) andSIB19(if UE is accessing NR via NTN access).

[0169] The UE capable of MBS broadcast which is receiving or interested to receive MBS broadcast service(s) via a broadcast MRB shall ensure having a valid version ofSIB20, regardless of the RRC state the UE is in.

[0170] The UE shall ensure having a valid version of the posSIB requested by upper layers.

[0171] SIB validity and need to (re)-acquire SIB

[0172] The UE shall apply the SI acquisition procedure upon cell selection (e.g. upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB.

[0173] When the UE acquires aMIBor aSIB1or an SI message in a serving cell, and if the UE stores the acquired SIB, then the UE shall store the associatedareaScope, if present, the firstPLMN-Identityin thePLMN-IdentityInfoListfor non-NPN-only cells or the first NPN identity (SNPN identity in case of SNPN, or PNI-NPN identity in case of PNI-NPN) in theNPN-IdentityInfoListfor NPN-only cells, thecellIdentity, thesystemInformationAreaID, if present, and thevalueTag, if present, as indicated in thesi-SchedulingInfofor the SIB. If the UE stores the acquired posSIB, then the UE shall store the associatedareaScope, if present, thecellIdentity, thesystemInformationAreaID, if present, thevalueTag, if provided inassistanceDataSIB-Element, and theexpirationTimeif provided inassistanceDataSIB-Element. The UE may use a valid stored version of the SI exceptMIB,SIB1,SIB6,SIB7orSIB8e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. ThevalueTagandexpirationTimefor posSIB is optionally provided inassistanceDataSIB-Element.

[0174] A L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform the interested SIB(s) to the connected L2 U2N Relay UE and receive the SIB(s) from the L2 U2N Relay UE. A L2 U2N Remote UE in RRC_CONNECTED receives SIB1 and other SIB(s) inRRCReconfigurationmessage and performs on-demand SI request if required. The L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED is not required to obtain SI over Uu interface, but it may decide to perform the SI acquisition procedure over Uu interface by UE implementation.

[0175] - The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation.

[0176] Acquisition of System Information

[0177] - Acquisition ofMIBandSIB1

[0178] The UE shall:

[0179] 1> apply the specified BCCH configuration;

[0180] 1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

[0181] 1> if the UE is in RRC_CONNECTED while T311 is running:

[0182] 2> acquire theMIB;

[0183] 2> if the UE is unable to acquire theMIB;

[0184] 3> perform the actions according to essential system information missing;

[0185] 2> else:

[0186] 3> perform the actions according to actions upon reception of theMIB.

[0187] 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceSIB1andpagingSearchSpaceand has received an indication about change of system information; or

[0188] 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceSIB1and the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s), and, UE has not acquired SIB1 in current modification period; or

[0189] 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceSIB1, and, the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s), and,si-BroadcastStatusfor the required SIB(s) orposSI-BroadcastStatusfor the required posSIB(s) is set tonotbroadcastingin acquiredSIB1in current modification period; or

[0190] 1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

[0191] 1> if the UE is in RRC_CONNECTED while T311 is running:

[0192] 2> ifssb-SubcarrierOffsetindicatesSIB1is transmitted in the cell and ifSIB1acquisition is required for the UE:

[0193] 3> acquire theSIB1;

[0194] 3> if the UE is unable to acquire theSIB1:

[0195] 4> perform the actions according to essential system information missing;

[0196] 3> else:

[0197] 4> upon acquiringSIB1, perform the actions according to actions upon reception of theSIB1.

[0198] 2> else ifSIB1acquisition is required for the UE andssb-SubcarrierOffsetindicates thatSIB1is not scheduled in the cell:

[0199] 3> perform the actions according to essential system information missing.

[0200] - The UE in RRC_CONNECTED is only required to acquire broadcastedSIB1and MBS broadcast if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e., the broadcast and unicast / MBS multicast beams are quasi co-located. The UE in RRC_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcastedSIB1andMIBif the UE can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.

[0201] - UE in RRC_INACTIVE that does not supportinactiveStateNTN-r17enters RRC_IDLE upon cell reselection between TN cell and NTN cell, and initiates the NAS signalling connection recovery.

[0202] Request for on demand system information

[0203] The UE shall, while SDT procedure is not ongoing:

[0204] 1> ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigSULand criteria to select supplementary uplink is met:

[0205] 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigSULcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0206] 2> if acknowledgement for SI request is received from lower layers:

[0207] 3> acquire the requested SI message(s), immediately;

[0208] 1> else if the UE is a RedCap UE and ifinitialUplinkBWP-RedCapis configured inUplinkConfigCommonSIBand ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigRedCapand criteria to select normal uplink is met:

[0209] 2> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigRedcapcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0210] 2> if acknowledgement for SI request is received from lower layers:

[0211] 3> acquire the requested SI message(s) immediately;

[0212] 1> else:

[0213] 2> if the UE is not a RedCap UE and ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigand criteria to select normal uplink is met; or

[0214] 2> if the UE is a RedCap UE and ifinitialUplinkBWP-RedCapis not configured inUplinkConfigCommonSIBand ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigand criteria to select normal uplink is met:

[0215] 3> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0216] 3> if acknowledgement for SI request is received from lower layers:

[0217] 4> acquire the requested SI message(s) immediately;

[0218] 2> else:

[0219] 3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided inSIB1;

[0220] 3> apply the default MAC Cell Group configuration;

[0221] 3> apply thetimeAlignmentTimerCommonincluded inSIB1;

[0222] 3> apply the CCCH configuration;

[0223] 3> initiate transmission of theRRCSystemInfoRequestmessage withrrcSystemInfoRequest;

[0224] 3> if acknowledgement forRRCSystemInfoRequestmessage withrrcSystemInfoRequestis received from lower layers:

[0225] 4> acquire the requested SI message(s) immediately;

[0226] 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers:

[0227] 2> reset MAC;

[0228] 2> if SI request is based onRRCSystemInfoRequestmessage withrrcSystemInfoRequest:

[0229] 3> release RLC entity for SRB0.

[0230] - After RACH failure for SI request it is up to UE implementation when to retry the SI request.

[0231] Actions related to transmission ofRRCSystemInfoRequestmessage

[0232] The UE shall set the contents ofRRCSystemInfoRequestmessage as follows:

[0233] 1> if the procedure is triggered to request the required SI message(s) other than positioning:

[0234] 2> set therequested-SI-Listto indicate the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0235] 1> else if the procedure is triggered to request the required SI message(s) for positioning:

[0236] 2> set therequestedPosSI-Listto indicate the SI message(s) that the UE upper layers require for positioning operations, and for whichposSI-BroadcastStatusis set tonotBroadcasting.

[0237] The UE shall submit theRRCSystemInfoRequestmessage to lower layers for transmission.

[0238] Acquisition of SIB(s) orposSIB(s) in RRC_CONNECTED

[0239] The UE shall:

[0240] 1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the fieldsearchSpaceOtherSystemInformationand the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s), or

[0241] 1> if the UE is in RRC_CONNECTED and acting as a L2 U2N Remote UE and the UE has not stored a valid version of a SIB, of one or several required SIB(s):

[0242] 2> for the SI message(s) that, according to thesi-SchedulingInfoorposSI-SchedulingInfoin the stored SIB1, contain at least one required SIB or requested posSIB:

[0243] 3> ifonDemandSIB-Requestis configured and timer T350 is not running:

[0244] 4> initiate transmission of theDedicatedSIBRequestmessage;

[0245] 4> start timer T350 with the timer value set to theonDemandSIB-RequestProhibitTimer;

[0246] 1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the fieldsearchSpaceOtherSystemInformationand the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s):

[0247] 2> for the SI message(s) that, according to thesi-SchedulingInfoin the stored SIB1, contain at least one required SIB and for whichsi-BroadcastStatusis set tobroadcasting:

[0248] 3> acquire the SI message(s);

[0249] 2> for the SI message(s) that, according to thesi-SchedulingInfoin the stored SIB1, contain at least one required SIB and for whichsi-BroadcastStatusis set tonotBroadcasting:

[0250] 3> ifonDemandSIB-Requestis configured and timer T350 is not running:

[0251] 4> initiate transmission of theDedicatedSIBRequestmessage;

[0252] 4> start timer T350 with the timer value set to theonDemandSIB-RequestProhibitTimer;

[0253] 4> acquire the requested SI message(s) corresponding to the requested SIB(s).

[0254] 2> for the SI message(s) that, according to theposSI-SchedulingInfoin the stored SIB1, contain at least one requested posSIB and for whichposSI-BroadcastStatusis set tobroadcasting:

[0255] 3> acquire the SI message(s);

[0256] 2> for the SI message(s) that, according to theposSI-SchedulingInfoin the stored SIB1, contain at least one requested posSIB and for whichposSI-BroadcastStatusis set tonotBroadcasting:

[0257] 3> ifonDemandSIB-Requestis configured and timer T350 is not running:

[0258] 4> initiate transmission of theDedicatedSIBRequestmessage;

[0259] 4> start timer T350 with the timer value set to theonDemandSIB-RequestProhibitTimer;

[0260] 4> acquire the requested SI message(s) corresponding to the requested posSIB(s).

[0261] - UE may include on demand request for SIB and / or posSIB(s) in the sameDedicatedSIBRequestmessage.

[0262] Actions related to transmission ofDedicatedSIBRequestmessage

[0263] The UE shall set the contents ofDedicatedSIBRequestmessage as follows:

[0264] 1> if the procedure is triggered to request the required SIB(s):

[0265] 2> includerequestedSIB-Listin theonDemandSIB-RequestListto indicate the requested SIB(s);

[0266] 1> if the procedure is triggered to request the required posSIB(s):

[0267] 2> includerequestedPosSIB-Listin theonDemandSIB-RequestListto indicate the requested posSIB(s).

[0268] The UE shall submit theDedicatedSIBRequestmessage to lower layers for transmission.

[0269] Actions upon receipt of System Information

[0270] Acquisition ofMIBandSIB1

[0271] The UE shall:

[0272] 1> apply the specified BCCH configuration;

[0273] 1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

[0274] 1> if the UE is in RRC_CONNECTED while T311 is running:

[0275] 2> acquire theMIB,which is scheduled;

[0276] 2> if the UE is unable to acquire theMIB;

[0277] 3> perform the actions according to essential system information missing;

[0278] 2> else:

[0279] 3> perform the actions according to actions upon reception of theMIB.

[0280] 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceSIB1andpagingSearchSpaceand has received an indication about change of system information; or

[0281] 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceSIB1and the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s), and, UE has not acquired SIB1 in current modification period; or

[0282] 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured bysearchSpaceSIB1, and, the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s), and,si-BroadcastStatusfor the required SIB(s) orposSI-BroadcastStatusfor the required posSIB(s) is set tonotbroadcastingin acquiredSIB1in current modification period; or

[0283] 1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

[0284] 1> if the UE is in RRC_CONNECTED while T311 is running:

[0285] 2> ifssb-SubcarrierOffsetindicatesSIB1is transmitted in the cell and ifSIB1acquisition is required for the UE:

[0286] 3> acquire theSIB1,which is scheduled;

[0287] 3> if the UE is unable to acquire theSIB1:

[0288] 4> perform the actions according to essential system information missing;

[0289] 3> else:

[0290] 4> upon acquiringSIB1, perform the actions according to actions upon reception of theSIB1.

[0291] 2> else ifSIB1acquisition is required for the UE andssb-SubcarrierOffsetindicates thatSIB1is not scheduled in the cell:

[0292] 3> perform the actions according to essential system information missing.

[0293] - The UE in RRC_CONNECTED is only required to acquire broadcastedSIB1and MBS broadcast if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e., the broadcast and unicast / MBS multicast beams are quasi co-located. The UE in RRC_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcastedSIB1andMIBif the UE can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.

[0294] - UE in RRC_INACTIVE that does not supportinactiveStateNTN-r17enters RRC_IDLE upon cell reselection between TN cell and NTN cell, and initiates the NAS signalling connection recovery.

[0295] Request for on demand system information

[0296] The UE shall, while SDT procedure is not ongoing:

[0297] 1> ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigSULand criteria to select supplementary uplink is met:

[0298] 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigSULcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0299] 2> if acknowledgement for SI request is received from lower layers:

[0300] 3> acquire the requested SI message(s) immediately;

[0301] 1> else if the UE is a RedCap UE and ifinitialUplinkBWP-RedCapis configured inUplinkConfigCommonSIBand ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigRedCapand criteria to select normal uplink is met:

[0302] 2> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigRedcapcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0303] 2> if acknowledgement for SI request is received from lower layers:

[0304] 3> acquire the requested SI message(s) immediately;

[0305] 1> else:

[0306] 2> if the UE is not a RedCap UE and ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigand criteria to select normal uplink is met; or

[0307] 2> if the UE is a RedCap UE and ifinitialUplinkBWP-RedCapis not configured inUplinkConfigCommonSIBand ifSIB1includessi-SchedulingInfocontainingsi-RequestConfigand criteria to select normal uplink is met:

[0308] 3> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) insi-RequestConfigcorresponding to the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0309] 3> if acknowledgement for SI request is received from lower layers:

[0310] 4> acquire the requested SI message(s) immediately;

[0311] 2> else:

[0312] 3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided inSIB1;

[0313] 3> apply the default MAC Cell Group configuration;

[0314] 3> apply thetimeAlignmentTimerCommonincluded inSIB1;

[0315] 3> apply the CCCH configuration;

[0316] 3> initiate transmission of theRRCSystemInfoRequestmessage withrrcSystemInfoRequest;

[0317] 3> if acknowledgement forRRCSystemInfoRequestmessage withrrcSystemInfoRequestis received from lower layers:

[0318] 4> acquire the requested SI message(s) as defined immediately;

[0319] 1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers:

[0320] 2> reset MAC;

[0321] 2> if SI request is based onRRCSystemInfoRequestmessage withrrcSystemInfoRequest:

[0322] 3> release RLC entity for SRB0.

[0323] - After RACH failure for SI request it is up to UE implementation when to retry the SI request.

[0324] Actions related to transmission ofRRCSystemInfoRequestmessage

[0325] The UE shall set the contents ofRRCSystemInfoRequestmessage as follows:

[0326] 1> if the procedure is triggered to request the required SI message(s) other than positioning:

[0327] 2> set therequested-SI-Listto indicate the SI message(s) that the UE requires to operate within the cell, and for whichsi-BroadcastStatusis set tonotBroadcasting;

[0328] 1> else if the procedure is triggered to request the required SI message(s) for positioning:

[0329] 2> set therequestedPosSI-Listto indicate the SI message(s) that the UE upper layers require for positioning operations, and for whichposSI-BroadcastStatusis set tonotBroadcasting.

[0330] The UE shall submit theRRCSystemInfoRequestmessage to lower layers for transmission.

[0331] Acquisition of SIB(s) orposSIB(s) in RRC_CONNECTED

[0332] The UE shall:

[0333] 1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the fieldsearchSpaceOtherSystemInformationand the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s), or

[0334] 1> if the UE is in RRC_CONNECTED and acting as a L2 U2N Remote UE and the UE has not stored a valid version of a SIB, of one or several required SIB(s):

[0335] 2> for the SI message(s) that, according to thesi-SchedulingInfoorposSI-SchedulingInfoin the stored SIB1, contain at least one required SIB or requested posSIB:

[0336] 3> ifonDemandSIB-Requestis configured and timer T350 is not running:

[0337] 4> initiate transmission of theDedicatedSIBRequestmessage;

[0338] 4> start timer T350 with the timer value set to theonDemandSIB-RequestProhibitTimer;

[0339] 1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the fieldsearchSpaceOtherSystemInformationand the UE has not stored a valid version of a SIB or posSIB, of one or several required SIB(s) or posSIB(s):

[0340] 2> for the SI message(s) that, according to thesi-SchedulingInfoin the stored SIB1, contain at least one required SIB and for whichsi-BroadcastStatusis set tobroadcasting:

[0341] 3> acquire the SI message(s);

[0342] 2> for the SI message(s) that, according to thesi-SchedulingInfoin the stored SIB1, contain at least one required SIB and for whichsi-BroadcastStatusis set tonotBroadcasting:

[0343] 3> ifonDemandSIB-Requestis configured and timer T350 is not running:

[0344] 4> initiate transmission of theDedicatedSIBRequestmessage;

[0345] 4> start timer T350 with the timer value set to theonDemandSIB-RequestProhibitTimer;

[0346] 4> acquire the requested SI message(s) corresponding to the requested SIB(s).

[0347] 2> for the SI message(s) that, according to theposSI-SchedulingInfoin the stored SIB1, contain at least one requested posSIB and for whichposSI-BroadcastStatusis set tobroadcasting:

[0348] 3> acquire the SI message(s);

[0349] 2> for the SI message(s) that, according to theposSI-SchedulingInfoin the stored SIB1, contain at least one requested posSIB and for whichposSI-BroadcastStatusis set tonotBroadcasting:

[0350] 3> ifonDemandSIB-Requestis configured and timer T350 is not running:

[0351] 4> initiate transmission of theDedicatedSIBRequestmessage;

[0352] 4> start timer T350 with the timer value set to theonDemandSIB-RequestProhibitTimer;

[0353] 4> acquire the requested SI message(s) corresponding to the requested posSIB(s).

[0354] - UE may include on demand request for SIB and / or posSIB(s) in the sameDedicatedSIBRequestmessage.

[0355] Actions related to transmission ofDedicatedSIBRequestmessage

[0356] The UE shall set the contents ofDedicatedSIBRequestmessage as follows:

[0357] 1> if the procedure is triggered to request the required SIB(s):

[0358] 2> includerequestedSIB-Listin theonDemandSIB-RequestListto indicate the requested SIB(s);

[0359] 1> if the procedure is triggered to request the required posSIB(s):

[0360] 2> includerequestedPosSIB-Listin theonDemandSIB-RequestListto indicate the requested posSIB(s).

[0361] The UE shall submit theDedicatedSIBRequestmessage to lower layers for transmission.

[0362] Actions upon receipt of System Information

[0363] Actions upon reception of theMIB

[0364] Upon receiving theMIBthe UE shall:

[0365] 1> store the acquiredMIB;

[0366] 1> if the UE is in RRC_IDLE or in RRC_INACTIVE, or if the UE is in RRC_CONNECTED whileT311is running:

[0367] 2> if the access is not for NTN or the UE is not capable of NTN; and

[0368] 2> if thecellBarredin the acquiredMIBis set tobarred:

[0369] 3> if the UE is a RedCap UE andssb-SubcarrierOffsetindicatesSIB1is transmitted in the cell:

[0370] 4> acquire theSIB1,which is scheduled;

[0371] 3> consider the cell as barred;

[0372] 3> perform cell re-selection to other cells on the same frequency as the barred cell;

[0373] 2> else:

[0374] 3> apply the receivedsystemFrameNumber,pdcch-ConfigSIB1,subCarrierSpacingCommon,ssb-SubcarrierOffsetanddmrs-TypeA-Position.

[0375] - A UE capable of NTN access should acquire SIB1 to determine whether the cell is an NTN cell.

[0376] Actions upon reception of theSIB1

[0377] Upon receiving theSIB1the UE shall:

[0378] 1> store the acquiredSIB1;

[0379] 1> if the access is for NTN, and thecellBarredNTNin the acquiredSIB1is set tobarredor thecellBarredNTNis not included in the acquiredSIB1:

[0380] 2> consider the cell as barred;

[0381] 2> perform cell re-selection to other cells on the same frequency as the barred cell;

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

[0383] 2> ifintraFreqReselectionRedCapis not present inSIB1:

[0384] 3> consider the cell as barred;

[0385] 3> perform barring as ifintraFreqReselectionRedCapis set to allowed;

[0386] 2> else:

[0387] 3> if thecellBarredRedCap1Rxis present in the acquiredSIB1and is set tobarredand the UE is equipped with 1 Rx branch; or

[0388] 3> if thecellBarredRedCap2Rxis present in the acquiredSIB1and is set tobarredand the UE is equipped with 2 Rx branches; or

[0389] 3> if thehalfDuplexRedCapAllowedis not present in the acquiredSIB1and the UE supports only half-duplex FDD operation:

[0390] 4> consider the cell as barred;

[0391] 4> perform barring based onintraFreqReselectionRedCap;

[0392] 1> if thecellAccessRelatedInfocontains an entry of a selected SNPN or PLMN and in case of PLMN the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast:

[0393] 2> in the remainder of the procedures usenpn-IdentityList, trackingAreaCode,andcellIdentityfor the cell as received in the corresponding entry ofnpn-IdentityInfoListcontaining the selected PLMN or SNPN;

[0394] 1> else if thecellAccessRelatedInfocontains an entry with thePLMN-Identityof the selected PLMN:

[0395] 2> in the remainder of the procedures useplmn-IdentityList,trackingAreaCode,trackingAreaList,andcellIdentityfor the cell as received in the correspondingPLMN-IdentityInfocontaining the selected PLMN;

[0396] 1> if the UE in RRC_INACTIVE is configured for feature(s) that it does not support in current serving cell:

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

[0398] 1> if in RRC_CONNECTED while T311 is not running:

[0399] 2> disregard thefrequencyBandList, if received, while in RRC_CONNECTED;

[0400] 2> forward thecellIdentityto upper layers;

[0401] 2> forward thetrackingAreaCodeto upper layers, if included;

[0402] 2> forward thetrackingAreaListto upper layers, if included;

[0403] 2> forward the receivedposSIB-MappingInfoto upper layers, if included;

[0404] 2> apply the configuration included in theservingCellConfigCommon;

[0405] 2> if the UE has a stored valid version of a SIB or posSIB, that the UE requires to operate within the cell:

[0406] 3> use the stored version of the required SIB or posSIB;

[0407] 2> else:

[0408] 3> acquire the required SIB or posSIB requested by upper layer;

[0409] 1> else:

[0410] 2> if the UE supports one or more of the frequency bands indicated in thefrequencyBandListfor downlink for TDD, or one or more of the frequency bands indicated in thefrequencyBandListfor uplink for FDD, and they are not downlink only bands, and

[0411] 2> if the UE is IAB-MT or supports at least oneadditionalSpectrumEmissionin theNR-NS-PmaxListfor a supported band in the downlink for TDD, or a supported band in uplink for FDD, and

[0412] 2> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration which

[0413] - is smaller than or equal to thecarrierBandwidth(indicated inuplinkConfigCommonfor the SCS of the initial uplink BWP or, for RedCap UE, of the RedCap-specific initial uplink BWP if configured), and which

[0414] - is wider than or equal to the bandwidth of the initial uplink BWP or, for RedCap UE, of the RedCap-specific initial uplink BWP if configured, and

[0415] 2> if the UE supports a downlink channel bandwidth with a maximum transmission bandwidth configuration which

[0416] - is smaller than or equal to thecarrierBandwidth(indicated indownlinkConfigCommonfor the SCS of the initial downlink BWP or, for RedCap UE, of the RedCap-specific initial downlink BWP if configured), and which

[0417] - is wider than or equal to the bandwidth of the initial downlink BWP or, for RedCap UE, of the RedCap-specific initial downlink BWP if configured, and

[0418] 2> iffrequencyShift7p5khzis present and the UE supports corresponding 7.5kHz frequency shift on this band; orfrequencyShift7p5khzis not present:

[0419] 3> if neithertrackingAreaCodenortrackingAreaListis provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list:

[0420] 4> consider the cell as barred;

[0421] 4> perform cell re-selection to other cells on the same frequency as the barred cell;

[0422] 3> else if UE is IAB-MT and ifiab-Supportis not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN:

[0423] 4> consider the cell as barred;

[0424] 3> else:

[0425] 4> apply a supported uplink channel bandwidth with a maximum transmission bandwidth which

[0426] - is contained within thecarrierBandwidthindicated inuplinkConfigCommonfor the SCS of the initial uplink BWP or, for RedCap UEs, RedCap-specific initial uplink BWP, if configured, and which

[0427] - is wider than or equal to the bandwidth of the initial BWP for the uplink or, for a RedCap UE, of the RedCap-specific initial uplink BWP if configured;

[0428] 4> apply a supported downlink channel bandwidth with a maximum transmission bandwidth which

[0429] - is contained within thecarrierBandwidthindicated indownlinkConfigCommonfor the SCS of the initial downlink BWP or, for RedCap UEs, RedCap-specific initial downlink BWP, if configured, and which

[0430] - is wider than or equal to the bandwidth of the initial BWP for the downlink or, for a RedCap UE, of the RedCap-specific initial downlink BWP if configured;

[0431] 4> select the first frequency band in thefrequencyBandList, for FDD fromfrequencyBandListfor uplink, or for TDD fromfrequencyBandListfor downlink,which the UE supports and for which the UE supports at least one of theadditionalSpectrumEmissionvalues innr-NS-PmaxList, if present;

[0432] 4> forward thecellIdentityto upper layers;

[0433] 4> forward thetrackingAreaCodeto upper layers;

[0434] 4> forward thetrackingAreaListto upper layers, if included;

[0435] 4> forward the receivedposSIB-MappingInfoto upper layers, if included;

[0436] 4> forward the PLMN identity or SNPN identity or PNI-NPN identity to upper layers;

[0437] 4> if in RRC_INACTIVE and the forwarded information does not trigger message transmission by upper layers:

[0438] 5> if the serving cell does not belong to the configuredran-NotificationAreaInfo:

[0439] 6> initiate an RNA update;

[0440] 4> forward theims-EmergencySupportto upper layers, if present;

[0441] 4> forward theeCallOverIMS-Supportto upper layers, if present;

[0442] 4> forward theUAC-AccessCategory1-SelectionAssistanceInfoorUAC-AC1-SelectAssistInfofor the selected PLMN / SNPNto upper layers, if present and set toa,borc;

[0443] 4> if the UE is in SNPN access mode:

[0444] 5> forward theimsEmergencySupportForSNPNindicators with the corresponding SNPN identities to upper layers, if present;

[0445] 4> apply the configuration included in theservingCellConfigCommon;

[0446] 4> apply the specified PCCH configuration;

[0447] 4> if the UE has a stored valid version of a SIB, that the UE requires to operate within the cell:

[0448] 5> use the stored version of the required SIB;

[0449] 4> if the UE has not stored a valid version of a SIB, of one or several required SIB(s):

[0450] 5> for the SI message(s) that, according to thesi-SchedulingInfo, contain at least one required SIB and for whichsi-BroadcastStatusis set to broadcasting:

[0451] 6> acquire the SI message(s);

[0452] 5> for the SI message(s) that, according to thesi-SchedulingInfo, contain at least one required SIB and for whichsi-BroadcastStatusis set tonotBroadcasting:

[0453] 6> trigger a request to acquire the SI message(s);

[0454] 4> if the UE has a stored valid version of a posSIB of one or several required posSIB(s):

[0455] 5> use the stored version of the required posSIB;

[0456] 4> if the UE has not stored a valid version of a posSIB of one or several posSIB(s):

[0457] 5> for the SI message(s) that, according to theposSI-SchedulingInfo, contain at least one requested posSIB and for whichposSI-BroadcastStatusis set tobroadcasting:

[0458] 6> acquire the SI message(s);

[0459] 5> for the SI message(s) that, according to theposSI-SchedulingInfo, contain at least one requested posSIB for whichposSI-BroadcastStatusis set tonotBroadcasting:

[0460] 6> trigger a request to acquire the SI message(s);

[0461] 4> apply the first listedadditionalSpectrumEmissionwhich it supports among the values included inNR-NS-PmaxListwithinfrequencyBandListinuplinkConfigCommonfor FDD or indownlinkConfigCommonfor TDD;

[0462] 4> if theadditionalPmaxis present in the same entry of the selectedadditionalSpectrumEmissionwithinNR-NS-PmaxList:

[0463] 5> apply theadditionalPmaxfor UL;

[0464] 4> else:

[0465] 5> apply thep-MaxinuplinkConfigCommonfor UL;

[0466] 4> ifsupplementaryUplinkis present inservingCellConfigCommon; and

[0467] 4> if the UE supports one or more of the frequency bands indicated in thefrequencyBandListfor thesupplementaryUplink; and

[0468] 4> if the UE supports at least oneadditionalSpectrumEmissionin theNR-NS-PmaxListfor a supported supplementary uplink band; and

[0469] 4> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration which

[0470] - is smaller than or equal to thecarrierBandwidth(indicated insupplementaryUplinkfor the SCS of the initial uplink BWP), and which

[0471] - is wider than or equal to the bandwidth of the initial uplink BWP of the SUL:

[0472] 5> consider supplementary uplink as configured in the serving cell;

[0473] 5> select the first frequency band in thefrequencyBandListfor thesupplementaryUplinkwhich the UE supports and for which the UE supports at least one of theadditionalSpectrumEmissionvalues innr-NS-PmaxList, if present;

[0474] 5> apply a supported supplementary uplink channel bandwidth with a maximum transmission bandwidth which

[0475] - is contained within thecarrierBandwidth(indicated insupplementaryUplinkfor the SCS of the initial uplink BWP), and which

[0476] - is wider than or equal to the bandwidth of the initial BWP of the SUL;

[0477] 5> apply the first listedadditionalSpectrumEmissionwhich it supports among the values included inNR-NS-PmaxListwithinfrequencyBandListfor thesupplementaryUplink;

[0478] 5> if theadditionalPmaxis present in the same entry of the selectedadditionalSpectrumEmissionwithinNR-NS-PmaxListfor thesupplementaryUplink:

[0479] 6> apply theadditionalPmaxinsupplementaryUplinkfor SUL;

[0480] 5> else:

[0481] 6> apply thep-MaxinsupplementaryUplinkfor SUL;

[0482] - For an out of coverage L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE receiving SIB1 from its connected L2 U2N Relay UE, it is up to Remote UE implementation whether to consider and apply the following parameters:frequencyBandList,carrierBandwidth,frequencyShift7p5khz, frequency band, channel bandwidth, the configuration included in theservingCellConfigCommon, the specified PCCH configuration,additionalSpectrumEmission,additionalPmax, andp-Max.

[0483] 2> else:

[0484] 3> consider the cell as barred; and

[0485] 3> perform barring as ifintraFreqReselection, orintraFreqReselectionRedCapfor RedCap UEs, is set tonotAllowed;

[0486] Hereinafter, technical features related to essential system information missing are described. Sections of 3GPP TS 38.331 v17.6.0 may be referred.

[0487] The UE shall:

[0488] 1> if in RRC_IDLE or in RRC_INACTIVE or in RRC_CONNECTED while T311 is running:

[0489] 2> if the UE is unable to acquire theMIB:

[0490] 3> consider the cell as barred;

[0491] 3> perform barring as ifintraFreqReselection, orintraFreqReselectionRedCapfor RedCap UEs, is set toallowed;

[0492] 2> else if the UE is unable to acquire theSIB1:

[0493] 3> consider the cell as barred;

[0494] 3> if the UE is a RedCap UE:

[0495] 4> perform barring as ifintraFreqReselectionRedCapis set toallowed;

[0496] 3> else:

[0497] 4> perform cell re-selection to other cells on the same frequency as the barred cell.

[0498] - TheSIB19is essential for NTN access. If UE is unable to acquire theSIB19for NTN access, the action is up to UE implementation (e.g., cell re-selection to other cells).

[0499] Hereinafter, technical features related to states and state transitions in RRC_IDLE are described. Sections of 3GPP TS 38.304 v17.6.0 may be referred.

[0500] FIG. 11 shows an example of RRC_IDLE and RRC_INACTIVE Cell Selection and Reselection.

[0501] In particular, FIG. 11 shows the states and state transitions and procedures in RRC_IDLE and RRC_INACTIVE.

[0502] Whenever a new PLMN selection or new SNPN selection is performed, it causes an exit to number 1.

[0503] Hereinafter, technical features related to cell selection / reselection are described. Sections of 3GPP TS 38.304 v17.6.0 may be referred.

[0504] Cell Selection process

[0505] Cell selection is performed by one of the following two procedures:

[0506] a) Initial cell selection (no prior knowledge of which RF channels are NR frequencies):

[0507] 1. The UE shall scan all RF channels in the NR bands according to its capabilities to find a suitable cell.

[0508] 2. On each frequency, the UE need only search for the strongest cell, except for operation with shared spectrum channel access where the UE may search for the next strongest cell(s).

[0509] 3. Once a suitable cell is found, this cell shall be selected.

[0510] b) Cell selection by leveraging stored information:

[0511] 1. This procedure requires stored information of frequencies and optionally also information on cell parameters from previously received measurement control information elements or from previously detected cells.

[0512] 2. Once the UE has found a suitable cell, the UE shall select it.

[0513] 3. If no suitable cell is found, the initial cell selection procedure in a) shall be started.

[0514] - Priorities between different frequencies or RATs provided to the UE by system information or dedicated signalling are not used in the cell selection process.

[0515] Cell Selection Criterion

[0516] The cell selection criterion S is fulfilled when:

[0517] Srxlev > 0 AND Squal > 0

[0518] where:

[0519] Srxlev = Qrxlevmeas - (Qrxlevmin + Qrxlevminoffset)- Pcompensation - Qoffsettemp

[0520] Squal = Qqualmeas - (Qqualmin + Qqualminoffset) - Qoffsettemp

[0521] Srxlev: Cell selection RX level value (dB)

[0522] Squal: Cell selection quality value (dB)

[0523] Qoffsettemp: Offset temporarily applied to a cell (dB)

[0524] Qrxlevmeas: Measured cell RX level value (RSRP)

[0525] Qqualmeas: Measured cell quality value (RSRQ)

[0526] Qrxlevmin: Minimum required RX level in the cell (dBm). If the UE supports SUL frequency for this cell, Qrxlevmin is obtained from q-RxLevMinSUL, if present, in SIB1, SIB2 and SIB4, additionally, if QrxlevminoffsetcellSUL is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell; else Qrxlevmin is obtained from q-RxLevMin in SIB1, SIB2 and SIB4, additionally, if Qrxlevminoffsetcell is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell.

[0527] Qqualmin: Minimum required quality level in the cell (dB). Additionally, if Qqualminoffsetcell is signalled for the concerned cell, this cell specific offset is added to achieve the required minimum quality level in the concerned cell.

[0528] Qrxlevminoffset: Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN.

[0529] Qqualminoffset: Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN.

[0530] Pcompensation: For FR1, if the UE supports the additionalPmax in the NR-NS-PmaxList, if present, in SIB1, SIB2 and SIB4: max(PEMAX1 -PPowerClass, 0) - (min(PEMAX2, PPowerClass) - min(PEMAX1, PPowerClass)) (dB); else: max(PEMAX1 -PPowerClass, 0) (dB); For FR2, Pcompensation is set to 0; For IAB-MT, Pcompensation is set to 0.

[0531] PEMAX1, PEMAX2: Maximum TX power level of a UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX. If UE supports SUL frequency for this cell, PEMAX1 and PEMAX2 are obtained from the p-Max for SUL in SIB1 and NR-NS-PmaxList for SUL respectively in SIB1, SIB2 and SIB4, else PEMAX1 and PEMAX2 are obtained from the p-Max and NR-NS-PmaxList respectively in SIB1, SIB2 and SIB4 for normal UL.

[0532] PPowerClass: Maximum RF output power of the UE (dBm) according to the UE power class.

[0533] The signalled values Qrxlevminoffsetand Qqualminoffsetare only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN. During this periodic search for higher priority PLMN, the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN.

[0534] Measurement rules for cell re-selection

[0535] Following rules are used by the UE to limit needed measurements:

[0536] - If the serving cell fulfils Srxlev> SIntraSearchPand Squal > SIntraSearchQ:

[0537] - IfdistanceThreshandreferenceLocationare broadcasted in SIB19, and if UE supports location-based measurement initiation and has obtained its location information:

[0538] - If the distance between UE and the serving cell reference locationreferenceLocationis shorter thandistanceThresh, the UE may not perform intra-frequency measurements;

[0539] - Else, the UE shall perform intra-frequency measurements;

[0540] - Else, the UE may not perform intra-frequency measurements;

[0541] - Else, the UE shall perform intra-frequency measurements.

[0542] - The UE shall apply the following rules for NR inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided:

[0543] - For a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies.

[0544] - For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current NR frequency:

[0545] - If the serving cell fulfils Srxlev > SnonIntraSearchPand Squal > SnonIntraSearchQ:

[0546] - IfdistanceThreshandreferenceLocationare broadcasted in SIB19, and if UE supports location-based measurement initiation and has obtained its UE location information:

[0547] - If the distance between UE and the serving cell reference locationreferenceLocationis shorter thandistanceThresh, the UE may choose not to perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority;

[0548] - Else, the UE shall perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority;

[0549] - Else, the UE may choose not to perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority;

[0550] - Else,the UE shall perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority.

[0551] - If the UE supports relaxed measurement andrelaxedMeasurementis present inSIB2, the UE may further relax the needed measurements.

[0552] If thet-Serviceof the serving cell is present in SIB19, and if UE supports time-based measurement initiation, the UE shall perform intra-frequency, inter-frequency or inter-RAT measurements before the t-Service, regardless of the distance between UE and the serving cell reference location or whether the serving cell fulfils Srxlev > SIntraSearchPand Squal > SIntraSearchQ, or Srxlev > SnonIntraSearchPand Squal > SnonIntraSearchQ, The exact time to start measurement beforet-Serviceis up to UE implementation. UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies regardless of the remaining service time of the serving cell (i.e. time remaining untilt-Service).

[0553] - When evaluating the distance between UE and the serving cell reference location, it's up to UE implementation to obtain UE location information.

[0554] Mobility states of aUE

[0555] The UE mobility state is determined if the parameters (TCRmax, NCR_H, NCR_M, TCRmaxHystandcellEquivalentSize) are broadcasted in system information for the serving cell.

[0556] State detection criteria:

[0557] Normal-mobility state criteria:

[0558] - If number of cell reselections during time period TCRmaxis less than NCR_M.

[0559] Medium-mobility state criteria:

[0560] - If number of cell reselections during time period TCRmaxis greater than or equal to NCR_Mbut less than or equal to NCR_H.

[0561] High-mobility state criteria:

[0562] - If number of cell reselections during time period TCRmaxis greater than NCR_H.

[0563] The UE shall not consider consecutive reselections where a cell is reselected again right after one reselection for mobility state detection criteria. If the UE is capable of HSDN and thecellEquivalentSizeis configured, the UE counts the number of cell reselections for this cell ascellEquivalentSizeconfigured for this cell.

[0564] State transitions:

[0565] The UE shall:

[0566] - if the criteria for High-mobility state is detected:

[0567] - enter High-mobility state.

[0568] - else if the criteria for Medium-mobility state is detected:

[0569] - enter Medium-mobility state.

[0570] - else if criteria for either Medium- or High-mobility state is not detected during time period TCRmaxHyst:

[0571] - enter Normal-mobility state.

[0572] If the UE is in High- or Medium-mobility state, the UE shall apply the speed dependent scaling rules.

[0573] Hereinafter, technical features related to Random Access Resource are described. Sections of 3GPP TS 38.321 v17.6.0 may be referred.

[0574] The Random Access procedure described in this clause is initiated by a PDCCH order, by the MAC entity itself, or by RRC for the events. There is only one Random Access procedure ongoing at any point in time in a MAC entity. The Random Access procedure on an SCell shall only be initiated by a PDCCH order with ra-PreambleIndex different from 0b000000.

[0575] - If a new Random Access procedure is triggered while another is already ongoing in the MAC entity, it is up to UE implementation whether to continue with the ongoing procedure or start with the new procedure (e.g. for SI request).

[0576] - If there was an ongoing Random Access procedure that is triggered by a PDCCH order while the UE receives another PDCCH order indicating the same Random Access Preamble, PRACH mask index and uplink carrier, the Random Access procedure is considered as the same Random Access procedure as the ongoing one and not initialized again.

[0577] When a Random Access procedure is initiated, UE selects a set of Random Access resources as specified in clause 5.1.1b and initialises the following parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources:

[0578] - prach-ConfigurationIndex: the available set of PRACH occasions for the transmission of the Random Access Preamble for Msg1. These are also applicable to the MSGA PRACH if the PRACH occasions are shared between 2-step and 4-step RA types;

[0579] - prach-ConfigurationPeriodScaling-IAB: the scaling factor and applicable to IAB-MTs, extending the periodicity of the PRACH occasions baseline configuration indicated by prach-ConfigurationIndex;

[0580] - prach-ConfigurationFrameOffset-IAB: the frame offset and applicable to IAB-MTs, altering the ROs frame defined in the baseline configuration indicated by prach-ConfigurationIndex;

[0581] - prach-ConfigurationSOffset-IAB: the subframe / slot offset and applicable to IAB-MTs, altering the ROs subframe or slot defined in the baseline configuration indicated by prach-ConfigurationIndex;

[0582] - msgA-PRACH-ConfigurationIndex: the available set of PRACH occasions for the transmission of the Random Access Preamble for MSGA in 2-step RA type;

[0583] - preambleReceivedTargetPower: initial Random Access Preamble power for 4-step RA type;

[0584] - msgA-PreambleReceivedTargetPower: initial Random Access Preamble power for 2-step RA type;

[0585] - rsrp-ThresholdSSB: an RSRP threshold for the selection of the SSB for 4-step RA type. If the Random Access procedure is initiated for beam failure recovery, rsrp-ThresholdSSB used for the selection of the SSB within candidateBeamRSList refers to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE;

[0586] - rsrp-ThresholdCSI-RS: an RSRP threshold for the selection of CSI-RS for 4-step RA type. If the Random Access procedure is initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE;

[0587] - msgA-RSRP-ThresholdSSB: an RSRP threshold for the selection of the SSB for 2-step RA type;

[0588] - rsrp-ThresholdSSB-SUL: an RSRP threshold for the selection between the NUL carrier and the SUL carrier;

[0589] - msgA-RSRP-Threshold: an RSRP threshold for selection between 2-step RA type and 4-step RA type when both 2-step and 4-step RA type Random Access Resources are configured in the UL BWP;

[0590] - rsrp-ThresholdMsg3: an RSRP threshold for Msg3 repetition;

[0591] - FeatureCombination: feature or a combination of features associated with a set of Random Access resources;

[0592] - featurePriorities: priorities for features, such as RedCap, Slicing, etc.;

[0593] - msgA-TransMax: The maximum number of MSGA transmissions when both 4-step and 2-step RA type Random Access Resources are configured;

[0594] - candidateBeamRSList: a list of reference signals (CSI-RS and / or SSB) identifying the candidate beams for recovery and the associated Random Access parameters;

[0595] - recoverySearchSpaceId: the search space identity for monitoring the response of the beam failure recovery request;

[0596] - powerRampingStep: the power-ramping factor;

[0597] - msgA-PreamblePowerRampingStep: the power ramping factor for MSGA preamble;

[0598] - powerRampingStepHighPriority: the power-ramping factor in case of prioritized Random Access procedure;

[0599] - scalingFactorBI: a scaling factor for prioritized Random Access procedure;

[0600] - ra-PreambleIndex: Random Access Preamble;

[0601] - ra-ssb-OccasionMaskIndex: defines PRACH occasion(s) associated with an SSB in which the MAC entity may transmit a Random Access Preamble (see clause 7.4);

[0602] - msgA-SSB-SharedRO-MaskIndex: Indicates the subset of 4-step RA type PRACH occasions shared with 2-step RA type PRACH occasions for each SSB. If 2-step RA type PRACH occasions are shared with 4-step RA type PRACH occasions and msgA-SSB-SharedRO-MaskIndex is not configured, then all 4-step RA type PRACH occasions are available for 2-step RA type;

[0603] - ssb-SharedRO-MaskIndex: defines PRACH occasions, on which preambles are allocated for a feature or a combination of features, associated with an SSB in which the MAC entity may transmit a Random Access Preamble;

[0604] - ra-OccasionList: defines PRACH occasion(s) associated with a CSI-RS in which the MAC entity may transmit a Random Access Preamble;

[0605] - ra-PreambleStartIndex: the starting index of Random Access Preamble(s) for on-demand SI request;

[0606] - startPreambleForThisPartition: the first preamble associated with the set of Random Access Resources applicable to the Random Access procedure;

[0607] - preambleTransMax: the maximum number of Random Access Preamble transmission;

[0608] - ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH occasion for 4-step RA type and the number of contention-based Random Access Preambles mapped to each SSB;

[0609] - msgA-CB-PreamblesPerSSB-PerSharedRO: defines the number of contention-based Random Access Preambles for 2-step RA type mapped to each SSB when the PRACH occasions are shared between 2-step and 4-step RA types;

[0610] - msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH occasion for 2-step RA type and the number of contention-based Random Access Preambles mapped to each SSB;

[0611] - numberOfPreamblesPerSSB-ForThisPartition: defines the number of consecutive preambles for a feature or a combination of features mapped to each SSB;

[0612] - msgA-PUSCH-ResourceGroupA: defines MSGA PUSCH resources that the UE shall use when performing MSGA transmission using Random Access Preambles group A;

[0613] - msgA-PUSCH-ResourceGroupB: defines MSGA PUSCH resources that the UE shall use when performing MSGA transmission using Random Access Preambles group B;

[0614] - msgA-PUSCH-Resource-Index: identifies the index of the PUSCH resource used for MSGA in case of contention-free Random Access with 2-step RA type;

[0615] - if groupBconfigured is configured, then Random Access Preambles group B is configured for 4-step RA type.

[0616] - Amongst the contention-based Random Access Preambles associated with an SSB, the first numberOfRA-PreamblesGroupA included in groupBconfigured Random Access Preambles belong to Random Access Preambles group A. The remaining Random Access Preambles associated with the SSB belong to Random Access Preambles group B (if configured).

[0617] - if groupB-ConfiguredTwoStepRA is configured, then Random Access Preambles group B is configured for 2-step RA type.

[0618] - Amongst the contention-based Random Access Preambles for 2-step RA type associated with an SSB, the first numberOfRA-PreamblesGroupA included in GroupB-ConfiguredTwoStepRA Random Access Preambles belong to Random Access Preambles group A. The remaining Random Access Preambles associated with the SSB belong to Random Access Preambles group B (if configured).

[0619] - If Random Access Preambles group B is supported by the cell Random Access Preambles group B is included for each SSB.

[0620] - if Random Access Preambles group B is configured for 4-step RA type:

[0621] - ra-Msg3SizeGroupA: the threshold to determine the groups of Random Access Preambles for 4-step RA type;

[0622] - msg3-DeltaPreamble: △PREAMBLE_Msg3;

[0623] - messagePowerOffsetGroupB: the power offset for preamble selection included in groupBconfigured;

[0624] - numberOfRA-PreamblesGroupA: defines the number of Random Access Preambles in Random Access Preamble group A for each SSB included in groupBconfigured.

[0625] - if Random Access Preambles group B is configured for 2-step RA type:

[0626] - msgA-DeltaPreamble: △MsgA_PUSCH;

[0627] - messagePowerOffsetGroupB: the power offset for preamble selection included in GroupB-ConfiguredTwoStepRA;

[0628] - numberOfRA-PreamblesGroupA: defines the number of Random Access Preambles in Random Access Preamble group A for each SSB included in GroupB-ConfiguredTwoStepRA;

[0629] - ra-MsgA-SizeGroupA: the threshold to determine the groups of Random Access Preambles for 2-step RA type.

[0630] - the set of Random Access Preambles and / or PRACH occasions for SI request, if any;

[0631] - the set of Random Access Preambles and / or PRACH occasions for beam failure recovery request, if any;

[0632] - the set of Random Access Preambles and / or PRACH occasions for reconfiguration with sync, if any;

[0633] - ra-ResponseWindow: the time window to monitor RA response(s) (SpCell only);

[0634] - ra-ContentionResolutionTimer: the Contention Resolution Timer (SpCell only);

[0635] - msgB-ResponseWindow: the time window to monitor RA response(s) for 2-step RA type (SpCell only).

[0636] Selection of the set of Random Access resources for the Random Access procedure

[0637] The MAC entity shall:

[0638] 1> if the BWP selected for Random Access procedure is configured with both set(s) of Random Access resources with msg3-Repetitions set to true and set(s) of Random Access resources without msg3-Repetitions set to true and the RSRP of the downlink pathloss reference is less than rsrp-ThresholdMsg3; or

[0639] 1> if the BWP selected for Random Access procedure is only configured with the set(s) of Random Access resources with msg3-Repetitions set to true:

[0640] 2> assume Msg3 repetition is applicable for the current Random Access procedure.

[0641] 1> else:

[0642] 2> assume Msg3 repetition is not applicable for the current Random Access procedure.

[0643] 1> if neither contention-free Random Access Resources nor Random Access Resources for SI request have been provided for this Random Access procedure and one or more of the features including RedCap and / or Slicing and / or SDT and / or MSG3 repetition is applicable for this Random Access procedure:

[0644] - The applicability of SDT is determined by MAC entity. The applicability of NSAG-ID is determined by upper layers when the Random Access procedure is initiated. The applicability of RedCap is also determined by upper layers when Random Access procedure is initiated and it is applicable to the Random Access procedures initiated by PDCCH orders and any Random Access procedure initiated by the MAC entity.

[0645] 2> if none of the sets of Random Access resources are available for any feature applicable to the current Random Access procedure:

[0646] 3> select the set(s) of Random Access resources that are not associated with any feature indication for this Random Access procedure.

[0647] 2> else if there is one set of Random Access resources available which can be used for indicating all features triggering this Random Access procedure:

[0648] 3> select this set of Random Access resources for this Random Access procedure.

[0649] 2> else (i.e. there are one or more sets of Random Access resources available that are configured with indication(s) for a subset of all features triggering this Random Access procedure):

[0650] 3> select a set of Random Access resources from the available set(s) of Random Access resources based on the priority order indicated by upper layers for this Random Access Procedure.

[0651] 1> else if contention-free Random Access Resources have been provided for this Random Access procedure and RedCap is applicable for the current Random Access procedure and there is one set of Random Access resources available that is only configured with RedCap indication:

[0652] 2> select this set of Random Access resources for this Random Access procedure.

[0653] 1> else:

[0654] 2> select the set of Random Access resources that are not associated with any feature indication for the current Random Access procedure.

[0655] Selection of the set of Random Access resources based on feature prioritization

[0656] The MAC entity shall:

[0657] 1> among the available sets of Random Access resources for this Random Access procedure, identify those configured with a feature which has the highest priority assigned in featurePriorities among all the features applicable to this Random Access procedure.

[0658] 1> if a single set of Random Access resources is identified:

[0659] 2> select this set of Random Access resources.

[0660] 1> else if more than one set of Random Access resources is identified:

[0661] 2> repeat the procedure taking as an input the identified sets of Random Access resources and the feature applicable to the current Random Access procedure with the highest priority assigned in featurePriorities among all the features applicable to this Random Access procedure, except the features considered already.

[0662] 1> else (i.e. no set of Random Access resources is identified):

[0663] 2> repeat the procedure taking as an input the previous identified available sets of Random Access resources and the feature applicable to the current Random Access procedure with the highest priority assigned in featurePriorities among all the features applicable to this Random Access procedure, except the features considered already.

[0664] Random Access Resource selection

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

[0666] 1> if the Random Access procedure was initiated for SpCell beam failure recovery; and

[0667] 1> if the beamFailureRecoveryTimer is either running or not configured; and

[0668] 1> if the contention-free Random Access Resources for beam failure recovery request associated with any of the SSBs and / or CSI-RSs have been explicitly provided by RRC; and

[0669] 1> if at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB amongst the SSBs in candidateBeamRSList or the CSI-RSs with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the CSI-RSs in candidateBeamRSList is available:

[0670] 2> select an SSB with SS-RSRP above rsrp-ThresholdSSB amongst the SSBs in candidateBeamRSList or a CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the CSI-RSs in candidateBeamRSList;

[0671] 2> if CSI-RS is selected, and there is no ra-PreambleIndex associated with the selected CSI-RS:

[0672] 3> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the SSB in candidateBeamRSList which is quasi-colocated with the selected CSI-RS.

[0673] 2> else:

[0674] 3> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SSB or CSI-RS from the set of Random Access Preambles for beam failure recovery request.

[0675] 1> else if the ra-PreambleIndex has been explicitly provided by PDCCH; and

[0676] 1> if the ra-PreambleIndex is not 0b000000:

[0677] 2> set the PREAMBLE_INDEX to the signalled ra-PreambleIndex;

[0678] 2> select the SSB signalled by PDCCH.

[0679] 1> else if the contention-free Random Access Resources associated with SSBs have been explicitly provided in rach-ConfigDedicated and at least one SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs is available:

[0680] 2> select an SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs;

[0681] 2> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SSB.

[0682] 1> else if the contention-free Random Access Resources associated with CSI-RSs have been explicitly provided in rach-ConfigDedicated and at least one CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the associated CSI-RSs is available:

[0683] 2> select a CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS amongst the associated CSI-RSs;

[0684] 2> set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected CSI-RS.

[0685] 1> else if the Random Access procedure was initiated for SI request; and

[0686] 1> if the Random Access Resources for SI request have been explicitly provided by RRC:

[0687] 2> if at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB is available:

[0688] 3> select an SSB with SS-RSRP above rsrp-ThresholdSSB.

[0689] 2> else:

[0690] 3> select any SSB.

[0691] 2> select a Random Access Preamble corresponding to the selected SSB, from the Random Access Preamble(s) determined according to ra-PreambleStartIndex;

[0692] 2> set the PREAMBLE_INDEX to selected Random Access Preamble.

[0693] 1> else (i.e. for the contention-based Random Access preamble selection):

[0694] 2> if at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB is available:

[0695] 3> select an SSB with SS-RSRP above rsrp-ThresholdSSB.

[0696] 2> else:

[0697] 3> select any SSB.

[0698] 2> if the RA_TYPE is switched from 2-stepRA to 4-stepRA:

[0699] 3> if a Random Access Preambles group was selected during the current Random Access procedure:

[0700] 4> select the same group of Random Access Preambles as was selected for the 2-step RA type.

[0701] 3> else:

[0702] 4> if Random Access Preambles group B is configured; and

[0703] 4> if the transport block size of the MSGA payload configured in the rach-ConfigDedicated corresponds to the transport block size of the MSGA payload associated with Random Access Preambles group B:

[0704] 5> select the Random Access Preambles group B.

[0705] 4> else:

[0706] 5> select the Random Access Preambles group A.

[0707] 2> else if Msg3 buffer is empty:

[0708] 3> if Random Access Preambles group B is configured:

[0709] 4> if the potential Msg3 size (UL data available for transmission plus MAC subheader(s) and, where required, MAC CEs) is greater than ra-Msg3SizeGroupA and the pathloss is less than PCMAX (of the Serving Cell performing the Random Access Procedure) - preambleReceivedTargetPower - msg3-DeltaPreamble - messagePowerOffsetGroupB; or

[0710] 4> if the Random Access procedure was initiated for the CCCH logical channel and the CCCH SDU size plus MAC subheader is greater than ra-Msg3SizeGroupA:

[0711] 5> select the Random Access Preambles group B.

[0712] 4> else:

[0713] 5> select the Random Access Preambles group A.

[0714] 3> else:

[0715] 4> select the Random Access Preambles group A.

[0716] 2> else (i.e. Msg3 is being retransmitted):

[0717] 3> select the same group of Random Access Preambles as was used for the Random Access Preamble transmission attempt corresponding to the first transmission of Msg3.

[0718] 2> select a Random Access Preamble randomly with equal probability from the Random Access Preambles associated with the selected SSB and the selected Random Access Preambles group;

[0719] 2> set the PREAMBLE_INDEX to the selected Random Access Preamble.

[0720] 1> if the Random Access procedure was initiated for SI request; and

[0721] 1> if ra-AssociationPeriodIndex and si-RequestPeriod are configured:

[0722] 2> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB in the association period given by ra-AssociationPeriodIndex in the si-RequestPeriod permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions corresponding to the selected SSB).

[0723] 1> else if an SSB is selected above:

[0724] 2> determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured, or ssb-SharedRO-MaskIndex if configured, or indicated by PDCCH (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions regardless the FR2 UL gap, corresponding to the selected SSB; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB).

[0725] 1> else if a CSI-RS is selected above:

[0726] 2> if there is no contention-free Random Access Resource associated with the selected CSI-RS:

[0727] 3> determine the next available PRACH occasion from the PRACH occasions, permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured, corresponding to the SSB in candidateBeamRSList which is quasi-colocated with the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the consecutive PRACH occasions regardless the FR2 UL gap, corresponding to the SSB which is quasi-colocated with the selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the SSB which is quasi-colocated with the selected CSI-RS).

[0728] 2> else:

[0729] 3> determine the next available PRACH occasion from the PRACH occasions in ra-OccasionList corresponding to the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers regardless the FR2 UL gap, corresponding to the selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected CSI-RS).

[0730] 1> perform the Random Access Preamble transmission procedure.

[0731] - When the UE determines if there is an SSB with SS-RSRP above rsrp-ThresholdSSB or a CSI-RS with CSI-RSRP above rsrp-ThresholdCSI-RS, the UE uses the latest unfiltered L1-RSRP measurement.

[0732] - If a RedCap UE in RRC_IDLE or RRC_INACTIVE mode is configured with a BWP indicated by initialDownlinkBWP-RedCap which is not associated with any SSB, SS-RSRP measurement is performed based on the SSB associated with the BWP indicated by initialDownlinkBWP. If a RedCap UE in RRC_INACTIVE mode is configured with SDT and with a BWP indicated by initialDownlinkBWP-RedCap which is associated with NCD-SSB, SS-RSRP measurement can also be performed based on this NCD-SSB during SDT.

[0733] - If a RedCap UE in RRC_IDLE or RRC_INACTIVE mode is configured with a BWP indicated by initialDownlinkBWP-RedCap which is not associated with any SSB for RACH, it is up to the UE implementation to perform a new RSRP measurements before Msg1 / MsgA retransmission.

[0734] Meanwhile, in cell re-selection procedure, UE is allowed to transmit a wake up signal (WUS) (for example, a SIB1 request) to request system information block type 1 (SIB1) transmission of a neighbor on-demand(OD)-SIB1 Cell, only if the OD-SIB1 Cell satisfies the cell reselection criteria to minimize the SIB1 transmission and the WUS transmission for network energy saving and UE power saving respectively.

[0735] However, when UE performs the cell selection, for example, for RRC connection re-establishment, it has no serving cell and the cell reselection criteria cannot be fulfilled. This means that the UE cannot trigger the WUS transmission based on the cell reselection criteria in this case. To enable UE to request SIB1 transmission for cell selection, a new triggering condition for WUS transmission should be defined, and the UE should select one triggering condition between them, for example, cell reselection criteria and the new triggering condition, based on the UE's condition, for example, whether the UE is performing cell selection or cell reselection.

[0736] Therefore, studies for triggering of SIB1 request are required.

[0737] Hereinafter, a method for triggering of SIB1 request, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

[0738] The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals / messages / fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings. Herein, a wireless device may be referred to as a user equipment (UE).

[0739] FIG. 12 shows an example of a method for triggering of SIB1 request, according to some embodiments of the present disclosure.

[0740] In particular, FIG. 12 shows an example of a method performed by a wireless device in a wireless communication system.

[0741] In step S1201, the wireless device may receive a configuration related to a system information block type 1 (SIB1) request.

[0742] For example, the configuration related to the SIB1 request may include information related to a radio resource for transmission of the SIB1 request and information related to the target cell identity.

[0743] For example, the SIB1 request for the target cell may be a random access channel (RACH) preamble. For example, the radio resource included in the SIB1 request configuration may be a RACH preamble.

[0744] In step S1202, the wireless device may determine whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria.

[0745] For example, the target cell may transmit the SIB1 in an on-demand manner.

[0746] For example, the wireless device may declare a radio link failure (RLF) for a serving cell. For example, the wireless device may initiate a radio resource control (RRC) connection re-establishment. For example, the wireless device may start a timer (for example, T311). For example, upon expiry of the timer, the wireless device may enter RRC_IDLE.

[0747] For example, while the timer is running, the wireless device may determine that the triggering condition is cell selection criteria. For example, upon expiry of the timer, the wireless device may determine that the triggering condition is cell reselection criteria.

[0748] For example, the wireless device may determine that the triggering condition is cell selection criteria based on that the wireless device does not camp on a suitable cell. The wireless device may determine that the triggering condition is cell reselection criteria based on that the wireless device camps on a suitable cell.

[0749] For example, the wireless device may determine that the triggering condition is cell selection criteria based on that the wireless device is in RRC_CONNECTED. The wireless device may determine that the triggering condition is cell reselection criteria based on that the wireless device is in RRC_IDLE or RRC_INACTIVE.

[0750] For example, the wireless device may determine that the triggering condition is cell selection criteria based on that the wireless device is performing a cell selection procedure. The wireless device may determine that the triggering condition is cell reselection criteria based on that the wireless device is performing a cell reselection procedure.

[0751] In step S1203, the wireless device may transmit a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0752] For example, while the timer (for example, T311) is running, the wireless device may transmit the SIB1 request for the target cell based on that the cell selection criteria is satisfied.

[0753] For example, upon expiry of the timer (for example, T311), the wireless device may transmit the SIB1 request for the target cell based on that the cell reselection criteria is satisfied.

[0754] For example, the wireless device may receive a SIB1 from the target cell. For example, the wireless device may select the target cell based on the received SIB1.

[0755] According to some embodiments of the present disclosure, the wireless device may be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0756] Hereinafter, technical features related to selection of SIB1 request condition are provided.

[0757] Embodiment #1

[0758] The UE selects a triggering condition of SIB1 request between the first condition and the second condition based on whether the UE is in camped normally state or not.

[0759] The UE selects the first condition if the UE is in the camped normally state.

[0760] The UE selects the second condition if the UE is not in the camped normally state.

[0761] The UE selects the first condition if the UE camps on a suitable cell.

[0762] The UE selects the second condition if the UE does not camp on a suitable cell.

[0763] The first condition is the cell re-selection criteria. If an OD-SIB1 cell satisfies the cell re-selection criteria, the UE considers the first condition is met for the OD-SIB1 cell.

[0764] The second condition is the cell selection criteria. If an OD-SIB1cell satisfies the cell selection criteria, the UE considers the second condition is met for the OD-SIB1cell.

[0765] The second condition is that the measurement result of an OD-SIB1cell, e.g., RSRP and / or RSRQ, is high than a radio quality threshold. In this case, if the measurement result of an OD-SIB1cell is high than the threshold, the UE considers the second condition is met for the OD-SIB1cell.

[0766] If the selected triggering condition is met for an OD-SIB1 cell, the UE transmit SIB1 request to the OD-SIB1 cell.

[0767] The OD-SIB1 cell is a cell which transmits SIB1 in on-demand manner.

[0768] Embodiment #2

[0769] The UE selects a triggering condition of SIB1 request between the first condition and the second condition based on the UE's RRC state.

[0770] The UE selects the first condition if the UE is RRC_IDLE.

[0771] The UE selects the first condition if the UE is RRC_INACTIVE.

[0772] The UE selects the second condition if the UE is RRC_CONNECTED.

[0773] Embodiment #3

[0774] The UE selects a triggering condition of SIB1 request between the first condition and the second condition based on the procedure that the UE is performing.

[0775] The UE selects the first condition if the UE is performing the cell re-selection.

[0776] The UE selects the second condition if the UE is performing the cell selection.

[0777] SIB1request configuration

[0778] UE receives the SIB1 request configuration from network, for example, via system information. The SIB1 request configuration at least includes a list of cells that transmit SIB1 in on-demand manner and the necessary details for requesting SIB1 transmission, e.g., RACH resources assigned for SIB1 request and / or a radio quality threshold.

[0779] A certain RACH resource is associated with a certain cell which supports the on-demand SIB1 transmission.

[0780] The SIB1 request configuration includes information required to check whether the OD-SIB1 cell satisfies the cell selection criteria, for example, Qrxlevmin, Qrxlevminoffset, and / or p-Max.

[0781] For example, the cell selection criterion S is fulfilled when:

[0782] Srxlev > 0 AND Squal > 0

[0783] where:

[0784] Srxlev = Qrxlevmeas- (Qrxlevmin+ Qrxlevminoffset)- Pcompensation- Qoffsettemp

[0785] Squal = Qqualmeas- (Qqualmin+ Qqualminoffset) - Qoffsettemp

[0786] Herein,

[0787] Srxlev: Cell selection RX level value (dB)

[0788] Squal: Cell selection quality value (dB)

[0789] Qoffsettemp: Offset temporarily applied to a cell (dB)

[0790] Qrxlevmeas: Measured cell RX level value (RSRP)

[0791] Qqualmeas: Measured cell quality value (RSRQ)

[0792] Qrxlevmin: Minimum required RX level in the cell (dBm). If the UE supports SUL frequency for this cell, Qrxlevminis obtained from q-RxLevMinSUL, if present, in SIB1, SIB2 and SIB4, additionally, if QrxlevminoffsetcellSULis present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell; else Qrxlevminis obtained from q-RxLevMin in SIB1, SIB2 and SIB4, additionally, if Qrxlevminoffsetcellis present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell.

[0793] Qqualmin: Minimum required quality level in the cell (dB). Additionally, if Qqualminoffsetcell is signalled for the concerned cell, this cell specific offset is added to achieve the required minimum quality level in the concerned cell.

[0794] Qrxlevminoffset: Offset to the signalled Qrxlevmintaken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN.

[0795] Qqualminoffset: Offset to the signalled Qqualmintaken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN.

[0796] Pcompensation: For FR1, if the UE supports the additionalPmax in the NR-NS-PmaxList, if present, in SIB1, SIB2 and SIB4

[0797] The SIB1 request configuration includes information required to check whether the OD-SIB1 cell satisfies the cell reselection criteria (for example, NR inter-frequency and inter-RAT Cell Reselection criteria, and / or intra-frequency and equal priority inter-frequency Cell Reselection criteria).

[0798] For example, the SIB1 request configuration includes information related to cell-ranking criterion Rs for serving cell and Rn for neighbouring cells.

[0799] where:

[0800] Rs= Qmeas,s+Qhyst- Qoffsettemp

[0801] Rn= Qmeas,n-Qoffset- Qoffsettemp

[0802] where:

[0803] Qmeas: RSRP measurement quantity used in cell reselections.

[0804] Qoffset: For intra-frequency, equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency, equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency.

[0805] Qoffsettemp: Offset temporarily applied to a cell.

[0806] For example, the UE shall perform ranking of all cells that fulfil the cell selection criterion S. The cells shall be ranked according to the R criteria specified above by deriving Qmeas,nand Qmeas,sand calculating the R values using averaged RSRP results.

[0807] SIB1request

[0808] If UE needs to acquire SIB1 of a certain cell, the UE selects a RACH resource which is associated with the certain cell. Then, the UE performs Random Access Preamble transmission using the selected RACH resource.

[0809] UE can directly request SIB1 transmission from a cell that is not broadcasting SIB1, for example, a cell that transits SIB1 in on-demand manner, based on the SIB1 request configuration.

[0810] UE can request SIB1 transmission of a cell, for example, a cell that transits SIB1 in on-demand manner, from another cell, for example, current serving cell.

[0811] FIG. 13 shows an example of a method for selection of SIB1 request condition.

[0812] In step S1301, the UE may receive a configuration of the SIB1 request which includes a list of neighbor OD-SIB1 cells.

[0813] In step S1302, the UE may declare the Radio Link Failure for MCG, and initiate the RRC connection re-establishment.

[0814] For example, the wireless device may start a timer (for example, T311) upon declaring the RLF for the MCG.

[0815] In step S1303, the UE may perform cell selection.

[0816] For example, the UE may perform the cell selection while the timer is running.

[0817] In step S1304, the UE may detect an OD-SIB1 cell listed in the configuration of the SIB1 request.

[0818] In step S1305, the UE may select the first condition, for example, cell selection criteria, as a triggering condition, since it is performing the cell selection.

[0819] For example, the UE may select the cell selection criteria, as a triggering condition, while the timer (T311) is running.

[0820] In step S1306, the UE may transmit SIB1 request to the OD-SIB1 cell.

[0821] For example, the cell selection criteria are fulfilled for the OD-SIB1 cell, so the UE transmits SIB1 request to the OD-SIB1 cell.

[0822] For example, the UE may transmit SIB1 request to the OD-SIB1 cell, when the first condition being met.

[0823] In step S1307, the UE may receive SIB1 from the OD-SIB1 cell.

[0824] In step S1308, the UE may camp on the OD-SIB1 cell.

[0825] FIG. 14 shows an example of a method for selection of SIB1 request condition.

[0826] In step S1401, the UE may receive, from network, the configuration of SIB1 request, which indicates at least the radio resource which can be used to transmit SIB1 request and a target cell identity.

[0827] In step S1402, the UE may determine that the triggering condition is cell selection criteria if the UE does not camp on a suitable cell, or the UE may determine that the triggering condition is cell reselection criteria if the UE camps on a suitable cell.

[0828] In step S1403, the UE may transmit SIB1 request based on the determined triggering condition being met.

[0829] In step S1404, the UE may receive SIB1 of the target cell.

[0830] FIG. 15 shows an example of a method for selection of SIB1 request condition.

[0831] In step S1501, the UE may receive, from network, the configuration of SIB1 request, which indicates at least the radio resource which can be used to transmit SIB1 request and a target cell identity.

[0832] In step S1502, the UE may determine that the triggering condition is cell selection criteria if the UE is in RRC_CONNECTED, or the UE may determine that the triggering condition is cell reselection criteria if the UE is in RRC_IDLE / INACTIVE.

[0833] In step S1503, the UE may transmit SIB1 request based on the determined triggering condition being met.

[0834] In step S1504, the UE may receive SIB1 of the target cell.

[0835] FIG. 16 shows an example of a method for selection of SIB1 request condition.

[0836] In step S1601, the UE may receive, from network, the configuration of SIB1 request, which indicates at least the radio resource which can be used to transmit SIB1 request and a target cell identity.

[0837] In step S1602, the UE may determine that the triggering condition is cell selection criteria if the UE is performing cell selection, or the UE may determine that the triggering condition is cell reselection criteria if the UE is performing cell reselection.

[0838] In step S1603, the UE may transmit SIB1 request based on the determined triggering condition being met.

[0839] In step S1604, the UE may receive SIB1 of the target cell.

[0840] Some of the detailed steps shown in the examples of FIGS. 12 - 16 may not be essential steps and may be omitted. In addition to the steps shown in FIGS. 12 - 16, other steps may be added, and the order of the steps may vary. Some of the above steps may have their own technical meaning.

[0841] Hereinafter, an apparatus for triggering of SIB1 request, according to some embodiments of the present disclosure, will be described. Herein, the apparatus may be a wireless device (100 or 200) in FIGS. 2, 3, 5, and 10.

[0842] For example, a wireless device may perform methods described above. The detailed description overlapping with the above-described contents could be simplified or omitted.

[0843] Referring to FIG. 5, a wireless device 100 may include a processor 102, a memory 104, and a transceiver 106.

[0844] According to some embodiments of the present disclosure, the processor 102 may be configured to be coupled operably with the memory 104 and the transceiver 106.

[0845] For example, the wireless device may include at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations.

[0846] The operations comprise: receiving a configuration related to a system information block type 1 (SIB1) request; determining whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; and transmitting a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0847] For example, the operations further comprise: receiving a SIB1 for the target cell, wherein the target cell transmits the SIB1 in an on-demand manner.

[0848] For example, the operations further comprise: selecting the target cell based on the received SIB1.

[0849] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device does not camp on a suitable cell.

[0850] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device camps on a suitable cell.

[0851] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device is in RRC_CONNECTED.

[0852] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device is in RRC_IDLE or RRC_INACTIVE.

[0853] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device is performing a cell selection procedure.

[0854] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device is performing a cell reselection procedure.

[0855] For example, the configuration related to the SIB1 request includes information related to a radio resource for transmission of the SIB1 request and information related to the target cell identity.

[0856] For example, the SIB1 request for the target cell is a random access channel (RACH) preamble.

[0857] For example, the operations further comprise: declaring a radio link failure (RLF) for a serving cell; and initiating a radio resource control (RRC) connection re-establishment.

[0858] For example, the processor may be adapted to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0859] Hereinafter, a processor for a wireless device for triggering of SIB1 request, according to some embodiments of the present disclosure, will be described.

[0860] The processor may be adapted to control the wireless device to perform operations.

[0861] The operations comprise: receiving a configuration related to a system information block type 1 (SIB1) request; determining whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; and transmitting a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0862] For example, the operations further comprise: receiving a SIB1 for the target cell, wherein the target cell transmits the SIB1 in an on-demand manner.

[0863] For example, the operations further comprise: selecting the target cell based on the received SIB1.

[0864] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device does not camp on a suitable cell.

[0865] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device camps on a suitable cell.

[0866] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device is in RRC_CONNECTED.

[0867] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device is in RRC_IDLE or RRC_INACTIVE.

[0868] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device is performing a cell selection procedure.

[0869] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device is performing a cell reselection procedure.

[0870] For example, the configuration related to the SIB1 request includes information related to a radio resource for transmission of the SIB1 request and information related to the target cell identity.

[0871] For example, the SIB1 request for the target cell is a random access channel (RACH) preamble.

[0872] For example, the operations further comprise: declaring a radio link failure (RLF) for a serving cell; and initiating a radio resource control (RRC) connection re-establishment.

[0873] For example, the processor may be adapted to control the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0874] Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for triggering of SIB1 request, according to some embodiments of the present disclosure, will be described.

[0875] According to some embodiment of the present disclosure, the technical features of the present disclosure could be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.

[0876] Some example of storage medium is coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For another example, the processor and the storage medium may reside as discrete components.

[0877] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

[0878] For example, non-transitory computer-readable media may include random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.

[0879] In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0880] According to some embodiment of the present disclosure, a non-transitory computer-readable medium has stored thereon a plurality of instructions. The stored a plurality of instructions may be executed by a processor of a wireless device. The stored a plurality of instructions may cause the wireless device to perform operations.

[0881] The operations comprise: receiving a configuration related to a system information block type 1 (SIB1) request; determining whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; and transmitting a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0882] For example, the operations further comprise: receiving a SIB1 for the target cell, wherein the target cell transmits the SIB1 in an on-demand manner.

[0883] For example, the operations further comprise: selecting the target cell based on the received SIB1.

[0884] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device does not camp on a suitable cell.

[0885] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device camps on a suitable cell.

[0886] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device is in RRC_CONNECTED.

[0887] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device is in RRC_IDLE or RRC_INACTIVE.

[0888] For example, the operations further comprise: determining that the triggering condition is cell selection criteria based on that the wireless device is performing a cell selection procedure.

[0889] For example, the operations further comprise: determining that the triggering condition is cell reselection criteria based on that the wireless device is performing a cell reselection procedure.

[0890] For example, the configuration related to the SIB1 request includes information related to a radio resource for transmission of the SIB1 request and information related to the target cell identity.

[0891] For example, the SIB1 request for the target cell is a random access channel (RACH) preamble.

[0892] For example, the operations further comprise: declaring a radio link failure (RLF) for a serving cell; and initiating a radio resource control (RRC) connection re-establishment.

[0893] For example, the stored a plurality of instructions may cause the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

[0894] Hereinafter, a method performed by a base station (BS) for triggering of SIB1 request, according to some embodiments of the present disclosure, will be described.

[0895] The method comprises: transmitting a configuration related to a system information block type 1 (SIB1) request. For example, the wireless device determines whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria. For example, the wireless device transmits a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0896] Hereinafter, a base station (BS) for triggering of SIB1 request, according to some embodiments of the present disclosure, will be described.

[0897] The BS may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory.

[0898] The processor may be adapted to perform operations. The method comprises: transmitting a configuration related to a system information block type 1 (SIB1) request. For example, the wireless device determines whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria. For example, the wireless device transmits a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

[0899] The present disclosure can have various advantageous effects.

[0900] According to some embodiments of the present disclosure, the wireless device could efficiently trigger transmission of a SIB1 request of an OD-SIB1 cell.

[0901] For example, a wireless device could avoid incorrect WUS transmission which could delay the SIB1 acquisition, by applying different WUS triggering condition depending on whether the wireless device camps on a suitable cell or not.

[0902] For example, the network could avoid unnecessary SIB1 transmission. Therefore, the network could save energy by allowing the wireless device to request SIB1 transmission based on the appropriate triggering condition which is suitable for the situation of the wireless device.

[0903] For example, the wireless device could efficiently transmit a SIB1 request by configuring a suitable triggering condition based on whether the wireless device is in cell selection situation or cell reselection situation.

[0904] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for triggering of SIB1 request for an OD-SIB1 cell.

[0905] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0906] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims

1.A method, comprising:receiving, by a wireless device, a configuration related to a system information block type 1 (SIB1) request;determining, by the wireless device, whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; andtransmitting, by the wireless device, a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.2.The method of claim 1, wherein the method further comprising:receiving, by the wireless device, a SIB1 for the target cell,wherein the target cell transmits the SIB1 in an on-demand manner.3.The method of claim 2, wherein the method further comprising:selecting, by the wireless device, the target cell based on the received SIB1.4.The method of claim 1, wherein the method further comprising:determining, by the wireless device, that the triggering condition is cell selection criteria based on that the wireless device does not camp on a suitable cell.5.The method of claim 1, wherein the method further comprising:determining, by the wireless device, that the triggering condition is cell reselection criteria based on that the wireless device camps on a suitable cell.6.The method of claim 1, wherein the method further comprising:determining, by the wireless device, that the triggering condition is cell selection criteria based on that the wireless device is in RRC_CONNECTED.7.The method of claim 1, wherein the method further comprising:determining, by the wireless device, that the triggering condition is cell reselection criteria based on that the wireless device is in RRC_IDLE or RRC_INACTIVE.8.The method of claim 1, wherein the method further comprising:determining, by the wireless device, that the triggering condition is cell selection criteria based on that the wireless device is performing a cell selection procedure.9.The method of claim 1, wherein the method further comprising:determining, by the wireless device, that the triggering condition is cell reselection criteria based on that the wireless device is performing a cell reselection procedure.10.The method of claim 1,wherein the configuration related to the SIB1 request includes information related to a radio resource for transmission of the SIB1 request and information related to the target cell identity.11.The method of claim 1,wherein the SIB1 request for the target cell is a random access channel (RACH) preamble.12.The method of claim 1, wherein the method further comprising:declaring, by the wireless device, a radio link failure (RLF) for a serving cell; andinitiating, by the wireless device, a radio resource control (RRC) connection re-establishment.13.The method of claim 1,wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.14.A wireless device, comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving a configuration related to a system information block type 1 (SIB1) request;determining whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; andtransmitting a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.15.The wireless device of claim 14, wherein the operations further comprising:receiving a SIB1 for the target cell,wherein the target cell transmits the SIB1 in an on-demand manner.16.The wireless device of claim 15, wherein the operations further comprising:selecting the target cell based on the received SIB1.17.The wireless device of claim 14, wherein the operations further comprising:determining that the triggering condition is cell selection criteria based on that the wireless device does not camp on a suitable cell.18.The wireless device of claim 14, wherein the operations further comprising:determining that the triggering condition is cell reselection criteria based on that the wireless device camps on a suitable cell.19.The wireless device of claim 14, wherein the operations further comprising:determining that the triggering condition is cell selection criteria based on that the wireless device is in RRC_CONNECTED.20.The wireless device of claim 14, wherein the operations further comprising:determining that the triggering condition is cell reselection criteria based on that the wireless device is in RRC_IDLE or RRC_INACTIVE.21.The wireless device of claim 14, wherein the operations further comprising:determining that the triggering condition is cell selection criteria based on that the wireless device is performing a cell selection procedure.22.The wireless device of claim 14, wherein the operations further comprising:determining that the triggering condition is cell reselection criteria based on that the wireless device is performing a cell reselection procedure.23.The wireless device of claim 14,wherein the configuration related to the SIB1 request includes information related to a radio resource for transmission of the SIB1 request and information related to the target cell identity.24.The wireless device of claim 14,wherein the SIB1 request for the target cell is a random access channel (RACH) preamble.25.The wireless device of claim 14, wherein the operations further comprising:declaring a radio link failure (RLF) for a serving cell; andinitiating a radio resource control (RRC) connection re-establishment.26.The wireless device of claim 14,wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.27.A processor for a wireless device in a wireless communication system, wherein the processor is adapted to control the wireless device to perform operations comprising:receiving a configuration related to a system information block type 1 (SIB1) request;determining whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; andtransmitting a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.28.A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a wireless device, cause the wireless device to perform operations, the operations comprising,receiving a configuration related to a system information block type 1 (SIB1) request;determining whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria; andtransmitting a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.29.A method, the method comprising,transmitting, by a base station, a configuration related to a system information block type 1 (SIB1) request,wherein the wireless device determines whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria, andwherein the wireless device transmits a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.30.A base station, comprising:a transceiver;a memory; andat least one processor operatively coupled to the transceiver and the memory, and adapted to perform operations:transmitting a configuration related to a system information block type 1 (SIB1) request,wherein the wireless device determines whether a triggering condition for a target cell is based on either cell selection criteria or cell reselection criteria, andwherein the wireless device transmits a SIB1 request for the target cell, based on that the determined triggering condition is satisfied.

Images