Registration method through dual 3 GPP access

Abstract

One disclosure of the present specification provides a method by which a UDM performs communication. The method comprises the steps of: receiving dual registration-related information from a first AMF, wherein the dual registration-related information includes information indicating that a UE intends to perform dual registration through a first 3 GPP access and a second 3 GPP access, and the dual registration-related information includes information on a target network of registration through the second 3 GPP access; transmitting, to the UE, information indicating that the dual registration is possible on the basis of the dual registration-related information; receiving a registration request from a second AMF on the basis of the UE requesting registration through the second 3 GPP access from the second AMF; on the basis of the registration request from the second AMF, transmitting, to the first AMF, a message instructing deregistration of registration through the first 3 GPP access; and on the basis that the network of the second AMF corresponds to the target network, the UDM skipping transmitting a message indicating deregistration.

Description

How to register via dual 3GPP access

[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] For dual registration via dual 3GPP access, a method is needed to prevent deregistration of the 3GPP access for which registration was performed first.

[0006] The terminal transmits information about dual registration to the UDM, thereby preventing the UDM from performing deregistration for the 3GPP access for which registration was performed first.

[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] Figures 10 and 11 illustrate examples of flowcharts according to embodiments of the present specification.

[0015] Figure 12 illustrates the UDM procedure for the disclosure of this specification.

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

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

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

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

[0020] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, 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."

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

[0022] 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.”

[0023] 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”.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0040] 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), a recorder, or a black box.

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

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

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

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

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

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

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

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

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

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

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

[0052] 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 may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0102] - AUSF (Authentication Server Function)

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

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

[0105] - USDF (Unstructured Data Storage Function)

[0106] - NEF (Network Exposure Function)

[0107] - I-NEF (Intermediate NEF)

[0108] - NRF (Network Repository Function)

[0109] - NSSF (Network Slice Selection Function)

[0110] - PCF (Policy Control Function)

[0111] - SMF (Session Management Function)

[0112] - UDM (Unified Data Management)

[0113] - UDR (Unified Data Repository)

[0114] - UPF (User Plane Function)

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

[0116] - AF (Application Function)

[0117] - UE (User Equipment)

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

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

[0120] - NWDAF (Network Data Analytics Function)

[0121] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0149] <Registration Procedure>

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

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

[0152] 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:

[0153] - Initial registration for 5GS; or

[0154] - mobility registration update; or

[0155] - Periodic registration update; or

[0156] - Emergency registration

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

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

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

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

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

[0162] 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 the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in restricted service state).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0208] Dual 3GPP access

[0209] 1. Dual 5G satellite access

[0210] This use case describes a scenario where an autonomous ship is remotely controlled from shore. The ship has UEs served by two satellite RANs (GEO and LEO) belonging to the same PLMN managed by a 5G satellite operator. The ship's UEs have a single PLMN subscription.

[0211] Dual 5G satellite access will be deployed to accommodate the massive data traffic for remote control operations. To improve the performance of autonomous ship operations, delay-sensitive applications (e.g., remote control operations, collision / accident prevention, emergency management, etc.) will utilize LEO satellite links, which have lower UE-to-ground propagation delays than GEO satellite links (up to 30 ms for LEO vs. up to 280 ms for GEO). Other delay-sensitive applications (e.g., sensor data monitoring, video surveillance, etc.) can utilize GEO satellite links or aggregate traffic across both accesses.

[0212] 2. NTN-based dual 3GPP access

[0213] By integrating two 3GPP access links simultaneously, one of which is a non-terrestrial network, the following 5G services can be provided, which is particularly useful in isolated areas where bandwidth is limited or access links are unreliable:

[0214] - Expanded mobile broadband

[0215] - Very stable service communication

[0216] Several service scenarios (e.g., residential users in remote areas, users on vehicles, high-speed trains, ships, or airplanes) may benefit from combining terrestrial and non-terrestrial access, or from combining two types of non-terrestrial access (e.g., based on GSO and NGSO), to meet target service performance in terms of data rate and / or reliability.

[0217] In areas where service is unavailable, the bandwidth provided by terrestrial-based access (e.g., NR or LTE) may be limited at the cell edge. Adding NTN-based NG-RAN can help achieve the desired perceived data rates.

[0218] In some scenarios, such as on high-speed trains, the service area may not be completely uniform along the track, and multiple connections, including NTN-based NG-RAN, can provide the desired reliability.

[0219] Therefore, UEs can be connected and serviced simultaneously in the following ways:

[0220] - One NTN-based 3GPP access and one terrestrial-based 3GPP access

[0221] - One NTN-based 3GPP access (NGSO) and another NTN-based 3GPP access (GSO).

[0222] - One NTN-based 3GPP access (NGSO) via two different satellites in the same constellation

[0223] Dual access bonding can occur on the uplink, downlink, or both.

[0224] The same or different gNBs can serve NR cells via terrestrial access networks and satellite access networks (e.g., transparent payloads carried on satellites).

