Method related to multimodal service

Abstract

An embodiment of the present disclosure provides a method. The method comprises the steps of: receiving, by an SMF, capability information of a base station from an AMF, wherein the capability information includes information indicating that the base station supports multimodal recognition; receiving, by the SMF, a PCC rule from a PCF, wherein the PCC rule includes a multimodal service (MMS) ID; receiving, by the SMF, a request for indication of multimodal information from the base station; and on the basis of the capability information and the request, transmitting, by the SMF, indication configuration information for the multimodal information to a UPF, wherein the indication configuration information includes information causing the multimodal information to be indicated in a header of a packet corresponding to the MMS ID.

Description

Multimodal Service Related Methods

[0001] This specification relates to mobile communication.

[0002] 3GPP (3rd generation partnership project) LTE (long-term evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio Communication Sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

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

[0005] Based on base station capability information, the base station's request for multimodal information display, etc., the SMF performs multimodal information display settings with the UPF.

[0006] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0007] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0008] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0009] Figure 4 is a structural diagram of a next-generation mobile communication network.

[0010] FIG. 5 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0011] FIGS. 6 and 7 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0012] Figure 8 shows an example of a multimodal interactive system.

[0013] FIGS. 9 and FIGS. 10 illustrate examples of capability negotiation procedures according to the disclosure of the present specification.

[0014] FIG. 11 illustrates an example of a multimodal information marking procedure according to the disclosure of the present specification.

[0015] FIGS. 12, FIGS. 13, FIGS. 14 and FIGS. 15 illustrate examples of procedures according to the disclosure of the present specification.

[0016] FIG. 16 illustrates the procedure of the UE for the disclosure of the present specification.

[0017] FIG. 17 illustrates the procedure of the AMF for the disclosure of the present specification.

[0018] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through 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 through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

[0019] For convenience of explanation, the implementation of this specification is described primarily in relation to 3GPP-based wireless communication systems. However, the technical characteristics 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 3GPP-based wireless communication systems may be applied to other mobile communication systems.

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

[0021] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0022] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0023] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0024] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

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

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

[0027] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

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

[0029] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

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

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

[0032] Referring to FIG. 1, the 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 the network of the communication system (1), but the implementation of the present specification is not limited to a 5G system and may be applied to future communication systems beyond a 5G system.

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

[0034] 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. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs) and head-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0035] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (personal digital assistant), a PMP (portable multimedia player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, 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 financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

[0036] For example, a UAV can be an aircraft that is not on board and is navigated by radio control signals.

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

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

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

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

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

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

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

[0044] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through 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) may communicate with each other through the base station (200) / network (300), but they may 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., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0045] Wireless communication / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and base station (200) and / or between base station (200). Here, the wireless communication / connections 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 communication between base stations (150c) (e.g., relay, IAB (integrated access and backhaul)). Through the wireless communication / connections (150a, 150b, 150c), wireless devices (100a to 100f) and base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) may transmit / receive signals through various physical channels. To this end, based on various proposals in this specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0046] AI refers to the field of researching artificial intelligence or the methodologies to create it, while machine learning refers to the field of researching methodologies to define and solve various problems within the realm of artificial intelligence. Machine learning is also defined as an algorithm that improves performance on a task through continuous experience.

[0047] A robot can refer to a machine that automatically processes or operates given tasks based on its own capabilities. In particular, a robot equipped with the ability to perceive its environment, make independent judgments, and perform actions can be called an intelligent robot. Robots can be classified into industrial, medical, domestic, and military types depending on their purpose or field of use. Robots are equipped with drive units, including actuators or motors, to perform various physical movements, such as moving robot joints. Additionally, mobile robots include wheels, brakes, propellers, etc., in their drive units, enabling them to drive on the ground or fly in the air.

[0048] Autonomous driving refers to technology that drives itself, and an autonomous vehicle refers to a vehicle that drives without user intervention or with minimal user intervention. For example, autonomous driving can include technologies such as maintaining the driving lane, automatically adjusting speed like adaptive cruise control, driving automatically along a predetermined route, and automatically setting a route and driving once a destination is set. The term "vehicle" encompasses vehicles equipped solely with internal combustion engines, hybrid vehicles equipped with both internal combustion engines and electric motors, and electric vehicles equipped solely with electric motors; it can include not only automobiles but also trains and motorcycles. An autonomous vehicle can be viewed as a robot equipped with autonomous driving capabilities.

[0049] Augmented Reality is a collective term for VR, AR, and MR. VR technology provides real-world objects or backgrounds solely as CG images, AR technology provides virtual CG images superimposed on images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR technology in that it displays real-world and virtual objects together. However, there is a difference in that while virtual objects in AR technology are used to complement real-world objects, virtual and real objects in MR technology are used as equal entities.

[0050] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

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

[0052] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

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

[0054] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

[0055] Here, the wireless communication technology implemented in the wireless device of this specification may include LTE, NR, and 6G, as well as narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in 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 names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth, and / or LPWAN for low-power communication, and is not limited to the names mentioned above. For example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0056] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

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

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

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

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

[0061] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

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

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

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

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

[0066] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements instruction code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

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

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

[0069] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. 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 one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors.

[0070] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may consist of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drives, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0071] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0072] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, 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 operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0073] One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through 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) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0074] Although not illustrated in FIG. 2, the wireless device (100, 200) may 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., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

[0075] In an implementation of this specification, the UE may operate as a transmitting device in the uplink (UL; uplink) and as a receiving device in the downlink (DL; downlink). In an implementation of this specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed 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 to the first wireless device (100) may be configured to perform UE operations according to an implementation of this specification or to control a transceiver (106) to perform UE operations according to an implementation of this specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of this specification or to control a transceiver (206) to perform base station operations according to an implementation of this specification.

[0076] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0077] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

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

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

[0080] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation 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 operation flowcharts disclosed herein. Layers of a wireless 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 processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0081] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

[0082] A transceiver (106) is coupled to operate with a processor (102) and transmits and / or receives a wireless signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a wireless frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a wireless signal.

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

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

[0085] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

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

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

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

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

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

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

[0092] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform the function of managing Non-Access Stratum (NAS) security. The AMF (410) can perform the function of handling mobility in an idle state.

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

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

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

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

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

[0098] The illustrated SMF (420) can perform the function of assigning the IP (Internet Protocol) address of the UE. Also, the SMF (420) can control the PDU (protocol data unit) session.

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

[0100] Fifth-generation mobile communication supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban environments, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

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

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

[0103] - AUSF (Authentication Server Function)

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

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

[0106] - USDF (Unstructured Data Storage Function)

[0107] - NEF (Network Exposure Function)

[0108] - I-NEF (Intermediate NEF)

[0109] - NRF (Network Repository Function)

[0110] - NSSF (Network Slice Selection Function)

[0111] - PCF (Policy Control Function)

[0112] - SMF (Session Management Function)

[0113] - UDM (Unified Data Management)

