Data collection

Abstract

One disclosure of the present specification provides a method. The method may comprise the steps of: receiving, by a first network entity related to data collection, a request message related to data collection from a second network entity; receiving, by the first network entity, collected data from a UE; and determining, by the first network entity on the basis of information related to restrictions on AI data management, whether to transmit the collected data to the second network entity.

Description

Data Collection

[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, usage, and requirements, including eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type-Communications), and URLLC (Ultra-Reliable and Low Latency Communications). NR must be forward compatible by nature.

[0005] According to conventional technology, there is a problem in that UE data collection is not effectively supported. For example, there is a problem in that the operation for a network to collect UE data through the user plane is not specifically defined.

[0006] According to conventional technology, there is a problem in that UE data collection is not effectively supported. For example, there is a problem in that the operation for a network to collect UE data through the user plane is not specifically defined.

[0007] In one embodiment, a method is provided. The method may include the step of a first network entity related to data collection receiving a request message related to data collection from a second network entity; the step of the first network entity receiving collected data from a UE; and the step of the first network entity determining whether to transmit the collected data to the second network entity based on information related to restrictions on AI data management.

[0008] In another aspect, a device for implementing the above method is provided.

[0009] In one embodiment, a method is provided. The method may include the steps of: a UE transmitting a session establishment request message to a third network entity related to the session; the UE receiving a session establishment acceptance message from the third network entity; and the UE determining whether to transmit collected data to a first network entity related to data collection based on information related to restrictions on AI data management.

[0010] In another aspect, a device for implementing the above method is provided.

[0011] In one embodiment, a method is provided. The method may include the step of a third network entity associated with a session transmitting a session establishment request message from a UE; and the step of the third network entity transmitting a session establishment acceptance message to the UE based on information regarding restrictions on AI data management.

[0012] In another aspect, a device for implementing the above method is provided.

[0013] UE data collection can be effectively supported. For example, UE data collection for AI operations can be effectively supported.

[0014] For example, the operation of the network and / or the operation of the UE for collecting UE data can be defined.

[0015] For example, regarding UE data collection for AI operations, a procedure for using the user plane can be effectively supported.

[0016] For example, based on the constraints on AI data management, UE data collection for AI operations can be effectively supported. For example, based on the constraints on AI data management, a user-plane connection for UE data collection can be effectively established.

[0017] For example, based on technology related to control functions and / or procedures for user plane connections, an operator can perform effective admission control on connections used for AI operations. Users can select effective billing policies, and the efficiency of service usage can be maximized.

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

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

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

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

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

[0023] FIGS. 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0024] FIG. 7 illustrates a first example of a procedure for collecting UE data through a user plane according to one embodiment of the present disclosure.

[0025] FIG. 8 illustrates a second example of a procedure for collecting UE data through a user plane according to one embodiment of the present disclosure.

[0026] FIG. 9 illustrates an example of a procedure for user plane connection according to one embodiment of the present disclosure.

[0027] FIG. 10 illustrates a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0028] FIG. 11 illustrates a second example of a procedure according to one embodiment of the disclosure of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0042] The three main requirement 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.

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

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

[0045] 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), Internet-Of-Things (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 (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices) and HUDs (Head-Up Displays) 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.

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

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

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

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

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

[0051] 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

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

[0053] 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

[0054] 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 eMTC (enhanced MTC). 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 with consideration 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.

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

[0056] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use 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.

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

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

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

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

[0061] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement 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.

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

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

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

[0065] 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 code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or 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 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.

[0066] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and 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.

[0067] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, an 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.

[0068] 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. 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 be composed of Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, 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.

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

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

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

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

[0073] In an implementation of the present specification, the UE may operate as a transmitting device in the uplink and as a receiving device in the downlink. In an implementation of the present 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 the present specification or to control a transceiver (106) to perform UE operations according to an implementation of the present 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 the present specification or to control a transceiver (206) to perform base station operations according to an implementation of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] - AUSF (Authentication Server Function)

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

[0089] - DN (Data Network), for example, operator services, internet access, or third-party services

[0090] - USDF (Unstructured Data Storage Function)

[0091] - NEF (Network Exposure Function)

[0092] - I-NEF (Intermediate NEF)

[0093] - NRF (Network Repository Function)

[0094] - NSSF (Network Slice Selection Function)

[0095] - PCF (Policy Control Function)

[0096] - SMF (Session Management Function)

[0097] - UDM (Unified Data Management)

[0098] - UDR (Unified Data Repository)

[0099] - UPF (User Plane Function)

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

[0101] - AF (Application Function)

[0102] - UE (User Equipment)

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

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

[0105] - NWDAF (Network Data Analytics Function)

[0106] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0131] - 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)

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

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

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

[0135] FIGS. 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

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

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

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

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

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

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

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

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

[0144] First, the procedure of Fig. 5 will be explained.

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

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

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

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

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

[0150] 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 stores the new PDU session ID, S-NSAI(s), and the association of the selected SMF ID.

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

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

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

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

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

[0156] AMF rejects requests from urgently registered UEs where the request type does not indicate "Urgent Request" or "Existing Urgent PDU Session".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0181] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0189] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is explained.

[0190] (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, accepted / rejected QFI list, user plane enforcement policy notification), etc.

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

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

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

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

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

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

[0197] After this step, the AMF delivers the relevant events that the SMF has subscribed to.

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

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

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

