KR20240111963A - Method and apparatus for handlinginformation for ai/ml applications in wireless communication system - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. According to one embodiment of the present disclosure, a method for handling information related to AI/ML services by AMF in a wireless communication system is provided. The method includes receiving a registration request message including a list of requested AI/ML operation types from the UE; Identifying at least one operating condition for each AI/ML operation type included in the list of AI/ML operation types allowed for the UE and the list of AI/ML operation types allowed for the UE; Based on the list of requested AI/ML operation types, the list of AI/ML operation types allowed for the UE, and the at least one operating condition, the UE is included in the list of requested AI/ML operation types. determining whether it is permissible to use at least one AI/ML operation type; and transmitting a registration rejection message to the UE when determining that the UE is not permitted to use at least one AI/ML operation type included in the list of requested AI/ML operation types.

Description

Method and apparatus for handling information for AI/ML applications in a wireless communication system {METHOD AND APPARATUS FOR HANDLINGINFORMATION FOR AI/ML APPLICATIONS IN WIRELESS COMMUNICATION SYSTEM}

This disclosure relates to a method and apparatus for handling information for artificial intelligence/machine learning (AI/ML) applications in a wireless communication system.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss and increase radio wave transmission distance in ultra-high frequency bands. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

In addition, IAB (IAB) provides a node for expanding the network service area by integrating intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, and wireless backhaul links and access links. Integrated Access and Backhaul, Mobility Enhancement including Conditional Handover and DAPS (Dual Active Protocol Stack) handover, and 2-step Random Access (2-step RACH for simplification of random access procedures) Standardization in the field of wireless interface architecture/protocol for technologies such as NR) is also in progress, and 5G baseline for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technology Standardization in the field of system architecture/services for architecture (e.g., Service based Architecture, Service based Interface) and Mobile Edge Computing (MEC), which provides services based on the location of the terminal, is also in progress.

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional multiple input/output (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

5GS (5G system), a network that has recently been commercialized, and LTE (long-term evolution) and LTE-A (LTE-advanced) systems, which are networks currently providing mobile communication services, are all mobile devices that provide packet-based services. It is a communication system. This 5GS is being developed to support interworking with the Evolved Packet System (EPS) based on LTE and LTE-A. In this disclosure, the 5GS may be referred to as a 5G system. In the 5G system, the 5G core (5GC) network can provide UE Policy to the terminal.

In the 5G system, the connection between servers and terminals for AI/ML services can be supported, and the core network can provide auxiliary information necessary for AI/ML application operation to the terminal and server, respectively. For AI/ML services, the necessary network QoS and operating conditions may vary depending on the AI/ML model transfer method and data transmission method, and accordingly, the auxiliary information required for AI/ML application operation for the terminal and server may also vary. Therefore, the 5G core network may need a method to determine the operation type of the AI/ML application executed by the user and the type of information that terminal users and server operators can receive from the 5G core network.

Accordingly, the present disclosure provides a method and device related to providing network information for AI/ML applications to terminals and servers in a 5G system.

According to an embodiment of the present disclosure, a method for handling information related to an artificial intelligence/machine learning (AI/ML) service by an access and mobility management function (AMF) in a wireless communication system is provided. The method includes receiving a registration request message including a list of requested AI/ML operation types from a user equipment (UE); Identifying at least one operating condition for each AI/ML operation type included in the list of AI/ML operation types allowed for the UE and the list of AI/ML operation types allowed for the UE; Based on the list of requested AI/ML operation types, the list of AI/ML operation types allowed for the UE, and the at least one operating condition, the UE is included in the list of requested AI/ML operation types. determining whether it is permissible to use at least one AI/ML operation type; and transmitting a registration rejection message to the UE when determining that the UE is not permitted to use at least one AI/ML operation type included in the list of requested AI/ML operation types.

According to an embodiment of the present disclosure, a method for handling information related to an artificial intelligence/machine learning (AI/ML) service by a session management function (SMF) in a wireless communication system is provided. The method includes, from an access and mobility management function (AMF), an AI/ML operation type of an AI/ML application installed on a user equipment (UE), at least one operation condition related to at least one AI/ML operation type, and Receiving a protocol data unit (PDU) session creation request message including at least one of information indicating that the UE is located in an AI/ML service area related to an AI/ML operation type of the AI/ML application; Identifying subscriber information required for session management for the UE - Subscriber information required for session management for the UE includes a list of AI/ML operation types allowed for the UE and AI/ML operations allowed for the UE. Contains at least one of at least one operation condition for each AI/ML operation type included in the list of types -; AI/ML operation type of the AI/ML application, at least one operation condition related to the at least one AI/ML operation type, an AI/ML service area where the UE is associated with the AI/ML operation type of the AI/ML application determining whether the AI/ML application is operable in a requested PDU session based on at least one of information indicating that the AI/ML application is located within the UE and subscriber information required for session management for the UE; And when it is determined that the AI/ML application is not operable in the requested PDU session, transmitting a PDU session establishment rejection message to the AMF.

According to an embodiment of the present disclosure, a method for handling information related to an artificial intelligence/machine learning (AI/ML) service by a network exposure function (NEF) in a wireless communication system is provided. The method includes receiving a message from an application function (AF) to request authentication of a type of AI/ML auxiliary information for a service of an AI/ML application executed in the UE; Identifying subscriber information related to the AI/ML auxiliary information; Identifying allowed AI/ML auxiliary information based on the identified subscriber information; And transmitting a message containing a list of the identified allowed AI/ML auxiliary information to the AF.

According to one embodiment of the present disclosure, an apparatus for access and mobility management function (AMF) in a wireless communication network is provided. The device includes a transceiver; and at least one processor connected to the transceiver. The at least one processor receives a registration request message including a list of AI/ML operation types requested from a user equipment (UE), a list of AI/ML operation types allowed for the UE and the UE. Identifying at least one operating condition for each AI/ML operation type included in the list of AI/ML operation types allowed for the UE, the list of requested AI/ML operation types, and the AI/ML operation type allowed for the UE. Based on the list of ML operation types and the at least one operating condition, determine whether the UE is permitted to use at least one AI/ML operation type included in the list of requested AI/ML operation types, and , and when the UE determines that it is not permitted to use at least one AI/ML operation type included in the list of requested AI/ML operation types, send a registration rejection message to the UE.

According to one embodiment of the present disclosure, an apparatus for session management function (SMF) in a wireless communication network is disclosed. The device includes a transceiver; and at least one processor connected to the transceiver. The at least one processor receives, from an access and mobility management function (AMF), an AI/ML operation type of an AI/ML application installed on a user equipment (UE), and at least one operation type related to at least one AI/ML operation type. Receiving a protocol data unit (PDU) session creation request message containing at least one of operating conditions and information indicating that the UE is located in an AI/ML service area related to an AI/ML operation type of the AI/ML application, Identifying subscriber information required for session management for the UE, and the subscriber information required for session management for the UE includes a list of AI/ML operation types allowed for the UE and AI/ML operation types allowed for the UE. Contains at least one of at least one operation condition for each AI/ML operation type included in the list of -, AI/ML operation type of the AI/ML application, at least one related to the at least one AI/ML operation type Based on at least one of an operating condition, information indicating that the UE is located in an AI/ML service area related to an AI/ML operation type of the AI/ML application, and subscriber information required for session management for the UE. , determine whether the AI/ML application is operable in the requested PDU session, and when determining that the AI/ML application is not operable in the requested PDU session, send a PDU session establishment rejection message to the AMF. It is composed.

According to one embodiment of the present disclosure, an apparatus for network exposure function (NEF) in a wireless communication network is provided. The device includes a transceiver; and at least one processor connected to the transceiver. The at least one processor receives a message from an application function (AF) to request authentication of the type of AI/ML auxiliary information for the service of the AI/ML application executed in the UE, and sends a message related to the AI/ML auxiliary information. identify subscriber information, identify allowed AI/ML auxiliary information based on the identified subscriber information, and transmit a message containing a list of the identified allowed AI/ML auxiliary information to the AF. .

Figure 1 shows the network structure and interface of a 5G system, according to an embodiment of the present disclosure.
Figure 2 shows the network structure and interface of a 5G system, according to an embodiment of the present disclosure.
Figure 3 shows the network structure and interface of a 5G system, according to an embodiment of the present disclosure.
4A and 4B show the network structure and interface of a 5G system, according to an embodiment of the present disclosure.
Figures 5A, 5B, and 5C are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure.
6A, 6B, and 6C are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure.
7A, 7B, and 7C are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure.
8A and 8B are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure.
Figure 9 is a block diagram of a device according to an embodiment of the present disclosure.

In describing the embodiments in this specification, description of technical content that is well known in the technical field to which the present invention belongs and that is not directly related to the present invention will be omitted. This is to convey the gist of the present invention more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. The present embodiments are merely provided to ensure that the disclosure of the present invention is complete and to provide common knowledge in the technical field to which the present invention pertains. It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory The instructions stored in may also produce manufactured items containing instruction means that perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA or ASIC, and the '~unit' performs certain roles. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, 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 may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. At this time, it should be noted that the same components in the attached drawings are indicated by the same symbols whenever possible. In addition, it should be noted that the drawings of the present invention attached below are provided to aid understanding of the present invention, and the present invention is not limited to the form or arrangement illustrated in the drawings of the present invention. Additionally, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted. It should be noted that in the following description, only the parts necessary to understand the operation according to various embodiments of the present invention will be described, and the description of other parts will be omitted so as not to confuse the gist of the present invention. In addition, the present disclosure describes various embodiments using terms used in some communication standards (eg, 3rd Generation Partnership Project (3GPP)), but this is only an example for explanation. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

In the present disclosure, “A/B”, “A and/or B”, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, Phrases such as “at least one of A, B, and C” and “at least one of A, B, or C” each refer to any one of the items listed together in that phrase, or all possible combinations thereof. It can be included. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and may refer to that component in other respects, such as importance or order) is not limited.

