WO2022149936A1

WO2022149936A1 - Method and apparatus for acquiring network slice configuration in a wireless communication system

Info

Publication number: WO2022149936A1
Application number: PCT/KR2022/000396
Authority: WO
Inventors: Hyunjung CHOE; Sunghoon Jung
Original assignee: Lg Electronics Inc.
Priority date: 2021-01-11
Filing date: 2022-01-10
Publication date: 2022-07-14
Also published as: EP4275399A1; KR20230130662A

Abstract

A method and apparatus for acquiring network slice configuration in a wireless communication system is provided. A wireless device receives, from a cell in a tracking area, an encoded network slice configuration via system information. A wireless device determines that decoding information for the encoded network slice configuration is not obtained. A wireless device transmits, to a network, a UE configuration update request message for the decoding information. A wireless device receives, from the network, a UE configuration update response message including the decoding information. A wireless device performs mobility based on the encoded network slice configuration by using the decoding information.

Description

METHOD AND APPARATUS FOR ACQUIRING NETWORK SLICE CONFIGURATION IN A WIRELESS COMMUNICATION SYSTEM

The present disclosure relates to a method and apparatus for acquiring network slice configuration in a wireless communication system.

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.

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.

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.

In NR, a radio frequency may be associated with a particular network slice. A particular service associated with the particular network slice may be provided via the associated radio frequency.

For slice aware cell selection, slice related information (for example, slice related cell (re-)selection information) may need to be broadcast. However, many network operators have concerns about broadcasting their network slice information. One optional solution to solve network operators' concerns is broadcasting slice related information in a secured manner (that is, ciphered manner) and delivering the decoding rule (that is, key) in a dedicated signalling after security activation. For example, in case of broadcasting positioning SIBs (posSIBs), posSIBs may be broadcast in cipher and the key for decoding the posSIBs may be broadcast in Registration Accept message.

However, one drawback for applying this mechanism to deliver slice related cell (re-)selection information is that the slice related cell (re-)selection information cannot be used until the key is delivered via NAS signalling in RRC_CONNECTED, while cell (re-)selection needs to be quickly completed in RRC_IDLE/RRC_INACTIVE.

Therefore, studies for acquiring network slice configuration in a wireless communication system are required.

In an aspect, a method performed by a wireless device in a wireless communication system is provided. A wireless device receives, from a cell in a tracking area, an encoded network slice configuration via system information. A wireless device determines that decoding information for the encoded network slice configuration is not obtained. A wireless device transmits, to a network, a UE configuration update request message for the decoding information. A wireless device receives, from the network, a UE configuration update response message including the decoding information. A wireless device performs mobility based on the encoded network slice configuration by using the decoding information.

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

The present disclosure can have various advantageous effects.

According to some embodiments of the present disclosure, a wireless device could efficiently acquire network slice information.

For example, by proactively requesting network update, a wireless device could provide service continuity or reduce delay to provide services.

For example, a wireless device could by proactively request network update after idle-mode mobility. Therefore, the wireless device could be able to find the best cell for service continuity using the updated slice configuration.

In other words, a wireless device could reduce mobility delay, by directly requesting decoding information (for example, key or mapping information) of the network slice configuration used in the mobility.

According to some embodiments of the present disclosure, a wireless communication system could efficiently provide the network slice information in a ciphered manner.

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.

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

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

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

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

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

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.

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

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

FIG. 10 shows an example of AMF selection to which implementations of the present disclosure is applied.

FIG. 11 shows an example scenario for explaining some embodiments of the present disclosure.

FIG. 12 shows an example of a method for acquiring network slice configuration in a wireless communication system, according to some embodiments of the present disclosure.

FIG. 13 shows an example of a proactive method for cell (re-)selection using network configuration information, according to some embodiments of the present disclosure.

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.

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.

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.

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".

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".

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".

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".

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".

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

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.

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.

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.

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).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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 SNAPDRAGON^TM series of processors made by Qualcomm^®, EXYNOS^TM series of processors made by Samsung^®, A series of processors made by Apple^®, HELIO^TM series of processors made by MediaTek^®, ATOM^TM series of processors made by Intel^® or a corresponding next generation processor.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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.

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).

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.

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.

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.

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).

Referring to FIG. 8, downlink and uplink transmissions are organized into frames. Each frame has T_f = 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 T_sf per 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 = 2^u*15 kHz.

Table 1 shows the number of OFDM symbols per slot N^slot _symb, the number of slots per frame N^frame,u _slot, and the number of slots per subframe N^subframe,u _slot for the normal CP, according to the subcarrier spacing △f = 2^u*15 kHz.

Table 2 shows the number of OFDM symbols per slot N^slot _symb, the number of slots per frame N^frame,u _slot, and the number of slots per subframe N^subframe,u _slot for the extended CP, according to the subcarrier spacing △f = 2^u*15 kHz.

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 of N ^size,u _grid,x*N ^RB _sc subcarriers and N ^subframe,u _symb OFDM symbols is defined, starting at common resource block (CRB) N ^start,u _grid indicated by higher-layer signaling (e.g., RRC signaling), where N ^size,u _grid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. N ^RB _sc is the number of subcarriers per RB. In the 3GPP based wireless communication system, N ^RB _sc is 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth N ^size,u _grid for subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is 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 index k in the frequency domain and an index l representing 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.

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 configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides 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 to N ^size _BWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block n_PRB in the bandwidth part i and the common resource block n_CRB is as follows: n_PRB = n_CRB + N ^size _BWP,i, where N ^size _BWP,i is 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.

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).

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).

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.

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.

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.

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.