[0225] NTN-based NG-RAN can refer to transparent payload satellites as well as regenerative payload satellites equipped with, for example, some gNB functionality.

[0226] 3. Inter-PLMN or PLMN-SNPN

[0227] This example scenario depicts a stadium with an ad hoc / in-stadium 5G NR deployment (high capacity) from one SNPN or PLMN network (MNO-A) and 5G NR coverage from another PLMN outside the stadium (MNO-B). There is no network sharing between the two 5G networks.

[0228] The above example can be similarly applied to other local business locations such as campuses, companies, shopping malls, and factories.

[0229] MNO-B has a business and roaming partnership with MNO-A, including an agreement to lease additional capacity to provide ultra-broadband experiences to some of MNO-B's "golden" customers. The agreement between MNO-A and B includes the ability for MNO-B users' data traffic to utilize additional NR connectivity links in PLMN-A, enabling them to connect at higher data rates (including anchoring and aggregation to the HPLMN's CN). This capability is assumed to be supported by both PLMN's CNs and the UEs (of the golden MNO-B users). It involves a set of traffic policies and conditions negotiated by the MNOs, which the HPLMN controls and can provision (to UEs and CN entities).

[0230] A UE can receive services through two 3GPP accesses (or 3GPP access links).

[0231] Two 3GPP accesses may be connected to one Core Network (CN), or two 3GPP accesses may be connected to two CNs.

[0232] A CN can be a Public Land Mobile Network (PLMN) or a Non-Public Network (NPN).

[0233] For some services, a PDU session created by a terminal can be established via two 3GPP accesses. In this case, the PDU session may be a Multi-Access (MA) PDU session. Previously, an MA PDU session referred to a session via both a 3GPP access and a non-3GPP access, but the concept has now expanded to include two 3GPP accesses.

[0234] For some services, traffic can be steered, switched, and split across PDU sessions with two accesses.

[0235] Alternatively, for some services, a PDU session may be established over one 3GPP access and traffic may be transmitted over that session.

[0236] In dual access (or dual steer), a terminal may have a single subscription. In this case, conventionally, a terminal registered with only one core network for 3GPP access.

[0237] However, to receive services through two 3GPP accesses, a terminal can separately register for two 3GPP accesses for one 5G core network.

[0238] Alternatively, to receive services through two 3GPP accesses, the terminal may separately register with 3GPP access for each of the two 5G core networks.

[0239] A method may be proposed to support terminals to receive dual access (or dual steer) services.

[0240] The registration processing scheme for dual access (or dual steer) may consist of a combination of one or more of the actions / configurations / steps described below.

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

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

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

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

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

[0246] In this specification, the network may include a PLMN and a Non-Public Network (NPN).

[0247] In this specification, NPN may include both PNI-NPN (Public Network Integrated Non-Public Network) and SNPN (Stand-alone Non-Public Network), or may include only SNPN.

[0248] In this specification, PLMN may be interpreted to include PNI-NPN.

[0249] In this specification, the network identifier (or network identification information) may be a PLMN ID (or SNPN ID). The SNPN ID may be expressed as a PLMN ID and NID (Network Identifier or Network Identity).

[0250] The above network identifier (or network identification information) can be expressed as a parameter / information of PlmnIdNid as shown in Table 3. Table 3 shows the definition of the PlmnIdNid type.

[0251] Attribute nameData typePCardinalityDescriptionmccMccM1Mobile Country CodemncMncM1Mobile Network CodenidNidC0..1Network Identity; Shall be present if PlmnIdNid identifies an SNPN (see clauses 5.30.2.3, 5.30.2.9, 6.3.4, and 6.3.8 in 3GPP TS 23.501 v18.2.2). Otherwise, this attribute shall be absent.

[0252] 3GPP access in this specification may include or mean some or all of the RAT types (or radio technologies or access types or access link technologies or RAT information or 3GPP access types / information or 3GPP RAT types / information) as shown in Table 4. Table 4 shows a list of RatTypes.

[0253] Enumeration valueDescription"NR"New Radio"EUTRA"(WB) Evolved Universal Terrestrial Radio Access"WLAN"Untrusted Wireless LAN (IEEE 802.11) access"VIRTUAL"Virtual (see NOTE 1)"NBIOT"NB IoT"WIRELINE"Wireline access"WIRELINE_CABLE"Wireline Cable access"WIRELINE_BBF"Wireline BBF access"LTE-M"LTE-M (see NOTE 2)"NR_U"New Radio in unlicensed bands"EUTRA_U"(WB) Evolved Universal Terrestrial Radio Access in unlicensed bands"TRUSTED_N3GA"Trusted Non-3GPP access"TRUSTED_WLAN"Trusted Wireless LAN (IEEE 802.11) access"UTRA"UMTS Terrestrial Radio Access"GERA"GSM EDGE Radio Access Network"NR_LEO"NR (LEO) satellite access type"NR_MEO"NR (MEO) satellite access type"NR_GEO"NR (GEO) satellite access type"NR_OTHER_SAT"NR (OTHERSAT) satellite access type"NR_REDCAP"NR RedCap access type (see NOTE 3)NOTE 1: 신뢰할 수 없는 비 3GPP 접속에 사용된 접속 기술을 N3IWF가 모르는 경우 가상이 사용된다(Virtual shall be used if the N3IWF does not know the access technology used for an untrusted non-3GPP access.).NOTE 2: This RAT type value is used only in the Core Network; it shall be used when a Category M UE using E-UTRA has provided a Category M indication to the NG-RAN. NOTE 3: This RAT type value is used only in the Core Network; it shall be used only for an UE using NR with reduced radio capability provided to the NG-RAN.

[0254] The 3GPP access in this specification is not limited to the RAT types described above. The 3GPP access in this specification may be divided into various forms, more detailed forms, or multiple stages.

[0255] For example, 3GPP access in NR may be subdivided into Frequency Range (FR)1 and FR2.

[0256] For example, 3GPP access in NR may be divided into Terrestrial Network (TN) and Non-Terrestrial Network (NTN).

[0257] For example, if 3GPP access in NR is NTN, 3GPP access can be further subdivided into Geosynchronous Orbit (GEO), Medium Earth Orbit (MEO), Low Earth Orbit (LEO), etc.

[0258] In this specification, 3GPP access is described interchangeably with 3GPP RAT.

[0259] In this specification, services are described interchangeably with applications and traffic.

[0260] For a terminal to be dual-steered (or to receive dual-steer services or to transmit and receive traffic in a dual-steer fashion), it may need to connect to only two 3GPP access points.

[0261] The base stations of the above two 3GPP accesses may be the same or different. The CNs of the above two 3GPP accesses may be the same or different.

[0262] If the CNs of the two 3GPP accesses are the same, the serving AMFs of the two 3GPP accesses may be the same or different.

[0263] In this specification, dual steering support may be interpreted as dual registration support or dual 3GPP access support.

[0264] In this specification, dual registration may also be interpreted as registration for dual steering.

[0265] In this specification, MA (Multi-Access) is described interchangeably with DA (Dual-Access), DS (Dual Steer), Dual Steering, Dual 3GPP Access, and Multi 3GPP Access.

[0266] In this specification, MA (Multi-Access) PDU session is described interchangeably with DA (Dual-Access) PDU session, DS PDU session, dual steering PDU session, dual 3GPP access PDU session, multi 3GPP access PDU session, etc.

[0267] The above MA (Multi-Access) PDU session may be a PDU session that provides a PDU connectivity service, which can use one 3GPP access network at a time, or simultaneously two 3GPP access networks.

[0268] This specification mainly describes the proposed content.

[0269] For operations and procedures related to 5G systems, registration, PDU sessions, MA PDU sessions, and SoR (Steering of Roaming), TS 23.501 v18.2.2, TS 23.502 v18.2.0, TS 23.503 v18.2.0, and TS 23.122 v18.3.1 are basically referred to.

[0270] In this specification, with respect to the method of supporting dual steering, CN is mainly described with respect to 5G CN, but can also be applied to EPC.

[0271] In this specification, the proposed method is described mainly with respect to registration processing for using two 3GPP accesses, but it can also be applied to registration processing for using two non-3GPP accesses.

[0272] I. First Example

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

[0274] The procedures of Figures 8 and 9 illustrate that a UE registers via two 3GPP accesses for dual-steering. The procedures described herein focus on the proposed procedures, compared to existing registration procedures (see 4.2.2.2.2 General Registration of TS 23.502 v18.2.0 and Figures 6-7).

[0275] Serving Network#1 and Serving Network#2 may both be Home Networks or Visited Networks.

[0276] One of the serving networks, Serving Network#1 and Serving Network#2, may be the home network and the other serving network may be the visited network.

[0277] Serving Network#1 and Serving Network#2 may be the same (i.e., one) network or different networks.

[0278] Base station #a (NG-RAN#a) and base station #b (NG-RAN#b) may be the same NG-RAN or different NG-RANs.

[0279] AMF#a and AMF#b may be the same AMF or different AMFs.

[0280] Steps 1-2. The terminal can initiate a registration procedure with the first network (serving network #1) via the first 3GPP access. The terminal can send a registration request message to serving network #1. The registration request message can include information regarding the terminal's capability to register via dual 3GPP access.

[0281] Step 3. AMF#a, which has received the registration request message, can perform registration with UDM.

[0282] AMF#a can allocate a new 5G-GUTI (i.e., new 5G-GUTI information) for the terminal.

[0283] AMF#a may provide the above allocated 5G-GUTI to UDM.

[0284] At this time, if the terminal has a previously allocated 5G-GUTI or a GUTI allocated from EPS (i.e., old 5G-GUTI information), AMF#a can provide the GUTI to the UDM.

[0285] Alternatively, if the UE has previously allocated 5G-GUTI or GUTI allocated from EPS (i.e., old 5G-GUTI information), AMF#a may provide UDM with AMF identification information (e.g., GUAMI, AMF Identifier) ​​from previously allocated 5G-GUTI or MME identification information (e.g., Globally Unique MME Identifier (GUMMEI), MME Identifier) ​​from GUTI allocated from EPS.

[0286] The 5G-GUTI information in this specification may refer to the aforementioned AMF identification information and / or MME identification information.

[0287] AMF#a may provide the old 5G-GUTI information (provided if available, provided as a null / dummy value if not available, or indicating no information if not available, etc.) and the new 5G-GUTI information to the UDM. This action may be performed during this step or after this step (e.g., 4.2.2.2.2 General Registration of TS 23.502 v18.2.0 or step 24 of FIG. 7).

[0288] Since AMF already provides its Globally Unique AMF Identifier (GUAMI) to UDM, AMF may provide only the 5G-TMSI part of the new 5G-GUTI to UDM instead of additionally providing the new 5G-GUTI information itself.

[0289] AMF may also provide the above 5G-GUTI information to UDM only if AMF supports dual registration.

[0290] Step 4. UDM can respond to AMF#a's registration.

[0291] Steps 5-6. AMF#a can obtain subscriber information from UDM.

[0292] Step 7. AMF#a can subscribe to the UDM service to provide / be notified when subscriber information changes.

[0293] Step 8. AMF#a can send a Registration Accept message to the terminal.

[0294] Based on subscriber information and the dual registration capabilities of the terminal / network, AMF#a may determine that dual registration can be performed. The dual registration capabilities of the terminal may be information about the capabilities transmitted by the terminal in step 1.

[0295] Based on the above decision, the Registration Accept message may include information indicating that dual registration can be performed.

[0296] Step 9. The terminal may decide to perform dual registration.

[0297] Performing a dual registration may also be performing actions / procedures to receive dual steering services.

[0298] The terminal may decide to perform dual registration based on the information received in step 8 indicating that it can perform dual registration.

[0299] Dual registration may refer to connecting / connecting / registering via two 3GPP access / networks. This may be applied throughout this specification.

[0300] A terminal's decision to perform dual registration may be interpreted as i) deciding to receive dual steering service, ii) deciding to receive service via two 3GPP accesses (or dual 3GPP accesses), or iii) deciding to receive service via MA PDU session. This may be applied throughout this specification.

[0301] Step 9 may not be performed immediately after step 8.

[0302] For example, a terminal may decide to receive dual steering service after step 8 through serving network #1.

[0303] For example, the terminal may decide to receive a dual steering service after receiving a service by forming a PDU session after step 8.

[0304] Steps 10-11. The terminal can provide dual registration-related information to serving network #1 (AMF#a, ultimately UDM). This dual registration-related information can be provided explicitly, implicitly, in combination, or in a step-by-step manner. This dual registration-related information can include the following information:

[0305] a) Information indicating that the terminal wishes to perform dual registration: The information may be information indicating that the terminal wishes to perform registration with a second 3GPP access / network.

[0306] b) Network-related information for which the terminal wishes to perform dual registration: The network-related information may be identification information for the network targeted for dual registration. Additionally, the network-related information may include RAT information targeted for dual registration. In the case of FIG. 8, the network-related information may be identification information for serving network #2.

