Method for application operation through PC5

Abstract

A disclosure of the present specification provides a method by which an AAnF performs communication. The method comprises the steps of: transmitting, to an NEF, a request for UE selection assistance information for an application operation; on the basis of the request, receiving the UE selection assistance information from the NEF, the UE selection assistance information including a candidate UE list, a UE included in the candidate UE list being capable of performing the application operation through PC5 communication, and a quality of service (QoS) for Uu communication by the UE included in the candidate UE list failing to satisfy a specific criterion; on the basis of the UE selection assistance information, determining a member UE to perform the application operation through the PC5 communication; and transmitting PC5-related information to the member UE, wherein the PC5-related information includes information instructing the member UE to perform the application operation by performing a PC5 connection to a specific UE.

Description

How to run applications through PC5

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for new radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU radio communication sector) International Mobile Telecommunications (IMT)-2020 process. NR must also be able to utilize any spectrum band up to at least 100 GHz, ensuring that it remains available for wireless communications well into the future.

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

[0005] A method is needed for AF to select / instruct the terminal on which the application operation will be performed by PC5.

[0006] Additionally, when the QoS of Uu communication of a UE performing AI / ML operations through Uu communication is degraded, a method for continuing AI / ML operations is required.

[0007] AF receives information based on an AF request from CN, and AF can perform application operations through PC5 communication for UEs capable of PC5 communication.

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

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

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

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

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

[0013] Figure 6 shows a flowchart for member UE selection and update operations.

[0014] Figure 7 shows an example of a registration procedure to which the implementation of this specification applies.

[0015] Figure 8 illustrates the AF procedure for the disclosure of this specification.

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

[0017] Figure 10 illustrates NEF's procedure for disclosure of this specification.

[0018] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multicarrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented via wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented via wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (evolved UTRA). UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long-term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and / or 5G NR (new radio).

[0019] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

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

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

[0022] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0023] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0024] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

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

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

[0027] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

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

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

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

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

[0032] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

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

[0034] Wireless devices (100a to 100f) refer to devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), extended reality (XR) devices (100c), portable devices (100d), home appliances (100e), IoT devices (100f), and artificial intelligence (AI) devices / servers (400). For example, vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR / VR / mixed reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs) and heads-up displays (HUDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0035] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving functions, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

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

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

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

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

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

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

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

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

[0044] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0045] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, device-to-device (D2D) communication), and base station-to-base station communication (150c) (e.g., relay, integrated access and backhaul (IAB)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of the various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0046] AI is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0047] A robot can be defined as a machine that automatically processes or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making decisions, and performing actions on its own can be called an intelligent robot. Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with a drive unit, including an actuator or motor, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots include wheels, brakes, and propellers in their drive unit, enabling them to drive on the ground or fly in the air.

[0048] Autonomous driving refers to the technology of driving on one's own, while autonomous vehicles refer to vehicles that drive without, or with minimal, user intervention. For example, autonomous driving can include technologies such as lane keeping, automatic speed control like adaptive cruise control, autonomous driving along a set route, and autonomous driving based on a set destination. Vehicles encompass all types of vehicles: those with internal combustion engines, hybrid vehicles with both internal combustion engines and electric motors, and electric vehicles with only electric motors. These vehicles can include not only cars but also trains and motorcycles. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

[0049] Extended reality is a general term for VR, AR, and MR. VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images over images of real objects, and MR technology is a CG technology that mixes and combines virtual objects with the real world. MR technology is similar to AR in that it displays real and virtual objects together. However, there is a difference: while AR uses virtual objects to complement real objects, MR uses virtual and real objects equally.

[0050] NR supports multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

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

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

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

[0055] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (low power wide area network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

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

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

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

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

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

[0061] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

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

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

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

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

[0066] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements instruction codes, commands and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

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

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

[0069] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), and / or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphic processing unit (GPU), and a memory control processor.

[0070] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0071] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0072] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present specification, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0073] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0074] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0075] In the implementation of the present specification, a UE can operate as a transmitter in the uplink (UL) and as a receiver in the downlink (DL). In the implementation of the present specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of the present specification or to control a transceiver (106) to perform UE operations according to the implementation of the present specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of the present specification or to control a transceiver (206) to perform base station operations according to the implementation of the present specification.

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

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

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

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

[0080] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0081] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

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

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

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

[0085] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

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

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

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

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

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

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

[0092] The illustrated AMF (410) can manage access and mobility in a 5G system. The AMF (410) can perform functions to manage Non-Access Stratum (NAS) security. The AMF (410) can perform functions to handle mobility in the idle state.

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

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

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

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

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

[0098] The illustrated SMF (420) can perform the function of allocating an IP (Internet Protocol) address of the UE. In addition, the SMF (420) can control a PDU (protocol data unit) session.

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

[0100] 5G mobile communications support multiple numerologies, or subcarrier spacing (SCS), to support diverse 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands. A 30 kHz / 60 kHz SCS supports dense urban environments, lower latency, and wider carrier bandwidth. An SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

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

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

[0103] - AUSF (Authentication Server Function)

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

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

[0106] - USDF (Unstructured Data Storage Function)

[0107] - NEF (Network Exposure Function)

[0108] - I-NEF (Intermediate NEF)

[0109] - NRF (Network Repository Function)

[0110] - NSSF (Network Slice Selection Function)

[0111] - PCF (Policy Control Function)

[0112] - SMF (Session Management Function)

[0113] - UDM (Unified Data Management)

[0114] - UDR (Unified Data Repository)

[0115] - UPF (User Plane Function)

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

[0117] - AF (Application Function)

[0118] - UE (User Equipment)

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

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

[0121] - NWDAF (Network Data Analytics Function)

[0122] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0150] <AI / ML (Artificial Intelligence and Machine Learning)동작>

[0151] To support candidate UE selection, the AF provides a list of target UEs and one or more Member UE filtering criteria as part of its service operation parameters. Upon receiving an AF request, the NEF triggers the corresponding 5GC procedure to retrieve information about the UEs in the target UE list from the 5GC NF. Before transmitting the candidate UE list to the AF, the NEF integrates all information collected from other 5GC NFs to derive additional information based on one or more candidate UE lists and the Member UE filtering criteria requested by the AF.

[0152] 1. Select member UE

[0153] Figure 6 shows a flowchart for member UE selection and update operations.

[0154] Step 1. The AF subscribes to the member UE selection assistance function by sending an Nnef_MemberUESelectionAssistance_subscribe request containing a list of target UEs (at least one UE filtered by the criteria listed in Table 3) and optionally a time window. The AF can then update the filtering criteria of the subscription by calling Nnef_UEMemberSelectionAssistance_subscribe and providing the Subscription Correlation ID.

[0155] Step 2a. [Optional] NEF verifies whether the AF request is approved, identifies the information to be collected for each UE in the target UE list, and executes the corresponding service action based on the member UE filtering criteria (e.g., events, analytics, and / or notifications) provided by AF.

[0156] Step 2b. [Optional] NEF associates the Nnef_MemberUESelectionAssistance_Subscribe request with an existing subscription based on the Subscription Correlation ID. NEF uses the target UE received in step 1 to update member UEs using the updated filtering criteria.

[0157] Step 3. The NEF interacts with various 5GC network functions to collect the necessary information for each UE in the target UE list. The set of interactions between NEFs and 5GC NFs varies depending on the member UE filtering criteria provided by the AF.

[0158] Step 4. The NEF integrates all information collected from other 5GC NFs to derive a list of candidate UEs that meet the member UE filtering criteria in the AF request, based on the information collected from other 5GC NFs. The NEF can derive recommended time zones by considering the validity period of the analysis used in the member UE selection criteria, which is a subset of the time zones received from the AF.