Mobility and periodic registration update initiation is described. Section 5.5.1.3.2 of 3GPP TS 24.501 v17.1.0 may be referred.

The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF,

a) when the UE detects entering a tracking area that is not in the list of tracking areas that the UE previously registered in the AMF;

b) when the periodic registration updating timer T3512 expires in 5GMM-IDLE mode;

c) when the UE receives a CONFIGURATION UPDATE COMMAND message indicating "registration requested" in the Registration requested bit of the Configuration update indication IE;

d) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE either receives a paging or the UE receives a NOTIFICATION message with access type indicating 3GPP access over the non-3GPP access for PDU sessions associated with 3GPP access;

e) upon inter-system change from S1 mode to N1 mode and if the UE previously had initiated an attach procedure or a tracking area updating procedure when in S1 mode;

f) when the UE receives an indication of "RRC Connection failure" from the lower layers and does not have signalling pending (i.e. when the lower layer requests NAS signalling connection recovery);

g) when the UE changes the 5GMM capability or the S1 UE network capability or both;

h) when the UE's usage setting changes;

i) when the UE needs to change the slice(s) it is currently registered to;

j) when the UE changes the UE specific DRX parameters;

k) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE receives a request from the upper layers to establish an emergency PDU session or perform emergency services fallback;

l) when the UE needs to register for SMS over NAS, indicate a change in the requirements to use SMS over NAS, or de-register from SMS over NAS;

m) when the UE needs to indicate PDU session status to the network after performing a local release of PDU session(s);

n) when the UE in 5GMM-IDLE mode changes the radio capability for NG-RAN or E-UTRAN;

o) when the UE receives a fallback indication from the lower layers and does not have signalling pending (i.e. when the lower layer requests NAS signalling connection recovery;

p) void;

q) when the UE needs to request new LADN information;

r) when the UE needs to request the use of MICO mode or needs to stop the use of MICO mode or to request the use of new T3324 value;

s) when the UE in 5GMM-CONNECTED mode with RRC inactive indication enters a cell in the current registration area belonging to an equivalent PLMN of the registered PLMN and not belonging to the registered PLMN;

t) when the UE receives over 3GPP access a SERVICE REJECT message or a DL NAS TRANSPORT message, with the 5GMM cause value set to #28 "Restricted service area";

u) when the UE needs to request the use of eDRX, when a change in the eDRX usage conditions at the UE requires different extended DRX parameters, or needs to stop the use of eDRX;

A change in the eDRX usage conditions at the UE can include e.g. a change in the UE configuration, a change in requirements from upper layers or the battery running low at the UE.

v) when the UE supporting 5G-SRVCC from NG-RAN to UTRAN changes the mobile station classmark 2 or the supported codecs;

w) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE decides to request new network slices after being rejected due to no allowed network slices requested;

x) when the UE is not in NB-N1 mode and the applicable UE radio capability ID for the current UE radio configuration changes due to a revocation of the network-assigned UE radio capability IDs by the serving PLMN or SNPN;

y) when the UE receives a REGISTRATION REJECT message with 5GMM cause values #3, #6 or #7 without integrity protection over another access;

z) when the UE needs to request new ciphering keys for ciphered broadcast assistance data;

za) when due to manual CAG selection the UE has selected a CAG-ID which is not included in the "allowed CAG list" for the selected PLMN or a CAG-ID in a PLMN for which the entry in the "CAG information list" does not exist or when the UE has selected, without selecting a CAG-ID, a PLMN for which the entry in the "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells";

zb) when the UE needs to start, stop or change the conditions for using the WUS assistance information;

zc) when the UE changes the UE specific DRX parameters in NB-N1 mode; or

zd) when the UE in 5GMM-CONNECTED mode with RRC inactive indication enters a new cell with different RAT in current TAI list or not in current TAI list.

ze) when the UE enters state 5GMM-REGISTERED.NORMAL-SERVICE over 3GPP access after the UE has sent a NOTIFICATION RESPONSE message over non-3GPP access in response to reception of a NOTIFICATION message over non-3GPP access.

For example, the REGISTRATION ACCEPT message is sent by the AMF to the UE.

For example, content of the REGISTRATION ACCEPT message may include a Ciphering key data as an Information Element.

This IE (that is, Ciphering key data) is included if the network needs to send ciphering key data to the UE for ciphered broadcast assistance data.

For example, the CONFIGURATION UPDATE COMMAND message is sent by the AMF to the UE.

Technical features related to network slicing is described. Section 16.3 of 3GPP TS 38.300 v16.4.0 may be referred.

General Principles and Requirements

The general principles and requirements related to the realization of network slicing in the NG-RAN for NR connected to 5GC and for E-UTRA connected to 5GC are given.

A network slice always consists of a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. Network can realise the different network slices by scheduling and also by providing different L1/L2 configurations.

Each network slice is uniquely identified by a S-NSSAI. NSSAI (Network Slice Selection Assistance Information) includes one or a list of S-NSSAIs (Single NSSAI) where a S-NSSAI is a combination of:

- mandatory SST (Slice/Service Type) field, which identifies the slice type and consists of 8 bits (with range is 0-255);

- optional SD (Slice Differentiator) field, which differentiates among Slices with same SST field and consist of 24 bits.

The list includes at most 8 S-NSSAI(s).

