Communication related to network slice group

Abstract

An embodiment of the present disclosure provides a method by which an AMF performs communication. The method may comprise the steps of: receiving, from a UE, a registration request message including a requested NSSAI; transmitting a request message related to a network slice to a slice-related network entity; receiving a response message including information on whether a slice list satisfies a condition related to a slice group from the network entity; and transmitting, on the basis of the response message, a registration acceptance message including allowed NSSAI to the UE.

Description

Communication related to network slice groups

[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, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) 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] Support for network slice concurrent registration groups is needed. However, prior art suffers from the inefficient application of network slice concurrent registration groups to a single UE. This hinders the effective provision of services based on network slice concurrent registration groups to UEs.

[0006] According to one embodiment of the present disclosure, a method for an AMF to perform communication is provided. The method may include: receiving a registration request message including a requested NSSAI from a UE; transmitting a request message related to a network slice to a slice-related network entity; receiving a response message from the network entity including information on whether the slice list satisfies a condition related to a slice group; and transmitting a registration acceptance message including an allowed NSSAI to the UE based on the response message.

[0007] According to one embodiment, a device implementing the method is provided.

[0008] According to one embodiment of the present disclosure, a method for a network entity related to a slice to perform communication is provided. The method may include the steps of: receiving a request message related to a network slice from an AMF; determining whether the list of slices included in the request message satisfies a condition related to a slice group; and transmitting a response message to the AMF including information on whether the condition related to the slice group is satisfied.

[0009] According to one embodiment, a device implementing the method is provided.

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

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

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

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

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

[0015] Figure 7 is an example diagram showing an example of an architecture for implementing the concept of network slicing.

[0016] Figure 8 is an exemplary diagram showing another example of an architecture for implementing the concept of network slicing.

[0017] FIG. 9 illustrates an example of dual 5G satellite access according to one embodiment of the disclosure of the present specification.

[0018] FIG. 10 illustrates an example of traffic switching according to one embodiment of the disclosure of the present specification.

[0019] FIG. 11a illustrates a first example of multiple connections according to an embodiment of the disclosure of the present specification. FIG. 11b illustrates a second example of multiple connections according to an embodiment of the disclosure of the present specification. FIG. 11c illustrates a third example of multiple connections according to an embodiment of the disclosure of the present specification. FIG. 11d illustrates a fourth example of multiple connections according to an embodiment of the disclosure of the present specification.

[0020] FIG. 12 is an example of a single 3GPP access connection according to one embodiment of the disclosure of the present specification.

[0021] FIG. 13 is an example of a dual 3GPP access connection according to one embodiment of the disclosure of the present specification.

[0022] Figure 14 is an example of limiting the allowed NSSAI.

[0023] Figure 15 is an example of limiting a PDU session.

[0024] Figures 16a and 16b are examples of a procedure according to the first example of the disclosure of the present specification.

[0025] FIG. 17a and FIG. 17b are examples of a procedure according to the second example of the disclosure of the present specification.

[0026] FIG. 18 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0027] 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 Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using 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 Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes 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).

[0028] 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, but aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0043] The wireless devices (100a to 100f) represent 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. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) 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.

[0044] 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 function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

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

[0046] 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, D2D (Device-To-Device) communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). 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.

[0047] NR supports multiple numerologies, or subcarrier spacings (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.

[0048] 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 the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] 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 code, instructions 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.

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

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

[0066] 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. 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.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0068] 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 disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

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

[0071] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this 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 this specification or to control a transceiver (106) to perform UE operations according to the implementation of this 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 this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0085] - AUSF (Authentication Server Function)

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

[0087] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0088] - USDF (Unstructured Data Storage Function)

[0089] - NEF (Network Exposure Function)

[0090] - I-NEF (Intermediate NEF)

[0091] - NRF (Network Repository Function)

[0092] - NSSF (Network Slice Selection Function)

[0093] - PCF (Policy Control Function)

[0094] - SMF (Session Management Function)

[0095] - UDM (Unified Data Management)

[0096] - UDR (Unified Data Repository)

[0097] - UPF (User Plane Function)

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

[0099] - AF (Application Function)

[0100] - UE (User Equipment)

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

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

[0103] - NWDAF (Network Data Analytics Function)

[0104] - CHF (CHarging Function)

[0105] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0135] - Initial registration for 5GS; or

[0136] - mobility registration update; or

[0137] - Periodic registration update; or

[0138] - Emergency registration

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

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

[0141] First, the procedure of Fig. 5 is described.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0172] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0190] Network Slice

[0191] Below, we explain network slicing to be introduced in next-generation mobile communications.

[0192] Next-generation mobile communications introduce the concept of network slicing to provide diverse services through a single network. Here, a network slicing refers to a combination of network nodes with the functions necessary to provide a specific service. The network nodes that make up a slice instance can be either hardware-independent or logically independent.

[0193] Each slice instance can be composed of any combination of nodes required to form the entire network. In this case, a single slice instance can provide services to a UE independently.

[0194] Alternatively, a slice instance may be composed of a combination of nodes within the network. In this case, the slice instance may not provide services to the UE independently, but may instead collaborate with other existing network nodes to provide services to the UE. Furthermore, multiple slice instances may collaborate to provide services to the UE.

[0195] Slice instances differ from dedicated core networks in that the entire network, including the core network (CN) nodes and the RAN, can be separated. Furthermore, slice instances differ from dedicated core networks in that network nodes can be logically separated.

[0196] Note that for network slices, quotas can be used.

[0197] For example, a quota associated with a network slice may include a quota for a maximum number of UEs. The quota for the maximum number of UEs may refer to the maximum number of terminals that can simultaneously use the network slice. For example, each network slice information may include quota information for a maximum number of UEs (e.g., 10, 1,000,000, etc.).

[0198] For example, a quota associated with a network slice may include a quota for the maximum number of PDU sessions. The quota for the maximum number of PDU sessions may refer to the maximum number of concurrent PDU sessions supported by the network slice. For example, the maximum number of concurrent PDU sessions supported by the network slice may refer to the maximum number of PDU sessions that can be simultaneously established within a network slice associated with a Data Network Name (DNN) defined by the S-NSSAI.

[0199] In 5G mobile communications, network slice quota event notifications may be supported within a network slice. For example, event notifications regarding quotas related to a network slice may be supported. For example, an AF may request an event notification regarding quotas related to a network slice from 5GS. Then, the AF may receive quota notifications for attributes related to the network slice from 5GS. For example, the 5GS may notify the AF whether the quota for a specific attribute has reached a specified threshold. Then, the AF may influence 5GS routing decisions.

[0200] Figure 7 is an example diagram showing an example of an architecture for implementing the concept of network slicing.

[0201] As can be seen from Figure 7, a core network (CN) can be divided into multiple slice instances. Each slice instance can include one or more CP functional nodes and UP functional nodes.

[0202] Each UE can use a network slice instance suitable for its service through the RAN.

[0203] Unlike the example shown in FIG. 7, each slice instance may share one or more of the CP function nodes and UP function nodes with other slice instances. This is described below with reference to FIG. 8.

[0204] Figure 8 is an exemplary diagram showing another example of an architecture for implementing the concept of network slicing.

[0205] Referring to FIG. 8, multiple UP function nodes are clustered, and similarly multiple CP function nodes are clustered.

[0206] And, referring to FIG. 8, slice instance #1 (or referred to as instance #1) within the core network includes a first cluster of UP functional nodes. And, the slice instance #1 shares a cluster of CP functional nodes with slice #2 (or referred to as instance #2). The slice instance #2 includes a second cluster of UP functional nodes.

[0207] The illustrated NSSF selects a slice (or instance) that can accommodate the UE's service.

[0208] The illustrated UE can use service #1 through slice instance #1 selected by the NSSF, and can also use service #2 through slice instance #2 selected by the N.

[0209] In 3GPP, a study called FS_DualSteer (Study on Upper layer traffic steering, switching, and split over dual 3GPP access - SP-220445) is being discussed. Dual Steer can include use cases and service requirements related to steering, splitting, and switching UE traffic over two 3GPP access links, for example. Specifically, the study is being conducted for the following objectives. For examples of use cases and service requirements, please refer to TR 22.841 V1.1.0 "Study on Upper layer traffic steer, switch, and split over dual 3GPP access."

[0210] Examples of Objectives related to dual steering include:

[0211] Additional use cases and potential service requirements that could benefit from UE traffic support for higher layer steering, split and switching (e.g., related to the same data session) in 5GS are studied, assuming only a single subscription to two 3GPP access links, including the following scenarios:

[0212] - Single PLMN, PLMN plus (standalone) NPN, 2 PLMNs

[0213] - Same or different 3GPP RAT (add NR or NTN, or NR, NTN, or LTE)

[0214] Note: NTN can refer to NR-based satellite access, including various orbits (e.g., GEO / MEO / LEO), which stand for Geostationary Earth Orbit (GEO), Medium Earth Orbit (MEO), and Low Earth Orbit (LEO), respectively.

[0215] For the PLMN plus PLMN / NPN scenario, the two networks can be managed by the same operator or by different operators (assuming there is a business agreement between the operators).

[0216] The study related to dual steering includes a gap analysis regarding the support of use cases identified by existing service requirements and functions, including the potential applicability of existing multi-NW requirements (e.g., TS 22.261 V19.3.0 Sections 6.1, 6.3, 6.18, 6.41).

[0217] An example use case for TR 22.841 V1.1.0 is as follows:

[0218] Describes an example of a dual 5G satellite access use case in a maritime scenario.

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

[0220] 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 (LEO up to 30 ms vs. GEO up to 280 ms, TS 22.261 V19.3.0, Section 7.4.1). Other delay-sensitive applications (e.g., sensor data monitoring, video surveillance, etc.) can utilize GEO satellite links or aggregate traffic across both accesses.

[0221] The following prerequisites may apply for this use case:

[0222] An example of an autonomous ship is the Korean Autonomous Surface Ship (KASS). This autonomous ship can support dual 5G satellite connectivity (GEO and LEO).

[0223] UEs installed on autonomous ships have subscriptions to use GEO and LEO satellite services from 5G satellite operators.

[0224] UEs installed on autonomous ships register and connect to GEO and LEO satellite RANs.

[0225] According to the service agreement between the autonomous vessel management company and the 5G satellite operator, the 5G satellite network has the following policies for the autonomous vessel's UE:

[0226] - Data traffic for latency-sensitive applications is routed over LEO satellite links whenever available.

[0227] - Data traffic for delay-tolerant applications is aggregated across LEO and GEO satellite links.

[0228] For use cases related to autonomous ships, a service flow like the example below can be applied.

[0229] Referring to FIG. 9, a specific example of dual 5G satellite access in autonomous vessel operation is illustrated.

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

[0231] FIG. 9 illustrates an example of dual 5G satellite access according to one embodiment of the disclosure of the present specification.

[0232] 1. The autonomous vessel is at sea and can be remotely controlled by a shore control center. The autonomous vessel can have two active data sessions: one for remote control operations and one for sensor data monitoring. According to agreed-upon policies, remote control operation traffic (e.g., delay-sensitive traffic) is routed via LEO satellite links, while sensor data monitoring traffic (e.g., delay-tolerant traffic) is aggregated across LEO and GEO satellite links.

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

[0234] FIG. 10 illustrates an example of traffic switching according to one embodiment of the disclosure of the present specification.

[0235] The example in Figure 10 illustrates an example of traffic diversion due to a loss of connection with a LEO satellite access network.

[0236] 2. If LEO satellite access becomes unavailable (e.g., due to loss of line of sight between the UE and the satellite), all traffic routed via LEO satellite access will be shifted to GEO satellite access while maintaining data session continuity. Applications for ship remote control (delay-sensitive) will detect increased communication latency and adjust their operations accordingly.

[0237] 3. After a while, LEO satellite access becomes available again. Therefore, the traffic distribution between the two satellite accesses returns to the same state as in Step 1.

[0238] The postconditions are as follows: the remote control center controls the autonomous ship throughout the route, and the autonomous ship successfully reaches its destination.

[0239] Describes an example of an existing feature that encompasses some or all of the use case functionality.

[0240] The ATSSS feature specified in TS 23.501 V17.2.2 section 5.32 supports dual user plane connectivity between the UE and the data network using one 3GPP access network and one non-3GPP access network.

[0241] 5G systems should be able to dynamically offload portions of traffic based on operator policies, taking into account traffic load and traffic type (e.g., offloading from 3GPP RATs to non-3GPP access technologies).

[0242] Depending on operator policy, 5G systems must be able to provide simultaneous data transmission over different access technologies (e.g., NR, E-UTRA, non-3GPP) to access one or more 3GPP services.

[0243] When a UE uses two or more access technologies simultaneously, the 5G system must be able to optimally distribute user traffic by selecting one of the access technologies in use, taking into account the service, traffic characteristics, radio characteristics, and the UE's movement speed.

[0244] 5G systems must support UEs with multi-radio and single-radio capabilities.

[0245] 5G systems must be able to provide services using satellite access.

[0246] A 5G system capable of satellite access must support a variety of configurations where the radio access network is a satellite NG-RAN, a non-3GPP satellite access network, or both.

[0247] Potential new requirements needed to support this use case could include, for example: The 5G system must support mechanisms to steer, split, and switch user plane traffic across two 5G satellite access networks belonging to the same PLMN, with the user plane traffic anchored to the 5GC.

[0248] A use case for NTN-based dual 3GPP access is described.

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

[0250] - Expanded mobile broadband

[0251] - Ultra Reliable Service Communication

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

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

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

[0255] Therefore, one UE can be connected and served simultaneously by the following examples:

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

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

[0258] - One NTN-based 3GPP access (NGSO) via two different satellites of the same constellation.

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

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

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

[0262] With reference to the following Figures 11a to 11d, examples of a) to d) are described.

[0263] a) Multi-connectivity including transparent payload NTN-based NG-RAN and terrestrial NG-RAN;

[0264] The UE connects to the 5GCN simultaneously via two access points (e.g., a transparent NTN-based NG-RAN and a cellular NG-RAN). It is assumed that the NTN gateway is located in the PLMN area of ​​the cellular access network.

[0265] Referring to the examples of FIGS. 11a and 11b, an example of multi-connectivity including a transparent payload NTN-based NG-RAN and a terrestrial NG-RAN is described.

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

[0267] FIG. 11A is a first example of multiple connections according to one embodiment of the disclosure of the present specification.

[0268] In the example of Figure 11a, different operators may manage two PLMNs for multi-connectivity (assuming there is a business agreement between the two operators).

[0269] The example in Fig. 11a is an example of multi-connectivity including different PLMNs of transparent NTN-based NG-RAN and cellular NG-RAN.

[0270] As illustrated in Figure 11a, the UE may be connected to access based on a transparent NTN-based NG-RAN (e.g., access via a satellite, NTN gateway, gNB, or 5G CN of a first operator). Additionally, the UE may be connected to access based on a terrestrial NG-RAN connected to a 5G CN of a second operator.

[0271] Alternatively, as in the example of Figure 11b, the two accesses for multi-connectivity may be managed by the same operator.

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

[0273] FIG. 11b is a second example of multiple connections according to one embodiment of the disclosure of the present specification.

[0274] In the example of Figure 11b, PLMNs may be managed by the same operator. Figure 11b illustrates multi-connectivity (same PLMN) including a transparent NTN-based NG-RAN and a cellular NG-RAN.

[0275] b) Multi-connectivity including two transparent NTN-based NG-RAN accesses.

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

[0277] FIG. 11c is a third example of multiple connections according to one embodiment of the disclosure of the present specification.

[0278] The example in Fig. 11c shows multi-connectivity between two transparent NTN-based NG-RANs.

[0279] For example, referring to Figure 11c, multi-connectivity may include a combination of two transparent NTN-based NG-RANs (e.g., GSO and NGSO-based). This may be useful for providing service to UEs in areas where services are not available. The example of Figure 11c may utilize a relatively low-latency NGSO-based NG-RAN to support delay-sensitive traffic, and a GSO-based NG-RAN that provides additional bandwidth to meet target throughput requirements.

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

[0281] FIG. 11d is a fourth example of multiple connections according to one embodiment of the disclosure of the present specification.

[0282] Figure 11d shows an example of multi-connectivity between two regenerative NTN-based NG-RANs (e.g., onboard gNBs).

[0283] An example according to Fig. 11d is an example of a case where two regenerative NTN-based NG-RANs (gNB on board) are combined with an inter-satellite link via two satellites of the same constellation.

