Method and apparatus for receiving system information based on dynamic modification period

Abstract

A method and apparatus for receiving system information based on dynamic modification period is provided. The wireless device receives, from a network, information related to a first modification period. The wireless device acquisitions a first system information message based on the first modification period. The wireless device receives, from the network, a system information modification indication including information related to a second modification period. The wireless device acquisitions a second system information message based on the second modification period.

Description

METHOD AND APPARATUS FOR RECEIVING SYSTEM INFORMATION BASED ON DYNAMIC MODIFICATION PERIOD

[0001] The present disclosure relates to a method and apparatus for receiving system information based on dynamic modification period.

[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] Applying AIML method in wireless communication has the potential improvement in optimized configuration, which can improve UE / NW performance and proactive resolution from problematic scenario. Also, the optimized configuration can be utilized for UE / NW energy saving through compact resource allocation and reducing of measurements and reports. For R19 AIML mobility SI, dynamic adjustment on handover parameters / events based on AI / ML model, for example, adjustment on Hys and TTT, has been proposed. In this use case, it considers the UEs in RRC_CONNECTED with dedicated signalling.

[0006] With extension of use cases, dynamic adjustment can also be utilized for UEs in RRC_IDLE and RRC_INACTIVE. For example, dynamic optimized adjustment can be applied for configuration of mobility (for example, cell reselection) and / or power saving (for example, RRM relaxation, RLM / BFD relaxation).

[0007] However, in the legacy mechanism, acquisition of new system information happens in a restricted static time point. Change of system information only occurs at specific radio frame based on modification period. For example, for the UEs except eDRX UEs, modification period boundary is determined by SFN mod m = 0, where m is the number of radio frames comprising the modification period configured.

[0008] UEs in RRC_IDLE or in RRC_INACTIVE should monitor for SI change indication in its own paging occasion(s). UEs in RRC_CONNECTED should monitor for SI change indication in any paging occasion at least once per modification period. When UE receives the SI change indication in the current modification period(N), it applies the system information acquisition procedure from the start of the next modification period(N+1).

[0009] If the modification period is long, it takes a long time to apply the optimized adjustment, making it difficult to apply the effects of AIML on the UE and network.

[0010] On the other hand, if the modification period is always set to be short, frequent transmission / reception of system information is assumed, which places a burden on the UE / NW in terms of both signalling and power consumption, and mismatches between the UE / NW may occur in the settings. Therefore, a method is needed that ensures stable operation based on system information and allows optimized adjustments to be applied in a timely manner.

[0011] Thus, studies for receiving system information based on dynamic modification period are required.

[0012] In an aspect, a method, comprises: receiving, by a wireless device from a network, information related to a first modification period; acquisitioning, by the wireless device, a first system information message based on the first modification period; receiving, by the wireless device from the network, a system information modification indication including information related to a second modification period; and acquisitioning, by the wireless device, a second system information message based on the second modification period.

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

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

[0015] According to some embodiments of the present disclosure, a wireless device could efficiently receive system information based on dynamic modification period.

[0016] For example, by applying optimized system information dynamically, if necessary, NW can allow optimized adjustments to be applied in a timely manner. Through the dynamic optimized configuration using AIML mechanism, performance such as mobility (for example, cell reselection), power saving (for example, through RRM relaxation, RLM / BFD relaxation, SSB / CSI-RS measurement) can be improved quickly.

[0017] For example, by dynamically changing the modification period, the wireless device could save resources.

[0018] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for receiving system information based on dynamic modification period.

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

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

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

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

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

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

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

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

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

[0028] FIG. 10 shows an example of system information acquisition.

[0029] FIG. 11 shows an example of a scenario for acquisition of a new SI.

[0030] FIG. 12 shows an example of a method for receiving system information based on dynamic modification period.

[0031] FIG. 13 shows an example of a method for acquisition of system information based on dynamic modification period information.

[0032] FIG. 14 shows an example for acquisition of system information based on dynamic modification period information.

[0033] FIG. 15 shows an example for acquisition of system information based on dynamic modification period information.

[0034] FIG. 16 shows an example for acquisition of system information based on dynamic modification period information.

[0035] FIG. 17 shows an example of a method for acquisition of system information based on dynamic modification period information.

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

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

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

[0039] 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".

[0040] 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".

[0041] 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".

[0042] 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".

[0043] 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".

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

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

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

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

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

[0049] 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).

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

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

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

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

[0054] 5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-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.

[0055] 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 behavior 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.

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

[0057] 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 behaviors 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.

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

[0059] 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 reconstructible 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.

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

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

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

[0063] 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 smartpad, a wearable device (e.g., a smartwatch or a smartglasses), 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 smartmeter.

[0064] In the present disclosure, the wireless devices 100a to 100f may be called user equipments (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.

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

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

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

[0068] 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 smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.

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

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

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

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

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

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

[0075] 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 (eMTC). 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.

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

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

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

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

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

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

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

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

[0084] 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).

[0085] 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 (analog) 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 (analog) oscillators and / or filters under the control of the transceivers 102 and 202.

[0086] 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 behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior 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 behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0108] 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).

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

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

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

[0112] 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).

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

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

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

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

[0117] 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).

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

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

[0120] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

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

[0122] uNslotsymbNframe,uslotNsubframe,uslot212404

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

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

[0125] 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).

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

[0127] 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).

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

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

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

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

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

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

[0134] Hereinafter, technical features related to AI / ML are described.

[0135] The application of AI / ML to wireless communications has been thus far limited to implementation-based approaches, both, at the network and the UE sides. A study on enhancement for data collection for NR and ENDC (FS_NR_ENDC_data_collect) has examined thefunctional framework for RAN intelligence enabled by further enhancement of data collection through use cases, examples etc. and identify the potential standardization impacts on currentNG-RAN nodes and interfaces. In SA WG2 AI / ML related study, a network functionality NWDAF (Network Data Analytics Function) was introduced in Rel-15 and has been enhanced in Rel-16 and Rel-17.

[0136] In this study, we explore the benefits of augmenting the air-interface with features enabling improved support of AI / ML based algorithms for enhanced performance and / or reduced complexity / overhead. Enhanced performance here depends on the use cases under consideration and could be, e.g., improved throughput, robustness, accuracy or reliability, etc.

[0137] Through studying a few carefully selected use cases, assessing their performance in comparison with traditional methods and the associated potential specification impacts that enable their solutions, this SI will　lay the foundation for future air-interface use cases leveraging AI / ML techniques.

[0138] The goal is that sufficient use cases will be considered to enable the identification of a common AI / ML framework, including functional requirements of AI / ML architecture, which could be used in subsequent projects. The study should also identify areas where AI / ML could improve the performance of air-interface functions.

[0139] The study will serve identifying what is required for an adequate AI / ML model characterization and description establishing pertinent notation for discussions and subsequent evaluations. Various levels of collaboration between the gNB and UE are identified and considered.

[0140] Evaluations to exercise the attainable gains of AI / ML based techniques for the use cases under consideration will be carried out with the corresponding identification of KPIs with the goal to have a better understanding of the attainable gains and associated complexity requirements.

[0141] Finally, specification impact will be assessed in order to improve the overall understanding of what would be required to enable AI / ML techniques for the air-interface.

[0142] For the study on AI / ML for air-interface, the basic framework and principles agreed forFS_NR_ENDC_data_collectshould be taken into consideration for possible applicability.

[0143] Study the 3GPP framework for AI / ML for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.

[0144] Use cases to focus on:

[0145] 1> Initial set of use cases includes:

[0146] a) CSI feedback enhancement, e.g., overhead reduction, improved accuracy, prediction

[0147] b) Beam management, e.g., beam prediction in time, and / or spatial domain for overhead and latency reduction, beam selection accuracy improvement

[0148] c) Positioning accuracy enhancements for different scenarios including, e.g., those with heavy NLOS conditions