The UE provides NSSAI (Network Slice Selection Assistance Information) for network slice selection in RRCSetupComplete, if it has been provided by NAS. While the network can support large number of slices (hundreds), the UE need not support more than 8 slices simultaneously. A BL UE or a NB-IoT UE supports a maximum of 8 slices simultaneously.

Network Slicing is a concept to allow differentiated treatment depending on each customer requirements. With slicing, it is possible for Mobile Network Operators (MNO) to consider customers as belonging to different tenant types with each having different service requirements that govern in terms of what slice types each tenant is eligible to use based on Service Level Agreement (SLA) and subscriptions.

The following key principles apply for support of Network Slicing in NG-RAN:

RAN awareness of slices

- NG-RAN supports a differentiated handling of traffic for different network slices which have been pre-configured. How NG-RAN supports the slice enabling in terms of NG-RAN functions (i.e. the set of network functions that comprise each slice) is implementation dependent.

Selection of RAN part of the network slice

- NG-RAN supports the selection of the RAN part of the network slice, by NSSAI provided by the UE or the 5GC which unambiguously identifies one or more of the pre-configured network slices in the PLMN.

Resource management between slices

- NG-RAN supports policy enforcement between slices as per service level agreements. It should be possible for a single NG-RAN node to support multiple slices. The NG-RAN should be free to apply the best RRM policy for the SLA in place to each supported slice.

Support of QoS

- NG-RAN supports QoS differentiation within a slice.

RAN selection of CN entity

- For initial attach, the UE may provide NSSAI to support the selection of an AMF. If available, NG-RAN uses this information for routing the initial NAS to an AMF. If the NG-RAN is unable to select an AMF using this information or the UE does not provide any such information the NG-RAN sends the NAS signalling to one of the default AMFs.

- For subsequent accesses, the UE provides a Temp ID, which is assigned to the UE by the 5GC, to enable the NG-RAN to route the NAS message to the appropriate AMF as long as the Temp ID is valid (NG-RAN is aware of and can reach the AMF which is associated with the Temp ID). Otherwise, the methods for initial attach applies.

Resource isolation between slices

- The NG-RAN supports resource isolation between slices. NG-RAN resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources in one slice breaks the service level agreement for another slice. It should be possible to fully dedicate NG-RAN resources to a certain slice. How NG-RAN supports resource isolation is implementation dependent.

Access control

- By means of the unified access control (see clause 7.4), operator-defined access categories can be used to enable differentiated handling for different slices. NG-RAN may broadcast barring control information (i.e. a list of barring parameters associated with operator-defined access categories) to minimize the impact of congested slices.

Slice Availability

- Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.

- The NG-RAN and the 5GC are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend by factors such as support for the slice, availability of resources, support of the requested service by NG-RAN.

Support for UE associating with multiple network slices simultaneously

- In case a UE is associated with multiple slices simultaneously, only one signalling connection is maintained and for intra-frequency cell reselection, the UE always tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE camps.

Granularity of slice awareness

- Slice awareness in NG-RAN is introduced at PDU session level, by indicating the S-NSSAI corresponding to the PDU Session, in all signalling containing PDU session resource information.

Validation of the UE rights to access a network slice

- It is the responsibility of the 5GC to validate that the UE has the rights to access a network slice. Prior to receiving the Initial Context Setup Request message, the NG-RAN may be allowed to apply some provisional/local policies, based on awareness of which slice the UE is requesting access to. During the initial context setup, the NG-RAN is informed of the slice for which resources are being requested.

AMF and NW Slice Selection

- CN-RAN interaction and internal RAN aspects

NG-RAN selects AMF based on a Temp ID or NSSAI provided by the UE over RRC. The mechanisms used in the RRC protocol are described in the next clause.

Table 5 shows AMF selection based on Temp ID and NSSAI.

Radio Interface Aspects

When triggered by the upper layer, the UE conveys the NSSAI over RRC in the format explicitly indicated by the upper layer.

Resource Isolation and Management

Resource isolation enables specialized customization and avoids one slice affecting another slice.

Hardware/software resource isolation is up to implementation. Each slice may be assigned with either shared or dedicated radio resource up to RRM implementation and SLA.

To enable differentiated handling of traffic for network slices with different SLA:

- NG-RAN is configured with a set of different configurations for different network slices by OAM;

- To select the appropriate configuration for the traffic for each network slice, NG-RAN receives relevant information indicating which of the configurations applies for this specific network slice.

Signalling Aspects

In this clause, signalling flows related to the realization of network slicing in the NG-RAN are given.

AMF and NW Slice Selection

RAN selects the AMF based on a Temp ID or NSSAI provided by the UE.

In step S1001, gNB may transmit, to AMF1, an NG SETUP REQUEST message including list of S-NSSAI(s) supported per TA.

In step S1002, gNB may receive, from AMF1 and AMF2, an NG SETUP REQUEST including list of S-NSSAI(s) supported per PLMN.

In step S1003, gNB may transmit, to AMF2, an NG SETUP REQUEST message including list of S-NSSAI(s) supported per TA.

In step S1004, gNB may receive, from AMF2, an NG SETUP REQUEST including list of S-NSSAI(s) supported per PLMN.

In step S1005, gNB may receive, from UE, an RRC (Connection) Setup Complete message including Temp ID (optional) and NSSAI (optional).

In step S1006, gNB may identify slice policies, identify CN node supporting concerned slice(s), or select default CN node.

In step S1007, gNB may transmit, to AMF1, an INITIAL UE message.

In step S1008, gNB may validate UE rights and slice(s) availability.

