SNPN communication method

Abstract

One disclosure of the present specification provides a method of UE communication. The method comprises the steps of: receiving valid time information for a localized service of an SNPN from the SNPN; receiving a registration rejection message or a registration release message; storing the SNPN on a prohibition list based on the registration rejection message or the registration release message; activating a timer based on the valid time information; based on the expiration of the timer, deleting the SNPN from the forbidden list; and selecting a cell for the localized service, in which the network stored on the prohibition list is excluded as a target of cell selection.

Description

TECHNICAL FIELD

[0001] The present specification relates to mobile communications. BACKGROUND

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage of and system capacity. As an upper layer of requirements, 3GPP LTE needs to support many kinds of services with different QoS (quality of service) requirements by using a limited radio resource. For LTE, the International Telecommunication Union (ITU) Radio Communication Sector (ITU-R) and the 3GPP have specified requirements in the International Mobile Telecommunications-Advanced (IMT-Advanced) standard and the 3GPP Long Term Evolution (LTE) standard, respectively. The 3GPP LTE standard is also called Evolved Universal Mobile Telecommunications System (E-UMTS) and is also called the fourth generation (4G) system.

[0003] Requirements and specifications have been started to be developed for a new radio (NR) system in the International Telecommunication Union (ITU) and the 3GPP. The 3GPP must identify and develop the technology components that need to be standardized for the new RAT to be successfully deployed on time for both the immediate (5G) and longer-term (beyond-5G) market opportunities as set forth by the ITU Radio communications Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. In addition, NR should be able to use any spectrum bands available for wireless communications even in a much higher frequency range than the 5G system, i.e., above 7 GHz, and also in a much lower frequency range than the 5G system, i.e., below 1 GHz.

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

[0005] In the case of a registration rejection / deregistration from the SNPN, the characteristics of the SNPN must be considered with respect to the time at which the terminal requests registration to the SNPN. SUMMARY

[0006] TECHNICAL SOLUTION

[0007] Receiving time validity information from the SNPN and performing SNPN selection based on the time validity information. BRIEF DESCRIPTION OF DRAWINGS

[0008] Figure 1 An example of a communication system to which implementations of the present disclosure is applied is illustrated.

[0009] Figure 2 An example of a wireless device to which implementations of the present disclosure is applied is illustrated.

[0010] Figure 3 An example of a UE to which implementations of the present disclosure is applied is illustrated.

[0011] Figure 4 Is a block diagram of a next-generation cellular network.

[0012] Figure 5 An example 5G system structure to which implementations of the present specification can be applied is illustrated.

[0013] Figure 6 and Figure 7 An example of a registration procedure to which implementations of the present disclosure are applied is shown.

[0014] Figure 8 An example of a procedure according to implementations of the present specification is shown.

[0015] Figure 9 An example of SNPN information according to implementations of the present disclosure is shown.

[0016] Figure 10 An example of time validity information according to implementations of the present disclosure is shown.

[0017] Figure 11 A procedure of a UE according to the disclosure of the present specification is shown.

[0018] Figure 12 A procedure of a SNPN according to the disclosure of the present specification is shown. DETAILED DESCRIPTION

[0019] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of the 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 multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and employs SC-FDMA in UL. Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0020] For the convenience of description, implementation modes of the disclosure are described mainly with respect to a 3GPP-based wireless communication system. However, technical features of the disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP-based wireless communication system, aspects of the disclosure, which are not limited to a 3GPP-based wireless communication system, are applicable to other mobile communication systems.

[0021] For terms and technologies not specifically described among terms and technologies employed in the disclosure, reference can be made to wireless communication standard documents published before the disclosure.

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

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

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

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

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

[0027] Technical features described separately in one drawing in the disclosure can be implemented alone or simultaneously.

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

[0029] Hereinafter, the present disclosure will be described in greater detail with reference to the accompanying drawings. The same reference numbers in the following drawings and / or description can represent the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0030] Figure 1 An example of a communication system to which implementations of the present disclosure are applied is illustrated.

[0031] Figure 1 The illustrated 5G usage scenarios are merely exemplary and the technical features of the present disclosure can be applied to other 5G usage scenarios not illustrated in Figure 1 FIG. 1.

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

[0033] Referring to Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 5G networks are illustrated as an example of the network of the communication system 1, implementations of the present disclosure are not limited to 5G systems and can be applied to future communication systems beyond 5G systems.

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

[0035] The wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or LTE), and can be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f can include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicles can include vehicles with wireless communication functionality, self-driving vehicles, and vehicles capable of performing communication between vehicles. The vehicles can include unmanned aerial vehicles (UAVs) (e.g., drones). The XR device can include an AR / VR / mixed reality (MR) device, and can be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. The handheld device can include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smartglasses), and a computer (e.g., a notebook). The home appliance can include a television, a refrigerator, and a washing machine. The IoT device can include a sensor and a smartmeter.

[0036] In the disclosure, the wireless devices 100a to 100f can be referred to as user equipment (UE). For example, the UE can include a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving functionality, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environment device, a device related to 5G services, or a device related to the fourth industrial revolution field.

[0037] For example, the UAV can be a flying object that flies by a wireless control signal without a person on board.

[0038] For example, the VR device can include a device for implementing objects or backgrounds of a virtual world. For example, the AR device can include a device implemented by connecting objects or backgrounds of a virtual world to objects or backgrounds of a real world. For example, the MR device can include a device implemented by merging objects or backgrounds of a virtual world into objects or backgrounds of a real world. For example, the hologram device can include a device for implementing a 360-degree stereoscopic image by recording and reproducing stereoscopic information using an optical interference phenomenon generated when two lasers meet, which is called holography.

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

[0040] For example, the MTC device and the IoT device can be devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device can include a smart meter, a vending machine, a thermometer, a smart light bulb, a door lock, or various sensors.

[0041] For example, the medical device can be a device for the purpose of diagnosing, treating, alleviating, curing, or preventing a disease. For example, the medical device can be a device for the purpose of diagnosing, treating, alleviating, or correcting an injury or a trauma. For example, the medical device can be a device for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device can be a device for adjusting pregnancy. For example, the medical device can include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for surgery.

[0042] For example, the safety device can be a device installed to prevent a danger that can occur and to maintain safety. For example, the safety device can be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

[0043] For example, the financial technology device can be a device capable of providing a financial service such as mobile payment. For example, the financial technology device can include a payment device or a point of sale (POS) system.

[0044] For example, the weather / environment device can include a device for monitoring or predicting weather / environment.