[0149] 2> Finalize representative sub use cases for each use case for characterization and baseline performance evaluations

[0150] a) The AI / ML approaches for the selected sub use cases need to be diverse enough to support various requirements on the gNB-UE collaboration levels

[0151] - the selection of use cases for this study solely targets the formulation of a framework to apply AI / ML to the air-interface for these and other use cases. The selection itself does not intend to provide any indication of the prospects of any future normative project.

[0152] AI / ML model, terminology and description to identify common and specific characteristics for framework investigations:

[0153] 3> Characterize the defining stages of AI / ML related algorithms and associated complexity:

[0154] a) Model generation, e.g., model training (including input / output, pre- / post-process, online / offline as applicable), model validation, model testing, as applicable

[0155] b) Inference operation, e.g., input / output, pre- / post-process, as applicable

[0156] 4> Identify various levels of collaboration between UE and gNB pertinent to the selected use cases, e.g.,

[0157] a) No collaboration: implementation-based only AI / ML algorithms without information exchange [for comparison purposes]

[0158] b) Various levels of UE / gNB collaboration targeting at separate or joint ML operation.

[0159] 5> Characterize lifecycle management of AI / ML model: e.g., model training, model deployment , model inference, model monitoring, model updating

[0160] 6> Dataset(s) for training, validation, testing, and inference

[0161] 7> Identify common notation and terminology for AI / ML related functions, procedures and interfaces

[0162] 8> Consider the work done for FS_NR_ENDC_data_collect when appropriate

[0163] For the use cases under consideration:

[0164] - Evaluate performance benefits of AI / ML based algorithms for the agreed use cases in the final representative set:

[0165] a) Methodology based on statistical models, for link and system level simulations.

[0166] i. Extensions of 3GPP evaluation methodology for better suitability to AI / ML based techniques should be considered as needed.

[0167] ii. Whether field data are optionally needed to further assess the performance and robustness in real-world environments should be discussed as part of the study.

[0168] iii. Need for common assumptions in dataset construction for training, validation and test for the selected use cases.

[0169] iv. Consider adequate model training strategy, collaboration levels and associated implications

[0170] v. Consider agreed-upon base AI model(s) for calibration

[0171] vi. AI model description and training methodology used for evaluation should be reported for information and cross-checking purposes

[0172] b) KPIs: Determine the common KPIs and corresponding requirements for the AI / ML operations. Determine the use-case specific KPIs and benchmarks of the selected use-cases.

[0173] i. Performance, inference latency and computational complexity of AI / ML based algorithms should be compared to that of a state-of-the-art baseline

[0174] ii. Overhead, power consumption (including computational), memory storage, and hardware requirements (including for given processing delays) associated with enabling respective AI / ML scheme, as well as generalization capability should be considered.

[0175] - Assess potential specification impact, specifically for the agreed use cases in the final representative set and for a common framework:

[0176] c) PHY layer aspects,

[0177] i. Consider aspects related to, e.g., the potential specification of the AI Model lifecycle management, and dataset construction for training, validation and test for the selected use cases

[0178] ii. Use case and collaboration level specific specification impact, such as new signalling, means for training and validation data assistance, assistance information, measurement, and feedback

[0179] d) Protocol aspects, e.g., (RAN2) - RAN2 only starts the work after there is sufficient progress on the use case study in RAN1

[0180] i. Consider aspects related to, e.g., capability indication, configuration and control procedures (training / inference), and management of data and AI / ML model, per RAN1 input

[0181] ii. Collaboration level specific specification impact per use case

[0182] e) Interoperability and testability aspects, e.g., (RAN4) - RAN4 only starts the work after there is sufficient progress on use case study in RAN1 and RAN2

[0183] i. Requirements and testing frameworks to validate AI / ML based performance enhancements and ensuring that UE and gNB with AI / ML meet or exceed the existing minimum requirements if applicable

[0184] ii. Consider the need and implications for AI / ML processing capabilities definition

[0185] - specific AI / ML models are not expected to be specified and are left to implementation. User data privacy needs to be preserved.

[0186] - The study on AI / ML for air interface is based on the current RAN architecture and new interfaces shall not be introduced.

[0187] The application of AI / ML techniques to NR air interface has been studied in FS_NR_AIML_Air.

[0188] In this work item, we provide the normative support for the general framework for AI / ML for air interface, as well as, enable the recommended use cases in the preceding study. In addition, a number of study objectives in this project will tackle some outstanding issues identified during the study in an attempt to deepen the understanding in view of future normative work.

[0189] Objective of SI or Core part WI or Testing part WI

[0190] Provide specification support for the following aspects:

[0191] 1> AI / ML general framework for one-sided AI / ML models within the realm of what has been studied in the FS_NR_AIML_Air project [RAN2]:

[0192] 2> Signalling and protocol aspects of Life Cycle Management (LCM) enabling functionality and model (if justified) selection, activation, deactivation, switching, fallback

[0193] 3> Identification related signalling is part of the above objective

[0194] 2> Necessary signalling / mechanism(s) for LCM to facilitate model training, inference, performance monitoring, data collection (except for the purpose of CN / OAM / OTT collection of UE-sided model training data) for both UE-sided and NW-sided models

[0195] 2> Signalling mechanism of applicable functionalities / models

[0196] 1> Beam management - DL Tx beam prediction for both UE-sided model and NW-sided model, encompassing [RAN1 / RAN2]:

[0197] 2> Spatial-domain DL Tx beam prediction for Set A of beams based on measurement results of Set B of beams ("BM-Case1")

[0198] 2> Temporal DL Tx beam prediction for Set A of beams based on the historic measurement results of Set B of beams ("BM-Case2")

[0199] 2> Specify necessary signalling / mechanism(s) to facilitate LCM operations specific to the Beam Management use cases, if any

[0200] 2> Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE

[0201] - Strive for common framework design to support both BM-Case1 and BM-Case2

[0202] 1> Positioning accuracy enhancements, encompassing [RAN1 / RAN2 / RAN3]:

[0203] 2> Direct AI / ML positioning:

[0204] 3> (1stpriority) Case 1: UE-based positioning with UE-side model, direct AI / ML positioning

[0205] 3> (2ndpriority) Case 2b: UE-assisted / LMF-based positioning with LMF-side model, direct AI / ML positioning

[0206] 3> (1stpriority) Case 3b: NG-RAN node assisted positioning with LMF-side model, direct AI / ML positioning

[0207] 2> AI / ML assisted positioning

[0208] 3> (2ndpriority) Case 2a: UE-assisted / LMF-based positioning with UE-side model, AI / ML assisted positioning

[0209] 3> (1stpriority) Case 3a: NG-RAN node assisted positioning with gNB-side model, AI / ML assisted positioning

[0210] 2> Specify necessary measurements, signalling / mechanism(s) to facilitate LCM operations specific to the Positioning accuracy enhancements use cases, if any

[0211] 2> Investigate and specify the necessary signalling of necessary measurement enhancements (if any)

[0212] 2> Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE for relevant positioning sub use cases

[0213] 1> Core requirements for the above two use cases for AI / ML LCM procedures and UE features [RAN4]:

[0214] 2> Specify necessary RAN4 core requirements for the above two use cases.

[0215] 2> Specify necessary RAN4 core requirements for LCM procedures including performance monitoring.

[0216] Study objectives with corresponding checkpoints in RAN#105 (Sept '24):

[0217] 1> CSI feedback enhancement [RAN1]:

[0218] 2> For CSI compression (two-sided model), further study ways to:

[0219] 3> Improve trade-off between performance and complexity / overhead

[0220] 4> e.g., considering extending the spatial / frequency compression to spatial / temporal / frequency compression, cell / site specific models, CSI compression plus prediction (compared to Rel-18 non-AI / ML based approach), etc.

[0221] 3> Alleviate / resolve issues related to inter-vendor training collaboration.