In case a Temp ID is not available, the NG-RAN uses the NSSAI provided by the UE at RRC connection establishment to select the appropriate AMF (the information is provided after MSG3 of the random access procedure). If such information is also not available, the NG-RAN routes the UE to one of the configured default AMF(s).

The NG-RAN uses the list of supported S-NSSAI(s) previously received in the NG Setup Response message when selecting the AMF with the NSSAI. This list may be updated via the AMF Configuration Update message.

Technical features related to Acquisition of System Information is described. Section 5.2.2.3 of 3GPP TS 38.331 v16.3.1 may be referred.

Acquisition of an SI message

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 where the mapping between PDCCH monitoring occasions and SSBs is specified. 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 K^th 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.

Request for on demand positioning system information is described.

The UE shall:

1> if SIB1 includes posSI - SchedulingInfo containing posSI -RequestConfigSUL and criteria to select supplementary uplink:

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

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

3> acquire the requested SI message(s);

1> else if SIB1 includes posSI - SchedulingInfo containing posSI -RequestConfig and criteria to select normal uplink:

2> trigger the lower layer to initiate the random access procedure on normal uplink using the PRACH preamble(s) and PRACH resource(s) in posSI -RequestConfig corresponding to the SI message(s) that the UE upper layers require for positioning operations , and for which posSI - BroadcastStatus is set to notBroadcasting;

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

3> acquire the requested SI message(s) as defined in sub-clause 5.2.2.3.2, immediately;

1> else:

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

2> apply the default MAC Cell Group configuration as specified in 9.2.2;

2> apply the timeAlignmentTimerCommon included in SIB1;

2> apply the CCCH configuration;

2> initiate transmission of the RRCSystemInfoRequest message with rrcPosSystemInfoRequest;

2> if acknowledgement for RRCSystemInfoRequest message with rrcPosSystemInfoRequest is received from lower layers:

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

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

2> reset MAC;

2> if SI request is based on RRCSystemInfoRequest message with rrcPosSystemInfoRequest:

3> release RLC entity for SRB0.

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

Acquisition of SIB(s) or posSIB(s) in RRC_CONNECTED is described.

The UE shall:

1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB of one or several required SIB(s) or if requested by upper layers:

2> for the SI message(s) that, according to the si - SchedulingInfo or posSI-SchedulingInfo in the stored SIB1, contain at least one required SIB or requested posSIB:

3> if onDemandSIB -Request is configured and timer T350 is not running:

4> initiate transmission of the DedicatedSIBRequest message;

4> start timer T350 with the timer value set to the onDemandSIB -RequestProhibitTimer;

1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB of one or several required SIB(s) or if requested by upper layers:

2> for the SI message(s) that, according to the si - SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si -BroadcastStatus is set to broadcasting:

3> acquire the SI message(s);

2> for the SI message(s) that, according to the si - SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si -BroadcastStatus is set to notBroadcasting:

3> if onDemandSIB -Request is configured and timer T350 is not running:

4> initiate transmission of the DedicatedSIBRequest message;

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

2> for the SI message(s) that, according to the posSI - SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting:

3> acquire the SI message(s);

2> for the SI message(s) that, according to the posSI - SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to notBroadcasting:

3> if onDemandSIB -Request is configured and timer T350 is not running:

4> initiate transmission of the DedicatedSIBRequest message;

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

UE may include on demand request for SIB and/or posSIB(s) in the same DedicatedSIBRequest message.

For example, the IE SIBpos contains positioning assistance data.

For example, the IE SIBpos includes assistanceDataSIB-Element and lateNonCriticalExtension, etc. The assistanceDataSIB-Element is a parameter AssistanceDataSIBelement. The first/leftmost bit of the first octet contains the most significant bit.

Meanwhile, for slice aware cell selection, slice related information (for example, slice related cell (re-)selection information) may need to be broadcast. However, many network operators have concerns about broadcasting their network slice information. One optional solution to solve network operators' concerns is broadcasting slice related information in a secured manner (that is, ciphered manner) and delivering the decoding rule (that is, key) in a dedicated signalling after security activation. For example, in case of broadcasting positioning SIBs (posSIBs), posSIBs may be broadcast in cipher and the key for decoding the posSIBs may be broadcast in Registration Accept message.

Referring to FIG. 11, (1) a wireless device (that is, UE) receives available network slice information in cipher for cell selection via broadcast system information in Cell-1. Cell-1 belongs to a Registration Area-1.

(2) The UE receives a key to decode the ciphered network slice information via NAS signalling, where the key is available within the Registration Area-1.

(3) The UE successfully decodes and stores network slice information for cell selection.

(4) The UE performs cell selection and moves to Cell-2. Cell-2 belongs to a Registration Area-2.

(5) The UE receives available network slice information in cipher for cell selection via broadcast system information in Cell-2.

(6) The UE cannot decode the network slice information received in Cell-2, because the key to decode the ciphered network slice information received in Cell-2 is not yet received in Registration Area-2 via NAS signalling.

(7) The UE receives a key to decode the ciphered network slice information during Registration procedure in Registration Area-2.

(8) The UE successfully decodes and stores network slice information for cell selection.

In this example, when the UE stays in step (6) before the key is updated, the UE cannot use valid network slice information for cell selection. It may cause delay to acquire the valid network slice information.

Hereinafter, a method for acquiring network slice configuration in a wireless communication system, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

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).

In particular, FIG. 12 shows an example of a method performed by a wireless device.