[0114] - UDR (Unified Data Repository)

[0115] - UPF (User Plane Function)

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

[0117] - AF (Application Function)

[0118] - UE (User Equipment)

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

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

[0121] - NWDAF (Network Data Analytics Function)

[0122] - CHF (CHarging Function)

[0123] In addition, the following network functions may be considered.

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

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

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

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

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

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

[0130] The 5G system structure includes the following reference points.

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

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

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

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

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

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

[0137] The following reference points show the interactions that exist between the NF services of NF.

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

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

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

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

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

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

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

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

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

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

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

[0149] In some cases, two NFs may need to be connected to each other to service the UE.

[0150] <PDU 세션 수립 절차>

[0151] The procedure for establishing a PDU session is described. Refer to Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0152] FIGS. 6 and 7 illustrate examples of PDU session establishment procedures to which the implementation of the present specification applies.

[0153] PDU session establishment may fall under the following:

[0154] - Procedure for establishing a PDU session initiated by the UE

[0155] - PDU session handover between 3GPP and non-3GPP initiated by the UE

[0156] - PDU session handover from EPS initiated by UE to 5GS.

[0157] - Procedure for establishing a PDU session triggered by the network

[0158] A PDU session may (a) be associated with a single access type at any given time, namely either a 3GPP access or a non-3GPP access, or (b) be associated with multiple access types simultaneously, namely one 3GPP access and one non-3GPP access. A PDU session associated with multiple access types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) enabled UE.

[0159] Figures 6 and 7 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0160] In the procedure shown in Figures 6 and 7, it is assumed that the AMF has already retrieved user subscription data from the UDM unless the UE is urgently registered, since the UE is already registered with the AMF.

[0161] First, the procedure of Fig. 6 will be explained.

[0162] (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID.

[0163] The UE initiates the PDU session establishment procedure requested by the UE by transmitting a NAS message containing a PDU session establishment request message within an N1 SM container. The PDU session establishment request message includes a PDU session ID, a requested PDU session type, a requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), an SM PDU DN Request Container, and a UE Integrity Protection Maximum Data Rate.

[0164] If the PDU session establishment is a request to establish a new PDU session, the request type indicates "Initial Request". If the request refers to an existing PDU session transitioning between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN (packet data network) connection in the EPC, the request type indicates "Existing PDU Session". If the PDU session establishment is a request to establish a PDU session for an emergency service, the request type indicates "Emergency Request". If the request refers to an existing PDU session for an emergency service transitioning between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for an emergency service in the EPC, the request type indicates "Existing Emergency PDU Session".

[0165] The UE includes an S-NSSAI from the allowed NSSAI of the current connection type. If a Mapping of Allowed NSSAI is provided to the UE, the UE provides both the S-NSSAI of the visited VPLMN from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI.

[0166] (2) Step 2: The AMF selects an SMF. If the request type indicates an "initial request" or if the request is due to a handover from a non-3GPP connection provided by an EPS or another AMF, the AMF stores the connection type of the PDU session, as well as the association of the S-NSSAI(s), the DNN (data network name), the PDU session ID, and the SMF ID.

[0167] If the request type is "Initial Request" and the message also includes a previous PDU session ID representing an existing PDU session, the AMF selects an SMF and saves the new PDU session ID, S-NSAI(s), and the association of the selected SMF ID.

[0168] If the request type indicates an "existing PDU session," the AMF selects an SMF based on the SMF-ID received from the UDM. The AMF updates the connection type stored for the PDU session.

[0169] If the request type indicates an "existing PDU session" that refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and the serving PLMN S-NSSAI of the PDU session exists in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases.

[0170] - When the SMF ID corresponding to the PDU session ID and the AMF belong to the same PLMN;

[0171] - If the SMF ID corresponding to the PDU session ID belongs to the HPLMN;

[0172] Otherwise, the AMF rejects the request to establish a PDU session with an appropriate reason for rejection.

[0173] AMF rejects requests from urgently registered UEs where the request type does not indicate "urgent request" or "existing urgent PDU session".

[0174] (3) Step 3: If the AMF is not associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "initial request"), the AMF calls the Create SMContext request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for a PDU session ID provided by the UE (e.g., when the request type indicates "existing PDU session"), the AMF calls the Update SMContext request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0175] The AMF transmits the S-NSSAI of the serving PLMN from the allowed NSSAI to the SMF. For a local breakout (LBO) roaming scenario, the AMF also transmits the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI to the SMF.

[0176] The AMF ID is the UE's GUAMI and uniquely identifies the AMF serving the UE. The AMF transmits the PDU Session ID along with an N1 SM container containing the PDU session establishment request message received from the UE. The generic public subscription identifier (GPSI) is included if available in the AMF.

[0177] If a UE in a restricted service state is registered for emergency services without providing a SUPI, the AMF provides a PEI instead of a SUPI. If a UE in a restricted service state is registered for emergency services while providing a SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI from a UE or if the AMF indicates that the SUPI is not authenticated, the UE is determined to be unauthenticated.

[0178] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the H-PCF (home PCF) in the non-roaming case and the V-PCF (visited PCF) in the LBO roaming case.

[0179] (4) Step 4: If session management subscription data for S-NSSAI of the corresponding SUPI, DNN, HPLMN is unavailable, SMF can retrieve the session management subscription data from UDM and be notified when this subscription data is modified.

[0180] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF in accordance with the request received in Step 3.

[0181] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0182] If the SMF decides not to accept the establishment of a PDU session, the SMF rejects the UE request via a NAS SM signal containing the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and that the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.

[0183] (6) Step 6: Optional secondary authentication / authorization may be performed.

[0184] (7a) Step 7a: When dynamic policy and charging control (PCC) is used in a PDU session, the SMF can perform PCF selection.

[0185] (7b) Step 7b: SMF can establish an SM policy association with PCF and obtain a basic PCC rule for the PDU session by performing the SM policy association establishment procedure.

[0186] (8) Step 8: SMF selects one or more UPFs.

[0187] (9) Step 9: SMF can provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by SMF.

[0188] (10) Step 10: If the request type indicates an “initial request,” the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF.

[0189] In step 10a, SMF can send an N4 session establishment / modification request to UPF and provide packet detection, enforcement, and reporting rules installed in UPF for the PDU session. In step 10b, UPF can confirm by sending an N4 session establishment / modification response.

[0190] (11) Step 11: SMF sends an N1N2 message transfer message (e.g., Namf_Communication_N1N2 Message Transfer) to AMF.

[0191] The N1N2 message delivery message may include N2 SM information. The N2 SM information carries the following information that the AMF will transmit to the (R)AN.

[0192] - CN Tunnel Info: Corresponds to the core network address of the N3 tunnel corresponding to the PDU session;

[0193] - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles;

[0194] - PDU Session ID: Indicates to the UE the association between the RAN resource and the PDU session for the UE;

[0195] - S-NSSAI with a value for the serving PLMN (i.e., HPLMN S-NSSAI, or VPLMN S-NSSAI in the case of LBO roaming);