[0307] c) Timer value / information for dual registration (or timer value / information related to dual registration): The timer value / information may be based on an expected time required for the terminal to complete dual registration. The timer value / information may be set in the terminal. The timer value / information may be provided to the terminal at various times via various messages from the network (e.g., AMF) (e.g., via step 8, via a response message of step 10 / 11, etc.). When the terminal receives the timer value / information for dual registration from the network, the terminal may include the provided value as is in the dual registration-related information, may include a value desired by the terminal, or may include an acknowledgment for the value provided by the network.

[0308] A terminal may have a timer value / information set, allowing the terminal to transmit dual registration-related information including the timer value / information to network #1. In this case, the terminal may transmit the information and operate the timer based on the set timer value / information.

[0309] After providing dual registration-related information to serving network #1, the terminal may not perform or complete registration (i.e., dual registration) with serving network #2 until the timer for dual registration expires. In this case, if the terminal later decides to perform dual registration again, the terminal may re-provide dual registration-related information to serving network #1. After re-provision, the terminal may restart the timer.

[0310] A terminal can determine whether the network targeted for dual registration supports dual registration. This determination may be based on information provided by the network, terminal configuration information, etc.

[0311] If the network targeted for dual registration supports dual registration, the terminal can transmit dual registration-related information to the network.