[0201] (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 session management subscription data modification.

[0202] A study on 6G mobile communication systems, Release 20 / [FS_6G-REQ] Study on 6G Use Cases and Service Requirements (SP-241391), has been initiated in SA1. Agreed-upon candidate scenarios are scheduled to be added to TR 22.870. However, the discussion is limited to basic requirements, and the definitions of functional structures, procedures, and detailed protocols (stage 2 / stage 3) have not yet begun as studies have not started. In other words, the technologies required to implement actual services have not been defined.

[0203] Meanwhile, for 6G AI use cases, the amount of data required for Artificial Intelligence Machine Learning (AIML) operations and services is vast. Therefore, it is necessary to discuss ways to support the transmission or reception of necessary information between the terminal and the network via the user plane. For example, in 6G, a method utilizing the user plane-based Location Services (LCS) approach used in conventional 5G systems could also be discussed.

[0204] However, according to conventional technology, there is a problem in that UE data collection is not effectively supported. For example, there is a problem in that the operation for the network to collect UE data through the user plane is not specifically defined.

[0205] For example, when a UE performs data collection for AI operations, there is a problem in that no specific method is defined for the UE to transmit the collected data to the network through the user plane.

[0206] In various examples of this specification, methods such as the following examples are proposed to solve the above problems. The methods described below may be performed or used selectively, in combination, or complementarily.

[0207] In this disclosure, examples targeting 5G evolution / 6G systems in zero-touch configuration / operation environments with extended network automation are described. For example, this disclosure describes examples of operations, system functions, and / or procedures that can effectively control the computing capabilities of a mobile communication system.

[0208] For example, examples for effectively supporting UE data collection for AI operations can be described. For instance, examples of procedures for using the user plane to perform UE data collection for AI operations are described. Additionally, examples of control functions and / or procedures for user plane connections are described.

[0209] According to one embodiment of the present disclosure, effective admission control for connections used for AI operations can be performed from the perspective of an operator. According to one embodiment of the present disclosure, from the perspective of a user, an effective billing policy can be selected or the efficiency of service usage can be maximized.

[0210] In this specification, embodiments have been described based on the structure, procedures, messages, etc. of a 5G mobile communication system, but the scope of this specification is not limited thereto. For example, the contents described in the various examples of this specification may also be applied to an evolved form of a 6G mobile communication system.

[0211] Various examples in this specification describe embodiments based on AI data. However, within the scope of this specification, data is not limited to AI data only. For example, the descriptions of AI data in this specification may also apply to data such as the following examples. For example, the descriptions of AI data may also apply to various data that can be transmitted through a user plane data connection established between a terminal and a network. For example, such data may include various data such as sensing data and / or XR-specific service data.

[0212] The AI ​​data management restriction described in the examples of this specification may be applied as a restriction for managing other data as well as AI data. For example, the AI ​​data management restriction may be replaced with a sensing data management restriction, an XR-specific service data management restriction, etc.

[0213] In some implementations, the AI ​​data management restriction described in the examples of this specification may be generalized to subscriber information specialized for such data. Alternatively, the AI ​​data management restriction described in the examples of this specification may be generalized to subscriber information in a combined / integrated form.

[0214] Below, a generalized example for collecting UE data through the user plane is described.

[0215] From FS_AIML_CN_Ph2 SID (SP-250399), the following example needs to be discussed.

[0216] - Work Task (WT)#1: To meet AI / ML requirements for NR air interface operation including UE-side model training, investigate methods and whether to support standardized transmission of UP-based standardized data for UE data collection.

[0217] NOTE 1: The WT#1 scope is based on UP data collection for Option 2 documented in RAN LS RP-243316 and RP-242389.

[0218] NOTE 2: The requirements are described in detail in LS RP-242389 and R2-2411152, which will be considered during the study phase.

[0219] NOTE 3: The impact of WT#1 on user consent and privacy will be handled in cooperation with SA3.

[0220] The following example may be an example for solving key issue #1 (e.g., WT#1).

[0221] In some implementations, the following examples may include operations that support generalized UE data collection through the user plane by applying a user plane-based LCS, similar to the user plane connection between the UE and the LMF described in 3GPP TS 23.273 V19.1.0 S6.18.

[0222] In some implementations, network entities involved in data collection may be included in the core network. For example, network entities involved in data collection within the core network may be referred to as Data collection functions (DCFs).

[0223] For example, the DCF may decide to use the user plane for UE data collection based on at least one of UE subscription data (e.g., subscriber information), UE capabilities, and / or local settings.

[0224] For example, the DCF may instruct the UE to use the user plane by transmitting information related to the establishment of a secure connection to the UE.

[0225] For example, the DCF may send requests related to event reporting to the UE.

[0226] For example, the DCF can receive data collected from the UE. The DCF can transmit the collected data to a UE-side data collection server and / or an OTT server, etc.

[0227] In some implementations, UE subscription data (e.g., subscriber information) may be stored in the UDM. The UE subscription data (e.g., subscriber information) may include at least one of the following pieces of information, for example:

[0228] - DCF ID. For example, the DCF ID may be an identifier (identity) for identifying the DCF. The terminal can identify the DCF based on the DCF ID; and / or

[0229] - Information regarding whether data collection through the user plane between the UE and the DCF is permitted (e.g., permitted or not permitted), etc.; and / or

[0230] - AI Data Management restriction: An AI Data Management restriction may include information regarding restrictions related to the collection of AI data, the transmission of AI data, AI models, and / or the transmission of (final or intermediate) inference results. AI Data Management restrictions may be included in subscriber information.

[0231] In some implementations, the network may transmit URSP and / or UE local configuration information to the terminal. Note that UE local configuration information may be pre-configured in the UE. The URSP and / or UE local configuration information sent by the network to the terminal may include session-related information (e.g., information required by the terminal to establish a session with the network).

[0232] For example, URSP and / or UE local configuration information may include at least one of a DCF address and / or information related to a session for UE data collection (e.g., PDU session information). Information related to a session may include, for example, DNN and / or S-NSSAI.

[0233] In some implementations, AI data management restrictions may include one or more of the following examples of information. For reference, the following examples of information are merely illustrative, and the scope of this specification is not limited to the following examples of information. For example, AI data management restrictions may include any information related to restrictions for data management. For reference, in this specification, AI data management restrictions may also be referred to as AI data management restriction information and / or information related to AI data management restrictions. AI data management restrictions may include one or more of the following examples of information:

[0234] - Information regarding the areas and / or times where AI data collection is permitted (e.g., at least one of allowed area / not allowed area, allowed time / not allowed time, and / or allowed / no-allowed time period);

[0235] - Information regarding the areas and / or times where the transmission of collected AI data is permitted (e.g., allowed area / not allowed area, allowed time / not allowed time, and / or allowed / not-allowed time period);

[0236] - Information regarding the area and / or time where the transmission of the AI ​​model is permitted (allowed area / not allowed area, allowed time / not allowed time, allowed / not-allowed time period); and / or

[0237] - Information regarding the regions and / or times where the transmission of (final / intermediate) results inferred using an AI model is permitted (e.g., allowed area / not allowed area, allowed time / not allowed time, allowed / not-allowed time period).

[0238] In some implementations, Allowed area information and / or not allowed area information included in AI data management restrictions may be based on or include TAI and / or geographical information.

[0239] In some implementations, at least one piece of information included in the subscriber information may be delivered by the UDM to core network functions such as AMF and / or SMF based on the provision mechanism of the subscriber information. Core network functions such as AMF and / or SMF may apply at least one piece of information included in the subscriber information.

[0240] In some implementations, at least one piece of information included in the subscriber information may be transmitted to core network functions, such as a PCF, NEF, and / or a newly defined DCF in one embodiment, based on an interaction process with the UDM. Core network functions, such as a PCF, NEF, and / or a newly defined DCF in one embodiment, may apply at least one piece of information included in the subscriber information.

[0241] For reference, in the various examples of this specification, the operations performed by the DCF may also be performed by a network entity related to the analysis. For example, the network entity related to the analysis may be a Network Data Analytics Function (NWDAF).

[0242] In some implementations, at least one piece of information included in the subscriber information may be transmitted to the base station and / or UE in the form of a policy, a processed policy, and / or a configuration. The base station and / or UE may also apply at least one piece of information included in the subscriber information.

[0243] The following drawings are prepared 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.

[0244] FIG. 7 illustrates a first example of a procedure for collecting UE data through a user plane according to one embodiment of the present disclosure.

[0245] In the example of FIG. 7, the UE side server / OTT server may be an example of a network entity related to a server and / or application. In the present disclosure, the UE side server / OTT server may be replaced with a network entity related to a server and / or application (e.g., Application Function (AF)).

[0246] For example, the UE side server could be a UE side data collection server.

[0247] The example in Fig. 7 shows an example of a high-level procedure for collecting UE data through a user plane.

[0248] 1. A UE side server / OTT server can send a UE data collection request to a core network (e.g., 5G Core Network (5GC)). For example, a UE side server / OTT server can send a UE data collection request to an AMF. In the example of FIG. 7, the recipient to whom the UE side server / OTT server sends the UE data collection request is the AMF, but this is merely an example. A UE side server / OTT server may also send a UE data collection request to any network entity within the core network.

[0249] 2. AMF can select DCF. For example, AMF can select DCF in the same way as LMF search and selection.

[0250] 3. Interactions between AMF and DCF can be performed. For example, an association between AMF and DCF can be established.

[0251] 4. DCF can determine whether to use the user plane for UE data collection. For example, DCF can decide to use the user plane for UE data collection.

[0252] In some implementations, step 4 may be triggered by a request from the AMF.

[0253] In some implementations, a network node (e.g., DCF) may determine whether to use the user plane for UE data collection based on the UE's subscription data (e.g., subscriber information). For example, the UE's subscription data may include information regarding whether data collection through the user plane between the UE and the DCF is permitted (e.g., permitted or not permitted) and / or AI data management restrictions. The network node (e.g., DCF) may also determine whether to use the user plane for UE data collection based on information regarding whether data collection through the user plane between the UE and the DCF is permitted (e.g., permitted or not permitted) and / or AI data management restrictions.

[0254] 5. The DCF can send a UP connection establishment request message. For example, the DCF can send a UP connection establishment request message to the AMF, and the AMF can send a UP connection establishment request message to the UE.

[0255] For example, 3GPP TS 24.572 V19.2.0 may be referenced for the user plane connection establishment procedure. For example, to request the delivery of a USER PLANE CONNECTION ESTABLISHMENT COMMAND message, the DCF may call the Namf_Communication_N1N2MessageTransfer service operation on the AMF. The AMF may deliver the USER PLANE CONNECTION ESTABLISHMENT COMMAND message to the UE via a DL Non Access Stratum (NAS) TRANSPORT message.

[0256] 6. A secure user plane connection may be established between the UE and the DCF. For example, a secure user plane connection may be established between the UE and the DCF via the NG-RAN, AMF, and / or UPF.

[0257] In some implementations, when a user plane is set (or established) between the UE and the DCF, at least one of the following actions may be performed:

[0258] - The UE may have obtained AI data management restriction information from the network. Based on the AI ​​data management restriction information, the UE may determine whether sending a session establishment request message (e.g., a PDU session establishment request message) is permitted. For example, based on the AI ​​data management restriction, the UE may determine whether at least one of the collection of AI data, the transmission of collected AI data, the transmission of an AI model, and / or the transmission of (final / intermediate) results inferred using an AI model is permitted. If, based on the AI ​​data management restriction, at least one of the collection of AI data, the transmission of collected AI data, the transmission of an AI model, and / or the transmission of (final / intermediate) results inferred using an AI model is permitted, the UE may send a session establishment request message (e.g., a PDU session establishment request message) to a network entity (e.g., an SMF) related to the session;

[0259] - A network entity (e.g., SMF) may check subscriber information when determining whether to establish a session (e.g., PDU session) and / or when selecting a UPF. For example, a network entity (e.g., SMF) may determine whether to establish a session (e.g., PDU session) or / or select a UPF based on AI data management restriction information. For example, a network entity (e.g., SMF) may also determine whether the establishment of a session (e.g., PDU session) is permitted or / or the selection of a UPF is permitted based on AI data management restriction information. For example, a network entity (e.g., SMF) may check the location information and / or time information of a terminal (e.g., UE) to verify AI data management restriction information (e.g., to check whether AI data management restrictions are violated). A network entity (e.g., SMF) may determine, based on AI data management restrictions, whether at least one of the collection of AI data, the transmission of collected AI data, the transmission of an AI model, and / or the transmission of (final / intermediate) results inferred using an AI model is permitted. If, based on AI data management restrictions, it is determined that at least one of the collection of AI data, the transmission of collected AI data, the transmission of an AI model, and / or the transmission of (final / intermediate) results inferred using an AI model is permitted, the network entity (e.g., SMF) may transmit an acceptance message for session establishment (e.g., PDU session establishment acceptance message) to a terminal (e.g., UE); and / or

[0260] - A network entity (e.g., SMF) may continuously check the terminal's location information and / or time information, etc. Based on this, the network entity (e.g., SMF) may determine whether the authorized state of at least one of the collection of AI data, the transmission of the collected AI data, the transmission of the AI ​​model, and / or the transmission of (final / intermediate) results inferred using the AI ​​model changes. Based on whether the authorized state changes, the network entity (e.g., SMF) may determine the activation, deactivation, and / or release of a session (e.g., PDU session). If the network entity (e.g., SMF) determines the activation, deactivation, and / or release of a session (e.g., PDU session), it may send a message to the terminal and / or another network entity to perform the activation, deactivation, and / or release of the session (e.g., PDU session).

[0261] 7. The UE can send a UP connection establishment complete message.

[0262] For example, the UE can send a USER PLANE CONNECTION COMPLETE message to the AMF via a UL NAS TRANSPOT message. The AMF can pass the USER PLANE CONNECTION COMPLETE message to the DCF by calling the Namf_Communication_N1MessageNotify service operation.

[0263] 8. The UE may perform UE data collection. For example, the UE may collect at least one of information related to beams measured by the UE, information related to Radio Resource Management (RRM), and / or information related to Channel State Information (CSI) measurements.

[0264] For example, in some implementations, a base station (e.g., NG-RAN) may provide the UE with settings for measuring (or collecting) UE data. For example, these settings may include information regarding the type and / or time of data the UE is to measure (or collect), and / or information regarding the type and / or time of data the UE is to report. For example, the UE may perform UE data collection based on the settings for measuring (or collecting) UE data.

[0265] In some implementations, the UE may have obtained AI data management restriction information from the network. In this case, the UE may determine, based on the AI ​​data management restriction information, whether data collection and / or transmission of collected data is permitted. For example, if data collection is permitted, the UE may collect data. For example, if transmission of collected data is permitted, the UE may transmit the data collected in step 9. For example, the UE may determine, based on the AI ​​data management restriction, whether at least one of the collection of AI data, transmission of collected AI data, transmission of the AI ​​model, and / or transmission of (final / intermediate) results inferred using the AI ​​model is permitted. If at least one of the collection of AI data, transmission of collected AI data, transmission of the AI ​​model, and / or transmission of (final / intermediate) results inferred using the AI ​​model is permitted, the UE may collect data and / or transmit the data collected in step 9.

[0266] 9. The UE can transmit the collected data to the DCF. The DCF can transmit (or expose) the collected data to the UE side server / OTT server.

[0267] For example, based on the request in Step 1, collected data and / or event reports may be notified to the UE side server / OTT server via the DCF.

[0268] In some implementations, event reporting may mean that the UE transmits collected data to the DCF when a specific event occurs. For example, the UE may transmit collected data at a specific time, transmit collected data periodically based on a specific cycle, and / or transmit collected data when a threshold related to the collected data is exceeded.

[0269] In some implementations, when a network node DCF transmits collected data (e.g., AI data) received from a terminal (e.g., UE) to a UE side server / OTT server (or before transmission), it may consider AI Data Management restrictions based on the subscriber information of the terminal (e.g., UE). For example, the DCF may transmit the data if the AI ​​Data Management restrictions are not violated. For example, the DCF may determine, based on the AI ​​Data Management restrictions, whether transmitting the collected data (e.g., AI data) to the UE side server / OTT server is permitted. For example, based on the AI ​​Data Management restrictions, the DCF may determine whether at least one of the following is permitted: AI data collection, transmission of collected AI data, transmission of an AI model, and / or transmission of (final / intermediate) results inferred using an AI model. If at least one of the following is permitted: AI data collection, transmission of collected AI data, transmission of an AI model, and / or transmission of (final / intermediate) results inferred using an AI model, the DCF may transmit the data to the UE side server / OTT server.

[0270] In some implementations, one or more of the following examples of operations may be performed:

[0271] - In Step 1, the UE side server / OTT server may provide information to the DCF to override the terminal's subscriber information. In this case, the DCF may update the subscriber information that the DCF maintains internally.

[0272] - UE side server / OTT server is 3 rd It may be a party AF. In this case, the UE side server / OTT server may exist outside the operator network. In this case, prior to Step 1, by utilizing prior art, 3 rd A party AF (e.g., UE side server / OTT server) can send a request message to the core network via the NEF. This request message may include AI Data Management restriction information. AI Data Management restriction information can be forwarded to Unified Data Management (UDM) / Unified Data Repository (UDR). UDM / UDR can update subscriber information based on the AI ​​Data Management restriction information. UDM / UDR can provision the updated subscriber information to network nodes (e.g., AMF, SMF, UPF, and / or DCF, etc.).

[0273] - Data collected in Step 9 may be determined to be in violation of the AI ​​Data Management restriction. In this case, the DCF may send an error message containing information related to the violation (e.g., information related to the violation of the AI ​​Data Management restriction) to the terminal and other network nodes, UE side server / OTT server, etc.

[0274] - If it is determined in Step 9 that the AI ​​Data Management restriction has been violated, additional subscriber information or operator policies, etc., may be pre-configured or provisioned to perform appropriate actions of the DCF. For example, appropriate actions of the DCF may include at least one of the following: storing collected data for a certain period of time and then delivering it after re-evaluating whether the AI ​​Data Management restriction has been violated, and / or determining how many times such re-evaluation can be performed or retried.

[0275] - If the AI ​​Data Management restriction includes time period information, terminals and / or network nodes (e.g., AMF, SMF, UPF, and / or DCF, etc.) may maintain a timer.

[0276] In some implementations, the DCF can determine whether to use the user plane for UE data collection. The DCF may also notify the UE that the user plane is being used for UE data collection. The DCF may expose collected data and / or event reports received from the UE to a server (e.g., UE side server / OTT server).

[0277] In some implementations, the AMF may select the DCF. The AMF may also interact with the DCF.

[0278] In some implementations, the UE can establish a secure user plane with the DCF for UE data collection. The UE can perform UE data collection. The UE can also provide the collected data to the DCF.

[0279] The following drawings are prepared 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.

[0280] FIG. 8 illustrates a second example of a procedure for collecting UE data through a user plane according to one embodiment of the present disclosure.

[0281] 1. The UE side server / OTT server can send UE data collection requests to the core network (e.g., 5GC). For example, the UE side server / OTT server can send UE data collection requests to the DCF.

[0282] In some implementations, a UE data collection request may also request UE data collection and / or UE data transmission.

[0283] In some implementations, a UE data collection request may include at least one of target UE(s), data configured to be collected, and / or validity conditions for data transfer (e.g., immediate, or time / location for transfer, etc.).

[0284] The UE-side data collection server / OTT server may be located outside the MNO. In this case, the NEF may authenticate the UE data collection request to accept the request.

[0285] 2. DCF can determine whether to use the user plane for UE data collection. For example, DCF can decide to use the user plane for UE data collection.

[0286] In some implementations, the DCF may determine whether to use the user plane for UE data collection based on UE subscriber data (e.g., subscriber information). For example, the subscriber information may include information regarding whether data collection through the user plane between the UE and the DCF is permitted (e.g., permitted or not permitted), and / or AI data management restrictions.

[0287] In some implementations, Step 2 may be triggered by a request from the AMF.

[0288] In some implementations, AMF or DCF may verify user consent for the purpose of collecting UE data and / or training ML models.

[0289] In some implementations, depending on the network deployment, the DCF may be collocated with the Location Management Function (LMF) described in TS 23.273 V19.1.0.

[0290] In some implementations, the network node DCF can determine (1) whether to use the user plane for UE data collection based on the UE's subscriber information. In addition, the network node DCF can consider not only whether the use of the user plane is permitted (e.g., information regarding whether data collection through the user plane between the UE and the DCF is allowed (e.g., allowed or not allowed), but also (2) AI Data Management restrictions.

[0291] For example, the subscriber information of a UE may include (1) information on whether the UP mechanism can be used for the collection / transmission of UE data (e.g., whether the use of the user plane is permitted (e.g., whether data collection through the user plane between the UE and the DCF is allowed) and / or (2) information on restrictions regarding data collection / transmission (e.g., AI Data Management restriction). For example, the AI ​​Data Management restriction may include restrictions related to the collection of AI data, transmission of AI data, transmission of AI models, and / or transmission of (final or intermediate) inference results, etc. The AI ​​Data Management restriction may be included in the subscriber information.

[0292] In some implementations, AI data management restrictions may include one or more of the following examples of information. For reference, the following examples of information are merely illustrative, and the scope of this specification is not limited to the following examples of information. For example, AI data management restrictions may include any information related to restrictions for data management. AI data management restrictions may include one or more of the following examples of information:

[0293] - Information regarding the areas and / or times where AI data collection is permitted (e.g., at least one of allowed area / not allowed area, allowed time / not allowed time, and / or allowed / no-allowed time period);

[0294] - Information regarding the areas and / or times where the transmission of collected AI data is permitted (e.g., allowed area / not allowed area, allowed time / not allowed time, and / or allowed / not-allowed time period);

[0295] - Information regarding the area and / or time where the transmission of the AI ​​model is permitted (allowed area / not allowed area, allowed time / not allowed time, allowed / not-allowed time period); and / or

[0296] - Information regarding the regions and / or times where the transmission of (final / intermediate) results inferred using an AI model is permitted (e.g., allowed area / not allowed area, allowed time / not allowed time, allowed / not-allowed time period).

[0297] In some implementations, Allowed area information and / or not allowed area information included in AI data management restrictions may be based on or include TAI and / or geographical information.

[0298] In some implementations, although not explicitly illustrated in the example of FIG. 8, the DCF may perform the following actions. In some implementations, the DCF may obtain subscriber information from the UDM and / or UDR. For example, the DCF may request subscriber information from the UDM and / or UDR and receive subscriber information from the UDM and / or UDR. In some implementations, based on a conventional subscriber information provision mechanism, the UDM / UDR may pass subscriber information to core network functions such as the AMF and SMF. Core network functions such as the AMF and SMF may further pass subscriber information to the DCF.

[0299] In some implementations, the SMF and / or PCF may include such AI data management restriction information in a format understandable to the base station (e.g., Quality of Service (QoS) profiles and / or new profiles similar to QoS profiles). The SMF and / or PCF may transmit information in a format understandable to the base station containing the AI ​​data management restriction information to the base station. For example, the base station may check the AI ​​data management information, determine whether permission is granted (or whether AI data management restrictions are violated), and control data collection and / or data transmission. For example, if the base station determines that transmission is not permitted in a certain area or time, the base station may perform controls such as discarding collected data or delaying transmission by storing it in a buffer for a certain period.

[0300] In some implementations, the SMF and / or PCF may include such AI data management restriction information in information that the terminal can understand (e.g., QoS rules or new rules similar to QoS rules, and / or UE policies or new policies similar to UE policies). The SMF and / or PCF may transmit information containing AI data management restriction information to the terminal in a format that the base station can understand. The terminal may check the AI ​​data management information, determine whether permission is granted (or whether the AI ​​data management restriction is violated), and control data collection and / or data transmission. For example, if the terminal determines that it is in an area or time where transmission is not permitted, the terminal may perform controls such as discarding collected data or delaying transmission by storing it in a buffer for a certain period of time.

[0301] In Step 2, if the AI ​​Data Management restriction of subscriber information is not violated, the DCF may send a message to the terminal to establish a UP connection in Step 3. If the AI ​​Data Management restriction is violated, the DCF may send a response message to the AF (e.g., UE side server / OTT server) along with the reason for failure / rejection.

[0302] 3. The DCF can send a UP connection establishment request message. For example, the DCF can send a UP connection establishment request message to the AMF, and the AMF can send a UP connection establishment request message to the UE.

[0303] In some implementations, the DCF may include information requesting data collection (e.g., a request for “transmission of data collected by the UE”) in the UP connection establishment request message.

[0304] In some implementations, after step 5, the DCF may transmit information requesting data collection to the terminal.

[0305] For example, regarding the user plane connection establishment procedure, 3GPP TS 24.572 V19.1.0 S6.2.1 may be referenced. For example, to request the delivery of a USER PLANE CONNECTION ESTABLISHMENT COMMAND message, the DCF may call the Namf_Communication_N1N2MessageTransfer service operation on the AMF. The AMF may deliver the USER PLANE CONNECTION ESTABLISHMENT COMMAND message to the UE via a DL Non Access Stratum (NAS) TRANSPORT message.

[0306] 4. A secure user plane connection can be established between the UE and the DCF.

[0307] For example, if an established session (e.g., PDU session) does not exist for the UE to DCF PDU connectivity service, the UE can establish a session (e.g., PDU session). The UE can also establish a Transport Layer Security (TLS) connection with the DCF. A secure user plane connection can be established between the UE and the DCF.

[0308] For reference, URSP rules or UE local settings may be used to enable the routing of collected data through specific PDU sessions. For example, specific PDU sessions may be identified based on associated DNNs and / or S-NSSAIs. “UE data collection” traffic is identified by PDU sessions containing associated DNNs and / or S-NSSAIs, and settings regarding which DNNs and / or S-NSSAIs to use, etc., may be determined by the operator and / or SLA.

[0309] For reference, the example in FIG. 9 below may be referenced as an example of a detailed procedure related to the user plane connection established between the UE and the DCF.

[0310] 5. The UE can send a UP connection establishment complete message.

[0311] For example, the UE can send a USER PLANE CONNECTION COMPLETE message to the AMF via a UL NAS TRANSPOT message. The AMF can pass the USER PLANE CONNECTION COMPLETE message to the DCF by calling the Namf_Communication_N1MessageNotify service operation.

[0312] In some implementations, after a secure user plane connection is established, the DCF may send a request to the UE for “transmission of data collected by the UE” via UP signaling. The request for “transmission of data collected by the UE” may include information regarding the initiation or termination of data transmission and / or conditions for data transmission (e.g., immediately, or time / location for transmission, etc.).

[0313] 6. The UE may perform UE data collection. For example, the UE may collect at least one of information related to beams measured by the UE, information related to Radio Resource Management (RRM), and / or information related to Channel State Information (CSI) measurements.

[0314] For example, in some implementations, a base station (e.g., NG-RAN) may provide the UE with settings for measuring (or collecting) UE data. For example, these settings may include information regarding the type and / or time of data the UE is to measure (or collect), and / or information regarding the type and / or time of data the UE is to report. For example, the UE may perform UE data collection based on the settings for measuring (or collecting) UE data.

[0315] For reference, the configuration and / or triggers in the UE and NG-RAN for data collection may be defined on a use case basis. In some implementations, data collection between the UE and NG-RAN may be performed independently of the request in Step 1.

[0316] In some implementations, the UE may obtain (or receive) information regarding AI data management restrictions from the network. In this case, the UE can determine whether the AI ​​data management restrictions are violated. Based on the information regarding AI data management restrictions, the UE may also determine whether data collection and / or the transmission of collected data is permitted.

[0317] For example, if the AI ​​data management restrictions are not violated (e.g., if data collection is permitted), the UE may collect data. For example, if the AI ​​data management restrictions are not violated (e.g., if the transmission of collected data is permitted), the UE may transmit the data collected in Step 7. For example, the UE may determine, based on the AI ​​data management restrictions, whether at least one of the collection of AI data, the transmission of collected AI data, the transmission of the AI ​​model, and / or the transmission of (final / intermediate) results inferred using the AI ​​model is permitted. If at least one of the collection of AI data, the transmission of collected AI data, the transmission of the AI ​​model, and / or the transmission of (final / intermediate) results inferred using the AI ​​model is permitted, the UE may collect data and / or transmit the data collected in Step 7.

[0318] In some implementations, if the UE determines that AI data management restrictions have been violated, at least one of the following actions may be performed:

[0319] - The UE may wait until any violation of AI data management restrictions is resolved. For example, the UE may wait until the AI ​​data management restrictions are no longer violated. Once the AI ​​data management restrictions are no longer violated, the UE may collect data or / or transmit the data collected in Step 7; and / or

[0320] - The UE may notify the network (e.g., DCF) of information regarding violations of AI data management restrictions. For example, the UE may simply notify the network of a failure (or error) situation. As another example, the UE may notify the network of information that it will perform data collection and / or data transmission once the failure (or error) situation and / or AI data management restrictions are no longer violated. For example, the UE may also notify the network of the situation regarding data collection and / or data transmission.

[0321] 7. The UE can transmit the collected data to the DCF. The DCF can transmit (or expose) the collected data to the UE side server / OTT server.

[0322] For example, based on the request of Step 1, (where event data collection is allowed, such as with Deferred MT-LR in TS 23.273 V19.2.0) the collected data and / or event reports may be notified to the UE side server / OTT server via the DCF.

[0323] In some implementations, event reporting may mean that the UE transmits collected data to the DCF when a specific event occurs. For example, the UE may transmit collected data at a specific time, transmit collected data periodically based on a specific cycle, and / or transmit collected data when a threshold related to the collected data is exceeded.

[0324] In some implementations, the DCF may perform the following actions before transmitting (or exposing) the collected data to the UE side server / OTT server. For example, the DCF may verify whether the collected UE data is standardized data and / or whether the collected UE data matches the request in Step 1.

[0325] In some implementations, when a network node DCF transmits collected data (e.g., AI data) received from a terminal (e.g., UE) to a UE side server / OTT server (or before transmission), it may consider an AI Data Management restriction based on the terminal's (e.g., UE) subscriber information.

[0326] For example, the DCF may transmit data if the AI ​​Data Management restriction is not violated. For example, the DCF may determine whether transmitting collected data (e.g., AI data) to the UE side server / OTT server is permitted. For example, based on the AI ​​Data Management restriction, the DCF may check whether at least one of the following is permitted: AI data collection, transmission of collected AI data, transmission of AI models, and / or transmission of (final / intermediate) results inferred using AI models. If at least one of the following is permitted: AI data collection, transmission of collected AI data, transmission of AI models, and / or transmission of (final / intermediate) results inferred using AI models, the DCF may transmit the data to the UE side server / OTT server.

[0327] In some implementations, if the AI ​​Data Management restriction is violated, the DCF may perform at least one of the following actions:

[0328] - DCF can send a response message to AF (e.g., UE side server / OTT server) along with the reason for failure and / or rejection;

[0329] - DCF may store collected data for a certain period of time and, once AI Data Management restrictions are not violated, transmit the collected data to AF (e.g., UE side server / OTT server); and / or

[0330] - The DCF may request the terminal (e.g., UE) to transmit data again. After receiving data from the terminal (e.g., UE), if the AI ​​Data Management restriction is not violated, the DCF may transmit the collected data to the AF (e.g., UE side server / OTT server).

[0331] Referring to FIG. 9, a detailed example of the user plane connection established between the UE and the DCF in step 4 of FIG. 8 is described.

[0332] The following drawings are prepared 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.

[0333] FIG. 9 illustrates an example of a procedure for user plane connection according to one embodiment of the present disclosure.

[0334] 1. A UE can establish a PDU session. For example, actions such as the following example may be performed.

[0335] 1-1. The UE can send a PDU session establishment request message to the SMF.

[0336] For example, the UE may receive a message from the network regarding the establishment of an UP connection in step 3 of FIG. 8. If there is no PDU session for a connection from the UE to the DCF, the UE must first establish a PDU session.

[0337] Before performing Step 1-1 (e.g., before the UE sends a PDU session establishment request message), the UE can check whether the AI ​​Data Management restriction is violated based on a policy including AI Data Management restriction information received from the network. If the AI ​​Data Management restriction is not violated (e.g., if data transmission is allowed), the UE can send a PDU session establishment request message to the SMF.

[0338] 1-2. SMF can send N4 rules to UPF.

[0339] In some implementations, a network node SMF that receives a PDU session establishment request message can check subscriber information (e.g., AI Data Management restriction information). For example, the SMF can determine whether the AI ​​Data Management restriction is violated. Based on the AI ​​Data Management restriction, the SMF can decide whether to establish the PDU session, and / or select a UPF and generate an N4 rule to send to the UPF. For example, if the AI ​​Data Management restriction is not violated, the SMF may decide to establish the PDU session. If the AI ​​Data Management restriction is not violated, the SMF may select a UPF and generate an N4 rule. In this case, the SMF can send the N4 rule to the UPF.

[0340] In some implementations, to determine whether the AI ​​Data Management restriction is violated, the SMF may check the terminal's location information and / or the terminal's time information. For example, the SMF may check the terminal's location information and / or the terminal's time information according to prior art or based on information transmitted by the terminal.

[0341] 1-3. UPF can send a response to the N4 rule to SMF.

[0342] In some implementations, the UPF may have received AI Data Management restriction information from other network nodes in advance. In this case, the UPF can determine whether the AI ​​Data Management restriction is violated before sending a response to the N4 rule. Based on the AI ​​Data Management restriction, the UPF can decide whether to establish an association between the SMF and the UPF. For example, the UPF may decide to establish an association between the SMF and the UPF if the AI ​​Data Management restriction is not violated.

[0343] In some implementations, UPF may additionally consider operator policies configured in UPF along with AI Data Management restrictions. For example, even if some or all of the AI ​​Data Management restrictions are violated, UPF may proceed with establishing a PDU session based on local policies pre-configured in UPF. For example, in this case, UPF may send a response to the N4 rule.

[0344] 1-4. SMF can send a PDU session establishment acceptance message to the UE.

[0345] In some implementations, the network node SMF may continuously check the terminal's location information and / or time information, etc. Based on this, the SMF may decide to enable, disable, and / or release a session (e.g., PDU session) based on a change in authorized state information (e.g., a change in whether an AI Data Management restriction is violated). If the SMF decides to enable, disable, and / or release a session (e.g., PDU session), it may send a message to the terminal and / or other network entities to perform the enable, disable, and / or release of the session (e.g., PDU session).

[0346] 2. A PDU session may be established. For example, when the terminal receives an Accept message regarding the establishment of a PDU session, the PDU session is established.

[0347] 3-1. The terminal can send TLS-related messages (e.g., TLS setup request messages) to the DCF.

[0348] For example, the terminal can send TLS-related messages (e.g., TLS setup request messages) to the DCF through the established PDU session.

[0349] In some implementations, before sending a TLS setup request message to the PCF, the terminal may determine whether an AI Data Management restriction is violated based on a policy containing AI Data Management restriction information received from the network. If the AI ​​Data Management restriction is not violated (e.g., if the AI ​​Data Management restriction is not violated for data transmission), the terminal may send a TLS setup request message to the network (e.g., DCF).

[0350] 3-2. The DCF can send a TLS setup acceptance message to the UE.

[0351] For example, a DCF that receives a TLS setup request message from a terminal can determine whether to establish TLS based on subscriber information (e.g., AI Data Management restriction information). For example, if the AI ​​Data Management restriction is not violated, the DCF can send a TLS setup acceptance message to the UE.

[0352] In some implementations, additionally, the DCF may also consider operator policies set in the DCF along with AI Data Management restrictions. For example, even if some or all of the AI ​​Data Management restrictions are violated, the DCF may proceed with establishing a TLS session based on local policies pre-set in the DCF. For example, in this case, the DCF may send a TLS setup acceptance message to the UE.

[0353] In some implementations, the network node DCF may continuously check the terminal's location information and / or time information, etc., after sending the TLS setup acceptance message. The DCF may decide to release the relevant TLS session, etc., based on a change in the permitted state information (e.g., a change in whether the AI ​​Data Management restriction is violated). If the DCF decides to release the TLS session, the DCF may send a message to the terminal and / or other network nodes to perform the release of the TLS session, etc.

[0354] For reference, the operation of verifying subscriber information must not be performed at every step described in the various examples disclosed in this specification. For example, the operation of verifying subscriber information (e.g., AI Data Management restriction) may be performed at least one step among the various steps described in which the operation of verifying subscriber information (e.g., AI Data Management restriction) is described.

[0355] 4. A secure user plane connection may be established. For example, when a UE receives an acceptance message for establishing a TLS session, a secure user plane connection may be established. For example, a secure user plane connection may refer to a secure UP connection session.

[0356] For reference, in this specification, network node and network entity may be used as terms with the same meaning.

[0357] In some implementations, a network node associated with the session (e.g., SMF) can obtain (or receive) subscriber information related to AI data management from a network node associated with the data (e.g., UDM / UDR).

[0358] In some implementations, a network node associated with a session (e.g., SMF) may determine whether an AI data management restriction is violated. For example, based on the result of the above determination, the network node associated with the session (e.g., SMF) determines PDU session management. PDU session management may include at least one of establishing, activating, deactivating, and / or releasing a PDU session. The network node associated with the session (e.g., SMF) may send a message to other network nodes and / or terminals to perform at least one of establishing, activating, deactivating, and / or releasing a PDU session.

[0359] In some implementations, a network node involved in data collection (e.g., DCF) can obtain (or receive) UE subscriber information (e.g., subscriber information related to AI data management) from a network node involved in data (e.g., UDM / UDR).

[0360] In some implementations, a network node involved in data collection (e.g., DCF) can determine whether an AI data management restriction is violated. For example, in some implementations, a network node involved in data collection (e.g., DCF) may decide whether to use a user plane connection based on the result of the above determination. In some implementations, a network node involved in data collection (e.g., DCF) may send a message to other network nodes and / or terminals to use a user plane connection.

[0361] In some implementations, a network node involved in data collection (e.g., DCF) may receive AI-related data, such as collected AI data, and / or event notifications from a terminal (e.g., UE) via a user plane connection. The network node involved in data collection (e.g., DCF) may determine whether an AI data management restriction is violated. Based on the result of the above determination, the collected data may be transmitted to a UE side server / OTT server.

[0362] In some implementations, a terminal (e.g., UE) may receive information related to AI data management (e.g., AI data management restriction) directly and / or indirectly from a network. In some implementations, a terminal (e.g., UE) may receive instructions from a network (e.g., DCF) to establish (or set up) a user plane connection. The terminal (e.g., UE) may determine whether the AI ​​data management restriction is violated by comparing the terminal's (e.g., UE) location and / or time, etc.

[0363] In some implementations, the terminal (e.g., UE) may send a PDU session establishment message to the network based on the result of the decision. In some implementations, the terminal (e.g., UE) may collect AI data based on the result of the decision, and / or send the collected data to the network (e.g., DCF).

[0364] The following drawings are prepared 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.

[0365] FIG. 10 illustrates a first example of a procedure according to one embodiment of the disclosure of the present specification.

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

[0367] For example, regarding the example of FIG. 10, the operations described in the examples of FIG. 1 through 9 may also be applied. For example, even if the operations, contents, etc. are not directly described in the example of FIG. 10, the operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0368] For example, in the example of FIG. 10, the first network entity may be a network entity involved in data collection (e.g., DCF).

[0369] For example, in the example of FIG. 10, the second network entity may be a server or an AF. The second network entity may be, for example, a UE side server and / or an OTT server as described in various examples of the present disclosure.

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

[0371] In step (S1001), the second network entity can send a request message related to data collection to the first network entity.

[0372] In step (S1002), the UE can transmit the collected data to the first network entity.

[0373] In step (S1003), the first network entity can determine whether to transmit the collected data to the first network entity.

[0374] For example, the first network entity may decide whether to transmit the collected data to the second network entity based on information regarding restrictions on Artificial Intelligence (AI) data management.

[0375] In some implementations, information regarding restrictions on AI data management may include at least one of information regarding a region where data collection is permitted, information regarding a time where data collection is permitted, information regarding a region where data transmission is permitted, information regarding a time where data transmission is permitted, information regarding a region where transmission of an Artificial Intelligence (AI) model is permitted, information regarding a time where transmission of the AI ​​model is permitted, information regarding a region where transmission of results inferred based on the AI ​​model is permitted, or information regarding a time where transmission of results inferred based on the AI ​​model is permitted.

[0376] In some implementations, based on the fact that the restrictions on AI data management are not violated, the first network entity may transmit the collected data to the second network entity.

[0377] In some implementations, the first network entity may send a user plane connection establishment request message to the UE. In this case, the first network entity may receive a user plane connection establishment completion message from the UE.

[0378] In some implementations, the first network entity may determine whether to send a request message to the UE to establish a user plane connection based on at least one of information regarding whether using a user plane for data collection is permitted or information regarding restrictions on AI data management.

[0379] In some implementations, the first network entity may obtain subscriber information of the UE. For example, the subscriber information of the UE may include at least one of information related to restrictions on data management or information related to whether the use of the user plane for data collection is permitted.

[0380] In some implementations, the UE of FIG. 10 may perform the operation of the UE according to the example of FIG. 11 below.

[0381] The following drawings are prepared 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.

[0382] FIG. 11 illustrates a second example of a procedure according to one embodiment of the disclosure of the present specification.

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

[0384] For example, regarding the example of FIG. 11, the operations described in the examples of FIG. 1 through 10 may also be applied. For example, even if the operations, contents, etc. are not directly described in the example of FIG. 11, the operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0385] For example, in the example of FIG. 11, the first network entity may be a network entity involved in data collection (e.g., DCF).