[0045] The wireless devices 100a-100f can be connected to the network 300 via the BS 200. The AI technology can be applied to the wireless devices 100a-100f, and the wireless devices 100a-100f can be connected to the 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 super 5G network. Although the wireless devices 100a-100f can communicate with each other through the BS 200 / network 300, the wireless devices 100a-100f can perform direct communication (e.g., sidelink communication) with each other without going through the BS 200 / network 300. For example, the vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a-100f.

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

[0047] AI refers to a field of studying artificial intelligence or a method of creating it, and machine learning refers to a field of defining various problems solved in the AI field and a field of methods of solving them. Machine learning is also defined as an algorithm that increases performance of a task through stable experience of the task.

[0048] A robot means a machine that automatically processes or operates a given task by its own ability. In particular, a robot having the ability to recognize an environment and determine a performance action by itself can be referred to as an intelligent robot. Depending on a use purpose or a field, a robot can be classified into industrial, medical, home, military, etc. A robot can perform various physical operations, such as moving a robot joint using an actuator or a motor. A movable robot also includes a driven wheel, a brake, a propeller, etc., thereby allowing it to travel on the ground or fly in the air.

[0049] Autonomous driving means a technology of driving by itself, and an autonomous vehicle means a vehicle that drives without user control or with minimal user control. For example, autonomous driving can include maintaining a lane in motion, automatically adjusting a speed (e.g., adaptive cruise control), automatically driving along a set route, and automatically setting a route when a destination is set. A vehicle encompasses a vehicle equipped with an internal combustion engine, a hybrid vehicle equipped with an internal combustion engine and an electric motor, and an electric vehicle equipped with an electric motor, and can include a train, a motorcycle, etc., as well as an automobile. An autonomous vehicle can be regarded as a robot having an autonomous driving function.

[0050] Extended reality is collectively referred to as VR, AR, and MR. VR technology provides real-world objects and backgrounds only through computer graphics (CG) images. AR technology provides virtual CG images on top of real object images. MR technology is a CG technology that combines virtual objects into the real world. MR technology is similar to AR technology in that they display real objects and virtual objects together. However, the difference is that, in AR technology, virtual objects are used as a supplementary form of real objects, whereas, in MR technology, virtual objects and real objects are used as equal individuals.

[0051] NR supports multiple numerologies (and / or multiple subcarrier spacings (SCSs)) to support various 5G services. For example, if the SCS is 15 kHz, a wide area can be supported in a legacy cellular band, if the SCS is 30 kHz / 60 kHz, a dense urban, lower latency, and wider carrier bandwidth can be supported. If the SCS is 60 kHz or more, a bandwidth greater than 24.25 GHz can be supported to overcome phase noise.

[0052] An NR frequency band can be defined as two types of frequency ranges, i.e., FR1 and FR2. The numerical values of the frequency ranges can change. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 can mean a "sub-6 GHz range," FR2 can mean a "above-6 GHz range" and can be referred to as a millimeter wave (mmW).

[0053] [Table 1]

[0054]

[0055] As described above, the numerical values of the frequency ranges of the NR system can change. For example, as shown in Table 2 below, FR1 can include a frequency band of 410 MHz to 7125 MHz. That is, FR1 can include a frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or more. For example, the frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or more included in FR1 can include an unlicensed band. The unlicensed band can be used for various purposes, for example, communication for vehicles (e.g., autonomous driving).

[0056] [Table 2]

[0057]

[0058] Here, the radio communication technology implemented in the wireless device in the present disclosure can include Narrow Band Internet of Things (NB-IoT) technology for low power communication as well as LTE, NR, and 6G. For example, the NB-IoT technology can be an example of a low power wide area network (LPWAN) technology, can be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and can not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure can be communicated based on LTE-M technology. For example, the LTE-M technology can be an example of a LPWAN technology and be referred to as various names such as enhanced machine type communication (eMTC). For example, the LTE-M technology can be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine type communication, and / or 7) LTE M, and can not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low power communication, and can not be limited to the above names. For example, the ZigBee technology can generate a personal area network (PAN) associated with small / low power digital communication based on various specifications such as IEEE 802.15.4, and can be referred to as various names.

[0059] Figure 2 An example of a wireless device to which implementations of the present disclosure are applied is illustrated.

[0060] In Figure 2 , the first wireless device 100 and / or the second wireless device 200 can be implemented in various forms according to use cases / services. For example, {the first wireless device 100 and the second wireless device 200} can correspond to at least one of {the wireless devices 100a to 100f and the BS 200}, {the wireless devices 100a to 100f and the wireless devices 100a to 100f}, and / or {the BS 200 and the BS 200}. Figure 1 The first wireless device 100 and / or the second wireless device 200 can be configured by various elements, devices / components, and / or modules.

[0061] The first wireless device 100 can include at least one transceiver (e.g., the transceiver 106), at least one processing chip (e.g., the processing chip 101), and / or one or more antennas 108.

[0062] The processing chip 101 can include at least one processor (e.g., processor 102) and at least one memory (e.g., memory 104). Additionally and / or alternatively, the memory 104 can be placed outside of the processing chip 101.

[0063] The processor 102 can control the memory 104 and / or the transceiver 106, and can be adapted to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts described in the present disclosure. For example, the processor 102 can process information within the memory 104 to generate first information / signal, and then transmit a radio signal including the first information / signal through the transceiver 106. The processor 102 can receive a radio signal including second information / signal through the transceiver 106, and then store information obtained by processing the second information / signal in the memory 104.

[0064] The memory 104 can be operatively connected to the processor 102. The memory 104 can store various types of information and / or instructions. The memory 104 can store firmware and / or software code 105 implementing code, commands, and / or command sets that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or software code 105 can implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or software code 105 can control the processor 102 to perform one or more protocols. For example, the firmware and / or software code 105 can control the processor 102 to perform one or more layers of a radio interface protocol.

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

[0066] The second wireless device 200 can include at least one transceiver (e.g., transceiver 206), at least one processing chip (e.g., processing chip 201), and / or one or more antennas 208.

[0067] The processing chip 201 can include at least one processor (e.g., processor 202) and at least one memory (e.g., memory 204). Additionally and / or alternatively, the memory 204 can be placed outside of the processing chip 201.

[0068] The processor 202 can control the memory 204 and / or the transceiver 206, and can be adapted to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts described in the present disclosure. For example, the processor 202 can process information within the memory 204 to generate third information / signal, and then transmit a radio signal including the third information / signal through the transceiver 206. The processor 202 can receive a radio signal including fourth information / signal through the transceiver 106, and then store information obtained by processing the fourth information / signal in the memory 204.

[0069] The memory 204 can be operatively connected to the processor 202. The memory 204 can store various types of information and / or instructions. The memory 204 can store firmware and / or software code 205 implementing code, commands, and / or command sets, which, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or software code 205 can implement instructions, which, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or software code 205 can control the processor 202 to perform one or more protocols. For example, the firmware and / or software code 205 can control the processor 202 to perform one or more layers of a radio interface protocol.

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