In step S1201, a wireless device may receive, from a cell in a tracking area, an encoded network slice configuration via system information.

For example, the encoded network slice configuration may be ciphered by the network. In this case, the decoding information, in step S1202 below, may include a key for decoding the encoded network slice configuration ciphered by the network.

For example, the encoded network slice configuration may be encoded through a mapping table. In this case, the encoded network slice configuration includes at least one value related to at least one network slice configuration, wherein the at least one value included in the mapping table.

For example, the encoded network slice configuration may include information on (1) Slice/Service Type (SST), (2) Single Network Slice Selection Assistance Information (S-NSSAI), and/or (3) service identity. That is, the network slice configuration, acquired by decoding the encoded network slice configuration, may include information on (1) SST, (2) S-NSSAI, and/or (3) service identity.

In step S1202, a wireless device may determine that decoding information for the encoded network slice configuration is not obtained.

For example, the decoding information may include a key for decoding the encoded network slice configuration ciphered by the network.

For example, the decoding information may include the mapping table including information on one or more values mapped to one or more network slice configurations, which are available on the tracking area. For example, the mapping table may include mapping information between the one or more network slice configurations and one or more service types.

According to some embodiments of the present disclosure, a wireless device may move to the current tracking area from a previous tracking area. Upon moving to the current tracking area, the wireless device may check whether the decoding information is obtained or not. In this case, the tracking area is different from the previous tracking area.

For example, the wireless device may determine that the decoding information for the encoded network slice configuration is not obtained, based on that the tracking area is a new tracking area, where the wireless device has never been before.

According to some embodiments of the present disclosure, a wireless device may receive, from the cell of the tracking area, an area identity related to the encoded network slice configuration. A wireless device may identify the tracking area based on the area identity. For example, the wireless device may determine whether the tracking area is a new tracking area based on the received area identity.

In step S1203, a wireless device may transmit, to a network, a UE configuration update request message for the decoding information.

For example, upon determining that the decoding information for the encoded network slice configuration is not obtained, the wireless device may transmit, to a network, a UE configuration update request message for the decoding information.

For example, the wireless device may transmit, to the network, the UE configuration update request message via NAS signalling or RRC signalling after AS security activation.

For example, the UE configuration update request message may be an RRC signalling, which requests NAS signalling, from the network, for configuration update command.

For example, the wireless device may transmit, to the cell in the tracking area, the UE configuration update request message. For other example, the wireless device may transmit, to another cell in the tracking area, the UE configuration update request message.

For example, the UE configuration update request message may be a Registration Request message for a Registration procedure.

In step S1204, a wireless device may receive, from the network, a UE configuration update response message including the decoding information.

For example, the wireless device may receive the UE configuration update response message via a NAS signalling, an RRC signalling, or a MAC signalling.

For example, the wireless device may receive, from the cell in the tracking area, the UE configuration update response message. For example, the wireless device may receive, from another cell in the tracking area, the UE configuration update response message.

For example, the UE configuration update response message may be a Registration Response message.

In step S1205, a wireless device may perform mobility based on the encoded network slice configuration by using the decoding information.

For example, a wireless device may decode the encoded network slice configuration by using the key included in the decoding information. The wireless device may acquire a specific network slice configuration for the tracking area from the encoded network slice configuration. The wireless device may perform mobility by applying the specific network slice configuration.

For other example, a wireless device may select a specific network slice configuration among the one or more network slice configurations based on (1) the at least one value included in the encoded network slice configuration and (2) the mapping table. The wireless device may perform mobility by applying the selected specific network slice configuration.

For example, the wireless device may select or reselect the cell in the tracking area based on the network slice information acquired from the encoded network slice information. In other words, the wireless device may camp on the cell while in RRC_IDLE or RRC_INACTIVE.

For example, the wireless device may select or reselect another cell in the tracking area based on the network slice information acquired from the encoded network slice information. In other words, the wireless device may camp on another cell while in RRC_IDLE or RRC_INACTIVE.

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

Hereinafter, a proactive method for RRC_IDLE/RRC_INACTIVE mobility using network configuration information such as slice configuration, according to some embodiments of the present disclosure, will be described.

To implement a proactive solution for cell (re-)selection using network configuration information such as slice configuration, the present disclosure proposes an indication for proactive operation. That is, if the stored information for mobility (for example, cell (re-)selection) is invalid, the UE may transmit an indication to the network to proactively operate based on an updated network configuration and/or network controlled operation request.

For example, the indication transmitted by the UE may be to inform that the stored information for mobility is invalid and/or to request an updated network configuration or network command.

According to some embodiments of the present disclosure, the network configuration information for mobility may include parameters related to, for example, (1) slice aware UE operations such as SST, SD, (2) S-NSSAI, (3) traffic information, (4) frequency associated to slice, (5) cell identity associated to slice, (6) access category, (7) access identity, (8) PLMN identity, (9) non-public network identity, etc.

According to some embodiments of the present disclosure, the network configuration information may be ciphered or encoded using a mapping table (for example, in the mapping table, the encoded value '01100' maps to IOT service).

For example, if the network configuration information for mobility is ciphered, the UE may receive the key to decode the network configuration information via dedicated signalling after AS security activation.

For example, if the network configuration information for mobility is encoded using a mapping table, the UE may receive the mapping information for decoding the network configuration information via dedicated signalling after AS security activation.

According to some embodiments of the present disclosure, the network configuration may be preconfigured and/or transmitted to the UE via broadcast or dedicated signalling from the network.