[0386] For example, in the example of FIG. 11, the second network entity may be a server or an AF. The second network entity may be, for example, a UE side server and / or an OTT server as described in various examples of the present disclosure.

[0387] For example, in the example of FIG. 11, the third network entity may be a network entity related to the session. For example, the third network entity may be an SMF.

[0388] The operations illustrated in FIG. 11 are merely examples, and the scope of disclosure of this specification is not limited to the operations illustrated in FIG. 11. For example, the first network entity of FIG. 11 may also perform the operations of the first network entity described in the example of FIG. 10.

[0389] In some implementations, the UE may obtain information related to the restrictions on the management of the AI ​​data mentioned above.

[0390] In some implementations, a third network entity may obtain subscriber information of the UE that includes information related to restrictions on AI data management. For example, the third network entity may obtain (or receive) subscriber information related to AI data management from a network entity related to data (e.g., UDM / UDR).

[0391] In step (S1101), the second network entity can send a request message related to data collection to the first network entity.

[0392] In some implementations, a request message related to data collection may include information related to requesting at least one of the data collection or data transmission.

[0393] In step (S1102), the UE can send a session establishment request message to a third network entity.

[0394] In some implementations, the UE may receive a user plane connection establishment request message from the first network entity. Based on the receipt of the user plane connection establishment request message, the session establishment request message may be transmitted.

