Slice-based PLMN selection

Abstract

One disclosure of the present specification provides a method by which an AAnF performs communication. The method comprises the steps of: transmitting, to a first public land mobile network (PLMN), support information indicating that UE can perform slice-based PLMN selection; receiving slice-related information from the first PLMN on the basis of the support information, the slide-related information comprising information about a network slice supported for each PLMN; and selecting a second PLMN supporting a specific network slice that the UE wants to use, on the basis of the slice-related information.

Description

Slice-based PLMN selection

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU radio communication sector) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable and low latency communications (URLLC). NR must be inherently forward-compatible.

[0005] A trigger condition for slice-based PLMN selection is required.

[0006] We propose conditions that trigger slice-based PLMN selection.

[0007] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0008] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0009] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0010] Figure 4 is a structural diagram of a next-generation mobile communications network.

[0011] Figure 5 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0012] Figures 6 and 7 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0013] Figures 8 and 9 illustrate examples of flowcharts according to embodiments of the present specification.

[0014] FIG. 10 illustrates an example of a trigger condition for slice-based PLMN selection according to an embodiment of the present specification.

[0015] Figure 11 shows an example showing an indication according to an embodiment of the present specification.

[0016] Figure 12 illustrates the UE's procedure for disclosure of this specification.

[0017] Figure 13 illustrates the PLMN's procedure for disclosure of this specification.

[0018] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

[0019] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0020] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0021] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0022] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0023] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0024] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0025] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0026] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0027] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0028] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0029] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0030] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

[0031] The three main requirement categories for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC).

[0032] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0033] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0034] Wireless devices (100a to 100f) refer to devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs) and heads-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0035] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving functions, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic 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 / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0036] For example, a UAV may be an aircraft that is unmanned and navigated by radio control signals.

[0037] For example, a VR device may include a device for implementing objects or backgrounds in a virtual environment. For example, an AR device may include a device that implements objects or backgrounds in a virtual world by connecting them to objects or backgrounds in the real world. For example, an MR device may include a device that implements objects or backgrounds in a virtual world by merging them with objects or backgrounds in the real world. For example, a holographic device may include a device that implements 360-degree stereoscopic images by recording and reproducing three-dimensional information using the light interference phenomenon that occurs when two laser lights, called holograms, meet.

[0038] For example, a public safety device may include an image relay device or imaging device that can be worn on the user's body.

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

[0040] For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, a medical device may be a device used for diagnosing, treating, alleviating, or correcting an injury or damage. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function. For example, a medical device may be a device used for the purpose of regulating pregnancy. For example, a medical device may include a therapeutic device, a driving device, an (in vitro) diagnostic device, a hearing aid, or a surgical device.

[0041] For example, a security device may be a device installed to prevent potential hazards and maintain safety. For example, a security device may be a camera, closed-circuit television (CCTV), recorder, or black box.

[0042] For example, a fintech device may be a device capable of providing financial services, such as mobile payments. For example, a fintech device may include a payment device or a point-of-sale system.

[0043] For example, a weather / environment device may include a device that monitors or predicts the weather / environment.

[0044] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0045] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, device-to-device (D2D) communication), and base station-to-base station communication (150c) (e.g., relay, integrated access and backhaul (IAB)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of the various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0046] AI is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0047] A robot can be defined as a machine that automatically processes or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making decisions, and performing actions on its own can be called an intelligent robot. Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with a drive unit, including an actuator or motor, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots include wheels, brakes, and propellers in their drive unit, enabling them to drive on the ground or fly in the air.

[0048] Autonomous driving refers to the technology of driving on one's own, while autonomous vehicles refer to vehicles that drive without, or with minimal, user intervention. For example, autonomous driving can include technologies such as lane keeping, automatic speed control like adaptive cruise control, autonomous driving along a set route, and autonomous driving based on a set destination. Vehicles encompass all types of vehicles: those with internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors. These vehicles can include not only cars but also trains and motorcycles. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

[0049] Extended reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images over images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR in that it displays real and virtual objects together. However, there is a difference: while AR uses virtual objects to complement real objects, MR uses virtual and real objects equally.

[0050] NR supports multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0051] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in NR systems, FR1 can mean the "sub-6GHz range," and FR2 can mean the "above 6GHz range," which can be referred to as millimeter wave (mmW).

[0052] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0053] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands can be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0054] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0055] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (low power wide area network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0056] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0057] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0058] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0059] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0060] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0061] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or 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 herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0062] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (radio frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0063] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

[0064] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0065] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0066] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements instruction codes, commands and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or 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 herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0067] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0068] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs), one or more service data units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0069] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For 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), and / or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphic processing unit (GPU), and a memory control processor.

[0070] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0071] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0072] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0073] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0074] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0075] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