[0159] Step 5. NEF sends a Nnef_MemberUESelectionAssistance_Notify request to AF containing a list of candidate UEs and additional information.

[0160] 2. Member UE filtering criteria

[0161] Table 3 summarizes the member UE filtering criteria that AF may request.

[0162] Member UE filtering criteriaDescription of filtering criterionUE filtering informationDetailed description clauseQoSThe Quality of Service of the selected UEs match or exceed the QoS of the filtering criteriaService operation: Nsmf_EventExposure or Nudm_EvenExposure,Filter: target=SUPI, Event=QoS Monitoring, traffic descriptor (e.g. Application ID)4.15.13.3 in TS 23.502 v18.2.0Access Type and / or RAT Type of the PDU SessionIndicate the Access Type and / or RAT Type of the selected UE for the PDU Session used by the application (e.g. 3GPP / NR, Non-3GPP / WLAN, additional Access Type and RAT Type for MA PDU session)Service operation: Nsmf_EventExposureFilter: a list of GPSI(s) or SUPI(s), DNN / S-NSSAIEvent ID: Change of Access Type and / or Change of RAT TypeThis can be provided by existing service operations, events and procedures.End-to-end data volume transfer timeIndicate the end-to-end data volume transfer time that refers to a time for completing the transmission of a specific data volume between UE to AF, e.g. the average and variance of End-to-end data volume transfer timeService operation: Nnwdaf_AnalyticsSubscription / Nnwdaf_AnalyticsInfoFilter: Analytics ID = End-to-end data volume transfer time, target = GPSI(s) or SUPI(s)4.15.13.6 in TS 23.502 v18.2.0UE current locationIndicate the certain area that the selected UE currently located in.Service operation: Namf_EventExposureFilter: a list of GPSI(s) or SUPI(s)4.15.13.4 in TS 23.502 v18.2.0UE historical locationIndicate the certain area that the selected UE appeared in a historical period of timeService operation:Nnwdaf_AnalyticsSubscriptionFilter: Analytics ID = UE mobility,Filters include "Visited AoI = Target AOI" and "target period = historical nomadic period4.15.13.4 in TS 23.502 v18.2.0UE directionIndicate the selected UEs should include different moving directionService operation:Nnwdaf_AnalyticsSubscriptionFilter: Analytics ID= UE Mobility, Direction4.15.13.4 in TS 23.502 v18.2.0UE separation distance(NOTE 1)Indicate the selected UEs should comply with a minimum separation distance between each otherService operation:Nnwdaf_AnalyticsSubscription / Nnwdaf_AnalyticsInfoFilter: Analytics ID = Relative ProximityFilters include "Proximity Attributes"4.15.13.4 in TS 23.502 v18.2.0Service ExperienceIndicates selected UEs fulfilling ceratin Service Experience criteria e.g., MOS valueService operation: Nnwdaf_AnalyticsInfo_Request / Subscribe Analytics ID=Service ExperienceFilter: S-NSSAI, DNN, Application ID, DNAI, AoI, Service Experience Contribution weight reporting threshold (NOTE 2), Service Experience Type (NOTE 3)4.15.13.5 in TS 23.502 v18.2.0DNNIndicate the DNN of the selected UE for the PDU Session used by the applicationService operation: Nsmf_EventExposureFilter: a list of GPSI(s) or SUPI(s)Event ID: QFI allocation5.2.8.3 in TS 23.502 v18.2.0NOTE 1: This criterion should only be applied when the number of UEs is in the range of 10's or less.NOTE 2: The Service Experience Contribution Weights signal the relative importance of each UE's Service Experience value (i.e. MOS), as defined in TS 23.288 v18.2.0. For example, it might be that the service experience of a UE in relation to other UEs may not be as important e.g. because the data provided by such UE is not as critical to the service.NOTE 3: Indicates the type of service experience analytics, e.g. AIML traffic where a customized MoS apply.

[0163] If a terminal's direct network connection fails to meet the QoS requirements while participating in a federated learning (FL) operation (AI / ML operation), the terminal can establish a direct device connection (DDC) with another UE to continue the FL operation (AI / ML operation). A specific solution is needed in this regard.

[0164] In this specification, application operation, AI / ML operation, and FL operation are described interchangeably. That is, an application operation can be an AI operation, an ML operation, or an FL operation.

[0165] The AI / ML operation support method considering PC5 communication proposed in this specification can be composed of a combination of one or more operations / configurations / steps described below.

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

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

[0168] In this specification, Application Function (AF) and Application Server (AS) are used interchangeably.

[0169] In this specification, AI / ML (related / based) operation is described interchangeably with AI / ML (related / based) service, AI / ML (related / based) application, application AI / ML, application layer AI / ML, AI / ML (related / based) operation in the application layer, AI / ML (related / based) task, etc.

[0170] In this specification, services and applications may be interpreted as the same unless otherwise stated.

[0171] AI / ML operations may include the following operations, and the AI / ML operation support method considering PC5 communication proposed in this specification may be applied to the following operations:

[0172] - AI / ML operation splitting between AI / ML endpoints;

[0173] - AI / ML model / data distribution and sharing over 5G system;

[0174] - Distributed / Federated Learning over 5G system.

[0175] In this specification, direct device connection is described interchangeably with PC5 / Sidelink / ProSe, PC5 / Sidelink / ProSe operation, PC5 / Sidelink / ProSe service, Device-to-Device connection, UE-to-UE connection, ProSe / PC5 / Sidelink connection, PC5 / Sidelink / ProSe communication, direct device communication, etc.

[0176] PC5 / Sidelink / ProSe operations may be understood to include some or all of the operations / procedures related to 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay, and 5G ProSe UE-to-UE Relay.

[0177] In this specification, AI / ML operations using direct device connection are described interchangeably with decentralized AI / ML operations, decentralized averaging methods, etc.

[0178] Decentralized AI / ML operations may be AI / ML operations performed via direct device connections (PC5).

[0179] In this specification, direct device connection may mean / include / use one or more of the following cast modes / types:

[0180] - Unicast (or PC5 unicast link or Layer-2 link)

[0181] - Group Cast

[0182] - Broadcast

[0183] In this specification, PC5 is described interchangeably with sidelink and ProSe.

[0184] In this specification, direct network connection is described interchangeably with Uu connection, Uu communication, connection via network, communication via network, direct network communication, etc.

[0185] In this specification, AI / ML operations using direct network connections are described interchangeably with centralized AI / ML operations, centralized averaging methods, etc.

[0186] In this specification, a UE with PC5 capability may be interpreted as a 5G ProSe-enabled UE.

[0187] This specification primarily describes the proposed content. For operations and procedures related to 5G systems, AF interactions, and the core network, TS 23.501 v18.2.2, TS 23.502 v18.2.0, and TS 23.503 v18.2.0 are primarily referenced. For operations and procedures related to ProSe / PC5 / Sidelink, TS 23.304 v18.2.0 is primarily referenced.

[0188] I. First Example

[0189] Figure 7 shows an example of a registration procedure to which the implementation of this specification applies.

[0190] In relation to FIG. 7, the content proposed in this specification is mainly described based on section 5.46 (Assistance to AI / ML Operations in the Application Layer) of TS 23.501 v18.2.2 and section 4.15.13 (Assistance for Member UE selection) of TS 23.502 v18.2.0.

[0191] Step 1. AF can perform Nnef_MemberUESelectionAssistance_Subscribe (i.e., subscribe to the member UE selection assistance information / notification service) with NEF. AF can send member UE selection assistance subscription (Nnef_MemberUESelectionAssistance_Subscribe) to NEF. AF can send a subscription request for member UE selection assistance to NEF. AF can request information about member UE selection assistance from NEF via Nnef_MemberUESelectionAssistance_Subscribe. Information about member UE selection assistance can be information for application operation (AI / ML operation).