[0395] In some implementations, based on the receipt of the session establishment request message and information regarding restrictions on AI data management, the third network entity may transmit an N4 rule to a fourth network entity related to the user plane. The third network entity may receive a response to the N4 rule from the fourth network entity. Based on the receipt of the response to the N4 rule, the third network entity may transmit a session establishment acceptance message.

[0396] In step (S1103), the third network entity can send a session establishment acceptance message to the UE.

[0397] In some implementations, a third network entity may send a session establishment acceptance message to the UE based on information regarding restrictions on AI data management. For example, the third network entity may send the session establishment acceptance message based on the fact that the restrictions on AI data management are not violated.

[0398] Based on the reception of the above session establishment acceptance message, the UE may also send a user plane connection establishment completion message to the first network entity.

[0399] The UE can perform data collection. For example, the UE can perform data collection based on information related to restrictions on AI data management. The data collected by the UE based on data collection may be AI-related data.

[0400] In step (S1104), the UE can decide whether to transmit the collected data.

[0401] For example, the UE may determine whether to transmit the collected data to a first network entity involved in data collection based on information regarding restrictions on Artificial Intelligence (AI) data management.

[0402] In some implementations, information regarding restrictions on AI data management may include at least one of information regarding a region where data collection is permitted, information regarding a time where data collection is permitted, information regarding a region where data transmission is permitted, information regarding a time where data transmission is permitted, information regarding a region where transmission of an Artificial Intelligence (AI) model is permitted, information regarding a time where transmission of the AI ​​model is permitted, information regarding a region where transmission of results inferred based on the AI ​​model is permitted, or information regarding a time where transmission of results inferred based on the AI ​​model is permitted.