[0076] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0077] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0078] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0079] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0080] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0081] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0082] A transceiver (106) is operably coupled to 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 a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0083] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0084] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0085] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0086] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0087] Figure 4 is a structural diagram of a next-generation mobile communications network.

[0088] 5GC (5G Core) may include various components, and in FIG. 5, some of them include AMF (Access and Mobility Management Function) (410), SMF (Session Management Function) (420), PCF (Policy Control Function) (430), UPF (User Plane Function) (440), AF (Application Function) (450), UDM (Unified Data Management) (460), and N3IWF (Non-3GPP (3rd Generation Partnership Project) Inter Working Function) (490).

[0089] The UE (100) is connected to a data network via UPF (440) through a Next Generation Radio Access Network (NG-RAN) including a gNB (20).

[0090] The UE (100) can also receive data services via untrusted non-3GPP access, such as a Wireless Local Area Network (WLAN). To connect the non-3GPP access to the core network, an N3IWF (490) may be deployed.

[0091] The illustrated N3IWF (490) performs the function of managing interworking between non-3GPP access and 5G system. When UE (100) is connected to non-3GPP access (e.g., WiFi, referred to as IEEE 801.11), UE (100) can be connected to 5G system through N3IWF (490). N3IWF (490) performs control signaling with AMF (410) and is connected to UPF (440) through N3 interface for data transmission.

[0092] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform functions to manage Non-Access Stratum (NAS) security. The AMF (410) can perform functions to handle mobility in the idle state.

[0093] The illustrated UPF (440) is a type of gateway through which user data is transmitted and received. The UPF node (440) can perform all or part of the user plane functions of the S-GW (Serving Gateway) and P-GW (Packet Data Network Gateway) of 4th generation mobile communications.

[0094] The UPF (440) acts as a boundary point between the next generation radio access network (NG-RAN) and the core network, and is an element that maintains a data path between the gNB (20) and the SMF (420). In addition, when the UE (100) moves across the area served by the gNB (20), the UPF (440) acts as a mobility anchor point. The UPF (440) can perform a function of handling PDUs. For mobility within the NG-RAN (Next Generation-Radio Access Network defined after 3GPP Release-15), the UPF can route packets. Additionally, the UPF (440) may also function as an anchor point for mobility with other 3GPP networks (RANs defined before 3GPP Release-15, e.g., UTRAN, E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network)) or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network). The UPF (440) may correspond to a termination point of a data interface toward a data network.

[0095] The illustrated PCF (430) is a node that controls the business operator's policy.

[0096] The illustrated AF (450) is a server for providing various services to the UE (100).

[0097] The illustrated UDM (460) is a type of server that manages subscriber information, such as the HSS (Home Subscriber Server) of 4th generation mobile communications. The UDM (460) stores and manages the subscriber information in a Unified Data Repository (UDR).

[0098] The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session.

[0099] For reference, the drawing symbols for AMF (410), SMF (420), PCF (430), UPF (440), AF (450), UDM (460), N3IWF (490), gNB (20), or UE (100) may be omitted below.

[0100] 5G mobile communications support multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands. A 30 kHz / 60 kHz SCS supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0101] Figure 5 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0102] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0103] - AUSF (Authentication Server Function)

[0104] - AMF (Access and Mobility Management Function)

[0105] - DN (Data Network), 예를 들어 운영자 서비스, 인터넷 접속 또는 타사 서비스

[0106] - USDF (Unstructured Data Storage Function)

[0107] - NEF (Network Exposure Function)

[0108] - I-NEF (Intermediate NEF)

[0109] - NRF (Network Repository Function)

[0110] - NSSF (Network Slice Selection Function)

[0111] - PCF (Policy Control Function)

[0112] - SMF (Session Management Function)

[0113] - UDM (Unified Data Management)

[0114] - UDR (Unified Data Repository)

[0115] - UPF (User Plane Function)

[0116] - UCMF (UE radio Capability Management Function)

[0117] - AF (Application Function)

[0118] - UE (User Equipment)

[0119] - (R)AN ((Radio) Access Network)

[0120] - 5G-EIR (5G-Equipment Identity Register)

[0121] - NWDAF (Network Data Analytics Function)

[0122] - CHF (CHarging Function)

[0123] Additionally, the following network features may be considered:

[0124] - N3IWF (Non-3GPP InterWorking Function)

[0125] - TNGF (Trusted Non-3GPP Gateway Function)

[0126] - W-AGF (Wireline Access Gateway Function)

[0127] Figure 5 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0128] For clarity of the point-to-point diagram in Figure 5, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0129] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0130] The 5G system architecture includes the following benchmarks:

[0131] - N1: Reference point between UE and AMF.

[0132] - N2: Reference point between (R)AN and AMF.

[0133] - N3: Reference point between (R)AN and UPF.