[0192] A Member UE Selection Assistance Subscription (Nnef_MemberUESelectionAssistance_Subscribe) may contain one or more of the following additional information:

[0193] When AF initially subscribes to the Member UE Selection Assistance information / notification service with NEF, AF may include one or more of the following additional information in the Member UE Selection Assistance Subscription (Nnef_MemberUESelectionAssistance_Subscribe):

[0194] Additionally, even when updating what AF has already subscribed to, AF may include one or more of the following additional information in the Member UE Selection Assistance Subscription (Nnef_MemberUESelectionAssistance_Subscribe):

[0195] The information below may be expressed in explicit, implicit, combined, implicit, or step-by-step form.

[0196] 1) Information requesting provision of ProSe Service Authorization information (or ProSe subscriber information) for UE(s) included in a list of target UE(s) or a list(s) of candidate UE(s).

[0197] The ProSe service authorization information may refer to subscriber information (ProSe Subscription data). Alternatively, the ProSe service authorization information may refer to information about ProSe Direct Communication (i.e., information about whether the UE is authorized to use ProSe Direct Communication) among the subscriber information. Alternatively, the ProSe service authorization information may refer to information about ProSe UE-to-Network Relay (i.e., whether the UE is authorized to use or serve as a ProSe UE-to-Network Relay) among the subscriber information. Alternatively, the ProSe service authorization information may be subscriber information about a direct device connection related to a newly defined AI / ML operation (application operation) (or subscriber information about an Application Layer UE-to-Network Relay).

[0198] For the above subscriber information, please refer to Table 5.2.3.3.1-1: UE Subscription data types in TS 23.502 v18.2.0.

[0199] The above ProSe service authorization information may be provided to the AF only when authorized, or may be provided to the AF not only when authorized but also when not authorized.

[0200] 2) Information requesting to provide “5G ProSe authorized” information for UE(s) included in a list of target UE(s) or a list of candidate UE(s).

[0201] The above "5G ProSe authorized" information may refer to "5G ProSe authorized" information provided by the AMF to the NG-RAN. The information may refer to information about ProSe Direct Communication (i.e., whether the UE is authorized to use 5G ProSe Direct Communication), or the information may refer to information about ProSe UE-to-Network Relay (i.e., one or more of whether the UE is authorized to act as a 5G ProSe Layer-2 UE-to-Network Relay, whether the UE is authorized to act as a 5G ProSe Layer-3 UE-to-Network Relay, and whether the UE is authorized to act as a 5G ProSe Layer-2 Remote UE). Alternatively, the above "5G ProSe authorized" information may be authorized information about a newly defined AI / ML operation-related direct device connection (or authorized information about an Application Layer UE-to-Network Relay).

[0202] For the above "5G ProSe authorized" information, please refer to Section 6.6 (Procedures for Service Authorization to NG-RAN) of TS 23.304 v18.2.0.

[0203] The above “5G ProSe authorized” information may be provided to AF only when authorized, or may be provided to AF not only when authorized but also when not authorized.

[0204] 3) Information requesting that the application layer ID be provided for the UE(s) included in the list of target UE(s) or the list(s) of candidate UE(s).

[0205] The above application layer ID may be identification information used for PC5 operation.

[0206] Application Layer ID: An identifier identifying a 5G ProSe-enabled UE within the context of a specific application.

[0207] The above application layer ID may be stored in 5GC NF such as UDM, UDR, PCF, NEF, and 5G DDNMF (5G Direct Discovery Name Management Function).

[0208] The above application layer ID may be UE-specific information, subscriber-specific information, ProSe service-specific information (i.e., ProSe identifier), application-specific information (i.e., Application ID), or AF identifier-specific information. In other words, the application layer ID may be set / stored / provided in various granularities.

[0209] 4) Information indicating that ProSe Service Authorization information exists (or ProSe Service Authorization information has been approved) as part of the Member UE filtering criteria.

[0210] For the above ProSe service approval information, please refer to the information described in 1) above.

[0211] 5) Information indicating that “5G ProSe authorized” information exists (or “5G ProSe authorized” information is approved) as part of the member UE filtering criteria.

[0212] For the above “5G ProSe authorized” information, please refer to the information described in 2) above.

[0213] 6) Information requesting that when there is a change in the previously provided / notified candidate UE list (or UE(s) included therein) (e.g., due to a change in whether the member UE filtering criteria are satisfied, or due to a change in ProSe service authorization information), instead of providing an updated candidate UE list (updated list(s) of candidate UE(s)), the UE be notified of which UEs have changed in which filtering criteria they have satisfied in the already provided / notified candidate UE list (list(s) of candidate UE(s)).

[0214] The request may be specific to a specific filtering criterion. This may be one or more specific filtering criteria. For example, the filtering criterion may be "QoS." The filtering criterion may be "End-to-end data volume transfer time." The filtering criterion may be "Service Experience."

[0215] The above specific filtering criteria may also be interpreted as being related to direct network connection / Uu related QoS or direct network / Uu related transmission conditions.

[0216] If a request is made only for specific filtering criteria, and satisfaction of other filtering criteria changes, NEF may determine / produce an updated list(s) of candidate UE(s) based on this and provide / notify the AF of the updated list(s) of candidate UE(s).

[0217] 7) Information requesting provision (notification) of whether the filtering criteria are satisfied (information) and / or whether the filtering criteria have changed (information) when providing (notifying) the list(s) of candidate UE(s).

[0218] The above candidate UE list(s) of candidate UE(s) may correspond only to the updated candidate UE list(s) of candidate UE(s). Alternatively, the above candidate UE list(s) of candidate UE(s) may correspond to both the updated candidate UE list(s) of candidate UE(s) and the initial candidate UE list(s) of candidate UE(s).

[0219] 8) Information requesting provision (notification) of UE(s) that were included in the previously provided (notified) list(s) of candidate UE(s) but excluded (omitted) from the updated list(s) of candidate UE(s) and the reason(s) for their exclusion (omission) when providing (notifying) an updated list(s) of candidate UE(s). It may also be requested to be notified whether any filtering criteria have been satisfied for the UE(s).

[0220] 9) Information requesting location information for UE(s) included in a list of target UE(s) or a list of candidate UE(s).

[0221] The above location information can be provided to AF in various forms (e.g., coordinate information, address information, cell information, tracking area information, etc.).

[0222] 10) Information requesting that, if a UE included in the list(s) of candidate UE(s) that has already been provided / notified does not satisfy the Uu QoS, it not be excluded (or kept) from the list(s) of candidate UE(s) if PC5 operation is possible (allowed).

[0223] 11) Information requesting inclusion in the candidate UE list (list(s) of candidate UE(s)) if PC5 operation is possible / allowed when Uu QoS is not satisfied.

[0224] That is, a UE that is unable to perform Uu communication (does not satisfy QoS) but capable of PC5 communication can be included in the candidate UE list (candidate UE list to be transmitted to AF).

[0225] In this specification, the list(s) of candidate UE(s) is described interchangeably with the list(s) of recommended UE(s).

[0226] In this specification, member UE filtering criteria are described interchangeably with filtering criteria.

[0227] The above 1) to 3) may be interpreted as a request to provide information related to PC5 availability / acceptance.

[0228] AF can transmit a list of target UEs to NEF, thereby allowing NEF to collect information about the terminals included in the list.

[0229] The above 4) to 5) may be interpreted as requesting the NEF to select only UEs capable / allowed of PC5 operation when selecting candidate UEs (or to include only UEs capable / allowed of PC5 operation in the candidate UE list).

[0230] Step 2. Actions corresponding to step 2a and step 2b of section 4.15.13.1 of TS 23.502 v18.2.0 can be performed.