[0403] In step (S1105), the UE can transmit the collected data to the first network entity.

[0404] For example, the UE may transmit the collected data to the first network entity based on the fact that the restrictions on AI data management are not violated.

[0405] This specification may have various effects.

[0406] UE data collection can be effectively supported. For example, UE data collection for AI operations can be effectively supported.

[0407] For example, the operation of the network and / or the operation of the UE for collecting UE data can be defined.

[0408] For example, regarding UE data collection for AI operations, a procedure for using the user plane can be effectively supported.

[0409] For example, based on the constraints on AI data management, UE data collection for AI operations can be effectively supported. For example, based on the constraints on AI data management, a user-plane connection for UE data collection can be effectively established.

[0410] For example, based on technology related to control functions and / or procedures for user plane connections, an operator can perform effective admission control on connections used for AI operations. Users can select effective billing policies, and the efficiency of service usage can be maximized.

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

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

[0413] Additionally, instructions for performing the operation of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of the terminal described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0414] For reference, the operation of a network node (e.g., AMF, SMF, UPF, NWDAF, NEF, DCF, UE side server, OTT server, AF, etc.) or a base station (e.g., NG-RAN, gNB, RAN, (R)AN, etc.) described in this specification may be implemented by the device of FIGS. 1 to 3, which will be described below. For example, the network node or base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of a network node or base station described in this specification may be processed by one or more processors (102 or 202). The operation of a terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) can control one or more memories (104 or 204) and one or more transceivers (106 or 206) and execute instructions / programs stored in one or more memories (104 or 204) to perform the operation of a network node or base station as described in the disclosure of this specification.