[0196] - User plane security enforcement information determined by SMF;

[0197] - Maximum data rate for UE integrity protection received in PDU session establishment request message: When integrity protection is indicated as "Preferred" or "Required" in user plane security enforcement information

[0198] - RSN (redundancy sequence number) parameter

[0199] The N1N2 message delivery message may include an N1 SM container. The N1 SM container includes a PDU session establishment acceptance message that the AMF will provide to the UE. The PDU session establishment acceptance message includes an S-NSSAI from an allowed NSASI. In the case of an LBO roaming scenario, the PDU session establishment acceptance message includes an S-NSSAI from an allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI for the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0200] If necessary for QoS flows related to QoS rules and QoS profiles, multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment acceptance message and N2 SM information within the N1 SM container.

[0201] If PDU session establishment fails between steps 5 and 11, the N1N2 message delivery message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. (R)AN sends a NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0202] (12) Step 12: The AMF sends a NAS message containing a PDU session ID destined for the UE, a message accepting the establishment of a PDU session, and N2 SM information received from the SMF to (R)AN within the N2 PDU session request message.

[0203] (13) Step 13: (R)AN can perform AN-specific signal exchanges with the UE regarding information received from the SMF. For example, in the case of NG-RAN, it can perform RRC connection reconfiguration with the UE to set up necessary NG-RAN resources in relation to the QoS rules for the PDU session request received by the UE in Step 12.

[0204] (R)AN forwards the NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signal exchange with the UE includes the addition of (R)AN resources related to the received N2 command.

[0205] If N2 SM information is not included in step 11, steps 14–16b and step 17 below are omitted.

[0206] Now, the procedure of Fig. 7 following the procedure of Fig. 6 is explained.

[0207] (14) Step 14: (R)AN sends an N2 PDU session response message to AMF. The N2 PDU session response message may include a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs, user plane enforcement policy notifications), etc.

[0208] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

[0209] (16a) Step S16a: SMF initiates the N4 session modification procedure with UPF. SMF provides AN tunnel information and the corresponding forwarding rule to UPF.

[0210] (16b) Step S16b: UPF provides the N4 session modification response to SMF.

[0211] After this step, UPF can deliver the DL packet that may have been buffered for this PDU session to the UE.

[0212] (16c) Step 16c: If the SMF is not yet registered for this PDU session, the SMF can register with the UDM for the given PDU session.