[0071] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers can be implemented by the one or more processors 102 and 202, but are not limited thereto. For example, the one or more processors 102 and 202 can implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium 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). The one or more processors 102 and 202 can 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, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 can generate signals (e.g., baseband signals) including the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure, and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106 and 206, and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure.

[0072] The one or more processors 102 and 202 can be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 can be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) can be included in the one or more processors 102 and 202. For example, the one or more processors 102 and 202 can be configured by a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphics processing units (GPUs), and memory control processors.

[0073] One or more memories 104, 204 may be associated with one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. These memories 104, 204 may include random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. These memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, these memories 104, 204 may be coupled to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0074] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as described herein, to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as described herein, from one or more other devices. For example, the one or more transceivers 106, 206 may be associated with the one or more processors 102, 202 and may transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, wireless signals, etc., to one or more other devices. Furthermore, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, wireless signals, etc., from one or more other devices.

[0075] One or more transceivers 106, 206 may be associated with one or more antennas 108, 208. Additionally and / or alternatively, the one or more transceivers 106, 206 may include one or more antennas 108, 208. The one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, features, processes, suggestions, methods, and / or operation flowcharts disclosed herein via the one or more antennas 108, 208. As used herein, the one or more antennas 108, 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0076] One or more transceivers 106, 206 can convert received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., can be processed by the one or more processors 102, 202. The one or more transceivers 106, 206 can use the one or more processors 102, 202 to convert the processed user data, control information, radio signals / channels, etc., from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106, 206 can, under the control of the one or more processors 102, 202, upconvert OFDM baseband signals to OFDM signals via (analog) oscillators and / or filters, and transmit the upconverted OFDM signals at a carrier frequency. One or more transceivers 106, 206 can receive OFDM signals at a carrier frequency and, under the control of one or more processors 102, 202, down-convert the OFDM signals to OFDM baseband signals via (analog) oscillators and / or filters.

[0077] although Figure 2 As not shown, wireless devices 100 and 200 may also include additional components. Additional component 140 may be configured differently depending on the type of wireless devices 100 and 200. For example, additional component 140 may include at least one of a power unit / battery, input / output (I / O) devices (e.g., audio I / O ports, video I / O ports), drive devices, and computing devices. Additional component 140 may be coupled to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0078] In the implementation of this disclosure, the UE can operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In the implementation of this disclosure, the BS can operate as a receiving device in the UL and as a transmitting device in the DL. For ease of description, it is primarily assumed below that the first wireless device 100 acts as the UE and the second wireless device 200 acts as the BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 may be adapted to perform UE behavior according to the implementation of this disclosure or to control the transceiver 106 to perform UE behavior according to the implementation of this disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 may be adapted to perform BS behavior according to the implementation of this disclosure or to control the transceiver 206 to perform BS behavior according to the implementation of this disclosure.

[0079] In this disclosure, BS is also referred to as Node B (NB), eNode B (eNB), or gNB.

[0080] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0081] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0082] Reference Figure 3 UE 100 can correspond to Figure 2 The first wireless device 100.

[0083] The UE 100 includes a processor 102, a 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 subscriber identification module (SIM) card 145, a speaker 146, and a microphone 147.

[0084] Processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 may be adapted to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A layer of the radio interface protocol may be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuitry, and / or data processing means. Processor 102 may be an application processor. Processor 102 may include at least one of a DSP, CPU, GPU, and modem (modulator and demodulator). Examples of processor 102 can be found in the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, Samsung® manufactured EXYNOS TM Series processors, a range of processors manufactured by Apple®, and HELIO manufactured by MediaTek® TM Series processors, Intel® manufactured ATOM TM This series of processors or the corresponding next-generation processors.

[0085] Memory 104 is operatively coupled to processor 102 and stores various information to operate processor 102. Memory 104 may include ROM, RAM, flash memory, memory card, storage medium, and / or other storage devices. When the implementation is software-based, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. Modules may be stored in memory 104 and executed by processor 102. Memory 104 may be implemented within or outside processor 102, in which case it may be communicatively coupled to processor 102 via various means known in the art.

[0086] Transceiver 106 is operatively coupled to processor 102 and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry for processing radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

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

[0088] Display 143 outputs the results processed by processor 102. Keypad 144 receives inputs to be used by processor 102. Keypad 144 can be displayed on display 143.

[0089] The SIM card 145 is an integrated circuit designed to securely store the International Mobile Subscriber Identity (IMSI) number and its associated key used for identifying and authenticating subscribers on mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0090] Speaker 146 outputs the sound-related results processed by processor 102. Microphone 147 receives the sound-related input to be used by processor 102.

[0091] Figure 4 This is a block diagram of the next-generation cellular network.

[0092] The 5G core (5GC) can include various components, some of which are in Figure 5 The diagram shows functions such as Access and Mobility Management Function (AMF) (410), Session Management Function (SMF) (420), Policy Control Function (PCF) (430), User Plane Function (UPF) (440), Application Function (AF) (450), Unified Data Management (UDM) (460) and Non-3GPP Interoperability Function (N3IWF) (490).

[0093] UE 100 connects to the data network via UPF 440 through a next-generation radio access network (NG-RAN) including gNB 20.

[0094] Data services can also be provided to UE 100 via untrusted non-3GPP access (such as wireless local area network (WLAN)). To connect the aforementioned non-3GPP access to the core network, an N3IWF 490 can be deployed.

[0095] The N3IWF 490 shown performs the function of managing interoperability between non-3GPP access and 5G systems. When UE 100 is associated with a non-3GPP access (e.g., WiFi, also known as IEEE 801.11), UE 100 can associate with a 5G system via the N3IWF 490. The N3IWF 490 communicates with the AMF 410 for control signaling and with the UPF 440 via the N3 interface for data transmission.

[0096] The AMF 410 shown can manage access and mobility in 5G systems. The AMF 410 can perform functions for managing Non-Access Stratum (NAS) security. The AMF 410 can perform functions for handling mobility in idle states.

[0097] The UPF 440 shown is a gateway through which user data is sent and received. The UPF node 440 can perform all or part of the user plane functions of a Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW) for fourth-generation mobile communications.