[0415] Additionally, instructions for performing the operation of a network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transient) computer-readable storage medium. The storage medium may be contained in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of a network node or base station described in the disclosure of this specification by being executed by one or more processors (102 or 202).

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

[0417] In the exemplary system described above, methods are described based on a flowchart as a series of steps or blocks, but are not limited to the order of the described steps, and some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, a person skilled in the art will understand that the steps shown in the flowchart are not exclusive, and that other steps may be included, or that one or more steps of the flowchart may be omitted without affecting the scope of rights.

[0418] 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

1. A first network entity related to data collection receives a request message related to data collection from a second network entity; The first network entity receives collected data from User Equipment (UE); and A method comprising the step of determining whether the first network entity transmits the collected data to the second network entity based on information regarding restrictions on Artificial Intelligence (AI) data management.

2. In Paragraph 1, A method comprising at least one of the following: information regarding restrictions on the management of the AI ​​data, wherein the information regarding the restriction on the AI ​​data management includes: information regarding the region where data collection is permitted; information regarding the time where data collection is permitted; information regarding the region where data transmission is permitted; information regarding the time where data transmission is permitted; information regarding the region where transmission of an Artificial Intelligence (AI) model is permitted; information regarding the time where transmission of the AI ​​model is permitted; information regarding the region where transmission of results inferred based on the AI ​​model is permitted; or information regarding the time where transmission of results inferred based on the AI ​​model is permitted.