[0231] Step 3. The action corresponding to step 3 of section 4.15.13.1 of TS 23.502 v18.2.0 can be performed.

[0232] Based on the information provided by AF, NEF may perform additional actions beyond those corresponding to step 3 of section 4.15.13.1 of TS 23.502 v18.2.0.

[0233] For example, to obtain 1) and 3) of step 1 above, NEF can interact with UDM.

[0234] For example, to obtain step 1) 2 above, NEF can interact with AMF.

[0235] For example, to obtain step 3) of the above step 1, NEF can interact with UDR.

[0236] With regard to steps 1), 2), and 3) of the above step 1, the NF that exposes the information may provide (notify) the information to other NFs (e.g., NEF, AF, etc.) using a newly defined event. This can be applied throughout this specification.

[0237] For example, a NEF can receive information about multiple UEs from another NF.

[0238] For example, the NEF may receive information about terminals included in the target UE list received in step 1 from another NF.

[0239] NEF can receive PC5 QoS-related information (or events) from NG-RAN, OAM, 5GC, etc. Using the received PC5 QoS-related information (or events), NEF can provide (or notify) member UE selection assistance information to AF.

[0240] Step 4. The action corresponding to step 4 of section 4.15.13.1 of TS 23.502 v18.2.0 can be performed.

[0241] To utilize information collected from other 5GC NF(s) and its own information, the NEF can consolidate the information collected from other 5GC NF(s) and its own information. Based on the consolidated information, the NEF can determine (or derive) a list of candidate UEs.

[0242] The target UE list received by the NEF in Step 1 may include the determined candidate UE list. That is, the NEF may determine a candidate UE list that includes at least one terminal included in the target UE list received in Step 1. The determined candidate UE list may be a subset of the target UE list received by the NEF in Step 1.

[0243] The terminals included in the candidate UE list may include terminals that have already performed Uu communication but do not satisfy Uu QoS.

[0244] The terminals included in the candidate UE list may include terminals that do not perform Uu communication and do not satisfy Uu QoS.

[0245] Step 5. The NEF may provide (or notify) the AF with a list of candidate UEs. At this time, based on the AF's request, the NEF may also provide (or notify) the AF with various information.

[0246] The NEF may transmit member UE selection assistance information to the AF. The member UE selection assistance information may include the candidate UE list and various other information. The various other information may include PC5 QoS-related information (or events) collected from NG-RAN, OAM, 5GC, etc. in step 3.

[0247] The AF can select (decide) which UE(s) (e.g., UE#1 and UE#2) to participate in (or use) the AI / ML operation (application operation) based on the member UE selection assistance information provided by the NEF.

[0248] AF can enable selected UE(s) (e.g., UE#1 and UE#2) to perform AI / ML operations (e.g., FL task).

[0249] When AF selects (decides) UE(s) to participate (use) in AI / ML operations (application operations), AF can construct a list of target UE(s) including the selected UE(s).

[0250] AF can subscribe to the new Member UE Selection Assistance Information / Notification Service through NEF. AF can include a newly configured target UE list in the subscription message. The newly configured target UE list can include UEs selected to participate in AI / ML operations.

[0251] Alternatively, AF can update the subscription made in step 1 with NEF.

[0252] The aforementioned AF subscription update (or new subscription) may be to provide changed information (e.g., change in QoS situation for Uu communication, etc.) to the UEs selected by the AF to participate in AI / ML operations.

[0253] The aforementioned AF subscription update (or new subscription) can be performed in step 1. Alternatively, the aforementioned AF subscription update (or new subscription) can be performed after step 5. Alternatively, the aforementioned AF subscription update (or new subscription) can be performed after step 8.

[0254] Based on the aforementioned AF subscription update (or new subscription), one of the following actions may be performed:

[0255] - If the information provided to the AF in step 5 or step 8 includes information that a UE that was performing an AI / ML operation cannot satisfy the QoS for Uu communication, the AF can switch from the AI / ML operation based on Uu communication that is being performed to the AI / ML operation based on PC5 communication.

[0256] - If the information provided to the AF in step 5 or step 8 includes information that a UE that was performing AI / ML operations cannot satisfy QoS for Uu communication and that the UE cannot perform AI / ML operations based on PC5 communication, the AF may perform actions such as excluding the UE from member UEs so that the UE no longer performs AI / ML operations.

[0257] The above action can be performed after step 1, step 5, or step 8.

[0258] Step 6. NEF may be notified by other 5GC NF(s) with which NEF subscribed to or interacted with the service in step 3 that any information has changed or that an event has occurred.

[0259] For example, as described in section 4.15.13.3.3 (Member UE Assistance with QoS filtering criteria for real-time QoS Monitoring) of TS 23.502 v18.2.0 in step 3, the NEF can subscribe to the SMF for QoS monitoring ('QoS monitoring') events. Based on this, the NEF can be notified of QoS monitoring-related information from the UPF.

[0260] Step 7. The NEF can determine which UE's status will change based on the information received in step 6. Alternatively, the NEF can determine an updated list of candidate UEs.

[0261] For example, a UE may once have satisfied a filtering criterion but may no longer. For example, a UE may have been a candidate UE but may no longer be. For example, a UE may have been included in the candidate UE list but may no longer be.

[0262] For example, a UE may initially fail to satisfy the filtering criteria, but then eventually does. For example, a UE may not be a candidate UE, but then become one. For example, a UE may not have been included in the candidate UE list, but then become one.

[0263] In this way, when the status of a UE changes, the NEF can determine an updated candidate UE list.

[0264] The NEF may determine that it needs to provide the AF with an updated candidate UE list. Based on this, the NEF may determine an updated candidate UE list.

[0265] Step 8. NEF may provide updated (changed) Member UE selection assistance information to AF based on AF's request.

[0266] The above updated member UE selection assistance information may include an updated candidate UE list determined by the NEF in step 7.

[0267] The NEF may provide (notify) the AF with information about which filtering criteria have changed for which UEs in the previously provided (notified) candidate UE list (e.g., the candidate UE list provided in step 5). This action may be based on the AF's inclusion of 6) in the member UE selection assistance subscription (Nnef_MemberUESelectionAssistance_Subscribe) in step 1.

[0268] The NEF may provide (notify) the AF with UE(s) that have been excluded (omitted) from the previously provided (notified) candidate UE list (e.g., the candidate UE list provided in step 5) and the reason(s) for their exclusion (omission). At this time, the NEF may also inform the AF of any changes in the filtering criteria satisfied by the excluded UE(s). This action may be based on the AF's inclusion of 8) in the member UE selection assistance subscription (Nnef_MemberUESelectionAssistance_Subscribe) in step 1.

[0269] AF may determine (perceive) one or more of the following based on information provided by NEF:

[0270] a) Some UE(s) cannot satisfy the direct network connection / Uu related QoS or transmission conditions to perform AI / ML operations (application operations).

[0271] b) It is not desirable or possible for any UE(s) to use direct network connection / Uu to perform AI / ML operations (application operations).

[0272] c) Some UE(s) must switch (or be able to use) direct device connection / PC5 to perform AI / ML operations (application operations): This may be interpreted as recognizing (determining) that some UE(s) can continue to participate (use) AI / ML operations.

[0273] d) Decentralized AI / ML operations (application operations) are required or must be performed.

[0274] e) A UE that must switch to direct device connection / PC5 to perform AI / ML operations (application operations) (e.g., a UE corresponding to a) to b) above) and candidate UE(s) that can (or are capable of) performing direct device connection / PC5 communication with this UE.

[0275] The above candidate UE(s) may be a UE that needs to switch (transition) to direct device connection / PC5 and a UE(s) that is determined to be at a location (distance) where PC5 operation is possible. That is, the AF may determine the candidate UE(s) based on the location information of the UEs.