[0098] The UPF 440 acts as a boundary between the Next Generation Radio Access Network (NG-RAN) and the core network, and is an element that maintains the data path between gNB 20 and SMF 420. Additionally, the UPF 440 acts as a mobility anchor when the UE 100 moves across the area served by gNB 20. The UPF 440 can perform PDU processing functions. For mobility within the NG-RAN (Next Generation Radio Access Network as defined in 3GPP Release 15 and later), the UPF can route packets. The UPF 440 can also be used as an anchor for mobility with other 3GPP networks (RANs defined prior to 3GPP Release 15, such as UTRAN, E-UTRAN (Evolved UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network) or GERAN (Global System for Mobile Communications (GSM) / EDGE (Global Evolution Enhanced Data Rate) Radio Access Network). The UPF 440 can correspond to the termination point of the data interface to the data network.

[0099] The PCF 430 shown is a node that controls the operator's policies.

[0100] The AF 450 shown is a server used to provide multiple services to UE 100.

[0101] The UDM 460 shown is a type of server that manages subscriber information, such as the Home Subscriber Server (HSS) in fourth-generation mobile communications. The UDM 460 stores and manages subscriber information in a unified data repository (UDR).

[0102] The SMF 420 shown can perform the function of assigning Internet Protocol (IP) addresses to UEs. The SMF 420 can also control Protocol Data Unit (PDU) sessions.

[0103] For reference purposes, the reference numerals for AMF 410, SMF 420, PCF 430, UPF 440, AF 450, UDM460, N3IWF 490, gNB 20, or UE 100 may be omitted in this document.

[0104] Fifth-generation mobile communication supports multiple parameter sets or subcarrier spacings (SCS) to support a variety of 5G services. For example, a 15kHz SCS supports wide-area coverage in traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths greater than 24.25GHz to overcome phase noise.

[0105] Figure 5 Example 5G system architectures that can be implemented using the methods described in this specification are illustrated.

[0106] The architecture of a 5G system (5GS; 5G system) consists of the following network functions (NFs).

[0107] -AUSF (Authentication Server Functionality)

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

[0109] -DN (Data Network), such as carrier services, internet access, or third-party services.

[0110] -USDF (Unstructured Data Storage Function)

[0111] -NEF (Network Open Functionality)

[0112] -I-NEF (middle NEF)

[0113] -NRF (Network Storage Function)

[0114] -NSSF (Network Slice Selection Function)

[0115] -PCF (Policy Control Function)

[0116] -SMF (Session Management Function)

[0117] -UDM (Unified Data Management)

[0118] -UDR (Unified Data Repository)

[0119] -UPF (User Plane Function)

[0120] -UCMF (UE Radio Capability Management Function)

[0121] -AF (Application Function)

[0122] -UE (User Equipment)

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

[0124] -5G-EIR (5G Device Identifier Register)

[0125] -NWDAF (Network Data Analysis Function)

[0126] -CHF (Billing Function)

[0127] In addition, the following network functions can be considered.

[0128] -N3IWF (Non-3GPP interoperability function)

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

[0130] -W-AGF (Wired Access Gateway Function)

[0131] Figure 5 The architecture of a 5G system in a non-roaming scenario is shown using reference points that illustrate how various network functions interact with each other.

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

[0133] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in [the original text]. Figure 5 As shown in the image. For clarity, Figure 5 The connection between NWDAF and other NFs (e.g., PCF) is not shown.

[0134] The 5G system architecture includes the following reference points.

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

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

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

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

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

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

[0141] The following reference points illustrate the interactions that exist between NF services.

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

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

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

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

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

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

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

[0149] -N14: Reference point between the two AMFs.

[0150] -N15: The reference point between the PCF and AMF in non-roaming scenarios, and the reference point between the PCF and AMF of the visited network in roaming scenarios.

[0151] -N16: Reference point between two SMFs (in the case of roaming, between the visiting SMF and the home SMF).

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

[0153] In some cases, it may be necessary to connect two NFs to each other to serve the UE.

[0154] <Registration Process>

[0155] Describe the registration process. Refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0156] Figure 6 and Figure 7 An example of a registration process applying the implementation of this disclosure is shown.

[0157] The UE needs to register with the network to obtain authorization to receive services, enabling mobility tracking and reachability. The UE initiates the registration process using one of the following registration types:

[0158] - To the initial registration of 5GS; or

[0159] -Mobility registration update; or

[0160] - Periodic registration and updates; or

[0161] - Urgent registration.

[0162] Figure 6 and Figure 7 The general registration process applies to all of these registration processes, but periodic registration updates do not need to include all the parameters used in other registration cases.

[0163] Figure 6 and Figure 7 The general registration process is also used for 3GPP access when the UE has already registered in a non-3GPP access scenario, and vice versa. Registration in 3GPP access when the UE has already registered in a non-3GPP access scenario may require an AMF change.

[0164] First, description Figure 6 The process.

[0165] (1) Step 1: The UE sends a registration request message to the (R)AN. The registration request message corresponds to the AN message.

[0166] The registration request message may include AN parameters. In the case of NG-RAN, 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 Auxiliary Information (NSSAI). AN parameters also include the establishment reason. The establishment reason provides the reason for requesting to establish 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 Layer Connection Establishment NSSAI Include Mode parameter.

[0167] The 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 the RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to mobility issues or because the UE needs to update its capabilities or protocol parameters or requests a change in the set of network slices it is allowed to use), a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process because the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in a restricted service state).

[0168] When the UE is performing initial registration, the UE should indicate its UE identifier in the registration request message, as shown below, listed in descending order of preference:

[0169] i) If the UE has a valid Evolved Packet System (EPS) GUTI, then the 5G Globally Unique Temporary Identifier (5G-GUTI) is mapped from the EPS GUTI.

[0170] ii) The native 5G-GUTI assigned by the PLMN to which the UE is attempting to register (if available);

[0171] iii) The native 5G-GUTI assigned by the equivalent PLMN to the PLMN the UE is trying to register to (if available);

[0172] iv) Native 5G-GUTI assigned by any other PLMN (if available);

[0173] v) Otherwise, the UE should include its Subscriber Hidden Identifier (SUCI) in the registration request message.

[0174] When a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE should also indicate the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE should select the 5G-GUTI from items (ii) to (iv) in the list above in descending order of preference.

[0175] When a UE is performing initial registration using native 5G-GUTI, the UE should indicate the relevant GUAMI information in the AN parameters. When a UE is performing initial registration using its SUCI, the UE should not indicate any GUAMI information in the AN parameters.

[0176] For emergency registration, if the UE does not have a valid 5G-GUTI available, the SUCI should be included; when the UE does not have a Subscriber Permanent Identifier (SUPI) and does not have a valid 5G-GUTI, the Permanent Device Identifier (PEI) should be included. In other cases, the 5G-GUTI is included and it indicates the last serving AMF.

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

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

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

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

[0181] If the (R)AN cannot select an appropriate AMF, it will forward the registration request message to the AMF already configured in the (R)AN to perform AMF selection.

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