[0284] Note that Figure 11d is for illustrative purposes only. Other architectures (e.g., a split NG-RAN architecture between satellite and terrestrial) may be considered. SRI represents the satellite radio interface in Figure 11d.

[0285] Examples of preconditions relevant to this use case include:

[0286] There may be some coverage overlap between the two NG-RAN access links involved.

[0287] If the PLMN of both access links is the same, the UE connects to the 5GC that provides both access links.

[0288] 5GC knows the characteristics of each of the two access links.

[0289] When different PLMNs are used for each access link, the UE gains access to other networks through roaming agreements. Information about each access link's characteristics can be exchanged between the two networks.

[0290] The UE is in connected mode on one or more of the access links.

[0291] Slices can be deployed and managed on both access links.

[0292] An example service flow related to this use case is as follows:

[0293] A UE may establish a VoIP, video, or data service over a single 3GPP access link, but its QoS (e.g., throughput, latency, etc.) may be inadequate. If another 3GPP access link becomes available, it will be activated and combined with the first link to support the required QoS for the service.

[0294] Depending on the target QoS of the service, the user plane traffic of the connection can be intelligently steered, split and switched bidirectionally between two 3GPP NG-RAN access links based on the specific performance of each access link, such as latency, throughput, jitter and error rate.

[0295] QoS requirements for user plane traffic can be determined through specific policies associated with different data flows or different traffic types within the same data flow.

[0296] Traffic is steered / segmented between access links based on QoS requirements (e.g., latency, throughput, jitter, error rate), traffic characteristics, wireless link conditions, and the UE's mobility speed. For example, traffic requiring low latency may be best steered / segmented to the access link with the lowest latency characteristics.

[0297] In the event of a handover, temporary radio link failure, or congestion on one access link, user plane traffic can be switched to the remaining active access link. Once the radio link is re-established, user plane traffic is split and steered across the two access links based on QoS.

[0298] Data volume and other traffic statistics reported on each access link are used for billing purposes.

[0299] According to the postcondition, due to appropriate steering, splitting and switching of user plane traffic, dual NG-RAN access connections with minimal NTNs can support targeted QoS that a single access cannot support.

[0300] Examples of existing features that partially or fully encompass the use case functionality include:

[0301] This use case can leverage and extend some of the existing service requirements, including:

[0302] - Multiple access technology (see TS 22.261 V19.3.0 S6.3)

[0303] - Multi-network connection and service provision between operators (refer to TS 22.261 V19.3.0 S6.18)

[0304] -NW slice (see S6.1 of TS 22.261 V19.3.0)

[0305] - Efficient user plane (see S6.5 of TS 22.261 V19.3.0)

[0306] Potential new requirements to support the 5.5.6 use case include, for example:

[0307] Based on the use of at least one NR satellite RAT, the 5G system should be able to support simultaneous data transmissions by UEs associated with the same data session on two 3GPP 5G access networks, subject to operator policy. Based on the connection conditions (e.g., radio characteristics, mobility, congestion) of the two access networks and the UE's movement speed, the 5G system can optimally distribute user traffic between the two access networks.

[0308] When two 5G access networks are used simultaneously for the same data session, the 5G system can collect charging information for both links simultaneously.

[0309] Note that if the two 5G access networks belong to different PLMNs, single subscription and data anchoring on the HPLMN 5G CN is assumed.

[0310] Hereinafter, with reference to FIGS. 12 and 13, the use cases of the PLMN-to-PLMN scenario or the PLMN-SNPN scenario will be described.

[0311] This example scenario illustrates a stadium scenario where an ad-hoc / in-venue 5G NR deployment (high-capacity) is provided by one SNPN or PLMN network (MNO-A) and 5G NR coverage is provided by another PLMN outside the stadium (MNO-B). There is no network sharing between the two 5G networks. In this case, the MNO is the Mobile Network Operator.

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

[0313] MNO-B has a business and roaming partnership with MNO-A, which includes an agreement to lease additional capacity (from MNO-A) to provide ultra-broadband experiences to certain MNO-B special customers (e.g., "golden" customers). The agreement between MNO-A and B includes the ability for MNO-B users' data traffic to utilize additional NR connection links in PLMN-A, enabling them to connect at higher data rates (including anchoring and aggregation to the CN in the HPLMN). This capability is assumed to be supported by both PLMN CNs and the UEs (of the golden MNO-B users) and is associated with a set of traffic policies and conditions negotiated by the MNO. This capability is controlled by the HPLMN and can be provisioned (to UEs and CN entities).

[0314] Examples of preconditions relevant to this use case include:

[0315] Alice and Bob have arrived at a stadium to watch a concert by their favorite singer. Alice is a golden subscriber to MNO-B, and Bob is a "regular" MNO-B customer. Referring to the examples in Figures 12 and 13, Bob's UE, Bob UE, and Alice's UE, Alice UE, are depicted.

[0316] Both UEs are camped and registered with the MNO-B NW and are in the Idle state. Alice's UE supports dual (NR) radios.

[0317] Alice's specific traffic policy, part of the MNO-B "Golden User" contract, includes dual access usage for high-quality video calls, depending on QoS or traffic type. Otherwise, Alice's UE must use a single access / link from the MNO-B.

[0318] The service flow of FIG. 12 and FIG. 13 is as follows:

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

[0320] FIG. 12 is an example of a single 3GPP access connection according to one embodiment of the disclosure of the present specification.

[0321] Referring to Figure 12, Bob UE and Alice UE are illustrated. In Figure 12, both Bob UE and Alice UE are connected to a data network in PLMN-B based on 3GPP Access 1.

[0322] 1) Before the concert begins, Alice and Bob make a voice call to their best friend, describing the stadium atmosphere and promising to share a video of the concert later. Both are using a single 3GPP access connection (via PLMN-B).

[0323] Figure 12 is an example of an Alice & Bob data session using a single 3GPP access connection, according to step 1.

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

[0325] FIG. 13 is an example of a dual 3GPP access connection according to one embodiment of the disclosure of the present specification.

[0326] Referring to Figure 13, Alice UE uses both a connection based on 3GPP Access 1 and a connection based on 3GPP Access 2.

[0327] 2) When the concert begins, Alice and Bob decide to initiate a video call (with their friends) to share the live experience (with high-quality video settings). Alice's UE registers with NW-A and establishes a dual-access connection across the two networks. Bob's UE continues to use single-access through PLMN-B.

[0328] Figure 13 illustrates Alice's data session scenario using dual 3GPP access connections, according to step 2.

[0329] 3) Alice and Bob hang up the video call and continue enjoying the concert.

[0330] According to the use cases referenced in Figures 12 and 13, Alice's video quality was much better than Bob's video.

[0331] Describes an example of an existing feature that partially or fully encompasses the use case feature.

[0332] A) Steps 2 and 3 include a feature called Access Traffic Steering, Switching, and Splitting (ATSS). A similar feature described in this use case is supported by TS 25.301 V17.0.0 Section 5.3.2, but is limited to 3GPP access and non-3GPP dual access.

[0333] B) Existing service requirements (e.g., TS 22.261 V19.3.0 S6.18 and S6.41) capture some common multi-NW connectivity requirements and do not fully address or satisfy specific target use cases and capabilities. For example, in the prior art, for a user subscribed to a single operator, the use of multiple service networks operated by different operators is under the control of the home operator. For example, in the prior art, if multiple operators provide the same service, the UE should receive the subscribed service preferentially on the home operator's network, unless the home operator's network instructs otherwise. In this case, if the service is unavailable on the home operator's network (e.g., due to insufficient network coverage), the UE can receive the service on the network of another operator. In the prior art, the QoS provided on the partner operator's network for the same service may vary depending on the contract between the two operators and may differ from that provided on the domestic operator's network.

[0334] Examples of potential new requirements needed to support use cases include:

[0335] The 5G system shall be able to support mechanisms to coordinate, split and switch the user plane traffic of a UE for a single data session between two 5G networks belonging to two different PLMN operators (e.g., both using NR connectivity) or between an HPLMN and a SNPN.

[0336] It is assumed that an HPLMN subscription is used to access both networks, data traffic is anchored to HPLMN, and there are appropriate business agreements in place between the two network operators, including specific traffic routing policies based on geographic location, subscription, and traffic type.