[0312] If the network targeted for dual registration does not support dual registration, the terminal may transmit dual registration-related information to the network.

[0313] The terminal may also perform step 10 using conventional procedures / NAS messages. For this purpose, conventional procedures / NAS messages may be extended. For example, dual registration-related information may be included in the registration request message of the registration procedure, the service request message of the service request procedure, and the UL NAS transport message of the UL NAS transmission procedure.

[0314] Alternatively, the terminal may perform step 10 using a newly defined procedure / NAS message. For example, dual registration-related information may be transmitted in a newly defined UE-initiated SoR (Steering of Roaming) procedure, a dual registration execution notification procedure, etc. In the case of a UE-initiated SoR procedure, the dual registration-related information may be included in an SoR container.

[0315] The terminal may provide some or all of the dual registration related information described above to the AMF.

[0316] Step 12. AMF#a can forward dual registration-related information provided by the terminal to the UDM. AMF#a can provide the dual registration-related information provided by the terminal to the UDM in its original or modified form. AMF#a can also provide additional information to the dual registration-related information provided by the terminal to the UDM.

[0317] To perform Step 12, existing service operations may be extended or new service operations may be defined and used.

[0318] The UDM may send a response containing information to the terminal informing that the terminal's dual registration operation is permitted.

[0319] Additionally, the UDM can notify AMF#a that the dual registration operation of the terminal is allowed. Based on this, when the terminal performs registration in the future, AMF#a can determine that Nudm_UECM_Registration to the UDM is required and provide the terminal's 5G-GUTI and old 5G-GUTI information to the UDM.