[0213] (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.

[0214] After this step, AMF delivers the relevant events subscribed to by SMF.

[0215] (18) Step 18: At any time after Step 5, if the establishment of the PDU session fails during the procedure, the SMF may notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF may also release the created N4 session, the assigned PDU session address (e.g., IP address), and, if possible, release the association with the PCF. In this case, Step 19 below is omitted.

[0216] (19) Step 19: For PDU session type IPv6 or IPv4v6, the SMF can generate an IPv6 Router Advertisement and send it to the UE.

[0217] (20) Step 20: SMF can perform SM policy association modifications initiated by SMF.

[0218] (21) Step 21: If the establishment of a PDU session fails after Step 4, and the SMF no longer processes the UE's PDU session, the SMF may unsubscribe from the modification of the session management subscription data.

[0219] Multimodal service

[0220] A multimodal service is a communication service composed of multiple data flows that are interrelated and require coordination between applications. Data flows can transmit various types of data (e.g., audio, video, location, haptic data) and can be provided from various sources (e.g., a single user terminal, a single device, multiple devices connected to a single user terminal, or multiple user terminals).

[0221] For a single UE, since these data flows are closely associated and robust application coordination is expected to be required for the proper execution of multimodal applications, all data flows can be transmitted as a single PDU session.

[0222] Through the Nnef_AFsessionWithQoS service, AF can simultaneously provide the multimodal service ID, service requirements, and QoS monitoring requirements for each data flow belonging to a multimodal service.

[0223] - A multimodal service ID can explicitly indicate that a data flow is associated with a multimodal service. The PCF can use this information to derive accurate PCC rules and apply appropriate QoS policies to data flows that are part of a specific multimodal application.

[0224] - AF can provide PCF with QoS monitoring requirements for data flows related to multimodal services. PCF can create approved QoS monitoring policies for each data flow.

[0225] To initiate QoS monitoring for data flows related to multimodal services within a specific period, the PCF must receive QoS monitoring requirements for the corresponding data flows from the AF within a short time, whether there is a single request or multiple requests.

[0226] In addition to the features provided when a data flow is connected to a single UE, the following features may be provided when a data flow is connected to two or more UEs.

[0227] - Each relevant UE must select the same DNN / S-NSSAI combination for the multimodal service. The URSP rule evaluation framework is used to verify that the same DNN / S-NSSAI has been selected.

[0228] - The AF must use the same multimodal service ID in interactions with the PCF for all relevant UEs associated with the multimodal service. The PCF may consider this information when processing each AF request independently (e.g., applying specific QoS policies). While the data flow contributes to the service experience, it is valid on its own as it is transmitted via a separate PDU session with the relevant UE.

[0229] - When multiple PCFs are involved, the PCFs can make policy decisions based on inputs provided by the AF. Policy decisions can be performed individually by each PCF per PDU session.

[0230] 1. Support for the provision of multimodal services

[0231] To provide multimodal services, the AF can request multiple data flows from the NEF through multiple PDU sessions for a single UE or multiple UEs, and can send a separate request for each PDU session. This can be configured according to specific QoS requirements. If the AF provides specific information regarding the multimodal service, the following additional attributes may be supported:

[0232] - Multimodal Service ID: An identifier representing a multimodal communication service. Data flows belonging to the same multimodal service can share the same multimodal service ID.

[0233] AF supports multimodal service requirements composed of the following existing attributes to provide specific information about the data flow of a multimodal service, and AF can provide this information multiple times, for example, once per data flow.

[0234] - QoS monitoring requirements for each data flow

[0235] - QoS information and service requirements for each data flow (consisting of data flow description information and QoS parameters / QoS references)

[0236] Attributes for multiple data flows can be provided through a single or multiple AF requests.

[0237] Requests to the PCF may include a multimodal service ID and service requirements for each data flow belonging to the multimodal service. The PCF determines whether a request from the NEF or AF is approved, derives the necessary QoS parameters based on the provided information, and can provide the SMF with PCC rules containing updated policy control information for the affected PDU sessions.

[0238] The AF can provide QoS monitoring requirements for each data flow associated with the same multimodal service ID. When the PCF receives QoS monitoring requirements from the AF, the PCF can create a QoS monitoring policy for the PCC rule corresponding to that data flow.

[0239] If the PCF receives an additional AF request with the same multimodal service ID and PCF acknowledgment fails, the PCF may reject the AF request. The application can decide how to handle a data flow that has an already acknowledged AF request with the same multimodal service ID (e.g., stop the data flow, reconcile the AF request).

[0240] Currently, multiple media / data types belonging to or constituting the same multimodal service may be transmitted through different QoS flows depending on their respective QoS characteristics. Additionally, data / packets belonging to a multimodal service and those not belonging to it may be transmitted through the same QoS flow if their QoS characteristics are identical or similar. Furthermore, data / packets belonging to different multimodal services may also be transmitted through the same QoS flow.

[0241] Studies are underway to enable NG-RAN to recognize which QoS flows media / data types belonging to the same multimodal service are transmitted through via multimodal awareness at the base station and to support coordinated handling of packets constituting the multimodal service, including support for synchronization thresholds, through multimodal awareness at the base station.

[0242] If the base station supports multi-modal awareness, the base station can recognize multimodal service information markings in downlink packets. Based on the multimodal service information (e.g., timestamp) within the GTP header of the downlink packet, the base station can perform radio resource scheduling and synchronized data transmission between packets to the terminal.

[0243] In this study, based on the synchronization threshold requirements described in the above SA WG1, methods for supporting coordinated handling of different types of traffic and support units (e.g., Packet-level or Flow-level) in NG-RAN are being discussed (to ensure that DL traffic constituting multimodal services arrives at the receiving terminal at similar times).

[0244] Information required to support coordinated handling of multimodal services in NG-RAN may be provided from the 5G core network. The type of information that must be provided may vary depending on the granularity at the packet level or flow level.

[0245] In this specification, details regarding capability negotiation and multimodal information marking mechanisms for providing multimodal service-related information from a core network to an NG-RAN to support multimodal awareness at a base station may be described.

[0246] 2. Tactile and Multimodal Communication Services

[0247] Tactile and multimodal communication services can be applied in various fields such as industry, robotics and remote presence, virtual reality, augmented reality, medical, road traffic, functional games, education, culture, and smart grids. These services can support applications that can deliver information more effectively by receiving input from multiple sources or sending output to multiple destinations.

[0248] Figure 8 shows an example of a multimodal interactive system.

[0249] Input and output can be performed in various ways, including the following:

[0250] - Video / Audio Media;

[0251] - Ambient environmental information received by the sensor (e.g., brightness, temperature, humidity, etc.)

[0252] - Tactile data: This can be the sensation of touching a surface (e.g., pressure, texture, vibration, temperature) or kinesthetic sensation (e.g., gravity, attraction, position perception).

[0253] For immersive multimodal VR applications, synchronization between different media components can be critical to avoid negatively impacting the user experience (e.g., viewers detecting a lack of synchronization). This is especially true when the synchronization threshold between two or more modalities is lower than the application's latency KPI.

[0254] Table 3 shows examples of typical synchronization thresholds for immersive multimodal VR applications.

[0255] Media componentssynchronization threshold (note 1)audio-tactileaudio delay:50 mstactile delay:25 msvisual-tactilevisual delay:15 mstactile delay:50 msNOTE 1: for each media component, "delay" refers to the case where that media component is delayed compared to the other.

[0256] 5G systems must allow authorized third parties to provide policies for flows related to applications. Policies may include, for example, sets of UEs and data flows, expected QoS processing and related trigger events, and other coordination information.

[0257] The 5G system must support means to apply third-party policies to flows related to applications. Policies may include, for example, sets of UEs and data flows, expected QoS processing and related trigger events, and other coordination information.

[0258] Note: This policy can be used to coordinate the transmission of multiple UE flows (e.g., haptics, audio, and video) of a multimodal communication session in third-party applications.

[0259] High data rate and low latency

[0260] Audiovisual interaction is characterized by humans interacting with an environment or people, controlling a User Equipment (UE), and relying on audiovisual feedback. In use cases such as VR and interactive dialogue, latency requirements may include latency at the application layer (e.g., codecs).

[0261] To support VR environments with low motion-to-photon performance, 5G systems can support the following:

[0262] - Operation-to-photon latency in the range of 7ms to 15ms while maintaining up to 8K resolution, user data transfer rate of up to [1Gbit / s]

[0263] - Motion vs. Acoustic Delay [< 20ms]

[0264] Motion-to-photon latency is defined as the delay between the physical movement of the user's head and the updated screen of the VR headset. Motion-to-sound latency is the delay between the physical movement of the user's head and the arrival of updated sound waves from the head-mounted speakers at the user's ears.

[0265] To support the completion of conversational tasks during voice conversations, 5G systems must support low-latency voice coding for conversational conversation services (100ms, unidirectional mouth-to-ear method).

[0266] Because audio and video components are processed separately, 5G systems can support VR audio-video synchronization to prevent negative impacts on the user experience (e.g., viewers detecting a lack of synchronization). To support VR environments, 5G systems can support the following audio-video synchronization thresholds:

[0267] - For latency audio [125ms ~ 5ms],

[0268] - For high-end audio [45ms ~ 5ms].

[0269] 5G systems can support AR / VR service continuity to support immersive user experiences in high UE mobility environments.

[0270] Regarding the implementation of applications including AR / VR components, 5G network requirements may vary depending on the choice of architecture for implementing these services.

[0271] - Cloud / Edge / Split Rendering: Cloud / Edge / Split Rendering is characterized by the switching and exchange of rendering data between a rendering server and a device.

[0272] - Game or learning data exchange: This use case features the exchange of game or learning service data between two 5G-connected AR / VR devices.

[0273] - Use of VR content via a tethered VR headset: This use case involves a tethered VR headset receiving VR content through a connected UE. This approach alleviates some of the computational complexity required by the VR headset by allowing some or all decoding functions to be executed locally on the connected UE. The requirements in the table below refer to a direct wireless connection between the tethered VR headset and its connected UE.

[0274] The names network node, entity, message, etc. in this specification are merely examples.

[0275] For example, in this specification, an AMF may be a node / entity that manages connectivity and mobility in 6G.

[0276] For example, in this specification, SMF may be a node / entity that manages / is responsible for session and traffic processing rules in 6G.

[0277] For example, in this specification, PCF may be a node / entity that provides policy decisions and QoS rules in 6G.

[0278] For example, in this specification, NG-RAN may be a network node / entity responsible for wireless access and data transfer between a terminal and a Core network in 6G.

[0279] In this specification, coordinated handling of multimodal services of NG-RAN may be referred to as a multimodal awareness at RAN support function at a base station. This function may be referenced for the processing and resource management of multimodal service traffic at a base station based on information provided from the core network.

[0280] In this specification, synchronization threshold information for coordinated handling of NG-RAN may be received from AF. Alternatively, such information may be available information pre-configured in the network, such as requirement information available in the 5G core network.

[0281] In addition, this specification assumes a Deep Packet Inspection (DPI) function for header fields (e.g., Sequence Number, Time Stamp, Payload Type for identifying Type information, etc.) within RTP packets used for multimodal services in UPF.

[0282] 1. First embodiment

[0283] A capability negotiation method for multi-modal awareness at RAN at a base station can be proposed.

[0284] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0285] FIGS. 9 and FIGS. 10 illustrate examples of capability negotiation procedures according to the disclosure of the present specification.