[0276] The AF can also determine the location information of UEs based on the LCS method / mechanism (see TS 23.273 v18.2.0). The AF can also obtain the location information of UEs from the UEs through application layer messages. This can be applied throughout this specification.

[0277] If there are multiple UEs that need to switch to direct device connection / PC5 for AI / ML operations, the candidate UE(s) may be candidate UE(s) that can (or are capable of) performing direct device connection / PC5 communication for each UE.

[0278] f) UE(s) that will perform (or participate in) decentralized AI / ML operations (application operations).

[0279] The UE(s) that perform the above distributed AI / ML operations may include at least UE(s) corresponding to a) to c) above.

[0280] The UE(s) to perform the above distributed AI / ML operations may include candidate UE(s) that do not correspond to a) to c) above, but are capable (or possible) of performing direct device connection / PC5 communication with the UE(s) corresponding to a) to c) above.

[0281] In the case where there is one UE corresponding to the above a) to c), the UE(s) that will perform the distributed AI / ML operation may include candidate UE(s) that do not correspond to the above a) to c) but are capable (or possible) of performing direct device connection / PC5 communication with the UE corresponding to the above a) to c).

[0282] If there are multiple UEs corresponding to the above a) to c) and direct device connection / PC5 communication can be performed between the multiple UEs, the UE(s) to perform the distributed AI / ML operation may not include the candidate UE(s) (candidate UE(s) that do not correspond to the above a) to c) but can (or are capable of) performing direct device connection / PC5 communication with the UE corresponding to the above a) to c).

[0283] AF can determine whether direct device connection / PC5 communication can be performed between UEs based on the location information of the UEs.

[0284] g) UE that acts as a server when decentralized AI / ML operations (application operations) are performed.

[0285] A UE performing the above server role may perform one or more of the following actions:

[0286] - Training results are received from other UEs through PC5 and aggregated.

[0287] - Transmit the update of the training model for the next round to other UEs via PC5.

[0288] - Send training results to AF / AS

[0289] The UE that performs the above server role can perform a leader role, an aggregator role, a network connection / relay role, a leading UE role, etc.

[0290] h) Cast mode / type to use for decentralized AI / ML operations (application operations): unicast or groupcast

[0291] i) Some UE(s) are unable to switch to Direct Device Connect / PC5 (or Direct Device Connect / PC5 is not available) to perform AI / ML operations (application operations): This may be interpreted as the UE(s) recognizing / determining that they cannot continue to participate in / use AI / ML operations.

[0292] j) Member UE(s) to participate (use) in the AI / ML operation / task: These UE(s) may be UEs included in the initial list of member UEs. These UE(s) may also be UEs included in the updated list of member UEs. For example, if the AI / ML operation / task is FL, these UE(s) may be UEs that will participate in FL in the next round.

[0293] When AF recognizes (determines) the above e), the UE corresponding to the above e) may be UE#1 and UE#2. That is, UE#1 may be a UE that must switch (transition) to direct device connection / PC5 to perform AI / ML operations, and UE#2 may be a candidate UE that can (or is capable of) performing direct device connection / PC5 communication with this UE (UE#1).

[0294] If AF recognizes (determines) the above f), the UE corresponding to the above f) may be UE#1 and UE#2. That is, UE#1 and UE#2 may be UEs that perform (or participate in) decentralized AI / ML operations.

[0295] Any UE and any candidate UE(s) capable of (or possibly capable of) performing direct device connection / PC5 communication with this UE may all be UEs participating in (using) (the same) AI / ML operation. Alternatively, any UE and any candidate UE(s) capable of (or possibly capable of) performing direct device connection / PC5 communication with this UE may be UEs that are not participating in (using) AI / ML operation.

[0296] All UEs that perform (or participate in) the above-described decentralized AI / ML operation may be UEs that are participating (using) the (same) AI / ML operation. Alternatively, the UEs that perform (or participate in) the above-described decentralized AI / ML operation may be UEs that are not participating (using) the AI / ML operation.

[0297] AF can determine which UE(s) will perform AI / ML operations based on information provided by NEF.

[0298] AF may perform a procedure to provide specific information (event) to a specific UE (UE(s) included in the target UE list, UE(s) included in the candidate UE list, or UE(s) determined to be used for AI / ML operation) before performing the procedure of FIG. 7, or in parallel with the procedure of FIG. 7, or after receiving the message of step 5.

[0299] The above specific information (event) may be Uu QoS-related information (event) (such as Uu QoS performance-related information (event, Uu QoS satisfaction-related information (event), Uu resource allocation-related information (event), Uu QoS monitoring information (event), congestion-related information (event), etc.) of 5GC (5G core), PC5 QoS-related information (event) (e.g., PC5 QoS performance-related information (event), PC5 QoS satisfaction-related information (event), PC5 resource allocation-related information (event), PC5 QoS monitoring information (event), PC5 congestion-related information (event), etc.), location-related information (event), etc.

[0300] For this purpose, various conventional procedures and / or newly defined procedures can be used.

[0301] For example, various conventional procedures may be procedures for requesting analytics information from NWDAF (see TS 23.288 v18.2.0), various information (event) provision (exposure) procedures defined in Section 4.15.6 (External Parameter Provisioning) of TS 23.502 v18.2.0 (e.g., Section 4.15.6.13 (Multi-member AF session with required QoS), Section 4.15.6.6 (Setting up an AF session with required QoS procedure), Section 4.15.6.6a (AF session with required QoS update procedure), etc.).

[0302] AF may also recognize (decide) a) to j) above for a certain UE based on these actions / procedures.

[0303] The AF may also obtain various information (e.g., PC5 capability of the UE, location information of the UE, Uu QoS-related information, PC5 QoS-related information, etc.) from the UE to recognize (determine) the above a) to j).

[0304] The AF may first receive a list(s) of candidate UE(s) from the NEF to recognize / determine a) to j) above. In this case, it can be understood that UE(s) that have difficulty performing AI / ML operations / tasks via Uu perform AI / ML operations / tasks via PC5 from the beginning.

[0305] Step 9. AF may provide PC5-related information to UE#1 (the UE that AF has determined to perform AI / ML operations). The PC5-related information may include one or more of the following information. The information below may be expressed explicitly, implicitly, in combination, implicitly, or in a step-by-step manner. The PC5-related information may also be considered a ProSe policy (or parameter).

[0306] I) Information that instructs (requests) to use direct device connection / PC5 for AI / ML operations, or to switch to direct device connection / PC5, or to perform decentralized AI / ML operations.

[0307] II) AI / ML action / task identification information.

[0308] The above information may be information (ID) for identifying the AI / ML operation / task in which the UE is participating / using. For example, if the UE is participating in a FL task, the AI / ML operation / task identification information may be information for identifying the FL task. The AI / ML operation / task identification information may be assigned or designated by the AF.

[0309] III) Information about candidate UE(s) that will perform direct device connection / PC5 connection for AI / ML operations (this may be particularly relevant if e) in step 8 above has been recognized / determined) (e.g., UE#2)

[0310] Information about the above candidate UE(s) may include one or more of the following information. This information may be obtained by requesting it from the NEF (via step 1). Alternatively, this information may be obtained from the UE.

[0311] - Application Layer ID of each candidate UE

[0312] - Layer-2 ID of each candidate UE

[0313] IV) Information about other UE(s) that will perform decentralized AI / ML operations (this may be particularly the case when f) is recognized (determined) in step 8 above);