[0337] Describes example use cases for UEs using terrestrial and satellite access.

[0338] Satellite access, known for its wide coverage, can improve service availability in areas with poor terrestrial access network coverage or poor radio conditions (e.g., multipath interference). When a fast-moving UE requests real-time services, such as IMS voice / video conferencing, it can simultaneously connect to the 5G system via terrestrial and satellite access, minimizing the impact of terrestrial network outages while providing continuous, stable service.

[0339] Eric is traveling to Saudi Arabia on business. He travels from Makkah to Madinah on the Haramain high-speed train, crossing 450 kilometers of desert at 300 kilometers per hour, to visit clients. He must handle urgent business via online video conferencing while on the road and resolve any issues before his arrival.

[0340] Examples of preconditions include:

[0341] TerrA's terrestrial access network offers good coverage in urban areas, suburban areas, and railway stops, but is limited in rural areas and deserts between stops. SatA's satellite access network (e.g., LEO) provides nationwide coverage, and SatA can provide its own communications services. Note that TerrA is a terrestrial network operator, while SatA is a satellite network operator.

[0342] Based on this Agreement, TerrA may direct, divert or split User traffic onto the data path of the SatA network and consolidate it into TerrA's 5GC, taking into account SatA's service availability or coverage.

[0343] Eric's UE (e.g. mobile phone or wireless network card) is capable of dual 3GPP radio access, including satellite access, and is subscribed to a service-approved TerrA (PLMN NetA).

[0344] By default, only terrestrial access functions are activated.

[0345] An example of a service flow is as follows:

[0346] Eric activates the UE's satellite access feature while waiting to check in at the Macca train station.

[0347] UEs register with NetA based on their service preferences (e.g., instant chat when terrestrial access is preferred, HD TV when satellite access is preferred) over terrestrial access and satellite access networks.

[0348] After Eric connects, the online video conference begins via the terrestrial access network. During the one-hour conference, UE traffic is autonomously steered, switched, or split between the terrestrial and satellite network traffic paths with the help of TerrA's core network, and then converged on TerrA's core network to ensure uninterrupted video conference.

[0349] When the train reaches its destination, Eric disables satellite access and the UE updates its registration with NetA.

[0350] The postconditions associated with the use case are as follows: For example, the video conference is completed smoothly and without interruption. The user is unaware of any navigation, transitions, or splits during the video conference.

[0351] Examples of existing features that partially or fully encompass the use case functionality are described below.

[0352] 5G systems must support UEs with multi-radio and single-radio capabilities.

[0353] 5G systems must support the ability to steer UEs to select specific 3GPP access networks based on operator policy.

[0354] Depending on operator policy, 5G systems must be able to provide simultaneous data transmission over different access technologies (e.g., NR, E-UTRA, non-3GPP) to access one or more 3GPP services.

[0355] A UE can use two or more access technologies simultaneously. In this case, the 5G system must be able to optimally distribute user traffic by selecting one of the access technologies in use, taking into account factors such as the service, traffic characteristics, radio characteristics, and the UE's movement speed.

[0356] 5G systems must be able to support data transmission optimized for different access technologies (e.g., 3GPP, non-3GPP) for UEs simultaneously accessing the network through different connections.

[0357] Service continuity between 5G terrestrial access networks and 5G satellite access networks owned by the same operator or by different operators under contract must be supported by the 5G system.

[0358] Examples of potential new requirements needed to support use cases include:

[0359] For example, a 5G system should support a mechanism to coordinate user traffic of a UE between different 3GPP access networks and the core network for a UE using dual 3GPP access, taking into account service preferences, traffic characteristics, radio characteristics, QoS, etc. For example, a 5G system should support seamless service continuity by switching and splitting user traffic paths between different 3GPP access networks and the core network for a UE using dual 3GPP access (e.g., NR and satellite access) based on network availability, service preferences, etc.

[0360]

[0361] Looking at the above use cases, services can be provided to the UE through two 3GPP accesses (or 3GPP access links). For example, the UE may receive services from two 3GPP accesses connected to a single CN (Core Network) (or from two 3GPP accesses belonging to the same network). Alternatively, the UE may receive services from two 3GPP accesses connected to different CNs (or from two 3GPP accesses belonging to different networks). In the above, the network may be a PLMN or an NPN.

[0362] And, for some services, traffic may be steered, switched, and split through a PDU Session formed through two 3GPP accesses. Here, this PDU Session may be referred to as a Multi-Access (MA) PDU Session. In the prior art, an MA PDU Session was established through a 3GPP access and a non-3GPP access, but in the disclosure of this specification, a PDU Session may be established through two 3GPP accesses.

[0363] For some services, traffic may be transmitted through a PDU Session established via a single 3GPP access.

[0364] In the dual-steering example described above, it is assumed that the UE has a single subscription. Conventional technology has the problem of the UE registering with only one 5G CN for 3GPP access. Furthermore, conventional technology has not defined a method for providing services to the UE via two 3GPP accesses.

[0365] However, a UE may need to register with two 5G CNs to receive services over two 3GPP accesses. Furthermore, a UE may need to perform separate registration procedures for each 3GPP access, even for a single 5G CN, to receive services over two 3GPP accesses.

[0366] Additionally, if a UE is registered to two 5G CNs, the UE may need to select and / or decide on which 5G CN to establish a PDU Session for which service and to which 5G CN to transmit traffic.

[0367] To achieve this, UEs must simultaneously register using two 3GPP RATs on a single network (PLMN or SNPN). Alternatively, UEs must simultaneously register on different networks for each 3GPP RAT (both PLMNs, both SNPNs, or one PLMN and the other SNPN). Furthermore, the 3GPP RATs must be able to support various formats, such as NR+NR, NR+E-UTRA, TN-NTN, and NTN-NTN.

[0368] The Dual Steer item defines the use cases and service requirements for providing services to terminals using two 3GPP accesses simultaneously in 5GS (TR 22.841 V1.1.0 "Study on Upper layer traffic steer, switch and split over dual 3GPP access").

[0369] Meanwhile, groups related to network slices have also been introduced. For example, a group can be created to allow only certain slices to be used together, and only the slices included in that group can be used together. Network slice groups can be supported based on the subscriber information of the terminal. For example, Network Slice Simultaneous Registration Group (NSSRG) information related to the network group can be included in the subscriber information. Based on the NSSRG subscriber information, the AMF can control which slices can be used simultaneously.

[0370] For example, if the NSSRG values ​​of Slice A, Slice B, and Slice C are 1, and the NSSRG values ​​of Slice D and Slice E are 2, Slice A, Slice B, and Slice C can be used simultaneously. However, slices with different NSSRGs, such as Slice A and Slice D, cannot be used simultaneously.

[0371] To support NSSRG-based operations, the AMF can check the NSSRG value when transmitting Allowed NSSAI to the terminal. The AMF must always include slices with the same NSSRG in the Allowed NSSAI.

[0372] However, there is a problem that NSSRG-based operation is not supported for dual steer, where 5GS provides services to a terminal using two 3GPP accesses simultaneously. For example, if a terminal performs registration twice through a 3GPP access, a different AMF may be selected for each 3GPP access. In this case, since each AMF assigns an Allowed NSSAI to the terminal, a problem arises in which slices with different NSSRG values ​​are assigned to the terminal. In other words, the NSSRGs of the slices included in the Allowed NSSAI received by the terminal from the first AMF may be different from the NSSRGs of the slices included in the Allowed NSSAI received by the terminal from the second AMF.

[0373] In other words, dual steer, where 5GS provides services to terminals using two 3GPP accesses simultaneously, is being discussed. The Network Slice Simultaneous Registration Group (NSSRG) has been introduced, which allows only slices belonging to a network slice group to be used together. Based on the NSSRG, the AMF can control which slices can be used simultaneously. If a terminal performs registration twice through a 3GPP access, a problem may arise where different AMFs are selected for each 3GPP access. In this case, since each AMF assigns an Allowed NSSAI to the terminal, the problem of assigning a slice with a different NSSRG value to the terminal arises.

[0374] This problem occurs equally when a terminal registers with different PLMNs in 3GPP access and non-3GPP access.

[0375] To address these issues, conventional methods, such as those illustrated in FIGS. 14 and 15 , have been proposed. However, even the examples based on FIGS. 14 and 15 still suffer from the problem of inefficient signaling. The conventional method will be described with reference to FIGS. 14 and 15 .