[0320] Contrary to the above, UDM may not provide a response to the terminal.

[0321] After Step 11, AMF can provide a response to the terminal.

[0322] Alternatively, after Step 11, AMF can provide a response to the terminal, and after Step 12, UDM can provide a response to the terminal via AMF.

[0323] Step 13. UDM can start / run a timer for dual registration of the terminal.

[0324] Additionally, UDM can also set / enable DRPF (Dual Registration Proceed Flag) for the terminal.

[0325] Since the terminal is a terminal that is permitted (authorized) to perform dual registration, the above-mentioned actions (timer operation or DRPF setting / activation) may be performed.

[0326] The above-mentioned actions (timer driving or DRPF setup / activation) may be performed because the terminal has dual registration related capabilities.

[0327] The above mentioned timer values / information may be set in the UDM.

[0328] Or the terminal may have provided a timer value / information.

[0329] Or it could be provided by AMF#a.

[0330] The setup / activation of DRPF described above may not be performed.

[0331] Steps 14-15. The terminal can initiate a registration procedure with the second network via the second 3GPP access.

[0332] Based on the terminal receiving information indicating that dual registration operation is allowed, a registration procedure with a second network via a second 3GPP access can be performed.

[0333] Registering with a network via a second 3GPP access may also involve performing a procedure (newly defined procedure and / or NAS message) to add a second (serving) network (or second 3GPP access). This may be applied throughout this specification.

[0334] Step 16. AMF#b can perform registration with UDM. As described in step 3 above, AMF#b may also provide 5G-GUTI information to UDM. If AMF#b does not support dual registration, AMF#b may not provide 5G-GUTI information to UDM.

[0335] Based on the dual registration related information provided to UDM in step 12 and the information provided to UDM by AMF#b when registering, UDM can recognize / determine that the terminal has performed dual registration.

[0336] In particular, based on the b) information described in step 10 above included in the dual registration related information and the GUAMI information (including network identification information as defined in Table 5 or section 5.3.4.1 of TS 29.571 v18.2.0) provided by AMF#b while registering with UDM, UDM can recognize / determine whether the terminal has performed registration on the target network of dual registration.

[0337] Table 5 shows the definition of type GUAMI.

[0338] Attribute nameData typePCardinalityDescriptionplmnIdPlmnIdNidM1PLMN Identity and Network IdentityamfIdAmfIdM1AMF Identity

[0339] In case of non-dual registration, when registration is performed through the first 3GPP access and deregistration is performed through the second 3GPP access, in this case, UDM may send Nudm_UECM_DeregistrationNotification to the AMF associated with the first 3GPP access. Accordingly, deregistration may be performed for AMF#a (i.e., the AMF associated with the first 3GPP access). Nudm_UECM_DeregistrationNotification may be a message instructing AMF#a to deregister.