[0314] Information about the other UE(s) may include one or more of the following information. This information may be obtained by requesting it from the NEF (via step 1). Alternatively, this information may be obtained from the UE (e.g., UE #2).

[0315] - Application Layer ID of each UE

[0316] - Layer-2 ID of each UE

[0317] V) When decentralized AI / ML operations are performed, information about the UE that will act as a server (e.g., the application layer ID information of the UE)

[0318] UE#2 may be the UE that will perform the server role.

[0319] VI) Cast mode / type information used for decentralized AI / ML operations. If not provided, the default mode / type may be unicast.

[0320] If the cast mode / type information used for the above decentralized AI / ML operation is groupcast, an Application Layer Group ID and / or ProSe Layer-2 Group ID may be additionally provided to the terminal (UE#1).

[0321] VII) PC5 QoS parameters to apply when using direct device connection / PC5 for AI / ML operations.

[0322] VIII) Information indicating that direct device connection / PC5 is ready for use for AI / ML operations or that switching to direct device connection / PC5 is performed (completed).

[0323] The Application Layer ID may also contain AI / ML operation / task identification information.

[0324] The Application Layer Group ID may also contain AI / ML action / task identification information.

[0325] The application layer ID and / or application layer group ID may also be assigned (specified) by AF.

[0326] When decentralized AI / ML operations are performed, the UE to act as a server may be determined (selected) through negotiation among UEs. This negotiation may be conducted via application layer messages. This negotiation may be conducted via PC5-S messages.

[0327] AF may provide one or more of the information I) to VI) to UE#1 as well as UE#2.

[0328] If AF recognizes (decides) e) in step 8, AF may not provide the information of III) to UE#2.

[0329] If AF recognizes (determines) f) in step 8 above, AF can provide information about UE#1 to UE#2 as information of IV).

[0330] The AF may provide some or all of the above PC5 related information to the UE using application layer messages (signaling).

[0331] Additionally, the AF may provide some or all of the PC5-related information to the 5GC using an AF-based service parameter provisioning method (procedure). Then, the PCF of the 5GC may transmit the PC5-related information to the UE(s) to which it should be provided.

[0332] The AF-based service parameter provisioning method (procedure) can be referred to Section 4.2.4 (AF-based service parameter provisioning) and Section 6.2.5 (AF-based service parameter provisioning for ProSe over control plane) of TS 23.304 v18.2.0.

[0333] If AF recognizes (decides) that i) a switching (transition) from Uu to PC5 is required for a UE participating (using) an AI / ML operation, or ii) a decentralized AI / ML operation needs to be performed, or iii) a switching (transition) to PC5 is performed (completed), it may keep the member UEs participating (using) the AI / ML operation (i.e., the list of member UE(s)) as is without making any changes.

[0334] AF can store information about UEs participating in decentralized AI / ML operations.

[0335] When AF determines which UE(s) will participate in (use) AI / ML operations, AF may provide one or more of the information of II) to VIII) to the UE(s).

[0336] When AF determines which UE(s) will participate in (use) AI / ML operations, AF can provide the information of I) above to the corresponding UE(s) at the time when direct device connection / switching to PC5 is required.

[0337] When the AF determines which UE(s) will participate in (use) the AI / ML operation, the AF may provide one or more of the information of II) to VIII) above to the UE(s), and may also explicitly (or implicitly) instruct (request) the UE(s) to perform direct device connection / switching to PC5 when the AF determines that the UE(s) have difficulty using Uu or cannot satisfy QoS. The instruct (request) above may be configured in the UE.

[0338] Alternatively, the UE may implementally decide to perform the above switching.

[0339] If there is a UE that has been excluded while participating (using) in an AI / ML operation (task), the AF (or 5GC) may perform an operation (procedure) to revoke the PC5-related information provided to the UE.

[0340] Step 10. When unicast is used for decentralized AI / ML operations, the UE that has received the PC5-related information can initiate a procedure to establish a PC5 unicast link with another UE. That is, the UE can send a direct communication request to the other UE.

[0341] If the above PC5 related information is provided to multiple UEs, a UE that does not perform a server role may initiate a procedure for forming a PC5 unicast link to a UE that performs a server role.

[0342] Alternatively, if the PC5 related information is provided to multiple UEs, a UE acting as a server may initiate a procedure for forming a PC5 unicast link to a UE not acting as a server.

[0343] UE#1 can transmit a DCR (Direct Communication Request) message to form a PC5 unicast link with UE#2 based on the above PC5-related information.

[0344] The PC5 unicast link establishment procedure can be referred to Section 6.4.3.1 (Layer-2 link establishment over PC5 reference point) of TS 23.304 v18.2.0. The DCR message may include one or more of the following information elements (or parameters, fields):

[0345] - Source User Info: Application Layer ID of UE#1

[0346] - Target User Info: Application Layer ID of UE#2. This may be included if UE#1 has received or is aware of it. Or, even if it has received or is aware of it, it may not be included.

[0347] - ProSe Service Info: Can include (set) AI / ML operation / task identification information. The AI / ML operation / task identification information can be information (ID) that identifies the AI / ML operation (task) that UE#1 is participating in (using). If the AI / ML operation / task identification information has been provided to or is known to UE#1, the ProSe Service Info can include the AI / ML operation / task identification information. Or, even if it has been provided or is known, it may not include it.

[0348] You can also define new information elements (or parameters, fields) in the DCR message to include (set) AI / ML action / task identification information.

[0349] If the Layer-2 ID of UE#2 is provided to UE#1, the Layer-2 ID of UE#2 can be set as the Destination Layer-2 ID for transmitting the DCR message.

[0350] UE#1 can receive information about multiple UEs as candidate UE(s) to perform direct device connection / PC5 connection.

[0351] In this case, UE#1 may transmit a PC5 unicast link formation request message to one of the multiple UEs. Alternatively, in this case, UE#1 may transmit a PC5 unicast link formation request message to multiple UEs (some or all of the candidate UEs).

[0352] When UE#1 transmits a PC5 unicast link formation request message to multiple UEs (some or all of the candidate UEs), UE#1 may receive response messages (e.g., a Direct Security Mode Command message, a Direct Communication Accept message, etc.) from the multiple UEs. In this case, UE#1 may decide to form a PC5 unicast link with one or more UEs among the UEs that transmitted the response messages. The decision may be performed based on PC5 sync signal (quality) information, etc., with the UE that transmitted the response message. This may be applied throughout the present specification.

[0353] Additionally, UE#1 may transmit a DCR message by setting (including) only AI / ML operation / task identification information without setting (including) target user information. In this case, UE#1 may receive response messages (e.g., Direct Security Mode Command messages, Direct Communication Accept messages, etc.) from multiple UEs participating in the AI / ML operation / task. Then, it may decide to form a PC5 unicast link with one or more of the UEs.

[0354] Step 11. UE#2 can respond to UE#1's PC5 unicast formation request. Based on this, a PC5 unicast link can be formed between UE#1 and UE#2.

[0355] UE#1 can notify AF that it is ready for direct device connection / PC5 (or that switching to direct device connection / PC5 has been performed / completed).

[0356] UE#1 can perform AI / ML operations via direct device connection / PC5.

[0357] For example, UE#1 can transmit the training result to UE#2 via the established PC5 unicast link. Then, UE#2 can locally aggregate the training result and transmit the update of the training model for the next round to UE#1 via the PC5 unicast link. If UE#2 has no problem using Uu, UE#2 can perform AI / ML operation-related interactions with the Application Server (such as transmitting the training result to the Application Server).

[0358] When the UE determines that switching to Direct Device Connection (PC5) is necessary based on the QoS (or transmission conditions) of Uu, etc., the UE may transmit a PC5 unicast link formation request message to some or all of the other UEs participating in the AI / ML operation (this may be because it does not know which UEs are capable of PC5 communication). Thereafter, when the UE receives response messages (e.g., Direct Security Mode Command messages, Direct Communication Accept messages, etc.) from multiple UEs, the UE may decide to form a PC5 unicast link with one or more UEs among the multiple UEs.

