Method and device for monitoring terminal data collection in wireless communication system
Patent Information
- Application Number
- PCT/KR2026/005860
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
Smart Images

Figure KR2026005860_12112026_PF_FP_ABST
Abstract
Description
Method and apparatus for monitoring terminal data collection in a wireless communication system
[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure proposes a method and apparatus for monitoring wireless communication network resources used when collecting terminal information for training a machine learning model running on a terminal.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.
[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC), technologies included beamforming and massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands; support for various numerologies (such as operating multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources; initial access technologies to support multi-beam transmission and broadband; definition and operation of band-width parts (BWPs); new channel coding methods such as low-density parity check (LDPC) codes for high-volume data transmission and polar codes for reliable transmission of control information; L2 pre-processing; and networks providing dedicated networks specialized for specific services. Standardization of network slicing and the like has been carried out.
[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (vehicle-to-everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (new radio unlicensed), which aims for system operation in unlicensed bands that meets various regulatory requirements; NR terminal low power consumption technology (UE power saving); non-terrestrial network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.
[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including conditional handover and Dual Active Protocol Stack (DAPS) handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., service-based architecture, service-based interface) for incorporating network functions virtualization (NFV) and software-defined networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.
[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using extended reality (XR), artificial intelligence (AI), and machine learning (ML) to efficiently support augmented reality (AR), virtual reality (VR), and mixed reality (MR).
[0007] In addition, the advancement of these 5G mobile communication systems can serve as a foundation for the development of new waveforms for ensuring coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, metamaterial-based lenses and antennas to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable intelligent surface) technology, as well as full-duplex technology for improving frequency efficiency and system networks of 6G mobile communication technology, AI-based communication technology that realizes system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology that realizes services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources.
[0008] In order to perform training on a machine learning model used to improve wireless communication performance at a terminal, data collected from the terminal may be transmitted to a machine learning model training server. Data collected from the terminal may be collected by network functions within the core network for the control and management of a mobile communication network operator and then transmitted to the machine learning model training server. In the case of signaling data exchanged between the network functions of the existing core network and the terminal, it is generally transmitted and received through a control plane. However, transmitting data to be used for machine learning model training collected from the terminal through the control plane may not be suitable. This is because, considering the protocols, signaling messages, and wireless resource allocations supported by the existing control plane, it is not suitable for transmitting large amounts of data. The present disclosure proposes a method for monitoring wireless communication network resources used when transmitting data collected from the terminal to network functions within the core network through a user plane rather than a control plane.
[0009] A method according to one embodiment for solving the above-mentioned problem is characterized in that, in a method for processing a control signal in a wireless communication system, the method comprises the steps of receiving a first control signal transmitted from a base station, processing the received first control signal, generating a second signal based on the processing, and transmitting the generated second control signal to the base station.
[0010] General terminal traffic and traffic used for data collection can be separated. When collected terminal data is provided to an external training server provider, a business model may be provided that charges are based on the monitoring results of wireless communication network usage used for data collection. Alternatively, traffic usage for data collection, rather than the user's general traffic, may be controlled to be excluded from the charges charged to the user.
[0011] FIG. 1 illustrates an example of a wireless communication system structure that supports machine learning-based operation according to one embodiment of the present disclosure.
[0012] FIG. 2 illustrates a method in which a Data Collection Function (DCF) according to one embodiment of the present disclosure generates a user plane connection for data collection.
[0013] FIG. 3 illustrates another method in which a DCF according to one embodiment of the present disclosure creates a user plane connection for data collection.
[0014] FIG. 4 illustrates the configuration of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0015] FIG. 5 illustrates the configuration of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0016] FIG. 6 illustrates the configuration of a network entity in a wireless communication system according to one embodiment of the present disclosure.
[0017] In the following description of the present invention, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the essence of the present invention, such detailed description will be omitted.
[0018] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted.
[0019] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. Furthermore, the terms described below are defined based on their functions in the present disclosure. Since the terms of the present disclosure may vary depending on the intent or convention of the user or operator, their definitions should be determined according to the content throughout the present disclosure.
[0020] Terms used in this disclosure to refer to network entities or network functions, messages, identification information, etc., are examples provided for convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0021] For convenience, the present invention uses terms and names defined in 5G system specifications, but is not limited by said terms and names and can be applied in the same way to systems conforming to other specifications.
[0022] The operating principle of the present invention is described in detail below with reference to the attached drawings.
[0023] In describing the embodiments of the present disclosure, descriptions of technical details that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure may be omitted. This is intended to convey the essence of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0024] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual size. Identical or corresponding components in each drawing may be assigned the same reference number.
[0025] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. The embodiments provided are merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.
[0026] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0027] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.
[0028] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.
[0029] In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Embodiments of the present disclosure will be described below with reference to the attached drawings.
[0030] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0031] For convenience of explanation, the present disclosure uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present disclosure is not limited by the above terms and names and may be applied equally to systems conforming to other standards. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Additionally, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.
[0032] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above examples.
[0033] In particular, the present disclosure is applicable to 3GPP NR (5th generation mobile communication standard). Furthermore, the present disclosure is applicable to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. In the present invention, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Additionally, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.
[0034] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 3GPP’s HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.
[0035] As a representative example of a broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment; UE or Mobile Station; MS) transmits data or control signals to a base station (eNode B or BS; Base Station), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above multiple access method distinguishes the data or control information of each user by allocating and operating time-frequency resources to be transmitted for each user so that they do not overlap, that is, so that orthogonality is established.
[0036] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include Enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).
[0037] According to some embodiments, eMBB may aim to provide data transmission speeds that are higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. In addition, the 5G communication system may need to provide a user-perceived data rate while simultaneously providing the peak data rate. To satisfy these requirements, the 5G communication system may require improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Furthermore, while current LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can satisfy the data transmission speeds required by the 5G communication system by using a frequency bandwidth wider than 20 MHz in frequency bands of 3 to 6 GHz or above 6 GHz.
[0038] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT services, mMTC may require support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, wider coverage may be required compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.
[0039] Finally, URLLC is a mission-critical cellular-based wireless communication service that can be used for services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to offer very low latency and very high reliability. For example, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and may simultaneously require a packet error rate of 10^-5 or less. Consequently, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.
[0040] The three services considered in the aforementioned 5G communication system, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types to which the present disclosure applies are not limited to the examples mentioned above.
[0041] In addition, although embodiments of the present disclosure are described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems as examples, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. Furthermore, embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0042] Furthermore, the terms described below are defined in consideration of their functions in the present invention, and these may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.
[0043] Preferred embodiments of the present disclosure are described in detail below with reference to the attached drawings. It should be noted that identical components in the attached drawings are indicated by the same reference numerals whenever possible. Furthermore, it should be noted that the drawings of the present invention attached below are provided to aid in understanding the present invention, and that the present invention is not limited to the forms or arrangements illustrated in the drawings. Additionally, detailed descriptions of known functions and configurations that may obscure the essence of the present invention will be omitted. It should be noted that in the following description, only the parts necessary for understanding the operation according to various embodiments of the present invention are described, and descriptions of other parts will be omitted so as not to distract from the essence of the present invention. Furthermore, the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3GPP (3rd Generation Partnership Project)), but this is merely an example for illustrative purposes. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.
[0044] The present invention proposes a method for monitoring mobile communication network resources used to collect data from a terminal to a mobile communication core network. Specifically, to monitor mobile communication network resources used according to the path for transmitting and receiving data collected from the terminal, the invention proposes a method for distinguishing between general application traffic or signaling traffic and terminal data collection traffic.
[0045] FIG. 1 illustrates an example of a wireless communication system structure that supports machine learning-based operation according to one embodiment of the present disclosure.
[0046] Referring to FIG. 1, a 5G system structure supporting machine learning-based operation may include various network functions (NF), and FIG. 1 illustrates some of these, including an access and mobility management function (AMF), a session management function (SMF), unified data management (UDM), a data network (DN) or a local part of the DN capable of local access to the data network, a user plane function (UPF), a (radio) access network ((R)AN), user equipment (UE), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Network Data Analytics Function (NWDAF), and a Data Collection Function (DCF).
[0047] A terminal may use a machine learning model to perform operations such as channel state information prediction, channel state information compression, beam management, and positioning to improve wireless communication performance. For example, the terminal may decide to use a machine learning model to perform the specific operations mentioned above, and if multiple machine learning models are used, it may select one model to perform operations for improving wireless communication performance. The terminal may receive requests for data collection and configuration information for data collection from network devices such as a RAN, DCF, or NWDAF.
[0048] Each NF supports the following functions.
[0049] - AMF provides functions for connectivity and mobility management at the UE level, and each UE can be connected to one AMF by default.
[0050] - (R)AN transmits and receives data wirelessly with the terminal and can transmit and receive terminal user plane data with the UPF. In addition, it performs access and mobility management of the terminal in conjunction with the AMF.
[0051] - DN refers to, for example, operator services, internet access, or third-party services. The DN transmits downlink protocol data units (PDUs) to the UPF or receives PDUs transmitted from the UE from the UPF. A local part of a DN refers to a data network within a part of the DN that enables local access and has a short data transmission path. It can be used to refer to a DN where edge application servers supporting edge computing services are deployed.
[0052] - The PCF receives information about packet flows from application servers and provides the function of determining policies such as mobility management and session management. Specifically, the PCF supports functions such as supporting a unified policy framework to control network behavior, providing policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and implementing a front end to access relevant subscription information within the unified data repository (UDR) for policy decisions.
[0053] - SMF provides session management functions, and if a UE has multiple sessions, each session can be managed by a different SMF.
[0054] - UDM stores user subscription data, policy data, etc. It can store user consent information regarding the collection, storage, and processing of device-related information used for machine learning training, inference, etc.
[0055] - The UPF forwards the downlink PDU received from the DN to the UE via the (R)AN, and forwards the uplink PDU received from the UE to the DN via the (R)AN.
[0056] - The DCF can collect terminal-related information and provide configuration information for collecting terminal-related information to the terminal or RAN. The DCF can be defined as a new network function or as a new function or device included in an existing NF (e.g., NWDAF or Data collection and coordination function) and deployed and operated. Additionally, the DCF can perform the function of transmitting information collected from the terminal to a network device or server that performs machine learning. Furthermore, the DCF can perform review and analysis of the information collected from the terminal before transmitting it to the machine learning execution device. Depending on the specific machine learning execution use case, the DCF may be a function or device included in the location management function. For example, when calculating terminal location based on machine learning, the LMF performs terminal-related data collection, and the specific function or device within the LMF responsible for data collection may be considered as the DCF.
[0057] FIG. 2 illustrates a method in which a DCF generates a user plane connection for data collection according to one embodiment of the present disclosure.
[0058] 0. A DCF can receive a data collection request from a server performing machine learning training. The data collection request can be transmitted to the DCF via a device such as a Network exposure function as an AF request. At this time, a specific DCF may be selected and the data collection request transmitted, taking into account the machine learning training model target or machine learning application use case information (e.g., beam management, CSI (channel state information) prediction, CSI compression, positioning, etc.).
[0059] 0-a. When the DCF receives a data collection request, it may send a policy authorization request message to the PCF to create and apply a session management policy related to monitoring of data collection. The policy authorization request message sent by the DCF to the PCF may include at least one of the following: an application ID assigned to the DCF or data collection device, a data collection service ID, address information that can be used as the data collection endpoint address of the DCF as SDF (Service Data Flow) template information (e.g., DCF IP address, port number, or terminal UE IP address (private IP address or public IP address)), a DNN (data network name) or S-NSSAI (Single Network Slice Selection Assistance Information) information assigned (or can be used) for data collection through the DCF, or an identifier for the data collection target terminal, an identifier assigned to the training server or training server provider (e.g., training server provider ID, application function ID, application service provider ID, data collection ID, data collection binding ID, or data collection requestor ID). The data collection service ID provided by DCF is information that can be mapped to packet traffic information, DCF addresses, etc., which can be used to detect or classify traffic used for data collection.The data collection service ID can be set to a unique value within the PLMN and may be configured within network functions involved in data collection, such as PCF, SMF, UPF, DCF, and UDR.
[0060] 0-b. The PCF can obtain subscription data from the UDR that can be considered when creating a session management policy related to data collection. The PCF can use the information received through the operation 0-a to obtain subscription data from the UDR. For example, when the PCF receives a terminal IP address from the DCF, it can obtain a terminal identifier corresponding to the terminal IP address through the Binding Support Function (BSF), and request the UDR with the obtained terminal identifier to obtain the subscription data stored in the UDR.
[0061] 0-c. PCF can generate a session management policy by considering monitoring information related to data collection within subscription data obtained from UDR. The session management policy generated by PCF may include at least one of the following information.
[0062] -Data collection start / stop notification requested
[0063] - Data collection start / stop policy control request trigger
[0064] - Usage Monitoring control related information: Defines the information required to enable user plane monitoring of resources for individual applications / services, groups of applications / services, and a PDU Session. When data collection is performed through the user plane, this information may be included to monitor how much of the user plane resources used for data collection are being utilized. For example, information such as a monitoring key, volume threshold, time threshold, monitoring time, and inactivity detection time may be included and configured specifically for data collection. The PCF can transmit to the DCF the result regarding whether a session management policy containing user plane resource monitoring information used for data collection has been successfully created and applied.
[0065] Operations 0-a through 0-c are described as the DCF receiving and performing a data collection request, but the present disclosure does not limit the timing at which the DCF performs said operations. For example, operations 0-a through 0-c may be performed by the DCF and PCF after step 8, after the PDU session creation and UP connection have been successfully created.
[0066] According to one embodiment of the present invention, operations 0-a to 0-c may be performed when the DCF obtains the IP address or terminal identifier of the terminal.
[0067] 1. The DCF may transmit a terminal data collection request to the AMF. The conditions under which the DCF decides to transmit the terminal data collection request may be at least one of the following.
[0068] - Received a data collection request from the machine learning training server (Over the top server, training server) in the previous step
[0069] - DCF decides on data collection based on operator policy or local configuration.
[0070] The DCF can determine the terminals to be collected for data collection before transmitting a terminal data collection request to the AMF. The considerations when selecting the terminals to be collected for data collection may include at least one of the following.
[0071] - A terminal supporting the ability to perform data collection and transfer for machine learning model training (UE data collection and transfer capability): Such information may be defined as a type of UE capability. UE data collection capability information may be defined separately from UE data transfer capability and may include information regarding data that can be collected by the terminal. For example, UE data collection capability may include at least one of machine learning model information or information indicating the purpose of using the machine learning model, or may be defined in correspondence with such information. Machine learning model information or information regarding the purpose of using the machine learning model may be defined as information or an index that can represent use cases, such as beam management, CSI prediction, or positioning. Additionally, machine learning model information and information regarding the purpose of using the machine learning model may include information indicating which device the trained machine learning model is running on (e.g., may include information indicating a UE-side model, network-side model, LMF-side model, etc.). Here, a UE-side model may be information indicating that it is a machine learning model running within the terminal for operations performed on the terminal.
[0072] - Terminals provided with user consent information for terminal data collection: The DCF may send a data collection request only if the terminal stores user consent information or privacy profile information corresponding to information such as the terminal identifier (e.g., SUPI (Subscription Permanent Identifier) or GPSI (Generic Public Subscription Identifier)), indicating that the user has consented to terminal data collection within the subscriber information. In the case of UE positioning, which is the purpose of use for a machine learning model, the DCF may check the LCS privacy profile to determine whether information indicating that the terminal consents to the collection of location-related information is stored within the core network (e.g., UDM or UDR).
[0073] - Radio access type or Radio access technology information
[0074] - Frequency band information
[0075] The DCF can search for and discover the AMF managing the terminal, the AMF registered by the terminal, or the AMF storing and managing the UE context for the terminal through the UDM or NRF, and transmit a data collection request. The AMF can consider the information received from the DCF and transmit a data collection request to the RAN node to which the terminal is currently wirelessly connected.
[0076] 2. If the RAN can successfully perform the data collection request, it can send a response to the data collection request to the DCF.
[0077] 3. The RAN can perform configuration operations on the data collection target terminal. It can provide information for UE measurement configuration to the terminal so that the terminal can acquire the data to be collected.
[0078] 4. The terminal can perform UE measurements based on information provided by the RAN and store and manage the collected information within the terminal. The terminal may store the collected data in the layer processing the Access stratum, which is the lower layer of the modem, or pass the collected data to the upper layer processing the Non-Access stratum. Alternatively, the terminal may pass the UE measurement information obtained through Access stratum signaling to the upper layer of the modem, or pass it to terminal equipment outside the modem within the terminal for storage and management.
[0079] 5. The DCF may perform operations to receive data collected by the terminal simultaneously with or after the data collection request. The DCF may perform the following operations to perform UE data transfer.
[0080] - Selection of transmission path for data collected from the terminal: The DCF may select whether to receive the terminal collected data to the control plane or to the user plane (which may be referred to as UP in this disclosure). The selection may determine whether to perform data transfer to the user plane by considering at least one of the control plane status information (e.g., at least one of CP congestion status, AMF congestion level, or control plane interface congestion level with the RAN core network), the size of the collected data (e.g., the information may use reference information regarding the size of data collected by the terminal set within the DCF, or at least one of the collected data size information included in the data collection progress / result information received from the terminal through direct signaling exchange with the terminal), information on a machine learning model to perform learning through the collected data, use case information to which the machine learning model to perform learning through the collected data applies, terminal subscriber information (e.g., information on whether the terminal is allowed to transmit data collected through the user plane), or UE capability information (e.g., information on whether the terminal can transmit information collected through the user plane to the core network). According to one embodiment, the DCF may obtain and consider at least one of the following information from the AMF or RAN: CP congestion status, AM congestion or overload information, or control plane interface congestion with the RAN core network. According to one embodiment, the DCF may obtain information about data collected from a terminal (e.g., size of data collected from the terminal) and perform an operation to make a decision on data transfer path selection (e.g., selection of CP or UP).For example, the DCF may request data collection progress or result information from the terminal through step 5-a, and in response, receive information regarding the size of the collected data, etc., as part of the data collection information from the terminal. According to one embodiment, through step 5-a, the DCF may provide information such as a DCF identifier and a data collection / transfer binding ID to the terminal.
[0081] According to various embodiments, the DCF may determine to perform data collection via the user plane only for terminals that are allowed to transmit data collected via the user plane and that support the corresponding data transfer over UP related function. According to one embodiment, the DCF may determine whether to perform data transmission collected via the user plane by obtaining subscriber information from the UDM or UDR indicating whether the terminal is allowed to transmit data collected via the user plane. UE capability information regarding whether the terminal supports the data transmission function via the user plane may be obtained from the AMF, or the network function managing UE capability information may be obtained from the UCMF (UE Capability Management Function). When performing a Registration operation with the AMF to provide the DCF with information regarding whether the terminal supports data transmission collected via the user plane, the terminal may transmit UE capability information regarding whether it supports the corresponding data transfer via UP function to the AMF.
[0082] When the DCF determines terminal data transmission, it can assign a data collection binding ID or a data transfer binding ID based on a specific terminal and the data information collected by that terminal. The data collection / transfer binding ID can be expressed in various forms, such as a data collection / transfer association ID or context ID, index, reference ID, correlation ID, etc. The data collection / transfer binding ID can be assigned and managed according to the purpose for which the collected data is used (e.g., purpose information that can be defined based on use cases or machine learning model information) or the training server, which is the final destination for data transmission. Furthermore, in the case of the data collection / transfer binding ID, if the transmission method of the collected terminal data is determined to be data transfer via UP, it can be assigned, stored, and managed in correspondence with the corresponding UP connection information (e.g., connection or session information established on the user plane between the terminal and the DCF). Additionally, the data collection / transfer binding ID can be stored and managed in correspondence with a terminal identifier (e.g., SUPI or GPSI).According to one embodiment, the DCF can generate UE data collection / transfer context information for the purpose of managing data collection and transmission on a terminal basis, and store and manage data collection binding ID or data transfer binding ID, data collection purpose (e.g., use case, ML model information), data collection final destination information (e.g., OTT server, training server), selected data transfer method (e.g., data transfer via CP or data transfer via UP), data collection request execution information (e.g., data collection request time stamp), etc.
[0083] 6. When the DCF decides to perform the transmission of collected terminal data, it may transmit a message to the AMF comprising at least one of a terminal identifier, a collected data transmission request indicator, a UP connection request indication (which may be included if the DCF decides to perform the transmission of collected terminal data through the UP), a DCF identifier, DCF user plane information (which may include at least one of address information required to establish a UP connection with the DCF, such as an FQDN or IP address), a DNN, an S-NSSAI, a data collection / transfer binding ID, and security information required for security regarding the UP connection between the DCF and the terminal (such as security protocol information). According to one embodiment, the DCF may call the Namf_comm_N1N2Transfer service to transmit the message to the AMF.
[0084] 7. The AMF may receive a request for data transfer from a DCF and generate and manage terminal data transfer information according to the method of the request for data transfer from the DCF. For example, if the DCF determines a data transfer via UP and the AMF receives a request for data transfer from the DCF and DCF UP information, the AMF may store the information within the AMF. According to one embodiment, the AMF may not perform storage of the information in step 7, but may generate it after receiving an acknowledgment from the terminal that data transfer can be performed. The AMF may store and manage UP connection context information within the AMF. The UP connection context information may include at least one of DCF information (e.g., identifier and address information), UP connection ID, and data collection / transfer binding ID. Considering the information received from the DCF, the AMF may transmit a message (through the RAN) to the terminal to which the terminal that needs to perform data collection transmission is currently connected, the message including at least one of a data collection transmission request indicator, a UP connection request indication (e.g., may be included if the DCF decides to perform data collection transmission through the UP), DCF user plane information (e.g., may include at least one of address information required to establish a UP connection with the DCF, such as an FQDN or an IP address), a DNN, an S-NSSAI, a data collection / transfer binding ID, and security information required for security regarding the UP connection between the DCF and the terminal (e.g., security protocol information, etc.).When the AMF receives a data transmission request message from the DCF in step 6, depending on the connection status between the terminal and the AMF, it can perform paging to establish a NAS layer signaling connection with the terminal to secure connectivity with the terminal, and then transmit the above information to the terminal.
[0085] 8. The terminal may perform the following operations by considering the information within the message received through the AMF. When the terminal receives a UP connection request indication or DCF UP information, it may perform an operation to establish a UP connection to the DCF using the information included in the DCF UP information. Such operation may include the following.
[0086] - If the terminal receives DNN or S-NSSAI information, the terminal uses the received DNN / S-NSSAI information to create a new PDU session, or if a PDU session corresponding to the DNN / S-NSSAI has already been created, performs the operation of reusing the existing PDU session.
[0087] - If the DCF address information included in the DCF's UP information is an FQDN, the terminal may send a DNS query to a DNS server configured within the terminal to obtain an IP address for the DCF. The DNS server address may be the address of a DNS server configured or operated by the core network operator or the operator responsible for operating the DCF. The DNS server address information may be the DNS server address provided to the terminal during the process of creating a PDU session. Alternatively, the DNS server address may be configured as an EASDF (edge application server discovery function) address used in the core network and provided to the terminal.
[0088] - The terminal can transmit a UP connection message to the DCF to the DCF via a user plane path (through the created or selected PDU session) using the DCF address information included in the DCF UP information, after performing a creation or selection operation for a PDU session to transmit the UP connection message to the DCF. The UP connection message to the DCF may include information such as a data collection / transfer binding ID, a UE identifier, and information related to collected data (e.g., collected data metadata, size of collected data). The UP connection message to the DCF transmitted by the terminal may be transmitted as part of a specified protocol message (e.g., AI / ML data collection / transfer protocol) defined between the terminal and the DCF.
[0089] - Upon receiving a UP connection request message, the DCF may perform an authentication security procedure for the corresponding terminal and perform the following operations. The DCF may consider the information within the received UP connection request message, assign a UP connection ID to the UP connection established with the terminal, and manage it in correspondence with data collection / transfer binding ID information. According to one embodiment, multiple UP Connection IDs and data collection / transfer binding IDs may be assigned and used between a single terminal and the DCF. For example, if the terminal performs data collection and transmission for multiple use cases, a different data collection / transfer binding ID may be assigned and used for each use case. Additionally, multiple UP connection IDs may also be assigned and managed for each data set collected by the terminal or for each use case of the data collected by the terminal.
[0090] - After confirming that it can successfully execute the terminal's UP connection request, the DCF may send a response message to the UP connection request to the terminal notifying that a UP connection has been successfully established. The response message may include at least one of UP connection ID or data collection / transfer binding ID information. The DCF and the terminal may associate the established UP connection with the terminal / DCF using at least one of the UP connection ID or data collection / transfer binding ID information, and this information may be used to identify which data among the collected data the UP connection is intended to transmit (for example, it may be used to identify the established UP connection in association with which use case or data for training a machine learning model).
[0091] If the terminal transmits a PDU session creation request to the AMF during the operation of Step 8 above, the following operations may be performed. The AMF may determine from the terminal that the request is a PDU session creation request that can be used for data collection through one of the following methods.
[0092] - If the terminal provides the AMF with a data collection over UP support indication, the AMF can recognize that it is a request to create a PDU session that can be used for data collection.
[0093] - If AMF creates and manages DCF UP information received from DCF through the previous steps or contexts related to the use of user plane resources for data collection, it can determine that the PDU session request is for a session related to data collection.
[0094] - When the AMF receives a PDU session request for a specific DNN or S_NSSAI, it can determine, based on internal settings, that the PDU session for the corresponding DNN, S_NSSAI, and the terminal identifier requesting the PDU session creation can be used for data collection.
[0095] When the AMF receives a PDU session request for a specific DNN or S_NSSAI, it can receive subscription data regarding the corresponding DNN, S_NSSAI, and the terminal identifier requesting the PDU session creation through the UDM. For example, the AMF obtains data collection over UP supported / allowed information included in the SMF selection data within the UDM from the UDM, and through this information, it can determine whether the user plane is allowed or supported for the corresponding terminal, DNN, and S_NSSAI. Through the subscription data obtained from the UDM in this way, the AMF can determine that the requested PDU session creation can be used for data collection.
[0096] If the AMF determines through various methods as described above that the PDU session requested by the terminal can be used for data collection, the AMF can send a data collection over UP supported / allowed indication to the SMF.
[0097] 8-A. When the SMF receives a data collection over UP supported / allowed indication from the AMF, it can confirm that data collection over UP is permitted by considering the data collection over UP authorization information included in the session management subscription data received from the UDM.
[0098] When the SMF receives a data collection over UP supported / allowed indication from the AMF or receives information from the UDM indicating that data collection over UP is supported and allowed, it may transmit an indication of DC over UP allowed when requesting a session management policy from the PCF. According to one embodiment, when the SMF receives a data collection over UP supported / allowed indication from the AMF or receives information from the UDM indicating that data collection over UP is supported and allowed, it may perform a session management association procedure while transmitting at least one of an indication of DC over UP allowed, a data collection binding ID, DCF information, and DCF UP information to the PCF.
[0099] 8-B. When the PCF receives a session management association request or a session management policy request message from the SMF that includes an indication of DC over UP allowed, the PCF may provide at least one of Usage Monitoring Control related information for DC over UP and Policy control request trigger information to the SMF, taking into account the DCF information related to data collection. The SMF may set the usage monitoring control related information for DC over UP received from the PCF to the UPF located in the data collection path.
[0100] 9. When the terminal successfully completes the creation of a UP connection for data transfer with the DCF in the previous step, it may send an acknowledgment to UP connection established for data transfer message to the AMF. The message may include the result of creating a UP connection to transfer data collected by the terminal to the DCF via UP, a UP connection ID, or a data collection / transfer binding ID.
[0101] 10. The AMF may transmit an acknowledgment to UP connection established for data transfer message received from the terminal to the DCF. If the acknowledgment to UP connection established for data transfer message contains result information indicating that the terminal has successfully established a UP connection with the DCF, the AMF may store and manage UP connection context information within the AMF. The UP connection context information may include at least one of DCF information (e.g., identifier and address information), a UP connection ID, and a data collection / transfer binding ID.
[0102] 11. The terminal can transmit the collected data through a UP connection with the DCF successfully created in the previous step. When transmitting the collected data, the UP connection ID or the Data collection / transfer binding ID may be transmitted together.
[0103] 11-A. When the PDU session creation and the UP connection creation between the terminal and the DCF are successfully performed through steps 8 to 10 above, the UPF, having received usage monitoring control related information for DC over UP from the SMF, can monitor the usage, transmission time, etc. of the traffic transmitted to the DCF. The UPF can determine the information to be monitored based on the usage monitoring control related information for DC over UP received from the SMF.
[0104] 11-B. The UPF may transmit to the SMF the results of monitoring the wireless communication network user plane resources used for data transmission to the terminal's DCF. The SMF may report the monitoring results received from the UPF to the PCF by mapping them to at least one of the following information: a Data Collection binding ID, a Data Collection function identifier, or a monitoring key. The information reported by the SMF to the PCF may be determined based on policy control request / report trigger (PCRT) information related to data collection over UP received from the PCF, and may include, for example, information such as the occurrence of a Data Collection start / stop event.
[0105] 11-C. The UPF may transmit to the SMF the results of monitoring the wireless communication network user plane resources used for data transmission to the terminal's DCF. The SMF may report the monitoring results received from the UPF to the CHF (charging function) by mapping them to at least one of the following information: a Data Collection binding ID, a Data Collection function identifier, and a monitoring key. The information reported by the SMF to the CHF may include the monitoring results received from the UPF, at least one of the following information: a Data Collection binding ID, a Data Collection function identifier, a monitoring key, and a charging key, as well as user plane resource usage information (e.g., data volume used, data transmission / reception duration).
[0106] 12. The DCF can store and manage data to be used for training received from the terminal. The DCF can perform an operation to verify whether the received data is data collected in accordance with the data collection settings. The DCF can identify the machine learning model training server to which the data to be used for training transmitted by the terminal should be transmitted and transmit the collected data. This step may be transmitted along with the response message to the data collection request made by the machine learning model training server in Step 0. Additionally, the DCF can transmit information regarding Reporting Usage Monitoring information for the transmitted data to Training Server (e.g., ASP ID, Training Server provider ID, Data Collection Binding ID) to the CHF.
[0107] 13. After successfully performing machine learning training using the data collection requested from DCF, the machine learning model training server can perform the operation of setting the trained machine learning model on the terminal.
[0108] According to one embodiment of the present disclosure, through the operations illustrated in FIG. 2, the SMF and CHF can know information regarding the usage of mobile communication network resources used to collect data to be provided to a specific training server (or over-the-top server). The SMF or CHF can store and manage information regarding the usage of network resources provided from the UPF in correspondence (or association) with at least one of DCF information (e.g., identifier or address information), an identifier assigned to the training server or training server provider (e.g., training server provider ID, application function ID, application service provider ID, data collection ID, data collection binding ID, or data collection requestor ID), a terminal identifier, or an application ID.
[0109] According to an embodiment of the present disclosure, the result of monitoring the usage of user plane network resources used to collect data can be used for various purposes as follows. According to one embodiment, when charges for mobile communication services are applied to a specific terminal, the usage of user plane network resources used for AIML model training described in the present disclosure may be excluded from the charges. This operation may be performed by the CHF excluding the result of monitoring the resource usage used for data collection, reported by the SMF, from the total network resource usage. Additionally, according to one embodiment, the result of monitoring the user plane network resource usage may be stored and managed by the SMF or CHF for each training server provider. This may mean that the network resource usage used to transmit and receive collected data from the terminal to provide it to a specific training server can be calculated and stored. The CHF may charge for data collection and provision based on the network resource usage used for data collection for each training server provider.
[0110] FIG. 3 illustrates another method in which a DCF generates a user plane connection for data collection according to one embodiment of the present disclosure. Meanwhile, descriptions that overlap with those described in FIG. 2 may be omitted in the following description of FIG. 3.
[0111] 0. A DCF can receive a data collection request from a server performing machine learning training. The data collection request can be transmitted to the DCF via a device such as a Network exposure function as an AF request. At this time, a specific DCF may be selected and the data collection request transmitted, taking into account the machine learning training model target or machine learning application use case information (e.g., beam management, CSI (channel state information) prediction, CSI compression, positioning, etc.).
[0112] DCF and UDR can store data for monitoring usage for data collection through UP. For example, as in step 0-a, DCF can send a message to UDR that provides information that can be used to create a session management policy related to monitoring data collection. The policy authorization request message sent by DCF to UDR may include at least one of the following: an application ID assigned to DCF or a data collection device, a data collection service ID, and address information that can be used as the DCF's data collection endpoint address as SDF template information (e.g., DCF IP address, port number, or terminal UE IP address (private IP address or public IP address)); DNN or S-NSSAI information assigned (or can be used) for data collection through DCF; or a data collection target terminal identifier, or an identifier assigned to a training server or training server provider (e.g., training server provider ID, application function ID, application service provider ID, data collection ID, data collection binding ID, or data collection requestor ID). The data collection service ID provided by DCF is information that can be mapped to packet traffic information, DCF addresses, etc., which can be used to detect or classify traffic used for data collection.The data collection service ID can be set to a unique value within the PLMN and may be set within network functions involved in data collection, such as PCF, SMF, UPF, DCF, and UDR. The UDR can successfully store information received from the DCF and send a message to the DCF indicating that the information has been successfully stored.
[0113] Additionally, as in step 0-b, the UDR can notify the PCF of the data stored therein. The PCF may have already completed the subscription to notification operation by sending a subscribe request message to the UDR in advance to receive data from the UDR for creating a session management policy related to data collection.
[0114] According to one embodiment of the present disclosure, the time at which the DCF performs steps 0-a and 0-b is not limited to after receiving a data collection request from the training server.
[0115] According to one embodiment of the present disclosure, the time at which the DCF performs steps 0-a and 0-b may be before receiving a data collection request from the training server, depending on the operator policy or internal settings within the DCF.
[0116] According to one embodiment of the present disclosure, the time at which the DCF performs steps 0-a and 0-b may be after it is decided to perform data collection using a user plane for a specific terminal according to an operator policy or an internal setting within the DCF.
[0117] 1. The DCF may transmit a terminal data collection request to the AMF. The conditions under which the DCF decides to transmit the terminal data collection request may be at least one of the following.
[0118] - Received a data collection request from the machine learning training server (Over the top server, training server) in the previous step
[0119] - DCF decides on data collection based on operator policy or local configuration.
[0120] The DCF can determine the terminals to be collected for data collection before transmitting a terminal data collection request to the AMF. The considerations when selecting the terminals to be collected for data collection may include at least one of the following.
[0121] - A terminal supporting the ability to perform data collection and transfer for machine learning model training (UE data collection and transfer capability): Such information may be defined as a type of UE capability. UE data collection capability information may be defined separately from UE data transfer capability and may include information regarding data that can be collected by the terminal. For example, UE data collection capability may include at least one of machine learning model information or information indicating the purpose of using the machine learning model, or may be defined in correspondence with such information. Machine learning model information or information regarding the purpose of using the machine learning model may be defined as information or an index that can represent use cases, such as beam management, CSI prediction, or positioning. Additionally, machine learning model information and information regarding the purpose of using the machine learning model may include information indicating which device the trained machine learning model is running on (e.g., may include information indicating a UE-side model, network-side model, LMF-side model, etc.). Here, a UE-side model may be information indicating that it is a machine learning model running within the terminal for operations performed on the terminal.
[0122] - Terminals provided with user consent information for terminal data collection: The DCF may send a data collection request only if the terminal stores user consent information or privacy profile information corresponding to information such as the terminal identifier (e.g., SUPI (Subscription Permanent Identifier) or GPSI (Generic Public Subscription Identifier)), indicating that the user has consented to terminal data collection within the subscriber information. In the case of UE positioning, which is the purpose of use for a machine learning model, the DCF may check the LCS privacy profile to determine whether information indicating that the terminal consents to the collection of location-related information is stored within the core network (e.g., UDM or UDR).
[0123] - Radio access type or Radio access technology information
[0124] - Frequency band information
[0125] The DCF can search for and discover the AMF managing the terminal, the AMF registered by the terminal, or the AMF storing and managing the UE context for the terminal through the UDM or NRF, and transmit a data collection request. The AMF can consider the information received from the DCF and transmit a data collection request to the RAN node to which the terminal is currently wirelessly connected.
[0126] 2. If the RAN can successfully perform the data collection request, it can send a response to the data collection request to the DCF.
[0127] 3. The RAN can perform configuration operations on the data collection target terminal. It can provide information for UE measurement configuration to the terminal so that the terminal can acquire the data to be collected.
[0128] 4. The terminal can perform UE measurements based on information provided by the RAN and store and manage the collected information within the terminal. The terminal may store the collected data in the layer processing the Access stratum, which is the lower layer of the modem, or pass the collected data to the upper layer processing the Non-Access stratum. Alternatively, the terminal may pass the UE measurement information obtained through Access stratum signaling to the upper layer of the modem, or pass it to terminal equipment outside the modem within the terminal for storage and management.
[0129] 5. The DCF may perform operations to receive data collected by the terminal simultaneously with or after the data collection request. The DCF may perform the following operations to perform UE data transfer.
[0130] - Selection of transmission path for data collected from the terminal: The DCF may select whether to receive the terminal collected data to the control plane or to the user plane (which may be referred to as UP in this disclosure). The selection may determine whether to perform data transfer to the user plane by considering at least one of the control plane status information (e.g., at least one of CP congestion status, AMF congestion level, or control plane interface congestion level with the RAN core network), the size of the collected data (e.g., the information may use reference information regarding the size of data collected by the terminal set within the DCF, or at least one of the collected data size information included in the data collection progress / result information received from the terminal through direct signaling exchange with the terminal), information on a machine learning model to perform learning through the collected data, use case information to which the machine learning model to perform learning through the collected data applies, terminal subscriber information (e.g., information on whether the terminal is allowed to transmit data collected through the user plane), or UE capability information (e.g., information on whether the terminal can transmit information collected through the user plane to the core network). According to one embodiment, the DCF may obtain and consider at least one of the following information from the AMF or RAN: CP congestion status, AM congestion or overload information, or control plane interface congestion with the RAN core network. According to one embodiment, the DCF may obtain information about data collected from a terminal (e.g., size of data collected from the terminal) and perform an operation to make a decision on data transfer path selection (e.g., selection of CP or UP).For example, the DCF may request data collection progress or result information from the terminal through step 5-a, and in response, receive information regarding the size of the collected data, etc., as part of the data collection information from the terminal. According to one embodiment, through step 5-a, the DCF may provide information such as a DCF identifier and a data collection / transfer binding ID to the terminal.
[0131] According to various embodiments, the DCF may determine to perform data collection via the user plane only for terminals that are allowed to transmit data collected via the user plane and that support the corresponding data transfer over UP related function. According to one embodiment, the DCF may determine whether to perform data transmission collected via the user plane by obtaining subscriber information from the UDM or UDR indicating whether the terminal is allowed to transmit data collected via the user plane. UE capability information regarding whether the terminal supports the data transmission function via the user plane may be obtained from the AMF, or the network function managing UE capability information may be obtained from the UCMF (UE Capability Management Function). When performing a Registration operation with the AMF to provide the DCF with information regarding whether the terminal supports data transmission collected via the user plane, the terminal may transmit UE capability information regarding whether it supports the corresponding data transfer via UP function to the AMF.
[0132] When the DCF determines terminal data transmission, it can assign a data collection binding ID or a data transfer binding ID based on a specific terminal and the data information collected by that terminal. The data collection / transfer binding ID can be expressed in various forms, such as a data collection / transfer association ID or context ID, index, reference ID, correlation ID, etc. The data collection / transfer binding ID can be assigned and managed according to the purpose for which the collected data is used (e.g., purpose information that can be defined based on use cases or machine learning model information) or the training server, which is the final destination for data transmission. Furthermore, in the case of the data collection / transfer binding ID, if the transmission method of the collected terminal data is determined to be data transfer via UP, it can be assigned, stored, and managed in correspondence with the corresponding UP connection information (e.g., connection or session information established on the user plane between the terminal and the DCF). Additionally, the data collection / transfer binding ID can be stored and managed in correspondence with a terminal identifier (e.g., SUPI or GPSI).According to one embodiment, the DCF can generate UE data collection / transfer context information for the purpose of managing data collection and transmission on a terminal basis, and store and manage data collection binding ID or data transfer binding ID, data collection purpose (e.g., use case, ML model information), data collection final destination information (e.g., OTT server, training server), selected data transfer method (e.g., data transfer via CP or data transfer via UP), data collection request execution information (e.g., data collection request time stamp), etc.
[0133] 6. When the DCF decides to perform the transmission of collected terminal data, it may transmit a message to the AMF comprising at least one of a terminal identifier, a collected data transmission request indicator, a UP connection request indication (which may be included if the DCF decides to perform the transmission of collected terminal data through the UP), a DCF identifier, DCF user plane information (which may include at least one of address information required to establish a UP connection with the DCF, such as an FQDN or IP address), a DNN, an S-NSSAI, a data collection / transfer binding ID, and security information required for security regarding the UP connection between the DCF and the terminal (such as security protocol information). According to one embodiment, the DCF may call the Namf_comm_N1N2Transfer service to transmit the message to the AMF.
[0134] 7. The AMF may receive a request for data transfer from a DCF and generate and manage terminal data transfer information according to the method of the request for data transfer from the DCF. For example, if the DCF determines a data transfer via UP and the AMF receives a request for data transfer from the DCF and DCF UP information, the AMF may store the information within the AMF. According to one embodiment, the AMF may not perform storage of the information in step 7, but may generate it after receiving an acknowledgment from the terminal that data transfer can be performed. The AMF may store and manage UP connection context information within the AMF. The UP connection context information may include at least one of DCF information (e.g., identifier and address information), UP connection ID, and data collection / transfer binding ID. Considering the information received from the DCF, the AMF may transmit a message (through the RAN) to the terminal to which the terminal that needs to perform data collection transmission is currently connected, the message including at least one of a data collection transmission request indicator, a UP connection request indication (e.g., may be included if the DCF decides to perform data collection transmission through the UP), DCF user plane information (e.g., may include at least one of address information required to establish a UP connection with the DCF, such as an FQDN or an IP address), a DNN, an S-NSSAI, a data collection / transfer binding ID, and security information required for security regarding the UP connection between the DCF and the terminal (e.g., security protocol information, etc.).When the AMF receives a data transmission request message from the DCF in step 6, depending on the connection status between the terminal and the AMF, it can perform paging to establish a NAS layer signaling connection with the terminal to secure connectivity with the terminal, and then transmit the above information to the terminal.
[0135] 8. The terminal may perform the following operations by considering the information within the message received through the AMF. When the terminal receives a UP connection request indication or DCF UP information, it may perform an operation to establish a UP connection to the DCF using the information included in the DCF UP information. Such operation may include the following.
[0136] - If the terminal receives DNN or S-NSSAI information, the terminal uses the received DNN / S-NSSAI information to create a new PDU session, or if a PDU session corresponding to the DNN / S-NSSAI has already been created, performs the operation of reusing the existing PDU session.
[0137] - If the DCF address information included in the DCF's UP information is an FQDN, the terminal may send a DNS query to a DNS server configured within the terminal to obtain an IP address for the DCF. The DNS server address may be the address of a DNS server configured or operated by the core network operator or the operator responsible for operating the DCF. The DNS server address information may be the DNS server address provided to the terminal during the process of creating a PDU session. Alternatively, the DNS server address may be configured as an EASDF (edge application server discovery function) address used in the core network and provided to the terminal.
[0138] - The terminal can transmit a UP connection message to the DCF to the DCF via a user plane path (through the created or selected PDU session) using the DCF address information included in the DCF UP information, after performing a creation or selection operation for a PDU session to transmit the UP connection message to the DCF. The UP connection message to the DCF may include information such as a data collection / transfer binding ID, a UE identifier, and information related to collected data (e.g., collected data metadata, size of collected data). The UP connection message to the DCF transmitted by the terminal may be transmitted as part of a specified protocol message (e.g., AI / ML data collection / transfer protocol) defined between the terminal and the DCF.
[0139] - Upon receiving a UP connection request message, the DCF may perform an authentication security procedure for the corresponding terminal and perform the following operations. The DCF may consider the information within the received UP connection request message, assign a UP connection ID to the UP connection established with the terminal, and manage it in correspondence with data collection / transfer binding ID information. According to one embodiment, multiple UP Connection IDs and data collection / transfer binding IDs may be assigned and used between a single terminal and the DCF. For example, if the terminal performs data collection and transmission for multiple use cases, a different data collection / transfer binding ID may be assigned and used for each use case. Additionally, multiple UP connection IDs may also be assigned and managed for each data set collected by the terminal or for each use case of the data collected by the terminal.
[0140] - After confirming that it can successfully execute the terminal's UP connection request, the DCF may send a response message to the UP connection request to the terminal notifying that a UP connection has been successfully established. The response message may include at least one of UP connection ID or data collection / transfer binding ID information. The DCF and the terminal may associate the established UP connection with the terminal / DCF using at least one of the UP connection ID or data collection / transfer binding ID information, and this information may be used to identify which data among the collected data the UP connection is intended to transmit (for example, it may be used to identify the established UP connection in association with which use case or data for training a machine learning model).
[0141] If the terminal transmits a PDU session creation request to the AMF during the operation of Step 8 above, the following operations may be performed. The AMF may determine from the terminal that the request is a PDU session creation request that can be used for data collection through one of the following methods.
[0142] - If the terminal provides the AMF with a data collection over UP support indication, the AMF can recognize that it is a request to create a PDU session that can be used for data collection.
[0143] - If AMF creates and manages DCF UP information received from DCF through the previous steps or contexts related to the use of user plane resources for data collection, it can determine that the PDU session request is for a session related to data collection.
[0144] - When the AMF receives a PDU session request for a specific DNN or S_NSSAI, it can determine, based on internal settings, that the PDU session for the corresponding DNN, S_NSSAI, and the terminal identifier requesting the PDU session creation can be used for data collection.
[0145] When the AMF receives a PDU session request for a specific DNN or S_NSSAI, it can receive subscription data regarding the corresponding DNN, S_NSSAI, and the terminal identifier requesting the PDU session creation through the UDM. For example, the AMF obtains data collection over UP supported / allowed information included in the SMF selection data within the UDM from the UDM, and through this information, it can determine whether the user plane is allowed or supported for the corresponding terminal, DNN, and S_NSSAI. Through the subscription data obtained from the UDM in this way, the AMF can determine that the requested PDU session creation can be used for data collection.
[0146] If the AMF determines through various methods as described above that the PDU session requested by the terminal can be used for data collection, the AMF can send a data collection over UP supported / allowed indication to the SMF.
[0147] 8-A. When the SMF receives a data collection over UP supported / allowed indication from the AMF, it can confirm that data collection over UP is permitted by considering the data collection over UP authorization information included in the session management subscription data received from the UDM.
[0148] When the SMF receives a data collection over UP supported / allowed indication from the AMF or receives information from the UDM indicating that data collection over UP is supported and allowed, it may transmit an indication of DC over UP allowed when requesting a session management policy from the PCF. According to one embodiment, when the SMF receives a data collection over UP supported / allowed indication from the AMF or receives information from the UDM indicating that data collection over UP is supported and allowed, it may perform a session management association procedure while transmitting at least one of an indication of DC over UP allowed, a data collection binding ID, DCF information, and DCF UP information to the PCF.
[0149] 8-B. When the PCF receives a session management association request or a session management policy request message from the SMF that includes an indication of DC over UP allowed, the PCF may provide at least one of Usage Monitoring Control related information for DC over UP and Policy control request trigger information to the SMF, taking into account the DCF information related to data collection. The SMF may set the usage monitoring control related information for DC over UP received from the PCF to the UPF located in the data collection path.
[0150] 9. When the terminal successfully completes the creation of a UP connection for data transfer with the DCF in the previous step, it may send an acknowledgment to UP connection established for data transfer message to the AMF. The message may include the result of creating a UP connection to transfer data collected by the terminal to the DCF via UP, a UP connection ID, or a data collection / transfer binding ID.
[0151] 10. The AMF may transmit an acknowledgment to UP connection established for data transfer message received from the terminal to the DCF. If the acknowledgment to UP connection established for data transfer message contains result information indicating that the terminal has successfully established a UP connection with the DCF, the AMF may store and manage UP connection context information within the AMF. The UP connection context information may include at least one of DCF information (e.g., identifier and address information), a UP connection ID, and a data collection / transfer binding ID.
[0152] 11. The terminal can transmit the collected data through a UP connection with the DCF successfully created in the previous step. When transmitting the collected data, the UP connection ID or the Data collection / transfer binding ID may be transmitted together.
[0153] When the PDU session creation and the UP connection creation between the terminal and the DCF are successfully performed through the preceding steps 8 to 10, the UPF, having received usage monitoring control related information for DC over UP from the SMF, can monitor the usage, transmission time, etc. of the traffic transmitted to the DCF. The UPF can determine the information to be monitored based on the usage monitoring control related information for DC over UP received from the SMF.
[0154] The UPF can transmit to the SMF the results of monitoring the wireless communication network user plane resources used for data transmission to the terminal's DCF. The SMF can report the monitoring results received from the UPF to the PCF by mapping them to at least one of the following information: a Data Collection binding ID, a Data Collection function identifier, or a monitoring key. The information reported by the SMF to the PCF may be determined based on policy control request / report trigger (PCRT) information related to data collection over UP received from the PCF, and may include, for example, information such as the occurrence of a Data Collection start / stop event.
[0155] 11-C. The UPF may transmit to the SMF the results of monitoring the wireless communication network user plane resources used for data transmission to the terminal's DCF. The SMF may report the monitoring results received from the UPF to the CHF (charging function) by mapping them to at least one of the following information: a Data Collection binding ID, a Data Collection function identifier, and a monitoring key. The information reported by the SMF to the CHF may include the monitoring results received from the UPF, at least one of the following information: a Data Collection binding ID, a Data Collection function identifier, a monitoring key, and a charging key, as well as user plane resource usage information (e.g., data volume used, data transmission / reception duration).
[0156] 12. The DCF can store and manage data to be used for training received from the terminal. The DCF can perform an operation to verify whether the received data is data collected in accordance with the data collection settings. The DCF can identify the machine learning model training server to which the data to be used for training transmitted by the terminal should be transmitted and transmit the collected data. This step may be transmitted along with the response message to the data collection request made by the machine learning model training server in Step 0. Additionally, the DCF can transmit information regarding Reporting Usage Monitoring information for the transmitted data to Training Server (e.g., ASP ID, Training Server provider ID, Data Collection Binding ID) to the CHF.
[0157] 13. After successfully performing machine learning training using the data collection requested from DCF, the machine learning model training server can perform the operation of setting the trained machine learning model on the terminal.
[0158] According to one embodiment of the present disclosure, an operator may designate and use a network slice or DNN for data collection. This may mean that a dedicated S-NSSAI or DNN for data collection is configured in the network. The operator may generate and transmit a UE Route Selection Policy (URSP) to a terminal through network functions within the core network to instruct the terminal to use a specific network slice or DNN to transmit collected data. According to one embodiment of the present disclosure, the following operations may be performed to generate a URSP for data collection.
[0159] (1) service description (e.g., information that can be used to create / modify a URSP related to terminal data collection within the UDR, which may include at least one of the following: information that can identify a terminal data collection service, e.g., a combination of DNN or S-NSSAI, an AF identifier, a data collection request training server identifier, a training server provider identifier, an AF-Service-Identifier, an External Application Identifier, or a DCF identifier), service parameters (e.g., information that can be set on the terminal as information about a specific service or a specific data collection service; information necessary to support a service that can be identified by the service description), application traffic descriptor (e.g., information that can be used to set a URSP traffic descriptor, which may include FQDN, a domain descriptor, an application ID, an OS App ID, a traffic category, etc.; DCF address information may be set as the traffic descriptor), route selection parameter (e.g., may include DNN, S-NSSAI information), spatial validity condition, temporal validity condition, target UE, a group of UEs or PLMN ID(s), or Subscription to events (e.g. For example, at least one piece of information (such as subscriptions for UE policy-related settings or delivery-related notifications) may be stored.The UDR can receive information that can be used for generating and modifying such UDRPs from the DCF, configured by the OAM, or provided via the NEF when the training server acts as the AF. When the DCF provides information to the UDR that can be used for generating and modifying UDRPs, information such as traffic descriptors, route selection parameters, or terminal identifiers required to generate the UDRP, along with data collection binding IDs, DCF identifiers, and training server provider IDs, may be stored together within the UDR. Additionally, the DCF may provide information within the traffic descriptor to the UDR by configuring it as the DCF's address information (e.g., IP address or FQDN information).
[0160] (2) Information that can be used to create / modify URSPs related to terminal data collection stored in the UDR may be transmitted to the PCF. According to one embodiment, the PCF may receive a UE policy association request operation from the AMF. The UE policy association request transmitted by the PCF to the AMF may include at least one of the following: information on whether the terminal can perform data collection using the user plane (e.g., data collection over UP supported / allowed indication), information on whether the terminal supports data collection using the user plane, or information on whether the terminal is allowed to perform data collection using the user plane. The PCF may decide to provide a URSP related to the use of the user plane for data collection to the terminal by considering at least one of the information received from the AMF, internal settings, or subscription data. According to one embodiment, the AMF may determine whether the terminal can perform data collection and transmission using the user plane by considering subscription data that can be verified during the linkage with the DCF for data collection over UP, linkage with the terminal, or registration procedure. To this end, the terminal may transmit information to the AMF regarding whether it supports a function to perform data collection and transmission using the user plane (for example, it may be transmitted to the AMF by including it as one of the terminal support function information within a registration request message).When the AMF sends a request message to the PCF to create or modify a UE policy association, taking into account whether the terminal supports data collection and transmission-related functions received from the terminal, information on whether the terminal in the subscription data is allowed to collect / transmit data using the user plane, and the results of the interaction with the DCF, it may provide information on whether data collection through the user plane of the terminal is allowed / supported.
[0161] (3) PCF can generate a URSP using information that can be obtained from UDR (information that can be used to generate the URSP described above). PCF can provide the generated URSP to AMF. AMF can transmit the URSP received from PCF to a terminal. The terminal can perform data collection / transmission through the user plane using the URSP received through AMF. According to one embodiment, the URSP generated for data collection may include at least one of the following: Application descriptors for a client application within the terminal performing data collection / transmission (e.g., OS ID and OS App ID: OS specific Application Identifier), DNN or S-NSSAI information corresponding to a PDU session used to transmit the collected data, a traffic descriptor capable of identifying traffic transmitting the collected data, or a traffic category (data collection transfer category). The terminal may determine the DNN or S-NSSAI included in the PDU session creation request to transmit collected data based on the URSP received through the AMF, or determine whether a PDU session corresponding to the DNN / S-NSSAI information already included in the URSP has been created, and decide to use the PDU session to transmit the collected data.
[0162] FIG. 4 illustrates the configuration of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0163] A terminal according to one embodiment of the present disclosure may include a processor (430) that controls the overall operation of the terminal, a transceiver (410) including a transmitter and a receiver, and a memory (420). Of course, it is not limited to the examples described above, and the terminal may include more configurations than those shown in FIG. 4, or fewer configurations.
[0164] According to one embodiment of the present disclosure, the transceiver (410) may transmit and receive signals with network entities, a base station, or another terminal. The signals transmitted and received with the network entities, a base station, or another terminal may include control information and data. Additionally, the transceiver (410) may receive a signal through a wireless channel and output it to a processor (430), and transmit the signal output from the processor (430) through a wireless channel.
[0165] According to one embodiment of the present disclosure, the processor (430) can control the terminal to perform any one of the above-described embodiments. Meanwhile, the processor (430), memory (420), and transceiver (410) are not necessarily implemented as separate modules, and can be implemented as a single component in the form of a single chip. Also, the processor (430) and the transceiver (410) can be electrically connected. Additionally, the processor (430) may include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.
[0166] According to one embodiment of the present disclosure, the memory (420) may store data such as a basic program, an application program, and setting information for the operation of the terminal. In particular, the memory (420) provides the stored data upon the request of the processor (430). The memory (420) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, a CD-ROM, and a DVD. Additionally, the memory (420) may be a plurality of. Furthermore, the processor (430) may perform the aforementioned embodiments based on a program for performing the aforementioned embodiments of the present disclosure stored in the memory (420).
[0167] FIG. 5 illustrates the configuration of a base station in a wireless communication system according to one embodiment of the present disclosure.
[0168] The base station of FIG. 5 may refer to a RAN node or BS as described in the aforementioned embodiments.
[0169] A base station according to one embodiment of the present disclosure may include a processor (530) that controls the overall operation of the base station, a transceiver (510) including a transmitter and a receiver, and a memory (520). Of course, it is not limited to the above examples, and the base station may include more or fewer configurations than the configuration shown in FIG. 5.
[0170] According to one embodiment of the present disclosure, the transceiver (510) can transmit and receive signals with at least one of a terminal, another base station, or a network entity. The signals transmitted and received may include at least one of control information and data.
[0171] According to one embodiment of the present disclosure, the processor (530) can generally control the operation of the base station to perform any one of the above-described embodiments. Meanwhile, the processor (530), the transceiver (510), and the memory (520) are not necessarily implemented as separate modules, and can be implemented as a single component in the form of a single chip. Furthermore, the processor (530) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (510) may include at least one communication interface for transmitting and receiving signals via wired / wireless to a terminal, another base station, or a network entity.
[0172] According to one embodiment of the present disclosure, the memory (520) may store data such as a basic program, an application program, and configuration information for the operation of the base station. Additionally, the memory (520) provides the stored data upon request from the processor (530). The memory (520) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, a CD-ROM, and a DVD. Additionally, there may be multiple memory (520). Additionally, the processor (530) may perform at least one of the aforementioned embodiments based on a program for performing an operation according to at least one of the aforementioned embodiments of the present disclosure stored in the memory (520).
[0173] FIG. 6 illustrates the configuration of a network entity in a wireless communication system according to one embodiment of the present disclosure.
[0174] A network entity according to one embodiment of the present disclosure may include a processor (630) that controls the overall operation of the network entity, a transceiver (610) including a transmitter and a receiver, and a memory (620). Of course, it is not limited to the examples described above, and the network entity may include more or fewer configurations than the configuration shown in FIG. 6.
[0175] According to one embodiment of the present disclosure, the transceiver (610) may transmit and receive a signal with at least one of other network entities, a base station, or a terminal. The signal transmitted and received with at least one of other network entities, a base station, or a terminal may include control information and data.
[0176] According to one embodiment of the present disclosure, the processor (630) can control a network entity to perform any one of the above-described embodiments. Meanwhile, the processor (630), memory (620), and transceiver (610) are not necessarily implemented as separate modules, but can be implemented as a single component in the form of a single chip. Also, the processor (630) and the transceiver (610) can be electrically connected. Additionally, the processor (630) may include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.
[0177] According to one embodiment of the present disclosure, the memory (620) may store data such as a basic program, an application program, and configuration information for the operation of a network entity. In particular, the memory (620) provides the stored data upon request by the processor (630). The memory (620) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, a CD-ROM, and a DVD. Additionally, the memory (620) may be a plurality of. Furthermore, the processor (630) may perform the aforementioned embodiments based on a program for performing the aforementioned embodiments of the present disclosure stored in the memory (620).
[0178] It should be noted that the aforementioned configuration diagrams, exemplary diagrams of control / data signal transmission and reception methods, and exemplary diagrams of operation procedures are not intended to limit the scope of the embodiments of the present disclosure. That is, all of the aforementioned components, entities, or steps of operation should not be interpreted as essential components for implementing the disclosure, and may be implemented to the extent that the essence of the disclosure is not compromised even if only some components are included.
[0179] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading the program code stored in the memory device by a processor or a CPU (Central Processing Unit) and executing it.
[0180] The entities or various components of terminal devices and modules described in this disclosure may be operated using hardware circuits, such as, for example, complementary metal oxide semiconductor-based logic circuits, firmware, software, and / or a combination of hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.
[0181] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0182] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the claims or embodiments described in the specification of this disclosure.
[0183] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in a memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0184] Additionally, the program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, LAN (local area network), WAN (wide area network), or SAN (storage area network), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
[0185] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.
[0186] Meanwhile, the embodiments disclosed in this specification and drawings described above are merely specific examples provided to facilitate the explanation and understanding of the content of the invention and are not intended to limit the scope of the invention. Accordingly, the scope of the invention should be interpreted to include all modifications or variations derived based on the technical concept of the invention, in addition to the embodiments disclosed herein.
[0187] The electronic device for implementing, operating, and performing the various embodiments of the present disclosure may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of the present disclosure is not limited to the aforementioned devices.
[0188] The various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of such embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more items unless the relevant context clearly indicates otherwise. In the present disclosure, each of the phrases such as “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “at least one of A, B, or C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order). Where any (e.g., first) component is referred to as “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicationly,” it means that the component may be connected to the other component directly (e.g., via a wire), wirelessly, or through a third component.
[0189] The term “module” as used in various embodiments of the present disclosure may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally or a minimum unit of a component or part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).
[0190] Various embodiments of the present disclosure may be implemented as software (e.g., a program) comprising one or more instructions stored in a storage medium (e.g., internal memory or external memory) readable by a machine (e.g., an electronic device). For example, a processor (e.g., a processor) of the machine (e.g., an electronic device) may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to at least one called instruction. One or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, "non-transitory" simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.
[0191] According to one embodiment, the method according to various embodiments of the present disclosure may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.
[0192] According to various embodiments, each component (e.g., module or program) of the described components may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the aforementioned components or operations may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as they were performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically; one or more of the operations may be executed in a different order; may be omitted; or one or more other operations may be added.
Claims
1. A method performed by a terminal of a wireless communication system, A step of transmitting a first message containing information about the data collection result to the above DCF entity; A step of receiving a second message from an AMF (access and mobility management function) entity, the message including identification information related to data collection based on information regarding the data collection result; and A method comprising the step of transmitting a third message, including collected data and identification information related to the data collection, to the above DCF entity via a UP (user plane) connection.
2. In paragraph 1, the above method is: A method further comprising the step of creating the DCF entity and the UP connection based on identification information related to the above data collection.
3. In Paragraph 1, A method in which the identification information related to the above data collection includes at least one of a data collection binding ID (identifier) or identification information of the terminal related to the data collection binding ID.
4. In Paragraph 1, A method in which the above-mentioned collected data is data for AI (artificial intelligence) / ML (machine learning).
5. A method performed by a DCF (data collection function) entity of a wireless communication system, A step of storing usage data related to data collection through the user plane (UP) in a UDR (unified data repository) entity; A step of receiving a first message from the terminal containing information about the results of data collection; A step of transmitting a second message to an AMF (access and mobility management function) entity, the message including identification information related to data collection based on information regarding the data collection result; and A method comprising the step of receiving, via a UP connection, a third message including collected data and identification information related to the collection of said data from the above terminal.
6. In Paragraph 5, A method in which the above UP connection is generated based on identification information related to the above data collection.
7. In Paragraph 5, A method in which the identification information related to the above data collection includes at least one of a data collection binding ID (identifier) or identification information of the terminal related to the data collection binding ID.
8. In Paragraph 5, A method in which the above-mentioned collected data is data for AI (artificial intelligence) / ML (machine learning).
9. Regarding the terminal: At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the terminal: A step of transmitting a first message containing information about the data collection result to the above DCF entity; A step of receiving a second message from an AMF (access and mobility management function) entity, the message including identification information related to data collection based on information regarding the data collection result; and A terminal comprising the step of transmitting, to the above DCF entity, a third message including collected data and identification information related to the data collection through a UP (user plane) connection.
10. In paragraph 9, the above commands are the terminal: A terminal further comprising the step of creating the DCF entity and the UP connection based on identification information related to the above data collection.
11. In Paragraph 9, A terminal comprising at least one of the identification information related to the above data collection, the data collection binding ID (identifier) or the identification information of the terminal related to the data collection binding ID.
12. In Paragraph 9, A terminal whose collected data is data for AI (artificial intelligence) / ML (machine learning).
13. For DCF (data collection function) entities, At least one processor; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the DCF entity: A step of storing usage data related to data collection through the user plane (UP) in a UDR (unified data repository) entity; A step of receiving a first message from the terminal containing information about the results of data collection; A step of transmitting a second message to an AMF (access and mobility management function) entity, the message including identification information related to data collection based on information regarding the data collection result; and A DCF entity comprising the step of receiving, via a UP connection, a third message including collected data and identification information related to the data collection from the terminal.
14. In Paragraph 13, The above UP connection is a DCF entity that is created based on identification information related to the above data collection.
15. In Paragraph 13, The identification information related to the above data collection includes at least one of a data collection binding ID (identifier) or identification information of the terminal related to the data collection binding ID, and The above collected data is a DCF entity that is data for AI (artificial intelligence) / ML (machine learning).