[0286] 1) Step 1

[0287] NG-RAN can perform the NG setup procedure with AMF.

[0288] NG-RAN can send an NG configuration request message to AMF.

[0289] The NG SETUP request message may include NG-RAN capability information related to multi-modal awareness at RAN at the base station.

[0290] The capability information may include granularity information regarding coordinated handling that is supported in the NG-RAN. For example, the capability information may include whether flow-level and / or packet-level coordinated handling is supported.

[0291] The NG SETUP request message can be sent from the NG-RAN node to the AMF to transmit application layer information for the NG-C interface instance.

[0292] For example, the NG-RAN capability information related to multi-modal awareness at RAN at the base station of the NG SETUP request message may include the contents of Table 4.

[0293] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMulti-modal awareness at RAN SupportedOENUMERATED (Flow-level, Packet-level, ...)Indication of support for Multi-modal awareness at RAN.YESignore

[0294] 2) Step 2

[0295] During the terminal's PDU session establishment procedure, the AMF can transmit NG-RAN capability information related to multi-modal awareness at RAN received from the NG-RAN in Step 1 to the SMF.

[0296] The capability information may include whether flow-level and / or packet-level coordinated handling is supported.

[0297] Step 2 can be performed during the PDU session establishment procedure.

[0298] 3) Step 3

[0299] AF can send multimodal service request information through a specific procedure (e.g., AF session with required QoS).

[0300] The AF can send a request message (e.g., AF session with QoS Request) containing multimodal service request information to the NEF.

[0301] The above request message may include a Multi-modal Service ID (hereinafter, MMS ID) and / or a Multi-modal service requirement.

[0302] Multi-modal service requirement information may include synchronization threshold information, which represents the maximum relative delay allowed between different types of data. Alternatively, synchronization threshold information may be pre-configured in the 5G network (or base station (NG-RAN)).

[0303] 4) Step 4

[0304] Based on the AF request of Step 3, if the authentication procedure is successfully performed according to the conventional procedure, the NEF may transmit the multimodal service request information included in the request message to the PCF.

[0305] 5) Step 5

[0306] PCF can update the policy based on AF request information (multimodal service request information) received from NEF.

[0307] The PCF can transmit to the SMF a PCC rule that includes multimodal service-related information (e.g., MMS ID and / or Synchronization Threshold).

[0308] 6) Step 6

[0309] SMF can recognize whether multi-modal awareness at RAN is supported at the base station through Step 2.

[0310] When the SMF receives a PCC rule containing multimodal service requirements (e.g., MMS ID and Synchronization Threshold) from the PCF, it can transmit an N2 message containing multimodal service indication (information indicating multimodal service support in the core network) to the base station (NG-RAN).

[0311] The N2 message may include multimodal service requirements (e.g., MMS ID and Synchronization Threshold) and / or a QoS profile including said multimodal service indication.

[0312] Through N2 messages, the core network can inform the NG-RAN of multimodal service support.

[0313] 7) Step 7

[0314] Based on the multimodal service support notification information of the core network within the N2 message received from the SMF, the NG-RAN can send a reply message (e.g., N2 message) including a request for multimodal information marking.

[0315] The above reply message may include coordinated handling support unit information for multimodal services in NG-RAN (e.g., flow-level or packet-level).

[0316] For example, NG-RAN can selectively inform the core network (5GC) whether to support flow-level or packet-level based on its coordinated handling support unit, operator policy, internal configuration and status information, and can request the necessary information from the core network.

[0317] 2. Second embodiment

[0318] A multi-modal information marking support procedure can be proposed.

[0319] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0320] FIG. 11 illustrates an example of a multimodal information marking procedure according to the disclosure of the present specification.

[0321] 0) step 0

[0322] In Step 7 of the first embodiment, a flow-level or packet-level based multimodal information marking request from NG-RAN can satisfy an SM Policy Association update condition (e.g., Policy Control Request Trigger).

[0323] For example, the PCRT condition for a policy update request can be satisfied by a request for multimodal information marking from NG-RAN.

[0324] For example, access independent Policy Control Request Triggers relevant for SMF may include the contents of Table 5.

[0325] Policy Control Request TriggerDescriptionDifference compared with table 6.2 and table A.4.3-2 in TS 23.203 v19.0.0Conditions for reportingMotivationRequest for Multi-modal informationA request for Multi-modal information for the Multi-modal information marking by the SMF.AddedPCF

[0326] When the PCF receives multimodal information marking from the SMF, it can include a unique multimodal service identifier in the PCC rule for the SMF.

[0327] 1) Step 1

[0328] The PCRT condition can be satisfied by a multi-modal information marking request from NG-RAN. Based on this, the SMF can send a policy information creation / update request message to the PCF.

[0329] The message may be an SM Policy Control Update Request message.

[0330] 2) Step 2

[0331] PCF can generate a unique multi-modal service identifier within the multi-modal service information and update the PCC rule in response to a request from SMF.

[0332] For example, the PCF can generate a unique multimodal service identifier within the operator network based on the AF ID and the MMS ID received from the AF, and include it in the PCC rule.

[0333] For example, a PCF can assign a unique MMS ID. In a PCC rule, the PCF can map the MMS ID received from an existing AF to the assigned unique MMS ID.

[0334] The PCF may send an SM Policy Control Create response message containing an updated PCC rule to the SMF. The updated PCC rule may include a unique Multi-modal Service (MMS) ID.

[0335] 3) Step 3

[0336] The SMF may receive an updated PCC rule containing a unique MMS ID. Then, the SMF may transmit an N4 message containing instructions for multimodal information marking (e.g., multimodal information marking setting information) to the UPF (e.g., N6 PSA (PDU Session Anchor) UPF). This operation may be performed based on a multimodal information marking request from the base station and the base station's multimodal recognition capability information.

[0337] Instructions for multimodal information marking (e.g., multimodal information marking setting information) may include an MMS ID included in an updated PCC rule received by the SMF.

[0338] Instructions for multimodal information marking (e.g., multimodal information marking setting information) can be configured so that the marking information within the GTP-U header of downlink traffic differs depending on the coordinated handling unit supported by the base station (NG-RAN).

[0339] For example, if the base station (NG-RAN) supports flow-level coordinated handling, the SMF can configure the UPF to write the unique MMS ID (included in the received PCC rule) and / or Media Type information into the GTP-U header and send it to the base station (NG-RAN).

[0340] For example, if the base station (NG-RAN) supports packet-level coordinated handling, the SMF can configure the UPF to send the RTP / SRTP sequence number and / or time stamp information (identified by the UPF) together in the GTP-U header to the base station (NG-RAN), as well as the unique MMS ID (included in the received PCC rule) and / or Media Type information.

[0341] For example, instructions for multimodal information marking (e.g., multimodal information marking setting information) may include a separate indication for instructions to write RTP / SRTP sequence number and / or time stamp information (e.g., indication of packet-level multi-modal information marking).