In the present disclosure, the network technology may refer to standards defined by the ITU (international telecommunication union) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and are included in the network structure of FIG. 1, which will be described later. Components may refer to physical entities, software that performs individual functions, or hardware combined with software. In the drawings, reference symbols shown as Nx, such as N1, N2, N3,..., indicate known interfaces between NFs in the 5G core network (CN).

1 is a diagram showing the network structure and interface of a 5G system according to an embodiment of the present disclosure.

A network entity included in the network structure of the 5G system in FIG. 1 may include a network function (NF) depending on system implementation.

Referring to FIG. 1, the network structure of the 5G system may include various network entities. As an example, the 5G system includes an authentication server function (AUSF) 108, an access and mobility management function (AMF) 103, and a session management function (SMF). ) (105), policy control function (PCF) (106), application function (AF) (107), unified data management (UDM) (109), data network (DN) (110), network exposure function (NEF) (113), network slicing selection function (NSSF) (114). Edge application service domain repository (EDR) 113, edge application server (EAS, not shown), EAS discovery function (EASDF, not shown), user plane function ( user plane function (UPF) 104, (radio) access network (R)AN) 102, and user equipment (UE) (or terminal) 101. You can.

Each NF in the 5G system can support the following functions.

AUSF 108 may process and store data for authentication of UE 101.

The AMF 103 provides functions for UE-level access and mobility management, and each UE can be basically connected to one AMF. Specifically, the AMF 103 supports CN inter-node signaling for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), and non-access stratum (NAS) ) Endpoint of signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE accessibility ( reachability (including control and performance of paging retransmissions), mobility management control (subscriptions and policies), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (LI) (AMF) event and interface to the LI system), providing delivery of session management (SM) messages between the UE and SMF, transparent proxy for routing SM (session management) messages, access authentication (access) authentication, access authorization including roaming authorization checks, provision for delivery of SMS messages between the UE and short message service function (SMSF), security anchor function (SAF), and/or security context management. It can support functions such as SCM). Some or all of the functions of AMF 103 may be supported within a single instance of one AMF.

DN 110 may mean, for example, an operator service, Internet access, or a third party service. The DN 110 may transmit a downlink protocol data unit (PDU) to the UPF 104 or receive a PDU transmitted from the UE 101 from the UPF 104.

The PCF 106 may receive information about packet flow from an application server and provide the function of determining policies such as mobility management and session management. Specifically, PCF 106 supports a unified policy framework to govern network behavior, provides policy rules so that control plane function(s) (e.g., AMF, SMF, etc.) can enforce policy rules, and allows users to It can support functions such as implementing a front end to access relevant subscription information for policy decisions within a user data repository (UDR).

The SMF 105 provides a session management function, and when the UE 101 has multiple sessions, each session can be managed by a different SMF. Specifically, SMF 105 performs session management (e.g., session establishment, modification, and termination, including maintaining tunnels between UPF 104 and (R)AN 102 nodes), UE IP address allocation, and management (optionally including authentication), selection and control of user plane (UP) functions, establishment of traffic steering to route traffic to appropriate destinations in UPF 104, and policy control functions. Termination of interfaces, enforcement of policy and control portion of quality of service (QoS), lawful interception (LI) (for SM events and interfaces to LI systems), termination of SM portion of NAS messages, downlink data notification. notification), AN (access network) initiator of specific SM information (delivered to (R)AN (102) via N2 via AMF (103)), Session and Service Continuity (SSC) mode It can support functions such as decision making and roaming functions. Some or all of the functions of SMF 105 may be supported within a single instance of one SMF.

The UDM 109 may store user subscription data, policy data, etc. UDM 109 may include two parts: an application front end (FE) (not shown) and a user data repository (UDR) (not shown).

The front end (FE) (not shown) may include a UDM FE in charge of location management, subscription management, and credential processing, and a PCF in charge of policy control. UDR can store data required for functions provided by UDM-FE and policy profiles required by PCF. Data stored within the UDR may include user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. UDM-FE accesses subscription information stored in UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, and SMS management. You can.