[0376] Figures 14 and 15 relate to NSSRG restrictions for various access types in multiple PLMNs.

[0377] Question #1: Should NSSAIs requested across different access types in different PLMNs share a common NSSRG value?

[0378] Question #2: If the answer to Question #1 is 'Yes', how does the network (i.e., different AMFs in different PLMNs) enforce the common NSSRG value restriction for the requested NSSAI?

[0379] Regarding the two questions above, the following discussion took place.

[0380] The discussion regarding question #1 is as follows:

[0381] "Subscription information for a UE is contained within an allowed NSSAI. The subscription information may include, for each S-NSSAI, Network Slice Simultaneous Registration Group (NSSRG) information that limits the S-NSSAIs that can be simultaneously provided to the UE. If an S-NSSAI has associated NSSRG information, the S-NSSAIs within an allowed NSSAI must share at least one NSSRG."

[0382] "The serving AMF may provide the configured NSSAI to the UE, and the UE may have indicated that it supports the subscriber-based network slice simultaneous registration restriction feature. In this case, the AMF also provides the UE with NSSRG information related to the S-NSSAI of the HPLMN within the mapping information of the configured NSSAI. A UE that receives the NSSRG value included in the network slicing configuration information shall include only the S-NSSAIs that share the common NSSRG in the requested NSSAI based on the received information."

[0383] "A UE supporting the subscriber-based network slice concurrent registration limit feature, when it receives NSSRG information along with configured NSSAI, the UE shall only request S-NSSAIs that share at least one common NSSRG across all access types at any time."

[0384] Observation 1: NSSRG information is a per-UE subscriber information-based restriction, regardless of whether the UE is registered with a single PLMN or multiple PLMNs. The NSSRG information configured in the UE is related to the S-NSSAI of the HPLMN in the mapping information of the configured NSSAI. A UE receiving an NSSRG value must include only S-NSSAIs that share a common NSSRG in the requested NSSAI.

[0385] Observation 2: The answer to question #1 is 'yes'.

[0386] The discussion regarding question #2 is as follows:

[0387] Regarding question #2, network enforcement is only necessary when a UE registers with multiple PLMNs but does not verify the NSSRG information for the requested NSSAI in other PLMNs. There are two alternatives for network enforcement:

[0388] - Option A: Solution based on accepted NSSAI restrictions.

[0389] The main principle is that the serving AMF restricts the allowed NSSAI for the current PLMN based on the existing allowed NSSAIs (if any) for other PLMNs stored in the UDM, so that the allowed NSSAIs of UEs for different PLMNs share a common NSSRG.

[0390] When the serving AMF receives the requested NSSAI from the UE, there may not be NSSRG information related to the allowed NSSAIs of other PLMNs stored in the UDM. In this case, the serving AMF determines the allowed NSSAI based on the received NSSRG information. The serving AMF then stores the NSSRG information related to the currently allowed NSSAIs for each PLMN in the UDM. If the serving AMF receives the requested NSSAI from the UE and there is NSSRG information related to the allowed NSSAIs of other PLMNs stored in the UDM, the serving AMF checks whether the S-NSSAI of the requested NSSAI shares a common NSSRG with the allowed NSSAIs of other PLMNs.