[0222] while addressing other aspects requiring further study / conclusion as captured in the conclusions section of the TR 38.843.

[0223] 2> For CSI prediction (one-sided model), further study performance gain over Rel-18 non-AI / ML based approach and associated complexity, while addressing other aspects requiring further study / conclusion as captured in the conclusions section of the TR 38.843 (e.g., cell / site specific model could be considered to improve performance gain).

[0224] 1> Necessity and details of model Identification concept and procedure in the context of LCM [RAN2 / RAN1]

[0225] 1> CN / OAM / OTT collection of UE-sided model training data [RAN2 / RAN1]:

[0226] 2> For the FS_NR_AIML_Air study use cases, identify the corresponding contents of UE data collection

[0227] 2> Analyse the UE data collection mechanisms identified during the FS_NR_AIML_Air study along with the implications and limitations of each of the methods

[0228] 1> Model transfer / delivery [RAN2 / RAN1]:

[0229] 2> Determine whether there is a need to consider standardised solutions for transferring / delivering AI / ML model(s) considering at least the solutions identified during the FS_NR_AIML_Air study

[0230] 1> Testability and interoperability [RAN4]:

[0231] 2> Finalize the testing framework and procedure for one-sided models and further analyse the various testing options for two-sided models, in collaboration with RAN1, and including at least:

[0232] 3> Relation to legacy requirements

[0233] 3> Performance monitoring and LCM aspects considering use-case specifics

[0234] 3> Generalization aspects

[0235] 3> Static / non-static scenarios / conditions and propagation conditions for testing (e.g., CDL, field data, etc.)

[0236] 3> UE processing capability and limitations

[0237] 3> Post-deployment validation due to model change / drift

[0238] 2> RAN5 aspects related to testability and interoperability to be addressed on a request basis

[0239] - offline training is assumed for the purpose of this project.

[0240] - the outcome of the study objectives should be captured in TR 38.843 for future reference.

[0241] - Coordination with SA / SA WGs of the ongoing study / work as it may relate to their required work.

[0242] With existing L3 handover mechanism, handover is triggered and executed based on reported historical measurement result and / or measurement event(s) i.e., it is kind of reactive scheme by its nature. It may work well among macro cells when UE's mobility is low for existing services. But it could be problematic when either UE's mobility is high or among micro cells of high density or both for existing services or future services e.g. XR, where such reactive scheme may result in more unintended event e.g., handover failure, radio link failure, Ping-Pong phenomenon, throughput loss or too early / late handover etc. To improve handover robustness conditional handover is introduced in Rel-16. And to reduce interruption time of frequent handover among small cells LTM HO is introduced in Rel-18. However, these two mechanisms are not sufficient because they are still reactive scheme by design. On the other hand, mechanism based on AI / ML algorithm has the potential to enable proactive scheme.

[0243] In Rel-18 SID called FS_NR_AIML_air was studied extensively on physical layer centric use cases including spatial and temporal beam prediction. Temporal prediction within serving cell is mainly to predict the best or top-K beam(s) or beam pair(s) in time domain in order to improve UE throughput. While predict the best or top-K beam(s) or beam pair(s) among a set of beams by measuring a smaller set of beams could help reduce RS signalling overhead, measurement efforts and UE power consumption etc. By extended L1 beam measurement from serving cell to neighbouring cell, majority of the RAN1 work can be reused for e.g. LTM HO study. Since L3 measurement is based on filtering of L1 measurement, the study of AI / ML for air can be leveraged for mobility purpose e.g., temporal prediction can also be used to predict beam(s) / cell(s) becoming worse so that unintended event like radio link failure or short-stay handover can be avoided.

[0244] Mobility enhancement was also studied in RAN3 in Rel-17 in SID called FS_NR_ENDC_data_collect and is now specified in Rel-18 WID NR_AIML_NGRAN-Core. In these RAN3 items the study and normative work on mobility enhancement is based on information available in network side e.g. handover and stay of time in history among cells to predict UE's trajectory in single hop and hence potential candidates. In Rel-19 RAN3 will further work on UE's trajectory for multiple hops. The predicted UE's trajectory could be helpful for study on AI / ML mobility over air interface to some extent.

[0245] Based on progress made in RAN1 and RAN3 so far and assumption on UE's trajectory it is feasible to predict RRM measurement and / or event and hence candidate target cell in UE side. In network side new assistant information, if necessary, and statistics information based on measurement report from UE and / or neighbouring nodes can be also used for smart prediction. If some prediction information could be known by network, handover and / or RRM performance can be improved by proactive measures to either make a better decision or avoid unintended event.

[0246] Objective of SI or Core part WI or Testing part WI

[0247] The study will focus on mobility enhancement in RRC_CONNECTED mode over air interface by following existing mobility framework, i.e., handover decision is always made in network side. Mobility use cases focus on standalone NR PCell change. UE-side and network-side AI / ML model can be both considered, respectively.

[0248] Study and evaluate potential benefits and gains of AI / ML aided mobility for network triggered L3-based handover, considering the following aspects:

[0249] 1> AI / ML based RRM measurement and event prediction,

[0250] 2> Cell-level measurement prediction including intra and inter-frequency (UE sided and NW sided model) [RAN2]

[0251] 3> Inter-cell Beam-level measurement prediction for L3 Mobility (UE sided and NW sided model) [RAN2]

[0252] 2> HO failure / RLF prediction (UE sided model) [RAN2]

[0253] 2> Measurement events prediction (UE sided model) [RAN2]

[0254] 1> Study the need / benefits of any other UE assistance information for the network side model [RAN2]

[0255] 1> The evaluation of the AI / ML aided mobility benefits should consider HO performance KPIs (e.g., Ping-pong HO, HOF / RLF, Time of stay, Handover interruption, prediction accuracy, and measurement reduction) etc.) and complexity tradeoffs [RAN2]

[0256] 1> Potential AI mobility specific enhancement should be based on the Rel19 AI / ML-air interface WID general framework (e.g. LCM, performance monitoring etc) [RAN2]

[0257] - This would only be treated after sufficient progress is made in the Rel-19 AI / ML air interface WID

[0258] 1> Potential specification impacts of AI / ML aided mobility [RAN2]

[0259] 1> Evaluate testability, interoperability, and impacts on RRM requirements and performance

[0260] - RAN1 / 3 work can be triggered via LS

[0261] - RAN4 scope / work can be defined and confirmed by RAN#105 after some RAN2 discussions (within the RAN4 pre-allocated TUs)

[0262] - To avoid duplicate study with "AI / ML for NG-RAN" led by RAN3

[0263] - Two-sided model is not included

[0264] The functional AI / ML framework studied in the Release-18 TR 38.843 on AI / ML for NR air interface is the baseline for the AI / ML for inter-cell mobility. In addition to studying how AI / ML can be applied to optimize inter-cell mobility procedures, the Release-19 AI / ML for air interface (Mobility) study item should also identify any changes and extensions that are required in the functional AI / ML framework.

[0265] Proposal 1: The study item should investigate how the AI / ML air interface functional framework devised in Release-18 TR 38.843 can be extended for the mobility use cases.

[0266] The NR specifications support the following handover mechanisms.

[0267] - Rel-15: Basic Handover

[0268] - Rel-16: CHO (Conditional Handover)

[0269] - Rel-18: LTM (L1 / L2-Triggered Mobility)

[0270] In our view in this study, we could focus on Rel-15 basic handover and Rel-18 LTM mobility to reduce the study scope.

[0271] The baseline connected mode mobility methods have been extensively studied and optimized. Applying AI / ML methods has the potential to further improve and optimize the connected mode performance in new applications and in problematic scenarios, as well as in reducing the amount of radio measurements and reporting that are required. In addition, mobility-related resource allocation in the network can be optimized.