[0342] The above N4 message may include a QoS Enforcement Rule. The QoS Enforcement Rule may include a Multi-modal Information Marking Indicator. The Multi-modal Information Marking Indicator may instruct the UPF to insert multimodal information into the GTP-U header for packets belonging to a multimodal service. The Multi-modal Information Marking Indicator may also indicate whether packet-level multimodal information marking is applied. The UPF may identify DL multimodal traffic and forward the multimodal information in the GTP-U header to the NG-RAN. This field may include the following:

[0343] - Multimodal Service Identifier

[0344] - Media Type

[0345] - Sequence number

[0346] - Timestamp

[0347] 4) Step 4

[0348] The UPF (e.g., N6 PSA UPF) can identify packet(s) corresponding to a specific MMS ID (Multi-modal service identifier) ​​by performing packet inspection on downlink traffic based on configuration information from the SMF. The UPF (e.g., N6 PSA UPF) can perform packet-level or flow-level multi-modal information marking on the GTP-U header information of the identified packets.

[0349] 3. Third embodiment

[0350] A capability negotiation method for multi-modal awareness at RAN at a base station can be proposed.

[0351] The third embodiment may be an embodiment in which the first and second embodiments are combined.

[0352] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0353] FIGS. 12, FIGS. 13, FIGS. 14 and FIGS. 15 illustrate examples of procedures according to the disclosure of the present specification.

[0354] 1) Step 1

[0355] The contents of step 1 of Figs. 9 and 10 may be applied.

[0356] 2) Step 2

[0357] The contents of step 2 of Figs. 9 and 10 may be applied.

[0358] 3) Step 3

[0359] The contents of step 3 of Figs. 9 and 10 may be applied.

[0360] 4) Step 4

[0361] The contents of step 4 of Figs. 9 and 10 may be applied.

[0362] 5) Step 5

[0363] The PCF can update policies based on AF request information received via the NEF. The PCF can send PCC rules to the SMF. PCC rules can include information related to multimodal services.

[0364] Based on the multimodal service request information included in the AF request information received by the PCF, the PCF may determine the Policy Control Request Trigger (PCRT) requirements. The PCF may transmit the determined PCRT requirements to the SMF.

[0365] For example, the PCRT requirements determined above may be generated based on the multimodal service requirements in Step 3. The update requirements for multimodal service-related policies may be generated based on the receipt of multimodal service requirements. When the SMF performs a multimodal information marking decision, the update requirements for multimodal service-related policies may be satisfied. Based on this, the SMF may request a policy update from the PCF.

[0366] 6) Step 6

[0367] If SMF decides to support multi-modal information marking with NG-RAN, SMF can request a policy update from PCF.

[0368] For example, the decision to support multi-modal information marking with SMF's NG-RAN may be based on at least one of the following:

[0369] - Multi-modal awareness capability information of the NG-RAN received by the SMF in Step 2

[0370] - Multimodal service-related information within the PCC rules received by the SMF in Step 5

[0371] - Whether the PCRT conditions set by the PCF are met

[0372] - Business Policy

[0373] - Internal settings

[0374] If the SMF decides to support multi-modal information marking with the NG-RAN, the SMF may send a policy update request to the PCF that includes multi-modal information request information (e.g., Request for Multi-modal information indication).

[0375] A policy update request from the SMF to the PCF may be transmitted after receiving a multimodal information marking request from the NG-RAN in Step 8-step 9 described below. For example, if the SMF determines a multimodal information request based on receiving a multimodal information marking request from the NG-RAN, a policy update request to the PCF may be transmitted after receiving a multimodal information marking request from the NG-RAN.

[0376] For example, if there is no PCRT set from the PCF (e.g., multimodal information request condition), the SMF may send a policy update request to the PCF.

[0377] For example, even if the NG-RAN capability information (multi-modal awareness related capability) is not received, if the PCC rule contains multimodal related information (e.g., MMS ID), the SMF may send a policy update request to the PCF.

[0378] For example, if a multimodal information marking request is received from the base station (NG-RAN) in Step 8-step 9 described below, the SMF may also send a policy update request to the PCF.

[0379] 7) Step 7

[0380] In Step 6, upon receiving a policy update request from the SMF (e.g., an update request including a multimodal information request), the PCF may update the PCC rule by including the MMS ID or a unique MMS ID (a unique MMS ID newly generated based on the MMS ID within the multimodal service information) in the PCC rule.

[0381] PCF can transmit updated information to SMF.

[0382] For example, the unique MMS ID that the PCF generates / includes in the PCC rule may be an MMS ID received from the AF or a unique MMS ID (a unique multimodal service identifier within the operator network newly generated using the MMS ID received from the AF and the AF ID).

[0383] 8) Step 8

[0384] Based on NG-RAN capability information related to multi-modal awareness at RAN at the base station and / or updated PCC rules (e.g., MMS ID, synchronization threshold) received in step 7, the SMF can transmit a QoS profile containing information (e.g., multimodal service indication) that the core network (the core network to which the SMF belongs) supports multimodal services to the base station (NG-RAN) via an N2 message.

[0385] 9) Step 9

[0386] Based on information that the core network supports multimodal services (e.g., multimodal service indication), the base station (NG-RAN) can send a response message containing a request for multimodal information marking to the SMF.

[0387] The above response message may include coordinated handling support unit information (e.g., flow level, packet level) of the multimodal service of the base station (NG-RAN).

[0388] For example, based on the base station's coordinated processing support unit, operator policy, internal settings, status information, etc., the base station (NG-RAN) may optionally include information on the coordinated processing support unit of the multimodal service (e.g., flow level, packet level) in the response message and transmit it to the core network (e.g., SMF).

[0389] For example, a multimodal information marking request transmitted by a base station to an SMF may include coordinated handling support unit information for the multimodal service (e.g., flow level, packet level).

[0390] 10) Step 10

[0391] Based on NG-RAN capability information related to multi-modal awareness at RAN at the base station, information received from the base station in step 9, operator policy and / or internal settings, the SMF may transmit multi-modal information marking setting information (e.g., information instructing multi-modal information marking, unit information related to multi-modal service) to the UPF (e.g., N6 PSA UPF).

[0392] Multimodal information marking setting information (e.g., information instructing multimodal information marking, multimodal service-related unit information) may include an MMS ID included in an updated PCC rule received by the SMF.

[0393] Based on the above multimodal information marking configuration information, UPF can include different marking information within the GTP-U header of downlink traffic depending on the multimodal information marking unit (e.g., flow level, packet level).

[0394] For example, if the base station (NG-RAN) supports coordinated processing of multimodal services at the flow level, based on the multimodal information marking setting information, the SMF can write the unique MMS ID and / or media type information within the PCC rule into the GTP-U header and transmit it to the base station (NG-RAN).