[0134] - N4: Reference point between SMF and UPF.

[0135] - N6: Reference point between UPF and data network.

[0136] - N9: Reference point between two UPFs.

[0137] The following benchmarks illustrate the interactions that exist between NF services in NF.

[0138] - N5: Reference point between PCF and AF.

[0139] - N7: Reference point between SMF and PCF.

[0140] - N8: Reference point between UDM and AMF.

[0141] - N10: Reference point between UDM and SMF.

[0142] - N11: Reference point between AMF and SMF.

[0143] - N12: Reference point between AMF and AUSF.

[0144] - N13: Reference point between UDM and AUSF.

[0145] - N14: Reference point between two AMFs.

[0146] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

[0147] - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0148] - N22: Reference point between AMF and NSSF.

[0149] In some cases, two NFs may need to be interconnected to serve a UE.

[0150] <Registration Procedure>

[0151] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0152] Figures 6 and 7 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0153] A UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types:

[0154] - Initial registration for 5GS; or

[0155] - mobility registration update; or

[0156] - Periodic registration update; or

[0157] - Emergency registration

[0158] The general registration procedures of Figures 6 and 7 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0159] The general registration procedures of Figures 6 and 7 can also be used when registering for a 3GPP connection when the UE is already registered for a non-3GPP connection, and vice versa. Registering for a 3GPP connection when the UE is already registered for a non-3GPP connection scenario may require an AMF change.

[0160] First, the procedure of Fig. 6 is described.

[0161] (1) Step 1: The UE transmits a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0162] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and the requested network slice selection assistance information (NSSAI). The AN parameters also include an establishment cause. The establishment cause provides the reason for requesting establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0163] A registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the UE moves, or the UE wants to update its capabilities or protocol parameters, or because the UE requests a change in the set of network slices it is allowed to use), or a periodic registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because of expiration of the periodic registration update timer), or an emergency registration (i.e., the UE is in restricted service state).

[0164] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

[0165] i) If the UE has a valid evolved packet system (EPS) globally unique temporary identifier (GUTI), 5G-GUTI mapped from the EPS GUTI;

[0166] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0167] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0168] iv) Native 5G-GUTI allocated by another PLMN (if available);

[0169] v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message.

[0170] If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also indicates the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI from items (ii)-(iv) in decreasing priority order in the list above.

[0171] When the UE performs initial registration with native 5G-GUTI, the UE indicates the relevant GUAMI information in the AN parameters. When the UE performs initial registration with SUCI, the UE does not indicate the GUAMI information in the AN parameters.

[0172] For emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included. If the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

[0173] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the PDU session currently established in the PLMN in the UE.

[0174] (2) Step 2: (R)AN selects AMF.

[0175] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI, if available.

[0176] When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the UE's N2 connection.

[0177] If the (R)AN cannot select an appropriate AMF, the (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in the (R)AN.

[0178] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0179] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0180] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

[0181] If the registration type indicated by the UE is periodic registration update, steps 4-19 described below may be omitted.

[0182] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

[0183] (5) Step 5: The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call including the UE's SUPI and UE context.

[0184] (6) Step 6: If SUCI is not provided by the UE or not retrieved from the previous AMF, the new AMF may initiate an ID request procedure by sending an Identity Request message to request SUCI from the UE.

[0185] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN).

[0186] (8) Step 8: The new AMF may decide to initiate UE authentication by calling the AUSF. In this case, the new AMF selects the AUSF based on SUPI or SUCI.

[0187] (9) Step 9: Authentication / security can be established by UE, new AMF, AUSF and / or UDM.

[0188] (10) Step 10: If the AMF has changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the old AMF that the UE registration with the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the old AMF. The old AMF may continue as if the UE context transfer service operation was not received.

[0189] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0190] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0191] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is described.

[0192] (13) Step 13: If step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0193] (14) Step 14: New AMFs can be registered with UDM.

[0194] (15) Step 15: New AMF can select PCF.

[0195] (16) Step 16: The new AMF may optionally perform AM policy association establishment / modification.

[0196] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0197] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE context modification request to the N3IWF / TNGF / W-AGF.

[0198] (19) Step 19: N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF.

[0199] (20) Step 20: After the new AMF receives the response message from N3IWF / TNGF / W-AGF in step 19, the new AMF can register with UDM.

[0200] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0201] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0202] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0203] Additionally, optionally, the new AMF performs UE policy association establishment.

[0204] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0205] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

[0206] (23) Step 23: In case of registration via 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In case of registration via non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0207] (24) Step 24: AMF can perform information updates on UDM.

[0208] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

[0209] <Slice-based PLMN selection>