In step S1301, the UE may receive cell access information and the scheduling of other system information via SIB1.

For example, the UE may receive network slice configuration (for example, sliceConfig) which indicates network slice(s) supported in the cell in SIB1.

For example, the contents of network slice configuration may include, for example, SST, S-NSSAI, or service identity.

For example, the UE may receive scheduling information (for example, SliceSI-SchedulingInfo) needed for acquisition of system information related to network slice.

For example, the UE may receive slice information area identity (for example, sliceInformationAreaID) to identify an area, which consists of one or several cells, where the network slice configuration is available.

For example, the UE may receive broadcast status (for example, sliceSI -BroadcastStatus is either broadcasting, notbroadcasting, dedicated) of system information related to network slice.

In step S1302, the UE may receive other system information related to corresponding network slice, if the network slice configuration in SIB1 includes any of configured network slice in the UE. Otherwise, the UE finds another cell.

In step S1303, the UE may send a dedicated SIB request message (that is, DedicatedSIBRequest) to the network according to the scheduling information for system information related to network slice.

For example, the UE may send a dedicated SIB request message if a broadcast status of system information related to network slice is configured by the network as not broadcasting (for example, sliceSI - BroadcastStatus is notBroadcasting).

In step S1304, the UE may acquire network slice configuration for mobility via system information and store the network slice configuration.

For example, the UE may receive the network slice configuration in cipher. The UE may be indicated that the network slice configuration is ciphered (that is, ciphered).

For example, the UE may receive the network slice configuration in an encoded manner (for example, an encoding value is mapped to S-NSSAI or SD). The UE may be indicated that the network slice configuration is encoded (that is, encoded).

For example, the network slice configuration may include network slice(s) supported in a neighbour cell.

For example, the network slice configuration may include detailed slice description for the serving cell.

For example, the UE may receive slice information area identity (that is, sliceInformationAreaID) to identify an area, which consists of one or several cells, where the network slice configuration is available.

In step S1305, the UE may determine that update of the network slice configuration is needed.

For example, the UE may determine the update of the network slice configuration is needed:

- if ciphered or encoded network slice configuration is stored but no key for decoding the network slice configuration is stored; and/or

- if decoding using a stored key fails; and/or

- if decoded values using a stored key is invalid; and/or

- if no service (that is, Configured S-NSSAI, Allowed S-NSSAI, service identity) is mapped to the network slice configuration; and/or

- if the UE is not within the area (that is, sliceInformationAreaID ) received in system information.

In step S1306, the UE may transmit a UE Configuration Update Request message to the network.

For example, the UE may transmit the UE Configuration Update Request message via NAS or RRC signalling after AS security activation.

For example, the UE Configuration Update Request message may be Registration Request message during Registration procedure.

For example, the UE Configuration Update Request message may be RRC signalling requesting Configuration Update Command NAS signalling from the network.

For example, the UE may indicate that network slice configuration received in system information is available (that is, RAN slicing configured).

For example, the UE may indicate that unknown slice configuration exists (that is, Unknown service configuration).

In step S1307, the UE may receive UE Configuration Update Response message from the network.

For example, the UE may receive the UE Configuration Update Response message via NAS or RRC or MAC signalling.

For example, the UE Configuration Update Response message may be Registration Response message.

For example, the UE may receive the key to decode the network slice configuration received in system information.

For example, the UE may receive a mapping rule for network slice configuration (for example, a specific value (for example, '01100') maps to a specific service (for example, 'IOT service')).

For example, the UE may receive slice configuration (for example, S-NSSAI).

In step S1308, the UE may perform mobility based on the stored network slice configuration.

For example, the UE may decode the stored network slice configuration by using the key and/or the mapping rule received in step S1307. The UE may perform mobility based on the decoded network slice configuration.

For example, the UE may decode the network slice configuration received in step S1307 by using the stored key and/or mapping rule. The UE may perform mobility based on the decoded network slice configuration.

Hereinafter, an apparatus for acquiring network slice configuration in a wireless communication system, 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.

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

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

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.

The processor 102 may be configured to control the transceiver 106 to receive, from a cell in a tracking area, an encoded network slice configuration via system information. The processor 102 may be configured to determine that decoding information for the encoded network slice configuration is not obtained. The processor 102 may be configured to control the transceiver 106 to transmit, to a network, a UE configuration update request message for the decoding information. The processor 102 may be configured to control the transceiver 106 to receive, from the network, a UE configuration update response message including the decoding information. The processor 102 may be configured to perform mobility based on the encoded network slice configuration by using the decoding information.

According to some embodiments of the present disclosure, the encoded network slice configuration may be ciphered by the network. The decoding information may include a key for decoding the encoded network slice configuration ciphered by the network.

For example, the processor 102 may be configured to decode the encoded network slice configuration by using the key. The processor 102 may be configured to acquire a specific network slice configuration for the tracking area from the encoded network slice configuration.

According to some embodiments of the present disclosure, the encoded network slice configuration may include at least one value related to at least one network slice configuration. The at least one value is included in a mapping table. The decoding information may include the mapping table including information on one or more values mapped to one or more network slice configurations, which are available on the tracking area. For example, the mapping table may include mapping information between the one or more network slice configurations and one or more service types.

For example, the processor 102 may be configured to select a specific network slice configuration among the one or more network slice configurations based on (1) the at least one value included in the encoded network slice configuration and (2) the mapping table.