[0395] For example, if the base station (NG-RAN) supports coordinated processing of multimodal services at the packet level, based on the multimodal information marking setting information, the MF can transmit to the base station (NG-RAN) the RTP / SRTP sequence number (and / or time stamp) information (identified by the UPF) as well as the unique MMS ID (and / or media type information) within the PCC rule, by writing the information together in the GTP-U header.

[0396] For example, multimodal information marking configuration information may include a separate indication (e.g., indication of Packet-level Multi-modal Information marking) for instructions to write RTP / SRTP sequence number and / or time stamp information.

[0397] 11) Step 11

[0398] The UPF (e.g., N6 PSA UPF) can identify packet(s) corresponding to a specific MMS ID (Multi-modal service identifier) ​​by performing packet inspection on downlink traffic based on multimodal information marking configuration information from the SMF. The UPF (e.g., N6 PSA UPF) can perform multimodal information marking at the packet level or flow level on the GTP-U header information of the identified packets. The marked downlink traffic can be transmitted to the base station.

[0399] The procedures / methods in the first, second, and third embodiments may be applied to handover procedures and / or session management service procedures (etc.) based on the mobility of the terminal.

[0400] To support coordinated handling of multimodal services at the packet level (or flow level), information that must be provided from the core network (e.g., Multi-modal information marking in the GTP-U header) may be proposed in this specification.

[0401] The method proposed in this specification supports a suitable multimodal information marking mechanism through interaction with a base station (NG-RAN).

[0402] According to the disclosure of this specification, a base station can identify PDU(s) belonging to a multimodal service from downlink traffic. The base station can selectively perform support functions (e.g., coordinated delivery, joint admission control, multi-modal service level discarding, etc.) on the identified PDU(s). This enables more efficient resource scheduling.

[0403] - The first network node (e.g., NG-RAN) can provide the AMF with capability information (capability information regarding multi-modal awareness at RAN support) as well as information on the support unit of coordinated handling.

[0404] - The second network node (e.g., AMF) can transmit capability information (Multi-modal awareness at RAN) and support unit information of coordinated handling received from the NG-RAN to the SMF.

[0405] - A third network node (e.g., PCF) can transmit multimodal service-related requirement information received from AF to SMF by including it in PCC rules.

[0406] - The PCC rules include information on requirements related to multimodal services, and the base station (NG-RAN) is multimodal

[0407] When multi-modal awareness at RAN is supported, the fourth network node (e.g., SMF) may transmit to the base station (NG-RAN) i) information regarding requirements related to the multimodal service and ii) information indicating that the 5GC (core network) supports the multimodal service in an N2 message.

[0408] - The first network node (e.g., NG-RAN) can reply to the multimodal service support notification of 5GC in the N2 message with coordinated handling support unit information.

[0409] According to the second embodiment, the following operation may be performed:

[0410] - Based on a message received from a base station (NG-RAN) (a message including coordinated handling support unit information and a multi-modal information marking request), a fourth network node (e.g., SMF) may transmit a request to the PCF to update policy information including multi-modal awareness at RAN support notification information from the base station.

[0411] - Based on a request for policy information update including multi-modal awareness at RAN support notification information received from the base station from the SMF, the third network node (e.g., PCF) can generate a unique MMS ID within the operator's network and send the updated PCC rule back to the SMF.

[0412] - The fourth network node (e.g., SMF) can configure configuration information for multimodal information marking at the flow level or packet level based on information from the Coordinated Handling Support Unit of the NG-RAN. The fourth network node (e.g., SMF) can transmit configuration information for multimodal information marking to the N6 PSA UPF, including a unique MMS ID within the Operator's network within the PCC rule updated from the PCF.

[0413] - Based on configuration information for multimodal information marking from the SMF, the fifth network node (e.g., UPF) can perform packet inspection on downlink traffic. As a result of the packet inspection, the fifth network node (e.g., UPF) can perform flow-level or packet-level multimodal information marking on the GTP-U header information for packets corresponding to a specific MMS ID.

[0414] According to the third embodiment, the following operation may be performed:

[0415] - The fourth network node (e.g., SMF) can receive capability information regarding multi-modal awareness support of the NG-RAN and / or support unit information for coordinated handling from the AMF.

[0416] - The fourth network node (e.g., SMF) can receive PCRT conditions (e.g., policy request conditions for performing multi-modal information marking) from the PCF.

[0417] - Based on whether the PCRT related to multimodal information marking is satisfied, the ability of the NG-RAN to recognize multimodal information, whether information related to multimodal services is included in the PCC rule, and / or a request for multimodal information marking from the NG-RAN, the fourth network node (e.g., SMF) sends a policy update request to the PCF and can receive PCC rule update information containing information related to multimodal services (e.g., MMS ID and / or Synchronization threshold).

[0418] - Based on the NG-RAN's multimodal awareness capabilities and / or whether information related to multimodal services is included in PCC rules, etc., the fourth network node (e.g., SMF) may send notification information (e.g., Multi-modal indication) that the core network supports multimodal services to the NG-RAN, and receive multimodal information marking request information and / or coordinated handling support unit information from the NG-RAN.

[0419] - Based on the multimodal recognition capabilities of the NG-RAN and / or a request for multimodal information marking from the NG-RAN, the fourth network node (e.g., SMF) may send multimodal information marking instruction information (e.g., Multi-modal information marking activation and / or execution unit information (e.g., Per flow-level or per packet-level marking)) to the UPF.

[0420] - The first network node (e.g., NG-RAN) can send capability information for multi-modal awareness support and / or support unit information for coordinated handling to the AMF during the NG SETUP procedure.

[0421] - The first network node (e.g., NG-RAN) receives notification information from the SMF that the core network supports multimodal services and can transmit multimodal information marking request information and / or coordinated handling support unit information of the NG-RAN.

[0422] According to the first embodiment, a third network node (e.g., PCF) receives a multimodal service-related requirement received from AF and can send PCC rules and / or PCRT conditions (e.g., policy request conditions for performing multi-modal information marking) containing related information to SMF.

[0423] According to the first embodiment, a third network node (e.g., PCF) receives a request for a policy update related to a multimodal service from the SMF and can send PCC rule update information including information related to the multimodal service (e.g., MMS ID and / or Synchronization threshold) to the SMF.

[0424] According to the second embodiment, based on multi-modal information marking related instruction information received from the SMF (e.g., multi-modal information marking activation and / or execution unit information (e.g., per flow-level or per packet-level marking)), the fifth network node (e.g., UPF) can perform flow-level or packet-level multi-modal information marking on GTP-U header information for packets corresponding to a specific multi-modal service for downlink traffic.

[0425] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0426] FIG. 16 illustrates the procedure of the UE for the disclosure of the present specification.

[0427] 1. The SMF (Session Management Function) can receive capability information of the base station from the AMF (Access and Mobility Management Function).

[0428] The above capability information may include information that the base station supports multi-modal awareness.

[0429] 2. The above SMF can receive PCC rules from the PCF (Policy Control Function).

[0430] The above PCC rule may include an MMS (Multi-Modal Service) ID.

[0431] 3. The above SMF can receive a request for marking of multimodal information from the base station.