[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 14 is an example of limiting the allowed NSSAI.

[0393] For example, in the example shown in FIG. 14, it is assumed that the subscription data of the UE includes NSSRG#A {HPLMN S-NSSAI-1, HPLMN S-NSSAI-2} and NSSRG#B {HPLMN S-NSSAI-1, HPLMN S-NSSAI-3}.

[0394] At time T1, the UE registers with PLMN#1, and at time T2, the UE registers with PLMN#2.

[0395] According to Option A, the serving AMF restricts the allowed NSSAI for the current PLMN based on the existing allowed NSSAIs (if any) for other PLMNs stored in the UDM, so that the allowed NSSAIs of UEs for different PLMNs share a common NSSRG. This can result in a result similar to the example in Table 3.

[0396] Requested NSSAI Accepted NSSAI / Rejected NSSAI LMN#1 Requested NSSAI = S-NSSAI-A + S-NSSAI-B; Mapping of Requested NSSAI = S-NSSAI-A < - > HPLMN S-NSSAI-1,S-NSSAI-B < - > HPLMN S-NSSAI-2; Accepted NSSAI = S-NSSAI-A + S-NSSAI-B; Mapping of Accepted NSSAI = S-NSSAI-A < - > HPLMN S-NSSAI-1,S-NSSAI-B < - > HPLMN S-NSSAI-2; PLMN#2 Requested NSSAI = S-NSSAI-C + S-NSSAI-D; Mapping of Requested NSSAI = S-NSSAI-C <-> HPLMN S-NSSAI-1,S-NSSAI-D < - > HPLMN S-NSSAI-3; Accepted NSSAI = S-NSSAI-C; Mapping of Accepted NSSAI = S-NSSAI-C < -> HPLMN S-NSSAI-1; Rejected NSSAI = S-NSSAI-D;

[0397] According to the example in Table 3, for PLMN#1, the UE may transmit a requested NSSAI including HPLMN S-NSSAI-1 and HPLMN S-NSSAI-2. HPLMN S-NSSAI-1 may be mapped to S-NSSAI-A, and HPLMN S-NSSAI-2 may be mapped to S-NSSAI-B. In PLMN#1, the allowed NSSAIs may be S-NSSAI-A and S-NSSAI-B.

[0398] For a description of the requested NSSAI of PLMN#2, refer to the description of the requested NSSAI of PLMN#1. The allowed NSSAI in PLMN#2 may be S-NSSAI-C.

[0399] Observation 3: Option A adheres to the principle that the S-NSSAIs of the allowed NSSAIs must share at least one NSSRG. This has the problem of frequently sending signals to the UDM to store and delete allowed NSSAIs per serving PLMN, which affects both the AMF and the UDM.

[0400] - Option B: PDU Session Limit-Based Solution

[0401] The key principle is that if the requested NSSAIs for different PLMNs do not share a common NSSRG, the AMF determines the allowed NSSAIs to serve the PLMN based on the received NSSRG information. However, in this scenario, the AMF cannot impose restrictions on the allowed NSSAIs for different PLMNs. The UDM restricts PDU sessions to other PLMNs based on the NSSRG values ​​associated with the HPLMN S-NSSAI used by the SMF to register PDU sessions with the UDM.

[0402] In this option, the UE can request the establishment of a new PDU session, and the SMF registers the PDU session with the UDM using the HPLMN S-NSSAI. In this case, the UDM checks whether the HPLMN S-NSSAI for the existing PDU session stored in the UDM shares a common NSSRG with the HPLMN S-NSSAI for the new PDU session. If not, the UDM deregisters the previously registered SMF. Then, this SMF initiates the PDU session release procedure. Otherwise, the UDM accepts the SMF's registration for the new PDU session.

[0403] Referring to Figure 15, a specific example of Option B is described.

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

[0405] Figure 15 is an example of limiting a PDU session.

[0406] According to the example of Fig. 15, the SMF of PLMN-1 can perform PDU registration to the UDM. The SMF of PLMN-2 can also perform PDU registration to the UDM.

[0407] The UDM verifies whether the HPLMN S-NSSAI for the existing PDU session stored in the UDM shares a common NSSRG with the HPLMN S-NSSAI for the new PDU session. If not, the UDM deregisters the previously registered SMF. This SMF then initiates the PDU session release procedure. Otherwise, the UDM accepts the SMF's registration for the new PDU session.

[0408] For example, as shown in FIG. 15, it is assumed that the subscription data of the UE includes NSSRG#A {HPLMN S-NSSAI-1, HPLMN S-NSSAI-2} and NSSRG#B {HPLMN S-NSSAI-1, HPLMN S-NSSAI-3}.

[0409] At time T1, the UE registers with PLMN#1, and at time T2, the UE registers with PLMN#2. If the operation according to Option B is performed, a result similar to the example in Table 4 can be derived.

[0410] Requested NSSAI Accepted NSSAI / Rejected NSSAI LMN#1 Requested NSSAI = S-NSSAI-A + S-NSSAI-B; Mapping of Requested NSSAI = S-NSSAI-A < 좭PLMN S-NSSAI-1,S-NSSAI-B < 좭PLMN S-NSSAI-2; Accepted NSSAI = S-NSSAI-A + S-NSSAI-B; Mapping of Accepted NSSAI = S-NSSAI-A < 좭PLMN S-NSSAI-1,S-NSSAI-B < 좭PLMN S-NSSAI-2; PLMN#2 Requested NSSAI = S-NSSAI-C+ S-NSSAI-D; Mapping of Requested NSSAI = S-NSSAI-C < 좭PLMN S-NSSAI-1,S-NSSAI-D < 좭PLMN S-NSSAI-3; Allowed NSSAI = S-NSSAI-C+ S-NSSAI-D; Mapping of allowed NSSAI = S-NSSAI-C < 좭PLMN S-NSSAI-1,S-NSSAI-D < 좭PLMN S-NSSAI-3;

[0411] Table 4 can be interpreted in the same way as Table 3.

[0412] At time T3, the UE initiates a new PDU session for S-NSSAI-B in PLMN#1. At time T4, the UE initiates a new PDU session for S-NSSAI-D in PLMN#2. The UDM determines that S-NSSAI-B and S-NSSAI-D cannot share a common NSSRG value and decides to deregister the SMF providing the PDU session in PLMN#1.

[0413] Observation 4: Option B suffers from the problem that the S-NSSAIs of the allowed NSSAIs for different PLMNs cannot share at least one NSSRG. PDU sessions across different PLMNs may be restricted based on the NSSRG value associated with the S-NSSAI for the PDU session.

[0414] The conclusions and suggestions of the prior art based on the examples of Figs. 14 and 15 are as follows.

[0415] Conclusion 1: The answer to question #1 is 'yes' because NSSRG information is a per-UE subscription-based restriction, regardless of whether the UE is registered with a single PLMN or with different PLMNs.

[0416] Conclusion 2: The NSSRG information configured in the UE is related to the S-NSSAI of the HPLMN in the mapping information of the configured NSSAI. The UE receiving the NSSRG value must include only the S-NSSAIs that share the common NSSRG in the requested NSSAI. Regarding Question #2, network enforcement is only required when the UE registers to multiple PLMNs but does not verify the NSSRG information of the requested NSSAI through different PLMNs.

[0417] However, the prior art according to the examples of FIGS. 14 and 15 still has problems.

[0418] In the prior art according to the examples of FIGS. 14 and 15, whenever the AMF transmits Allowed NSSAI to the terminal, an operation of registering Allowed NSSAI to the UDM is performed. Alternatively, an operation of registering Allowed NSSAI to the UDM is performed whenever the terminal creates a PDU session. By this method, it is possible to prevent slices having different NSSRGs from being used. However, if the Allowed NSSAI is registered to the UDM, there is a problem in that signaling to the UDM occurs whenever the Allowed NSSAI is changed. In addition, when the UDM checks the NSSRG when creating a PDU session, there is a problem in that the concept of not including slices having different NSSRGs in the Allowed NSSAI according to the existing agreement is changed.

[0419] Various examples disclosed in this specification propose methods for supporting NSSRG when a UE performs dual 3GPP registration. Note that the methods disclosed in this specification can be applied in the same manner when a UE registers to different PLMNs for both 3GPP access and non-3GPP access.

[0420] According to various examples of the disclosure of this specification, a method for supporting registration in dual 3GPP access is composed of a combination of one or more of the operations / configurations / steps described below.

[0421] In this specification, UE (User Equipment) and terminal may be used as terms with the same meaning.

[0422] In this specification, the terms “Subscriber” and “User” may be used interchangeably.

[0423] In this specification, Application Function (AF) and Application Server (AS) may be used as terms with the same meaning.

[0424] The methods presented below may be performed or used in combination or complementary manner.

[0425] 1. First example of disclosure of this specification

[0426] A first example of the disclosure of this specification includes an operation based on NSSAAF.

[0427] In the first example of the disclosure of the present specification, before the AMF transmits the Allowed NSSAI to the terminal, it can check with the NSSAAF whether the NSSRG is satisfied. To this end, the NSSAAF can store and manage the Allowed NSSAI allocated to each terminal and the NSSRG for each slice. For example, for this operation, a new service can be defined for the NSSAAF service, or the existing NSSAAF service can be extended and used. For example, as shown in Table 5 below, in addition to the existing Nnssaaf_NSSAA and Nnssaaf_AIW services, the Nnssaaf_NSSRG service can be additionally added. Alternatively, the existing Nnssaaf_NSSAA service can be extended and used.

[0428] Service NameService OperationOperation SemanticsExemplary ConsumersNnssaaf_NSSAAAuthenticateRequest / ResponseAMFRe-AuthenticationNotificationNotifyAMFRevocationNotificationNotifyAMFNnssaaf_AIWAuthenticateRequest / ResponseAUSFNnssaaf_NSSRGRegistrationRequest / ResponseAMFUpdateRequest / ResponseAMFDeregistrationRequest / ResponseAMF

[0429] Referring to FIGS. 16A and 16B , specific operations according to the first example of the disclosure of the present specification will be described. In the examples of FIGS. 16A and 16B , descriptions of operations identical to those in the prior art will be omitted, and descriptions will be focused on the matters proposed in the present specification.

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

[0431] Figures 16a and 16b are examples of a procedure according to the first example of the disclosure of the present specification.

[0432] 1. A terminal can send a Registration Request message. The Registration Request message can include a Requested NSSAI. The Requested NSSAI can include slices that the terminal wishes to use.

[0433] 2. AMF can perform registration for UDM. For example, AMF can perform registration for a terminal using UDM. If AMF does not have terminal subscriber information, AMF can retrieve subscriber information from UDM based on Nudm_SDM_Get. AMF can perform Nudm_SDM_Subscribe to receive changes to subscriber information.

[0434] 3. The AMF may transmit a registration request message related to the NSSRG to the NSSAAF. For example, the AMF may determine the slices that can be transmitted to the UE based on the subscriber information of the UE. The AMF transmits information to the NSSAAF for checking the NSSRG to determine whether the slices to be transmitted to the UE satisfy the NSSRG. Here, the fact that the slices satisfy the NSSRG means that at least one or more slices to be allowed to the UE have the same NSSRG value. At this time, the AMF may transmit to the NSSAAF a list of slices that can be transmitted to the UE, as determined by the AMF, along with the NSSRG values ​​for the corresponding slices.

[0435] Additionally, the AMF can transmit information to the NSSAAF that can distinguish the terminal's 3GPP access from other 3GPP accesses. This information can include information such as the access type, RAT type, and an ID that distinguishes the registration.

[0436] NSSAAF can compare the received slice list and NSSRG value with the slice list and NSSRG value stored by NSSAAF. If the terminal does not store slice information related to the slice being used, NSSAAF can store the slice list and NSSRG value transmitted by AMF, information that can distinguish access, AMF information, etc.

[0437] 4. NSSAAF may send a registration response message to AMF. For example, NSSAAF may inform AMF that NSSRG is satisfied.

[0438] 5. AMF can send a registration acceptance message to the terminal. For example, AMF sends Allowed NSSAI, which satisfies NSSRG, to the terminal.

[0439] 6. The terminal can send a Registration Request message. For example, the terminal performs the registration procedure using another network or another NG-RAN within the same network. The Registration Request message can include a Requested NSSAI. The Requested NSSAI can include the slices the terminal wishes to use.

[0440] 7. AMF can perform registration for UDM. For example, AMF can perform registration for a terminal using UDM. If AMF does not have terminal subscriber information, AMF can retrieve subscriber information from UDM based on Nudm_SDM_Get. AMF can perform Nudm_SDM_Subscribe to receive changes to subscriber information.

[0441] 8. The AMF may transmit a registration request message related to the NSSRG to the NSSAAF. For example, the AMF may determine the slices that can be transmitted to the UE based on the subscriber information of the UE. The AMF transmits information to the NSSAAF for verifying the NSSRG to determine whether the slices to be transmitted to the UE satisfy the NSSRG. Here, the slices satisfying the NSSRG mean that the slices to be transmitted to the UE have at least one identical NSSRG value. At this time, the AMF may transmit to the NSSAAF a list of slices that can be transmitted to the UE, as determined by the AMF, along with the NSSRG values ​​for the corresponding slices.

[0442] Additionally, the AMF can transmit information to the NSSAAF that can distinguish the terminal's 3GPP access from other 3GPP accesses. This information can include information such as the access type, RAT type, and an ID that distinguishes the registration.

[0443] NSSAAF can compare the received slice list and received NSSRG value with the slice list and NSSRG value stored by NSSAAF.

[0444] 9. The slices being used by the terminal and the NSSRG may not be aligned. For example, the slices transmitted by AMF2 may not have at least one identical NSSRG value. For another example, the NSSRG of the slices transmitted by AMF1 and the slices transmitted by AMF2 may not have at least one identical NSSRG value. In this case, the NSSAAF may notify AMF2 that the NSSRG is not satisfied, and may also provide the slice list and NSSRG information currently being used by the terminal. Here, the slice list and NSSRG information currently being used by the terminal may refer to the slice list and NSSRG information being used by the terminal through another network or another NG-RAN in the same network.

[0445] 10. Based on the information transmitted by NSSAAF, AMF can determine the Allowed NSSAI to be transmitted to the terminal. If necessary, AMF may re-perform steps 8 and 9 before performing step 10.

[0446] Afterwards, if the Allowed NSSAI of the terminal needs to be updated, the AMF (e.g., AMF1 or AMF2) can perform the actions described in steps 3, 4, 8, and 9 for the NSSAAF. In addition, if the terminal is deregistrated, the AMF can notify the NSSAAF of the deregistration and request the NSSAAF to delete the slice information being used by the terminal. For example, the AMF can directly request the NSSAAF to delete the slice information, or it can notify the NSSAAF that the terminal has been deregistrated and have the NSSAAF delete the information. The NSSAAF can maintain the terminal's slice and NSSRG information if the terminal is registered with another AMF. If the terminal is not registered with another AMF, the NSSAAF can delete the terminal's information. For this purpose, the AMF can use services such as Nnssaaf_NSSRG_Update or Nnssaaf_NSSRG_Deregistrtion.

[0447] 2. Second example of disclosure of this specification

[0448] A second example of the disclosure of this specification includes an operation based on NSACF.

[0449] The method according to the second example of the disclosure of this specification has the disadvantage that it can only be used when the same NSACF is used for all slices. However, it has the advantage that NSSRG can be applied even when a PDN Connection is established in the EPC.

[0450] AMF can send Nnsacf_NSAC_NumberOfUEsUpdate request. AMF can also send NSSRG information about slice to NSACF. NSACF stores UE ID, S-NSSAI, Access Type, NSSRG information, etc. In addition, NSACF checks NSSRG information about slices that UE is currently using and checks whether the slice sent by AMF can be used simultaneously with slices that UE is currently using. If it is a slice that cannot be used simultaneously, NSACF can send Nnsacf_NSAC_NumberOfUEsUpdate response to AMF that includes information as a result that NSSRG is not satisfied.

[0451] Basically, if the AMF is configured to require a slice to perform Network Slice Admission Control (NSAC), the AMF can perform NSAC. However, to apply NSSRG, the AMF must be configured to perform NSAC for all slices. Alternatively, the AMF can be configured to perform NSAC if the subscriber information contains NSSRG information.

[0452] If the AMF only needs to perform the NSSRG check without performing the NSAC, it can include information in the Nnsacf_NSAC_NumberOfUEsUpdate request message to only check the NSSRG. Specifically, according to the prior art, the AMF performs the NSAC only if the AMF is set to perform the NSAC. However, if the NSAC is performed only for the NSSRG check without performing the NSAC, the AMF can include information in the NSACF to not perform the NSAC and only perform the NSSRG check. Alternatively, it can be information not to check the maximum number of UEs for the slice.

[0453] Before the AMF sends the Registration Accept message, the Early Admission Control (EAC) mode can be set to active for all slices so that the AMF can check the NSSRG through the NSACF. If the EAC mode is not active, the AMF can first send the Registration Accept containing the Allowed NSSAI. Then, the AMF can check the NSSRG from the NSACF. If necessary based on the check result (e.g., if the NSSRG is not satisfied), the AMF can update the Allowed NSSAI through the UE Configuration Update procedure so that only slices that satisfy the NSSRG are included in the Allowed NSSAI.

[0454] To support roaming, it can be set to always use HPLMN NSAC Admission Mode.

[0455] Referring to FIGS. 17a and 17b, specific operations according to the second example of the disclosure of the present specification will be described. In the examples of FIGS. 17a and 17b, descriptions of operations identical to those in the prior art will be omitted, and descriptions will be focused on the matters proposed in the present specification.

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

[0457] FIG. 17a and FIG. 17b are examples of a procedure according to the second example of the disclosure of the present specification.

[0458] 1~2. The same operations as steps 1~2 of FIGS. 16a and 16b can be performed.

[0459] 3. The AMF can send a NumOfUEsUpdate (Number of UEs Update) request message to the NSACF. For example, the AMF can determine which slices can be transmitted to the terminal based on the terminal's subscriber information. To check whether the slices to be transmitted to the terminal satisfy the NSSRG, the AMF can send the Nnsacf_NSAC_NumOfUEsUpdate request to the NSCAF. At this time, the AMF can send a list of slices that can be transmitted to the terminal, as determined by the AMF, along with the NSSRG values ​​for the corresponding slices.

[0460] Additionally, the AMF can transmit information to the NSSAAF that can distinguish the terminal's 3GPP access from other 3GPP accesses. This information can include information such as the access type, RAT type, and an ID that distinguishes the registration.

[0461] The NSACF can compare the received slice list and NSSRG value with the slice list and NSSRG value stored by the NSSAAF. If the terminal does not store slice information related to the slice being used, the NSCAF can store the slice list and NSSRG value transmitted by the AMF, information that can distinguish accesses, and AMF information.

[0462] 4. The NSACF may send a response message to the AMF. For example, the NSACF may notify the AMF that the NSSRG is satisfied. At this time, the NSACF may separately send the AMF information on whether the maximum number of UEs is satisfied and whether the NSSRG is satisfied.

[0463] For example, when the AMF sends Allowed NSSAI to a terminal, the AMF checks with the NSACF the number of terminals using S-NSSAI. The reason why the AMF checks the number of terminals is to limit the number of terminals that can use a specific slice simultaneously. Therefore, in order for the AMF to send Allowed NSSAI, the AMF can check not only the NSSRG but also whether the maximum number of terminals is exceeded. An example of a service that allows the AMF to check with the NSACF the number of terminals using a slice and determine whether the maximum number is exceeded is NumOfUEsUpdate.

[0464] 5. AMF can send a registration acceptance message to the terminal. For example, AMF sends Allowed NSSAI, which satisfies NSSRG, to the terminal.

[0465] 6~7. The same operations as steps 6~7 of FIGS. 16a and 16b can be performed.

[0466] 8. The AMF can send a NumOfUEsUpdate (Number of UEs Update) request message to the NSACF. For example, the AMF can determine which slices can be transmitted to the UE based on the UE's subscriber information. To check whether the slices to be transmitted to the UE satisfy the NSSRG, the AMF can send the Nnsacf_NSAC_NumOfUEsUpdate request message to the NSACF. At this time, the AMF can send a list of slices that can be transmitted to the UE, as determined by the AMF, along with the NSSRG values ​​for the corresponding slices.

[0467] Additionally, the AMF can transmit information to the NSSAAF that can distinguish the terminal's 3GPP access from other 3GPP accesses. This information can include information such as the access type, RAT type, and an ID that distinguishes the registration.

[0468] NSACF can compare the received slice list and received NSSRG value with the slice list and NSSRG value stored by NSSAAF.

[0469] 9. The slices being used by the terminal and the NSSRG may not be aligned. For example, the NSSRGs of the slices transmitted by AMF2 may not match. For another example, the NSSRGs of the slices transmitted by AMF1 may not match the NSSRGs of the slices transmitted by AMF2. In this case, the NSACF may notify AMF2 that the NSSRG is not satisfied, and may also provide the slice list and NSSRG information currently being used by the terminal. Here, the slice list and NSSRG information currently being used by the terminal may refer to the slice list and NSSRG information being used by the terminal through another network or another NG-RAN in the same network.

[0470] 10. Based on the information transmitted by the NSACF, the AMF can determine the Allowed NSSAI to be transmitted to the terminal. If necessary, the AMF may re-perform steps 8 and 9 before performing step 10.

[0471] Hereinafter, with reference to FIG. 18, an example of operations according to an embodiment of the disclosure of the present specification is described. The example of FIG. 18 may include operations based on the first and / or second examples of the disclosure of the present specification.

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

[0473] FIG. 18 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

[0474] For reference, the procedure illustrated in FIG. 18 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 18.

[0475] For example, with respect to the example of FIG. 18, the operations described in the examples of FIGS. 1 to 17A and 17B may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 18, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0476] In the example of Fig. 18, the slice-related NF may be, for example, NSSAAF or NSSRG.