[0210] Legacy UEs perform PLMN selection using PLMN selection information stored in the USIM or received via SoR, including VPLMN information. Furthermore, slice-based PLMN selection may be performed to select a VPLMN that supports the network slice requested by the UE. To support slice-based PLMN selection, the UE may receive VPLMN information and network slice information via SoR. If the UE supports slice-based PLMN selection, the UE may store legacy SoR information without slice information as well as SoR information including network slice information. To support slice-based PLMN selection, several UE behaviors must be clarified. For example, the point in time when the UE triggers slice-based PLMN selection must be defined.

[0211] In this specification, a method for triggering slice-based PLMN selection may be proposed.

[0212] The method for triggering slice-based PLMN selection may consist of a combination of one or more of the actions / configurations / steps described below.

[0213] In this specification, UE (User Equipment) and terminal are used interchangeably.

[0214] In this specification, the terms Subscriber and User are used interchangeably.

[0215] In this specification, the terms network, CN (Core Network), 5G CN, 3GPP network, and 3GPP system are used interchangeably.

[0216] In this specification, the terms Home Network, Subscribed Network, and Non-roaming Network are used interchangeably.

[0217] In this specification, the terms Visited Network, Non-subscribed Network, Roaming Network, and Non-home Network are used interchangeably.

[0218] In order to implement a mechanism for a UE to perform PLMN selection based on SoR information including network slice information, several triggering points for slice-based PLMN selection can be proposed in the present disclosure.

[0219] If the terminal indicates that it supports slice-based PLMN selection (sbPLMN support indication or capability for slice-based PLMN selection), the network may send SoR information to the terminal, including network slice information (e.g., VPLMN list, VPLMN priority, list of network slices supported in a particular VPLMN, etc.).

[0220] The terminal can store SoR information for slice-based PLMN selection.

[0221] When receiving specific instructions or information from the network or when specific conditions are satisfied on the terminal side, the terminal can perform slice-based PLMN selection based on SoR information.

[0222] In this specification, slice-based PLMN selection may refer to selecting a PLMN that supports the network slice the terminal desires to use. In this case, the terminal may perform registration with the selected PLMN. Additionally, the terminal may deregister from the PLMN prior to selection.

[0223] The PLMN selection operation may include any type of network selection. For example, PLMN selection may also include SNPN selection.

[0224] 1. The terminal receives information about slice-based PLMN selection.

[0225] Figures 8 and 9 illustrate examples of flowcharts according to embodiments of the present specification.

[0226] Figures 8 and 9 illustrate examples of message flows for receiving sbPLMN (slice-based PLMN selection) information. After receiving sbPLMN information, the terminal can decide whether to perform slice-based PLMN selection or legacy PLMN selection that does not consider network slices.

[0227] 1) Step 1: If the terminal supports slice-based PLMN selection (sbPLMN), the terminal may provide a sbPLMN support indication (or capability) to the network.

[0228] When a terminal registers with a network and the registration type is “initial registration” or “emergency registration,” the terminal may transmit an sbPLMN support indication as a 5GMM capability parameter of the registration request message.

[0229] When the terminal performs a periodic or mobility registration update procedure, the terminal may send an sbPLMN support indication in the SOR transparent container IE of the registration request message.

[0230] 2) Step 2: Depending on the UE context, the AMF may request sbPLMN information from the UDM. If sbPLMN information needs to be transmitted to the UE, the AMF may forward the request to the UDM.

[0231] 3) Step 3: If the UDM determines that sbPLMN information needs to be transmitted to the terminal, the UDM may transmit a sbPLMN information request to the SOR-AF or UDR.

[0232] SOR-AF or UDR can transmit sbPLMN information to UDM.

[0233] 4) Step 4: UDM can transmit sbPLMN information to AMF. sbPLMN information can be in the form of a SOR Transparent Container IE or a security packet as specified in TS 24.501 v18.3.1.

[0234] sbPLMN information may include:

[0235] - List of preferred PLMNs (e.g. VPLMN)

[0236] - List of preferred PLMN (e.g. VPLMN) / access technology combinations

[0237] - List of supported network slices by PLMN (e.g. VPLMN)

[0238] - Indication indicating whether sbPLMN should be performed upon receipt of SoR message containing slice information.

[0239] 5) Step 5: If AMF needs to update UE subscription data, AMF can notify UDM.

[0240] 6) Step 6: AMF can transmit sbPLMN information to the terminal. AMF can transmit SoR information including sbPLMN information to the terminal.

[0241] A terminal that receives sbPLMN information can store the information.

[0242] If the sbPLMN information is in the form of a SOR transparent container IE, the terminal can store the information in the ME (Mobile Equipment).

[0243] If the sbPLMN information is in the form of a security packet, the terminal can store the information in the USIM.

[0244] 2. Conditions that trigger slice-based PLMN selection

[0245] If the conditions described below are met, the terminal may decide to perform slice-based PLMN selection. Based on the above decision, the terminal may perform slice-based PLMN selection.