[0359] If there is another UE that is considered capable of PC5 communication (e.g., the UE is aware of this in an implementation-specific way), the UE may send a PC5 unicast formation request message to that UE.

[0360] The UE may also perform an action (procedure) to discover other UEs participating in the same AI / ML action (task) by performing ProSe Direct Discovery based on PC5-related information.

[0361] When decentralized AI / ML operations are performed in a groupcast manner, the UE can perform groupcast based on PC5-related information.

[0362] II. Second Example

[0363] AF can perform member UE selection for AI / ML operations (application operations) without NEF assistance.

[0364] In this case, the content described in the first embodiment may be applied even if Annex I (informative): Member UE selection without the NEF assistance at the AF of TS 23.502 v18.2.0 is used.

[0365] AF can interact with UDM to obtain steps 1) and 3) of step 1 of the first embodiment.

[0366] AF can interact with AMF to obtain step 2) of step 1 of the first embodiment.

[0367] AF may need to perform additional actions, such as interaction with UDR, to obtain step 1) 3) of the first embodiment.

[0368] When interacting with UDM, AF may additionally request to provide (notify) 1) and 3) of step 1 of the first embodiment.

[0369] When performing an interaction with AMF, AF may additionally request to provide (notify) 1) and 2) of step 1 of the first embodiment.

[0370] When interacting with UDR, AF may additionally request to provide (notify) step 1, 3) of the first embodiment.

[0371] AF can recognize (determine) a) to j) described in step 8 of the first embodiment.

[0372] Without the member UE selection assistance information provided by NEF, AF can recognize (decide) a) to j) described in step 8 of the first embodiment based on the information obtained from 5GC (or UE, etc.).

[0373] The AF described in step 8 of the first embodiment may be applied to acquire various information about the UE(s) included in the target UE list from the 5GC (5G Core), the UE(s) or the UE(s) selected (determined) as the UE(s) to participate in (use) the AI / ML operation.

[0374] The above acquisition operation (procedure) may be performed before, in parallel with, or after step 5 (i.e., Member UE Selection) of Annex I (informative): Member UE selection without the NEF assistance at the AF of TS 23.502 v18.2.0.

[0375] The contents described in steps 9 to 11 of the first embodiment can be applied.

[0376] If a UE participating in an AI / ML operation finds it difficult (impossible) to perform the AI / ML operation via a Uu connection, the UE can be made to perform the AI / ML operation via PC5. By providing the UE with the information necessary for the PC5 operation, the AI / ML operation can be efficiently and smoothly continued via PC5.

[0377] AF can select terminals to participate in AI / ML. AF can enable the selected terminals to perform AI / ML operations. In this regard, the following actions can be performed:

[0378] - AF may request NEF to provide / notify member UE selection assistance information. Or, it may subscribe to the above provision / notification service.

[0379] - AF can select / decide which member UE(s) to participate in (use) AI / ML operations based on member UE selection assistance information provided (notified) from NEF.

[0380] - AF can provide PC5 related information to the selected (determined) member UE(s).

[0381] The above PC5 related information may be part or all of I) to VIII) described in step 9 of the first embodiment.

[0382] The above PC5 related information may also be provided to the UE(s) together with the AF when instructing the UE(s) to perform AI / ML operations (e.g., FL).

[0383] - If it is determined that it is difficult or impossible for the UE to perform AI / ML operations using Uu, or if Uu becomes unavailable, it may be determined that the AI / ML operations are performed using PC5.

[0384] - The UE can perform AI / ML operations through PC5 with other UE(s) participating in the AI / ML operations.

[0385] The PC5-related information may be used to perform AI / ML operations via the PC5. For example, the PC5-related information may be used when forming a PC5 unicast link with another UE.

[0386] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0387] Figure 8 illustrates the AF procedure for the disclosure of this specification.

[0388] 1. AF can send a request for UE (User Equipment) selection assistance information for application operation to NEF (Network Exposure Function).

[0389] 2. Based on the above request, the AF can receive UE selection assistance information from the NEF.

[0390] The above UE selection assistance information may include a candidate UE list.

[0391] A UE included in the above candidate UE list may be capable of performing the above application operation via PC5 communication.

[0392] The QoS (Quality of Service) for Uu communication of a UE included in the above candidate UE list may not satisfy certain criteria.

[0393] 3. Based on the above UE selection assistance information, the AF can determine a member UE to perform the application operation through PC5 communication.

[0394] 4. AF can transmit PC5 related information to the above member UE.

[0395] The above PC5 related information may include information instructing the member UE to perform the application operation by performing a PC5 connection with a specific UE.

[0396] A UE included in the above candidate UE list may be performing the above application operation via Uu communication.

[0397] Based on the above UE selection assistance information, the AF can determine another member UE to perform the application operation via PC5 communication.

[0398] The AF can transmit the PC5 related information to the other member UE.

[0399] The above PC5 related information may include information that the specific UE acts as a server for the application operation.

[0400] The above PC5 related information may include information instructing the other member UE to perform the application operation by performing a PC5 connection with the specific UE.

[0401] The above request may include filtering criteria.

[0402] A UE included in the above candidate UE list may satisfy the above filtering criteria.

[0403] After receiving the UE selection assistance information, based on the fact that the first UE included in the candidate UE list does not satisfy the filtering criteria, the AF can receive a list from the NEF in which the first UE is deleted from the candidate UE list.

[0404] The step of determining the member UE may be performed based on the list from which the first UE has been deleted.

[0405] The above request may include a list of target UEs.

[0406] The above UE selection assistance information may include information about a UE included in the target UE list.

[0407] The above target UE list may include UEs included in the above candidate UE list.

[0408] The above PC5 related information may include information about a cast for the PC5 connection.

[0409] The above application operation may be an AI (Artificial Intelligence) operation or an ML (Machine Learning) operation.

[0410] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0411] Figure 9 illustrates the UE's procedure for disclosure of this specification.

[0412] 1. The UE can receive PC5 related information from the AF (Application Function).

[0413] The above UE may be capable of performing application operations via PC5 communication.

[0414] The QoS (Quality of Service) for Uu communication of the above UE may not meet certain criteria.

[0415] The above PC5 related information may include information instructing the UE to perform the application operation by performing a PC5 connection with a specific UE.

[0416] 2. Based on the above PC5 related information, the UE can form a PC5 connection with the specific UE.

[0417] The above UE may be performing the above application operation via Uu communication.

[0418] The above PC5 related information may include information about a cast for the PC5 connection.

[0419] The above application operation may be an AI (Artificial Intelligence) operation or an ML (Machine Learning) operation.

[0420] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0421] Figure 10 illustrates NEF's procedure for disclosure of this specification.

[0422] 1. NEF can receive a request for UE (User Equipment) selection assistance information for application operation from AF (Application Function).

[0423] 2. Based on the above request, NEF can receive information about multiple UEs from other NFs (Network Functions).

[0424] 3. Based on the information about the above multiple UEs, NEF can determine a list of candidate UEs.

[0425] A UE included in the above candidate UE list may be capable of performing the above application operation via PC5 communication.

[0426] The QoS (Quality of Service) for Uu communication of a UE included in the above candidate UE list may not satisfy certain criteria.

[0427] 4. NEF can transmit UE selection assistance information including the candidate UE list to the AF.

[0428] A UE included in the above candidate UE list may be performing the above application operation via Uu communication.

[0429] The above request may include filtering criteria.

[0430] The information about the plurality of UEs may include information about whether the plurality of UEs satisfy a filtering criterion.

[0431] A UE included in the above candidate UE list may satisfy the above filtering criteria.