[0183] The registration request message may include all and / or a portion of the information included in the registration request message received from the UE as described in step 1.

[0184] The registration request message may include N2 parameters. When using NG-RAN, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell identifier associated with the cell where the UE is camped, and a UE context request indicating that a UE context including security information needs to be set up at NG-RAN. When using NG-RAN, the N2 parameters should also include the reason for registration.

[0185] If the registration type indicated by the UE is periodic registration update, steps 4 to 19 can be omitted.

[0186] (4) Step 4: If the UE’s 5G-GUTI is included in the registration request message and the service AMF has changed since the last registration process, the new AMF can invoke the Namf_Communication_UEContextTransfer service operation on the old AMF, which includes the complete registration request non-access stratum (NAS) message, to request the UE’s SUPI and UE context.

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

[0188] (6) Step 6: If the SUCI is not provided by the UE or retrieved from the old AMF, the identity request process can be initiated by sending an identity request message to the UE requesting the SUCI through the new AMF.

[0189] (7) Step 7: The UE can respond with an identity response message that includes the SUCI. The UE obtains the SUCI by using the provisioning public key of the home PLMN (HPLMN).

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

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

[0192] (10) Step 10: If the AMF has changed, the new AMF can notify the old AMF of the UE's registration completion in the new AMF by calling the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security process fails, registration will be rejected, and the new AMF can call the Namf_Communication_RegistrationCompleteNotify service operation with a rejection indication reason code to the old AMF. The old AMF can continue as if it had never received the UE context delivery service operation.

[0193] (11) Step 11: If the PEI is not provided by the UE or retrieved from the old AMF, the identity request process can be initiated by sending an identity request message to the UE through the new AMF to retrieve the PEI. The PEI should be transmitted in encrypted form unless the UE performs emergency registration and cannot be authenticated.

[0194] (12) Step 12: Optionally, the new AMF can initiate an ME identity check by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0195] Now, the description is in Figure 6 After the process Figure 7 The process.

[0196] (13) Step 13: If you want to perform step 14 below, the new AMF can select UDM based on SUPI, and then UDM can select UDR instance.

[0197] (14) Step 14: The new AMF can register with the UDM.

[0198] (15) Step 15: The new AMF can select PCF.

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

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

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

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

[0203] (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.

[0204] (21) Step 21: The new AMF sends a registration acceptance message to the UE.

[0205] The new AMF sends a registration acceptance message to the UE, indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, this 5G-GUTI is included. If the UE is already in RM-REGISTERED state via another access point in the same PLMN, the UE should use the 5G-GUTI received in the registration acceptance message for both registrations. If the registration acceptance message does not include a 5G-GUTI, the UE will also use the 5G-GUTI allocated for the existing registration for the new registration. If the new AMF allocates a new registration area, it should send the registration area to the UE via the registration acceptance message. If the registration acceptance message does not include a registration area, the UE should treat the old registration area as valid. Mobility restrictions are included if they apply to the UE and the registration type is not emergency registration. The new AMF indicates the established PDU session to the UE in the PDU session state. The UE locally removes any internal resources associated with a PDU session not marked as established in the received PDU session state. When a UE connects to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes any internal resources associated with the current PLMN's PDU session that are not marked as established in the received PDU session state. If the PDU session state information is in the registration request message, the new AMF should indicate the PDU session state to the UE.

[0206] The allowed NSSAIs provided in the registration acceptance message are valid within the registered region, and it applies to all PLMNs whose tracking regions are included within the registered region. The mapping of allowed NSSAIs is a mapping from each S-NSSAI of the allowed NSSAIs to the HPLMN S-NSSAIs. The mapping of configured NSSAIs is a mapping from each S-NSSAI of the configured NSSAIs used to serve the PLMN to the HPLMN S-NSSAIs.

[0207] In addition, optionally, the new AMF performs UE policy association establishment.

[0208] (22) Step 22: When the UE successfully updates itself, the UE can send a registration completion message to the new AMF.

[0209] The UE can send a registration completion message to the new AMF to confirm whether a new 5G-GUTI has been allocated.

[0210] (23) Step 23: For registration via 3GPP access, if the new AMF does not release the signaling connection, the new AMF can send the RRC inactivity auxiliary information to the NG-RAN. For registration via non-3GPP access, if the UE is also in the CM-CONNECTED state on 3GPP access, the new AMF can send the RRC inactivity auxiliary information to the NG-RAN.

[0211] Step 24: The new AMF may perform information updates towards the UDM.

[0212] Step 25: The UE may perform network slice specific authentication and authorization procedures.

[0213] <Selection and Registration of SNPN>

[0214] The UE may select an SNPN that provides access for the local service, and the network may update the UE with information about the local service (e.g., SNPN configuration for the local service). After the UE selects a specific SNPN, the UE will register the SNPN and periodically update the registration to the SNPN.

[0215] Although the UE selects an SNPN, the network may reject the UE registration request because the UE is not authorized for the service (e.g., does not meet the service validity criteria). This may occur when the UE has outdated service validity information for the service.

[0216] After the UE is rejected by the SNPN, the behavior of the UE should be clarified.

[0217] For example, if the UE receives a registration rejection message in the SNPN, the UE may place the SNPN in the prohibited SNPN list. According to the existing prohibited list handling mechanism, the UE may start a UE implementation specific timer for no less than 60 minutes to maintain the prohibited SNPN. The UE may remove the SNPN from the temporary prohibited SNPN list if one of the following conditions is met:

[0218] a) There is a successful LR after subsequent manual selection of an SNPN;

[0219] b) The MS implementation specific timer for no less than 60 minutes expires;

[0220] c) The MS is configured to use timer T3245 and timer T3245 expires;

[0221] d) The MS is not configured to use timer T3245, timer T3247 expires, and the value of the SNPN specific attempt counter for this SNPN is less than the MS implementation specific maximum defined in 3GPP TS 24.501

[64] ;

[0222] e) The MS is turned off;

[0223] f) If the following is performed in the selected SNPN, update the entry of the "subscriber data list" that identifies the subscribed SNPN identity of the SNPN or remove the USIM:

[0224] - Using EAP-AKA's EAP-based primary authentication and key negotiation process; or

[0225] - The main authentication and key negotiation process based on 5G AKA; or

[0226] g) For the selected PLMN subscription, update the selected entry in the "Subscriber Data List" or remove the USIM.

[0227] However, the existing mechanism may not be effective because even though the SNPN has been temporarily unavailable and resumed service, the UE may not reselect the SNPN for at least 60 minutes.

[0228] In normal operation, if SNPN registration is rejected, the UE may be unable to select that SNPN and continue the registration process for at least 60 minutes. This uniform time (at least 60 minutes) may not apply to a specific SNPN.