3. In Paragraph 1 or 2, A method further comprising the step of the first network entity transmitting the collected data to the second network entity based on the fact that the restriction on AI data management is not violated.

4. In any one of paragraphs 1 through 3, The first network entity transmits a user plane connection establishment request message to the UE; and A method further comprising the step of the first network entity receiving a user plane connection establishment completion message from the UE.

5. In Paragraph 4, A method further comprising the step of determining whether the first network entity sends a request message to establish a user plane connection to the UE based on at least one of information regarding whether the use of the user plane for data collection is permitted or information regarding restrictions on the management of the AI ​​data.

6. In any one of paragraphs 1 through 5, The above first network entity further includes the step of acquiring subscriber information of the UE, and A method wherein the subscriber information of the above UE comprises at least one of information related to restrictions on data management or information related to whether the use of the user plane for data collection is permitted.

7. In any one of paragraphs 1 through 6, A method in which a request message related to the above data collection includes information related to requesting at least one of the above data collection or data transmission.

8. In the device, At least one transmitter / receiver; At least one processor; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is: a device adapted to perform a method according to any one of claims 1 to 7.

9. A step in which the User Equipment (UE) sends a session establishment request message to a third network entity associated with the session; The step of the UE receiving a session establishment acceptance message from the third network entity; and A method comprising the step of determining whether the above UE transmits the collected data to a first network entity involved in data collection based on information regarding restrictions on Artificial Intelligence (AI) data management.