[0272] The potential of machine learning driven solutions is in the ability to learn the specific mobility context, which enables tailored mobility solutions. For example, the mobility procedures may be optimized for each cell boundary and / or UE type (fast or slow moving etc.), or even for each individual handover. Aligned with the potential study scope summarized in we see that it would be beneficial to study the following ML optimization use cases for connected mode mobility:

[0273] - Handover optimization and target prediction

[0274] > Extension of beam prediction concepts to inter-cell mobility

[0275] > ML-based optimization of handover parameters

[0276] - RRM measurement and event prediction

[0277] > Prediction of mobility-related events

[0278] > Inter-cell mobility measurement reduction

[0279] Network and / or UE-sided

[0280] Inference in the network or in the UE are to be studied for mobility ML use cases. In Rel-19, the UEs are expected to follow the baseline handover and existing events but can provide predicted events or other additional information based on ML and for ML features in the network.

[0281] The potential of ML in mobility use cases is in enabling learning the local radio environment and mobility patterns, which in turn enables optimizing the mobility procedures for each situation. Therefore, the ML models in mobility use cases may often be cell-, site-, or area-specific, or otherwise localized to covering only a specific scope. For cell-, site- or area-specific mobility ML models, inference in the network may be preferable since inference in the UE can pose challenges to the ML Life-Cycle Management (LCM). For example, in UE deployments model switching may be required when the UE is moving and this may require network assistance.

[0282] Observation 1: The potential of ML in mobility use cases is to enable learning the local radio environment and mobility patterns, which may often require cell / site / area-specific ML models.

[0283] Observation 2: For cell-, site- or area-specific mobility ML models, inference in the network may be preferable.

[0284] Data sources in both the UE and the network may be used in mobility use cases. For example, the UE takes the radio measurements and the network has data related to the handover preparation. When analysing either network or UE sided inference for a mobility use case, the location of the data sources and the signalling impacts need to be studied and considered.

[0285] Observation 3: When analysing either network or UE sided inference for a mobility use case, the location of the data sources and the signalling impacts need to be studied and considered.

[0286] Reliability and Scalability

[0287] Mobility methods need to be very reliable, even in case of unexpected circumstances. This includes any ML solutions used to optimize mobility, which must perform in a wide variety of scenarios. ML-driven mobility solutions need to be designed to be robust, resilient, and fail-safe. The solutions need to also scale to diverse network deployments.

[0288] Observation 4: ML-driven mobility solutions need to be designed to be robust, resilient, and fail-safe.

[0289] Observation 5: ML-driven mobility solutions need to be scalable to diverse network deployments.

[0290] The traditional handover decision for mobility is controlled by the network based on the measurement report from the UE. However, the measurement report causes high overhead and latency on the air interface.

[0291] The traditional mobility procedure lacks self-learning ability for handover decision, which may make an inappropriate decision on handover, e.g., inappropriate parameters, early / late / incorrect handover.

[0292] The traditional handover events have some drawbacks, the UE could handover to a new target cell but leave it in a short time even though the configured event is fulfilled, i.e., unnecessary handover or ping-pong issue could happen.

[0293] Objectives:

[0294] Study L3-based mobility enhancement with assistance of AI / ML, including

[0295] - Handover prediction / request based on AI / ML model, e.g., the UE predicts target cell and report / request to NW for handover decision.

[0296] - Temporal / spatial RRM measurement result prediction based on AI / ML model, e.g., the RS measurement results of future time instances can be predicted, using intra-frequency measurement results to predict inter-frequency measurement results;

[0297] - Temporal RLM measurement result prediction based on AI / ML model, e.g., the RLM-RS measurement results of future time instances can be predicted;

[0298] - Dynamic adjustment on handover parameters / events based on AI / ML model, e.g., adjustment on Hys, TTT;

[0299] Study the following scenarios based on LCM framework in Rel-18 for L3-based mobility enhancement

[0300] - AI / ML model is trained by network side and using the LCM procedure - model transfer to transfer the trained AI / ML model to the UE for its execution;

[0301] - AI / ML model is trained by UE side;

[0302] - Further model training (update) at peer side, e.g., When the UE receives the initial AI / ML model from the network, each UE may continue AI / ML model training.

[0303] Then eventually, different UE may run totally different AI / ML models for inference.

[0304] Study the benefit of AI / ML for L3-based mobility enhancement over NG-RAN AI / ML mobility enhancement

[0305] Hereinafter, technical features related to system information are described. Sections of 3GPP TS 38.331 v18.0.0 may be referred.

[0306] System Information (SI) is divided into the MIB and a number of SIBs and posSIBs where:

[0307] - the MIB is 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 acquire SIB1 from the cell. The first transmission of the MIB is scheduled in subframes, and repetitions are scheduled according to the period of SSB;

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

[0309] - the SIB1 is transmitted on the DL-SCH with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms. The default transmission repetition periodicity of SIB1 is 20 ms but the actual transmission repetition periodicity is up to network implementation. For SSB and CORESET multiplexing pattern 1, SIB1 repetition transmission period is 20 ms. For SSB and CORESET multiplexing pattern 2 / 3, SIB1 transmission repetition period is the same as the SSB period. SIB1 includes 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. SIB1 is cell-specific SIB;

[0310] - SIBs other than SIB1 and posSIBs are carried in SystemInformation (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 except SIB1 can be configured to be cell specific or area specific, using an indication in SIB1. 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;

[0311] - The mapping of SIBs to SI messages is configured in schedulingInfoList and schedulingInfoList2, while the mapping of posSIBs to SI messages is configured in posSchedulingInfoList and schedulingInfoList2.

[0312] Each SIB and each posSIB is mapped to a single SI message. posSIBs of the same posSibType carrying GNSS Generic Assistance Data for different GNSS / SBAS (identified by gnss-id / sbas-id) are mapped to different SI messages.

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

[0314] 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 particular sibType / posSibType in each SI message;

[0315] - For a UE in RRC_CONNECTED, the network can provide system information through dedicated signalling using the RRCReconfiguration message, 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.

[0316] - For PSCell and SCells, the network provides the required SI by dedicated signalling, i.e. within an RRCReconfiguration message. Nevertheless, the UE shall acquire MIB of 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.

[0317] NOTE 2: The physical layer imposes a limit to the maximum size a SIB can take. The maximum SIB1 or SI message size is 2976 bits.

[0318] FIG. 10 shows an example of system information acquisition.

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

[0320] The UE in RRC_IDLE and RRC_INACTIVE shall ensure having a valid version of (at least) the MIB, SIB1 through SIB4, 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), and SIB13, 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), SIB19 (if UE is accessing NR via NTN access) and SIB22 (for ATG access).

[0321] 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 of SIB20, regardless of the RRC state the UE is in.

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

[0323] SIB validity

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

[0325] When the UE acquires a MIB or a SIB1 or an SI message in a serving cell, and if the UE stores the acquired SIB, then the UE shall store the associated areaScope, if present, the first PLMN-Identity in the PLMN-IdentityInfoList for 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 the NPN-IdentityInfoList for NPN-only cells, the cellIdentity, the systemInformationAreaID, if present, and the valueTag, if present, as indicated in the si-SchedulingInfo for the SIB. If the UE stores the acquired posSIB, then the UE shall store the associated areaScope, if present, the cellIdentity, the systemInformationAreaID, if present, the valueTag, if provided in assistanceDataSIB-Element, and the expirationTime if provided in assistanceDataSIB-Element. The UE may use a valid stored version of the SI except MIB, SIB1, SIB6, SIB7 or SIB8 e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. The valueTag and expirationTime for posSIB is optionally provided in assistanceDataSIB-Element.

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

[0327] The UE shall:

[0328] 1> delete any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid;

[0329] 1> for each stored version of a SIB:

[0330] 2> if the areaScope is associated and its value for the stored version of the SIB is the same as the value received in the si-SchedulingInfo for that SIB from the serving cell:

[0331] 3> if the UE is NPN capable and the cell is an NPN-only cell:

[0332] 4> if the first NPN identity included in the NPN-IdentityInfoList, the systemInformationAreaID and the valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the NPN identity, the systemInformationAreaID and the valueTag associated with the stored version of that SIB:

[0333] 5> consider the stored SIB as valid for the cell;

[0334] 3> else if the first PLMN-Identity included in the PLMN-IdentityInfoList, the systemInformationAreaID and the valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the PLMN-Identity, the systemInformationAreaID and the valueTag associated with the stored version of that SIB:

[0335] 4> consider the stored SIB as valid for the cell;

[0336] 2> if the areaScope is not present for the stored version of the SIB and the areaScope value is not included in the si-SchedulingInfo for that SIB from the serving cell:

[0337] 3> if the UE is NPN capable and the cell is an NPN-only cell:

[0338] 4> if the first NPN identity in the NPN-IdentityInfoList, the cellIdentity and valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the NPN identity, the cellIdentity and the valueTag associated with the stored version of that SIB:

[0339] 5> consider the stored SIB as valid for the cell;

[0340] 3> else if the first PLMN-Identity in the PLMN-IdentityInfoList, the cellIdentity and valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the PLMN-Identity, the cellIdentity and the valueTag associated with the stored version of that SIB:

[0341] 4> consider the stored SIB as valid for the cell;

[0342] 1> for each stored version of a posSIB:

[0343] 2> if the areaScope is associated and its value for the stored version of the posSIB is the same as the value received in the posSIB-MappingInfo for that posSIB from the serving cell and the systemInformationAreaID included in the si-SchedulingInfo is identical to the systemInformationAreaID associated with the stored version of that posSIB:

[0344] 3> if the valueTag for the posSIB received from the serving cell is identical to the valueTag associated with the stored version of that posSIB; or if the expirationTime associated with the stored posSIB has not been expired:

[0345] 4> consider the stored posSIB as valid for the cell;

[0346] 2> if the areaScope is not present for the stored version of the posSIB and the areaScope value is not included in the posSIB-MappingInfo for that posSIB from the serving cell and the cellIdentity for the posSIB received from the serving cell is identical to the cellIdentity associated with the stored version of that posSIB:

[0347] 3> if the valueTag for the posSIB received from the serving cell is identical to the valueTag associated with the stored version of that posSIB; or if the expirationTime associated with the stored posSIB has not been expired:

[0348] 4> consider the stored posSIB as valid for the cell;

[0349] SI change indication and PWS notification

[0350] A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS, positioning assistance data, and some NTN-specific information as specified in the field descriptions ) is broadcasted in the modification period following the one where SI change indication is transmitted. The modification period boundaries are defined by SFN values for which SFN mod m = 0, where m is the number of radio frames comprising the modification period. The modification period is configured by system information. If H-SFN is provided in SIB1, and UE is configured with eDRX, modification period boundaries are defined by SFN values for which (H-SFN * 1024 + SFN) mod m = 0.

[0351] For UEs in RRC_IDLE or RRC_INACTIVE configured to use an IDLE eDRX cycle longer than the modification period, an eDRX acquisition period is defined. The boundaries of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod 1024 = 0.

[0352] The UE receives indications about SI modifications and / or PWS notifications using Short Message transmitted with P-RNTI over DCI. Repetitions of SI change indication may occur within preceding modification period or within preceding eDRX acquisition period. SI change indication is not applicable for SI messages containing posSIBs.

[0353] UEs in RRC_IDLE or in RRC_INACTIVE while SDT procedure is not ongoing shall monitor for SI change indication in its own paging occasion(s) that the UE monitors. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging.

[0354] UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for SI change indication in any paging occasion at least once per modification period, if the initial downlink BWP on which the SDT procedure is ongoing is associated with a CD-SSB.

[0355] During a modification period where ETWS or CMAS transmission is started or stopped, the SI messages carrying the posSIBs scheduled in posSchedulingInfoList may change, so the UE might not be able to successfully receive those posSIBs in the remainder of the current modification period and next modification period according to the scheduling information received prior to the change.

[0356] ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE while SDT procedure is not ongoing shall monitor for indications about PWS notification in its own paging occasion(s) that the UE monitors. ETWS or CMAS capable UEs in RRC_CONNECTED shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging.

[0357] ETWS or CMAS capable UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle, if the initial downlink BWP on which the SDT procedure is ongoing is associated with a CD-SSB.

[0358] For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging.

[0359] A L2 U2N Remote UE is not required to monitor paging occasion for SI modifications and / or PWS notifications. It obtains the updated system information and SIB6 / 7 / 8 from the connected L2 U2N Relay UE.

[0360] If the UE receives a Short Message, the UE shall:

[0361] 1> if the UE is ETWS capable or CMAS capable, the etwsAndCmasIndication bit of Short Message is set, and the UE is provided with searchSpaceSIB1 and searchSpaceOtherSystemInformation on the active BWP or the initial BWP:

[0362] 2> immediately re-acquire the SIB1;

[0363] 2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB6:

[0364] 3> acquire SIB6, immediately;

[0365] 2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB7:

[0366] 3> acquire SIB7, immediately;

[0367] 2> if the UE is CMAS capable and si-SchedulingInfo includes scheduling information for SIB8:

[0368] 3> acquire SIB8 immediately;

[0369] - In case SIB6, SIB7, or SIB8 overlap with a measurement gap it is left to UE implementation how to immediately acquire SIB6, SIB7, or SIB8.

[0370] 1> if the UE does not operate an IDLE eDRX cycle longer than the modification period and the systemInfoModification bit of Short Message is set:

[0371] 2> apply the SI acquisition procedure from the start of the next modification period;

[0372] 1> if the UE operates an IDLE eDRX cycle longer than the modification period and the systemInfoModification-eDRX bit of Short Message is set:

[0373] 2> apply the SI acquisition procedure from the start of the next eDRX acquisition period boundary.

[0374] Acquisition of an SI message

[0375] For SI message acquisition PDCCH monitoring occasion(s) are determined according to searchSpaceOtherSystemInformation. If searchSpaceOtherSystemInformation is set to zero, PDCCH monitoring occasions for SI message reception in SI-window are same as PDCCH monitoring occasions for SIB1. If searchSpaceOtherSystemInformation is not set to zero, PDCCH monitoring occasions for SI message are determined based on search space indicated by searchSpaceOtherSystemInformation. PDCCH monitoring occasions for SI message which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from one in the SI window. The [x*N+K]th PDCCH monitoring occasion (s) for SI message in SI-window corresponds to the Kth transmitted SSB, where x = 0, 1, .. X-1, K = 1, 2, .. N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoring occasions in SI-window / N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the SI window, PDCCH for an SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception SI messages is up to UE implementation.

[0376] Request for on demand system information

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

[0378] 1> if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL-MSG1-Repetition and criteria to select supplementary uplink is met and if criteria to apply MSG1 repetition for the concerned si-RequestConfigSUL-MSG1-Repetition is met:

[0379] 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in si-RequestConfigSUL-MSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

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

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

[0382] 1> else if the UE is a RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigRedCap-MSG1-Repetition and criteria to select normal uplink is met and if criteria to apply MSG1 repetition for the concerned si-RequestConfigRedCap-MSG1-Repetition is met:

[0383] 2> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in si-RequestConfigRedCap-MSG1-Repetition corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

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

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

[0386] 1> else if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink is met:

[0387] 2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

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

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

[0390] 1> else if the UE is an (e)RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigRedCap and criteria to select normal uplink is met:

[0391] 2> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigRedcap corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

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

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

[0394] 1> else:

[0395] 2> if the UE is not a RedCap UE and if SIB1 includes si-SchedulingInfo containing si-RequestConfigMSG1-Repetition and criteria to select normal uplink and to apply MSG1 repetition for the concerned si-RequestConfigMSG1-Repetition are met; or