[0229] Therefore, the characteristics of the SNPN must be considered to determine when the UE can select and register with the SNPN again.

[0230] When a UE has refused or requested to deregister from the network (e.g., a specific SNPN), the UE can re-allow the specific SNPN based on the time validity information for localized services in the SNPN or a timer value received from the network.

[0231] When a UE receives a registration rejection message or deregistration request message from the network, the UE can reselect a specific SNPN after a specific time and perform the registration process. The specific time can be based on time validity information for localized services (e.g., a specific SNPN) in the SNPN or a timer value received from the network.

[0232] When a UE receives a registration rejection message or deregistration request message from the network (e.g., a specific SNPN), the UE can store (or add) the specific SNPN to a prohibited list (temporary or permanent prohibited list) or a list of disallowed SNPNs.

[0233] After a certain period of time, the UE may be allowed to reselect an SNPN. To determine when reselection of a specific SNPN is permitted, the UE can use stored time validity information for the SNPN or a timer value received from the network.

[0234] When a UE receives a registration rejection message or deregistration request message from a network (e.g., a specific SNPN), the UE can store the network (e.g., a specific SNPN) in a prohibited list (or a list of disallowed SNPNs).

[0235] When a terminal receives time validity information from a specific SNPN, it can determine a timer value based on the time validity information while storing (or adding) the specific SNPN to the prohibited list (or list of disallowed SNPNs). The terminal can then start (run) a timer using the determined timer value. The time validity information can be information about the next valid time for the localized service of the specific SNPN (the next time period during which the terminal can receive the localized service). The time validity information may include the start time and / or end time of the next valid time for the localized service of the specific SNPN (the next time period during which the terminal can receive the localized service). The timer value can be based on the start time and / or end time of the next valid time (the next time period during which the terminal can receive the localized service). The timer value can be a random value drawn from a range between a first time and a second time. The first time period can be the time from when the specific SNPN is stored (or added) to the prohibited list (or list of disallowed SNPNs) to the start time of the next valid time period (the next time period during which the terminal can receive the localized service). The second time period can be the time from when a specific SNPN is stored (or added) to the prohibited list (or the list of disallowed SNPNs) to the end of the next valid time period (the next time period in which the terminal can receive localized services).

[0236] After a specific time period (corresponding to a timer value) starting from the time when the terminal stores (or adds) a specific SNPN to the prohibited list (or a list of disallowed SNPNs), the terminal may be allowed to reselect the specific SNPN. The specific time period may be based on time validity information for localized services in the SNPN or a timer value received from the network (e.g., the specific SNPN).

[0237] Time validity information can be a value received from the network (e.g., a specific SNPN).

[0238] Time validity information can be sent to the terminal via a registration accept message. Alternatively, time validity information can be sent to the terminal via a DL NAS transmission message. Alternatively, time validity information can be sent to the terminal via a registration reject message. Alternatively, time validity information can be sent to the terminal via a deregistration message.

[0239] After a specific period of time has elapsed since the terminal stored (or added) a specific SNPN to the prohibited list (or list of disallowed SNPNs), the terminal can remove the specific SNPN from the prohibited list (or list of disallowed SNPNs). As a result, the terminal can be allowed to reselect the specific SNPN.

[0240] Time validity information may include the start and / or end times of the next validity period of a localized service for a specific SNPN (the next period in which the terminal can receive the localized service).

[0241] Figure 8 An example of a process according to an embodiment of this specification is shown.

[0242] The terminal can notify the UE that it supports UE capabilities for SNPN access for localized services. The terminal can send UE capabilities to the network (e.g., SNPN).

[0243] The terminal can receive information about localized services. This information can be sent to the terminal via SOR, USAT commands, or RRC / NAS signaling. This information can be time validity information regarding the localized service. This information can be received from the network or SNPN.

[0244] Time validity information can be sent to the terminal via a registration accept message. Alternatively, time validity information can be sent to the terminal via a DL NAS transmission message. Alternatively, time validity information can be sent to the terminal via a registration reject message. Alternatively, time validity information can be sent to the terminal via a deregistration message.

[0245] Time validity information can be included in a SoR transparent container and sent to the terminal.

[0246] The terminal can receive SoR information from the SNPN for localized services. This information can be time validity information for the localized service. Information can be received from the network or the SNPN.

[0247] The terminal can be pre-configured for localized services. The terminal can be pre-configured with time validity information or location validity information for localized services.

[0248] The terminal can store SNPN service information. SNPN service information may include time validity information or location validity information for localized services.

[0249] The terminal can send a registration request message to the network (e.g., a specific SNPN).

[0250] Registration request messages can be initial, mobility update, or periodic update messages.

[0251] In response to a registration request message, the terminal can receive a registration rejection message.

[0252] Registration rejection messages may include a specific reason for rejection and / or a timer value. Alternatively, registration rejection messages may include time validity information.

[0253] A timer value can indicate a period of time during which access to a specific SNPN is not permitted. Alternatively, a timer value can indicate time information regarding the validity of a specific SNPN. Alternatively, a timer value can indicate information regarding when a specific SNPN provides valid localized services.

[0254] Timer values ​​received from the network (e.g., a specific SNPN) can have a higher priority than service time validity information previously stored in the terminal.

[0255] Time validity information may include the start and / or end times of the next valid period (the next period in which services can be received) for a specific SNPN's localized service.

[0256] The terminal can receive a deregistration request message from the network (e.g., a specific SNPN).

[0257] The terminal can receive a network-initiated deregistration message from the network (e.g., a specific SNPN).

[0258] A deregistration request message (or a network-initiated deregistration message or deregistration message) may include specific deregistration reasons and / or deregistration type information. A deregistration request message (or a network-initiated deregistration message or deregistration message) may include a timer value (or time validity information).

[0259] The cancellation type information indicates that re-registration is possible after a certain period of time.

[0260] A timer value can indicate a period of time during which access to a specific SNPN is not permitted. Alternatively, a timer value can indicate time information regarding the validity of a specific SNPN. Alternatively, a timer value can indicate information regarding when a specific SNPN provides valid localized services.

[0261] When a terminal receives a registration rejection (or deregistration) message from a specific SNPN, the terminal can store (or add) the specific SNPN (or its identifier) ​​to a prohibited list (or a temporary prohibited list for accessing localized services within the SNPN) or a list of disallowed SNPNs. When the terminal selects a PLMN, it can choose not to select an SNPN (or PLMN) that belongs to a prohibited list (a temporary or permanent prohibited list for accessing localized services within the SNPN) or a list of disallowed SNPNs.