[0432] After receiving information about the plurality of UEs, the NEF can receive notification information from the other NF.

[0433] The above notification information may include information that the first UE included in the candidate UE list does not satisfy the filtering criteria.

[0434] Based on the above notification information, the NEF can transmit to the AF a list in which the first UE is deleted from the candidate UE list.

[0435] The above request may include a list of target UEs.

[0436] The above target UE list may include the plurality of UEs.

[0437] The above target UE list may include UEs included in the above candidate UE list.

[0438] The above UE selection assistance information may include information about the plurality of UEs.

[0439] The above application operation may be an AI (Artificial Intelligence) operation or an ML (Machine Learning) operation.

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

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

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

[0443] The operations performed by the processor include: transmitting a request for UE selection assistance information for application operation to an NEF; receiving UE selection assistance information from the NEF based on the request; the UE selection assistance information includes a candidate UE list, and a UE included in the candidate UE list is capable of performing the application operation through PC5 communication, and a QoS (Quality of Service) for Uu communication of a UE included in the candidate UE list does not satisfy a specific standard, and determining a member UE to perform the application operation through PC5 communication based on the UE selection assistance information; and transmitting PC5-related information to the member UE, wherein the PC5-related information may include information instructing the member UE to perform the application operation by performing a PC5 connection with a specific UE.

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

[0445] The operations performed by the processor include: transmitting a request for UE selection assistance information for application operation to an NEF; receiving UE selection assistance information from the NEF based on the request; the UE selection assistance information includes a candidate UE list, and a UE included in the candidate UE list is capable of performing the application operation through PC5 communication, and a QoS (Quality of Service) for Uu communication of a UE included in the candidate UE list does not satisfy a specific standard, and determining a member UE to perform the application operation through PC5 communication based on the UE selection assistance information; and transmitting PC5-related information to the member UE, wherein the PC5-related information may include information instructing the member UE to perform the application operation by performing a PC5 connection with a specific UE.

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

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

[0448] Some examples of storage media are coupled to the processor, allowing the processor to read information from the storage media. Alternatively, the storage media may be integrated into the processor. The processor and storage media may reside in an ASIC. In other examples, the processor and storage media may reside as separate components.

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

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

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

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

[0453] The stored one or more commands include: transmitting a request for UE selection assistance information for application operation to an NEF; receiving UE selection assistance information from the NEF based on the request; the UE selection assistance information includes a candidate UE list, and a UE included in the candidate UE list is capable of performing the application operation through PC5 communication, and a QoS (Quality of Service) for Uu communication of a UE included in the candidate UE list does not satisfy a specific criterion, and determining a member UE to perform the application operation through PC5 communication based on the UE selection assistance information; and transmitting PC5-related information to the member UE, wherein the PC5-related information may include information instructing the member UE to perform the application operation by performing a PC5 connection with a specific UE.

[0454] This specification may have various effects.

[0455] For example, through the procedures disclosed herein, AF can select a terminal and instruct it to perform an application operation via PC5.

[0456] The effects that can be achieved through specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0457] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. As a method for AF (Application Function) to perform communication, A step of transmitting a request for UE (User Equipment) selection assistance information for application operation to NEF (Network Exposure Function); A step of receiving UE selection assistance information from the NEF based on the above request; The above UE selection assistance information includes a candidate UE list, The UE included in the above candidate UE list is capable of performing the above application operation through PC5 communication, The QoS (Quality of Service) for Uu communication of the UE included in the above candidate UE list does not meet a specific standard, A step of determining a member UE to perform the application operation through PC5 communication based on the above UE selection assistance information; Including a step of transmitting PC5 related information to the member UE, A method wherein the PC5-related information includes information instructing the member UE to perform the application operation by performing a PC5 connection with a specific UE.

2. In paragraph 1, The UE included in the above candidate UE list is a method in which the above application operation is being performed via Uu communication.

3. In paragraph 1 or 2, A step of determining another member UE to perform the application operation through PC5 communication based on the UE selection assistance information; Further comprising a step of transmitting the PC5 related information to the other member UE, The above PC5 related information includes information that the specific UE acts as a server for the application operation, A method wherein the PC5-related information includes information instructing the other member UE to perform the application operation by performing a PC5 connection with the specific UE.

4. In any one of the clauses 1 to 3, The above request includes filtering criteria, A method in which a UE included in the above candidate UE list satisfies the above filtering criteria.

5. In paragraph 4, Further comprising the step of receiving a list from the NEF in which the first UE is deleted from the candidate UE list based on the fact that the first UE included in the candidate UE list does not satisfy the filtering criteria after receiving the UE selection assistance information, A method in which the step of determining the member UE is performed based on a list from which the first UE has been deleted.

6. In paragraph 4, The above request includes a list of target UEs, The above UE selection assistance information includes information about the UE included in the target UE list, A method in which the target UE list includes a UE included in the candidate UE list.

7. In any one of paragraphs 1 to 6, A method wherein the above PC5 related information includes information about a cast for the above PC5 connection.

8. In any one of paragraphs 1 to 7, The above application operation is an AI (Artificial Intelligence) operation or an ML (Machine Learning) operation.

9. A method by which UE (User Equipment) performs communication, A step of receiving PC5 related information from AF (Application Function); The above UE can perform application operations through PC5 communication, The QoS (Quality of Service) for Uu communication of the above UE does not meet certain criteria, The above PC5 related information includes information instructing the UE to perform the application operation by performing a PC5 connection with a specific UE, A method comprising a step of forming a PC5 connection with the specific UE based on the PC5-related information.

10. In paragraph 9, The above UE is a method in which the above application operation is being performed via Uu communication.

11. In paragraph 9, A method wherein the above PC5 related information includes information about a cast for the above PC5 connection.

12. In any one of the clauses 9 to 11, The above application operation is an AI (Artificial Intelligence) operation or an ML (Machine Learning) operation.

13. As a method of performing communication by NEF (Network Exposure Function), A step of receiving a request for UE (User Equipment) selection assistance information for application operation from AF (Application Function); A step of receiving information about multiple UEs from another NF (Network Function) based on the above request; A step of determining a candidate UE list based on information about the plurality of UEs; The UE included in the above candidate UE list is capable of performing the above application operation through PC5 communication, The QoS (Quality of Service) for Uu communication of the UE included in the above candidate UE list does not meet a specific standard, A method comprising the step of transmitting UE selection assistance information including the candidate UE list to the AF.

14. In paragraph 13, The UE included in the above candidate UE list is a method in which the above application operation is being performed via Uu communication.

15. In paragraph 13, The above request includes filtering criteria, The information about the plurality of UEs includes information about whether the plurality of UEs satisfy the filtering criteria, A method in which a UE included in the above candidate UE list satisfies the above filtering criteria.

16. In paragraph 15, A step of receiving notification information from another NF after receiving information about the plurality of UEs; The above notification information includes information that the first UE included in the candidate UE list does not satisfy the filtering criteria, A method further comprising the step of transmitting to the AF a list of candidate UEs in which the first UE is deleted based on the notification information.

17. In paragraph 15, The above request includes a list of target UEs, The above target UE list includes the plurality of UEs, The target UE list includes UEs included in the candidate UE list, A method wherein the UE selection assistance information includes information about the plurality of UEs.

18. In any one of the clauses 13 to 17, The above application operation is an AI (Artificial Intelligence) operation or an ML (Machine Learning) operation.

19. As an AF (Application Function) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a method according to any one of claims 1 to 8.

20. As a UE (User Equipment) performing communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a UE according to any one of claims 9 to 12.

21. As a Network Exposure Function (NEF) that performs communication, Transmitter and receiver; Contains a processor, The operation performed by the above processor is a method according to any one of claims 13 to 18.

Images