[0396] 2> if the UE is a RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigMSG1-Repetition and criteria to select normal uplink and to apply MSG1 repetition for the concerned si-RequestConfigMSG1-Repetition are met:

[0397] 3> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) associated with the applicable MSG1 repetition number in corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

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

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

[0400] 2> else if the UE is neither a RedCap nor an eRedCap UE and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink is met; or

[0401] 2> if the UE is an (e)RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink is met:

[0402] 3> trigger the lower layer to initiate the Random Access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

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

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

[0405] 2> else:

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

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

[0408] 3> apply the timeAlignmentTimerCommon included in SIB1;

[0409] 3> apply the CCCH configuration;

[0410] 3> initiate transmission of the RRCSystemInfoRequest message with rrcSystemInfoRequest;

[0411] 3> if acknowledgement for RRCSystemInfoRequest message with rrcSystemInfoRequest is received from lower layers:

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

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

[0414] 2> reset MAC;

[0415] 2> if SI request is based on RRCSystemInfoRequest message with rrcSystemInfoRequest:

[0416] 3> release RLC entity for SRB0.

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

[0418] Meanwhile, applying AIML method in wireless communication has the potential improvement in optimized configuration, which can improve UE / NW performance and proactive resolution from problematic scenario. Also, the optimized configuration can be utilized for UE / NW energy saving through compact resource allocation and reducing of measurements and reports. For R19 AIML mobility SI, dynamic adjustment on handover parameters / events based on AI / ML model, for example, adjustment on Hys and TTT, has been proposed. In this use case, it considers the UEs in RRC_CONNECTED with dedicated signalling.

[0419] With extension of use cases, dynamic adjustment can also be utilized for UEs in RRC_IDLE and RRC_INACTIVE. For example, dynamic optimized adjustment can be applied for configuration of mobility (for example, cell reselection) and / or power saving (for example, RRM relaxation, RLM / BFD relaxation).

[0420] However, in the legacy mechanism, acquisition of new system information happens in a restricted static time point. Change of system information only occurs at specific radio frame based on modification period. For example, for the UEs except eDRX UEs, modification period boundary is determined by SFN mod m = 0, where m is the number of radio frames comprising the modification period configured.

[0421] UEs in RRC_IDLE or in RRC_INACTIVE should monitor for SI change indication in its own paging occasion(s). UEs in RRC_CONNECTED should monitor for SI change indication in any paging occasion at least once per modification period. When UE receives the SI change indication in the current modification period(N), it applies the system information acquisition procedure from the start of the next modification period(N+1).

[0422] FIG. 11 shows an example of a scenario for acquisition of a new SI.

[0423] For example, FIG. 11 illustrates an example of a procedure for acquiring system information based on a static period.

[0424] If the modification period is long, it takes a long time to apply the optimized adjustment, making it difficult to apply the effects of AIML on the UE and network.

[0425] On the other hand, if the modification period is always set to be short, frequent transmission / reception of system information is assumed, which places a burden on the UE / NW in terms of both signalling and power consumption, and mismatches between the UE / NW may occur in the settings. Therefore, a method is needed that ensures stable operation based on system information and allows optimized adjustments to be applied in a timely manner.

[0426] Thus, studies for receiving system information based on dynamic modification period are required.

[0427] Hereinafter, a method for receiving system information based on dynamic modification period, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

[0428] 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).

[0429] FIG. 12 shows an example of a method for receiving system information based on dynamic modification period.

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

[0431] In step S1201, a wireless device may receive, from a network, information related to a first modification period.

[0432] For example, the information related to the first modification period may include a first length of the first modification period.

[0433] For example, the first length of the first modification period may be configured as a multiple of a default paging cycle.

[0434] In step S1202, a wireless device may acquire a first system information message based on the first modification period.

[0435] For example, the wireless device may detect a system information modification message in a current modification period.

[0436] For example, the first system information message may be acquired from a start of a next modification period based on the first modification period. That is, the wireless device may acquire the first system information from the start of the next modification period based on the first length of the first modification period.

[0437] For example, the information related to the first modification period may be included in a Radio Resource Control (RRC) message, a System Information Block Type 1 (SIB1), a Downlink Control Information (DCI), and / or a Medium Access Control (MAC) Control Element (CE).

[0438] In step S1203, the wireless device may receive, from the network, a system information modification indication including information related to a second modification period.

[0439] For example, the wireless device may receive the system information modification indication based on a paging occasion.

[0440] For example, the second modification period may be different from the first modification period.

[0441] For example, the wireless device may apply the second modification period upon receiving the system information modification indication.

[0442] For example, the information related to the second modification period may include a second length of the first modification period.

[0443] For example, the second length of the second modification period may be configured as a multiple of a default paging cycle.

[0444] For example, the system information modification indication may be included in an RRC message, a SIB1, a DCI, and / or a MAC CE.

[0445] For example, the information related to the second modification period may be included in an RRC message, a SIB1, a DCI, and / or a MAC CE.

[0446] In step S1204, the wireless device may acquire a second system information message based on the second modification period.

[0447] For example, the system information modification message may be received in a current modification period, in step S1203. The second system information message may be acquired from a start of a next modification period based on the second modification period.

[0448] For example, the wireless device may receive the system information modification message in a current modification period, and acquire the second system information message from the start of the next modification period, based on the second length of the second modification period.

[0449] According to some embodiments of the present disclosure, the wireless device may apply the second modification period only for acquiring the second system information message. The wireless device may apply the first modification period after acquiring the second system information message.

[0450] In other words, the wireless device may use the second modification period only for receiving the second system information message.

[0451] According to some embodiments of the present disclosure, the wireless device may maintain the second modification period after acquiring the second system information message. For example, the wireless device may change the modification period from the first modification period to the second modification period upon receiving the system information modification indication including the information related to the second modification period. The wireless device may use the second modification period even after receiving the second system information message.

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

[0453] Hereinafter, some embodiments of a method for acquisition of system information based on dynamic modification period information.

[0454] For example, the present disclosure provides a method of acquisition of new system information based on dynamic modification period. NW may configure new (dynamic) modification period with system information modification indication. UEs in RRC_IDLE or RRC_INACTIVE may detect new modification period during its own PO.

[0455] Instead of following a static modification period configured in SIB1, UE can acquire new system information according to dynamic modification period.

[0456] FIG. 13 shows an example of a method for acquisition of system information based on dynamic modification period information.

[0457] In particular, FIG. 13 shows an example of a method performed by a user equipment (UE) and a network (NW) in a wireless communication system.

[0458] In step S1301, NW configures a first length of modification period.

[0459] In step S1302, UE acquires system information message(s) applying the first length of modification period.

[0460] In step S1303, NW sets system information modification bit with a second length of modification period.

[0461] In step S1304, UE acquires system information message(s) applying the second length of modification period.

[0462] Regarding step S1301,

[0463] 1> NW may configure a first length of modification period

[0464] 2> The first length of modification period may be configured via RRC message, e.g., SIB1, DCI or MAC CE

[0465] 2> The first length of modification period may set as a multiple of paging cycle, e.g., n2, where n is default paging cycle

[0466] Regarding step S1302,

[0467] 1> UE may acquire system information message(s) applying the first length of modification period

[0468] 2> UE may detect system information modification indication in a current modification period(N)

[0469] 3> UE may acquire the (concerned) system information message(s) from a start of the next modification period(N+1) based on the first modification period

[0470] 4> If the first length of modification period is configured as a multiple of paging cycle, the start of the next modification period(N+1) may be the nearest upcoming radio frame / slot / symbol of paging cycle(n) x first length of modification period(m) x l in time domain, where l = 0, 1, 2, ..;

[0471] Regarding step S1303,

[0472] 1> NW may set a second length of modification period with system information modification indication in current modification period(N+1)