[0477] The operations illustrated in FIG. 18 are merely examples, and the scope of the disclosure of this specification is not limited to the operations illustrated in FIG. 18.

[0478] In step (S1801), the UE may transmit a registration request message to the AMF. The registration request message may include a requested NSSAI. The requested NSSAI may include information related to one or more network slices.

[0479] At step (S1802), AMF can send a request message to the slice related NF.

[0480] For example, a request message may be a request message related to a network slice.

[0481] For example, based on the slice group information being included in the subscriber information of the UE and the AMF being configured to check the slice group information through the network entity, the AMF can transmit a request message related to the network slice.

[0482] For example, the request message may include a slice list including one or more network slices that may be transmitted to the UE and slice group information associated with each of the one or more network slices.

[0483] For example, the request message may further include information to identify only the 3GPP access of the UE and slice group information.

[0484] For example, a slice-related NF may determine whether the slice list included in the request message satisfies a condition related to a slice group. For example, based on a slice list stored in the slice-related NF and stored slice group information related to the stored slice list, the slice-related NF may determine whether the slice list included in the request message satisfies a condition related to a slice group.

[0485] For example, if the saved slice list and the saved slice group information do not exist, the slice-related NF can store the slice list and slice group information included in the request message.

[0486] For example, the AMF may determine one or more network slices that can be transmitted to the UE based on the subscriber information of the UE and the requested NSSAI. A slice list including the determined one or more network slices may be included in the request message.