[0246] The conditions described below can be combined with each other and used as conditions to trigger slice-based PLMN selection.

[0247] (1) When receiving a specific cause for rejection

[0248] Messages from the network (e.g., registration rejection messages) may include the reason for the rejection.

[0249] The above rejection cause may include a new cause indicating that network slicing is not supported.

[0250] Alternatively, the above rejection reasons may include the following example reasons.

[0251] - No network slices available

[0252] - Insufficient resources for specific slices and DNNs

[0253] - Insufficient resources for a specific slice

[0254] - DNN is not supported or subscribed to in network slice

[0255] (2) When a terminal requests a network slice (or requests it by indicating a preference for using a network slice), the terminal receives rejection information for the network slice.

[0256] (3) Receive a list of high priority PLMNs supporting network slices.

[0257] The above network slice may be a slice requested by the terminal to the network, a slice for which the terminal has indicated a preference for use in the network, or a slice that the terminal determines is necessary.

[0258] (4) When the time validity condition or location validity condition for a specific network slice is satisfied and the network slice and / or related PLMN information is received via SoR or stored in the UE.

[0259] (5) When requested from the upper layer

[0260] Upper layers may request specific services / applications and / or network slices. If the current network does not support the service / application and / or network slice, the UE may perform slice-based PLMN selection.

[0261] Upon request from a higher layer for a specific service or application, the terminal can successfully establish a connection (e.g., a PDU session) with the network even if there is no network slice that exactly matches the stored local information (e.g., URSP) by applying a default configuration (e.g., a default URSP). In this case, the terminal can perform slice-based PLMN selection to select a network that supports an exact matching network slice for more adaptive services (e.g., better QoS).

[0262] For example, even if a terminal can use eMBB-General service to use a gaming application, the terminal can perform slice-based PLMN selection for a network slice that supports eMBB-Gaming service.

[0263] The UE preferred slice value may be SST=A (eMBB) and SD=B (gaming). If the UE is connected to the network using SST=A (eMBB) and SD=C (general), the UE may perform slice-based PLMN selection.

[0264] (6) The terminal requests a specific network slice and the stored SoR information includes the network slice.

[0265] (7) The terminal can perform PLMN selection when there is no ongoing service.

[0266] (8) When emergency services do not exist, the terminal can perform PLMN selection.

[0267] (9) If the selected area does not support the network slice requested by the terminal (or set to the terminal).

[0268] (10) If the selected area does not allow the network slice requested by the terminal (or set to the terminal).

[0269] (11) If the selected area does not support some of the network slices that the UE must use.

[0270] If there are ongoing services (e.g., low priority services / applications, background services) that use lower priority slices, the terminal may perform slice-based PLMN selection.

[0271] If there is an ongoing service but better QoS or better throughput is expected in the new network, the terminal can perform slice-based PLMN selection.

[0272] FIG. 10 illustrates an example of a trigger condition for slice-based PLMN selection according to an embodiment of the present specification.

[0273] According to the procedures of FIGS. 8 and 9, the terminal can receive slice-based SoR information (or sbPLMN information). Based on the information, the terminal can perform slice-based PLMN selection.

[0274] When the UE receives sbPLMN information and SOR-CMCI information, the UE may perform slice-based PLMN selection after a timer started with the Tsor-cm timer value of the SOR-CMCI rule parameter expires.

[0275] If the terminal has sbPLMN information and the network does not support (is not available for) the network slice required by the terminal, the terminal can perform slice-based PLMN selection.

[0276] The network may transmit an indication to the terminal indicating slice-based PLMN selection. Based on the indication, the terminal may perform slice-based PLMN selection.

[0277] When a terminal receives a message from the network containing a specific rejection cause, the terminal may perform slice-based PLMN selection. The specific rejection cause may be information indicating that the network does not support a specific slice.

[0278] For example, a terminal may send a registration request message to a network by including a slice for which registration is desired in the 'requested NSSAI'. The terminal may receive a registration rejection message. The rejection cause included in the registration rejection message may be at least one of 'no available network slice', 'insufficient resources for a specific slice and DNN', 'insufficient resources for a specific slice', 'DNN is not supported or subscribed in the network slice', 'indication to perform slice-based PLMN selection immediately after receiving the rejection cause', and 'information that slice-based PLMN selection is required'. In this case, the terminal may perform slice-based PLMN selection.

[0279] The terminal can perform slice-based PLMN selection for slices with high priority.

[0280] A terminal may be requested to use a network slice that is not currently supported by the network. In this case, the terminal may perform slice-based PLMN selection.

[0281] If there are no ongoing services, the terminal can perform slice-based PLMN selection. Performing PLMN selection may result in the disconnection of ongoing services.