[0262] Therefore, if a specific SNPN is added to a prohibited list (temporary or permanent) or a list of disallowed SNPNs, the terminal may not select that specific SNPN during PLMN selection.

[0263] When a terminal receives time validity information from a specific SNPN, it can determine a timer value based on the time validity information while storing (or adding) the specific SNPN to the prohibited list (or list of disallowed SNPNs). The terminal can then start (run) a timer using the determined timer value. The time validity information can be information about the next valid time for the localized service of the specific SNPN (the next time period during which the localized service can be received). The time validity information may include the start time and / or end time of the next valid time for the localized service of the specific SNPN (the next time period during which the localized service can be received). The timer value can be based on the start time and / or end time of the next valid time (the next time period during which the localized service can be received). The timer value can be a random value drawn from a range between a first time and a second time. The first time period can be the time from when the specific SNPN is stored (or added) to the prohibited list (or list of disallowed SNPNs) to the start time of the next valid time period for the localized service (the next time period during which the localized service can be received). The second time period can be the time from when a specific SNPN is stored (or added) to the prohibited list (or a list of disallowed SNPNs) to the end time of the next valid time period of the localization service (the next time period that can receive the localization service). The timer can expire between the start time and the end time.

[0264] The terminal can start (or run) a timer based on the timer value (or time validity information) included in the registration rejection (or deregistration) message.

[0265] Time validity information may include the start and / or end times of the next valid time period (the next time period in which the service can be received) for the localized service of SNPN.

[0266] The timer value can be determined based on the period between the start and end of the next valid period (the next period in which services can be received) of a specific SNPN's localized service. The timer value can be determined by the SNPN.

[0267] After a specific time (after the timer expires) following the time when the terminal stores (or adds) a specific SNPN (identifier of the specific SNPN) into the prohibited list (or list of disallowed SNPNs), the terminal can remove the specific SNPN (identifier of the specific SNPN) from the prohibited list (or list of disallowed SNPNs).

[0268] A specific time can be based on a timer value (or time validity information) included in a registration rejection (or deregistration) message. Alternatively, a specific time can be based on a time period associated with the time validity information. Alternatively, a specific time can be based on the valid start and / or end times of the localized service included in the time validity information.

[0269] The terminal can perform cell selection based on removing a specific SNPN (or its identifier) ​​from a prohibited list (or a list of disallowed SNPNs). As a result of the cell selection, the terminal can select the specific SNPN. The terminal can then perform a registration process with the specific SNPN.

[0270] The aforementioned time validity information can be sent to the terminal via the SOR transparent container.

[0271] Figure 9 An example of SNPN information according to an embodiment of this disclosure is shown.

[0272] Figure 10 An example of time validity information according to an embodiment of this disclosure is shown.

[0273] Figure 9 An example of SNPN information included in a transparent SOR container is shown. Figure 9 An example of SNPN information for localized service support is shown.

[0274] Figure 10 An example of time validity information included in SNPN information is shown.

[0275] Time periods can be encoded as Route Descriptor (RSD) component value fields for "time window types". For "time window types", the RSD component value fields can be encoded as sequences of Starttime and Stoptime fields.

[0276] The Starttime field represents the number of seconds since January 1, 1970, 00:00:00, and can be encoded in a defined 64-bit NTP timestamp format. Here, the binary encoding of the integer part can encode the first 32 bits and the last 32 bits of the fractional part. The encoding of the Stoptime field can be the same as that of the Starttime field.

[0277] For example, according to an embodiment of this disclosure, the Starttime field can indicate the start time of the validity period of the SNPN's localized service. According to an embodiment of this disclosure, the Stoptime field can indicate the end time of the validity period of the SNPN's localized service.

[0278] Terminals can select SNPN for localized services.

[0279] You can receive deregistration messages or registration rejection messages from SNPN.

[0280] Cancellation or registration rejection messages may include timers.

[0281] The terminal can start a received timer. The timer value can be determined (or calculated) based on the timer value received when a deregistration message or registration rejection message is received from the SNPN, or based on the time validity information for localized services in the SNPN.

[0282] SNPN can be selected based on the expiration of the timer.

[0283] The following figures were created to illustrate specific examples of this specification. The names of specific devices or signals / messages / fields depicted in the figures are presented as examples, and therefore the technical features of this specification are not limited to the specific names used in the following figures.

[0284] Figure 11 The procedure of the UE disclosed in this specification is shown.

[0285] 1. The UE can receive validity time information for localized services for the SNPN from the Independent Non-Public Network (SNPN).

[0286] 2. The UE can receive registration rejection messages or deregistration messages.

[0287] 3. The UE can store SNPN information in the blocked list based on the registration rejection message or the deregistration message.

[0288] 4. The UE can start a timer based on validity time information.

[0289] 5. Based on the expiration of the timer, the UE can remove SNPN information from the prohibited list.

[0290] 6. The UE can perform cell selection for localized services.

[0291] Networks on the blacklist can be excluded from the target selection for the cell.

[0292] The steps for performing the cell selection may include:

[0293] SNPNs are selected based on information about their removal from the banned list.

[0294] The UE can send a registration request message to the SNPN based on the cell selection.

[0295] The validity period information may include the start and end times of the next valid period during which localized services can be received.

[0296] The timer value can be based on a range between the start and end times.

[0297] The UE can send information to the SNPN about its ability to access the SNPN.

[0298] The steps for receiving validity time information can be performed based on information about the capability.

[0299] The validity period information can be the information of the SoR (SoR) transparent container.

[0300] The steps for receiving validity time information can be:

[0301] Receive downlink (DL) non-access stratum (NAS) transmission messages.

[0302] Registration rejection messages may include validity period information.

[0303] The cancellation message may include validity period information.

[0304] The steps for receiving validity time information can be:

[0305] Receive a registration acceptance message that includes the validity period information.

[0306] The following figures were created to illustrate specific examples of this specification. The names of specific devices or signals / messages / fields depicted in the figures are given by way of example, and therefore the technical features of this specification are not limited to the specific names used in the following figures.

[0307] Figure 12 The SNPN process disclosed in this specification is shown.

[0308] 1. SNPN can send the validity period information of the localized service to the UE.

[0309] 2. SNPN can send registration rejection messages or deregistration messages to the UE.

[0310] 3. SNPN can receive registration request messages from UE at a specific time point based on validity time information.

[0311] The registration request message can be based on the cell selection of the SNPN performed by the UE.

[0312] The validity period information may include the start and end times of the next valid period during which localized services can be received.

[0313] SNPN can receive information from UE about the UE's ability to access SNPN.

[0314] The steps for sending validity period information can be performed based on information about the capabilities.

[0315] The validity period information can be the information of the SoR (SoR) transparent container.

[0316] The steps for sending validity time information are as follows:

[0317] Send downlink (DL) non-access stratum (NAS) transmission messages.

[0318] Registration rejection messages may include validity period information.

[0319] The cancellation message may include validity period information.

[0320] The steps for sending validity time information can be:

[0321] Send a registration acceptance message that includes the validity period information.

[0322] In the following, a device for performing communication according to some embodiments of this specification will be described.

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

[0324] For example, the processor can be configured to be operationally coupled to the memory and the processor.

[0325] The processor can perform the following actions: receiving validity period information for localized services of an Independent Non-Public Network (SNPN); receiving a registration rejection message or a deregistration message; storing the SNPN's information in a prohibited list based on the registration rejection message or the deregistration message; starting a timer based on the validity period information; deleting the SNPN's information from the prohibited list based on the timer's expiration; and performing cell selection for the localized service, wherein the network in the prohibited list is excluded from the target of the cell selection.

[0326] In the following sections, a processor for providing communication according to some embodiments of this specification will be described.

[0327] The processor is configured to: receive validity period information for localized services for a standalone non-public network (SNPN); receive a registration rejection message or a deregistration message; store the SNPN's information in a prohibited list based on the registration rejection message or the deregistration message; start a timer based on the validity period information; delete the SNPN's information from the prohibited list based on the timer's expiration; and perform cell selection for localized services, wherein the networks in the prohibited list are excluded from the target of the cell selection.

[0328] In the following, a non-volatile computer-readable medium storing one or more instructions for providing multicast services in wireless communication will be described according to some embodiments of this specification.

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

[0330] Some examples of storage media are coupled to a processor, allowing the processor to read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. For another example, the processor and storage media can reside as separate components.

[0331] Computer-readable media can include tangible and non-volatile computer-readable storage media.

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

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

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

[0335] The stored one or more instructions cause the processor to: receive validity period information for localized services for an Independent Non-Public Network (SNPN); receive a registration rejection message or a deregistration message; store the SNPN's information in a prohibited list based on the registration rejection message or the deregistration message; start a timer based on the validity period information; delete the SNPN's information from the prohibited list based on the timer's expiration; and perform cell selection for the localized service, wherein the network in the prohibited list is excluded from the target of the cell selection.

[0336] This instruction manual can have various effects.

[0337] For example, through the process disclosed in this specification, efficient SNPN selection can be performed by allowing terminals that have been rejected / cancelled from the SNPN to make a registration request to the SNPN after a period of time when the characteristics of the SNPN are considered.

[0338] The effects achievable through the specific examples in this specification are not limited to those listed above. For instance, there may be various technical effects that a person skilled in the art can understand or derive from this specification. Therefore, 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.

[0339] The claims described herein can be combined in various ways. For example, the technical features of the method claims of this specification can be combined and implemented as a device, and the technical features of the device claims of this specification can be combined and implemented as a method. Furthermore, the technical features of the method claims and the device claims of this specification can be combined and implemented as a device, and the technical features of the method claims and the device claims of this specification can be combined and implemented as a method. Other embodiments are within the scope of the appended claims.

Claims

1. A method of performing communication by a user equipment (UE), the method comprising: receiving, from a standalone non-public network (SNPN), validity time information for a localized service of the SNPN; receiving a registration reject message or a deregistration message; based on the registration reject message or the deregistration message, storing information of the SNPN in a barred list; starting a timer based on the validity time information; based on expiration of the timer, deleting the information of the SNPN from the barred list; and performing cell selection for the localized service, wherein networks in the barred list are excluded from a target of the cell selection. 2.The method of claim 1, the step of performing the cell selection is: wherein, selecting the SNPN based on the deletion of the information of the SNPN from the barred list. 3.The method of claim 2, the method further comprising: sending a registration request message to the SNPN based on the cell selection. 4.The method of any of claims 1-3, the validity time information includes information on a start time and an end time of a next validity time in which the localized service can be received. wherein 5.The method of claim 4, a timer value of the timer is based on a range between the start time and the end time. wherein 6.The method of any of claims 1-5, the method further comprising: sending, to the SNPN, information on a capability of the UE to access SNPNs, wherein the step of receiving the validity time information is performed based on the information on capability. 7.The method of any of claims 1-6, the validity time information is a service roaming steering (SoR) transparent container information. wherein 8.The method of any of claims 1-7, the step of receiving the validity time information is: wherein, receiving a downlink (DL) non-access stratum (NAS) transport message. 9.The method of any of claims 1-6, the registration reject message includes the validity time information. wherein 10.The method of any of claims 1-6, the deregistration message includes the validity time information. wherein 11.The method of any of claims 1-6, the step of receiving the validity time information is: wherein, receiving a registration accept message including the validity time information. 12.A method of performing communication by a standalone non-public network (SNPN), the method comprising: sending, to a user equipment (UE), validity time information for a localized service of the SNPN; sending a registration reject message or a deregistration message for the UE; and based on the validity time information, receiving a registration request message from the UE at a specific point in time. 13.The method of claim 12, the registration request message is based on cell selection for the SNPN performed by the UE. 14.The method of claim 12 or claim 13, wherein ​ ​ wherein The validity time information includes information on a start time and an end time of a next validity time in which the localized service can be received.

15. The method of any one of claims 12 to 14, the method further comprising: receiving, from the UE, information on a capability of the UE to support access to a SNPN, wherein the step of sending the validity time information is performed based on the information on the capability.

16. The method of any one of claims 12 to 15, wherein the validity time information is roaming steering SoR transparent container information.

17. The method of any one of claims 12 to 15, wherein the step of sending the validity time information is: sending a downlink, DL, non-access stratum, NAS, transport message.

18. The method of any one of claims 12 to 15, wherein, the registration reject message includes the validity time information.

19. The method of any one of claims 12 to 15, wherein, the de-registration message includes the validity time information.

20. The method of any one of claims 12 to 15, wherein, the step of sending the validity time information is: sending a registration accept message including the validity time information.

21. A user equipment, UE, for performing communication, the UE comprising: a transceiver; and a processor, wherein the processor performs operations as the method of one of claims 1 to 11.

22. A standalone non-public network, SNPN, for performing communication, the SNPN comprising: a transceiver; and a processor, wherein the processor performs operations as the method of one of claims 12 to 20.

23. An apparatus in mobile communication, the apparatus comprising: at least one processor; and at least one memory storing instructions and operatively connectable with the at least one processor, wherein based on the instructions operated by the at least one processor, the instructions perform operations as the method of one of claims 1 to 11.

24. A non-volatile computer-readable storage medium recording instructions, wherein, the instructions based on being executed by one or more processors cause the one or more processors to perform operations as the method of one of claims 1 to 11.

Images