[0487] At step (S1803), the slice-related NF can send a response message to the AMF.

[0488] For example, the response message may include information from the slice-related NF about whether the slice list satisfies a condition related to the slice group.

[0489] For example, a condition related to a slice group may include a condition that all network slices related to the UE transmitted from one or more AMFs including the AMF to the slice-related NF have one or more common slice groups.

[0490] For example, based on the response message including information that a condition related to the slice group is not satisfied, the response message may further include slice group information related to the slice list being used by the UE and each network slice included in the slice list being used. For example, if the condition related to the slice group is not satisfied, the slice-related NF may transmit a response message to the AMF including slice group information related to the slice list being used by the UE and each network slice included in the slice list being used.

[0491] For example, AMF can determine the allowed NSSAI based on the response message.

[0492] In step (S1804), the AMF may transmit a registration response message to the UE. For example, the registration response message may be a registration acceptance message including the allowed NSSAI. Based on the response message, the AMF may transmit a registration acceptance message including the allowed NSSAI to the UE.

[0493] For example, based on the fact that the response message includes information that a condition related to the slice group is satisfied, the allowed NSSAI may include all of the one or more network slices included in the slice list (e.g., the slice list included by the AMF in the request message). In other words, since all network slices included in the slice list transmitted by the AMF satisfy the condition related to the slice group, the AMF may include all network slices included in the slice list in the allowed NSSAI.

[0494] For example, at least one network slice included in an allowed NSSAI may all be associated with the same slice group.

[0495] According to one embodiment of the disclosure of this specification, when performing dual registration, the AMF may provide the NSSAAF or NSACF with slice information to be transmitted to the terminal and NSSRG information for the slice. Accordingly, the NSSAAF or NSACF may store this information and compare it with existing information to determine whether the NSSRG is satisfied.

[0496] This specification may have various effects.

[0497] For example, based on Dual 3GPP access, NSSRG can be effectively supported even when registration procedures are performed separately.

[0498] The effects that can be achieved through the 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.

[0499] For reference, the operation of the terminal (e.g., UE) described in this specification may be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). The one or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute the instructions / programs stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0500] Additionally, the commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal described in the disclosure of this specification.

[0501] For reference, the operations of a network node (e.g., AMF, SMF, UPF, UDM, H-PCF, NEF, AF, UDR, NSACF, NSSAAF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, (R)AN, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operations of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operations of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0502] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

[0503] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to these specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0504] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0505] 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. In the method of Access and Mobility Management Function (AMF) performing communication, A step of receiving a registration request message including requested network slice selection assistance information (NSSAI) from a User Equipment (UE); A step of transmitting a request message related to a network slice to a network entity related to the slice; The request message includes a slice list including one or more network slices that can be transmitted to the UE and slice group information related to each of the one or more network slices; A step of receiving a response message from the network entity including information on whether the slice list satisfies a condition related to a slice group; and A step of transmitting a registration acceptance message including an allowed NSSAI to the UE based on the response message, A method characterized in that at least one network slice included in the above allowed NSSAI is related to the same slice group.

2. In paragraph 1, A method characterized in that it further comprises the step of determining the one or more network slices that can be transmitted to the UE based on subscriber information of the UE and the requested NSSAI.

3. In paragraph 1 or 2, A method characterized in that the conditions related to the above slice groups include a condition that all network slices related to the UE transmitted from one or more AMFs including the AMF to the network entity have one or more common slice groups.

4. In any one of paragraphs 1 to 3, A method further comprising the step of determining the allowed NSSAI based on the response message.

5. In any one of paragraphs 1 to 4, A method characterized in that a request message related to the network slice is transmitted based on the slice group information being included in the subscriber information of the UE and the AMF being set to check the slice group information through the network entity.

6. In any one of paragraphs 1 to 5, A method characterized in that the allowed NSSAI includes all of the one or more network slices included in the slice list, based on the information that the response message includes information that a condition related to the slice group is satisfied.

7. In any one of paragraphs 1 to 5, A method characterized in that the response message further includes slice group information related to each network slice included in the slice list being used by the UE and slice list being used, based on information that the condition related to the slice group is not satisfied.

8. In any one of paragraphs 1 to 7, A method characterized in that the request message further includes information for identifying the 3GPP access of the UE and information for confirming only slice group information.

9. In any one of paragraphs 1 to 8, A method characterized in that the above network entity is NSSAAF or NSSRG.

10. In the Access and Mobility Management Function (AMF) that performs communication, the AMF: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; An operation performed based on the above command being executed by the one or more processors is an AMF method according to any one of claims 1 to 9.

11. In an apparatus of a communication system, the apparatus: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A device wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 1 to 9.

12. A non-transitory computer readable medium (CRM) storing instructions, wherein an operation performed based on the instructions being executed by one or more processors is a method according to any one of claims 1 to 9.

13. In the method of communication between network entities related to slices, A step of receiving a request message related to a network slice from the Access and Mobility Management Function (AMF), The request message includes a slice list including one or more network slices that can be transmitted to a User Equipment (UE) and slice group information related to each of the one or more network slices; A step of determining whether the slice list included in the request message satisfies a condition related to a slice group based on the slice list stored in the network entity and the stored slice group information related to the stored slice list; and A method comprising the step of transmitting a response message to the AMF including information on whether a condition related to the slice group is satisfied.

14. In paragraph 13, A method further comprising the step of storing the slice list and the slice group information included in the request message if the stored slice list and the stored slice group information do not exist.

15. In paragraph 13 or 14, A method characterized in that the conditions related to the above slice groups include a condition that all network slices related to the UE transmitted from one or more AMFs including the AMF to the network entity have one or more common slice groups.

16. In any one of paragraphs 13 to 15, A method characterized in that the response message further includes slice group information related to each network slice included in the slice list being used by the UE and slice list being used, based on information that the condition related to the slice group is not satisfied.

17. In any one of paragraphs 13 to 16, A method characterized in that the request message further includes information for identifying the 3GPP access of the UE and information for confirming only slice group information.

18. In any one of paragraphs 13 to 17, A method characterized in that the above network entity is NSSAAF or NSSRG.

19. A slice-related network entity configured to operate in a wireless communication system, wherein the slice-related network entity: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; The actions performed based on the above instructions being executed by the one or more processors are: A network entity related to a slice according to any one of claims 13 to 18.

Images