According to some embodiments of the present disclosure, the processor 102 may be configured to move to the tracking area from a previous tracking area. The processor 102 may be configured to check whether the decoding information is obtained or not upon moving to the tracking area. The tracking area may be different from the previous tracking area.

For example, it may be determined that the decoding information for the encoded network slice configuration is not obtained, based on that the tracking area is a new tracking area for the wireless device.

According to some embodiments of the present disclosure, the processor 102 may be configured to control the transceiver 106 to receive, from the cell of the tracking area, an area identity related to the encoded network slice configuration. The processor 102 may be configured to identify the tracking area based on the area identity.

For example, the encoded network slice configuration may include information on (1) Slice/Service Type (SST), (2) Single Network Slice Selection Assistance Information (S-NSSAI), and/or (3) service identity.

For example, the UE configuration update request message may be a Registration Request message for a Registration procedure. For example, the UE configuration update response message may be a Registration Response message.

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

Hereinafter, a processor for a wireless device for acquiring network slice configuration in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The processor may be configured to control the wireless device to receive, from a cell in a tracking area, an encoded network slice configuration via system information. The processor may be configured to control the wireless device to determine that decoding information for the encoded network slice configuration is not obtained. The processor may be configured to control the wireless device to transmit, to a network, a UE configuration update request message for the decoding information. The processor may be configured to control the wireless device to receive, from the network, a UE configuration update response message including the decoding information. The processor may be configured to control the wireless device to perform mobility based on the encoded network slice configuration by using the decoding information.

For example, the processor may be configured to control the wireless device to decode the encoded network slice configuration by using the key. The processor may be configured to control the wireless device to acquire a specific network slice configuration for the tracking area from the encoded network slice configuration.

For example, the processor may be configured to control the wireless device to select a specific network slice configuration among the one or more network slice configurations based on (1) the at least one value included in the encoded network slice configuration and (2) the mapping table.

According to some embodiments of the present disclosure, the processor may be configured to control the wireless device to move to the tracking area from a previous tracking area. The processor may be configured to control the wireless device to check whether the decoding information is obtained or not upon moving to the tracking area. The tracking area may be different from the previous tracking area.

According to some embodiments of the present disclosure, the processor may be configured to control the wireless device to receive, from the cell of the tracking area, an area identity related to the encoded network slice configuration. The processor may be configured to control the wireless device to identify the tracking area based on the area identity.

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

Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for acquiring network slice configuration in a wireless communication system, according to some embodiments of the present disclosure, will be described.

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.

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.

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

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.

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.

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

The stored a plurality of instructions may cause the wireless device to receive, from a cell in a tracking area, an encoded network slice configuration via system information. The stored a plurality of instructions may cause the wireless device to determine that decoding information for the encoded network slice configuration is not obtained. The stored a plurality of instructions may cause the wireless device to transmit, to a network, a UE configuration update request message for the decoding information. The stored a plurality of instructions may cause the wireless device to receive, from the network, a UE configuration update response message including the decoding information. The stored a plurality of instructions may cause the wireless device to perform mobility based on the encoded network slice configuration by using the decoding information.

For example, the stored a plurality of instructions may cause the wireless device to decode the encoded network slice configuration by using the key. The stored a plurality of instructions may cause the wireless device to acquire a specific network slice configuration for the tracking area from the encoded network slice configuration.

For example, the stored a plurality of instructions may cause the wireless device to select a specific network slice configuration among the one or more network slice configurations based on (1) the at least one value included in the encoded network slice configuration and (2) the mapping table.

According to some embodiments of the present disclosure, the stored a plurality of instructions may cause the wireless device to move to the tracking area from a previous tracking area. The stored a plurality of instructions may cause the wireless device to check whether the decoding information is obtained or not upon moving to the tracking area. The tracking area may be different from the previous tracking area.

According to some embodiments of the present disclosure, the stored a plurality of instructions may cause the wireless device to receive, from the cell of the tracking area, an area identity related to the encoded network slice configuration. The stored a plurality of instructions may cause the wireless device to identify the tracking area based on the area identity.

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

Hereinafter, a method for providing network slice configuration performed by a base station (BS) in a wireless communication system, according to some embodiments of the present disclosure, will be described.

The BS may transmit, to a wireless device, an encoded network slice configuration via system information. The BS may receive, from the wireless device, a UE configuration update request message for the decoding information. The BS may transmit, to the wireless device, a UE configuration update response message including the decoding information.

Hereinafter, a base station (BS) for providing network slice configuration in a wireless communication system, according to some embodiments of the present disclosure, will be described.

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

The processor may be configured to control the transceiver to transmit, to a wireless device, an encoded network slice configuration via system information. The processor may be configured to control the transceiver to receive, from the wireless device, a UE configuration update request message for the decoding information. The processor may be configured to control the transceiver to transmit, to the wireless device, a UE configuration update response message including the decoding information.

The present disclosure can have various advantageous effects.

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

A method performed by a wireless device in a wireless communication system, the method comprising,

receiving, from a cell in a tracking area, an encoded network slice configuration via system information;

determining that decoding information for the encoded network slice configuration is not obtained;

transmitting, to a network, a UE configuration update request message for the decoding information;

receiving, from the network, a UE configuration update response message including the decoding information; and

performing mobility based on the encoded network slice configuration by using the decoding information.
The method of claim 1, wherein the encoded network slice configuration is ciphered by the network.
The method of claim 2, wherein the decoding information includes a key for decoding the encoded network slice configuration ciphered by the network.
The method of claim 3, wherein the method further comprises,