[0282] If the timer for network selection expires, the terminal may perform slice-based PLMN selection. If the timer does not expire, PLMN selection may not be performed.

[0283] The above timer may be a timer that controls periodic attempts of PLMN selection.

[0284] 3. Actions performed based on the example

[0285] A UE may indicate a UE capability indicating that it supports slice-based PLMN selection. The UE may transmit the UE capability to the network.

[0286] The UE may receive SOR information including network slice information. The SOR information may be sbPLMN information as shown in FIGS. 8 and 9.

[0287] The sbPLMN information may include a list of preferred PLMNs (e.g., VPLMN), a list of preferred PLMN (e.g., VPLMN) / access technology combinations, a list of supported network slices per PLMN (e.g., VPLMN), and an indication of whether sbPLMN should be performed upon receipt of an SoR message containing slice information.

[0288] The order of the above preferred PLMN list may indicate the priority of the PLMNs. For example, the first PLMN in the list may be the highest-priority PLMN.

[0289] The UE may receive an indication from the network indicating one of the following:

[0290] - Whether legacy PLMN selection should be performed

[0291] - Whether PLMN selection for localized services should be performed in SNPN

[0292] - Whether PLMN selection should be performed using operator control signal thresholds

[0293] - Whether slice-based PLMN selection should be performed

[0294] The above indication may be a combination of several characteristics. For example, the network may indicate that slice-based PLMN selection should be performed and that operator-controlled signal thresholds should be considered in PLMN selection.

[0295] The above indication can be delivered via SoR transparent container.

[0296] The indication can be conveyed as a bit in the SOR header. For example, the indication can be conveyed as shown in FIG. 11.

[0297] Figure 11 shows an example showing an indication according to an embodiment of the present specification.

[0298] Figure 11 shows the SOR header for the SOR data type with a value of "0".

[0299] Bit 6 "sbPLMN Indicator" may indicate an indication. If the value is set to 1, the UE may perform slice-based PLMN selection based on sbPLMN information.

[0300] After receiving SOR information including network slice information, the UE can transmit a response to the network.

[0301] The above response may be an acknowledgment.

[0302] The above response may include information requested by the UE. For example, the information requested by the UE may be more detailed information such as unsupported network slices, preferred network slices, and time validity information.

[0303] The UE can store SOR information including network slice information.

[0304] If the UE has stored information for slice-based PLMN selection, the UE can perform slice-based PLMN selection.

[0305] If the UE receives a specific rejection reason from the network, the UE may perform slice-based PLMN selection.

[0306] The above reasons for rejection may include the following example reasons:

[0307] - No network slices available

[0308] - Insufficient resources for specific slices and DNNs

[0309] - Insufficient resources for a specific slice

[0310] - DNN is not supported or subscribed to in network slice

[0311] If the UE receives a rejection indication for a particular network slice (e.g., rejection reason, reject S-NSSAI, rejection information, no user plane resources), the UE may perform slice-based PLMN selection.

[0312] For example, if the UE requests or uses S-NSSAI#1 (if a PDU session using S-NSSAI#1 is established), the UE may receive information that S-NSSAI#1 is rejected. In this case, the UE may perform slice-based PLMN selection.

[0313] For example, the UE may not be able to allocate user plane resources of S-NSSAI#1 due to mobility (e.g., handover). In this case, the UE may perform slice-based PLMN selection.

[0314] If the UE has stored a high priority PLMN, the UE may perform slice-based PLMN selection.

[0315] If the UE requires the use of a specific network slice and has stored a high priority PLMN for that specific network slice, the UE may perform slice-based PLMN selection.

[0316] If high priority services / applications need to be used, the UE may perform slice-based PLMN selection.

[0317] Even if there is an ongoing service, if the ongoing service has a lower priority than the requested service / application, the UE may perform slice-based PLMN selection. The requested service / application may be a service / application related to the network slice that the UE wishes to use.

[0318] Foreground services can have a higher priority than background services.

[0319] The most recently triggered service may have a higher priority.

[0320] Even if there is an ongoing service, the UE can perform slice-based PLMN selection if the service is supported based on the default URSP rules.

[0321] For example, since URSP does not provide dedicated slice information for gaming services, a UE using the gaming service may have established a PDU session using the default URSP rules. In this case, the UE may perform slice-based PLMN selection.

[0322] If no emergency service exists, the UE may perform slice-based PLMN selection.

[0323] Even if there is an ongoing service, the UE can perform slice-based PLMN selection. While the UE may utilize gaming applications using the eMBB-General service, the UE can also perform slice-based PLMN selection for network slices that support the eMBB-Gaming service.

[0324] If a higher-priority PLMN exists, even if there is an ongoing service, the UE may perform slice-based PLMN selection. If the service can be supported through a higher-priority PLMN for a network slice that supports eMBB-Gaming services, the UE may perform slice-based PLMN selection.