[0432] 4. Based on the above capability information and the above display request, the SMF can transmit display setting information for multimodal information to the UPF (User Plane Function).

[0433] The above display setting information may include information for performing multimodal information display in the header of the packet corresponding to the MMS ID.

[0434] The above SMF can transmit support information to the base station that the core network supports multimodal services.

[0435] The step of the above SMF receiving the display request from the base station can be performed based on the support information.

[0436] The above display request may include unit information supported by the base station.

[0437] The above unit information may be at the packet level or the flow level.

[0438] The above display setting information may include the above unit information.

[0439] The above SMF can receive a PCRT (Policy Control Request Trigger) requirement from the above PCF.

[0440] Based on the above PCRT requirements and the above capability information, the above SMF can send a policy update request to the above PCF.

[0441] The step of the above SMF receiving the PCC rule from the above PCF can be performed based on the policy update request.

[0442] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0443] FIG. 17 illustrates the procedure of the AMF for the disclosure of the present specification.

[0444] 1. The base station can transmit capability information to the SMF.

[0445] The above capability information may include information that the base station supports multi-modal awareness.

[0446] 2. The base station may transmit a request for marking of multimodal information to the SMF.

[0447] 3. The above base station may include the step of receiving downlink traffic including a display of multimodal information.

[0448] The above base station can receive support information from the above SMF that the core network supports multimodal services.

[0449] The step of the base station transmitting the display request to the SMF can be performed based on the support information.

[0450] The above display request may include unit information supported by the base station.

[0451] The above unit information may be at the packet level or the flow level.

[0452] The display of the above multimodal information may be based on the above unit information.

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

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

[0455] For example, the processor can be configured to be operablely coupled with memory and the processor.

[0456] The operation performed by the above processor comprises: a step in which a Session Management Function (SMF) receives capability information of a base station from an Access and Mobility Management Function (AMF); a step in which the capability information includes information that the base station supports multi-modal awareness, and the SMF receives a PCC rule from a Policy Control Function (PCF); a step in which the PCC rule includes an MMS (Multi-Modal Service) ID, and the SMF receives a request for marking multi-modal information from the base station; and a step in which, based on the capability information and the marking request, the SMF transmits setting information for marking multi-modal information to a User Plane Function (UPF), wherein the setting information may include information for performing multi-modal information marking in the header of a packet corresponding to the MMS ID.

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

[0458] The operation performed by the above processor includes the step of the SMF (Session Management Function) receiving capability information of a base station from the AMF (Access and Mobility Management Function); the capability information includes information that the base station supports multi-modal awareness, and the step of the SMF receiving a PCC rule from the PCF (Policy Control Function); the step of the PCC rule including an MMS (Multi-Modal Service) ID, and the step of the SMF receiving a request for marking multi-modal information from the base station; and the step of the SMF transmitting setting information for marking multi-modal information to the UPF (User Plane Function) based on the capability information and the marking request, wherein the setting information may include information for performing multi-modal information marking in the header of a packet corresponding to the MMS ID.

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

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

[0461] In some examples, storage media are coupled to the processor so that the processor can read information from the storage media. Alternatively, the storage media can be integrated into the processor. The processor and storage media can reside in an ASIC. In other examples, the processor and storage media can reside as separate components.

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

[0463] For example, non-volatile computer-readable media may include RAM (Random Access Memory) such as SDRAM (Synchronization Dynamic Random Access Memory), ROM (Read-Only Memory), and NVRAM (Non-Volatile Random Access Memory); read-only memory (EEPROM); flash memory; magnetic or optical data storage media; or other media that can be used to store instructions or data structures. Non-volatile computer-readable media may also include combinations of the above.

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

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

[0466] One or more stored commands include the steps of: a Session Management Function (SMF) receiving capability information of a base station from an Access and Mobility Management Function (AMF); the capability information including information that the base station supports multi-modal awareness; the SMF receiving a PCC rule from a Policy Control Function (PCF); the PCC rule including a Multi-Modal Service (MMS) ID; the SMF receiving a request for marking multi-modal information from the base station; and, based on the capability information and the marking request, the SMF transmitting setting information for marking multi-modal information to a User Plane Function (UPF), wherein the setting information may include information for performing multi-modal information marking in the header of a packet corresponding to the MMS ID.

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

[0468] This specification may have various effects.

[0469] For example, through the procedures disclosed in this specification, multimodal services can be efficiently provided.

[0470] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive 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.

[0471] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

As a method, A step in which the SMF (Session Management Function) receives capability information of the base station from the AMF (Access and Mobility Management Function); The above capability information includes information that the base station supports multi-modal awareness, and The step of the above SMF receiving a PCC rule from a PCF (Policy Control Function); The above PCC rule includes an MMS (Multi-Modal Service) ID, and The step of the above SMF receiving a request for marking of multimodal information from the base station; Based on the above capability information and the above display request, the SMF transmits display setting information of multimodal information to the UPF (User Plane Function), and A method comprising the above display setting information including information for performing multimodal information display in the header of a packet corresponding to the above MMS ID. In paragraph 1, The above SMF further includes the step of transmitting support information to the base station that the core network supports multimodal services, and The step of the above SMF receiving the above display request from the above base station is a method performed based on the above support information. In paragraph 1 or 2, The above display request includes unit information supported by the base station, and The above unit information is at the packet level or flow level, and The above display setting information is a method including the above unit information. In any one of paragraphs 1 through 3, The step of the above SMF receiving a PCRT (Policy Control Request Trigger) requirement from the above PCF; and Based on the above PCRT requirements and the above capability information, the above SMF further includes the step of sending a policy update request to the above PCF, and The step of the above SMF receiving the above PCC rule from the above PCF is performed based on the above policy update request. As a method, A step in which the base station transmits capability information to the SMF; The above capability information includes information that the base station supports multi-modal awareness, and A step in which the base station transmits a request for marking multimodal information to the SMF; A method comprising the step of the base station receiving downlink traffic including a display of multimodal information. In paragraph 5, The above base station further includes the step of receiving support information from the above SMF that the core network supports multimodal services, and The step of the base station transmitting the display request to the SMF is performed based on the support information. In paragraph 5 or 6, The above display request includes unit information supported by the base station, and The above unit information is at the packet level or flow level, and The display of the above multimodal information is a method based on the above unit information. As an SMF performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above at least one processor is an SMF that is a method according to any one of claims 1 to 4. As a base station performing communication, At least one transmitter / receiver; It includes at least one processor, The operation performed by the above-mentioned at least one processor is an AMF, which is a method according to any one of claims 5 to 7. As an apparatus in mobile communication, At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and A device in which the operation performed based on the execution of the above instruction by the at least one processor is a method according to any one of claims 1 to 4. As a non-volatile computer-readable storage medium that records instructions, A non-volatile computer-readable storage medium in which, when the above instructions are executed by one or more processors, the operation that causes the one or more processors to perform is a method according to any one of claims 1 to 4.

Images