10. In Paragraph 9, A method comprising at least one of the following: information regarding restrictions on the management of the AI ​​data, wherein the information regarding the restriction on the AI ​​data management includes: information regarding the region where data collection is permitted; information regarding the time where data collection is permitted; information regarding the region where data transmission is permitted; information regarding the time where data transmission is permitted; information regarding the region where transmission of an Artificial Intelligence (AI) model is permitted; information regarding the time where transmission of the AI ​​model is permitted; information regarding the region where transmission of results inferred based on the AI ​​model is permitted; or information regarding the time where transmission of results inferred based on the AI ​​model is permitted.

11. In Paragraph 9 or 10, A method further comprising the step of the UE transmitting the collected data to the first network entity based on the fact that the restriction on AI data management is not violated.

12. In any one of paragraphs 9 through 11, The above UE further includes the step of receiving a user plane connection establishment request message from the first network entity, and A method in which the session establishment request message is transmitted based on the reception of the above user plane connection establishment request message.

13. In any one of paragraphs 9 through 12, A method further comprising the step of the UE transmitting a user plane connection establishment completion message to the first network entity based on the reception of the session establishment acceptance message.

14. In any one of paragraphs 9 through 13, A method comprising the step of the above UE further performing data collection based on information related to the limitations on the AI ​​data management.

15. In any one of paragraphs 9 through 14, A method comprising the step of the above UE further acquiring information related to the limitations on the AI ​​data management.

16. In a device, the device is: At least one transmitter / receiver; At least one processor; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is: a device adapted to perform the method according to any one of claims 9 to 15.

17. A third network entity associated with the session transmits a session establishment request message from the User Equipment (UE); and The method includes the step of the third network entity sending a session establishment acceptance message to the UE based on information regarding restrictions on Artificial Intelligence (AI) data management, and A method in which a session establishment acceptance message is transmitted based on the fact that the above restrictions on AI data management are not violated.

18. In Paragraph 17, A method comprising at least one of the following: information regarding restrictions on the management of the AI ​​data, wherein the information regarding the restriction on the AI ​​data management includes: information regarding the region where data collection is permitted; information regarding the time where data collection is permitted; information regarding the region where data transmission is permitted; information regarding the time where data transmission is permitted; information regarding the region where transmission of an Artificial Intelligence (AI) model is permitted; information regarding the time where transmission of the AI ​​model is permitted; information regarding the region where transmission of results inferred based on the AI ​​model is permitted; or information regarding the time where transmission of results inferred based on the AI ​​model is permitted.

19. In Paragraph 17 or 18, A method comprising the step of the third network entity further acquiring subscriber information of the UE including information related to restrictions on AI data management.

20. In any one of paragraphs 17 through 19, The step of the third network entity transmitting an N4 rule to a fourth network entity related to the user plane, based on the receipt of the session establishment request message and information related to the restrictions on AI data management; and The above 3 network entities further include the step of receiving a response regarding the N4 rule from the above 4 network entities, and A method in which a session establishment acceptance message is transmitted based on the receipt of a response to the above N4 rule.

21. In a device, the device comprises: At least one transmitter / receiver; At least one processor; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is: a device adapted to perform the method according to any one of claims 17 to 20.

Images