[0473] 2> The second length of modification period may be configured via RRC message, e.g., SIB1, DCI or MAC CE

[0474] 2> Configuration related to Length of modification period

[0475] 3> The second length of modification period may set as multiples of paging cycle, e.g., n2, where n is default paging cycle

[0476] 3> The second length of modification period may set a specific length of time duration with units of radio frame, slot, or symbol

[0477] 3> The second length of modification period may set as a specific entry among the entries pre-configured, where the pre-configuration may include the length of modification period and / or start point related configuration of the next MP

[0478] 2> Configuration related to start point of the next MP

[0479] 3> The second length of modification period may include a start point information, for example, a specific number of radio frame, slot, or symbol

[0480] 3> The second length of modification period may include start point only, i.e., without length of modification period information

[0481] 2> UE may consider that the system information has been changed, and may apply the second length of modification period

[0482] 1> NW may set a second length of modification period without a system information modification indication in current modification period(N+1)

[0483] 2> UE may consider that the system information has been changed and may apply the second length of modification; or

[0484] 2> UE may apply the second length of modification only

[0485] Regarding step S1304,

[0486] 1> If UE considers that the system information has been changed, UE acquires system information message(s) applying the second length of modification period

[0487] 2> UE may acquire the (concerned) system information message(s) from a start of the next modification period(N+2) based on the second modification period

[0488] 3> If the second length of modification period is configured as a multiple of paging cycle, the start of the next modification period(N+2) may be:

[0489] 4> the nearest upcoming point of paging cycle(n) x the second length of modification period(m) x l, where m, l = 0, 1, 2, ..; or

[0490] 4> the point of the latest start of modification period + paging cycle(n) x the second length of modification period(m), where m = 0, 1, 2, ..;

[0491] 3> If the second length of modification period is configured to a specific length of time during, the start of the next modification period(N+2) may be:

[0492] 4> the nearest upcoming point of the specific length of time duration x l, where l = 0, 1,2,..; or

[0493] 4> the point of the latest start of modification period + the specific length of time duration

[0494] 3> If the second length of modification period consists of the starting number of a radio frame, slot or symbol, the start of the next modification period (N+2) can be the point indicated by the starting number

[0495] 4> If the starting number is configured only without second(new) length of modification period, UE may maintain the first length of modification period, and may apply only the starting number as a start point of the next modification period

[0496] 3> If the second length of modification period may set as a specific entry, UE apply the corresponding length of modification period and / or start point of the next modification period.

[0497] FIG. 14 shows an example for acquisition of system information based on dynamic modification period information.

[0498] In particular, FIG. 14 illustrates an example of reduced length of modification period compared to the procedure as shown in FIG. 11.

[0499] 1> The UE may apply the second length of modification period only once or maintain it until a new modification period is received.

[0500] 2> If UE receives the new length of modification period during acquisition of new SI procedure, UE may apply the new length of modification period; or

[0501] 2> If UE does not receive the new length of modification period during acquisition of new SI procedure, (i) UE may apply the second length of modification period only once, i.e., from the modification period N+2, UE may re-apply the first length of modification period as shown in Figure 3; or (ii) UE may maintain the second length of modification period as shown in Figure 4;

[0502] FIG. 15 shows an example for acquisition of system information based on dynamic modification period information.

[0503] In particular, FIG. 15 illustrates an example for applying new length of modification period only once.

[0504] FIG. 16 shows an example for acquisition of system information based on dynamic modification period information.

[0505] In particular, FIG. 16 illustrates an example for maintaining new length of modification period.

[0506] FIG. 17 shows an example of a method for acquisition of system information based on dynamic modification period information.

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

[0508] In step S1701, the wireless device may receive a first length of modification period.

[0509] In step S1702, the wireless device may acquire system information message(s) applying the first length of modification period.

[0510] In step S1703, the wireless device may receive an indication indicating the system information change and a second length of modification period.

[0511] In step S1704, the wireless device may acquire system information message(s) applying the second length of modification period.

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

[0513] Hereinafter, an apparatus for receiving system information based on dynamic modification period, 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, and 5.

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

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

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

[0517] The processor 102 may be adapted to perform operations.

[0518] The operations comprise: receiving, from a network, information related to a first modification period; acquisitioning a first system information message based on the first modification period; receiving, from the network, a system information modification indication including information related to a second modification period; and acquisitioning a second system information message based on the second modification period.

[0519] For example, the second modification period is different from the first modification period.

[0520] For example, the operations further comprises: detecting a system information modification message in a current modification period, wherein the first system information message is acquired from a start of a next modification period based on the first modification period.

[0521] For example, the operations further comprises: applying the second modification period upon receiving the system information modification indication.

[0522] For example, the system information modification message is received in a current modification period; and the second system information message is acquired from a start of a next modification period based on the second modification period.

[0523] For example, the information related to the first modification period includes a first length of the first modification period.

[0524] For example, the first length of the first modification period is configured as a multiple of a default paging cycle.

[0525] For example, the information related to the first modification period is included in a Radio Resource Control (RRC) message, a System Information Block Type 1 (SIB1), a Downlink Control Information (DCI), and / or a Medium Access Control (MAC) Control Element (CE).

[0526] For example, the information related to the second modification period includes a second length of the first modification period.

[0527] For example, the second length of the second modification period is configured as a multiple of a default paging cycle.

[0528] For example, the system information modification indication is included in an RRC message, a SIB1, a DCI, and / or a MAC CE.

[0529] For example, the operations further comprises: applying the second modification period only for acquiring the second system information message; and applying the first modification period after acquiring the second system information message.

[0530] For example, the operations further comprises: maintaining the second modification period after acquiring the second system information message.

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

[0532] Hereinafter, a processor for a wireless device for receiving system information based on dynamic modification period, according to some embodiments of the present disclosure, will be described.

[0533] The processor may be configured to control the wireless device to perform operations.

[0534] The operations comprise: receiving, from a network, information related to a first modification period; acquisitioning a first system information message based on the first modification period; receiving, from the network, a system information modification indication including information related to a second modification period; and acquisitioning a second system information message based on the second modification period.

[0535] For example, the second modification period is different from the first modification period.

[0536] For example, the operations further comprises: detecting a system information modification message in a current modification period, wherein the first system information message is acquired from a start of a next modification period based on the first modification period.

[0537] For example, the operations further comprises: applying the second modification period upon receiving the system information modification indication.

[0538] For example, the system information modification message is received in a current modification period; and the second system information message is acquired from a start of a next modification period based on the second modification period.

[0539] For example, the information related to the first modification period includes a first length of the first modification period.

[0540] For example, the first length of the first modification period is configured as a multiple of a default paging cycle.

[0541] For example, the information related to the first modification period is included in a Radio Resource Control (RRC) message, a System Information Block Type 1 (SIB1), a Downlink Control Information (DCI), and / or a Medium Access Control (MAC) Control Element (CE).

[0542] For example, the information related to the second modification period includes a second length of the first modification period.

[0543] For example, the second length of the second modification period is configured as a multiple of a default paging cycle.

[0544] For example, the system information modification indication is included in an RRC message, a SIB1, a DCI, and / or a MAC CE.

[0545] For example, the operations further comprises: applying the second modification period only for acquiring the second system information message; and applying the first modification period after acquiring the second system information message.

[0546] For example, the operations further comprises: maintaining the second modification period after acquiring the second system information message.

[0547] For example, the processor may be configured 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.

[0548] Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for receiving system information based on dynamic modification period, according to some embodiments of the present disclosure, will be described.

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

[0550] 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 other example, the processor and the storage medium may reside as discrete components.

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

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

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

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

[0555] The stored plurality of instructions may cause the wireless device to perform operations.

[0556] The operations comprise: receiving, from a network, information related to a first modification period; acquisitioning a first system information message based on the first modification period; receiving, from the network, a system information modification indication including information related to a second modification period; and acquisitioning a second system information message based on the second modification period.