[0325] If the serving network does not support the network slice requested by the UE, the UE may perform slice-based PLMN selection.

[0326] Based on the expiration of a specific timer, the UE may perform slice-based PLMN selection.

[0327] The above specific timer may be T3245.

[0328] The UE may perform slice-based PLMN selection upon expiration of a timer to define or limit the duration of the search time using non-considered slice network selection (e.g., legacy PLMN selection, legacy SNPN selection, PLMN selection for localized services in SNPN, SENSE-based PLMN selection, etc.).

[0329] If the UE needs to perform slice-based PLMN selection to receive service, the UE may inform the network of the unavailability period.

[0330] The UE may send an Unavailability Period IE during the deregistration procedure.

[0331] The following actions can be performed:

[0332] - Receive SoR information including slice information

[0333] - Perform slice-based PLMN selection if one of the following conditions is met:

[0334] - Receive indications for specific PLMN selection functions

[0335] - Receive specific reasons for rejection

[0336] - Receive specific rejected network slice information

[0337] - Request a specific slice (a network slice that is not currently supported on the network)

[0338] - Store higher priority PLMNs that support specific network slices

[0339] - Network selection timer expired

[0340] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0341] Figure 12 illustrates the UE's procedure for disclosure of this specification.

[0342] 1. The UE may transmit assistance information to the first PLMN indicating that the UE is capable of performing slice-based PLMN (Public Land Mobile Network) selection.

[0343] 2. Based on the above support information, the UE can receive slice-related information from the first PLMN.

[0344] The above slice-related information may include information about network slices supported by each PLMN.

[0345] 3. Based on the above slice-related information, the UE can select a second PLMN that supports a specific network slice that the UE wants to use.

[0346] The UE may send a registration request message to the first PLMN.

[0347] The step of transmitting the above registration request message may include: a step of the UE transmitting the above support information.

[0348] The above registration request message may include information about the specific network slice that the UE wishes to use.

[0349] The above slice related information may include information that the first PLMN does not support the specific network slice.

[0350] The above second PLMN may support the above specific network slice.

[0351] The above slice related information may include an indication that instructs the UE to perform slice-based PLMN selection.

[0352] Based on the existence of a service being used by the UE, the UE may skip selecting the second PLMN.

[0353] Based on the service being used by the UE having a higher priority than the service associated with the particular network slice, the UE may skip selecting the second PLMN.

[0354] The UE may select the second PLMN based on the service being used by the UE having a lower priority than the service associated with the particular network slice.

[0355] Based on the above selection, the UE may perform deregistration for the first PLMN.

[0356] Based on the above selection, the UE can perform registration for the second PLMN.

[0357] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0358] Figure 13 illustrates the PLMN's procedure for disclosure of this specification.

[0359] 1. The PLMN can receive assistance information from a UE (User Equipment) indicating that the UE can perform slice-based PLMN selection.

[0360] 2. Based on the above support information, the PLMN can transmit slice-related information to the UE.

[0361] The above slice-related information may include information about network slices supported by each PLMN.

[0362] 3. Based on the fact that the UE has performed slice-based PLMN selection based on the slice-related information, the PLMN may release registration with the UE.

[0363] The PLMN may receive a registration request message from the UE.

[0364] The step of receiving the above registration request message may include: a step of the PLMN receiving the above support information.

[0365] The above registration request message may include information about a specific network slice that the UE wishes to use.

[0366] The above slice related information may include information that the PLMN does not support the specific network slice.

[0367] The other PLMNs mentioned above may support the specific network slice.

[0368] The above slice related information may include an indication that instructs the UE to perform slice-based PLMN selection.

[0369] Based on the existence of a service being used by the UE, the PLMN may skip deregistering with the UE.

[0370] The PLMN may skip deregistering the UE based on the service being used by the UE having a higher priority than the service associated with the particular network slice.

[0371] The PLMN may deregister with the UE based on the service being used by the UE having a lower priority than the service associated with the particular network slice.

[0372] Hereinafter, a device for performing communication according to some embodiments of the present specification will be described.

[0373] For example, a device may include a processor, a transceiver, and memory.

[0374] For example, a processor may be configured to be operatively coupled with memory and a processor.

[0375] The operations performed by the processor may include: transmitting support information to a first PLMN indicating that the UE can perform slice-based PLMN (Public Land Mobile Network) selection; receiving slice-related information from the first PLMN based on the support information; and selecting a second PLMN that supports a specific network slice that the UE desires to use based on the slice-related information, wherein the slice-related information includes information on a network slice supported by each PLMN.

[0376] Below, a processor of a device for providing communication according to some embodiments of the present specification is described.