decoding the encoded network slice configuration by using the key; and

acquiring a specific network slice configuration for the tracking area from the encoded network slice configuration.
The method of claim 1, wherein the encoded network slice configuration includes at least one value related to at least one network slice configuration, wherein the at least one value is included in a mapping table.
The method of claim 5, wherein the decoding information includes the mapping table including information on one or more values mapped to one or more network slice configurations, which are available on the tracking area.
The method of claim 6, wherein the mapping table includes mapping information between the one or more network slice configurations and one or more service types.
The method of claim 6, wherein the method further comprises,

selecting a specific network slice configuration among the one or more network slice configurations based on (1) the at least one value included in the encoded network slice configuration and (2) the mapping table.
The method of claim 1, wherein the method further comprises,

moving to the tracking area from a previous tracking area; and

checking whether the decoding information is obtained or not upon moving to the tracking area,

wherein the tracking area is different from the previous tracking area.
The method of claim 9, wherein it is determined that the decoding information for the encoded network slice configuration is not obtained, based on that the tracking area is a new tracking area for the wireless device.
The method of claim 1, wherein the method further comprises,

receiving, from the cell of the tracking area, an area identity related to the encoded network slice configuration; and

identifying the tracking area based on the area identity.
The method of claim 1, wherein the encoded network slice configuration includes information on (1) Slice/Service Type (SST), (2) Single Network Slice Selection Assistance Information (S-NSSAI), and/or (3) service identity.
The method of claim 1, wherein the UE configuration update request message is a Registration Request message for a Registration procedure, and

wherein the UE configuration update response message is a Registration Response message.
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.
A wireless device in a wireless communication system comprising:

a transceiver;

a memory; and

at least one processor operatively coupled to the transceiver and the memory, and configured to:

control the transceiver to receive, from a cell in a tracking area, an encoded network slice configuration via system information;

determine that decoding information for the encoded network slice configuration is not obtained;

control the transceiver to transmit, to a network, a UE configuration update request message for the decoding information;

control the transceiver to receive, from the network, a UE configuration update response message including the decoding information; and

perform mobility based on the encoded network slice configuration by using the decoding information.
The wireless device of claim 15, wherein the encoded network slice configuration is ciphered by the network.
The wireless device of claim 16, wherein the decoding information includes a key for decoding the encoded network slice configuration ciphered by the network.
The wireless device of claim 17, wherein the at least one processor is further configured to,

decode the encoded network slice configuration by using the key; and

acquire a specific network slice configuration for the tracking area from the encoded network slice configuration.
The wireless device of claim 15, wherein the encoded network slice configuration includes at least one value related to at least one network slice configuration, wherein the at least one value is included in a mapping table.
The wireless device of claim 19, wherein the decoding information includes the mapping table including information on one or more values mapped to one or more network slice configurations, which are available on the tracking area.
The wireless device of claim 20, wherein the mapping table includes mapping information between the one or more network slice configurations and one or more service types.
The wireless device of claim 20, wherein the at least one processor is further configured to,

select a specific network slice configuration among the one or more network slice configurations based on (1) the at least one value included in the encoded network slice configuration and (2) the mapping table.
The wireless device of claim 15, wherein the at least one processor is further configured to,

move to the tracking area from a previous tracking area; and

check whether the decoding information is obtained or not upon moving to the tracking area,

wherein the tracking area is different from the previous tracking area.
The wireless device of claim 23, wherein it is determined that the decoding information for the encoded network slice configuration is not obtained, based on that the tracking area is a new tracking area for the wireless device.
The wireless device of claim 15, wherein the at least one processor is further configured to,

control the transceiver to receive, from the cell of the tracking area, an area identity related to the encoded network slice configuration; and

identify the tracking area based on the area identity.
The wireless device of claim 15, wherein the encoded network slice configuration includes information on (1) Slice/Service Type (SST), (2) Single Network Slice Selection Assistance Information (S-NSSAI), and/or (3) service identity.
The wireless device of claim 15, wherein the UE configuration update request message is a Registration Request message for a Registration procedure, and

wherein the UE configuration update response message is a Registration Response message.
The wireless device of claim 15, wherein the at least one processor is further configured to,

control the transceiver to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
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 cell in a tracking area, an encoded network slice configuration via system information;

determining that decoding information for the encoded network slice configuration is not obtained;

transmitting, to a network, a UE configuration update request message for the decoding information;

receiving, from the network, a UE configuration update response message including the decoding information; and

performing mobility based on the encoded network slice configuration by using the decoding information.
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:

receive, from a cell in a tracking area, an encoded network slice configuration via system information;

determine that decoding information for the encoded network slice configuration is not obtained;

transmit, to a network, a UE configuration update request message for the decoding information;

receive, from the network, a UE configuration update response message including the decoding information; and

perform mobility based on the encoded network slice configuration by using the decoding information.
A method performed by a base station in a wireless communication system, the method comprising,

transmitting, to a wireless device, an encoded network slice configuration via system information;

receiving, from the wireless device, a UE configuration update request message for the decoding information; and

transmitting, to the wireless device, a UE configuration update response message including the decoding information.
A base station in a wireless communication system comprising:

a transceiver;

a memory; and

a processor operatively coupled to the transceiver and the memory, and configured to:

control the transceiver to transmit, to a wireless device, an encoded network slice configuration via system information;

control the transceiver to receive, from the wireless device, a UE configuration update request message for the decoding information; and

control the transceiver to transmit, to the wireless device, a UE configuration update response message including the decoding information.