[0557] For example, the second modification period is different from the first modification period.

[0558] For example, the operations further comprises: detecting a system information modification message in a current modification period, wherein the first system information message is acquired from a start of a next modification period based on the first modification period.

[0559] For example, the operations further comprises: applying the second modification period upon receiving the system information modification indication.

[0560] For example, the system information modification message is received in a current modification period; and the second system information message is acquired from a start of a next modification period based on the second modification period.

[0561] For example, the information related to the first modification period includes a first length of the first modification period.

[0562] For example, the first length of the first modification period is configured as a multiple of a default paging cycle.

[0563] For example, the information related to the first modification period is included in a Radio Resource Control (RRC) message, a System Information Block Type 1 (SIB1), a Downlink Control Information (DCI), and / or a Medium Access Control (MAC) Control Element (CE).

[0564] For example, the information related to the second modification period includes a second length of the first modification period.

[0565] For example, the second length of the second modification period is configured as a multiple of a default paging cycle.

[0566] For example, the system information modification indication is included in an RRC message, a SIB1, a DCI, and / or a MAC CE.

[0567] For example, the operations further comprises: applying the second modification period only for acquiring the second system information message; and applying the first modification period after acquiring the second system information message.

[0568] For example, the operations further comprises: maintaining the second modification period after acquiring the second system information message.

[0569] According to some embodiments of the present disclosure, the stored 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.

[0570] Hereinafter, a method performed by a base station (BS) for receiving system information based on dynamic modification period, according to some embodiments of the present disclosure, will be described.

[0571] The BS may transmit, to a wireless device, information related to a first modification period. The wireless device acquires a first system information message based on the first modification period. The BS may transmit, to the wireless device, a system information modification indication including information related to a second modification period. The wireless device acquires a second system information message based on the second modification period.

[0572] Hereinafter, a base station (BS) for receiving system information based on dynamic modification period, according to some embodiments of the present disclosure, will be described.

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

[0574] The processor may be configured to control the transceiver to transmit, to a wireless device, information related to a first modification period. The wireless device acquires a first system information message based on the first modification period. The processor may be configured to control the transceiver to transmit, to the wireless device, a system information modification indication including information related to a second modification period. The wireless device acquires a second system information message based on the second modification period.

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

[0576] According to some embodiments of the present disclosure, a wireless device could efficiently receive system information based on dynamic modification period.

[0577] For example, by applying optimized system information dynamically, if necessary, NW can allow optimized adjustments to be applied in a timely manner. Through the dynamic optimized configuration using AIML mechanism, performance such as mobility (for example, cell reselection), power saving (for example, through RRM relaxation, RLM / BFD relaxation, SSB / CSI-RS measurement) can be improved quickly.

[0578] For example, by dynamically changing the modification period, the wireless device could save resources.

[0579] According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for receiving system information based on dynamic modification period.

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

[0581] 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 from a network, information related to a first modification period;acquisitioning, by the wireless device, a first system information message based on the first modification period;receiving, by the wireless device from the network, a system information modification indication including information related to a second modification period; andacquisitioning, by the wireless device, a second system information message based on the second modification period.2.The method of claim 1,wherein the second modification period is different from the first modification period.3.The method of claim 1, wherein the method further comprising:detecting, by the wireless device, a system information modification message in a current modification period,wherein the first system information message is acquired from a start of a next modification period based on the first modification period.4.The method of claim 1, wherein the method further comprising:applying, by the wireless device, the second modification period upon receiving the system information modification indication.5.The method of claim 1,wherein the system information modification message is received in a current modification period; andwherein the second system information message is acquired from a start of a next modification period based on the second modification period.6.The method of claim 1,wherein the information related to the first modification period includes a first length of the first modification period.7.The method of claim 6,wherein the first length of the first modification period is configured as a multiple of a default paging cycle.8.The method of claim 1,wherein the information related to the first modification period is included in a Radio Resource Control (RRC) message, a System Information Block Type 1 (SIB1), a Downlink Control Information (DCI), and / or a Medium Access Control (MAC) Control Element (CE).9.The method of claim 1,wherein the information related to the second modification period includes a second length of the first modification period.10.The method of claim 9,wherein the second length of the second modification period is configured as a multiple of a default paging cycle.11.The method of claim 1,wherein the system information modification indication is included in an RRC message, a SIB1, a DCI, and / or a MAC CE.12.The method of claim 1, wherein the method further comprising:applying, by the wireless device, the second modification period only for acquiring the second system information message; andapplying, by the wireless device, the first modification period after acquiring the second system information message.13.The method of claim 1, wherein the method further comprising:maintaining, by the wireless device, the second modification period after acquiring the second system information message.14.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.15.A wireless device, comprising:a transceiver;a memory; andat least one processor operatively coupled to the transceiver and the memory, and adapted to perform operations, the operations comprising:receiving, from a network, information related to a first modification period;acquisitioning a first system information message based on the first modification period;receiving, from the network, a system information modification indication including information related to a second modification period; andacquisitioning a second system information message based on the second modification period.16.The wireless device of claim 15,wherein the second modification period is different from the first modification period.17.The wireless device of claim 15, wherein the operations further comprising:detecting a system information modification message in a current modification period,wherein the first system information message is acquired from a start of a next modification period based on the first modification period.18.The wireless device of claim 15, wherein the operations further comprising:applying the second modification period upon receiving the system information modification indication.19.The wireless device of claim 15,wherein the system information modification message is received in a current modification period; andwherein the second system information message is acquired from a start of a next modification period based on the second modification period.20.The wireless device of claim 15,wherein the information related to the first modification period includes a first length of the first modification period.21.The wireless device of claim 20,wherein the first length of the first modification period is configured as a multiple of a default paging cycle.22.The wireless device of claim 15,wherein the information related to the first modification period is included in a Radio Resource Control (RRC) message, a System Information Block Type 1 (SIB1), a Downlink Control Information (DCI), and / or a Medium Access Control (MAC) Control Element (CE).23.The wireless device of claim 15,wherein the information related to the second modification period includes a second length of the first modification period.24.The wireless device of claim 23,wherein the second length of the second modification period is configured as a multiple of a default paging cycle.25.The wireless device of claim 15,wherein the system information modification indication is included in an RRC message, a SIB1, a DCI, and / or a MAC CE.26.The wireless device of claim 15, wherein the operations further comprising:applying the second modification period only for acquiring the second system information message; andapplying the first modification period after acquiring the second system information message.27.The wireless device of claim 15, wherein the operations further comprising:maintaining the second modification period after acquiring the second system information message.28.The wireless device of claim 15,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.29.A processor for a wireless device in a wireless communication system, wherein the processor is configured to control the wireless device to perform operations comprising:receiving, from a network, information related to a first modification period;acquisitioning a first system information message based on the first modification period;receiving, from the network, a system information modification indication including information related to a second modification period; andacquisitioning a second system information message based on the second modification period.30.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, from a network, information related to a first modification period;acquisitioning a first system information message based on the first modification period;receiving, from the network, a system information modification indication including information related to a second modification period; andacquisitioning a second system information message based on the second modification period.31.A method, comprising,transmitting, by a base station to a wireless device, information related to a first modification period,wherein the wireless device acquires a first system information message based on the first modification period; andtransmitting, by the base station to the wireless device, a system information modification indication including information related to a second modification period,wherein the wireless device acquires a second system information message based on the second modification period.32.A base station in a wireless communication system comprising:a transceiver;a memory; anda processor operatively coupled to the transceiver and the memory, and adapted to:transmit, to a wireless device, information related to a first modification period,wherein the wireless device acquires a first system information message based on the first modification period; andtransmit, to the wireless device, a system information modification indication including information related to a second modification period,wherein the wireless device acquires a second system information message based on the second modification period.

Images