[0377] The operations performed by the processor may include: transmitting support information to a first PLMN indicating that the UE can perform slice-based PLMN (Public Land Mobile Network) selection; receiving slice-related information from the first PLMN based on the support information; and selecting a second PLMN that supports a specific network slice that the UE desires to use based on the slice-related information, wherein the slice-related information includes information on a network slice supported by each PLMN.

[0378] Hereinafter, a non-volatile computer-readable medium storing one or more commands for providing mobile communication according to some embodiments of the present specification is described.

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

[0380] Some examples of storage media are coupled to the processor, allowing the processor to read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may reside in an ASIC. In other examples, the processor and storage media may reside as separate components.

[0381] Computer-readable media may include tangible and non-volatile computer-readable storage media.

[0382] For example, nonvolatile computer-readable media may include random access memory (RAM), such as synchronized dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), read-only memory (EEPROM), flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Nonvolatile computer-readable media may also include combinations of the above.

[0383] Additionally, the methods described herein can be realized at least in part by a computer-readable communication medium that carries or transmits code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0384] According to some embodiments of the present disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The one or more stored instructions can be executed by a processor of a base station.

[0385] The one or more stored commands may include: transmitting to a first PLMN support information indicating that the UE is capable of performing slice-based Public Land Mobile Network (PLMN) selection; receiving, based on the support information, slice-related information from the first PLMN; and selecting, based on the slice-related information, a second PLMN that supports a specific network slice that the UE desires to use.

[0386] This specification may have various effects.

[0387] For example, network slice-based PLMN selection may be triggered.

[0388] The effects that can be achieved through specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0389] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A method by which UE (User Equipment) performs communication, A step of transmitting assistance information indicating that the UE can perform slice-based PLMN selection to a first PLMN (Public Land Mobile Network); A step of receiving slice-related information from the first PLMN based on the above support information; The above slice-related information includes information about the network slices supported by each PLMN, A method comprising the step of selecting a second PLMN supporting a specific network slice that the UE wishes to use based on the slice-related information.

2. In paragraph 1, Further comprising the step of transmitting a registration request message to the first PLMN, A method comprising: transmitting the registration request message; transmitting the support information.

3. In paragraph 2, The above registration request message includes information about the specific network slice that the UE wishes to use, The above slice-related information includes information that the first PLMN does not support the specific network slice, A method in which the second PLMN supports the specific network slice.

4. In any one of the clauses 1 to 3, A method wherein the slice-related information includes an indication that instructs the UE to perform slice-based PLMN selection.

5. In any one of paragraphs 1 to 4, A method in which the UE skips selecting the second PLMN based on the existence of a service being used by the UE.

6. In any one of paragraphs 1 to 4, Based on the service being used by the UE having a higher priority than the service associated with the specific network slice, the UE skips selecting the second PLMN, A method in which the step of selecting the second PLMN is performed based on the service being used by the UE having a lower priority than the service associated with the specific network slice.

7. In any one of paragraphs 1 to 5, A step of performing deregistration for the first PLMN based on the above selection; A method further comprising the step of performing registration for the second PLMN based on the above selection.

8. A method by which PLMN (Public Land Mobile Network) performs communication, A step of receiving support information from a UE (User Equipment) indicating that the UE can perform slice-based PLMN selection; A step of transmitting slice-related information to the UE based on the above support information; The above slice-related information includes information about the network slices supported by each PLMN, A method comprising the step of releasing registration with the UE based on the fact that the UE has performed slice-based PLMN selection based on the slice-related information.

9. In paragraph 8, Further comprising the step of receiving a registration request message from the UE, A method comprising: receiving the registration request message; receiving the support information.

10. In paragraph 9, The above registration request message includes information about a specific network slice that the UE wishes to use, The above slice-related information includes information that the PLMN does not support the specific network slice, The above other PLMNs support the above specific network slice.

11. In any one of the clauses 8 to 10, A method wherein the slice-related information includes an indication that instructs the UE to perform slice-based PLMN selection.

12. In any one of the clauses 8 to 11, A method in which the PLMN skips deregistration with the UE based on the existence of a service being used by the UE.

13. In any one of the clauses 8 to 11, Based on the fact that the service being used by the UE has a higher priority than the service associated with the specific network slice, the PLMN skips deregistering the UE, A method in which a step of deregistering with the UE is performed based on the service being used by the UE having a lower priority than the service associated with the specific network slice.

14. As a UE (User Equipment) performing communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a UE according to any one of claims 1 to 7.

15. As a PLMN (Public Land Mobile Network) that performs communications, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a PLMN according to any one of claims 8 to 13.

16. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to at least one processor, A device wherein the operation performed based on the command being executed by the at least one processor is a method according to any one of claims 1 to 7.

17. A non-volatile computer-readable storage medium that records commands, A non-volatile computer-readable storage medium, wherein the instructions, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 7.

Images