The UPF (104) delivers the downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102) and receives it from the UE (101) via the (R)AN (102). One uplink PDU can be delivered to the DN 110. Specifically, the UPF 104 is an anchor point for intra/inter RAT mobility, an external PDU session point for interconnect to a data network, packet routing and forwarding, and packet inspection ( User plane portion of inspection and policy rule enforcement, lawful intercept, traffic usage reporting, and uplink classifier to support routing of traffic flows to the data network, multi-homed Branching points to support PDU sessions, QoS handling for the user plane (e.g. packet filtering, gating, uplink/downlink rate enforcement), uplink traffic verification (service data) It can support functions such as flow (service data flow (SDF) mapping between SDF and QoS flow), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering function. Some or all of the functions of UPF 104 may be supported within a single instance of one UPF.

AF 107 supports 3GPP for service provision (e.g., supporting functions such as application influence on traffic routing, access to network capability exposure, and interaction with policy framework for policy control). It can interoperate with the core network.

(R)AN 102 supports both evolved E-UTRA (evolved E-UTRA), which is an evolved version of 4G radio access technology, and new radio (NR) (e.g., gNB). A general term for a new wireless access network.

The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic provision of resources to the UE in uplink/downlink). dynamic allocation of resources (i.e. scheduling), internet protocol (IP) header compression, encryption and integrity protection of user data streams, routing to AMF is not determined from the information provided to the UE. In this case, selection of AMF upon attachment of the UE, user plane data routing to UPF(s), control plane information routing to AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from AMF), system Scheduling and transmission of broadcast information (from AMF or operating and maintenance (O&M)), establishment of measurements and measurement reporting for mobility and scheduling, transport level packet marking in the uplink, Session management, support of network slicing, QoS flow management and data mapping to radio bearers, support of UE in inactive mode, distribution function of NAS messages, NAS node selection function, radio access network sharing, dual connectivity ( It can support functions such as dual connectivity and tight interworking between NR and E-UTRA.

UE 101 may refer to a user device. A user device may be referred to by terms such as terminal, mobile equipment (ME), mobile station (MS), etc. Additionally, the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, or a multimedia device, or it may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.

NEF 111 is provided by 3GPP network functions, e.g., 3rd party, internal exposure/re-exposure, application functions, edge computing. It can provide a means to safely expose services and capabilities for. NEF 111 may receive information (based on the exposed capability(s) of the other NF(s)) from other NF(s). NEF 111 may store received information as structured data using standardized interfaces to data storage network functions. The stored information can be re-exposed by the NEF 111 to other NF(s) and AF(s) and used for other purposes such as analysis.

NRF 115 may support service discovery functions. An NF discovery request can be received from an NF instance, and information on the discovered NF instance can be provided to the NF instance. Additionally, it can maintain available NF instances and the services they support.

Meanwhile, FIG. 1 illustrates a reference model for a case where the UE 101 accesses one DN 110 using one PDU session for convenience of explanation, but the present disclosure is not limited thereto.

UE 101 may access two (i.e., local and central) data networks simultaneously, for example, using multiple PDU sessions. At this time, two SMFs may be selected for different PDU sessions. However, each SMF may have the ability to control both the local UPF and the central UPF within the PDU session.

Additionally, UE 101 may simultaneously access, for example, two (ie, local and central) data networks provided within a single PDU session.

NSSF 114 may select a set of network slice instances serving UE 101. Additionally, the NSSF 114 may determine permitted network slice selection assistance information (NSSAI) and, if necessary, perform mapping on subscribed single-network slice selection assistance information (S-NSSAI). Additionally, the NSSF 114 may determine the configured NSSAI and, if necessary, perform mapping to the subscribed S-NSSAIs. Additionally, the NSSF 114 may determine the set of AMFs used to serve the UE, or, depending on settings, may query the NRF 115 to determine a list of candidate AMFs.

NRF 115 may support service discovery functions. An NF discovery request can be received from an NF instance, and information on the discovered NF instance can be provided to the NF instance. Additionally, it can maintain available NF instances and the services they support.

In the 3GPP system, the conceptual link connecting NFs in the 5G system is defined as a reference point. The following illustrates reference points included in the 5G system architecture represented in Figure 1.

- N1: Reference point between UE and AMF

- N2: Reference point between (R)AN and AMF

- N3: Reference point between (R)AN and UPF

- N4: Reference point between SMF and UPF

- N5: Reference point between PCF and AF

- N6: Reference point between UPF and data network

- N7: Reference point between SMF and PCF

- N8: Reference point between UDM and AMF

- N9: Reference point between two core UPFs

- N10: Reference point between UDM and SMF

- N11: Reference point between AMF and SMF

- N12: Reference point between AMF and AUSF

- N13: Reference point between UDM and authentication server function (AUSF)

- N14: Reference point between two AMFs

- N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios

In the following description, the terminal may refer to the UE 101, and the terms UE and terminal may be used interchangeably. In this case, unless the terminal is specifically defined additionally, it can be understood as the UE (101).

Figure 2 is a diagram showing the network structure and interface of a 5G system, according to an embodiment of the present disclosure. The Network Data Analytics Function (NWDAF) can collect data from any NF included in the core network. At this time, the NWDAF and the counterpart NF must belong to the same PLMN. An Nnf reference point can be used between NWDAF and any NF.

Figure 3 is a diagram showing the network structure and interface of a 5G system, according to an embodiment of the present disclosure. Any NF included in the core network can request network analysis information and an analytics logical function (AnLF) from NWDAF. The Nnwdaf reference point can be used between the request NF (Consumer NF) and NWDAF. Request NF and NWDAF consuming analysis information must belong to the same PLMN.

4A and 4B are diagrams showing the network structure and interface of a 5G system according to an embodiment of the present disclosure. FIGS. 4A and 4B include the system described in FIGS. 1 to 3, and the corresponding content may have been omitted from the description of FIGS. 4A and 4B.

Looking at FIGS. 4A and 4B, the UE may be composed of an Application Layer, Operating System, and Modem. UE can be connected to the core network, control plane, and user plane. For the control plane, the UE can be connected through the AMF and N1 interfaces through the RAN. In the case of the user plane, the UE can be connected to the UPF through the RAN, and the RAN and UPF can be connected through the N3 interface. UPF can be connected to the DN through the N6 interface.

Modem can operate in the Connection Processor. Modem may include NAS Controller, URSP Handler, Data Receiver/Transmitter, and PDU Session Handler. Modem's receiving unit can deliver data corresponding to NAS messages among the data received from the core network to the NAS Controller. The NAS Controller can write control plane data to be transmitted to the core network as a NAS message and provide it to the modem's transmitter. Among various types of NAS messages received from the core network, the NAS Controller can deliver the UE Policy (including URSP rule) and related information provided to the UE by the PCF to the URSP Handler. When the URSP Handler specifies a URSP rule for an application, the NAS Controller determines whether there is an existing PDU Session to which the URSP rule is applied. If so, data is transmitted/received through the PDU Session, and if not, data is sent/received through the PDU Session. You can perform the procedure to establish a new PDU Session. The NAS Controller can deliver the information necessary for PDU Session management to the PDU Session Handler among various types of NAS messages received from the core network. The URSP Handler stores the UE Policy (including URSP rules) and related information provided to the terminal by the PCF, or when the core network requests the UE Policy and related information stored by the terminal, it transmits it to the core network through the NAS Controller. can do. The URSP Handler receives information that allows the OS to directly or indirectly identify the application executed on top of the OS, and can specify one URSP rule for the application among one or more URSP rules received from the NAS Controller. The OS is information that can directly or indirectly identify the application and can use Application ID and/or AI/ML operation type. Data Receiver/Transmitter can transmit uplink data to the core network (transmitter) or receive downlink data from the core network (receiver). Data Receiver can deliver downlink data to PDU Session Handler. The Data Transmitter can transmit uplink data received from the PDU Session Handler to the core network.

Operating System can run on Application Processor. The OS may include an Application Data Router. When an application is executed and data traffic occurs, the Application Data Router can deliver the application's direct/indirect identification information (which may include Application ID and AI/ML operation type) to the URSP Handler. Additionally, the Application Data Router can provide the PDU Session Handler with data traffic to be transmitted through the user plane path of the PDU Session for the application.

The Application Layer may be located above the OS. Applications may exist in the Application Layer. When an application is executed and data traffic occurs, the application traffic can be transferred to the OS. Additionally, the Application ID may be provided to the Application Data Router so that traffic in question can be identified from which application the application traffic originates. There are various types of applications for AI/ML services in the 5G system, and can be typically classified according to the model transfer method. For example, depending on the model transfer method, you can specify the AI/ML operation type of the application as follows:

● Operation splitting type (hereinafter, Type#1 for convenience): AI/ML operation and/or AI/ML model can be divided into one or more parts depending on the AI/ML task to be performed by the terminal and the terminal's environment, and the terminal and Depending on the computing capabilities of network components (endpoints), some can be performed on the terminal and others can be performed on the network device. The AI/ML server can transmit part of the AI/ML model, not the entire AI/ML model, to the terminal, and in this case, the server can reduce the burden of data transmission. Even terminals that do not have sufficient computing capabilities for AI/ML data processing may be able to support the service.

● Model/data distribution and sharing type (hereinafter, Type#2 for convenience): This is a type that can adaptively select an AI/ML model depending on the function of the terminal. Because the size of the terminal's storage is limited, the terminal may not download all AI/ML models from the network at once. Therefore, after distributing the AI/ML model to network components (endpoints), the terminal adaptively selects the AI/ML model according to the AI/ML task to be performed and the terminal's environment and downloads it from the corresponding endpoints. The system can be configured to do so. Large amounts of AI/ML model data can be downloaded to the terminal. Since real-time is generally not important in model downloading, it may be possible to download large amounts of data at night when the network is not congested.

● Distributed/federated learning type (hereinafter referred to as Type#3 for convenience): A global model is learned from the cloud server, and the terminals download this global model and partially learn the local model, resulting in This corresponds to a type of updating the global model by aggregating on a cloud server using the 5G uplink channel. Large amounts of global model data may be downloaded to the terminal, and large amounts of upload data traffic may occur frequently from the terminal to the server.

An application that supports AI/ML services can provide the OS with the AI/ML operation type supported by the above-described application when transferring application traffic to the OS. For example, referring to Figures 4a and 4b, Application #1 has an AI/ML operation type value indicating "Operation splitting type", and Application #2 has an AI/ML operation type value indicating "Model/data distribution and sharing type". Application #3 can provide the ML operation type value and the AI/ML operation type value indicating "Distributed/federated learning type" to the OS.

Looking at Figures 4a and 4b, the AI/ML Application Server may be located in a trusted domain or an untrusted domain of the 5G core network. When located in the untrusted domain, the AF corresponding to the AI/ML Application Server can be considered a network device located outside the 5G core network and can communicate with other NFs in the core network through the NEF of the core network. When existing in a trusted domain, the AF corresponding to the AI/ML Application Server can be considered a network device that exists inside the 5G core network and can communicate with other NFs in the core network with or without NEF.

AF (AI/ML Application Server) can be composed of a data collector, AI/ML engine, and data network. AI/ML engine can perform model creation, transfer, and learning for AI/ML services. Data Collector can collect assistance information required for AI/ML operations from the 5G core network, and the collected information can be provided to the AI/ML engine. The Data Network can provide data of the operation results of the AI/ML engine to the terminal (Data Transmitter) or receive the results of the AI/ML operation of the terminal (Data Receiver).

Figures 5A, 5B, and 5C are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure. More specifically, Figures 5a, 5b, and 5c explain a method of authenticating the AI/ML operation type allowed to the UE during the registration procedure. FIGS. 5A, 5B, and 5C include the system described in FIGS. 1 to 4, and the corresponding content may have been omitted from the description of FIGS. 5A, 5B, and 5C.

501. The UE can determine the AI/ML operation type(s) supported by the AI/ML application(s) installed in the UE. When an AI/ML application is installed in the UE, the application can inform the Application Data Router of the AI/ML operation type it supports. The Application Data Router can provide this to the NAS Controller (which may or may not go through the URSP Handler).

502. The UE may transmit a Registration Request to the AMF. The UE may provide the list of AI/ML operation type(s) of the AI/ML application(s) installed in the UE recognized in step 501 to the AMF as a list of requested AIML operation types.

503. AMF can request subscriber information required for registration and mobility management of UE containing subscriber information related to AI/ML operation from UDM. AMF can use the Nudm_SDM_Get Request message and provide a subscription permanent identifier (SUPI) associated with the UE. If the AMF already stores subscriber information related to AI/ML operation for the UE, steps 503 to 506 may be omitted.

504. UDM may request subscriber information required for UE registration and mobility management from UDR. UDM can use the Nudr_DM_Query Request message and can provide SUPI.

505. UDR can provide UDM with subscriber information necessary for UE registration and mobility management, including subscriber information related to AI/ML operations. Subscriber information related to the AI/ML operation may include a list of at least one AIML operation type and at least one operation condition (list of allowed AIML operation types) allowed to the subscriber. Operation condition may include at least one of location and time. For example, for subscribers indicated by SUPI, operation splitting type and model/data distribution and sharing type may be included in the allowed AIML operation type. Each allowed AIML operation type may be provided with an operation condition. If, for the model/data distribution and sharing type of the two types, there is a condition that the service can be used only during a specific time period for a UE located in a specific tracking area, the location condition contains information about the allowed tracking area(s), time The condition may include an operation condition containing information about the start time and end time. UDR can use the Nudr_DM_Query Response message.

506. UDM can provide AMF with subscriber information necessary for UE registration and mobility management, including subscriber information related to AI/ML operations. UDM can use the Nudm_SDM_Get Response message.

507. The AMF may compare the requested AIML operation type list received from the UE in step 502 with the allowed AIML operation type list received from the UDM in step 506 to determine which type is allowed in the network among the types requested by the UE. After checking whether there are additional permission conditions, it can be determined whether operation is possible at the current location and/or current time of the UE.

508. If, as a result of the determination in step 507, any one of the operation types included in the requested AIML operation type list provided by the UE in step 502 is not included in the allowed AIML operation type list or does not satisfy the operation condition, the AMF performs Registration of the UE. You may refuse the request. The AMF may provide the UE with reasons for rejection: AIML service is not allowed, AIML service is not allowed in current location, or AIML service is not allowed at current time. If step 508 is executed, steps after step 508 of FIGS. 5A, 5B, and 5C may not be executed.

509. If the AMF determines that the UE is allowed to use the AIML service with the requested AIML operation type (at the current location and/or current time) as a result of the determination in step 507, AM considering the allowed AIML operation type and operation condition to the PCF You can request a policy. AMF can use the Npcf_AMPolicyControl_Create Request message and can provide the PCF with a list of allowed AIML operation types and operation conditions determined in step 507. AMF can provide location information of the UE if there are location-related conditions in the operation condition.

510. The PCF can determine the AM Policy for the AIML service based on the information received from the AMF in step 509. Additionally, the PCF can determine the Policy Control Request Trigger (PCRT) for AMF to monitor whether the AIML operation type and conditions are normally satisfied. PCRT for AMF may include at least one of Change of UE Presence in Presence Reporting Area, NWDAF Info change, and Change of allowed AIML operation type. Change of UE Presence in Presence Reporting Area is when the AMF reports this to the PCF when there is a change in information about whether the UE is located within the location area specified in the location condition during the operation condition, is not located, or is unknown. It corresponds to PCRT, which is required to be done. NWDAF Info change corresponds to a PCRT that causes AMF to report to PCF when information related to the relevant AIML application is collected from NWDAF and there is a change in the NWDAF information responsible for it. Change of allowed AIML operation type corresponds to PCRT that causes AMF to report to PCF when a change occurs in allowed AIML operation type or operation condition. For example, the AMF that has received this PCRT can request the UDM to notify it if a change in the allowed operation type or operation condition occurs in the subscriber information, and when it receives notification of the change from the UDM, the change occurs to the PCF. You can report that it was done.

511. The PCF may provide the AMF with the AM Policy for the AIML service determined in step 510 and the PCRT related to the AMF for the AIML service. PCF can use the Npcf_AMPolicyControl_Create Response message. AMF stores AM Policy information (which may include AM Policy, PCRT) received from PCF and can be applied to UE registration and mobility management.

512. AMF may accept the UE's registration request if all registration conditions, including registration conditions related to AIML operation type and condition subscriber information, are satisfied. AMF can transmit a Registration Accept message to the UE and provide a list of allowed AIML operations and operation conditions determined in step 507. After step 507, the AMF determines whether any of the operation types included in the requested AIML operation type list is not included in the allowed AIML operation type list according to information provided from other NFs, RANs, and/or UEs before step 512, or If the operation conditions are not met, the UE's registration request can be rejected. In this case, a reason for rejection such as step 508 may be provided.

513. The UE can store a list of allowed AIML operation types and operation conditions received from AMF, and if the conditions are met, it can request establishment of a PDU Session for AIML application. Referring to the description of Figures 4a and 4b, the NAS Controller provides the list of allowed AIML operation types and operation conditions received from AMF to the URSP Handler or OS (which may be the Application Data Router of the OS or another component of the OS). You can save it. When an AI/ML application is executed and application traffic occurs, the URSP Handler and/or OS determines whether the AI/ML operation type value provided by the application is included in the allowed AIML operation type list received from AMF. If it is included, it can be determined whether the operation condition is satisfied. If it is determined that the operation condition is satisfied, processing related to the PDU Session for the application can be performed.

514. If the AMF needs to monitor the UE's location information among the operation conditions received in step 507 and/or step 511, it may request the NG-RAN (e.g., base station) to report the UE's location information. For example, the AMF can transmit a Location Reporting Control Request message to the NG-RAN, and this message can provide information about the target area where the UE's location information must be monitored. For example, among the operation conditions included in the subscriber information received in step 506, the identifier of the Tracking Area(s) corresponding to the AIML service area or the AIML service area set in the AMF is selected as the area of interest (Area). of interest). The NG-RAN may report UE presence status (e.g., located, not located, unknown) or UE location information in the area of interest to the AMF. When providing UE location information, the UE location information may include Cell ID, TAI, PLMN ID, and country information. The reporting cycle, accuracy, etc. may be subject to AMF's requests.

515. If the AMF needs to monitor the UE's location information during the operation conditions received in step 507 and/or step 511, it may request NWDAF to collect and analyze the UE's mobility information. When requesting NWDAF to collect and analyze UE mobility information, AMF can use the Nnwdaf_AnalyticsInfo Request or Nnwdaf_AnalyticsSubscription_Subscribe message, with "UE mobility" as the Analytics ID value and UE ID or Internal Group as the Target of Analytics Reporting value. Area of interest can be provided through ID and Analytics Filter Information, and target period of information and analysis can be provided through Analytics Reporting Information. Area of Interest can provide information about the target area where the UE's mobility information must be monitored. For example, among the operation conditions included in the subscriber information received in step 506, the identifier of the Tracking Area(s) corresponding to the AIML service area or the AIML service area set in the AMF is selected as the area of interest (Area). of interest). NWDAF may collect UE mobility information within the area of interest from the network and perform analysis upon AMF's request, and may provide the collected information and/or analysis information to AMF. When NWDAF provides UE location information to AMF, the UE location information may include Cell ID, TAI, PLMN ID, and country information. NWDAF can use the Nnwdaf_AnalyticsInfo Response or Nnwdaf_AnalyticsSubscription_Notify message.

516. AMF can request a UE Policy from PCF considering the allowed AIML operation type and operation conditions. AMF can use the Npcf_UEPolicyControl_Create Request message and can provide the PCF with a list of allowed AIML operation types and operation conditions determined in step 507.

517. The PCF may request policy-related subscriber information from the UDR and/or the most recent UE Policy information transmitted to the UE. When requesting information from UDR, PCF can use the Nudr_DM_Query Request message, with "Policy Data" as the Data Set value and "UE context policy control data" as the Data Subset value (for requesting subscriber information related to policy). value), and/or "Policy Set Entry data" (value for requesting the most recent UE Policy information transmitted to the UE), and SUPI may be provided as the terminal identifier.

518. The UDR may provide the PCF with information requested in step 517. When providing information to the PCF, UDR can use the Nudr_DM_Query Response message and can provide policy-related subscriber information and/or the most recent UE Policy information transmitted to the UE.

519. The PCF may determine a UE Policy for AIML service based on the information received from the AMF in step 516 and the information received from the UDR in step 518. The UE Policy for AIML service may include at least one of a policy related to AI/ML model transition and a policy related to AI/ML data transition, each of which includes transmission frequency, transmission size, and transmission performance time (start It may include at least one of time, end time). The policy related to the AI/ML model transfer and the policy related to AI/ML data transfer may be included in the URSP rule. Additionally, the PCF can determine the Policy Control Request Trigger (PCRT) for AMF to monitor whether the AIML operation type and conditions are normally satisfied. PCRT for AMF may include at least one of Change of UE Presence in Presence Reporting Area, NWDAF Info change, and Change of allowed AIML operation type. Each may follow what is described in step 510.

520. The PCF may provide the AMF with the PCRT associated with the AMF for the AIML service determined in step 519. PCF can use the Npcf_UEPolicyControl_Create Response message. The AMF received from the PCF stores the PCRT received from the PCF and can be applied to the registration and mobility management of the UE.

521. The PCF may provide the AMF with a UE Policy Container containing the UE Policy for the AIML service determined in step 519. PCF can use the Namf_Communication_N1N2MessageTransfer message.

522. AMF may deliver the UE Policy Container received in step 521 to the UE.

523. The UE can store and process the UE Policy for the received AIML service. Referring to the description of FIGS. 4A and 4B, the NAS Controller can transmit the URSP rule to the URSP Handler. Additionally, when an AI/ML application is executed, the application provides an operation type to the Application Data Router, and the Application Data Router can deliver this to the URSP Handler. The URSP Handler can specify a URSP rule that matches the operation type provided by the application with the operation condition corresponding to the current UE location and/or current time. The URSP Handler can determine whether a PDU Session for the corresponding URSP rule already exists or whether a new PDU Session needs to be established, and depending on the judgment result, the NAS Controller can start the PDU Session Establishment procedure or the PDU Session Modification procedure. You can.

524. The UE may transmit the result of UE policy delivery (e.g., success or failure) to the AMF.

525. AMF can transmit information related to the result of UE Policy delivery to PCF.

526. The PCF includes the most recent UE Policy information (which may include the UE Policy for AIML service) transmitted to the UE received from the UDR in step 517 and the most recent UE Policy determined by the PCF and transmitted to the UE in step 519. By comparing information (which may include UE Policy for AIML service), UE Policy data can be stored or updated in UDR. PCF can use the Nudr_DM_Update Request message, with "Policy Data" as the Data Set value, "Policy Set Entry data" as the Data Subset value, and the most recent UE Policy information sent to the UE (UE Policy for AIML service). (can be included), SUPI can be provided as the terminal identifier. The most recent UE Policy information transmitted to the UE may consist of one or more PSI (Policy Set Identifiers) and a list of content (policy data).

527. UDR can respond to the PCF with the result of saving or updating UE Policy data and can use the Nudr_DM_Update Response message.

6A, 6B, and 6C are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure. More specifically, Figures 6a, 6b, and 6c explain a method of authenticating the AI/ML operation type allowed to the UE during the PDU Session Establishment procedure. FIGS. 6A, 6B, and 6C include the system described in FIGS. 1 to 5C, and the corresponding content may have been omitted from the description of FIGS. 6A, 6B, and 6C.

601. The UE can determine whether the executed AI/ML application satisfies the allowed operation type and operation condition received from the network in the registration procedure described in Figures 5a, 5b, and 5c, and a new PDU Session must be established for the application. You can decide whether to do it or not. For example, step 523 of FIG. 5C may be performed.

602. If the UE determines in step 601 that a new PDU Session needs to be established for the AI/ML application, it may transmit a PDU Session Establishment request to the AMF. In making this request, the UE may provide at least one of DNN for PDU Session, S-NSSAI, and AI/ML operation type of the corresponding AI/ML application.

603. In step 602, the AMF checks the list of allowed operation types and operation conditions stored by the AMF during the registration procedure described in the figure for the AI/ML operation type provided by the UE, and determines the current UE designation in the operation condition of the corresponding operation type. You can determine whether it is located within the AI/ML service area. For example, if the AMF stored the allowed operation type and operation condition in the UE's registration procedure that the model/data distribution and sharing type is allowed in the TA1 and TA2 areas, the AMF stores the allowed operation type and operation condition that the UE is currently located in TA1 or TA2. You can determine whether it exists or not. As described in steps 514 and 515 of FIG. 5B, the AMF may receive UE location information from NG-RAN or NWDAF, or other NF, or UE. At this time, the UE location information includes Cell ID and TAI. , PLMN ID, and country information may be included. AMF may reject the PDU Session Establishment request if the UE is not currently located within the AI/ML service area specified in the operation condition of the corresponding operation type or if the current time is not the time specified in the operation condition. The AMF may provide the UE with reasons for rejection: AIML service is not allowed, AIML service is not allowed in current location, or AIML service is not allowed at current time.

604. If the AMF determines that the UE is located within the AI/ML service area, it may request the SMF to establish a PDU session. In making this request, the AMF may use the Nsmf_PDUSession_CreateSMContext Request message, including the AIML operation type received in step 602, the operation condition provided by the UE or stored by the AMF, and whether the UE determined in step 603 is located in the AIML service area. It may include at least one of location information of the UE (e.g., located within the service area, not located, unknown).

605. SMF can request subscriber information needed for session management from UDM. AMF can use the Nudm_SDM_Get Request message, with SUPI, "Session Management Subscription data" as the value of the type of subscriber information requested, selected DNN (DNN requested by the UE, provided to AMF in step 602, and AMF in step 604 (Can be delivered to SMF), S-NSSAI of HPLMN (S-NSSAI of Home PLMN requested by UE, provided to AMF in step 602, AMF can be delivered to SMF in step 604), Serving PLMN ID, NID You can provide at least one. If the SMF already stores subscriber information necessary for session management, steps 605 to 608 may be omitted.

606. UDM can request subscriber information needed for session management from UDR. UDM can use the Nudr_DM_Query Request message, with SUPI, "Session Management Subscription data" as the value of the type of subscriber information requested, selected DNN (DNN requested by the UE, provided to AMF in step 602, and AMF in step 604 (Can be delivered to SMF), S-NSSAI of HPLMN (S-NSSAI of Home PLMN requested by UE, provided to AMF in step 602, AMF can be delivered to SMF in step 604), Serving PLMN ID, NID You can provide at least one.

607. UDR can provide UDM with subscriber information necessary for session management, including subscriber information related to AI/ML operations. Subscriber information related to the AI/ML operation may include a list of AIML operation types and operation conditions allowed to the subscriber (list of allowed AIML operation types), and the content described in step 505 of FIG. 5A may be applied. UDR can use the Nudr_DM_Query Response message.

608. UDM can provide SMF with subscriber information necessary for session management, including subscriber information related to AI/ML operations. UDM can use the Nudm_SDM_Get Response message.

609. The SMF compares the AIML operation type, operation condition, and/or whether the UE received from the AMF in step 604 and whether the UE is located in an AIML service area with the list of allowed AIML operation types and operation conditions received from the UDM in step 608, and determines whether the UE is located in the AIML service area. It can be determined whether operation is possible at the current location and/or current time. If it is determined that the AIML application of the requested PDU Session is operable at the UE's current location and/or current time, step 610 below may be omitted.

610. In step 609, if the SMF determines that the AIML application of the requested PDU Session is not operable in the UE's current location and/or current time, the SMF may reject the PDU Session Establishment request. The SMF may provide the AMF that the AIML service is not allowed, or the AIML service is not allowed in the current location, or the AIML service is not allowed at the current time, as the reason for rejection to the AMF, and the AMF may convey this to the UE.

611. If the SMF determines that the AIML application of the requested PDU Session is operable at the UE's current location and/or current time, the SMF may respond to the request in step 604 to the AMF. SMF can use the Nsmf_PDUSession_CreateSMContext Response message.

612. If the SMF determines that the AIML application of the requested PDU Session is operable at the UE's current location and/or current time, it may request an SM Policy considering the AIML operation type and operation condition from the PCF. The SMF can use the Npcf_SMPolicyControl_Create Request message and provide the PCF with at least one of the AIML operation type, operation condition, information about whether the UE is located within the AIML service area, and UE location information received from the AMF in step 604. .

613. The PCF may determine the SM Policy for the AIML service based on the information received from the SMF in step 612. Additionally, the PCF can determine the Policy Control Request Trigger (PCRT) for SMF to monitor whether the AIML operation type and conditions are normally satisfied. PCRT for SMF may include at least one of Change of UE Presence in Presence Reporting Area, NWDAF Info change, and Change of allowed AIML operation type. Change of UE Presence in Presence Reporting Area is when the SMF reports this to the PCF when there is a change in information about whether the UE is located within the location area specified in the location condition among the operation conditions, is not located, or is unknown. It corresponds to PCRT, which is required to be done. For example, the SMF that received this PCRT may report to the PCF that a change has occurred if the value of whether the UE is located in the AIML service area received from the AMF is different from the value previously received from the AMF. NWDAF Info change corresponds to a PCRT that causes the SMF to report to the PCF when information related to the relevant AIML application is collected from NWDAF and there is a change in the NWDAF information responsible for it. Change of allowed AIML operation type corresponds to PCRT that causes SMF to report to PCF when a change occurs in allowed AIML operation type or operation condition. For example, the SMF that received this PCRT may request the UDM to notify it if a change in the allowed operation type or operation condition occurs in the subscriber information, and when it receives notification of the change from the UDM, the change occurs to the PCF. You can report that it was done.

614. The PCF may provide the SMF with the SM Policy for the AIML service determined in step 613 and the PCRT associated with the SMF for the AIML service. PCF can use the Npcf_SMPolicyControl_Create Response message. SMF stores SM Policy information (which may include SM Policy and PCRT) received from PCF and can apply it to session management.

615. The SMF can request an N4 session from the UPF and perform procedures related to allocation of user plane resources (for example, this may include determination of CN N3 Tunnel Information).

616. UPF can perform procedures related to allocation of user plane resources and can respond to N4 session requests from SMF.

617. The SMF can accept the UE's PDU Session establishment request if it satisfies all PDU Session establishment conditions, including conditions related to AIML operation type and condition subscriber information. SMF can provide AMF with the information necessary for UE and RAN to complete PDU Session establishment. If the SMF does not satisfy the AIML operation type and condition based on information provided from other NFs, RANs, and/or UEs after step 609 but before step 617, the SMF may reject the UE's PDU Session establishment request. In this case, a reason for rejection such as step 610 may be provided. SMF can use the Namf_Communication_N1N2MessageTransfer message. AMF may provide a response message (eg, an acknowledgment response message) to the Namf_Communication_N1N2MessageTransfer message received from the SMF.

618. AMF can request an N2 PDU Session from RAN. AMF can provide the RAN with information related to access network resource allocation and NAS messages to be delivered to the UE.

619. The RAN may perform resource configuration for the access network between the UE and the RAN. The RAN may deliver a NAS message to the UE, and may include a PDU Session Accept message or a PDU Session Reject message provided by the SMF in step 617. The UE may provide the result of message reception to the RAN.

620. RAN can respond to the N2 PDU Session request to AMF. For example, it may include providing AN N3 Tunnel Information. After step 620, uplink data generated from the UE may be transmitted to the UPF through the RAN and N3 Tunnel.

621. The AMF may transfer the information received from the RAN to the SMF in step 620.

622. The SMF may transfer the information received in step 621 to the UPF.

623. UPF can respond to information transfer from SMF. For example, UPF can save AN N3 Tunnel Information and complete the setting of N3 Tunnel. After step 623, downlink data generated from the DN may be transmitted to the UE through the RAN and N3 Tunnel. At this time, the DN may be the Data Transmitter of the AI/ML Application Server described in FIGS. 4a and 4b.

624. SMF may respond to AMF.

625. If the SMF needs to monitor the UE's location information during AIML operation conditions, it can request NWDAF to collect and analyze the UE's mobility information. When requesting NWDAF to collect and analyze UE mobility information, SMF can use the Nnwdaf_AnalyticsInfo Request or Nnwdaf_AnalyticsSubscription_Subscribe message, with "UE mobility" as the Analytics ID value and UE ID or Internal Group as the Target of Analytics Reporting value. Area of interest can be provided through ID and Analytics Filter Information, and target period of information and analysis can be provided through Analytics Reporting Information. Area of Interest can provide information about the target area where the UE's mobility information must be monitored. For example, among the operation conditions received from AMF in step 604, included in the subscriber information received from UDM in step 608, or included in the SM Policy received in step 614, Tracking Area(s) corresponding to the AIML service area ) Alternatively, the identifier of the Tracking Area(s) corresponding to the AIML service area set in the SMF can be provided as part of the Area of Interest. NWDAF may collect UE mobility information within the area of interest from the network and perform analysis at the request of the SMF, and may provide the collected information and/or analysis information to the SMF. When NWDAF provides the UE's location information to the SMF, the UE's location information may include Cell ID, TAI, PLMN ID, and country information. NWDAF can use the Nnwdaf_AnalyticsInfo Response or Nnwdaf_AnalyticsSubscription_Notify message.

7A, 7B, and 7C are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure. More specifically, Figures 7a, 7b, and 7c explain a method of authenticating AI/ML assistance information allowed to AF during the AF's subscriber information access authentication procedure. FIGS. 7A, 7B, and 7C include the system described in FIGS. 1 to 6C, and the corresponding content may have been omitted from the description of FIGS. 7A, 7B, and 7C.

701. According to the procedures described in FIGS. 5A, 5B, and 5C, the 5G core network can complete the registration procedure for UEs permitted to use AIML services.

702. According to the procedures described in FIGS. 6a, 6b, and 6c, the 5G core network can complete the procedure for establishing a PDU session for the application if the UE satisfies the operation type and operation conditions that allow the AIML application to be used. UE's AIML application and AF's AIML server can transmit/receive data.

703. AF can recognize that an AI/ML application has been executed in the UE, and can determine whether AI/ML auxiliary information should be provided from the 5G core network to service the AI/ML application. For example, AI/ML auxiliary information that can be provided from the 5G core network may include network-related collection/analysis information and UE behavior-related collection/analysis information, and may be included in the operation type and/or operation condition of the AI/ML application. The necessary information can be determined accordingly.

704. AF can request NEF to certify the types of AI/ML auxiliary information it is allowed to receive from the 5G core network. At this time, AF may be the Data Collector of the AI/ML Application Server described in Figures 4a and 4b. AF can use the Naf_SDMAuthorization_Create Request message and can include at least one of GPSI, UE IP address, and Application ID.

705. Based on the information received from the AF in step 705, the NEF can identify the UE's identifier and the PDU Session for the application service provided by the AF to this UE. For example, NEF can determine the SUPI mapped to the GPSI received from AF, and can determine the PDU Session ID using the UE IP address and Application ID.

706. NEF may request subscriber information related to AIML assistance data from UDM. NEF can use the Nudm_SDM_Get Request message, and SUPI, "AIML assistance data" as the value of the type of subscriber information requested, DNN, S-NSSAI of HPLMN, Serving PLMN ID, NID, PDU Session ID, Application ID, AF ID At least one of them can be provided. The S-NSSAI of the DNN and HPLMN may correspond to the DNN and S-NSSAI of the PDU Session identified in step 705. If the NEF already stores subscriber information related to AIML assistance data, steps 706 to 709 may be omitted.

707. UDM can request subscriber information related to AIML assistance data from UDR. UDM can use the Nudr_DM_Query Request message and can provide at least one of SUPI, "AIML assistance data", DNN, S-NSSAI of HPLMN, Serving PLMN ID, and NID as a value for the type of subscriber information requested. The S-NSSAI of the DNN and HPLMN may correspond to the DNN and S-NSSAI of the PDU Session identified in step 705. If the UDM already holds subscriber information related to AIML assistance data, steps 707 to 708 can be omitted.

708. UDR can provide subscriber information related to AIML assistance data to UDM. The subscriber information related to the AIML assistance data may include at least one of a list of AIML assistance data allowed for an AIML application or AF, and a list of AIML assistance data allowed for a PDU session established for the AIML application. The list of allowed AIML assistance data may include a list of collection/analysis data types related to the network, and/or a list of collection/analysis data types related to UE behavior. UDR can use the Nudr_DM_Query Response message.

709. UDM can provide subscriber information related to AIML assistance data to NEF. UDM can use the Nudm_SDM_Get Response message.

710. Based on the information received in step 709, the NEF may determine whether there is AI/ML auxiliary information permitted to the AF.

711. The NEF may provide the result determined in step 710 as a result of authentication as the type of AI/ML assistance data allowed to be provided from the 5G core network requested by the AF in step 704. For example, if there is any AI/ML assistance information allowed to the AF in step 710, the NEF provides the AF with a list of allowed AIML assistance data received from the UDM in step 709 along with result information indicating that authentication was successful. can do. In step 710, if there is no AI/ML auxiliary information allowed to the AF, the NEF may provide a reason for the failure along with result information that authentication has failed, and the reason for the failure may be, for example, obtaining/providing AIML auxiliary information. May include Not Allowed.

712. The AF may store and process the list of allowed AI/ML auxiliary information received in step 711 (which may include a list of allowed AI/ML auxiliary information at the PDU Session level). AF may initiate an event exposure procedure for AI/ML auxiliary information included in the list of allowed AI/ML auxiliary information.

713. AF can request AI/ML auxiliary information needed to service AI/ML applications from NEF. At this time, the requested AI/ML assistance information may be information included in the list of allowed AI/ML assistance information received in step 712. AF can use the Nnef_AnalyticsExposure_Subscribe message and notify that it is requesting Analytic Reporting Information, and the target of the request may be the requested AIML assistance information.

714. NEF may forward the request in step 713 to NWDAF. NEF can use the Nnwdaf_AnalyticsExposure_Subscribe message and notify that it is requesting Analytic Reporting Information, and the target of the request may be requested AIML assistance information.

715. NWDAF may perform collection and analysis of information related to the requested AIML assistance information according to the request in step 714.

716. NWDAF may provide NEF with the results of the collection and analysis of information related to requested AIML assistance information. NWDAF can use the Nnwdaf_AnalyticsExposure_Notify message to notify that it provides analysis reporting information, and the content may include collection and analysis information related to requested AIML assistance information.

717. NEF may provide AF with the results of the collection and analysis of information related to requested AIML assistance information. AF can use the Nnef_AnalyticsExposure_Notify message to notify that analysis reporting information is provided, and the content may include collection and analysis information related to requested AIML assistance information.

718. AF may store and process collection and analysis information related to requested AIML assistance information received. Referring to Figures 4a and 4b, the Data Collector of the AI/ML Application Server can store the received information and provide it to the AI/ML engine to assist in the server's model and data learning and data generation.

8A and 8B are flowcharts for explaining procedures related to providing network information for AI/ML applications in a 5G system, according to an embodiment of the present disclosure. More specifically, Figures 8A and 8B illustrate how to provide information to AF during the event exposure procedure of the core network. FIGS. 8A and 8B include the system described in FIGS. 1 to 7C, and the corresponding content may have been omitted from the description of FIGS. 8A and 8B.

801. According to the procedures described in FIGS. 5A, 5B, and 5C, the 5G core network can complete the registration procedure for UEs permitted to use AIML services.

802. According to the procedures described in FIGS. 6a, 6b, and 6c, the 5G core network can complete the procedure for establishing a PDU session for the application if the UE satisfies the operation type and operation conditions that allow the AIML application to be used. UE's AIML application and AF's AIML server can transmit/receive data.

803. According to the procedures described in Figures 7a, 7b, and 7c, the AF can authenticate AI/ML auxiliary information that can be provided from the 5G core network, and collect and analyze information about the allowed AI/ML auxiliary information to the core network. You can request it.

804. If the operation of the AI/ML engine and/or Data Receiver/Transmitter may vary depending on the operation type and operation condition of the AI/ML application in the UE, AF may initiate an event exposure procedure related to the operation type and operation condition. .

805. AF can request NEF to notify when events related to the operation type and operation condition of the AI/ML application occur. The Naf_EventExposure_Subscribe message can be used, and may include at least one of GPSI, SUPI, and UE IP address as the identifier of the UE subject to event exposure, and may include Application ID and AIML operation type (operation condition) as the identifier of the subject of the event. ), and may include at least one of AF ID.

806. The NEF may identify the UE subject to event exposure based on the AF request information in step 805 and identify the target of the event. NEF is a change in the AIML operation type and/or operation condition of the AIML application that is the target of the event, changes related to the PDU session or subscriber information for the AIML application of the UE that is the target of the event, and to the AIML application or AF that is the target of the event. It is possible to determine the network entity(s) that can detect changes in allowed AIML assistance data. For example, if the location operation condition is included in the target of the event, it may be determined that the network entity that can detect changes related to the mobility of the UE is AMF.

807. According to the result of the judgment in step 806, the NEF informs the UDM of changes in subscriber information related to the AIML operation type and/or operation condition of the AIML application of the corresponding UE and/or subscriber information related to the AIML application or AIML assistance data permitted to the AF. You may request to be notified of any changes in information. NEF can use the Nnef_EventExposure_Subscribe message.

808. According to the determination result of step 806, the NEF may request the AMF to notify the AMF if a change related to the mobility of the corresponding UE occurs. Information about the mobility of the UE includes UE reachability (this may be a change in the UE's connection state and/or the UE's registration state), and Area Of Interest (this may be a change in whether the UE is located within the service area of the AIML applicatio). At least one of may be included. NEF can use the Nnef_EventExposure_Subscribe message. AMF can notify NEF when a change occurs and can use the Nnef_EventExposure_Notify message.

809. According to the determination result of step 806, the NEF may request the SMF to notify if a change related to the session occurs. Information about the session may include PDU Session Status (this may be a change in whether the PDN Session is maintained). NEF can use the Nnef_EventExposure_Subscribe message. SMF can notify NEF when a change occurs and can use the Nnef_EventExposure_Notify message.

810. Depending on the decision in step 806, the NEF may request the PCF to notify the PCF of any changes related to the policy. Information about the policy may include at least one of changes in AM policy, SM policy, and UE policy related to AIML operation type and/or operation condition. NEF can use the Nnef_EventExposure_Subscribe message. PCF can notify NEF when a change occurs and can use the Nnef_EventExposure_Notify message.

811. When the NEF receives a response to the notification request in steps 807, 808, and 809, it may forward it to the AF. NEF can use the Naf_EventExposure_Notfiy message.

812. When the AF receives notification of the occurrence of an event related to the operation type and operation condition of the AI/ML application in step 811, the AF can determine the cause of the event occurring in communication between the UE and the AI/ML application server based on this. For example, if the communication status between the AI/ML application server and the UE is not smooth, AI/ML determines whether the cause of the communication failure is a network problem or a change in the UE's subscriber information based on the notification of the occurrence of the event in step 811. , it is possible to determine whether it is due to a change in the permission information for the application server. The AI/ML application server may not have received the notification of step 811, or may determine that a problem with the core network is not the cause of the communication failure based on the notification of step 811. In this case, the AI/ML engine, data You can determine whether there is a problem with the collector and/or data network. AF can make a decision on data transmission according to the judgment result. For example, if the AF is notified by the core network that the session has been released or the UE is in an unreachable state, the AF may temporarily postpone and buffer the transmission of downlink data. As another example, if the AF is notified by the core network that the subscriber information has changed to no longer allow the corresponding AI/ML application, it may stop data transmission and end data processing for the corresponding UE.

Figure 9 is a block diagram of a device according to an embodiment of the present disclosure.

Apparatus 900 may also be referred to as an electronic device. Device 900 may implement any of the entities described in this disclosure. For example, the device 900 may implement one of the UE and a plurality of NFs described through FIGS. 1 to 8B. Device 900 may include a controller 910, transceiver 920, and memory 930.

The controller 910 may be connected to other elements (eg, transceiver 920 and memory 930) within the device 900 to control the operations of the other elements. Controller 910 may control itself and other elements of device 900 to cause device 900 to perform at least one operation. The operation of the device 900 can be interpreted as being substantially executed by the controller 910. Controller 910 may be implemented through at least one processor.

The transceiver 920 may include circuitry (i.e., communication circuitry) necessary for communication. Device 900 can communicate with other devices through transceiver 920. The transceiver 920 uses at least one of various wireless access technologies, such as long term evolution (LTE), LTE-Advanced (LTE-A), code division multiple access (CDMA), orthogonal frequency division multiplexing (OFDM), Bluetooth, etc. Support is available, but is not necessarily limited to this. Transceiver 920 may provide capabilities for communication for device 900 using any known wireless access technologies.

Memory 930 may be referred to as a 'non-transitory computer readable storage medium' to distinguish it from a medium for transmission of information. The memory 930 may be implemented through at least one of random access memory (RAM), read-only memory (ROM), hard disk, CD-ROM, and solid state drive (SSD), but is not limited to this and is not limited to information. It can be implemented through all possible types of storage media that can store and read. Memory 930 may store instructions executable by controller 910. When the commands are executed by controller 910, controller 910 (or device 900) may execute at least one of the operations of device 900 described in this disclosure. The memory 930 may further store temporary or permanent data necessary for the operation of the controller 910.

Methods according to embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present invention.

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM: Compact Disc-ROM), Digital Versatile Discs (DVDs), or other types of It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, multiple configuration memories may be included.

In addition, the program may be operated through a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present invention through an external port. Additionally, a separate storage device on a communication network may be connected to the device performing an embodiment of the present invention.

Meanwhile, the embodiments disclosed in the specification and drawings described above are only provided as specific examples to easily explain the contents of the present invention and to aid understanding, and are not intended to limit the scope of the present invention. Therefore, the scope of the present invention should be construed as including all changes or modified forms derived based on the technical idea of the present invention in addition to the embodiments disclosed herein. Additionally, each of the above embodiments can be operated in combination with each other as needed as long as there is no technical contradiction.

Claims (19)

A method for handling information related to AI/ML (artificial intelligence/machine learning) services by an access and mobility management function (AMF) in a wireless communication system,
Receiving a registration request message including a list of requested AI/ML operation types from a user equipment (UE);
Identifying at least one operating condition for each AI/ML operation type included in the list of AI/ML operation types allowed for the UE and the list of AI/ML operation types allowed for the UE;
Based on the list of requested AI/ML operation types, the list of AI/ML operation types allowed for the UE, and the at least one operating condition, the UE is included in the list of requested AI/ML operation types. determining whether it is permissible to use at least one AI/ML operation type; and
If the UE determines that it is not permitted to use at least one AI/ML operation type included in the list of requested AI/ML operation types, sending a registration rejection message to the UE, comprising:
method. According to claim 1,
The list of requested AI/ML operation types includes the at least one AI/ML operation type supported by at least one application installed in the UE.
method. According to claim 1,
Identifying a list of AI/ML operation types allowed for the UE and the at least one operating condition includes:
Transmitting a message to request subscriber information for the UE to unified data management (UDM); and
In response to a message for requesting subscriber information for the UE, receiving a response message from the UDM including a list of AI/ML operation types allowed for the UE and the at least one operating condition; ,
A list of AI/ML operation types allowed for the UE included in the response message received from the UDM and the at least one operation condition are obtained by the UDM from a user data repository (UDR),
method. According to claim 1,
When the UE determines that it is permitted to use at least one AI/ML operation type included in the list of requested AI/ML operation types, it asks a policy control function (PCF) to determine the AI/ML operation type permitted for the UE. Transmitting an access and mobility management (AM) policy creation request message for the UE, including a list of ML operation types and the at least one operation condition;
Receiving, from the PCF, an AM policy creation response message including a list of AI/ML operation types allowed for the UE and a policy control request trigger (PCRT) based on the at least one operating condition—the PCRT exists. includes at least one of a change in UE presence within a reporting area, a change in network data analytics function (NWDAF) information, and a change in the permitted AI/ML operation type; and
After receiving the AM policy creation response message, if the UE satisfies registration conditions, further comprising transmitting a registration accept message to the UE,
method. According to claim 1,
Transmitting, to a base station associated with the UE, a message for requesting location information of the UE, including information on an area of interest, wherein the information on the area of interest corresponds to an AI/ML service area associated with the UE. Contains an identifier for each of at least one tracking area -; and
Further comprising receiving a message containing location information of the UE from the base station,
method. According to claim 1,
Transmitting, to a network data analytics function (NWDAF), a message for requesting collection and analysis of mobility information of the UE, including information on an area of interest - the information on the area of interest is an AI/Air associated with the UE Contains an identifier for each of at least one tracking area corresponding to the ML service area; and
Further comprising receiving a message containing at least one of the mobility information of the UE collected from the NWDAF and the mobility information of the UE analyzed,
method. According to claim 1,
Transmitting, to a policy control function (PCF), a UE policy creation request message for the UE, including a list of AI/ML operation types allowed for the UE and the at least one operating condition;
UE comprising, from the PCF, a list of AI/ML operation types allowed for the UE and a UE policy and policy control request trigger (PCRT) for AI/ML services for the UE based on the at least one operating condition Receiving a policy creation response message; and
Further comprising delivering to the UE a UE policy for the AI/ML service for the UE,
The UE policy for the AI/ML service includes a policy related to AI/ML model transfer, and a policy related to AI/ML data transfer, each including at least one of transmission frequency, transmission size, and transmission performance time. containing at least one,
method. According to claim 1,
The AI/ML operation type of the AI/ML application installed in the UE is included in the list of AI/ML operation types allowed for the UE, and the AI/ML operation type of the AI/ML application satisfies the corresponding operation condition. In this case, receiving a PDU (protocol data unit) session establishment request including information about the AI/ML operation type of the AI/ML application from the UE;
In response to receiving the PDU session establishment request, determining whether the UE is located within an AI/ML service area associated with an AI/ML operation type of the AI/ML application; and
When the UE determines that it is located within an AI/ML service area related to the AI/ML operation type of the AI/ML application, the AI/ML operation type of the AI/ML application to a session management function (SMF), at least one Transmitting a PDU session creation request message containing at least one operating condition related to an AI/ML operation type and information indicating that the UE is located in an AI/ML service area related to the AI/ML operation type of the AI/ML application. Further comprising the steps of:
method. According to clause 8,
In response to the PDU session creation request message, when receiving a PDU session creation acceptance message from the SMF, a non-access stratum (NAS) containing information related to allocation of access network resources for the UE to a base station associated with the UE Further comprising transmitting an N2 PDU session request message including the message,
method. A method for handling information related to AI/ML (artificial intelligence/machine learning) services by a session management function (SMF) in a wireless communication system,
From an access and mobility management function (AMF), an AI/ML operation type of an AI/ML application installed on a user equipment (UE), at least one operation condition related to at least one AI/ML operation type, and the UE Receiving a protocol data unit (PDU) session creation request message including at least one of information indicating that the AI/ML application is located in an AI/ML service area related to an AI/ML operation type;
Identifying subscriber information required for session management for the UE - Subscriber information required for session management for the UE includes a list of AI/ML operation types allowed for the UE and AI/ML operations allowed for the UE. Contains at least one of at least one operation condition for each AI/ML operation type included in the list of types -;
AI/ML operation type of the AI/ML application, at least one operation condition related to the at least one AI/ML operation type, an AI/ML service area where the UE is associated with the AI/ML operation type of the AI/ML application determining whether the AI/ML application is operable in a requested PDU session based on at least one of information indicating that the AI/ML application is located within the UE and subscriber information required for session management for the UE; and
When determining that the AI/ML application is not operable in the requested PDU session, transmitting a PDU session establishment rejection message to the AMF,
method. According to claim 10,
When it is determined that the AI/ML application is operable in the requested PDU session, the AI/ML operation type of the AI/ML application and at least one related to the at least one AI/ML operation type are sent to a policy control function (PCF). Transmitting a session management (SM) policy creation request message containing at least one of an operating condition and information indicating that the UE is located in an AI/ML service area related to an AI/ML operation type of the AI/ML application. step; and
From the PCF, an AI/ML operation type of the AI/ML application, at least one operation condition related to the at least one AI/ML operation type, and the UE receives an AI/ML operation type associated with the AI/ML application. Further comprising receiving an SM policy creation response message including a PCRT and an SM policy determined based on at least one of information indicating that the ML service area is located,
method. According to clause 9,
Further comprising sending a message to a network data analytics function (NWDAF) to request collection and analysis of mobility information of the UE in order to monitor operating conditions related to the AI/ML operation type of the AI/ML application. do,
The message for requesting collection and analysis of mobility information of the UE includes information about the area of interest,
The information about the area of interest includes an identifier of each of at least one tracking area corresponding to an AI/ML service area associated with the UE.
method. A method for handling information related to AI/ML (artificial intelligence/machine learning) services by a network exposure function (NEF) in a wireless communication system,
Receiving a message from an application function (AF) to request authentication of the type of AI/ML auxiliary information for the service of the AI/ML application executed in the UE;
Identifying subscriber information related to the AI/ML auxiliary information;
Identifying allowed AI/ML auxiliary information based on the identified subscriber information;
Comprising transmitting a message containing a list of the identified permitted AI/ML auxiliary information to the AF,
method. According to claim 13,
The steps for identifying subscriber information related to the AI/ML auxiliary information are:
Transmitting a message to request subscriber information related to the AI/ML auxiliary information to unified data management (UDM); and
Receiving a response message containing subscriber information related to the AI/ML auxiliary information from the UDM,
Subscriber information related to the AI/ML auxiliary information included in the response message includes a list of AI/ML auxiliary data allowed for the AI/ML application or the AF, and AI allowed for the PDU session established for the AI/ML application. /ML Contains at least one of the list of auxiliary data,
method. According to claim 13,
Receiving, from the AF, a message for requesting AI/ML auxiliary information included in the list of allowed AI/ML auxiliary information for an event exposure clause;
Forwarding the request for the AI/ML auxiliary information to a network data analytics function (NWDAF);
Receiving a message from the NWDAF for notifying the results of collection or analysis of information on the AI/ML auxiliary information; and
Including delivering the results of collection or analysis of information about the AI/ML auxiliary information to the AF,
method. According to claim 13,
Receiving a message from the AF to request notification of the occurrence of an event related to the operation type and operation conditions of the AI/ML application;
determining at least one network entity capable of detecting a change in the AI/ML application or the allowed AI/ML auxiliary information associated with the event;
Receiving a message for requesting notification from the at least one network entity of an occurrence of a change in the AI/ML application or the permitted AI/ML auxiliary information;
Receiving a message for notification of the occurrence of a change in the AI/ML application or the permitted AI/ML auxiliary information from the at least one network entity; and
A step of delivering to the AF a notification of the occurrence of a change in the existing AI/ML application or the allowed AI/ML auxiliary information,
Notification of the occurrence of a change in the allowed AI/ML auxiliary information is used by the AF to determine the cause of the event,
method. A device for access and mobility management function (AMF) in a wireless communication network,
transceiver; and
At least one processor connected to the transceiver,
The at least one processor is configured to operate according to the method of any one of claims 1 to 9,
Device. A device for session management function (SMF) in a wireless communication network,
transceiver; and
At least one processor connected to the transceiver,
The at least one processor is configured to operate according to the method of any one of claims 10 to 12,
Device. A device for network exposure function (NEF) in a wireless communication network,
transceiver; and
At least one processor connected to the transceiver,
The at least one processor is configured to operate according to the method of any one of claims 13 to 16,
Device.

Images