[0340] If the UDM recognizes / determines that the terminal has performed registration on the target network of dual registration, the UDM may decide not to perform deregistration for the old AMF (AMF#a).

[0341] If registration (step 16) is performed from AMF#b after the timer started in step 13 has expired, UDM may send Nudm_UECM_DeregistrationNotification to the AMF associated with the first 3GPP access, even though it is a dual registration. Accordingly, deregistration of the old AMF (i.e., the AMF associated with the first 3GPP access) may be performed.

[0342] If it is decided not to perform deregistration, UDM may decide not to send Nudm_UECM_DeregistrationNotification to AMF#a.

[0343] UDM's decision not to send Nudm_UECM_DeregistrationNotification to AMF#a may be interpreted as: UDM maintaining UE's registration with Serving Network#1 (or first 3GPP access / network), maintaining AMF's registration with Serving Network#1 (or first 3GPP access / network), or allowing / handling / supporting dual registration of UE.

[0344] UDM can reset / stop the timer for dual registration for a terminal and reset / clear / disable DRPF.

[0345] When dual registration of a terminal is performed / completed, the UDM may store that the terminal is in a dual registered state (or set information / flag indicating or marking that the terminal is in a dual registered state).

[0346] If the terminal performs registration on a network other than the target network of dual registration, UDM may decide to deregister the old AMF (i.e., send Nudm_UECM_DeregistrationNotification to the old AMF).

[0347] Based on the 5G-GUTI information provided by the new AMF (see step 3 above) or the new AMF not providing 5G-GUTI information, the UDM can infer the old AMF from which deregistration should be performed.

[0348] If both old 5G-GUTI information and new 5G-GUTI information are provided to the UDM, the UDM may deregister the AMF to which the old 5G-GUTI was assigned. If 5G-GUTI information is not provided to the UDM, the UDM may deregister any previously registered AMF that does not provide 5G-GUTI information.

[0349] In this way, if the terminal performs registration on a network other than the target network of dual registration, the timer and DRPF for dual registration can continue to run / maintain.

[0350] The operations of the UDM described above may be performed in parallel with step 17 or after step 17.

[0351] Step 17. UDM can respond to AMF's registration.

[0352] Steps 18~19. AMF can obtain subscriber information from UDM.

[0353] Step 20. AMF can subscribe to the UDM service to provide / be notified when subscriber information changes.

[0354] Step 21. AMF can send a Registration Accept message to the terminal.

[0355] If the UDM determines / determines that the terminal has not performed or completed registration with the network targeted for dual registration before the timer for dual registration expires, the UDM may reset / stop the timer for dual registration. In addition, the UDM may reset / clear / deactivate DRPF.

[0356] Based on the fact that the UDM has not received a message (e.g., a step 16 message) for registration with the AMF of the network that is the target of the dual registration before the timer for dual registration expires, the UDM may determine / decide that the terminal has not performed or completed registration with the network that is the target of the dual registration. This may be applied throughout this specification.

[0357] If Serving Network #1 and Serving Network #2 are different networks, Serving Network #2 may not support dual registration (or dual registration feature / procedure / behavior).

[0358] In this case, the registration procedure performed in steps 14 to 21 can be performed in the same manner as the registration procedure of the prior art.

[0359] That is, the registration procedure performed in steps 14 to 21 above may not be a registration procedure to support dual steering (or dual registration).

[0360] For example, since AMF#b is a conventional AMF that does not support dual registration as described in step 16, AMF#b may not provide 5G-GUTI information to UDM during registration. This may be applied throughout this specification.

[0361] II. Second Example

[0362] Figures 10 and 11 illustrate examples of flowcharts according to embodiments of the present specification.

[0363] Figures 10 and 11 illustrate that a terminal registers via two 3GPP accesses for dual steering. Each procedure is described primarily based on the contents / matters proposed in this specification, compared to the existing registration procedure (see 4.2.2.2.2 General Registration of TS 23.502 v18.2.0 and contents of Figures 6-7) and the SoR procedure (see Annex C (normative): Control plane solution for steering of roaming in 5GS of TS 23.122 v18.3.0).

[0364] Serving Network#1 and Serving Network#2 may both be Home Networks or Visited Networks.

[0365] One of the serving networks, Serving Network#1 and Serving Network#2, may be the home network and the other serving network may be the visited network.

[0366] Serving Network#1 and Serving Network#2 may be the same (i.e., one) network or different networks.

[0367] Base station #a (NG-RAN#a) and base station #b (NG-RAN#b) may be the same NG-RAN or different NG-RANs.

[0368] AMF#a and AMF#b may be the same AMF or different AMFs.

[0369] Steps 1-8. The contents of steps 1 to 8 of the first embodiment can be applied.

[0370] Step 9. UDM can initiate SoR procedure to the terminal.

[0371] In FIGS. 10 and 11, the SoR procedure is shown as being performed after registration, but the SoR procedure may also be initiated during the registration procedure.

[0372] UDM can transmit SoR related information to AMF.

[0373] Step 10. AMF can transmit SoR-related information received from UDM to the terminal.

[0374] SoR related information may include information indicating that the terminal can perform dual registration.

[0375] Not only the terminal, but also the AMF can recognize that the terminal's dual registration operation is allowed through SoR-related information (step 10).

[0376] Based on the SoR related information, when the terminal performs registration and the AMF needs to perform Nudm_UECM_Registration with the UDM, the AMF can provide the terminal's 5G-GUTI and old 5G-GUTI information to the UDM.

[0377] Step 11. The terminal may decide to perform dual registration at or before step 11.

[0378] In this case, the terminal may provide dual registration related information (refer to steps 10-11 of the first embodiment) to the network / UDM. The timer value / information for dual registration may be based on the information provided by the UDM to the UE in step 9.

[0379] When the UDM requests an Acknowledgement for SoR information from the UE, the UE may provide the aforementioned dual registration-related information while transmitting the Acknowledgement.

[0380] Step 12. AMF can forward dual registration related information from UE to UDM.

[0381] Steps 13-21. The contents of steps 13-21 of the first embodiment can be applied.

[0382] Even if a visited network does not support dual steering / dual registration, a terminal can use this network as a single 3GPP access / network to receive dual steering services. This can also be applied to the first embodiment.

[0383] The following actions can be taken to support registration for dual steering:

[0384] - The UE can perform registration with the first network via the first 3GPP access.

[0385] - The UE may notify the primary network that it wishes to perform dual registration with UDM. At this time, information related to dual registration may be provided to UDM.

[0386] - The UDM can recognize / determine that the UE will perform dual registration. Accordingly, it can start a timer related to dual registration.

[0387] - The UE can perform registration with a second network via a second 3GPP access.

[0388] - The serving AMF of the second network can perform registration with UDM.

[0389] - The UDM may recognize / determine that the UE is registering with the target network of dual registration. Accordingly, the UDM may decide not to deregister with the serving AMF of the primary network.

[0390] - UDM can stop the timer related to dual registration.

[0391] 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, and 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.

[0392] Figure 12 illustrates the UDM procedure for the disclosure of this specification.

[0393] 1. The UDM can receive a registration request from the first AMF (Access Mobility Function) based on a UE (User Equipment) requesting registration through the first 3GPP (3rd Generation Partnership Project) access.

[0394] 2. The UDM can receive dual registration related information from the first AMF.

[0395] The above dual registration related information may include information indicating that the UE wishes to perform dual registration via the first 3GPP access and the second 3GPP access.

[0396] The above dual registration related information may include information about a target network for registration via the second 3GPP access.

[0397] 3. Based on the above dual registration related information, the UDM can transmit information indicating that the dual registration is possible to the UE.

[0398] 4. Based on the UE requesting registration to the second AMF via the second 3GPP access, the UDM can receive a registration request from the second AMF.

[0399] 5. Based on the registration request from the second AMF, the UDM may send a message to the first AMF instructing deregistration for registration via the first 3GPP access.

[0400] Based on the network of the second AMF corresponding to the target network, the UDM may skip sending a message indicating deregistration.

[0401] Based on receiving the above dual registration related information, the UDM can start the dual registration timer.

[0402] Based on the expiration of the above dual registration timer, the UDM may again receive dual registration related information from the first AMF.

[0403] Based on receiving the above dual registration related information again, the UDM can restart the dual registration timer.

[0404] Based on receiving a registration request from the second AMF after the dual registration timer expires, the UDM may not skip sending a message indicating deregistration even if the information of the target network includes information of the network of the second AMF.

[0405] The above dual registration related information may include the value of the dual registration timer.

[0406] The step of driving the above dual registration timer can be performed based on the value of the above dual registration timer.

[0407] 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, and 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.

[0408] Figure 13 illustrates the UE's procedure for disclosure of this specification.

[0409] 1. The UE may send a first registration request to the first AMF via the first 3GPP (3rd Generation Partnership Project) access.

[0410] The first registration request may include information about the capability of the UE to register via two 3GPP accesses.

[0411] 2. Based on the information about the above capabilities, the UE can receive information indicating that registration is possible through two 3GPP accesses from the first AMF.

[0412] 3. Based on the information indicating that registration is possible via the two 3GPP accesses, the UE may decide to perform registration via the first 3GPP access and the second 3GPP access.

[0413] 4. The UE may transmit dual registration related information including information about the decision to the first AMF.

[0414] The above dual registration related information may include information about a target network for registration via the second 3GPP access.

[0415] 5. Based on the above decision, the UE may send a second registration request to the second AMF via the second 3GPP access.

[0416] The network of the above second AMF may correspond to the target network.

[0417] The above dual registration related information may include information about a dual registration timer.

[0418] Based on transmitting the above dual registration related information, the UE can start the dual registration timer.

[0419] Based on the step of transmitting the second registration request being performed after the dual registration timer expires, the UE can retransmit the dual registration related information after the dual registration timer expires.

[0420] Based on the retransmission of the above dual registration related information, the UE may restart the dual registration timer.

[0421] The step of receiving information indicating that registration is possible via the above two 3GPP accesses comprises: the UE can receive an acknowledgment message for the first registration request.

[0422] The above approval message may include information indicating that registration via the two 3GPP accesses is possible.

[0423] The step of receiving information indicating that registration is possible via the above two 3GPP accesses is: the UE can receive a transport message including SoR (Steering of roaming) related information.

[0424] The above transport message may include information indicating that registration is possible via the two 3GPP accesses.

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

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

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

[0428] The operations performed by the processor include: transmitting a first registration request to a first AMF via a first 3GPP access; the first registration request including information about the capability of the UE to register via two 3GPP accesses, and receiving information from the first AMF indicating that registration via two 3GPP accesses is possible; determining to perform registration via the first 3GPP access and a second 3GPP access; transmitting dual registration related information including information about the determination to the first AMF; the dual registration related information including information about a target network of registration via the second 3GPP access, and transmitting a second registration request to a second AMF via the second 3GPP access, wherein the network of the second AMF may correspond to the target network.

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

[0430] The operations performed by the processor include: transmitting a first registration request to a first AMF via a first 3GPP access; the first registration request including information about the capability of the UE to register via two 3GPP accesses, and receiving information from the first AMF indicating that registration via two 3GPP accesses is possible; determining to perform registration via the first 3GPP access and a second 3GPP access; transmitting dual registration related information including information about the determination to the first AMF; the dual registration related information including information about a target network of registration via the second 3GPP access, and transmitting a second registration request to a second AMF via the second 3GPP access, wherein the network of the second AMF may correspond to the target network.

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

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

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

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

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

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

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

[0438] The stored one or more commands comprise: transmitting a first registration request to a first AMF via a first 3GPP access; wherein the first registration request includes information about a capability of the UE to register via two 3GPP accesses, and receiving information from the first AMF indicating that registration via two 3GPP accesses is possible; determining to perform registration via the first 3GPP access and a second 3GPP access; transmitting dual registration related information including information about the determination to the first AMF; wherein the dual registration related information includes information about a target network of registration via the second 3GPP access, and transmitting a second registration request to a second AMF via the second 3GPP access, wherein the network of the second AMF may correspond to the target network.

[0439] This specification may have various effects.

[0440] For example, dual registration via dual 3GPP access can be performed through the procedures disclosed herein.

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

[0442] 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. As a method of performing communication through UDM (Unified Data Management), A step of receiving a registration request from a first AMF (Access Mobility Function) based on a UE (User Equipment) requesting registration through a first 3GPP (3rd Generation Partnership Project) access; A step of receiving dual registration related information from the first AMF; The above dual registration related information includes information indicating that the UE wants to perform dual registration through the first 3GPP access and the second 3GPP access, The above dual registration related information includes information about the target network of registration via the second 3GPP access, A step of transmitting information indicating that dual registration is possible to the UE based on the dual registration related information; A step of receiving a registration request from the second AMF based on the UE requesting registration to the second AMF via the second 3GPP access; A step of transmitting a message to the first AMF instructing deregistration for registration through the first 3GPP access based on a registration request from the second AMF; A method in which the UDM skips sending a message indicating deregistration based on the network of the second AMF corresponding to the target network.

2. In paragraph 1, A method further comprising the step of driving a dual registration timer based on receiving the dual registration related information.

3. In paragraph 2, A step of re-receiving dual registration related information from the first AMF based on the expiration of the dual registration timer; A method further comprising the step of re-starting the dual registration timer based on re-receiving the dual registration related information.

4. In paragraph 2, A method in which the UDM does not skip sending a message instructing deregistration based on receiving a registration request from the second AMF after the dual registration timer expires, even if the information of the target network includes information of the network of the second AMF.

5. In any one of the clauses 2 to 4, The above dual registration related information includes the value of the dual registration timer, A method in which the step of driving the above dual registration timer is performed based on the value of the above dual registration timer.

6. As a method for UE (User Equipment) to perform communication, A step of transmitting a first registration request to the first AMF via the first 3GPP (3rd Generation Partnership Project) access; The above first registration request includes information about the capability of the UE to register via two 3GPP accesses, A step of receiving information indicating that registration is possible through two 3GPP accesses from the first AMF based on information about the above capabilities; A step of determining to perform registration through the first 3GPP access and the second 3GPP access based on information indicating that registration is possible through the two 3GPP accesses; A step of transmitting dual registration related information including information about the decision to the first AMF; The above dual registration related information includes information about the target network of registration via the second 3GPP access, Based on the above decision, comprising the step of transmitting a second registration request to the second AMF via the second 3GPP access, The network of the above second AMF is a method corresponding to the target network.

7. In paragraph 2, The above dual registration related information includes information about the dual registration timer, A step of driving the dual registration timer based on transmitting the dual registration related information; A method further comprising a step of retransmitting the dual registration related information after the dual registration timer expires, based on the step of transmitting the second registration request being performed after the dual registration timer expires.

8. In paragraph 7, A method further comprising the step of re-starting the dual registration timer based on re-transmitting the dual registration related information.

9. In any one of the clauses 6 to 8, The step of receiving information indicating that registration is possible through the above two 3GPP accesses is: the step of receiving an approval message for the first registration request, A method wherein the above approval message includes information indicating that registration is possible via the two 3GPP accesses.

10. In any one of the clauses 6 to 8, The step of receiving information indicating that registration is possible through the above two 3GPP accesses is: the step of receiving a transport message including SoR (Steering of roaming) related information, A method wherein the above transport message includes information indicating that registration is possible via the two 3GPP accesses.

11. As a UDM (Unified Data Management) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a UDM method according to any one of claims 1 to 5.

12. 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 6 to 10.

13. 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 at least one processor is a method according to any one of claims 1 to 5.

14. 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 5.

Images